Hello all,
This is my first post and since it has been a long time that I have been in robotics this might be a stupid question. So I have just started one of my new robots and i am using some old parts from my old rover and one of those parts was the SSC-32. I have the robot for the most part working but i have hit a major snag. When i go into the PC that is on the robot and I go into the Lynx-Rover controller software the controller wont be detected, granted that it has been nearly a year and half since i had the controller started up and ALOT of things have changed. For those wondering why I need to use the Lynx-Rover controller I control the robot through a remote desktop session and this was the only software that i could find that was capable of doing key inputs. For the configuration of the system on the robot it is a dual core Pentium running windows XP with a built in com port on the motherboard. An advice on what I should do would be greatly appreciated. 
Welcome to the Lynxmotion forums!
There are two main things to check: 1) power, 2) serial connection.
For the power, can you tell us what you are using (battery type, voltage) to power the board? Are you using one source for both VL and VS, or two sources: one for each? Does the D1 LED on the SSC-32 turn on when you power up the robot?
As for the serial, do you have the RX and TX jumpers installed? They’re identified as item 14 in the image of the SSC-32 manual (below). What baud rate are you using? The baud rate is configured with the jumpers that are item 9 in the image. Are you able to send the VER command and get the version number as a response?
SSC-32 Manual:
Hi,
The controller is reciving its power from a sabertooth speed controller. When I power it up the green led near the serial port lights up and stays lit when I try to connect to it on lynx-rover controller. The TX and RX jumpers are both in there respective pins, I have the Baud rate set to 115.2k and i can connect to it inside of lynxterm.
How do you have the controller connected? Possibly a driver issue?
It couldn’t possibly be a driver issue because i have the drivers installed it shows up inside of lynx-term and I am able to control the servos connected to the controller I currently have the firmware flashed to SSC32-V2.07Alpha1A-EGP. But I just am unable to get the controller to be seen by lynx rover controller which is very perplexing.
What comm port are you using. Also what baud rate? Several of the flow stone programs were setup to only check for an ssc32 on lower com numbers. Don’t remember how high he checked 16? 32? Also he may only work when baud is 115200.
well good new is that I got the controller to connect to lynx-rover controller bad news is that it is 0.0.6 that was on Friday more bad news is that the controller is unable to be flashed with new firmware nor will lynxterm detect it what so ever and this was on Sunday so is it now a possibility that the serial controller is toast. 
I’m not sure I understood the part about 0.0.6… Version 0.2.2 is still available, however it is no longer supported. I checked the FlowStone code, and the program will only check COM ports 1 through 8, and I verified that the SSC-32 must be set to 115,200 baud for the lynx-rover software to connect.
Also, are you careful to only use one of LynxTerm or lynx-rover at a time? Serial ports can only be opened by one program, so if you are already connected to the SSC-32 with LynxTerm, you will not be able to connect to it with lynx-rover. Maybe this is why you are not able to connect with LynxTerm anymore?
Well after a week of messing around I found the problem. The problem was due to the serial controller on the SSC-32 had eventually died. So i am currently using one of my cannibalized xbee to usb boards to interface with the micro controller on the SSC-32 and it seems pretty stable now and the lynxrover controller software now detects the SSC-32 servo controller. I think i will be keeping the xbee to usb adapter on the ssc-32 because usb is a little more prevalent on most computers. Thanks for your comments and ideas.