Modbus RTU Drexel & Weiss <> openHAB

Add-ons Bindings
58

Hi again… since i was busy the last weeks i couldn’t make much progress.
i tried your suggestions:

modbus.cfg:

serial.slave1.connection=/dev/ttyAMA0:9600:8:none:1:rtu
serial.slave1.id=1
serial.slave1.type=input
serial.slave1.start=200
serial.slave1.length=4
serial.slave1.valuetype=int32

items:

Group Modbus
Number Raum_MB "Raumtemperatur raw" (Modbus) {modbus="slave1:0"}
Number Raum_MB_kr "Raumtermperatur" (Modbus)
Number Aussen_MB "Aussentemperatur raw" (Modbus) {modbus="slave1:1"}

i get no values but errors in openhab.log

2017-05-09 19:53:46.916 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 04 00 c8 00 04 70 37
2017-05-09 19:53:46.917 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-09 19:53:46.919 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 1/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.ReadInputRegistersRequest@10da78e (unit id 1 & transaction 1). Serial parameters: SerialParameters@d8e661[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-09 19:53:47.067 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 04 00 c8 00 04 70 37
2017-05-09 19:53:47.072 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-09 19:53:47.073 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 2/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.ReadInputRegistersRequest@10da78e (unit id 1 & transaction 1). Serial parameters: SerialParameters@d8e661[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-09 19:53:47.176 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 04 00 c8 00 04 70 37
2017-05-09 19:53:47.177 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-09 19:53:47.178 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 3/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.ReadInputRegistersRequest@10da78e (unit id 1 & transaction 1). Serial parameters: SerialParameters@d8e661[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-09 19:53:47.178 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute reached max tries 3, throwing last error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.ReadInputRegistersRequest@10da78e. Serial parameters: SerialParameters@d8e661[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-09 19:53:47.179 [ERROR] [.binding.modbus.internal.ModbusSlave] - ModbusSlave (slave1): Error getting modbus data for request net.wimpi.modbus.msg.ReadInputRegistersRequest@10da78e. Error: I/O exception - failed to read. Endpoint ModbusSerialSlaveEndpoint@1c6568[portName=/dev/ttyAMA0]. Connection: SerialConnection@319350[portName=/dev/ttyAMA0,port=/dev/ttyAMA0]

with 2 different slaves it works:

serial.slave1.connection=/dev/ttyAMA0:9600:8:none:1:rtu
serial.slave1.id=1
serial.slave1.type=input
serial.slave1.start=200
serial.slave1.length=2
serial.slave1.valuetype=int32

serial.slave2.connection=/dev/ttyAMA0:9600:8:none:1:rtu
serial.slave2.id=1
serial.slave2.type=input
serial.slave2.start=202
serial.slave2.length=2
serial.slave2.valuetype=int32

items:

Group Modbus
Number Raum_MB "Raumtemperatur raw" (Modbus) {modbus="slave1:0"}
Number Raum_MB_kr "Raumtermperatur" (Modbus)
Number Aussen_MB "Aussentemperatur raw" (Modbus) {modbus="slave2:0"}

This is for reading items.

59

I note that the “working” and “not working” slave1 are completely identical.

60

yeah… well… after changing back to “working” setup i forgot to adjust length to “2”. (correct now in post above!)
just took my 2 hours why i had no success in reading slave1. argh!!! :confounded:

i tried to setup a r/w item and could read 5016, but i wasn’t able to write. i’ll post conf & log tonight!
cheers

61

I’m not an OH2 user, but I see a lot of frustration about its habit of caching configurations and using “older versions”. I suspect an OH restart is needed when tinkering with configs.

Reading with a length of 4 ought to work, we ought to get to the bottom of that.

Note that 32-bit write is problematic, if thats what you are attempting later

1 Like
62

Re caching : even restart might not be enough. Consult this post for more details how to clear the cache : Modbus RTU openHAB binding Error

Best
Sami

63

@ssalonen ty! your link helped clearing cache!

as for my “read/write” item:

modbus.cfg:

serial.slave3.connection=/dev/ttyAMA0:9600:8:none:1:rtu
serial.slave3.id=1
serial.slave3.type=holding
serial.slave3.start=5016
serial.slave3.length=2
serial.slave3.valuetype=int32

item:

Number Raum_MB_Soll "Raumtemperatur SOLL raw" (Modbus) {modbus="slave3:0"}

events.log (when changing temp. on heating system display)

2017-05-10 22:06:24.936 [ItemStateChangedEvent     ] - Raum_MB_Soll changed from 22500 to 22300

and this happens when i try to write: events.log

2017-05-10 22:09:13.895 [ItemCommandEvent          ] - Item 'Raum_MB_Soll' received command 22800
2017-05-10 22:09:14.278 [ItemStateChangedEvent     ] - Raum_MB_Soll changed from 22300 to 22800

it doesn’t relly change…

but i get this in openhab.log:

2017-05-10 22:09:13.985 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 10 13 98 00 01 02 59 10 a3 15
2017-05-10 22:09:13.986 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-10 22:09:13.988 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 1/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@1c7ccc2 (unit id 1 & transaction 49). Serial parameters: SerialParameters@1eaaaaf[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-10 22:09:14.117 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 10 13 98 00 01 02 59 10 a3 15
2017-05-10 22:09:14.118 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-10 22:09:14.120 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 2/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@1c7ccc2 (unit id 1 & transaction 49). Serial parameters: SerialParameters@1eaaaaf[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-10 22:09:14.229 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 10 13 98 00 01 02 59 10 a3 15
2017-05-10 22:09:14.230 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-10 22:09:14.232 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 3/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@1c7ccc2 (unit id 1 & transaction 49). Serial parameters: SerialParameters@1eaaaaf[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-10 22:09:14.233 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute reached max tries 3, throwing last error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@1c7ccc2. Serial parameters: SerialParameters@1eaaaaf[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-10 22:09:14.235 [ERROR] [.binding.modbus.internal.ModbusSlave] - ModbusSlave (slave3): error when executing write request (net.wimpi.modbus.msg.WriteMultipleRegistersRequest@1c7ccc2): I/O exception - failed to read

does this help?

64

From the binding WIKI

Note: The way Decimal commands are handled currently means that it is probably not useful to try to use Decimal commands with non-16bit valuetypes.

You cannot simply write 32-bit at present.

We’ll have to try to hack it with two 16-bit Items. It gets complicated because of the sign.

This is untested -

modbus.cfg to deal with this register pair as 16-bits, important note - Unsigned

writemultipleregisters = true

...
serial.slave3.type=holding
serial.slave3.start=5016
serial.slave3.length=2
serial.slave3.valuetype=uint16

Items to handle 32-bit data in 16-bit chunks

// a virtual item for incoming reading
Number Raum_MB_Soll "Raumtemperatur SOLL raw" (Modbus) {autoupdate="false"}
// a pair of modbus registers for 16-bit read/write
Number Raum_MB_Soll_Hi "Raumtemperatur high byte" (Modbus) {modbus="slave3:0", autoupdate="false"}
Number Raum_MB_Soll_Lo "Raumtemperatur low byte" (Modbus) {modbus="slave3:1", autoupdate="false"}

Rules to do the magic

rule  "process incoming words"
when
   Item Raum_MB_Soll_Lo changed    
then
  Thread::sleep(100)   // _Hi should have changed already, wait a little to be sure
   var int hiraw = (Raum_MB_Soll_Hi.state as DecimalType).intValue   // get word
   var int loraw = (Raum_MB_Soll_Lo.state as DecimalType).intValue
   var int result = (hiraw * 65535) + loraw
   if (hiraw > 32767 ) {
         // oh dear it is signed, weird maths to follow
      result =  result - 4294967296    // think this extracts twos complement to signed ?!
   } 
   Raum_MB_Soll.postUpdate(result)    // to virtual item
end

rule "process outgoing value"
when
   Item Raum_MB_Soll received command    // from UI or rule
then
   var int raw32 = (receivedCommand as DecimalType).intValue
   if (raw32 < 0) {
      logInfo("mbconvert","negative numbers not supported")    // I chickened out of twos complement maths
   } else {
      var int hival = raw32 / 65535
      var int loval = raw32.bitwiseAnd(65535)    // mask with FFFF
      Raum_MB_Soll_Hi.sendCommand(hival)
      Raum_MB_Soll_Lo.sendcommand(loval)
   }
end

I do not know if this idea will work at all, if the OH binding sends the two halves of the 32-bit pair separately the slave might reject it.

This is where you would want autoupdate=“false” in your Item config to ensure that the value in OH reflects what is in the real modbus device (at the next read poll), otherwise when you send the Item a command from UI or rule the autoupdate feature changes the Item value.

65

Thanks @rossko57 for pitching in. I fear that even that might not work since the default behavior is to write single register. The value written will be the decimal value rounded to 16bit integer, and function code will be 6 or 16 depending on the config.

Perhaps this slave refuses to respond with single register writes?

Best
Sami

66

That is my suspicion too, likely the reason that it only supports FC16

67

should i ask the manufacturer something?

68

error for rule:

2017-05-11 13:45:25.258 [ERROR] [.script.engine.ScriptExecutionThread] - Rule 'process outgoing value': An error occured during the script execution: The name '<XFeatureCallImplCustom>.sendcommand(<XFeatureCallImplCustom>)' cannot be resolved to an item or type.
69

Check Item(s) exist.
Does the read part work? twos complement stuff scares me.

70

items exist - i used your input 1:1
read part seems to work!

2017-05-11 15:34:40.584 [ItemStateChangedEvent     ] - Raum_MB_Soll_Lo changed from 22500 to 22000
2017-05-11 15:34:40.744 [ItemStateChangedEvent     ] - Raum_MB_Soll changed from 22500 to 22000
71

There is a funny pratfall using primitive variables like int, but I thought it did not apply to item.sendCommand method.

nevertheless, try instead

      var Number hival = (raw32 / 65535).intValue
      var Number loval = raw32.bitwiseAnd(65535)    // mask with FFFF
      Raum_MB_Soll_Hi.sendCommand(hival)
      Raum_MB_Soll_Lo.sendcommand(loval)

I’m still expecting to see a Modbus failure in the end though

72

Still a problem with rule:

2017-05-11 21:59:22.106 [ERROR] [.script.engine.ScriptExecutionThread] - Rule 'process outgoing value': An error occured during the script execution: The name '<XFeatureCallImplCustom>.sendcommand(<XFeatureCallImplCustom>)' cannot be resolved to an item or type.
2017-05-11 21:59:22.188 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 10 13 98 00 01 02 00 00 98 89
2017-05-11 21:59:22.189 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-11 21:59:22.190 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 1/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@13dbc24 (unit id 1 & transaction 1146). Serial parameters: SerialParameters@5f0110[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-11 21:59:22.296 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 10 13 98 00 01 02 00 00 98 89
2017-05-11 21:59:22.298 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-11 21:59:22.300 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 2/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@13dbc24 (unit id 1 & transaction 1146). Serial parameters: SerialParameters@5f0110[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-11 21:59:22.418 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 10 13 98 00 01 02 00 00 98 89
2017-05-11 21:59:22.420 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-11 21:59:22.422 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 3/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@13dbc24 (unit id 1 & transaction 1146). Serial parameters: SerialParameters@5f0110[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-11 21:59:22.426 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute reached max tries 3, throwing last error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@13dbc24. Serial parameters: SerialParameters@5f0110[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-11 21:59:22.430 [ERROR] [.binding.modbus.internal.ModbusSlave] - ModbusSlave (slave3): error when executing write request (net.wimpi.modbus.msg.WriteMultipleRegistersRequest@13dbc24): I/O exception - failed to read

this is rules:

rule  "process incoming words"
when
   Item Raum_MB_Soll_Lo changed    
then
  Thread::sleep(100)   // _Hi should have changed already, wait a little to be sure
   var int hiraw = (Raum_MB_Soll_Hi.state as DecimalType).intValue   // get word
   var int loraw = (Raum_MB_Soll_Lo.state as DecimalType).intValue
   var int result = (hiraw * 65535) + loraw
   if (hiraw > 32767 ) {
         // oh dear it is signed, weird maths to follow
      result =  result - 4294967296    // think this extracts twos complement to signed ?!
   } 
   Raum_MB_Soll.postUpdate(result)    // to virtual item
end

rule "process outgoing value"
when
   Item Raum_MB_Soll received command    // from UI or rule
then
   var int raw32 = (receivedCommand as DecimalType).intValue
   if (raw32 < 0) {
      logInfo("mbconvert","negative numbers not supported")    // I chickened out of twos complement maths
   } else {
      var Number hival = (raw32 / 65535).intValue
      var Number loval = raw32.bitwiseAnd(65535)    // mask with FFFF
      Raum_MB_Soll_Hi.sendCommand(hival)
      Raum_MB_Soll_Lo.sendcommand(loval)
   }
end
73

You don’t happen to have Items called hival or loval, by chance? Change the var names in the rule to avoid a clash.

I fear the Modbus error is terminal for this whole idea though. It appears this slave insists on a pair of registers being written together - fair enough for a 32-bit target. The current OH binding simply will not do that, it writes one at a time. (selecting writemultipleregisters only chooses write mode FC16, it actually still writes one at a time just using a different Modbus command).

Your only hope is for ‘someone’ to implement 32-bit writes, whcih may not be as easy as it sounds.

74

there’s defInitely no item called hival or loval.
what does this mean?

The name '<XFeatureCallImplCustom>.sendcommand(<XFeatureCallImplCustom>)' cannot be resolved to an item or type.

i had the same error on a completely different rule… (playsound()) …

75

ahh it’s a test you see … you copy/pasted my sendcommand/sendCommand typo :blush:

76

copy/paste is all i do here :relaxed: since this last posts are all beyond my understanding…

Raum_MB_Soll_Lo.sendcommand(loval)

should be

Raum_MB_Soll_Lo.sendCommand(loval)

and that’s it? or did you hide more typos?

77

okay, the rule error doesn’t pop up anymore… still, doesn’t seem to work:

2017-05-12 20:35:58.446 [ItemCommandEvent          ] - Item 'Raum_MB_Soll' received command 23500
2017-05-12 20:35:58.471 [ItemCommandEvent          ] - Item 'Raum_MB_Soll_Hi' received command 0
2017-05-12 20:35:58.482 [ItemCommandEvent          ] - Item 'Raum_MB_Soll_Lo' received command 23500

2017-05-12 20:35:58.573 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 10 13 98 00 01 02 00 00 98 89
2017-05-12 20:35:58.575 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-12 20:35:58.576 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 1/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@1188266 (unit id 1 & transaction 3065). Serial parameters: SerialParameters@14caf0d[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-12 20:35:58.683 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 10 13 98 00 01 02 00 00 98 89
2017-05-12 20:35:58.684 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-12 20:35:58.686 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 2/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@1188266 (unit id 1 & transaction 3065). Serial parameters: SerialParameters@14caf0d[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-12 20:35:58.797 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 10 13 98 00 01 02 00 00 98 89
2017-05-12 20:35:58.798 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-12 20:35:58.800 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 3/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@1188266 (unit id 1 & transaction 3065). Serial parameters: SerialParameters@14caf0d[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-12 20:35:58.801 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute reached max tries 3, throwing last error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@1188266. Serial parameters: SerialParameters@14caf0d[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-12 20:35:58.802 [ERROR] [.binding.modbus.internal.ModbusSlave] - ModbusSlave (slave3): error when executing write request (net.wimpi.modbus.msg.WriteMultipleRegistersRequest@1188266): I/O exception - failed to read
2017-05-12 20:35:58.930 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 10 13 99 00 01 02 5b cc a2 3d
2017-05-12 20:35:58.932 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-12 20:35:58.934 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 1/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@f8024f (unit id 1 & transaction 3066). Serial parameters: SerialParameters@185c155[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-12 20:35:59.041 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 10 13 99 00 01 02 5b cc a2 3d
2017-05-12 20:35:59.042 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-12 20:35:59.044 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 2/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@f8024f (unit id 1 & transaction 3066). Serial parameters: SerialParameters@185c155[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-12 20:35:59.157 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 01 10 13 99 00 01 02 5b cc a2 3d
2017-05-12 20:35:59.158 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: CRC Error in received frame: 0 bytes:
2017-05-12 20:35:59.160 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 3/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@f8024f (unit id 1 & transaction 3066). Serial parameters: SerialParameters@185c155[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-12 20:35:59.161 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute reached max tries 3, throwing last error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.WriteMultipleRegistersRequest@f8024f. Serial parameters: SerialParameters@185c155[portName=/dev/ttyAMA0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-12 20:35:59.162 [ERROR] [.binding.modbus.internal.ModbusSlave] - ModbusSlave (slave3): error when executing write request (net.wimpi.modbus.msg.WriteMultipleRegistersRequest@f8024f): I/O exception - failed to read