DEUTSCHE Version

Our WAC Usage documention describes the protocol in detail and is the starting point for understanding everything else. It contains the fundamental ModBus knowledge you need in order to adapt successfully with our Binding. With this foundation in place, you will be ready to apply the ModBus network rules, so that your home appliances can interoperate with those produced by other manufacturers as part of the OpenHAB ecosystem. This will free consumers to choose the devices that best match their needs, and combine them in novel ways with other compatible devices. See below for guidance as to what to look out for in each section. The possibilities are endless.

A key feature of ModBus that distinguishes it from other protocols is that any given node in the network can act as the master for one channel, and as the slave for another channel.  This allows complex network topologies to be formed.

This section describes how the host (MCU, PC interface etc) can interface with the WAC chip. Extended messaging is also introduced, which is useful if you need to include additional information such as the Device Number. Note that extended messaging does not extend the size of the data payload, which is fixed at 8 bytes and cannot be altered.

to handle many slaves in RTU mode, non blocking connections and RTS flow control.....

modbus_t *mb;

  uint16_t tab_reg[32];

  mb = modbus_new_tcp("127.0.0.1", 1502);
  modbus_connect(mb);

  /* Read 5 registers from the address 0 */
  modbus_read_registers(mb, 0, 5, tab_reg);

  modbus_close(mb);
  modbus_free(mb);

See Examples of typical WAC Bindings, if you have any suggestions or questions don't hesitate to contact us or use our Github account. The snapshot version of our industry4.0 binding can be downloaded, together with the rest of openhab.

Congratulations! You should now have a good general understanding of how the WAC ModBus protocol works, which will give you a strong foundation for all the work you do with OpenHAB. Be Inspired →by our genuine Apps...