![]() This is a sure indication that your program is not talking on the right serial, or “com” port, or the com port is defective, or the serial cable or USB to serial cable is defective, or the serial port enable jumpers are not installed on the SSC-32. For now remove the VS1 = VL jumper to isolate the servo power from the logic power. Make sure your VL terminal has from 6vdc to 9vdc connected to it. ![]() Remove the serial connector and try again. It’s possible that the LED is on for such a short time it appears to never go on. Note: LynxTerm, RIOS, SEQ and PowerPod all send commands to the serial port continuously when first opened. It’s a useful tool for troubleshooting the communication system. This will happen even if the baud rate is wrong. The LED will go out after it has received its first byte of data, and then blink after that when it’s receiving data. When power is first applied the LED will light up steady telling you it’s 99% functional. If this LED does not illuminate then you have a power problem. The green LED on the SSC-32 is a status indicator, not a power light. I can’t connect to the SSC-32 with any of its PC applications, LynxTerm, RIOS, SEQ, or PowerPod. ![]() ** if anyone thinks I left something out please feel free to post here.** These suggestions pertain to the SSC-32 communications AND the Bot Board II programming. Here is a list of some of the most common problems. If you are experiencing trouble communicating using the serial port or a usb to serial cable these are almost always issues with the PC. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |