[Bug] Remote Modules - Deactivation on on host; Reactivation on client

[LukePiewalker]

Version

Development

What is affected by the bug?

Module state of remote module is not displayed in the correct status upon reactivation from the client.

When does the bug occur?

After deactivating a remote (hardware) module on the host, reloading, and activating (cause after reload the module is not displayed as active in the manager GUI) on the client makes the module accessible again, yet it is still listed as deactivated in the manager GUI on the host.

How do we replicate the issue?

• Set up a remote module i.e. a simple switch_dummy with which I tested it (did only use the SwitchDummy, not the SwitchInterfuse) on one machine (Win10)
• Connecting to the remote module from another machine (Win10)
• Deactivating the remote module on the host machine
• Pressing "Reload", then "Activate" on the client machine

Expected behavior

The manager GUI on the host PC should display the correct module state.

Relevant log output

No response

Additional Comments

No response

Contact Details

[email protected]