Hi, i´m trying to develop my own hexapod for a school project.
So i have some doubts about the sequences.
Is it better to save the sequence data (steps, positions, time, etc…) as a table in the microcontroler that actually do the movements (EEPROM), and then just send commands for data read, or in a spreadsheet like excel and then send all this data to the controler at the same time that he´s doing the movements?
Or even save all the information in a spreadsheet, then send all the data to the controler, and just after all the data received the controler starts the sequence?
Actually, i don´t know the best way to manipulate this information, for example: The Lynx sequencer has a button to play the sequence, whats happening when the sequence is being played? Is the controler doing the movement at the same time that data is being received? Or the sequence is stored in the controler memory and the sequence program are just sending commands to call this information?
I want to develop a C# program that can do the sequences and then play then, i just dont know how to handle with all this information.
I don´t know if i just have to send commands like: go forward, backward, etc…or if i have to send all to tell the controller what he has to do!
Thanks for now!
I have the BB2 and the SSC-32 and I used the Visual Sequencer to develop all my move sequences such as walking, turning, moving arms, etc… The Seq project that contains all the Sequence movements when exported to a BAP program, it creates a word table at the beginning of the program, I guess like a spread sheet. The code can be modified to “call” each sequence as required, and run X-number of times. For example, if you have a 4 step sequence for walking, you need to run a loop so that it can walk a certain distance like 10 loops for 10 steps. Turning is the same thing; the more loops means the more it will turn.
The SSC-32 does not store the commands, unless you use the eeprom for the GP seq. If you do not use the eeprom, any commands sent to the ssc-32 will instantly run and will not respond to any new commands until finished with the first move command. So the way I have done it is to store the sequence steps as data in the code to be called on by the basic program. Since you are going to be using something other than the Mbasic language, I cant help with how to make the Mbasic export data convert to your language of choice.
In a nut shell, that’s how it works.
Do you have the BB2 or intend to use it? If so, then why not just use the code generated by Powerpod?
As has been mentioned, SEQ can generate an EEPROM file and a simple BAS file to execute it from the BB2 if your intent is just to repeat “canned” sequences.
If you want to “drive” your 'bot, then a PS2 or other remote (even autonomous) and IK running on the BB2 is the way to go.
Alan KM6VV
The “stop” command will stop a timed move command to a servo in the latest ssc-32 update.
Below is the stop command to which I was refering.
STOP 0-31 Immediately stops the specified servo at its current position. A space is optional before the servo number. STOP0
STOP 31

Below is the stop command to which I was refering.
STOP 0-31 Immediately stops the specified servo at its current position. A space is optional before the servo number. STOP0
STOP 31
Yep yep… and here is the link to the SSC-32 manual that covers that command as well:
Hi, thanks for your answers!
Actually i don´t even know what´s a BB2.
But as you are saying i can imagine that the BB2 is the responsable for sending the data for each step of the sequence to SSC32 execute it.
I was thinking that the programm that generates the sequence code itself send the commands directly to SSC32.
It must be a communication between the SCC32 and BB2, so the SSC32 need to inform the BB2 that the last command was completed and now it´s able to receive a nem command.
Is that right?
So the best way to do is to send a command, wait until the command is executed and then send a new command until the movement is completed?
Thanks1

Hi, thanks for your answers!
Actually i don´t even know what´s a BB2.
But as you are saying i can imagine that the BB2 is the responsable for sending the data for each step of the sequence to SSC32 execute it.
I was thinking that the programm that generates the sequence code itself send the commands directly to SSC32.
It must be a communication between the SCC32 and BB2, so the SSC32 need to inform the BB2 that the last command was completed and now it´s able to receive a nem command.
Is that right?
So the best way to do is to send a command, wait until the command is executed and then send a new command until the movement is completed?
Thanks1
BB2 is the Bot board 2. This is the board used to install the Basic Atom, Basic Atom Pro (BAP) and any other Basic Stamp compatable Micro Controller Unit (MCU). The MCU is a mini computer capeable of running Mbasic code to send sommands to the SSC-32 (Servo Controller) and the SSC-32 drives the servos as instructed.
If you have an SSC-32, you don’t need to have the BB2 fitted with an MCU to send commands; you can use your Seq software to send commands directly to the SSC-32 to make your bot move. Many people like to use MCU control, because it allows you to program IF… THEN… ELSE… conditions and cause your bot to move based off those conditions rather than running steps 1 through 10 in a linear fashion direct from your Seq software. Some people like to program their own software and run the SSC-32 from their PC using their custom code. The BB2 and the Atom Pro is a nice combination because all the processing is done locally on the robot and it’s very powerful. The New ARC32 boards that is soon to come out will offer even more power to your bot, and since it has both the SSC-32 and the Atom Pro all wrapped up into one, it will save space for even more goodies.
Oh, i got it! Thanks for yout explanation SN96, very helpfull!

If you want to “drive” your 'bot, then a PS2 or other remote (even autonomous) and IK running on the BB2 is the way to go.
Alan KM6VV
By the way, what´s IK?

By the way, what´s IK?
Google it and you’ll find alot of information about it.