Unable to set TC status about ads-rs

[gimmi]

absolutely, I think your driver is doing the right thing by exposing ADS api as is, then the fact that ADS protocol has strange quirks here and there is something that need to be handled by the application code

[birkenfeld]

Thanks for the report, I reproduced this locally.

Using Wireshark I traced what the difference between the PowerShell and this library is, and found that PowerShell actually doesn't set the state to Run but to Reset.

Can you try that?

[birkenfeld]

Also, there is Reconfig which must apparently be used to set to config mode, instead of Config.

[gimmi]

Interesting, will try later

[gimmi]

Confirm working, here is the full test

Starting from state Config

C:\temp>adstool.exe 127.0.0.1/192.168.15.4.1.1 state
Device: TwinCAT System 3.1.4024
Current state: Config

Go from Config to Run

C:\temp>adstool.exe 127.0.0.1/192.168.15.4.1.1 state Reset
Device: TwinCAT System 3.1.4024
Current state: Config
Set new state: Reset

Go from Run to Run (restart)

C:\temp>adstool.exe 127.0.0.1/192.168.15.4.1.1 state Reset
Device: TwinCAT System 3.1.4024
Current state: Run
Set new state: Reset

Go from Run to Config

C:\temp>adstool.exe 127.0.0.1/192.168.15.4.1.1 state Reconfig
Device: TwinCAT System 3.1.4024
Current state: Run
Set new state: Reconfig

Go from Config to Config

C:\temp>adstool.exe 127.0.0.1/192.168.15.4.1.1 state Reconfig
Device: TwinCAT System 3.1.4024
Current state: Config
Set new state: Reconfig

[birkenfeld]

Great! I'll add some text to the help of the state command, but I don't want to change the behavior as long as I don't have full knowledge of what Beckhoff are doing, and I don't think it's documented. Ok?