SSC32 + USB to RS-232 + MatLab strange problems

Hi all,

I’m trying to drive SSC-32 via MatLab.
3 Days ago I tried using a friend’s USBtoSerial interface, and it worked. I read the topic about the controller and matlab in this forum, I changed the “Terminator” and BaudRate, and it worked succesfully.

But I had to give back the interface to my friend, so I bought a new one.
And it doesn’t work :frowning:
It works properly with the lynx terminal, using COM8 port, but when I send the string via MatLab:

fprintf(serial8, ‘#0P1500’)

I get this error message: “An error occurred during writing”.

I can’t explain why ONLY the previous adapter worked properly. And in the Lynx Terminal all is OK…

Thank you, Michele

What’s the brand of the one that worked and the one that is not working? Are you absolutely sure nothing else changed? BTW USB to serial cables are not created equal. I know the IO Gear GUC232A works well, and Nathan from Basic Micro swears by the BAFO BF-810.

The working one is from HP, the other one is from hamlet.

The Instance ID shown in properties is: (Hamlet)
USB\VID_067B&PID_2303\6&1C5E72C7&0&1

The Instance ID shown in properties is: (HP - working)
FTDIBUS\VID_0403+PID_6001+12345678A\0000

I’m afraid that the cause of the malfunctioning is that the two peripherals work slightly differently in the emulation of the COM port…

Ok, I solved the problem by updating MatLab version from 6.5 to 7.1.
I don’t know why, but now it’s working properly. Maybe it could be useful reunite all info about matlab and ssc32 in a single 3D, I found very useful the previous one (about the Terminator character, ‘CR’).

Thank you for attention,
Michele

Just FYI, this chipset is from future technology devices, ftdichip.com and most of their USB-to-whatever chips have small eval boards made by DLP Design and available through Mouser. These are really hardy chips to work with so far, they do a nice job with their drivers, and don’t seem especially demanding in their pcb layout requirements. If you get to a point where you want to eliminate the RS-232 buffers (just making a TTL connection) and embed the USB directly to a project the DLP modules really work well for prototypes and hobby projects. :slight_smile:

Oh! I couldn’t deeply understand your reply, but it seems cool :slight_smile:
But that connector isn’t mine :frowning:
I will return it today, I’ll come back to Present Technology Device :stuck_out_tongue:

a small module like this
ftdichip.com/Documents/DataS … R_v091.pdf
found here (for example)
mouser.com/search/ProductDet … x?R=MM232R
or here
it.farnell.com/jsp/endecaSearch/ … KU=1146037
can be soldered to a microcontroller evaluation board to allow direct USB cable connection to the PC.
The module connects to the microcontroller using TTL level signals, rather than RS-232 level signals such as would be in a stand alone USB-to-RS232 adapter cable. Sometimes this can save on parts, space, and power consumption.
Often the USB cable is more thin and flexible than RS232 cable which has big connectors and many more connections internally.
:slight_smile: