User Tools

Site Tools


supported_protocols

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
supported_protocols [2019/01/09 14:29] – [The protocols supported] emozolyaksupported_protocols [2022/08/24 08:54] (current) – [Implemented using custom protocol mechanism] emozolyak
Line 1: Line 1:
 ====== The protocols supported ====== ====== The protocols supported ======
 +{{ network:comm_protocol_icon.png?nolink&100|}}
 WebHMI supports the following communication protocols: WebHMI supports the following communication protocols:
  
Line 6: Line 6:
   *[[adv_protocol| Advantech Adam serial protocol]]   *[[adv_protocol| Advantech Adam serial protocol]]
   *[[df1| Allen-Bradley DF1]]   *[[df1| Allen-Bradley DF1]]
 +  *[[eth_ip| Allen-Bradley Ethernet/IP]]
   *[[bacnet| Bacnet]]   *[[bacnet| Bacnet]]
   *[[delta_dvp|Delta Electronics DVP protocol]]   *[[delta_dvp|Delta Electronics DVP protocol]]
   *[[melsec| Mitsubishi Melsec protocol]]   *[[melsec| Mitsubishi Melsec protocol]]
   *[[modbus_protocol|Modbus protocol]]   *[[modbus_protocol|Modbus protocol]]
 +  *[[mqtt|MQTT protocol]]
   *[[owen| Owen protocol]]   *[[owen| Owen protocol]]
   *[[siemens_ppi| Siemens PPI ]]   *[[siemens_ppi| Siemens PPI ]]
 +  *[[siemens_iso| Siemens S7 Communicatoin (Iso-Over-Tcp) ]]
 +  *[[1wire| 1Wire bus for temperature sensors]]
 +  *[[broadlink_sps3| Broadlink SPS3]]
  
  
Line 39: Line 44:
  
  
-===== Siemens S7 Communication ===== 
  
-{{::s7-1200.jpg?direct|}} 
  
-Since version 1.7.0.3180 WebHMI supports work with Siemens S7 controllers via S7 Communication protocol over Ethernet (Profinet interface on the controller). It makes possible for WebHMI to work with PLCs such as Siemens S7-300, S7-400, S7-1200, S7-1500 and others that support this protocol. To configure the connection, you must define the following parameters in the controller configuration: 
  
-  ***PLC address** - This is the IP address of the controller or the communication module.  
-  ***TSAP** - This is the device address in the COTP protocol. It is indicated in hexadecimal format. The high byte indicates the access type (default is 03). The low byte consists of two values ​​of Rack (default is 0) and Slot (default is 1). See the documentation for the controller for more details. WebHMI uses local TSAP number = 1000. 
-In the S7 Communication protocol, the following registers are supported: 
  
-^Register ^Description ^Data type ^Read/Write^ 
-|Qx.y |Digital outputs of the controller. X — offset address, Y — bit address. You can address both bits and bytes and words. Examples: Q0.2, QB2, QW0, QD2 |Bit, Byte, Word, Double Word |Read/Write| 
-|Ix.y |Digital inputs of the controller. X — offset address, Y — bit address. You can address both bits and bytes and words. Examples: I0.2, IB2, IW0, ID2 |Bit, Byte, Word, Double Word |Read/—| 
-|Mx.y |М memory. X — offset address, Y — bit address. You can address both bits and bytes and words. Examples: M0.2, MB2, MW0, MD2 |Bit, Byte, Word, Double Word |Read/Write| 
-|Vx.y |Synonymous to DB1.DBxx. Accessing to memeory block DB1. X — offset address, Y — bit address. You can address both bits and bytes and words. Examples: V0.2, VB2, VW0, VD2 |Bit, Byte, Word, Double Word |Read/Write| 
-|DBx.DBy.z |Addressing datablock DBx, where X - datablock number (1, 2, 3 ...). Y — offset inside the datablock, Z — bit number. You can address both bits and bytes and words. Examples: DB1.DBB0.2, DB4.DBD2, DB4.DBW13.3 |Bit, Byte, Word, Double Word |Read/Write| 
  
-Note that although WebHMI correctly recognizes addresses with the data size included in them (for example, IW0 in the notation Siemens stands for a Word type register), but the data size from the address itself is ignored and instead the data size specified in the WebHMI project settings of this register is used. I.e. the address is used exclusively as an base address and in fact the three addresses IW0, IB0, ID0 are equivalent to the record I0. 
  
-Example of setting up a connection for the S7-1200 controller see : here. 
  
-Connecting WEBHMI to Siemens controllers is possible simultaneously with other devices on the same network (HMI panels, other controllers), because the controllers support several connections, depending on the type: 
  
-{{::s7-comm_1200_conn.png?direct&400|}} 
-{{::s7-comm_400_conn.png?direct&400|}} 
- 
-===== 1-Wire ===== 
- 
-Since WebHMI version 1.11.0.3453 1-Wire protocol support were added. 
- 
-At the current moment, it is possible to poll the DS18x20 family of sensors. To work with the 1-Wire bus you need a special USB adapter. E.g. like this one: 
- 
-{{::usb-1-wire.jpg?direct&200|}} 
- 
-When creating a connection, you must select: 
-  *PLC model: 1-Wire 
-  *Protocol: DS18x20 or DS2480 depending on the adapter you use 
- 
-{{::1wire_select_adapter.png?direct&500|}} 
- 
-Device: corresponding USB UART adapter. 
- 
-{{::1wire_select_bus.png?direct&800|}} 
- 
-When creating a register for thermometers, it is necessary to specify such register address format: "T" + thermometer address in hexadecimal. For example, **T28FFC85115150131**. 
- 
-For more convenient use of the system, under the address line of the register address, a link appears //Select 1-Wire device...//: 
-{{::one_wire_search.png?direct&600|}} 
- 
-If you click on it, the system will search for all devices on the 1-Wire bus and a new window will pop up where all these devices will be listed. For thermometers DS18x20 in the corresponding line will be a link with the correct register address for this thermometer. If you click on this address, the window will automatically close and the selected address will be inserted in the address field of the register:  
-{{::select_1w_sensor.png?direct&600|}} 
- 
-  P.S. The speed of reading 1-wire values ​​depends strongly on the selected UART-converter. So, the adapters on the  
-  FTDI chip will make big delays due to LatencyTimer's timeout. Reading one temperature reading on this adapter  
-  takes about 100ms. 
- 
-===== Broadlink SP3S ===== 
- 
-{{::broadlink_sps3.png?direct&150 |}} 
-Since version 2.10, WebHMI supports the Broadlink SP3S smart socket protocol. 
- 
-At the moment, supported protocol data are - state of the socket (on / off) and the power consumption. 
- 
-Following addressing map for the registers of the Broadlink SP3S socket is adopted: 
-^Register address ^Description ^Data type ^Reading/Writing^ 
-|DO1 |Digital Output 1. Allows switching on/off and read its state |Bit |Read/Write| 
-|P1 |Power Consumption, Watts |Double Word, Float, 32 IEEE 754 |Read/-| 
  
 ===== Implemented using custom protocol mechanism ===== ===== Implemented using custom protocol mechanism =====
 +The most popular custom protocols implemented are those:
  
-  *M-Bus (for heat meters (SCYLAR, SKS-3) +  *[[examples_of_webhmi_connections_to_various_devices| M-Bus (for heat meters (SCYLAR, SKS-3) ]] 
-  *DLMS/COSEM (for NIK electricity power meters) +  *[[examples_of_webhmi_connections_to_various_devices|DLMS/COSEM (for NIK electricity power meters)]] 
 +  *[[omron-c-commands|Omron Hostlink protocol]]
  
 +For more examples, please refer to [[examples_of_webhmi_connections_to_various_devices|this link]].
  
supported_protocols.1547044151.txt.gz · Last modified: 2019/01/09 14:29 by emozolyak

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki