Robot Dude wrote:
We also intend to reinstate the open source status for the SSC-32's firmware that was originally released as open source.
We are going to invest in more PC based robotics control solutions as well, using the powerful FlowStone visual programming language and USB based electronics.
great to hear about the open source status, i would sure like to take a look at that code.
ive writen a new protocol somewhere in a txt that i would like to try someday, this would greatly decrease the time i would take to talk with the SSC-32.
not sure about the pc based robotic control solutions using "FlowStone" ? visual programing but, i would sure like to see an analog/digital inputs device similar to the SSC-32 but with 32 input instead of 32 output.
or even better... a new SSC called the "SSC-X64" with 32 servo outputs and 32 inputs for the sensors.
all that in the same foot print of the actual SSC-32.
my greatest limit in my project so far is the sensor inputs, the SSC-32 provide 4 inputs which is great, but thats just not enough
i did look on the web for inputs solution and so far its not looking great.
imo robotic developpement should go toward mobile device support.
all these micro controller and other device doesnt make much sense to me, since mobile devices(more precisely Pocket PC platform) are rougly the size of these boards, but offer ALOT more capabilities/posibilities
just to list a few
200-600 + mhz of computing power
onboard battery/power supply and charging cercuitry
battery voltage sensor
battery temperature sensor
huge built-in storage and ram
CF, SD storage support
toutch screen monitor
3d graphic card
sound card(sound input/ouput)
and you can find/buy these devices for about the price of a SSC-32!
but the main point is software developpement, these device allow to make high level/complexe application that imo will be needed to build good autonomous machines and good software to interface human/machine communication.
also, win32_CE developpement is usualy very eazy to make crossplatform software with desktop/laptop window OS, which is the nicest feature, mean that the library i wrote to talk with the SSC-32 in my win32 enviroment is also compatible winCE, however, winCE is not fully compatible win32, but in most of the case the same code will run in both environments