I have an SSC-32U servo motor controller that works well with the Flowbotics software, except for one part that I cannot make work. There’s a “console” button on the GUI that allows for commands to be sent to any connected servo and one of the examples given is #5P1500S750. This says select #5 servo, center at 1500 uS and use a speed of 750. Nothing happens when I do this. I’ve tried other servos and modified the command.
I was under the impression that my USB connection to the controller was all I needed to run the GUI part AND the console section. Is this right?
I don’t know what else I could be missing.
Thanks
Hi,
Is the software you are using the SSC-32 servo sequencer utility? If so, the commands you specified are properly formatted and should work as expected, provided you have a servo motor connected on port 5 and that your SSC-32U is properly setup (jumpers, baud rate) and powered (VL, VS1 or VS2).
Also please note that if the servo is already at position 1500, nothing will happen. Try also the command #5p500s500 and #5p2500s500.
Could you provide us with one or more pictures of your setup with the SSC-32U and your servo motor? Make sure to clearly display all jumpers, connections to the servo and power sources.
Sincerely,
I’ve attached a screen shot of my Servo sequencer GUI, showing the configuration of 4 servos (they are attached to the model dump trucks). These work fine with the limits that I set in the sequencer, but I can’t get any to move using the commands and the “console” just above the STOP button.
I’ve attached two photos of my setup…a little messy with wires. Power is on the left, USB on the right, 4 servo connections for servos 0-3 are attached. At present some of my servos are not “homed” at 1500 uS, so they should respond to the command that tells them to go to that position. Nothing happens. No feedback, no error, nothing.
So, I’m correct that only the USB connection I have now is okay for comm to the board? I have to ask because I have a couple development boards that use USB for one thing, then serial (9 pin RS232) for another.
The only connection you need to interact with the SSC-32U using your PC is the USB connection (virtual serial port).
We noticed a few issues with your setup of your SSC-32U board. First, lets clear all jumper and wire issues:
-
Just a note, your jumpers for VS1=VS2 are currently set to have VS1 and VS2 user different power sources. If you ever want to power both servo rows with one power connection, simply place the jumpers in the other direction (flip them 90 degrees).
-
You currently have no ground wire ( - ) going into the VS1 screw connector and the VL = VS1 jumper is not in place. If you are using the same power source for both VL and VS1, please place the jumper in. If not, please connect the ground wire into the ( - ) screw terminal that matches the ( + ) for VS1, which seems to be a thin green wire in your picture.
-
Make sure that the signal (usually a yellow wire) is towards the inside of the board and that the ground (usually a black wire) is towards the outside of the board.
With the proper grounds in place, you should have no issue sending various commands to your servo motors if they are properly connected.
Sincerely,
My servos all work with the sliders.
They don’t work with the console commands.
VL=12 volts
VS=5 volts
Both have the same ground so I had only connected the VL- and not the VS-. Besides, it seems more like a software problem, not a power problem. I have 4 servos all with different characteristics running a pattern - all configured using the sliders. I’ll keep trying other things.
Well I feel a little like a dope…
The command I was putting in: 5P1500S750 should have a # at the beginning: #5P1500S750. I thought the “#” was just indicating it was the servo number, that it wasn’t PART of the message. It’s like when someone gives you something to type and it’s in quotes, but you are not supposed to enter the quotation marks.
Thanks.
Bob over and out. I’m on a roll.
We are glad to learn that you’ve resolved the issue.
No worries about the mistake in reading the commands, it happens to all of us at some point… and then again, and again, etc. 
Electronics projects are full of those moments!
Electronics projects are full of those moments!