Oh… I think you’re right… Maybe I should read the whole thing before trying to help.
If it is GP Sequencer, then I have no idea 
Hi Kåre!
Thanks for the tips! Dragging the slider with the mouse is not working very well for me.
Alan KM6VV
Hi,
I’m on the Sequence screen. I see the lock and the green arrows now, but I thought they were for the project! Thanks, that seems to work (simulated, anyway for now).
The mouse scroll and pgup/pgdn keys work too!
Great news! Thanks.
Alan KM6VV
Erm… I’m a little lost here 
Just to clarify, the GP Firmware/Sequencer is referring to the SSC-32 Sequencer??
And I just need to plug in a 24LC256 or 512 external EEPROM to my current board to store in the sequences? Cos I’ve got a couple of spare 24CL512 lying around 
Do I need to upgrade my Atmel chip together with SSC32-2.01GP firmware ?? And upgrade to which: ATMEGA168-20PU or ATMEGA168V-10PU ??
I’m using this version SSC32-1.06XE (when I ordered) of the sequencer
GP firmware is referring to the SSC-32 servo controller. It’s the code that makes it work. XE has a 12 servo hexapod sequencer built in to the firmware, but GP has two general purpose sequencers built in. It can store sequences in the EEPROM and the host micro can select which sequence to run, and at what speed and direction. We are uploading some instructions for it’s use today.
The 1.03GP firmware works, but it had a bug that was not addressable with the Mega 8 chip, so we decided to drop that version and port it to the mega 168.
Yes we are selling a preprogrammed 168 for $10.00.
You seem to be using “servo controller” and “sequencer” interchangeably, they are not the same thing. Hope this helps…
Ok, the GP firmware is the SCC32 servo controller. But where do I get this software? I was reading the manuel and it mention about the alternative GP sequencer Firmware (pg 14)
So this GP sequencer firmware is also part of the Visual Sequencer?
Does this bug occurs in the 1.06XE version? OR do I have to upgrade both the chip and firmware before I can use the EEPROM?? OR can I don;t upgrade and still use the EEPROM?
Great! But With the addition of postage + currency convertion + tax… It getting pretty $$$ for a chip . I was planning to order 2 piece from farnell and burn in the firmware myself once I can sort out how to go about doing it 
Another NEW question:
It just hit me, I’ve got spare PARALLAX RF TX/RX antennas link lying in my lab. Am I able to replace the serial cable to my com with these instead?
I know there are ppl already using Bluetooth to control their bot, but now I wan to use RF instead. Is it possible since the antennas are one way only?
Meaning: They are specifically TX antenna and RX antennas. I planning to link a RX to the SSC32 and a TX to the computer serial port via a MAX232 line driver cct.
From the data sheets: there are 3 pins: Gnd, Power, Data
The power connection is straight forward connection, but the data pin is the one that I am concern. Do I also connect it to the RX pin on the bot?
OR can I convert the DB9 via a MAX232 line driver and link it to the antenna pins?
Now I’m running a impossible tight time schedule, so for the presenation/demo I plan to run my quad from the computer terminal using these RF antennas and using a onboard power, so that my quad can “walk” around without dragging a cable behind it
**This site ROCKS! 
It’s on the product page, scroll to the bottom.
lynxmotion.com/Product.aspx? … #downloads
No, but the Visual Sequencer (SEQ) does make it easy to fill the EEPROM with properly formatted data for the Projects you teach the robot to do with the SEQ. This greatly simplifies the use of the GP sequencer engines in the SSC-32.
1.06XE does not support the EEPROM. Only the GP versions do. You can use the older 1-1Gbeta (sorry not 1.03GP) will work, but like I said there is a small bug that was not correctable with the mega 8 chip. I recommend you upgrade the chip if you are interested in experimenting with this.
We have everything you need to burn your own chip.
lynxmotion.com/images/html/proj078.htm
No no no, the programming is bidi, you can’t use one direction RF for programming.
Hope this helps…
Can you please upload the fuse bits that have to be programmed for the bootloader?
I’ll get the info and post it later today, hopefully… Sorry
Mike told me…
“They are similar to the ATmega8 bootloader, except they need to have a 256-word boot block. I don’t have the exact settings here at work so it will need to wait for tonight.”
I will post the info tomorrow.
Oic, the servo controller also send back data to the computer? I thought it was a 1-way thing: Com — data ----> servo controller.
Following the Bluetooth instructions, can I assume I just need to connect the RX to TX and TX to RX and Gnd of the DB9 on the computer to that of the servo controller?
Is there any programming settings that I need to reconfigure? OR it’s a simple plug and play issue
Thank you
Please redownload the btldr168.zip file. It now includes a jpg screen cap of the fuse bits.
Programming an Atom with the Bot Board is bidi and will not work as a one way serial connection.
The SSC-32 can work perfectly with a one way connection if you are controlling it from a micro or an application that does not need information back from the SSC-32.
Thank you Sir
I mean to ask, can I replace the bluetooth adapter and use RF antennas to control the servo control from the PC terminal?
** I’ve just tested using the same connections as the bluetooth adapter but fail to connect to the computer.
I’ve interfaced the RF anetennas to com port 1 on the computer and another pair onto the SSC32, but I’m unable to get a connection.
I’ve tried changing the different baud rates and even flipping RX/TX connection to the SSC32 board like the bluetooth tutorial BUT still failed… 
Wonder if there is anyone who have tried using RF instead of the bluetooth adapter?
Cheers 
What PC application are you using to talk to the SSC-32? SEQ, or LynxTerm, or something else? Have you used the RF modem sucessfully before? What baud rate is it capable of working at? 2400, 9600? You can’t just start changing connections and setting haphazardly and hope it will work.
You may need to do basic trouble shooting on the wireless equipment. I’d jumper the tx/rx on the remote wireless device, and then see if characters sent from the pc are received back at the pc.
I thought the same thing, but it’s a one way trip with this device.
This is where a cheap analog multimeter may be of use (walmart has them for ~$10, and the cheap ones do not have dampened meters). Connect the meter between the serial output and ground on the remote wireless device such that the meter is showing a positive voltage (usually ~5-12v). Then send a long string of "a"s from the pc. If the remote wireless device is sending out serial data, one should see a momentary quick dip in voltage on the meter. This can be first tried on the serial port output on the pc to see how it works. It is a simple hardware way to see if something is actually being sent from the serial port.
I’m using the same method as mention in the Bluetooh thread.
Instead of LynxTerm --> BT BT–> SSC32 I’m using LynxTerm --> RF RF–> SSC32
As the pin connections are all similar to that of the BT module: TX/TR/+5/GND
Tried sending “VER” as mention in the thread but got 0 byte read.
Will try this out on monday.
cheers