The modbusbase.vb is common for all modbus comms right?
ModbusBase.vb is the common class definition for both TCP and RTU driver.
Sometimes data is not updated when the form2 is viewed but the subscription is still active due to form1 so checking the disable subscription would return false.
Each instance of the driver does it's own subscription handling, so the Form1 instance can continue to poll and update subscriptions, but the DisableSubscriptions can be True on the Form2 driver instance without effecting form 1.
I set the poll rate different between the forms so I can view the TxRx lights to determine which form subscription is "active". When data is not updated on form2 the TxRx lights indicate form1 is polling data. It appears that sometimes form2 subscription does not initiate when form2 is opened because form1 already has a subscription to the device.
If a driver instance is on Form2, when it comes to subscriptions and polling, it will be completely independent of Form1's instance.
By checking which value the DisableSubscriptions gets set to, you can get an idea whether one of the driver instance's subscriptions gets stopped.