Fetching the coupler ID

[thy1037]

Only use tokio and tokio-modbus, and run the tcp-client example code, but show Fetching the coupler ID

Reproduction:

1. cargo new a new project
2. add tokio-modbus = "0.5.3", tokio = {version = "=1.22.0", features = ["full"]} to Cargo.toml
3. copy the example tcp-client code to main.rs
4. run cargo build, success, but cargo run show:

D:\xxx\yyy>cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.11s
     Running `target\debug\tokio-modbus.exe`
Fetching the coupler ID

Environment:
Win10
rustc 1.65.0 (897e37553 2022-11-02)
rustup 1.25.1 (bb60b1e89 2022-07-12)
x86_64-pc-windows-msvc
Modbus server use the Qt QModubs example's modbusslave.exe , with the configuration: tcp, 127.0.0.1:502 (modbusmaster.exe can work well)

[uklotzde]

If no one is able to reproduce the described behavior in their environment and without further details about the exact setup I recommend to close this issue.