OS2 World Community Forum
OS/2, eCS & ArcaOS - Technical => Hardware => Topic started by: Igor on January 06, 2025, 12:17:51 am
-
I spent some money (thanks to the Chinese industry) and a lot of time.
It turned out that the work of USBCOM is seriously broken.
Of the three different devices that I checked, only PL2303 is recognized and only on USB16 drivers.
But he does not work either.
PL2303 in USB32 is not identified by the system. Checked with USBCOM and USBSER drivers.
If you put the driver from USB16, then you can configure the port.
However, the device only works on receiving information.
Sending does not work.
If someone works for someone, please indicate which version of the drivers this can be launched.
-
There seems to be different PL2303 chips. I had a USB/Serial Modem that was actually a Serial modem with a PL2303 chip. At first it didn't work with any of the drivers that were available, then David A. updated his drivers (this was before AracaOS) and it worked. I worked with Lars trying to get his driver package to work and never did succeed.
Whether it would work with the latest from ArcaOS, I have no idea as I no longer have a phone line.
-
12.14 driver packages fixed PL2303 devices for me. From the ticket -
> /Z is normally needed if you don't have RTS/CTS wired.
So I misunderstood the usbcom.txt - '/Z Forces CTS handshaking and forces DSR and CTS on.'. 'Forces handshaking' sounds to me like I need CTS active driven from the link partner. I would call left unconnected CTS/RTS/DSR/DTR as 'no hardware handshake' or 'ignoring hardware handshake lines'.
And since then my config.sys look this for up to four devices. Mind before I needed 4 lines which are remed out here. Now only one USBCOM.SYS handles all up to four devices. HTH
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM5 /Z
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM6 /Z
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM7 /Z
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM8 /Z
REM ! DEVICE=M:\OS2\BOOT\USBCOM.SYS
DEVICE=M:\OS2\BOOT\USBCOM.SYS /M:4 /N:COM6 /Z
In another ticket I found someone needed /DCD parameter to get a device to work. The documentation for this was (is) misleading (wrong) on this too. (ticket 3485 for those with access)
-
Thank you very much, ALL!
I installed USBCOM from the USB 10.250 package from Lars Erdmann with /Z key
It worked.
The USBCOM 12.16 driver from Arca Noae does not see my device:
Bus 001 Device 004: ID 067b: 2303 Prolific Technology, Inc. PL2303 Serial Port / Mobile Action Ma-8910p
Also, they are not recognized any of the drivers and do not work:
Bus 001 Device 005: ID 0403: 6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 005: ID 1A86: 7523 Qinheng Electronics CH340 Serial Converter
-
For the "Future Technology" device you should try USBSER.SYS instead of USBCOM.SYS.
-
For the "Future Technology" device you should try USBSER.SYS instead of USBCOM.SYS.
I checked this configuration. Unfortunately, this does not work.
DEVICE=C:\OS2\BOOT\USBSER.SYS /V /Z /N:COM5
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
-
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?
-
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.
-
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
-
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 (http://hobbesarchive.com/?submit=Search&search=lsusb&stype=any&sort=type_name&dir=%2F)
-
Hello Dan
I did light testing with this device:
- https://www.os2world.com/wiki/index.php?title=Prolifc_PL2303_USB_2.0_to_COM
I don't have any serial device anymore to test it out. My only test (if the machine does not have already a serial port) is doing a "mode COM1" if the USB-To-Serial device is disconnected I get "SYS0021: The drive is not ready.", if the devices is plugged I get something in response.
Regards
-
Thanks, that's helpful.
I did a MODE COM6 - and it came up with serial parameters, which was helpful.
I'm using a FT232R, which the docs state has not been verified, but looking through usbser.txt, it looks to be the only in-production device supported.
Hopefully, soon I can get hooked to another PC's RS232 port and test.
-
Hello Dan
It's good that you got a response from the device. Please let me know the HardwareID and any remarks once you test it, so I can include it on the wiki.
Regards