Bug List / Command Quirks / Common Misconceptions

Lynxmotion Electronics & Software
1

Introduction
This heading list will be heavily moderated. Post and discuss the potential bugs here, and we will compile a concise list in this sticky post. After defining the trouble, the information will be added here, and the original posts will be removed. Please restrict the posts to programming issues concerning the SSC-32 only.

SSC-32 returns the incorrect values using a Stamp or Atom
Fix: Make sure you’re using the firmware version 1.06XE (1-06XE.abl)

Servos shake or go limp when moving several servos at the same time
Fix: This is usually caused by the microcontroller on the SSC-32 resetting due to low voltage. This can be caused by powering the VS (servo power) and VL (logic power) from a single supply that is not capable of delivering enough current. To fix this, connect a 9vdc battery clip to the VL terminal, a 6vdc supply, battery, etc. to the VS terminal and REMOVE the VS1=VL jumper. This isolates the logic power from the servo power.

Firmware can’t be undated at any other baud rate besides 115.2kb
Fix: This is normal. the SSC-32 firmware update requires the baudrate be set to 115.2kb on the SSC-32 and the program doing the update.

Edit: I added the firmware update information.

2

There was a bug with the QP command when it is used with offsets. For example if you create an offset for servo 0.

#0 PO -100 cr

When you tell the servo to go to center.

#0 P1500 cr

It actually goes to position 1400 (internal to the SSC-32).

The QP (query pulse) command has a resolution of 10uS. If you read the position it would respond with.

QP0 cr 140

Not the 150 you would expect. So we are testing the beta that has this fixed. We will post it later this week.