Skip to content
This repository has been archived by the owner on May 17, 2021. It is now read-only.

Serial modbus binding not working in v1.7.0 #2720

Closed
lionelbeard opened this issue Jun 12, 2015 · 1 comment
Closed

Serial modbus binding not working in v1.7.0 #2720

lionelbeard opened this issue Jun 12, 2015 · 1 comment

Comments

@lionelbeard
Copy link
Contributor

Hi,

Evertyhing was working fine in v1.6.2.
But since v1.7.0 update, nothing happens on serial bus with modbus binding.

Port permission is ok and openhab belongs to dialout group.

My openhab.cfg configuration looks like:
"

System

modbus:serial.slaveSystem.connection=/dev/ttyUSB0:19200:8:even:1
modbus:serial.slaveSystem.start=0
modbus:serial.slaveSystem.length=25
modbus:serial.slaveSystem.type=holding

Zone 1

modbus:serial.slaveZone1.connection=/dev/ttyUSB0:19200:8:even:1
modbus:serial.slaveZone1.start=256
modbus:serial.slaveZone1.length=14
modbus:serial.slaveZone1.type=holding

Zone 2

modbus:serial.slaveZone2.connection=/dev/ttyUSB0:19200:8:even:1
modbus:serial.slaveZone2.start=512
modbus:serial.slaveZone2.length=14
modbus:serial.slaveZone2.type=holding
"

And with debug output I get these warnings:
"
23:07:15.820 [DEBUG] [.modbus.internal.ModbusBinding:282 ] - modbusSlave 'slaveSystem' instanciated
23:07:15.824 [DEBUG] [b.m.internal.ModbusSerialSlave:41 ] - overriding modbus port: null by: /dev/ttyUSB0but there is currently only one port supported

23:07:15.827 [DEBUG] [.modbus.internal.ModbusBinding:282 ] - modbusSlave 'slaveZone1' instanciated
23:07:15.830 [DEBUG] [b.m.internal.ModbusSerialSlave:41 ] - overriding modbus port: /dev/ttyUSB0 by: /dev/ttyUSB0but there is currently only one port supported

23:07:15.832 [DEBUG] [.modbus.internal.ModbusBinding:282 ] - modbusSlave 'slaveZone2' instanciated
23:07:15.835 [DEBUG] [b.m.internal.ModbusSerialSlave:41 ] - overriding modbus port: /dev/ttyUSB0 by: /dev/ttyUSB0but there is currently only one port supported
"

Some tests I have made:

  • with minicom and binding v1.7.0, nothing happens on serial bus
  • with minicom and binding v1.6.2, I see some traffic

So nothing is written on serial bus with last version of modbus binding.

Workaround I found is to unpack v1.6.2 into addons directory (even with runtime v1.7.0), and it is working again.

Thanks!

@lionelbeard
Copy link
Contributor Author

Ok I found, issue can be closed.
A new parameter has been added to connection line in openhab.cfg.
The new syntax is:
modbus:serial.slaveSystem.connection=:::::

The last one is new with v1.7.0, and allow to choose between 3 different serial encodings. The value can be:
ascii (default one)
rtu
bin

If the field is empty (it is the case when you're upgrading from previous version), ASCII encoding is apply.
But my AIRZONE mainboard talks RTU modbus!!
So after adding :rtu at the end of each connection lines of my openhab.cfg file, it is now working!

jowi24 pushed a commit to jowi24/openhab that referenced this issue Aug 7, 2015
updated the copyright header with the year 2015
added immediate="true" flag to binding.xml, otherwise the binding does
 not get started automatically
removed unnecessary imports
removed the Activator. The bundleContext is available from the call to
 the activate method. The static Activator access is discouraged, since
 it is only valid when the bundle is ACTIVE, however, any code could
 access the static variable at any point in time
jowi24 pushed a commit to jowi24/openhab that referenced this issue Aug 7, 2015
changed the archetype default binding project according to openhab#2720
jowi24 pushed a commit to jowi24/openhab that referenced this issue Aug 7, 2015
* master:
  Bugfix for issue openhab#1351 Configurable command interval
  Removed annoying bin folders including .project files
  issue openhab#2027 - added modified callback for dynamic changes to the binding configuration
  Fix RRD4J error at midnight
  changed the archetype default binding project according to openhab#2720 updated the copyright header with the year 2015 added immediate="true" flag to binding.xml, otherwise the binding does  not get started automatically removed unnecessary imports removed the Activator. The bundleContext is available from the call to  the activate method. The static Activator access is discouraged, since  it is only valid when the bundle is ACTIVE, however, any code could  access the static variable at any point in time
  Adds the leviton vrcz4-m0z to the zwave database
jowi24 pushed a commit to jowi24/openhab that referenced this issue Aug 7, 2015
* zwave-database_updates:
  Add TKB TZ06
  Update codes for Fibaro universal sensor
  Bugfix for issue openhab#1351 Configurable command interval
  Removed annoying bin folders including .project files
  issue openhab#2027 - added modified callback for dynamic changes to the binding configuration
  Fix RRD4J error at midnight
  changed the archetype default binding project according to openhab#2720 updated the copyright header with the year 2015 added immediate="true" flag to binding.xml, otherwise the binding does  not get started automatically removed unnecessary imports removed the Activator. The bundleContext is available from the call to  the activate method. The static Activator access is discouraged, since  it is only valid when the bundle is ACTIVE, however, any code could  access the static variable at any point in time
jowi24 pushed a commit to jowi24/openhab that referenced this issue Aug 7, 2015
* zwave-initialisation:
  Bugfix for issue openhab#1351 Configurable command interval
  Removed annoying bin folders including .project files
  issue openhab#2027 - added modified callback for dynamic changes to the binding configuration
  Fix RRD4J error at midnight
  changed the archetype default binding project according to openhab#2720 updated the copyright header with the year 2015 added immediate="true" flag to binding.xml, otherwise the binding does  not get started automatically removed unnecessary imports removed the Activator. The bundleContext is available from the call to  the activate method. The static Activator access is discouraged, since  it is only valid when the bundle is ACTIVE, however, any code could  access the static variable at any point in time
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant