in reply to Win32::SerialPort on Win10 issue

> The actual write and read of data does not work

Not a helpful description :-) ... you'll need to show us your code that does not work, ideally in a SSCCE, along with a description of what you are trying to achieve.

For some sample PM code that uses Win32::SerialPort see: How to read serial port with WIN32:SerialPort? 

👁️🍾👍🦟

Replies are listed 'Best First'.
Re^2: Win32::SerialPort on Win10 issue
by cavac (Prior) on Jul 04, 2024 at 07:53 UTC

    Not a helpful description :-)

    Actually, in this specific case it most likely is. Win32::SerialPort is strange in how it works in the Background. The Linux/Unix version (Device::SerialPort) seems to just work by setting some parameters (baud rate etc) and you can get immediately to sending/receiving data.

    But in Win32::SerialPort, you have to call write_settings() after configuration changes, otherwise the object will just sit there ignoring all your send/receive calls, most likely without showing a warning or raising an error.

    PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP
    Also check out my sisters artwork and my rather simple sketches/one-panel comics
[reply]

In Section Seekers of Perl Wisdom