If you are experiencing trouble communicating using the serial port or a usb to serial cable these are almost always issues with the PC. Here is a list of some of the most common problems. These suggestions pertain to the SSC-32 communications AND the Bot Board II programming. If anyone thinks I left something out please feel free to post here. I can't connect to the SSC-32 with any of its PC applications, LynxTerm, RIOS, SEQ, or PowerPod.

Windows standard driver will be loaded if you inserted the USB device in the USB port of the PC with Windows® 10 which does not install Active USB-COM Port Driver. Должностная Инструкция Повара 2 Разряда there. The USB device does not support the operation with the Windows standard driver. Please use it after installing Active USB-COM Port Driver by all means. I have an Arduino Duemilanove with an Atmega 328. I am working on Ubuntu 12.04, and the Arduino IDE's version is 1.0. Recently, I tried to upload a few of the sample.

The green LED on the SSC-32 is a status indicator, not a power light. If this LED does not illuminate then you have a power problem. When power is first applied the LED will light up steady telling you it's 99% functional. The LED will go out after it has received its first byte of data, and then blink after that when it's receiving data. This will happen even if the baud rate is wrong.

It's a useful tool for troubleshooting the communication system. Note: LynxTerm, RIOS, SEQ and PowerPod all send commands to the serial port continuously when first opened. It's possible that the LED is on for such a short time it appears to never go on.

Remove the serial connector and try again. If the green LED never lights up. Make sure your VL terminal has from 6vdc to 9vdc connected to it. Red is positive and black is ground. For now remove the VS1 = VL jumper to isolate the servo power from the logic power.

If possible check it with a VOM meter. Note: LynxTerm, RIOS, SEQ and PowerPod all send commands to the serial port continuously when first opened. It's possible that the LED is on for such a short time it appears to never go on.

Remove the serial connector and try again. If the green LED never goes out. 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. Normal DB9 serial ports, indicated by the 9 pins sticking out of the D shaped metal part are normally numbered as com1 or com2. Try changing the com port to a different number. If you don't have a serial port it's easy to add one.

We will discuss USB to serial cables separately. What USB to serial cable should I use? Consider An Spherical Cow Pdf Converter.

We recommend only high quality name brand adapters. With these devices you literally get what you pay for, so don't skimp. Look for cables that use the FTDI driver chip if possible. We highly recommend the.

Others have reported good results with the following cables. Belkin F5U409, BAFO BF-810, I/O Gear GUC-232A, Keyspan USA-19HS, Dynex DX-UBDB9, etc. Although these adapters have worked in the past, with manufacturer changes, and new operating systems emerging, there is no guarantee they will continue to do so. The only USB to serial adapter we know will work for sure the the FTDI. When using the FTDI cable we recommend the following changes within the driver settings.

With the USB to serial cable plugged in and recognized by Windows go into: control panel system hardware device manager Ports (COM & LPT) USB Serial Port (COM?) Port Settings Advanced Make sure the receive and transmit transfer sizes are 4096, and change the latency to 1. Click ok then ok. Then close the rest. The latency is the delay before sending data. If it's too long problems arise. If you plan to do a lot with this hobby and want a trouble free interface then install a real serial port as illustrated here.