SSC32U not driving servos but is communicating

I am able to connect via USB (Com3) using a Baud Rate of 115200, but I can’t drive any of the Servos. I have a 6 volt power supply capable of driving 3 amps connected to VS1. I am only trying to use Ch 0 - 15. I do not have anything connected to VL. I started with the VS-VL jumper off, read the manual again. Put the jumper on. Still no luck. Took jumper back off. Tried to tie VS1 and VS2 and use Ch 16. Nothing. I am only trying to drive a single servo. Nothing… Please help.
I was originally trying to use Skull Tracker, but then downloaded SSC-32 Servo Sequencer and connected and tried to drive 1 servo with mutliple different channels. Nothing. I did get the firmware version back when I sent the command VER from Servo Sequencer and I can see the lights flash when I send servo commands. Yes, I have tried a different servo, one that I know is working.

I did check power at the channels. I have 6.07 volts at each channel and .5 volts at the pulse pin without sending a signal. Manual said that I should not put power to the VL if I had sufficient power to VS1. I certainly understand NOT to put power to VL if the VS=VL is jumpered. It did not come jumpered.

The default baud rate of the SSC-32U is 9600. If you didn’t change the baud rate on the board, you can’t establish communication at 115200 from an external device.

See page 13, 34 on how to change and view the baid rate of the board. Hope this helps. If not, double check the connection of the servo to the board and make sure the black wire connects to ground, and the (normally) white or yellow wire connects to pulse. Red wire is always in the middle.

You seem to have followed the right way to troubleshoot:

  • Only VS1 powered
  • Have only one servo connected to the board
  • Use the SSC-32 Sequencer (use the slider to move the servo)
  • Ensure the servos are connected properly to the board

If the baud rate doesn’t resolve the issue, please send a few photos of the board and setup so we can take a look.

1 Like

I did change the baud rate on all 3 devices. I tried all 3 at 9600, 38400, and 115200. All 3 being software, laptop comm port, and SSC-32U. As I mentioned, the board is communicating. I was able to send the VER command to the board and received the firmware version back via Servo Sequencer. Communication lights blink on the SSC every time i send a command.

What is not happening is driving the servos on any channel on either side of the board. I even moved the power from VS1 to VS2 and tried channels. 16-31. No response from Servo. Servo was tested using a servo tester, so I know the servo is good. Just to be complete, I took out a different servo and got the same non result.

Please send a few clear photos of the board and setup so we can take a look at all connections (and indicate which power supply you’re using). The more information you can provide the better.



Uploading: IMG_3317.mov…

One last short video using the sequencer to position the servo from 1500 up to 1700, down to 1300, and back to center. Serví did not budge or even make a sound.

So I put it down to work on my real job and I hear the servo moving. I took this video and edited it to shorten it. Note that the position on ServonSequencer was set at 1500 this entire time. Also note that the servo was hitting its limits. I set limits on ServoSequencer shown in image 2.

  1. Can you confirm the software connected to the SSC-32U board? “FOUND” turns green.
  2. Triple check that you’ve selected the right COM port selected? If you have a list of available COM ports, then disconnect the USB and see which COM disappears.
  3. Can you ensure you have the correct FTDI VCP drivers?
  4. Can you ensure you have the appropriate baud rate on the board (and reset after the change) by confirming the LED pattern based on the guide, which matches the selection in the software?
  5. Do you have any other RC servo motors you can connect to the board to test?

It is incredibly rare that these boards have issues, so we just need to be certain. Rest assured (assuming you’re within warranty) that we will replace the board if nothing here works.


One green light means 9600, correct?

Adding the FTDI driver was the first step in my troubleshooting a coupe of days ago.


Different Servo on ch1. Same results. Both servos have been tested on servo tester. Bother servos work. Anything else I should try?

Two last (weird) things to try:

  1. Remove the LVS = VS2 jumpers.
  2. Double check the wires are correctly within the VS1 screw terminals

You seem to have done everything correctly.

If that doesn’t do anything, please write to [email protected] with your order or invoice number and a link to think thread indicating “SSC-32 approved for exchange by CBenson”.


No luck. I ordered and paid for a replacement and paid for 1 day shipping last night. I spent most of Sunday and yesterday troubleshooting and concluded myself that the board was not functioning properly. I have a party this Saturday that I needed to be ready for, and I knew this process would take at least a day. I’ll explain all that in the email.

Our apologies - these boards have been incredibly reliable and have not changed.

To confirm, the VL = VS jumper is not in place when you’re using the USB, correct?

Did you write to support? If not, we can transfer this to internal support since it seems like an RMA situation.

1 Like

Yes, I wrote to support. The board I had overnighted came in this afternoon and works perfectly. I still haven’t received a response, but I am hoping they will just credit my account for the one that didn’t work. If I had waited until you and I had this conversation I wouldn’t be getting it until at least tomorrow. I got my first scene programmed in VSA, but needs a lot of time tweaking. Thanks