I am sending RoboRealm the required stuff to get the SSC-32 supported with this software. From the information I have received they should have it done in as little as one week after they receive the SSC-32’s. They are asking for an engineer to help test the interface once created. Any takers?
Ive only seen the roborealm a few days ago. I think the important bit will be to make sure they get the control of the SSC right. So if you have enough experience with it…
Considering how most people use the SSC-32, I’ve been thinking that direct control of it from roborealm might not be the ideal way to go.
Most peoples robots that use the SSC are fairly unique. Not in the way that 2 RoboNovas are unique in there home position trims. Most of them are much more individual than that. Some radically so.
We all have our own library of sequences we have built, some are using processors to execute them, some using SEQ but most of these sequences would not be useable on anyone elses robot except in the simplest of ways.
Driving the SSC directly would circumvent the processors and SEQ making the pre-built sequences inoperable.
Might it not be better to have roborealm interface to SEQ. Maybe just a command as simple as EXECUTE SEQUENCENAME. SEQUENCENAME being a string that you enter in SEQ as we do now to name the routine and the same name in roborealm could be passed through the interface.
That way all the configs and everything would still be in play.
How it would interface to those bots using on board processors I’m not certain. Perhaps through a similar command through a serial port. That feature I believe may already exist in roborealm. I believe Botboard has a serial port and could respond to a command in a similar manner.
I think it depends what the interface from RoboRealm is like. I can envision a way where an Atom microcontroller might receive the commands from RoboRealm, interpret them, and then command the SSC-32 to execute an appropriate sequence.
he SSC-32 and the Atom Bot Board (Basic Atom or Atom PRO) have serial ports, so RoboRealm would have to be using serial communications. This, could be via transparent wireless (Bluetooth, Zig-Bee, etc), which would not require the robot to be physically tethered to the PC.
This is just a scenario I can see being possible, but I am also assuming for now that the Atom could receive commands and then command the SSC-32. The Basic Atom may not be capable of this, but the Atom PRO has a hardware serial port also, so should be able to do it.
Of course, I may be way off in my thinking that this is possible too, at least with the Atoms.
I’ve just been experimenting with the serial aspect.
It works by assembling scripts based around the different supported modules. I believe it keeps looping around executing the different modules dependent on local variables and if-then statements.
The serial allows you to enter a string that can be ASCII and hex (in c notation) so it was quite simple to set up a #0P2000S1000\x0d to get the bot to turn its head in response to an if-then.
I think anything with a serial port and a processor could fairly easily be interfaced this way. Its just a case of getting to grips with the roborealm syntax’s
I think in the case of the SSC being directly controlled it might be different.
I just looked at one of my sequences, Turn Left which is 7 poses that make the bot turn left. Typing the code in would be easy enough but the timing would be a git. How to work out that one sequence has finished before the next can be started… Streaming Q’s at the SSC wouldnt be a good idea either
I do think it needs to talk to an intermediate app, i.e. SEQ which is already very adept at controlling the SSC.
The serial aspect does look good though and when I eventually decide which processor I’m going with I shall have some fun designing a protocol for it.
If my idea of actually having the Atom interpret the commands from RoboRealm and then controlling the SSC-32 works, then there shouldn’t be a problem. The Atom would be sending sequence commands to the SSC-32, and when it’s done it could send a return command back to RoboRealm, which must be able to do bi-directional communications. The Atom would be handling communications with RoboRealm in my scenario.
linuxguy, exactly my thinking. Thats if you have a processor on board, mine doesn’t at present and I imagine a few people are running the same way.
wowy7, roborealm is a video system capable of doing some rather clever analysis such as motion and object tracking. It has extensions and controls that allow it to talk to other devices thus controlling the actions of robots depending upon what the camera sees.
I’ll be using a webcam to play with RoboRealn. I bet it could be used with those neat small 2.4 GHz wireless cameras too. Get data from camera, process, send results back to robot via Bluetooth or some other wireless link, robot decides what to do and then does it (or executes a command sent from RoboRealm).
Laurent is putting the final touches on the new release of SEQ. It will have a socket server to receive commands form other software. You will have the ability to play projects, or sequences (plus speed and direction) from other programs, or from anywhere on the planet via the internet.
RIOS is next. It will have a more powerful set of socket server commends. It may be possible for RoboRealm to control an arm via RIOS. This would be incredibly powerful!
More on SSC-32 General Purpose firmware. The new SEQ update allows the sequences to be downloaded to the SSC-32’s EEPROM. So it will be easy to select which project or sequence to run, at what speed and direction directly from the SSC-32’s serial port. RoboRealm can surely be made to send these commands.
I do not however see RoboRealm sending commands to an Atom. There’s just too many different ways to do it.