<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to support-requests</title><link href="https://sourceforge.net/p/ftdi-usb-sio/support-requests/" rel="alternate"/><link href="https://sourceforge.net/p/ftdi-usb-sio/support-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/ftdi-usb-sio/support-requests/</id><updated>2005-11-15T01:59:22Z</updated><subtitle>Recent changes to support-requests</subtitle><entry><title>Setting latency time and buffer size</title><link href="https://sourceforge.net/p/ftdi-usb-sio/support-requests/5/" rel="alternate"/><published>2005-11-15T01:59:22Z</published><updated>2005-11-15T01:59:22Z</updated><author><name>zkasa</name><uri>https://sourceforge.net/u/kasaeng/</uri></author><id>https://sourceforge.netaf1a7a187ae6ef6613e7cbe664b0a5ff21579dd2</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;We are testing the USB-COMi USB to serial converter in &lt;br /&gt;
our Linux-based system, using the ttyUSB0 device with &lt;br /&gt;
rlSerial object. The kernel revision is  2.6.11-1.14_FC3.&lt;/p&gt;
&lt;p&gt;The converter is used in a multidrop RS-485 system, at &lt;br /&gt;
4800 Baud speed. &lt;/p&gt;
&lt;p&gt;The communication scheme is one byte out - one byte &lt;br /&gt;
in, dictated by the RS-485 hardware.&lt;/p&gt;
&lt;p&gt;The following test program is used:&lt;/p&gt;
&lt;p&gt;rlSerial ser;&lt;/p&gt;
&lt;p&gt;ser.openDevice("/dev/ttyUSB0",B4800,1,0,8,1);&lt;/p&gt;
&lt;p&gt;for (;;)&lt;br /&gt;
{&lt;br /&gt;
ser.writeChar(0xa0);&lt;br /&gt;
ser.readChar();&lt;br /&gt;
}&lt;/p&gt;
&lt;p&gt;Everything works fine, except that the 16 ms latency &lt;br /&gt;
time after each received byte slows down the system to &lt;br /&gt;
an unusable level.&lt;/p&gt;
&lt;p&gt;Please advise how we can set the latency time to the &lt;br /&gt;
minimum and the buffer size to one byte, either through &lt;br /&gt;
configuration settings, or in the application program.&lt;/p&gt;
&lt;p&gt;Thank you,&lt;br /&gt;
Zoltan Kasa&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>cant use a gammascout with ftdi_sio</title><link href="https://sourceforge.net/p/ftdi-usb-sio/support-requests/4/" rel="alternate"/><published>2005-08-04T07:28:49Z</published><updated>2005-08-04T07:28:49Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net370697483e7eb8d31177e427d389e3000d4902ef</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I hope you can help me with my problems.&lt;/p&gt;
&lt;p&gt;I try to work with a GAMMA-SCOUT device with usb on&lt;br /&gt;
linux. The GAMMA-SCOUT&lt;br /&gt;
has a fdti chip.&lt;/p&gt;
&lt;p&gt;First i tested the device on windows. I used a windows&lt;br /&gt;
driver from the&lt;br /&gt;
ftdichip site (www.ftdichip.com). The usb device was&lt;br /&gt;
mapped to a com port&lt;br /&gt;
(com3) and with&lt;br /&gt;
HyperTerminal i can read the data from my device. The&lt;br /&gt;
output starts by&lt;br /&gt;
typing a letter.&lt;/p&gt;
&lt;p&gt;port settings:&lt;/p&gt;
&lt;p&gt;2400baud, 7data bits, 1stop bit, even parity, no protocol&lt;/p&gt;
&lt;p&gt;output:&lt;/p&gt;
&lt;p&gt;GAMMA-SCOUT Protokoll&lt;/p&gt;
&lt;p&gt;0000 34 44 01 ff ff ff ff ff ff ff ff ff ff ff ff ff&lt;br /&gt;
0010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff&lt;br /&gt;
0020 13 01 ff ff ff ff 5a a5 ff ff ff ff ff ff ff ff&lt;br /&gt;
...&lt;/p&gt;
&lt;p&gt;On Linux i tried Fedora Core 1 with kernel 2.4.27 and&lt;br /&gt;
then Fedora Core 3&lt;br /&gt;
with kernel 2.6.12.3. To get the data from the device,&lt;br /&gt;
i started minicom on&lt;br /&gt;
/dev/ttyUSB0. But if i start minicom with the needed&lt;br /&gt;
settings, i can't type&lt;br /&gt;
a letter because following characters running over the&lt;br /&gt;
screen:&lt;/p&gt;
&lt;p&gt;output:&lt;/p&gt;
&lt;p&gt;.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p&lt;br /&gt;
...&lt;/p&gt;
&lt;p&gt;or:&lt;/p&gt;
&lt;p&gt;.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.&lt;br /&gt;
...&lt;/p&gt;
&lt;p&gt;I don't know, where the problem is.&lt;br /&gt;
Perhaps the driver didn't recognize the usb device and&lt;br /&gt;
there is no&lt;br /&gt;
conversion to a normal com port?&lt;br /&gt;
Do you have any ideas?&lt;/p&gt;
&lt;p&gt;Here some further outputs:&lt;/p&gt;
&lt;p&gt;If i plug in the device, i can see it in&lt;br /&gt;
/proc/bus/usb/devices:&lt;/p&gt;
&lt;p&gt;#more /proc/bus/usb/devices&lt;/p&gt;
&lt;p&gt;T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1&lt;br /&gt;
Spd=12  MxCh= 2&lt;br /&gt;
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0&lt;br /&gt;
D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8&lt;br /&gt;
#Cfgs=  1&lt;br /&gt;
P:  Vendor=0000 ProdID=0000 Rev= 2.06&lt;br /&gt;
S:  Manufacturer=Linux 2.6.12.3 uhci_hcd&lt;br /&gt;
S:  Product=Intel Corporation 82440MX USB Universal&lt;br /&gt;
Host Controller&lt;br /&gt;
S:  SerialNumber=0000:00:07.2&lt;br /&gt;
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA&lt;br /&gt;
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00&lt;br /&gt;
Driver=hub&lt;br /&gt;
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms&lt;/p&gt;
&lt;p&gt;T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3&lt;br /&gt;
Spd=12  MxCh= 0&lt;br /&gt;
D:  Ver= 2.00 Cls=00(&amp;gt;ifc ) Sub=00 Prot=00 MxPS= 8&lt;br /&gt;
#Cfgs=  1&lt;br /&gt;
P:  Vendor=0403 ProdID=d678 Rev= 4.00&lt;br /&gt;
S:  Manufacturer=Dr Mirow&lt;br /&gt;
S:  Product=GammaScout USB&lt;br /&gt;
S:  SerialNumber=GSNJR21O&lt;br /&gt;
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 50mA&lt;br /&gt;
I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff&lt;br /&gt;
Driver=(none)&lt;br /&gt;
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms&lt;br /&gt;
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms&lt;/p&gt;
&lt;p&gt;If i add no options to usbserial and i load the&lt;br /&gt;
ftdi_sio module, then i have&lt;br /&gt;
the following output in /var/log/messages and no device:&lt;/p&gt;
&lt;p&gt;#modprobe ftdi_sio&lt;br /&gt;
#tail /var/log/messages&lt;/p&gt;
&lt;p&gt;usbcore: registered new driver usbserial&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for Generic&lt;br /&gt;
usbcore: registered new driver usbserial_generic&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial Driver core&lt;br /&gt;
v2.0&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI SIO&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI&lt;br /&gt;
8U232AM Compatible&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI&lt;br /&gt;
FT232BM Compatible&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI&lt;br /&gt;
FT2232C Compatible&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for USB-UIRT&lt;br /&gt;
Infrared Tranceiver&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for&lt;br /&gt;
Home-Electronics TIRA-1 IR Transceiver&lt;br /&gt;
usbcore: registered new driver ftdi_sio&lt;br /&gt;
drivers/usb/serial/ftdi_sio.c: v1.4.2:USB FTDI Serial&lt;br /&gt;
Converters Driver&lt;/p&gt;
&lt;p&gt;If i add vendor and product options to&lt;br /&gt;
usbserial(vendor=0x403&lt;br /&gt;
product=0xd678) and i load the ftdi_sio module, then i&lt;br /&gt;
have the following&lt;br /&gt;
output in /var/log/messages and the device /dev/ttyUSB0:&lt;/p&gt;
&lt;p&gt;#modprobe ftdi_sio&lt;br /&gt;
#tail /var/log/messages&lt;/p&gt;
&lt;p&gt;usbcore: registered new driver usbserial&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for Generic&lt;br /&gt;
usbserial_generic 1-1:1.0: Generic converter detected&lt;br /&gt;
usb 1-1: Generic converter now attached to ttyUSB0&lt;br /&gt;
usbcore: registered new driver usbserial_generic&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial Driver core&lt;br /&gt;
v2.0&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI SIO&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI&lt;br /&gt;
8U232AM Compatible&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI&lt;br /&gt;
FT232BM Compatible&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI&lt;br /&gt;
FT2232C Compatible&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for USB-UIRT&lt;br /&gt;
Infrared Tranceiver&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for&lt;br /&gt;
Home-Electronics TIRA-1 IR Transceiver&lt;br /&gt;
usbcore: registered new driver ftdi_sio&lt;br /&gt;
drivers/usb/serial/ftdi_sio.c: v1.4.2:USB FTDI Serial&lt;br /&gt;
Converters Driver&lt;/p&gt;
&lt;p&gt;thanks,&lt;/p&gt;
&lt;p&gt;Gerrit Lehmann&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>cant use a gammascout with ftdi_sio</title><link href="https://sourceforge.net/p/ftdi-usb-sio/support-requests/3/" rel="alternate"/><published>2005-08-03T16:44:26Z</published><updated>2005-08-03T16:44:26Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netac096dacf0ce9a498ffbe3d94a9397244b803470</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I hope you can help me with my problems.&lt;/p&gt;
&lt;p&gt;I try to work with a GAMMA-SCOUT device with usb on&lt;br /&gt;
linux. The GAMMA-SCOUT&lt;br /&gt;
has a fdti chip.&lt;/p&gt;
&lt;p&gt;First i tested the device on windows. I used a windows&lt;br /&gt;
driver from the&lt;br /&gt;
ftdichip site (www.ftdichip.com). The usb device was&lt;br /&gt;
mapped to a com port&lt;br /&gt;
(com3) and with&lt;br /&gt;
HyperTerminal i can read the data from my device. The&lt;br /&gt;
output starts by&lt;br /&gt;
typing a letter.&lt;/p&gt;
&lt;p&gt;port settings:&lt;/p&gt;
&lt;p&gt;2400baud, 7data bits, 1stop bit, even parity, no protocol&lt;/p&gt;
&lt;p&gt;output:&lt;/p&gt;
&lt;p&gt;GAMMA-SCOUT Protokoll&lt;/p&gt;
&lt;p&gt;0000 34 44 01 ff ff ff ff ff ff ff ff ff ff ff ff ff&lt;br /&gt;
0010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff&lt;br /&gt;
0020 13 01 ff ff ff ff 5a a5 ff ff ff ff ff ff ff ff&lt;br /&gt;
...&lt;/p&gt;
&lt;p&gt;On Linux i tried Fedora Core 1 with kernel 2.4.27 and&lt;br /&gt;
then Fedora Core 3&lt;br /&gt;
with kernel 2.6.12.3. To get the data from the device,&lt;br /&gt;
i started minicom on&lt;br /&gt;
/dev/ttyUSB0. But if i start minicom with the needed&lt;br /&gt;
settings, i can't type&lt;br /&gt;
a letter because following characters running over the&lt;br /&gt;
screen:&lt;/p&gt;
&lt;p&gt;output:&lt;/p&gt;
&lt;p&gt;.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p&lt;br /&gt;
...&lt;/p&gt;
&lt;p&gt;or:&lt;/p&gt;
&lt;p&gt;.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.&lt;br /&gt;
...&lt;/p&gt;
&lt;p&gt;I don't know, where the problem is.&lt;br /&gt;
Perhaps the driver didn't recognize the usb device and&lt;br /&gt;
there is no&lt;br /&gt;
conversion to a normal com port?&lt;br /&gt;
Do you have any ideas?&lt;/p&gt;
&lt;p&gt;Here some further outputs:&lt;/p&gt;
&lt;p&gt;If i plug in the device, i can see it in&lt;br /&gt;
/proc/bus/usb/devices:&lt;/p&gt;
&lt;p&gt;#more /proc/bus/usb/devices&lt;/p&gt;
&lt;p&gt;T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1&lt;br /&gt;
Spd=12  MxCh= 2&lt;br /&gt;
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0&lt;br /&gt;
D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8&lt;br /&gt;
#Cfgs=  1&lt;br /&gt;
P:  Vendor=0000 ProdID=0000 Rev= 2.06&lt;br /&gt;
S:  Manufacturer=Linux 2.6.12.3 uhci_hcd&lt;br /&gt;
S:  Product=Intel Corporation 82440MX USB Universal&lt;br /&gt;
Host Controller&lt;br /&gt;
S:  SerialNumber=0000:00:07.2&lt;br /&gt;
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA&lt;br /&gt;
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00&lt;br /&gt;
Driver=hub&lt;br /&gt;
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms&lt;/p&gt;
&lt;p&gt;T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3&lt;br /&gt;
Spd=12  MxCh= 0&lt;br /&gt;
D:  Ver= 2.00 Cls=00(&amp;gt;ifc ) Sub=00 Prot=00 MxPS= 8&lt;br /&gt;
#Cfgs=  1&lt;br /&gt;
P:  Vendor=0403 ProdID=d678 Rev= 4.00&lt;br /&gt;
S:  Manufacturer=Dr Mirow&lt;br /&gt;
S:  Product=GammaScout USB&lt;br /&gt;
S:  SerialNumber=GSNJR21O&lt;br /&gt;
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 50mA&lt;br /&gt;
I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff&lt;br /&gt;
Driver=(none)&lt;br /&gt;
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms&lt;br /&gt;
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms&lt;/p&gt;
&lt;p&gt;If i add no options to usbserial and i load the&lt;br /&gt;
ftdi_sio module, then i have&lt;br /&gt;
the following output in /var/log/messages and no device:&lt;/p&gt;
&lt;p&gt;#modprobe ftdi_sio&lt;br /&gt;
#tail /var/log/messages&lt;/p&gt;
&lt;p&gt;usbcore: registered new driver usbserial&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for Generic&lt;br /&gt;
usbcore: registered new driver usbserial_generic&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial Driver core&lt;br /&gt;
v2.0&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI SIO&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI&lt;br /&gt;
8U232AM Compatible&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI&lt;br /&gt;
FT232BM Compatible&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI&lt;br /&gt;
FT2232C Compatible&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for USB-UIRT&lt;br /&gt;
Infrared Tranceiver&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for&lt;br /&gt;
Home-Electronics TIRA-1 IR Transceiver&lt;br /&gt;
usbcore: registered new driver ftdi_sio&lt;br /&gt;
drivers/usb/serial/ftdi_sio.c: v1.4.2:USB FTDI Serial&lt;br /&gt;
Converters Driver&lt;/p&gt;
&lt;p&gt;If i add vendor and product options to&lt;br /&gt;
usbserial(vendor=0x403&lt;br /&gt;
product=0xd678) and i load the ftdi_sio module, then i&lt;br /&gt;
have the following&lt;br /&gt;
output in /var/log/messages and the device /dev/ttyUSB0:&lt;/p&gt;
&lt;p&gt;#modprobe ftdi_sio&lt;br /&gt;
#tail /var/log/messages&lt;/p&gt;
&lt;p&gt;usbcore: registered new driver usbserial&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for Generic&lt;br /&gt;
usbserial_generic 1-1:1.0: Generic converter detected&lt;br /&gt;
usb 1-1: Generic converter now attached to ttyUSB0&lt;br /&gt;
usbcore: registered new driver usbserial_generic&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial Driver core&lt;br /&gt;
v2.0&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI SIO&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI&lt;br /&gt;
8U232AM Compatible&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI&lt;br /&gt;
FT232BM Compatible&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for FTDI&lt;br /&gt;
FT2232C Compatible&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for USB-UIRT&lt;br /&gt;
Infrared Tranceiver&lt;br /&gt;
drivers/usb/serial/usb-serial.c: USB Serial support&lt;br /&gt;
registered for&lt;br /&gt;
Home-Electronics TIRA-1 IR Transceiver&lt;br /&gt;
usbcore: registered new driver ftdi_sio&lt;br /&gt;
drivers/usb/serial/ftdi_sio.c: v1.4.2:USB FTDI Serial&lt;br /&gt;
Converters Driver&lt;/p&gt;
&lt;p&gt;thanks,&lt;/p&gt;
&lt;p&gt;Gerrit Lehmann&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>How to make RTS signaling throttle data into PC?</title><link href="https://sourceforge.net/p/ftdi-usb-sio/support-requests/2/" rel="alternate"/><published>2005-06-07T17:39:44Z</published><updated>2005-06-07T17:39:44Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netd2688daf0b286fbc8d53eabc243d133eb3de9a1c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I have a data logger logging data via and FPGA that is &lt;br /&gt;
constantly sending data into my PC via an FTDI 232BM &lt;br /&gt;
device.&lt;/p&gt;
&lt;p&gt;I have no problem under windows using the RTS input &lt;br /&gt;
from the FTDI chip to control when my FPGA can send &lt;br /&gt;
data back to the PC.&lt;/p&gt;
&lt;p&gt;In Windows, I have turned &lt;br /&gt;
on "RTS_CONTROL_HANDSHAKE" which lowers the &lt;br /&gt;
RTS pin when I am able to send and raises it when I &lt;br /&gt;
need to pause.&lt;/p&gt;
&lt;p&gt;Under Linux, I have nothing but problems using the 232 &lt;br /&gt;
device.  I use the 245BM without hickup under Linux &lt;br /&gt;
(SUSE 9.3 Pro latest released kernel from SUSE &lt;br /&gt;
update).&lt;/p&gt;
&lt;p&gt;Can someone please help?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>setserial returns &amp;quot;Cannot get serial info: Invalid argu</title><link href="https://sourceforge.net/p/ftdi-usb-sio/support-requests/1/" rel="alternate"/><published>2003-08-11T15:18:23Z</published><updated>2003-08-11T15:18:23Z</updated><author><name>Matthias Oster</name><uri>https://sourceforge.net/u/mao0209/</uri></author><id>https://sourceforge.netcccb155fde52ddeaace526f7c112ac9841d8b743</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When i try to run setserial on a serial port that is&lt;br /&gt;
emulated by the ftdi_sio module, the program outputs:&lt;/p&gt;
&lt;p&gt;Cannot get serial info: Invalid argument&lt;/p&gt;
&lt;p&gt;which (i think) causes other programs to crash, too,&lt;br /&gt;
that probably rely on setserial (Matlab?). &lt;/p&gt;
&lt;p&gt;Do you have any idea where this could come from?&lt;/p&gt;
&lt;p&gt;i'm using:&lt;br /&gt;
- SuSE 8.0 with their 2.4.19-4GB kernel &lt;br /&gt;
- i upgraded the (old) ftdi_sio module using the newest&lt;br /&gt;
from the site and downgrading it by removing the&lt;br /&gt;
'owner' entries.&lt;br /&gt;
- as converter we use either self-assembled systems&lt;br /&gt;
with the FT232BM chip or ones from &lt;a href="http://www.jelu.se." rel="nofollow"&gt;http://www.jelu.se.&lt;/a&gt;&lt;br /&gt;
These systems work under Windows with no problems and&lt;br /&gt;
full configuration options, so i expect the error to be&lt;br /&gt;
on the software side.&lt;/p&gt;
&lt;p&gt;thx!&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>