Modbus binding config

Hello everyone

I have some problems with configuring a wellpro wp8026adam 16xDigital input. I also have a wellpro wp8025adam 8x relay output and this works well until I add the wp8026adam. I have given the 8025 address 1 and the 8026 address 2.I already have Tried different addresses and configurations but it does not seem to succeed.
modbus:serial.slave1.connection=/dev/ttyUSB0:9600:8:none:1:rtu
modbus:serial.slave1.type=coil
modbus:serial.slave1.length=8
modbus:serial.slave1.start=0
modbus:serial.slave1.id=1

modbus:serial.slave2.connection=/dev/ttyUSB0:9600:8:none:1:rtu
modbus:serial.slave2.type=discrete
modbus:serial.slave2.length=17
modbus:serial.slave2.start=2
modbus:serial.slave2.id=2

https://pastebin.com/dU9QJxJr

I hope somebody can help me with this. I’ve been working for a couple of days now

I have a feeling that it should be changed to:

modbus:serial.slave2.connection=/dev/ttyUSB0:9600:8:none:1:rtu
modbus:serial.slave2.id=2
modbus:serial.slave2.type=discrete
modbus:serial.slave2.start=0
modbus:serial.slave2.length=16

No it does not work in that configuration it gives the same error in the error logs

Please show your debug with the settings I suggested.
I would also recommend to test the device outside of the OH. Can you operate the module with Wellpro debugging software?

Thanks in advance for thinking

I can control the module with the wellpro debug software in windows.

2017-05-19 18:16:21.893 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 1/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.ReadInputDiscretesRequest@3364d3 (unit id 2 & transaction 118). Serial parameters: SerialParameters@1800c91[portName=/dev/ttyUSB0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-19 18:16:22.069 [INFO ] [nding.sony.internal.ircc.IrccHandler] - Attempting connection to IRCC device…
2017-05-19 18:16:23.449 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 02 02 00 00 00 10 79 f5
2017-05-19 18:16:23.451 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: Error reading response (EOF)
2017-05-19 18:16:23.453 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 2/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.ReadInputDiscretesRequest@3364d3 (unit id 2 & transaction 118). Serial parameters: SerialParameters@1800c91[portName=/dev/ttyUSB0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-19 18:16:25.009 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 02 02 00 00 00 10 79 f5
2017-05-19 18:16:25.011 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: Error reading response (EOF)
2017-05-19 18:16:25.013 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute try 3/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.ReadInputDiscretesRequest@3364d3 (unit id 2 & transaction 118). Serial parameters: SerialParameters@1800c91[portName=/dev/ttyUSB0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-19 18:16:25.014 [ERROR] [pi.modbus.io.ModbusSerialTransaction] - execute reached max tries 3, throwing last error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.ReadInputDiscretesRequest@3364d3. Serial parameters: SerialParameters@1800c91[portName=/dev/ttyUSB0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=none,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
2017-05-19 18:16:25.016 [ERROR] [.binding.modbus.internal.ModbusSlave] - ModbusSlave (slave2): Error getting modbus data for request net.wimpi.modbus.msg.ReadInputDiscretesRequest@3364d3. Error: I/O exception - failed to read. Endpoint ModbusSerialSlaveEndpoint@60ddff[portName=/dev/ttyUSB0]. Connection: SerialConnection@2c1d9f[portName=/dev/ttyUSB0,port=/dev/ttyUSB0]
2017-05-19 18:16:26.779 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - Last request: 02 02 00 00 00 10 79 f5
2017-05-19 18:16:26.780 [ERROR] [t.wimpi.modbus.io.ModbusRTUTransport] - failed to read: Error reading response (EOF)

This is almost exact copy of the example provided in the manual:

Command for digital input collection :
Send: 01 02 00 00 00 10 79 C6

The only difference is a device id and of course the CRC.
Are you sure device id and communication parameters are OK, A/B lines not swapped?

I’ve checked everything with the debug software and I found an error with parity in the 8026 module that I have changed.Now everything is the same.Now i have no error logs anymore but with the 8026 module the light stays red?
The wire’s are not swapped.

I have 8027 only, so I can only refer to the manual for 8026.
If you have individual LEDs red - this could mean they are High, so worth trying to connect a port to Ground and see its status.
In any case you should have something in debug. Make sure it is still enabled.

The power/data led stay’s red.
The red input led lights up if it receives a input.
So that looks good.
I cant see any errors in the logs anymore only info

It seems that he also seems to receive the command of my 8025adam because if I give the 8025 a command, the 8026 turns power / data led red if I disconnect the bus from the 8025 and with a loose wire connect the input Of the 8026 it will not go red

From the manual:

Indicator LED description
When module powered on, Led is green.
When module is under communication, LED is twinkling.
when module receive correct command, LED is green.
when module receive incorrect command or command for other modules, LED is red.

I read the manual to.
I just dont see how he gets the wrong command

this corresponds to when module receive ... command for other modules, LED is red

There is no incorrect command and no command for other modules, so LED is not red.

Yes but how does he receives this incorrect command.
Is this command coming from openhab?
or is this just the command for the 8025 it is a diffrent adress so the command is normaly only for the 8025

yes, I suppose it’s a reaction to command for other module(s) - they’re all on the same bus, so all the devices are receiving all the commands and then just ignoring what is irrelevant.

Thank you for thinking with me I’ll try some more things tomorrow.

I can confirm that when you have several of these Wellpro modules on a bus, polled periodically, the last one to be polled sits with a green LED. All the others show a RED led. At the next poll, they all twinkle a bit and then return to that state.
It is all perfectly normal, by design, no error.

Hello,Rossko

Thank you for this confirmation