in reply to Re^2: Win32::SerialPort on Win10 issue
in thread Win32::SerialPort on Win10 issue
Hi. Thanks to all for the help.
I did try Serial Port Monitor (2 weeks trail). Wireshark looks too involved (and I previously have used on TCP/IP only). The Serial Port Monitor gives the response below, when I used the Realterm connection;
[05/07/2024 13:43:32] - Open port COM5 (C:\Program Files (x86)\BEL\Rea +lterm\realterm.exe) # this occurs on connection with SW [05/07/2024 13:04:58] Written data (COM5) 61 74 69 0d ati. + [05/07/2024 13:04:58] Read data (COM5) 45 4c 4d 33 32 37 20 76 31 2e 35 0d 0d 3e ELM327 v1.5..> + [05/07/2024 13:05:05] - Close port COM5 # this occurs on Realterm shutdown
While when I use the PERL connection;
[05/07/2024 13:05:12] - Open port COM5 (C:\Strawberry\perl\bin\perl.ex +e) # occurs with the creation of the object [05/07/2024 13:05:28] - Close port COM5 # occurs with Eclipse shutting down the running Perl
My only conclusion (at this stage) is that I am failing to connect to COM5 while there is nothing suspicious about the USB unit (yes it is a On Board Diagnostic unit used with automobiles with ~16 pin connector and no access to RS232).
Regards JC....
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^4: Win32::SerialPort on Win10 issue
by jmClifford (Beadle) on Jul 08, 2024 at 13:55 UTC | |
|
Re^4: Win32::SerialPort on Win10 issue
by Marshall (Canon) on Jul 06, 2024 at 02:00 UTC |