Provide additional error info for Modbus errors
planned
b
brianfitz612
Currently, the wrapper.log (and the gateway console) provide an error message when it receives a response from a Modbus slave device containing an exception code. Example:
INFO | jvm 1 | 2016/04/02 17:30:49 | ERROR [ReadHoldingRegistersRequest ] [17:30:49,141]: Received response with ExceptionCode: 0x08 (MemoryParityError).
However, it does not provide any info on what slave it was trying to talk to or what register it was trying to read. Even info on the tag it was trying to update would be helpful, if that is easier to provide. This info would be useful in trying to troubleshoot and track down troublesome equipment on the network.
Log In
kevin@inductiveautomation.com
The
device-name
MDC key was broken for some drivers but recently fixed, so that should cover figuring out which device the error is occurring on. More info about what addresses/registers were being read would be useful though.
l
lionel MAZEYRAT
device-name in the log and MDC filter with the device name could help