What are the main differences between the two? I know that the V2 has the Atmel 168, but what does that mean in terms of features??? Sorry if this has been posted before, I’ve been using the SSC-32 since it came out and just recently bought a V2 so I want to know what sort of new features I can take advantage of…
Hi Tom,
first read this tutorial for the SSC-32 (V2)
lynxmotion.com/images/html/build136.htm
I think the main difference is the controller and the integrate eeprom to use the GP Sequencer with the right firmeware version.
lynxmotion.com/images/html/build137.htm
Greatings
Matthias
BTW: The link for the SSC-32 Manual is not working on www.lynxmotion.com Error message 404 Page not found
The link appears to be working.
For the best answer to your question look at the SSC-32 product page / more information. It shows the progression of the firmware, listing changes as they were released. I will condense it for you.
Ver 2.01XE fixed a pulse offset bug that still exists in Ver 1.06XE. I will try to dig up the details. Beyond that Ver 1.06XE continues to work perfectly with all of our applications.
The XE version has the 12 servo hexapod sequencer built in. The majority of the improvements are with processor registers to allow storing servo offsets, startup positions, startup string, and other comm parameters right on the chip.
There are more improvements to the GP firmware. The Ver 2.XXGP release has all of the other improvements plus some General Purpose Sequencer specific bug fixes and new features. If you are working with the GP Sequencer then V2.04GP is what you want!
So, if you are using the SSC-32 in a project that doesn’t require the GP Sequencer, and it’s working for your project there is no reason to upgrade. The core functionality remains unchanged in all releases.
Oh, also the V2 SSC-32 includes the EEProm.
Hope this helps…
I think the addition of the servo “stop” command is significant. A servo can be given a timed move command, and when an event occurs, such as foot contact with a surface, the servo can be stopped at that position. Then the current servo position can be queried to determine the position of the servo without having to read the pot internal to the servo.
Thank you all for the info! It’s not the first time, but man, I can’t wait to get my little package from LM!!!
