In the LynxTerm, what are the port settings? We have been trying to connect our robotic arm to the computer, and we have finally been able to send data to the robot (the green light flashes when we enter a character), but we haven’t been able to get any information back. We suspect that we may have the incorrect port settings, but we haven’t been able to find the correct settings.
When entering the RIOS program we encounter a message saying it cant find the SSC-32 card.
Since the green light on your board does flash, we think you might have the wrong baud rate: from the Setup window, you need to choose the same rate as the one of your board.
To determine the rate of the board, you can look at the baud jumpers identified by the number 9 on the following page.
For example, if you have both jumpers installed, then your baud rate should be 115,200 kbps.
You might also want to check that the data bits is set to 8, the stop bits is set to 1, the parity is set to none, and the flow control is set to none.
If this doesn’t work, please let us know because you might have another problem.
We have checked all of those settings and everything seems to check out well
Have you done any firmware changes to your SSC-32? When you are connected in LynxTerm, can you see the firmware version when you click on the Firmware button?
Also, how is the SSC-32 connected to your computer? Directly to a COM port, through a USB-to-serial converter, through Bluetooth, or with something else? What baud rate are you using?
We have not done any firmware changes, and will check the version as soon as we get back into the office.
First we used a USB-to-serial converter, which is when we could send data to the robot but not receive anything back through LynxTerm. The LynxMotion software could not detect the SSC-32.
We then switched to a computer with a direct COM port, and the LynxMotion software recognized the robot and was able to make it move. However the LynxTerm no longer seems to see the SSC-32 and we cannot send data through LynxTerm.
The baud rate is 115200.
Thank you for all your help.
Sounds to me like your USB to serial converter may be the issue. Which one is it? How is it connected up to the SSC-32? In cases like this sometimes a picture can be a real help.
Things I would check include, if your converter is one where you are connecting directly up to the TTL level inputs of the SSC-32 (#14 in the diagram lynxmotion.com/images/html/b … m#ssc32lay ), then make sure the correct wires are connected up. Sounds like the one going out to the SSC-32 is correct, but the one coming back is not.
If your USB to serial converter is the type that has a standard looking 9 pin connector that is plugged into the normal connector #12, make sure both jumpers of #14 are correctly in place.
Hope that helps.
Kurt
Is your USB to serial adapter recognized as a comport? If it is, check the comport number assigned to the adapter in the comport advanced settings. In the lynxterm dropdown, make sure lynxterm is using the comport assigned to the USB adapter. If the comport number is 10 or grater, reassign it to a lower non used comport number.
Thank you guys for your advise on our project and sorry for the month delay as we were getting back into the school life. We finally got our program to work because we realized both programs can’t be open at the same time. We were able to successfully connect to the robot with our USB-Serial Port adapter, but our base servo was twitching out of control without the green light on the SSC-32 blinking. We are guessing we have a bad servo because all of the rest of the servos worked when we tested them. Do you have any suggestions on what we can do to get the base servo to work properly, or should we get a new servo? If we should get a new servo, where can we get one and is it possible to upgrade it to a more powerful/more durable servo?
Have you tried plugging the base servo into another servo pin besides pin 0? If it still twitches, then the servo is in fact defective. If not, the SSC-32 controller might have an issue…
Here’s a replacement servo of the same model:
And here’s a stronger version if you wish:
We hope this helps,
