Various Questions (SSC-32 Expandability + Issues...)

Lynxmotion Electronics & Software
1

Hello!
I picked up an SSC-32 and a copy of the sequencer program a few weeks ago from ActiveRobots UK.

But first a few questions before the bad news:…

1.) Can I drive multiple SSC-32 boards? Initially from the sequencer, and from a micro controller at some point in the future?

The plan is to design all the “frames” in the sequencer software (many many to do!) then hopefully I believe it is possible to export those frames and dump into an EEPROM, then source some sort of micro controller to program, and run each frame in sequence or based upon certain conditions?

I’ve got the design down to 32 separate servos; I would REALLY like to use another 16 or more if possible…

So any advice?

2.) What would be the best solution for a micro controller to do the above? I really don’t know the advantages or disadvantages of a BotBoard from a STAMP etc… All I need is something to program to pull certain frames from an EEPROM at certain times. Again, any tips/ideas/guidance?
Preferably quick and easy to use!! I do not need any specialist “robotic features” or anything fancy.

3.) The dreaded USB -> RS232 issues…
At first I thought it was my Prolific chipset causing issue, so I ordered a nice FTDI chipset USB->RS232 converter. (tronisoft.com/2455.php)
However the SSC-32 does EXACTLY the same; correct settings applied, power on, LED does not go out. None of the software (terminal nor sequencer) can talk to it.
I’ve searched for days on this forum, and I have tried almost everything but to no avail… :frowning:
Also note: I am using a MacBook Pro running XP natively through BootCamp.

Today I dusted off an old old Windows computer with an RS232 port! Tried it again, and still the same. I can’t get the light to turn off…

After speaking to ActiveRobots today they offered to test the board out, but it seems ok, in that it a.) powers up and b.) servos whizz a little when power applied
I think it’s a combination of settings + whatnot, but I am a bit worn down with this at present, as I feel I’ve tried everything… :frowning:
At this rate the board will be going back…

Cheers,
Dan

2

Some things to try before you send the board back. Make sure the two serial port enable jumpers are installed vertical (when you can read SSC-32). As you may already know the LED is a status indicator. It will go out when it receives any sort of data at all. Wrong baudrate, sending jibberish, it doesn’t matter. If there is anything going on the LED will go out. Having the servos wiz a little has nothing to do with anything. This only means they reacted to having power applied to them.

There is one other scenario where the LED will not go out. But it’s really that the LED goes out because it received a command to move a servo, but the attempt to move the servo drew too much power from the supply and the SSC-32 resets and it “looks” as if the LED never went out. I’m not suspecting that in this case though.

There is a way to test the USB to serial cable. Connect pins 2 and 3 together, you can use a small screw driver. This will connect Tx and Rx together Use a terminal and type anything. If the loopback is working the typed characters will appear on the screen. You must make sure echo locally is off when doing this test.

We can go into more detail when you have the board working.

Oh, and um welcome! :slight_smile:

3

Thank you!! :smiley:
I feel SUCH an idiot now. :blush:
For some reason the Tx and Rx jumpers were preset horizontally when I took it out the packaging. I assumed this to be correct, and obviously couldn’t get it to work!
Again, thank you! Such a simple thing. :laughing:

I’ve just unpacked the first 8 servos and threw them onto ports 0-7. Fired up the sequencer, dragged a few sliders, and they’re all humming away whizzing back and too now!
Very pleased :smiley:

Now, any ideas about the other q’s?

Cheers,
Dan

P.S. It’s working perfectly on XP virtualised on Parallels Desktop running on a Mac (10.6 Snow Leopard) with an FTDI USB->RS232 converter.