Looking to buy a serial/usb converter due to my com1 port not wanting to communicate and growing tired of it quickly. Anybody had any experience with a BYTECC or KINAMAX converter. I’m looking on NewEgg because I really don’t need to spend $30 on a converter. 
It’s already been proven that many USB<>Serial converters do not deliver when it comes to programming micros. You pretty much get what you pay for. NewEgg is great, but they will not make sure their products are worthy of being used with robotics at any level.
Would you rather buy something less expesive and have to replace it once or twice, or buy something more expensive and probably not worry about it? There can be bad units at all price ranges, but keep in mind that Lynxmotion will not stock something that is probably going to cause a problem for them or you.
That said, it’s not always in the hardware where a problem will occur - sometimes it will be in software drivers that don’t allow for needed options for applications such as we need for robotics programming and related usage. If you can, check out the drivers before you buy the hardware.
I am in no way associated with Lynxmotion, except has a very HAPPY customer. 
8-Dale
I’ve got some cheap usb/serial adapters that work with the ssc-32 for general I/O work. If you are planning to do program chips using the adapter, then it might save time and money in the long run to get an adapter that is known to work for programming.
Here’s the bottom line on USB to serial…
FTDI has proven technology for fast comms. The bandwidth is fast, yes, but also the latency is a driver property that can be minimized. FTDI cables work. The vast majority of the cheap USB to serial cables are just not going to do what you want. Buy FTDI, from me or some one else. But don’t waste your money on ebay specials. It’s money down the drain.
wow 
quick replies. I guess I’ll just try and fix whatever problem I’m having with my COM1 port or maybe just buy a PCI I/O card.
Since the replies are so quick and plentiful, thank you very much btw, do most prefer the usb converter or using the db9 I/o port? I just got the controller last week but I have a little bit of experience with computers.
Right now I just have it hooked straight up to the I/O port on the motherboard because I can’t find my db9 cable. I’ve read that even though baud rates are incorrect, the ver command should shut off the LED. All the drivers are updated for the port and device manager says it is operating properly. I/O jumpers are in place on the SSC32, but nothing wants to connect. I’m assuming something is wrong with the port on the motherboard. Next step will be to buy an I/O card I guess.
Okay, I borrowed a Belkin f5u409 today and got all the drivers set up(I saw that was one of the recommended ones so I got it). Now on the adapter I get the Transmit(tx) light to blink upon sending a command, but the recieve(rx) light will not blink on the adapter. Baud rates are all correct, Tx/Rx jumpers are in place, I set the transmit and recieve buffer both to 14, drivers are installed correctly, it has sufficient vL power, device manager sees the adapter as com4. Still can’t get it to communicate. Any suggestions 
I’m editing th original post here to reflect this point…
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.
FYI - I am still using the BAFO adapter which was earlier recommended by Nathan (Acidtech). I use it through a powered USB hub (Not sure if the hub is needed on this computer, but if it ain’t broke…). It is based on the Prolific chip set. I have now used on it XP, Vista and Windows7. I keep using it as it appears to do downloads a lot faster than any other cables I have tried. Keep meaning to order one of your newer FTDI cables
Kurt
To be sure I am understanding… The adapter has two LED’s one for TX and one for RX. The TX is blinking but the RX is not… For normal servo control the SSC-32 is a listen only device. It will not send anything back to the PC unless asked to. The more useful information would be is the SSC-32’s LED blinking?
Try this… Make sure the two serial port enable jumpers are installed (by the DB9) and they are oriented vertically (when you can read SSC-32) Also you can open a terminal program. Short out pins 2 and 3 on the DB9 end of the cable ans see it the typed characters appear on the screen.
Right the two LEDs are on the adapter. So now I know that it’s at least sending a signal to the port. And about the serial enable jumpers, when you say they should be vertically oriented, you mean they should be vertically oriented in reference to the Tx and Rx printed on the board (as in the picture that’s on lynxmotions website). If so, I have that right. But no the LED will not go out on the SSC-32. I have been trying this using LynxTerm. I will definately try the pin short trick when I get off of work tonight. Just to keep from extending the page from posts, if I don’t see the letters after I short the pins out, what’s my next step? Thanks a lot for your help. I’m glad I picked Lynxmotion.
We moved this out of the sticky thread…
You have sneaked in here getting help without providing much information.
Please take a few minutes to tell us more about your system, PC, project, components, goals, etc.
I mentioned you should be able to read the words SSC-32, but TX and RX is fine too. 
You need to get the LED on the SSC-32 to go out.
Remove all servos, power the board with a 9vdc battery only… no servos!
Observe the green LED on. Using LynxTerm set it up for 115.2kbaud and type VER then enter. Look to see the green LED go out then blink when each character is typed. If this doesn’t work, (the green LED is still on) then check in the control panel for the com port that was assigned to the USB cable. Make sure LynxTerm is set to the same port. Make sure all other applications that might use the serial port are closed before opening Lynxterm. Your turn…
I’m running windows XP and am trying to communicate through com4 with a Belkin usb to db9 adapter. I’m just wanting to do a simple talking skull project. I have 3 Hitec 422 servos and all I want to do, to start with, is just a head rotate, nod, and jaw movement using something like the VSA software. I misunderstood you at first when you said “I should be able to read SSC-32”, sorry. That aside, I have the serial port jumpers installed correctly. And yes, I know the objective is to turn off the LED on the board and have it blink upon communication. I am currently running vL on the board with a 9v battery, no servo power or servos hooked in and the Logic and servo power jumper is disconnected. I have set the board, the com port in device manager, and the port in lynxterm all to run off of 115.2k baud. I tried the shorting out pin 2 and 3 and it communicated back to lynxterm when I hit “all=1500”, so I know it wants to communicate.
I believe my problem is lying deeper than simply communication now. When the board isn’t hooked up to the computer(through the usb/db9 adapter), the LED stays lit and the voltage regulator on the board stays fairly cool. However, when I hook it up to the usb/db9 adapter, the LED goes out, comes back on dimly, then goes out for good, and my voltage regulator gets VERY HOT. Just using a standard 9v battery. Is my adapter trying to push power somewhere through the board?
Sounds like when you connect your adapter to the ssc-32, something is shorting the ssc-32. Try plugging in your adapter to the ssc-32 without the adapter being connected to the computer to see if the same thing happens. Check the ssc-32 connector and the USB adapter closely for small metal pieces or solder that could be causing a short.
YESSS!! Got it! I was using a Null modem gender bender between the usb adapter and the card as an extension and I took it out. I even pinned out the gender bender and all the pins were straight through?..Oh well, it works. Thanks a load everybody. I feel like a real douchebag now. sorry for the trouble.h