I’m currently working with the advanced Modbus driver for ClearSCADA/GeoSCADA Expert and have encountered an interesting challenge. It appears that the driver uses a transaction identifier value of ‘0’ until it receives a valid response from the outstation, at which point it starts incrementing the identifier. However, my outstation does not respond to a transaction identifier of ‘0’ and requires a non-zero identifier. I’ve tested this with Modbus Poll and Modscan software, both of which communicate successfully as soon as the transaction identifier is greater than zero.
I’m seeking advice on how to adjust the settings in ClearSCADA/GeoSCADA Expert to ensure the transaction identifier is always non-zero. This would streamline communication and prevent potential issues with devices that require a non-zero transaction identifier. If anyone has experience with this configuration or can provide guidance, I’d greatly appreciate it!