"Device or resource busy" in RTU server example about tokio-modbus

[wheregmis]

You can create a virtual serial ports using socat

and run
socat -d -d pty,raw,echo=0 pty,raw,echo=0
You will get two virtual serial ports for unix. (development purpose)
`
2023/11/28 15:10:19 socat[66531] N PTY is /dev/ttys031

2023/11/28 15:10:19 socat[66531] N PTY is /dev/ttys033

2023/11/28 15:10:19 socat[66531] N starting data transfer loop with FDs [5,5] and [7,7]

`

Use one for the server and another for the client
`

let server_builder = tokio_serial::new("/dev/ttys031", 19200);

let client_builder = tokio_serial::new("/dev/ttys033", 19200);

`

Use these builder for server and client. It will work.

[thienandangthanh]

I find out that it's used again in this line.

tokio-modbus/examples/rtu-server.rs

Line 53 in 5fc09c4

let client_serial = tokio_serial::SerialStream::open(&builder).unwrap();

And I still don't know how to make it work.

I think the examples and docs should be more easy to understand. Their purpose is to guide library user, not to confuse us.

[thienandangthanh]

Should we use other device path, like "/dev/ttyUSB1" to create the builder for client_serial instead of using the same builder?