I bought a SSC-32U from Robot Shop to replace the RS232 version I had in my
Lynxmotion CH3-R Hexapod.
Before installing the board in the Hexapod I connected via the USB to my Windows
7 PC, plus a 9v battery to VL to check that all worked OK. The FTDI device driver
downloaded and installed OK. There were no servos connected.
I then tried to talk to the processor on the SSC-32U with LynxTerm (V1.11
Freeware Version) having set the term to 9600 Baud because the manual said that
was the default for the processor.
I was expecting to at least be able to issue a VER command! I also noticed that
as soon as I connected the 9v battery the PWR LED lit, but also the A/B LEDs were
flashing red/green, quite fast.
I issued the VER command and got nothing back! I am right that it should respond
to VER?
Further reading of the manual said I could change the Baud Rate by following a
procedure involving the push button and LEDs. The only indication of flashing
LEDs was during the procedure, but not initially on power up!
Any thoughts on what else I can try before I declare it dead and send it back
under warranty?
I observed all the static precautions (wrist strap and anti-static mat) and
defiantly connected the 9v with correct polarity (red to + and black to -).
Hi,
First thing to do is verify the jumpers on the SSC-32U, can you take a good top picture ?
The SSC-32U will not be able to talk without proper VL power and jumper set.
Thanks for reply. I took photo as requested - sorry didn’t come out too well so
not attached (not that I could work out how to attach!), but jumpers are still in
place for VS1 = VS2 and VS to VL jumper is not connected.
Tried it this morning and lots of flashing LEDs did it again when had camera and
only the PWR blue LED was lit! Sounds more promising. No idea for the change.
I don’t know why I thought VER was a valid command to send with LynxTerm,
after looking in manual I couldn’t find it.
Tried #1P1500 and RX LED flashed for each character received, but since no
servo present no response expected.
I tried sending Q expecting + or . but nothing, but again 'cos no servo
present maybe shouldn’t expect a response!
Now to try with a spare servo.
Please, attach some pictures as this help us a lot in troubleshooting. (see picture for attachment procedure)
The “VER” command should return the board version, you where right. Make sure you selected the right serial settings.
Thanks for reply. I’ve added images/photo. Let’s hope they help, I can always add more. As you can see COM10 was assigned. I tried VER again, could someone point me at what page in the manual this is described please.
Looking at your pictures, almost everything seems fine.
You should get a blink LED on the SSC-32U each time you type something in LynxTerm which confirm the USB drivers.
Please power your SSC-32U through the VS1 (5-6VDC) and you should get it working.
The “VER” command is not explained in the new SSC-32U manual but is in the old SSC-32 (not usb) version HERE.
Thanks for that. Clarification sought - why should applying VS make it all work? Or should I connect a servo as well? I was expecting VER to get a reply even without VS/servos. I mean VER is only talking to SSC-32u processor, isn’t it? The processor is powered by the VL isn’t it? I looked in the old SSC-32 RS232 manual and it does have VER defined as you said - any thing else that didn’t make it to the SSC-32u manual? I will try the VS and then connect a servo as well, but since I’m disabled and depend on a helper for fiddly stuff and he is away at moment it will be some time till this happens. Will get back with hopefully a success.
Connecting VL only is not suggested and not useful for the new SSC-32U.
The old version had issues with low voltage dropout which need an external source otherwise the system had brown-out issues.
The VER query will work as long as you have the logic of the board powered and a properly setup serial connection.
You only need to power the board out of the VS1 with the required 6V for standard servos.
Best regards,
Just to close this thread down. I have now connected a 6v VS and a servo to
channel 0. It worked perfectly The blue PWR LED lights up brighter and the
servo moves to where instructed. VER now sends a reasonable version reply. I used
my XP PC 'cos it was nearer the power supply having downloaded an XP device
driver from the FTDI site. The Rx LED flashes each char received. Thanks for all
your help.
Good News…!!