Don't ad-block us - support your favorite websites. We have safe, unobstrusive, robotics related ads that you actually want to see - see here for more.
0 Members and 1 Guest are viewing this topic.
And if so, would its storage be accessible via the code you load onto the MCU? If for example I wrote a sufficient amount of code to surpass the onboard 64kB of space, it would utilize this extra space for the code and various serialized/data logging? Not sure what this would require doing but that's my end result.
64k seems like a little, but once compiled, code for these microcontrollers is very small. You won't be filling itnup anytime soon. Out of all of the Axons sold, only one person has filled the 64k, and thst was with a 20+ servo humanoid with kinematics.
I'm a web programmer by day, and am entirely new to working on embedded/small devices such as the Axon (any MCU for that matter). That said I can easily see myself surpassing the 64kB of space within a few months of tinkering.
Has anyone experimented with this? I'm wondering how easy or difficult it would be to make your robot accept, lets say, an SD card for a set of specific directions.
With a controller that can "reprogram in action" (those that can be used with a bootloader), it would be possible to store a range of programs on SD and let it change its own program in response to environmental changes or similar.
The program just needs to have a command interpreter which fetches the next direction and translates it into whatever action is needed (eg. F40 => rolling forward 40mm, 40s or whatever you choose).
Quote from: Soeren on June 24, 2010, 07:06:53 PMWith a controller that can "reprogram in action" (those that can be used with a bootloader), it would be possible to store a range of programs on SD and let it change its own program in response to environmental changes or similar.So let me see if I understand you here. This would basically be switching out the code on the fly, loading the new binaries(?) from the SD card according to the condition?
or..Quote from: Soeren on June 24, 2010, 07:06:53 PMThe program just needs to have a command interpreter which fetches the next direction and translates it into whatever action is needed (eg. F40 => rolling forward 40mm, 40s or whatever you choose).Would essentially have the ability to accept commands that are received via some means (bluetooth etc), and then run some code set to respond via the command issued?
So if I'm looking for something I could upgrade the space for the code, what kind of devices/architecture would make sense starting at the beginning of the design? Just so I'm aware of what to shop for or put on my x-mas list, ha.
But I would like to get to a point of programming enough logic to toy with AI. And speech recognition I'm sure is no small use of space. I may end up using an ARM core or something more powerful at that point, right now I'm just going to see how far I can get with the devices I'll be using (Axon MCU, DSP etc..) and learn the ropes.