Hello,
I am new to the forum. I just purchased and assembled 8 of the SSC-32U kits and was initially able to connect to the servo sequencer utility and flow arm. Now when I or my students try to connect, we are unsuccessful. Here is what is happening. I connected the USB to my computer and installed the drivers successfully. I opened Flow arm, select the bluetooth button, and select auto. The green “Found” LED lights up for about 2 seconds, then goes out. This has been happening on 4 different AL5D robots. Does anyone have a suggestion? I also checked the hardware ID and it matches with what I saw in these forums. When I look at my devices the name of the robot is FT232R USB UART.
I am having the same problem with my ssc-32u board not being able to connect to FlowArm or the sequencer program through the USB port. Using Windows 7 Enterprise, com drivers are installed and I have verified 9600 Baud on the ssc-32u and the com port setting on the PC. I see some LED activity on the board for a few seconds and then a time out message indicating to cycle power on the board. I am using the USB cable provided with the ALD5 kit (checked two cables).
As the sequencer attempts to connect on Auto, the A led blinks green, nothing on the B led, RX1 blinks yellow and nothing on the TX1 led. I have checked this out on two separate ssc-32u boards. No difference.
One other bit of information. When I switch the com to OFF then back to my com port (8) there is rapid flashing of the A (green) and B (red) , and RX LED’s, the Found lights up for a few seconds then it fails to connect.
I have had the exact same sequence with the LEDs. I was able to get one of the boards to sync up but I had to set the sequencer utility to 115200 for my baud rate. I was surprised this worked but all of the other boards would not connect on 9600 or 115200.
A few things may be happening here, so lets check a few possibilities:
When using FlowArm PLTW, please note that by default it attempts to connect at 115200 baud rate while the SSC-32U is set to 9600 baud rate by default. To connect at 9600, simply set the COM port to OFF and activate the Bluetooth icon (it should be blue). Then, set the COM port to a known port or AUTO. It should then connect properly.
If it still does not connect, then the issue may be with the FT232 chip. A possible fix is as follows:
First, disconnect everything from the SSC-32U. Then, open device manager and expand the Ports (LPT & COM) category. Connect the SSC-32U to a USB port and check if the device shows up.At this point, three things can happen:
]It shows up under Ports (LPT & COM) category as a device (such as “USB Serial Port (COM??)” or “2002 Design, Inc. USB Download Interface (COM??)”)/:m] ]It shows up with a yellow triangle as a device with no drivers installed (such as “FT232R USB UART”)/:m] ]It doesn’t show up at all/:m]
If it does not show up, please open a support ticket here. Make sure to add a link to this topic in your message and mention as many details as possible.
If the device does show up under the Ports category or with a yellow triangle icon, please follow the steps in the attached image to obtain the VID (should be 0x0403) & PID (0x6001) of the board.
A possible solution to an SSC-32U that is able to be found but display these symptoms would be to reprogram the interface chip (FT232R). Please find the steps below (see the attached images for details):
