OS/2, eCS & ArcaOS - Technical > Hardware

USBCOM big problem

<< < (2/4) > >>

Igor:

--- Quote from: Lars on January 10, 2025, 11:03:29 am ---For the "Future Technology" device you should try USBSER.SYS instead of USBCOM.SYS.

--- End quote ---

I checked this configuration. Unfortunately, this does not work.

--- Code: ---DEVICE=C:\OS2\BOOT\USBSER.SYS /V /Z /N:COM5
--- End code ---

The system say:
SYS1620: The COM port specified is not installed.

lsusb:
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC

Doug Clark:
Igor,

I am using an USB-RS232 adapter that uses the PL2303 chip with the AOS  USBCOM.SYS driver.  You can find the adapter on Amazon by searching for
   BENFEI USB to Serial Adapter, USB to RS-232 Male (9-pin) DB9 Serial Cable
It costs about $10

That adapter works fine with my own, very simple, program that talks to a IBM 6094-20 lighted keyboard.  The program sends and receives data through the COM port, however the device does not use the RS232 control signals DTR, DSR, CTS, RTS

That same adapter does not work when trying to connect the DOS program LapLink through a COM port assigned to the adapter to another computer.  LapLink reports that the COM port does not exist, while the OS/2 MODE command says that it does.  However LapLink also refuses to recognize any COM port on my Quatech 8 port serial card - I suspect that problem is related to the interrupts LapLink expects to be with a specific COM port and the fact that the 8 port serial card is a PCI card and the interrupts that are assigned at boot up do not match the standard COM1-COM4 interrupts.

I also have a graphics tablet (ACECAD) which will not work when connected to the USB-RS232 adapter, or when it is connected to a port on the QuaTech 8 port serial card - but will work when connected to a serial port on the motherboard.  I am guessing it is the same interrupt issue.

So if you are getting an error message from OS/2 when you issue a MODE command in a Command Prompt window on a COM port provided by the USB-RS232 adapter, then I am guessing you have an issue between the adapter and the driver.  It looks like you are using COM5 for your USB-RS232 adapter, so the command would be MODE COM5.  If the MODE command returns OK but your application says the COM port does not exist then you have a different issue.   I tried various combinations of switches/parameters with USBCOM.SYS and no combination would make LapLink work with the USB-RS232 adapter.  (I tried LapLink simply because I know it does all sorts of interesting things with a COM port and it was handy.)

If this is possible for you, have you thought about trying to connect to a COM port on your motherboard - assuming you are using a desktop computer and the motherboard has a COM port header?

Igor:
Thank you for the comment. I also managed to configure PL2303, but only with the driver Lars Erdmann 10.250.
This is enough for me. But I am ready to check the performance of other drivers and chips.
Unfortunately, I never achieved the stable operation of Pscom.sys drivers in my configuration.
While the PL2303 decision suits me.

Dan Eicher:
Perfect thread for me to tag on to.

I have a gearmo FTDI FT232R - amazon usb rs232 with lights.

I followed the docs:
   /sys/doc/usb/usbcom.txt - which then points to
     /sys/doc/usb/usbser.txt - for type FT232R.
        the docs specifically call out that the FT232R has not been tested.
 
I built up the correct DEVICE line in config.sys, and placed it at the bottom of the file.

Questions for you all.
   Should the usb rs232 be plugged in when you boot, or can you plug it in after you boot, or does that matter?

I installed ZOC and hooked up a loopback plug.

TX/RX do not seem to change state, but I see other lights, installing ZOC and setting to the correct com port Zoc thinks it's sending and receiving and I see stuff on screen.
Next test is to hook it to another computer with an RS232.

Last question, where can I find lsusb?
  I queried the ANPM and it said NADA.

Thanks,
Dan

Dave Yeo:
It shouldn't matter whether it is plugged in when you boot but your mileage may vary.
Hobbesarchive is the go to when looking for stuff, after ANPM, it's search is fairly good. http://hobbesarchive.com/?submit=Search&search=lsusb&stype=any&sort=type_name&dir=%2F

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version