When switching the Bachmann M1 driver into "callback" mode it does not react on a communication loss. When having the driver not in callback mode it recognizes communication loss proper and does a reconnect when cable is plugged in again. Also a message in Diagviewer is logged that the communication timed out. When switching it into callback mode the communication loss is not recognized when unplugging the cable. Nothing is logged in Diagviewer, no INVALID. When plugging the cable in the communication runs proper again. This makes problems when there are variable which have not yet been updated (no value, no status). These variables remain in that state when communication is lost.
When switching the Bachmann M1 driver into "callback" mode it does not react on a communication loss. When having the driver not in callback mode it recognizes communication loss proper and does a reconnect when cable is plugged in again. Also a message in Diagviewer is logged that the communication timed out. When switching it into callback mode the communication loss is not recognized when unplugging the cable. Nothing is logged in Diagviewer, no INVALID. When plugging the cable in the communication runs proper again. This makes problems when there are variable which have not yet been updated (no value, no status). These variables remain in that state when communication is lost.
The connection will be checked correctly.
Attention: with this fix:
When a communication failure occurs and variables are set to INVALID the driver cannot reconnect to the PLC.
Bachman does not support this communication protocol anymore. The suggestion from Bachmann for workarround of this reconnect issue is to use OPC UA connection with their PLCs. There is also an OPC UA Client driver in zenon that can be used for this connection.