Changes for page 12 PLC Protocol OLD

Last modified by Mora Zhou on 2024/12/05 14:53

From 103.1 to 102.1 From 135.1 to 134.1

From version 134.1

edited by Ben
on 2022/08/30 14:55

Change comment: There is no comment for this version

To version 103.1

edited by Ben
on 2022/08/29 16:38

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 9 removed)

Details

Page properties

Content

@@ -511,7 +511,7 @@
  (% style="text-align:center" %)
  [[image:12.PLC Protocol_html_58205bdf82c06d4.png||data-xwiki-image-style-alignment="center" height="307" width="500" class="img-thumbnail"]]
--== **CompactLogix FreeTag Ethernet protocol** ==
++== **FreeTag Ethernet/IP (CompactLogix)** ==
  Allen-Brandly CompactLogix
@@ -568,7 +568,7 @@
  (% style="text-align:center" %)
  [[image:12.PLC Protocol_html_2297240b57346b2a.png||data-xwiki-image-style-alignment="center" height="170" width="400" class="img-thumbnail"]]
--== **MicroLogix 1200** ** protocol** ==
++== **AB PLC address edit** ==
  The operational address is determined by the connection of Allen-Bradley PLC to HMI. For extension modules or other special conditions, refer to allen-Bradley PLC instruction manual. The following is an example of allen-bradley MicroLogix1200.
@@ -1631,192 +1631,242 @@
  **1）HMI Settings**
--|**Item**|**Settings**|**Note**
--|Protocol|DELTA AS300 MODBUS RTU|
--|Connection|RS485|
--|Baud rate|9600|
--|Data bit|8|
--|Parity|NONE|
--|Stop bit|1|
--|PLC station No.|1|
--
  **2）Address List**
++**3）Configure the communication protocol**
--|**Type**|**Device registers**|**HMI registers**|**Format**|**Range**|**Note**
--|Bit|X|X|X d|0~~63|
--|Bit|Y|Y|Y d|0~~63|
--|Bit|D|D|D d|0~~29999|
--|Bit|M|M|M d|0~~8191|
--|Bit|SM|SM|SM d|0~~4095|
--|Bit|S|S|S h|0~~2047|
--|Bit|T|T|T d|0~~511|
--|Bit|C|C|C d|0~~511|
--|Bit|HC|HC|HC d|0~~255|
--|Word|X|X|X h|0~~63|
--|Word|Y|Y|Y d|0~~63|
--|Word|SR|SR|SR d|0~~2047|
--|Word|D|D|D d|0~~29999|
--|Word|T|T|T d|0~~511|
--|Word|C|C|C h|0~~511|
--|Word|E|E|E d|0~~9|
++**4）Cable Wiring**
--**3）Configure the communication protocol**
++== **AS Ethernet Protocol** ==
--[[image:image-20220830094600-1.png]]
++**1）HMI Settings**
--[[image:image-20220830094657-2.png]]
++**2）Address List**
++**3）Configure the communication protocol**
++
  **4）Cable Wiring**
--Figure
++= **MODBUS** =
--[[image:image-20220830141138-1.png]]
++== **MODBUS RTU Master** ==
--Pin Definition Diagram
++Supported Series: MODBUS RTU CONTROLLER
--[[image:image-20220830095131-1.png]]
++HMI works as MODBUS SLAVE connecting with MASTER
--== **AS Ethernet Protocol** ==
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_44425b313b0a6b96.png||data-xwiki-image-style-alignment="center" height="571" width="544" class="img-thumbnail"]]
--**1）HMI Settings**
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_b56b9da32c3caaa.png||data-xwiki-image-style-alignment="center" height="462" width="600" class="img-thumbnail"]]
--|=**Items**|=**Settings**|=**Note**
--|Protocol|DELTA AS300 MODBUS TCP|
--|Connection|Ethernet|
--|Port No.|502|
--|Device No.|1|
--|HMI No.|0|
--**2）Address List**
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_67cd25458b9c72a6.png||data-xwiki-image-style-alignment="center" height="462" width="600" class="img-thumbnail"]]
++**HMI Settings**
--|**Type**|**Device registers**|**HMI registers**|**Format**|**Range**|**Note**
--|Bit|X|X|X d|0~~63|
--|Bit|Y|Y|Y d|0~~63|
--|Bit|D|D|D d|0~~29999|
--|Bit|M|M|M d|0~~8191|
--|Bit|SM|SM|SM d|0~~4095|
--|Bit|S|S|S h|0~~2047|
--|Bit|T|T|T d|0~~511|
--|Bit|C|C|C d|0~~511|
--|Bit|HC|HC|HC d|0~~255|
--|Word|X|X|X h|0~~63|
--|Word|Y|Y|Y d|0~~63|
--|Word|SR|SR|SR d|0~~2047|
--|Word|D|D|D d|0~~29999|
--|Word|T|T|T d|0~~511|
--|Word|C|C|C h|0~~511|
--|Word|E|E|E d|0~~9|
++(% class="table-bordered" %)
++|**Items**|**Settings**|**Note**
++|Protocol|MODBUS RTU Master|
++|Connection|RS485/RS232|
++|Baud rate|2400~~187500|
++|Data bit|8|
++|Parity|Even/ Odd/ None|
++|Stop bit|1/2|
++|Station No.|0~~255|
--**3）Configure the communication protocol**
++**Address List**
--[[image:image-20220830140537-1.png]]
++(% class="table-bordered" %)
++|**Type**|**HMI address**|**MODBUS code**|**Range**
++|Bit|HDX3000.0~~HDX3499.15|0|0~~7999
++|Word|HDW3500~~HDW7999|4|0~~4499
--[[image:image-20220830140629-2.png]]
++**Cable Wiring**
--**4）Cable Wiring**
++* **RS485**
--Figure
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_68dfb6d383f0edd9.png||data-xwiki-image-style-alignment="center" height="244" width="394" class="img-thumbnail"]]
--[[image:image-20220830094929-1.png]]
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_cbeb90cb4faaa8bc.png||data-xwiki-image-style-alignment="center" height="244" width="394" class="img-thumbnail"]]
--Pin Definition Diagram
++* **RS232**
--[[image:https://docs.we-con.com.cn/bin/download/PIStudio/12.PLC%20protocols/WebHome/12.PLC%20Protocol_html_2297240b57346b2a.png?width=401&height=170&rev=1.1||alt="12.PLC Protocol_html_2297240b57346b2a.png" height="170" width="401"]]
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_9030ba679545793b.png||data-xwiki-image-style-alignment="center" height="241" width="387" class="img-thumbnail"]]
--= Create communication with **Omron** PLC =
++**✎Note:** COM3 only available in PI8000/PI9000 series.
--== **CJ TCP FINS Ethemet  Protocol** ==
++== **MODBUS RTU Slave (All function)/(All function OneBaseAddress)** ==
--Supported device:CJ series
++Supported Series: MODBUS RTU CONTROLLER
--**1）HMI Settings**
++HMI works as MODBUS MASTER connecting with SLAVE.
--|=**Items**|=**Settings**|=**Note**
--|Protocol|OMRON CJ TCP FINS Ethemet|
--|Connection|Ethernet|
--|Port No.|9600|
--|Device No.|0|
--|HMI No.|0|(((
--
--)))
++The addresses in [All function] start from 0, while the addresses in [All function OneBaseAddress] start from 1 (offset 1).
--**2）Address List**
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_7236139c887defad.png||data-xwiki-image-style-alignment="center" height="571" width="544" class="img-thumbnail"]]
--|**Type**|**Device registers**|**HMI registers**|**Format**|**Range**|**Note**
--|Bit|CIO|CIO|CIO d|0~~99999|
--|Bit|W|W|W d|0~~99999|
--|Bit|D|D|D d|0~~99999|
--|Bit|H|H|H d|0~~99999|
--|Bit|A|A|A d|0~~99999|
--|Bit|T|T|T h|0~~99999|
--|Bit|CF|CF|CF d|0~~99999|
--|Bit|FF|FF|FF d|0~~99999|
--|Bit|C|C|C d|0~~99999|
--|Bit|EM0|EM0|EM0 d|0~~99999|
--|Bit|EM1|EM1|EM1 d|0~~99999|
--|Bit|EM2|EM2|EM2 d|0~~99999|
--|Bit|EM3|EM3|EM3 d|0~~99999|
--|Bit|EM4|EM4|EM4 d|0~~99999|
--|Bit|EM5|EM5|EM5 h|0~~99999|
--|Bit|EM6|EM6|EM6 d|0~~99999|
--|Bit|EM7|EM7|EM7 d|0~~99999|
--|Bit|EM8|EM8|EM8 d|0~~99999|
--|Bit|EM9|EM9|EM9 d|0~~99999|
--|Bit|EMA|EMA|EMA d|0~~99999|
--|Bit|EMB|EMB|EMB d|0~~99999|
--|Bit|EMC|EMC|EMC d|0~~99999|
--|Bit|Lamp|Lamp|Lamp d|0~~0|
--|Word|CIO|CIO|CIO d|0~~99999|
--|Word|W|W|W d|0~~99999|
--|Word|D|D|D d|0~~99999|
--|Word|H|H|H d|0~~99999|
--|Word|A|A|A d|0~~99999|
--|Word|T|T|T h|0~~99999|
--|Word|CF|CF|CF d|0~~99999|
--|Word|FF|FF|FF d|0~~99999|
--|Word|C|C|C d|0~~99999|
--|Word|EM0|EM0|EM0 d|0~~99999|
--|Word|EM1|EM1|EM1 d|0~~99999|
--|Word|EM2|EM2|EM2 d|0~~99999|
--|Word|EM3|EM3|EM3 d|0~~99999|
--|Word|EM4|EM4|EM4 d|0~~99999|
--|Word|EM5|EM5|EM5 h|0~~99999|
--|Word|EM6|EM6|EM6 d|0~~99999|
--|Word|EM7|EM7|EM7 d|0~~99999|
--|Word|EM8|EM8|EM8 d|0~~99999|
--|Word|EM9|EM9|EM9 d|0~~99999|
--|Word|EMA|EMA|EMA d|0~~99999|
--|Word|EMB|EMB|EMB d|0~~99999|
--|Word|EMC|EMC|EMC d|0~~99999|
--|Word|IR|IR|IR d|0~~99999|
--|Word|DR|DR|DR d|0~~99999|
--**3）Configure the communication protocol**
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_de80207f2b495c17.png||data-xwiki-image-style-alignment="center" height="462" width="600" class="img-thumbnail"]]
--[[image:image-20220830143348-1.png]]
--[[image:image-20220830143511-2.png]]
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_4e9e8eff81c7ff8b.png||data-xwiki-image-style-alignment="center" height="462" width="600" class="img-thumbnail"]]
++**HMI Settings**
++(% class="table-bordered" %)
++|**Items**|**Settings**|**Note**
++|Protocol|MODBUS RTU Slave (All function)/( All function OneBaseAddress)|
++|Connection|RS485/RS232|
++|Baud rate|2400~~187500|
++|Data bit|8|
++|Parity|Even/ Odd/ None|
++|Stop bit|1/2|
++|PLC station No.|0~~255|
--**4）Cable Wiring**
++**Address List**
--Pin Definition Diagram
++(% class="table-bordered" %)
++|**Type**|**Address Type**|**Function code & Description**
++|(% rowspan="11" %)Word|(% rowspan="3" %)3|04 (read input register: read current binary value in one or more input registers)
++|06 (write single register: write a binary value to a holding register)
++|10 (write values to multiple addresses )
++|(% rowspan="3" %)4|03 (read holding register: read current binary value in one or more holding registers)
++|06 (write single register: write a binary value to a holding register)
++|10 (write values to multiple addresses )
++|(% rowspan="3" %)W6|03 (read holding register: read current binary value in one or more holding registers)
++|06 (write single register: write a binary value to a holding register)
++|10 (write values to multiple addresses )
++|(% rowspan="2" %)W16|03 (read holding register: read current binary value in one or more holding registers)
++|10 (write values to multiple addresses )
++|(% rowspan="11" %)Bit|(% rowspan="3" %)0|01 (Read coil state)
++|05 (Force a single coil to force the on/off state of a logic coil)
++|0F (Write multiple bits, ie write continuously)
++|(% rowspan="3" %)1|02 (Read the input state)
++|05 (Force a single coil to force the on/off state of a logic coil)
++|0F (Write multiple bits)
++|(% rowspan="3" %)W5|01 (Read coil state to obtain the current state of a set of logic coils)
++|05 (Force a single coil to force the on/off state of a logic coil)
++|0F (Write multiple bits)
++|(% rowspan="2" %)W15|01 (Read coil state to obtain the current state of a set of logic coils)
++|0F (Write multiple bits)
--[[image:https://docs.we-con.com.cn/bin/download/PIStudio/12.PLC%20protocols/WebHome/12.PLC%20Protocol_html_2297240b57346b2a.png?width=401&height=170&rev=1.1||alt="12.PLC Protocol_html_2297240b57346b2a.png" height="170" width="401"]]
++**✎Note:**
--(% class="wikigeneratedid" %)
--==  ==
++* Modbus can also support getting bit from the word, which could access the address such as 100.1 and other formats.
++* The function codes sent out are the same as those that read and write words.
--== **EC55 Protocol** ==
++**Station number for more than one slaves**
++If there are more than one slaves connected to HMI, please set slave station number during editing address, as below shows.
++
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_31f028c6d80be344.png||data-xwiki-image-style-alignment="center" height="515" width="485" class="img-thumbnail"]]
++
++**Cable Wiring**
++
++* **RS485**
++
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_68dfb6d383f0edd9.png||data-xwiki-image-style-alignment="center" height="244" width="394" class="img-thumbnail"]]
++
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_cbeb90cb4faaa8bc.png||data-xwiki-image-style-alignment="center" height="244" width="394" class="img-thumbnail"]]
++
++* **RS232**
++
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_9030ba679545793b.png||data-xwiki-image-style-alignment="center" height="241" width="387" class="img-thumbnail"]]
++
++**✎Note:** COM3 only available in PI8000/PI9000 series.
++
++== **MODBUS TCP Slave (All function)** ==
++
++Supported series: MODBUS TCP controller
++
++HMI works as MODBUS TCP MASTER connecting with TCP SLAVE
++
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_8877cb7f39c2b607.png||data-xwiki-image-style-alignment="center" height="571" width="544" class="img-thumbnail"]]
++
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_e7e1f06f127a9175.png||data-xwiki-image-style-alignment="center" height="426" width="553" class="img-thumbnail"]]
++
++
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_60bbfe5de79417a6.png||data-xwiki-image-style-alignment="center" height="163" width="553" class="img-thumbnail"]]
++
++**HMI Setting**
++
++(% class="table-bordered" %)
++|**Items**|**Settings**|**Note**
++|Protocol|MODBUS TCP Slave (All function)|
++|Connection|Ethernet|
++|Port No.|502|
++|PLC station No.|1|
++
++**Address List**
++
++(% class="table-bordered" %)
++|**Type**|**Register**|**Function code & Description**
++|(% rowspan="11" %)Word|(% rowspan="3" %)3|04 (read input register: read current binary value in one or more input registers)
++|06 (write single register: write a binary value to a holding register)
++|10 (write values to multiple addresses )
++|(% rowspan="3" %)4|03 (read holding register: read current binary value in one or more holding registers)
++|06 (write single register: write a binary value to a holding register)
++|10 (write values to multiple addresses )
++|(% rowspan="3" %)W6|03 (read holding register: read current binary value in one or more holding registers)
++|06 (write single register: write a binary value to a holding register)
++|10 (write values to multiple addresses )
++|(% rowspan="2" %)W16|03 (read holding register: read current binary value in one or more holding registers)
++|10 (write values to multiple addresses )
++|(% rowspan="11" %)Bit|(% rowspan="3" %)0|01 (Read coil state)
++|05 (Force a single coil to force the on/off state of a logic coil)
++|0F (Write multiple bits, ie write continuously)
++|(% rowspan="3" %)1|02 (Read the input state)
++|05 (Force a single coil to force the on/off state of a logic coil)
++|0F (Write multiple bits)
++|(% rowspan="3" %)W5|01 (Read coil state to obtain the current state of a set of logic coils)
++|05 (Force a single coil to force the on/off state of a logic coil)
++|0F (Write multiple bits)
++|(% rowspan="2" %)W15|01 (Read coil state to obtain the current state of a set of logic coils)
++|0F (Write multiple bits)
++
++**Communication Settings**
++
++Enable HMI Ethernet in [Project Settings];
++
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_43b671f18153910d.png||data-xwiki-image-style-alignment="center" height="107" width="405" class="img-thumbnail"]]
++
++Set PLC IP in [Device IP] settings;
++
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_4bd3cc8348adecf8.png||data-xwiki-image-style-alignment="center" height="190" width="554" class="img-thumbnail"]]
++
++**Cable Wiring**
++
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_2297240b57346b2a.png||data-xwiki-image-style-alignment="center" height="170" width="401" class="img-thumbnail"]]
++
++= **Omron** =
++
++== **EC55** ==
++
  Supported device: EC55 temperature instrument
  **HMI Settings**
++(% class="table-bordered" %)
  |**Items**|**Settings**|**Note**
  |Protocol|Omron EC55|
  |Connection|RS485 (9600, 2, 7, EVEN)|
@@ -1825,6 +1825,7 @@
  **Address List**
++(% class="table-bordered" %)
  |**Type**|**Register**|**Device range**|**HMI range**|**Function**
  |(% rowspan="3" %)Double word|C0|0-13 (Hex)|0-19|Set read only parameter for area 0
  |C1|0-4D(Hex)|0-77|Set Read/Write parameter for area 0
@@ -1870,14 +1870,15 @@
  * Because of the mechanism problem, this protocol could not support CompoWay/F function that is read-write function of variables in protocol document.
  * When using double-word address, set the data format to 32 bits, otherwise the read/write function is unable.
  * Please set the communication delay time of 10ms in setting, to avoid that the instrument may not be able to communicate in a short time due to too fast data access and too much connection requests.
--* [[image:12.PLC Protocol_html_d428cad280fdefb3.png||height="276" width="347"]]Because of the particularity of the instrument, it is necessary to write the value of the address in the menu interface corresponding to the address, and to enter the menu where the address locates, so that the value could be written.
++* (% id="cke_bm_8690S" style="display:none" %)[[image:12.PLC Protocol_html_d428cad280fdefb3.png||height="276" width="347"]](%%)Because of the particularity of the instrument, it is necessary to write the value of the address in the menu interface corresponding to the address, and to enter the menu where the address locates, so that the value could be written.
--== **EtherNet/IP NX series Protocol** ==
++== EtherNet/IP NX series ==
  Supported series: Omron NX/NJ series
  **HMI Setting**
++(% class="table-bordered" %)
  |**Items**|**Settings**|**Note**
  |Protocol|Omron NX Ethernet/IP|
  |Connection|Ethernet|
@@ -1929,224 +1929,183 @@
  (% style="text-align:center" %)
  [[image:12.PLC Protocol_html_437cb087b36b5784.png||data-xwiki-image-style-alignment="center" height="330" width="600" class="img-thumbnail"]]
++
  (% style="text-align:center" %)
  [[image:12.PLC Protocol_html_60ef71528a99abf5.png||data-xwiki-image-style-alignment="center" height="188" width="554" class="img-thumbnail"]]
  **Cable Wiring**
--[[image:https://docs.we-con.com.cn/bin/download/PIStudio/12.PLC%20protocols/WebHome/12.PLC%20Protocol_html_2297240b57346b2a.png?width=401&height=170&rev=1.1||alt="12.PLC Protocol_html_2297240b57346b2a.png" height="170" width="401"]]
--
--= **MODBUS** =
--
--== **MODBUS RTU Master** ==
--
--Supported Series: MODBUS RTU CONTROLLER
--
--HMI works as MODBUS SLAVE connecting with MASTER
--
  (% style="text-align:center" %)
--[[image:12.PLC Protocol_html_44425b313b0a6b96.png||data-xwiki-image-style-alignment="center" height="571" width="544" class="img-thumbnail"]]
++[[image:12.PLC Protocol_html_2297240b57346b2a.png||data-xwiki-image-style-alignment="center" height="170" width="401" class="img-thumbnail"]]
++= **OpenCAN** =
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_b56b9da32c3caaa.png||data-xwiki-image-style-alignment="center" height="462" width="600" class="img-thumbnail"]]
++OpenCan is based on CAN2.0 standard; OpenCAN protocols that could be configured autonomously to accept and send frames.
++This protocol is only available in PI8000 series HMI.
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_67cd25458b9c72a6.png||data-xwiki-image-style-alignment="center" height="462" width="600" class="img-thumbnail"]]
--
  **HMI Settings**
  (% class="table-bordered" %)
  |**Items**|**Settings**|**Note**
--|Protocol|MODBUS RTU Master|
--|Connection|RS485/RS232|
--|Baud rate|2400~~187500|
--|Data bit|8|
--|Parity|Even/ Odd/ None|
--|Stop bit|1/2|
--|Station No.|0~~255|
++|Protocol|OPENCAN|
++|Connection|CAN port|
++|Baud rate|250000|
--**Address List**
++**CAN frame setting in HMI**
--(% class="table-bordered" %)
--|**Type**|**HMI address**|**MODBUS code**|**Range**
--|Bit|HDX3000.0~~HDX3499.15|0|0~~7999
--|Word|HDW3500~~HDW7999|4|0~~4499
++Click [OpenCAN setting] button in communication setting window;
--**Cable Wiring**
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_e866b9e56e19785d.png||data-xwiki-image-style-alignment="center" height="503" width="600" class="img-thumbnail"]]
--* **RS485**
++Click [Add] to create a new frame;
  (% style="text-align:center" %)
--[[image:12.PLC Protocol_html_68dfb6d383f0edd9.png||data-xwiki-image-style-alignment="center" height="244" width="394" class="img-thumbnail"]]
++[[image:12.PLC Protocol_html_3a6f4e2141763c8f.png||data-xwiki-image-style-alignment="center" height="315" width="600" class="img-thumbnail"]]
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_cbeb90cb4faaa8bc.png||data-xwiki-image-style-alignment="center" height="244" width="394" class="img-thumbnail"]]
++(% class="table-bordered" %)
++|**No**|**Items**|**Description**
++|1|Add|add a frame related to register address
++|2|Insert|Select the position where you want to insert a frame, and click [Insert frame] to add a new frame in front of the current frame position
++|3|Frame manager|This list shows some of the main parameters for each frame that the user adds
++|4|Modify|Modify the frames in frame management
++|5|Copy|Copy one frame to another
++|6|Delete|Remove the selected frames from the list by modifying the frames in frame management. If no frames are selected in the list, the first frame is deleted.
++|7|Empty|All frames in the list are cleared
++|8|Browse|Displays configuration files in XML format in IE
++|9|OK|Complete the configuration of the frame and exit
--* **RS232**
++Set CANBUS frame in setting windows
  (% style="text-align:center" %)
--[[image:12.PLC Protocol_html_9030ba679545793b.png||data-xwiki-image-style-alignment="center" height="241" width="387" class="img-thumbnail"]]
++[[image:12.PLC Protocol_html_7c83130820321ef.png||data-xwiki-image-style-alignment="center" height="507" width="600" class="img-thumbnail"]]
--**✎Note:** COM3 only available in PI8000/PI9000 series.
++(% class="table-bordered" %)
++|**No**|(% style="width:185px" %)**Items**|(% style="width:854px" %)**Description**
++|1|(% style="width:185px" %)ID|(% style="width:854px" %)Set the ID of a can frame in hexadecimal format;
++|2|(% style="width:185px" %)ID assign|(% style="width:854px" %)split the ID by PF, PS, and SA;
++|3|(% style="width:185px" %)Frame type|(% style="width:854px" %)Select Standard frame or Extended Frame;
++|4|(% style="width:185px" %)Frame format|(% style="width:854px" %)Select between data frame and remote Frame;
++|5|(% style="width:185px" %)Data|(% style="width:854px" %)Set the data part of CAN frame, with two Numbers representing a hexadecimal number and Spaces spaced; Maximum support of 8 bytes is defined according to CAN message;
++|6|(% style="width:185px" %)Use address|(% style="width:854px" %)(((
++Set the register address related to the CAN frame, which corresponds to the register address set on the main state one by one. The data obtained from the address is assigned continuously;
--== **MODBUS RTU Slave (All function)/(All function OneBaseAddress)** ==
++**Edit:** Set a bit or word address by its format;
--Supported Series: MODBUS RTU CONTROLLER
++**Option: **Set address options related to frame, enter “register address option” interface, specifically browse the following “register address option” interface;
++)))
++|(% rowspan="8" %)7|(% rowspan="8" style="width:185px" %)Data interactive configuration|(% style="width:854px" %)There are two interactive modes of the touch screen. One is that the touch screen actively sends frames, and the device receives and processes and feeds back. The other, on the contrary, passively receives frames from the device for processing and feedback;
++|(% style="width:854px" %)Send after receiving: if this item is selected, the interaction of the touch screen will act as a passive party, and the touch screen will receive the CAN frame first and send feedback. Unchecked items interact in the opposite way;
++|(% style="width:854px" %)Feedback mode: feedback mode includes no response, confirm response and data response;
++|(% style="width:854px" %)No response: the device or touch screen will not receive feedback;
++|(% style="width:854px" %)Confirm response: the device or the touch screen will receive feedback with confirmation, which could be used to compare the data parts. If this function is used, the 20 addresses before and after this address should not be used. All addresses of cata10-cata30 could not be used with the reply confirmation function of cata20;
++|(% style="width:854px" %)Data response: the device or touch screen will receive feedback with data, and the data to be separated from the feedback frame should be set to store in the register address;
++|(% style="width:854px" %)response ID: if the address wants to receive data on a frame with a different ID, set this, check "different from sender", and enter a different ID in the following input box. Without this setting, the screen will receive and process a frame with the same ID as the sender;
++|(% style="width:854px" %)Response timeout: sets whether the response frame timeout;
++|(% rowspan="3" %)8|(% rowspan="3" style="width:185px" %)Control address|(% style="width:854px" %)If ticked, enable sending when the value of the corresponding control bit number (address) is non-0.
++|(% style="width:854px" %)Control bit: CtrlBit register range 0~~255, if the control bit is ON, can instruction will run normally. Otherwise, it doesn't run;
++|(% style="width:854px" %)Manually send: a manually send tick indicates only one send;
++|9|(% style="width:185px" %)Flag configuration|(% style="width:854px" %)Communication control for each frame. Display OFF when communication is normal, and ON when communication is abnormal;
++|10|(% style="width:185px" %)Note|(% style="width:854px" %)Fill the text to explain the meaning of the frame;
++|11|(% style="width:185px" %)Data assign|(% style="width:854px" %)Preview the display in this table based on the address and the corresponding number of digits;
++|12|(% style="width:185px" %)Current operation display|(% style="width:854px" %)Display the description of current operation;
++|13|(% style="width:185px" %)Add|(% style="width:854px" %)Add a new frame;
++|14|(% style="width:185px" %)Save frame|(% style="width:854px" %)Save the configured frame format;
++|15|(% style="width:185px" %)Cancel|(% style="width:854px" %)Cancel the frame configuration;
--HMI works as MODBUS MASTER connecting with SLAVE.
++Set CAN address (Read or write operation);
--The addresses in [All function] start from 0, while the addresses in [All function OneBaseAddress] start from 1 (offset 1).
--
  (% style="text-align:center" %)
--[[image:12.PLC Protocol_html_7236139c887defad.png||data-xwiki-image-style-alignment="center" height="571" width="544" class="img-thumbnail"]]
++[[image:12.PLC Protocol_html_7e9f9b25eb6ae8ce.png||data-xwiki-image-style-alignment="center" height="446" width="600" class="img-thumbnail"]]
++(% class="table-bordered" %)
++|**No.**|(% style="width:207px" %)**Item**|(% style="width:829px" %)**Description**
++|1|(% style="width:207px" %)Current address|(% style="width:829px" %)Displays the register type and register address set by the user in the data access interface
++|(% rowspan="3" %)2|(% rowspan="3" style="width:207px" %)Trigger|(% style="width:829px" %)Two operations, "read" and "write," are based on on-screen registers
++|(% style="width:829px" %)If "read" is selected, the register address is reading device data in a manner of sending frames set by the user in a loop.
++|(% style="width:829px" %)If "write" is selected, the screen data of the register address will be written into the device. The writing mode is that the user makes a write operation on the screen, which will trigger the sending of a frame set by the user.
++|(% rowspan="5" %)3|(% rowspan="3" style="width:207px" %)Data operation|(% style="width:829px" %)The read and write operations in the trigger conditions are set accordingly.
++|(% style="width:829px" %)If the trigger condition is a read operation, this section needs to set the position and length of the data to be obtained at the current address in the frame.
++|(% style="width:829px" %)If the trigger condition is a writing operation, there are two situations:(((
++* If the "add writing data to the frame" option is not selected, the frame set by the user will be sent directly when the user writes on the screen.
++* Select the "add the written data to the frame" option, and when the user writes on the screen, the program will insert the data in the frame set by the user and send the written data to the frame set by the user according to the data insertion position and length set by the user.
++)))
++|(% rowspan="2" style="width:207px" %)Position and length input format|(% style="width:829px" %)If the register type is a bit address, the decimal point is required to represent the bits in the byte. For example, 1.1 represents the first bit of the first byte of 8 bytes in the data frame, and the length is in bits, and so on.
++|(% style="width:829px" %)If the register type is word address, the integer only needs to represent the byte, such as 1, which represents the first byte of 8-byte data in the data frame, and the unit of length is byte, and so on.
++|4|(% style="width:207px" %)Add|(% style="width:829px" %)Add current configuration
++|5|(% style="width:207px" %)Close|(% style="width:829px" %)Close the configuration window to exit
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_de80207f2b495c17.png||data-xwiki-image-style-alignment="center" height="462" width="600" class="img-thumbnail"]]
++**Multiple Packages Settings**
--
  (% style="text-align:center" %)
--[[image:12.PLC Protocol_html_4e9e8eff81c7ff8b.png||data-xwiki-image-style-alignment="center" height="462" width="600" class="img-thumbnail"]]
++[[image:12.PLC Protocol_html_107e0f6b1a90afff.png||data-xwiki-image-style-alignment="center" height="341" width="600" class="img-thumbnail"]]
--**HMI Settings**
++Check [Multiple packages supported] to open [Multiple package data] window, as below show.
--(% class="table-bordered" %)
--|**Items**|**Settings**|**Note**
--|Protocol|MODBUS RTU Slave (All function)/( All function OneBaseAddress)|
--|Connection|RS485/RS232|
--|Baud rate|2400~~187500|
--|Data bit|8|
--|Parity|Even/ Odd/ None|
--|Stop bit|1/2|
--|PLC station No.|0~~255|
++Select Multiple package type
--**Address List**
++* Not Multiple packages
++* J1939 Multiple packages
++* Customized Multiple packages
--(% class="table-bordered" %)
--|**Type**|**Address Type**|**Function code & Description**
--|(% rowspan="11" %)Word|(% rowspan="3" %)3|04 (read input register: read current binary value in one or more input registers)
--|06 (write single register: write a binary value to a holding register)
--|10 (write values to multiple addresses )
--|(% rowspan="3" %)4|03 (read holding register: read current binary value in one or more holding registers)
--|06 (write single register: write a binary value to a holding register)
--|10 (write values to multiple addresses )
--|(% rowspan="3" %)W6|03 (read holding register: read current binary value in one or more holding registers)
--|06 (write single register: write a binary value to a holding register)
--|10 (write values to multiple addresses )
--|(% rowspan="2" %)W16|03 (read holding register: read current binary value in one or more holding registers)
--|10 (write values to multiple addresses )
--|(% rowspan="11" %)Bit|(% rowspan="3" %)0|01 (Read coil state)
--|05 (Force a single coil to force the on/off state of a logic coil)
--|0F (Write multiple bits, ie write continuously)
--|(% rowspan="3" %)1|02 (Read the input state)
--|05 (Force a single coil to force the on/off state of a logic coil)
--|0F (Write multiple bits)
--|(% rowspan="3" %)W5|01 (Read coil state to obtain the current state of a set of logic coils)
--|05 (Force a single coil to force the on/off state of a logic coil)
--|0F (Write multiple bits)
--|(% rowspan="2" %)W15|01 (Read coil state to obtain the current state of a set of logic coils)
--|0F (Write multiple bits)
++Click [Edit Receive data] for [Receive] settings
--**✎Note:**
++* Start code+ Total length (J1939)
--* Modbus can also support getting bit from the word, which could access the address such as 100.1 and other formats.
--* The function codes sent out are the same as those that read and write words.
++(% style="text-align:center" %)
++[[image:12.PLC Protocol_html_3c360c6b5aca51bf.png||data-xwiki-image-style-alignment="center" height="340" width="426" class="img-thumbnail"]]
--**Station number for more than one slaves**
++As set above set, J1939 command is received by the HMI, only when its length is 25 bytes, and the start code is 0x57, 0x1B;
--If there are more than one slaves connected to HMI, please set slave station number during editing address, as below shows.
++* Start code + Data max length (J1939)
  (% style="text-align:center" %)
--[[image:12.PLC Protocol_html_31f028c6d80be344.png||data-xwiki-image-style-alignment="center" height="515" width="485" class="img-thumbnail"]]
++[[image:12.PLC Protocol_html_74496b2a68cfcdde.png||data-xwiki-image-style-alignment="center" height="340" width="426" class="img-thumbnail"]]
--**Cable Wiring**
++As set above set, J1939 command is received by the HMI, only when its length less than 50 bytes, and the start code is 0x57, 0x1B;
--* **RS485**
++* Data max length (J1939)
  (% style="text-align:center" %)
--[[image:12.PLC Protocol_html_68dfb6d383f0edd9.png||data-xwiki-image-style-alignment="center" height="244" width="394" class="img-thumbnail"]]
++[[image:12.PLC Protocol_html_98cea3e7cbd8f05d.png||data-xwiki-image-style-alignment="center" height="340" width="426" class="img-thumbnail"]]
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_cbeb90cb4faaa8bc.png||data-xwiki-image-style-alignment="center" height="244" width="394" class="img-thumbnail"]]
++As set above set, J1939 command is received by the HMI, only when its length less than 50 bytes.
--* **RS232**
++* Customized multiple package
  (% style="text-align:center" %)
--[[image:12.PLC Protocol_html_9030ba679545793b.png||data-xwiki-image-style-alignment="center" height="241" width="387" class="img-thumbnail"]]
++[[image:12.PLC Protocol_html_4635bbe4d7999db0.png||data-xwiki-image-style-alignment="center" height="395" width="367" class="img-thumbnail"]]
--**✎Note:** COM3 only available in PI8000/PI9000 series.
++As set above, It is received by the HMI, when the first frame starts with 0X57 0X1B, and the sum of the data lengths of multiple frames is equal to 79 bytes.
--== **MODBUS TCP Slave (All function)** ==
++Click [Edit Send data] for [Send] setting
--Supported series: MODBUS TCP controller
++* J1939
--HMI works as MODBUS TCP MASTER connecting with TCP SLAVE
--
  (% style="text-align:center" %)
--[[image:12.PLC Protocol_html_8877cb7f39c2b607.png||data-xwiki-image-style-alignment="center" height="571" width="544" class="img-thumbnail"]]
++[[image:12.PLC Protocol_html_a4769e44331ca732.png||data-xwiki-image-style-alignment="center" height="280" width="463" class="img-thumbnail"]]
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_e7e1f06f127a9175.png||data-xwiki-image-style-alignment="center" height="426" width="553" class="img-thumbnail"]]
++[Data] is all data to be sent.
++Since the frame of the J1939 frame contains the number of the data packet, so the data sent is: the first byte (number) + 7 bytes of data. If it is less than 7 bytes, it is sent in the actual number of bytes.
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_60bbfe5de79417a6.png||data-xwiki-image-style-alignment="center" height="163" width="553" class="img-thumbnail"]]
++* Customized multiple package
--**HMI Setting**
--
--(% class="table-bordered" %)
--|**Items**|**Settings**|**Note**
--|Protocol|MODBUS TCP Slave (All function)|
--|Connection|Ethernet|
--|Port No.|502|
--|PLC station No.|1|
--
--**Address List**
--
--(% class="table-bordered" %)
--|**Type**|**Register**|**Function code & Description**
--|(% rowspan="11" %)Word|(% rowspan="3" %)3|04 (read input register: read current binary value in one or more input registers)
--|06 (write single register: write a binary value to a holding register)
--|10 (write values to multiple addresses )
--|(% rowspan="3" %)4|03 (read holding register: read current binary value in one or more holding registers)
--|06 (write single register: write a binary value to a holding register)
--|10 (write values to multiple addresses )
--|(% rowspan="3" %)W6|03 (read holding register: read current binary value in one or more holding registers)
--|06 (write single register: write a binary value to a holding register)
--|10 (write values to multiple addresses )
--|(% rowspan="2" %)W16|03 (read holding register: read current binary value in one or more holding registers)
--|10 (write values to multiple addresses )
--|(% rowspan="11" %)Bit|(% rowspan="3" %)0|01 (Read coil state)
--|05 (Force a single coil to force the on/off state of a logic coil)
--|0F (Write multiple bits, ie write continuously)
--|(% rowspan="3" %)1|02 (Read the input state)
--|05 (Force a single coil to force the on/off state of a logic coil)
--|0F (Write multiple bits)
--|(% rowspan="3" %)W5|01 (Read coil state to obtain the current state of a set of logic coils)
--|05 (Force a single coil to force the on/off state of a logic coil)
--|0F (Write multiple bits)
--|(% rowspan="2" %)W15|01 (Read coil state to obtain the current state of a set of logic coils)
--|0F (Write multiple bits)
--
--**Communication Settings**
--
--Enable HMI Ethernet in [Project Settings];
--
  (% style="text-align:center" %)
--[[image:12.PLC Protocol_html_43b671f18153910d.png||data-xwiki-image-style-alignment="center" height="107" width="405" class="img-thumbnail"]]
++[[image:12.PLC Protocol_html_78546f765d6f3deb.png||data-xwiki-image-style-alignment="center" height="280" width="463"]]
--Set PLC IP in [Device IP] settings;
++[Data] is all data to be sent.
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_4bd3cc8348adecf8.png||data-xwiki-image-style-alignment="center" height="190" width="554" class="img-thumbnail"]]
++As set above, fist frame length is 2 bytes, and others are sent with 6 bytes for every frame, if the last frame is less than 6 bytes, send according to the actual length.
  **Cable Wiring**
  (% style="text-align:center" %)
--[[image:12.PLC Protocol_html_2297240b57346b2a.png||data-xwiki-image-style-alignment="center" height="170" width="401" class="img-thumbnail"]]
++[[image:12.PLC Protocol_html_fccede84efcbdc22.png||data-xwiki-image-style-alignment="center" height="111" width="391" class="img-thumbnail"]]
++**✎Note:** The address interval between each frame need to be more than a word address;
++
  = **SHIMADEN** =
  == **FP23** ==
@@ -2946,168 +2946,3 @@
  **Cable Wiring**
  [[image:https://docs.we-con.com.cn/bin/download/PIStudio/12.PLC%20protocols/WebHome/12.PLC%20Protocol_html_2297240b57346b2a.png?width=401&height=170&rev=1.1||alt="12.可编程逻辑控制器Protocol_html_2297240b57346b2a.png" height="170" width="401"]]
--
--
--= **OpenCAN** =
--
--OpenCan is based on CAN2.0 standard; OpenCAN protocols that could be configured autonomously to accept and send frames.
--
--This protocol is only available in PI8000 series HMI.
--
--**HMI Settings**
--
--|**Items**|**Settings**|**Note**
--|Protocol|OPENCAN|
--|Connection|CAN port|
--|Baud rate|250000|
--
--**CAN frame setting in HMI**
--
--Click [OpenCAN setting] button in communication setting window;
--
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_e866b9e56e19785d.png||data-xwiki-image-style-alignment="center" height="503" width="600" class="img-thumbnail"]]
--
--Click [Add] to create a new frame;
--
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_3a6f4e2141763c8f.png||data-xwiki-image-style-alignment="center" height="315" width="600" class="img-thumbnail"]]
--
--|**No**|**Items**|**Description**
--|1|Add|add a frame related to register address
--|2|Insert|Select the position where you want to insert a frame, and click [Insert frame] to add a new frame in front of the current frame position
--|3|Frame manager|This list shows some of the main parameters for each frame that the user adds
--|4|Modify|Modify the frames in frame management
--|5|Copy|Copy one frame to another
--|6|Delete|Remove the selected frames from the list by modifying the frames in frame management. If no frames are selected in the list, the first frame is deleted.
--|7|Empty|All frames in the list are cleared
--|8|Browse|Displays configuration files in XML format in IE
--|9|OK|Complete the configuration of the frame and exit
--
--Set CANBUS frame in setting windows
--
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_7c83130820321ef.png||data-xwiki-image-style-alignment="center" height="507" width="600" class="img-thumbnail"]]
--
--|**No**|**Items**|**Description**
--|1|ID|Set the ID of a can frame in hexadecimal format;
--|2|ID assign|split the ID by PF, PS, and SA;
--|3|Frame type|Select Standard frame or Extended Frame;
--|4|Frame format|Select between data frame and remote Frame;
--|5|Data|Set the data part of CAN frame, with two Numbers representing a hexadecimal number and Spaces spaced; Maximum support of 8 bytes is defined according to CAN message;
--|6|Use address|(((
--Set the register address related to the CAN frame, which corresponds to the register address set on the main state one by one. The data obtained from the address is assigned continuously;
--
--**Edit:** Set a bit or word address by its format;
--
--**Option: **Set address options related to frame, enter “register address option” interface, specifically browse the following “register address option” interface;
--)))
--|(% rowspan="8" %)7|(% rowspan="8" %)Data interactive configuration|There are two interactive modes of the touch screen. One is that the touch screen actively sends frames, and the device receives and processes and feeds back. The other, on the contrary, passively receives frames from the device for processing and feedback;
--|Send after receiving: if this item is selected, the interaction of the touch screen will act as a passive party, and the touch screen will receive the CAN frame first and send feedback. Unchecked items interact in the opposite way;
--|Feedback mode: feedback mode includes no response, confirm response and data response;
--|No response: the device or touch screen will not receive feedback;
--|Confirm response: the device or the touch screen will receive feedback with confirmation, which could be used to compare the data parts. If this function is used, the 20 addresses before and after this address should not be used. All addresses of cata10-cata30 could not be used with the reply confirmation function of cata20;
--|Data response: the device or touch screen will receive feedback with data, and the data to be separated from the feedback frame should be set to store in the register address;
--|response ID: if the address wants to receive data on a frame with a different ID, set this, check "different from sender", and enter a different ID in the following input box. Without this setting, the screen will receive and process a frame with the same ID as the sender;
--|Response timeout: sets whether the response frame timeout;
--|(% rowspan="3" %)8|(% rowspan="3" %)Control address|If ticked, enable sending when the value of the corresponding control bit number (address) is non-0.
--|Control bit: CtrlBit register range 0~~255, if the control bit is ON, can instruction will run normally. Otherwise, it doesn't run;
--|Manually send: a manually send tick indicates only one send;
--|9|Flag configuration|Communication control for each frame. Display OFF when communication is normal, and ON when communication is abnormal;
--|10|Note|Fill the text to explain the meaning of the frame;
--|11|Data assign|Preview the display in this table based on the address and the corresponding number of digits;
--|12|Current operation display|Display the description of current operation;
--|13|Add|Add a new frame;
--|14|Save frame|Save the configured frame format;
--|15|Cancel|Cancel the frame configuration;
--
--Set CAN address (Read or write operation);
--
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_7e9f9b25eb6ae8ce.png||data-xwiki-image-style-alignment="center" height="446" width="600" class="img-thumbnail"]]
--
--|**No.**|**Item**|**Description**
--|1|Current address|Displays the register type and register address set by the user in the data access interface
--|(% rowspan="3" %)2|(% rowspan="3" %)Trigger|Two operations, "read" and "write," are based on on-screen registers
--|If "read" is selected, the register address is reading device data in a manner of sending frames set by the user in a loop.
--|If "write" is selected, the screen data of the register address will be written into the device. The writing mode is that the user makes a write operation on the screen, which will trigger the sending of a frame set by the user.
--|(% rowspan="5" %)3|(% rowspan="3" %)Data operation|The read and write operations in the trigger conditions are set accordingly.
--|If the trigger condition is a read operation, this section needs to set the position and length of the data to be obtained at the current address in the frame.
--|If the trigger condition is a writing operation, there are two situations:(((
--* If the "add writing data to the frame" option is not selected, the frame set by the user will be sent directly when the user writes on the screen.
--* Select the "add the written data to the frame" option, and when the user writes on the screen, the program will insert the data in the frame set by the user and send the written data to the frame set by the user according to the data insertion position and length set by the user.
--)))
--|(% rowspan="2" %)Position and length input format|If the register type is a bit address, the decimal point is required to represent the bits in the byte. For example, 1.1 represents the first bit of the first byte of 8 bytes in the data frame, and the length is in bits, and so on.
--|If the register type is word address, the integer only needs to represent the byte, such as 1, which represents the first byte of 8-byte data in the data frame, and the unit of length is byte, and so on.
--|4|Add|Add current configuration
--|5|Close|Close the configuration window to exit
--
--**Multiple Packages Settings**
--
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_107e0f6b1a90afff.png||data-xwiki-image-style-alignment="center" height="341" width="600" class="img-thumbnail"]]
--
--Check [Multiple packages supported] to open [Multiple package data] window, as below show.
--
--Select Multiple package type
--
--* Not Multiple packages
--* J1939 Multiple packages
--* Customized Multiple packages
--
--Click [Edit Receive data] for [Receive] settings
--
--* Start code+ Total length (J1939)
--
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_3c360c6b5aca51bf.png||data-xwiki-image-style-alignment="center" height="340" width="426" class="img-thumbnail"]]
--
--As set above set, J1939 command is received by the HMI, only when its length is 25 bytes, and the start code is 0x57, 0x1B;
--
--* Start code + Data max length (J1939)
--
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_74496b2a68cfcdde.png||data-xwiki-image-style-alignment="center" height="340" width="426" class="img-thumbnail"]]
--
--As set above set, J1939 command is received by the HMI, only when its length less than 50 bytes, and the start code is 0x57, 0x1B;
--
--* Data max length (J1939)
--
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_98cea3e7cbd8f05d.png||data-xwiki-image-style-alignment="center" height="340" width="426" class="img-thumbnail"]]
--
--As set above set, J1939 command is received by the HMI, only when its length less than 50 bytes.
--
--* Customized multiple package
--
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_4635bbe4d7999db0.png||data-xwiki-image-style-alignment="center" height="395" width="367" class="img-thumbnail"]]
--
--As set above, It is received by the HMI, when the first frame starts with 0X57 0X1B, and the sum of the data lengths of multiple frames is equal to 79 bytes.
--
--Click [Edit Send data] for [Send] setting
--
--* J1939
--
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_a4769e44331ca732.png||data-xwiki-image-style-alignment="center" height="280" width="463" class="img-thumbnail"]]
--
--[Data] is all data to be sent.
--
--Since the frame of the J1939 frame contains the number of the data packet, so the data sent is: the first byte (number) + 7 bytes of data. If it is less than 7 bytes, it is sent in the actual number of bytes.
--
--* Customized multiple package
--
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_78546f765d6f3deb.png||data-xwiki-image-style-alignment="center" height="280" width="463"]]
--
--[Data] is all data to be sent.
--
--As set above, fist frame length is 2 bytes, and others are sent with 6 bytes for every frame, if the last frame is less than 6 bytes, send according to the actual length.
--
--**Cable Wiring**
--
--(% style="text-align:center" %)
--[[image:12.PLC Protocol_html_fccede84efcbdc22.png||data-xwiki-image-style-alignment="center" height="111" width="391" class="img-thumbnail"]]
--
--**✎Note:** The address interval between each frame need to be more than a word address;

image-20220830094600-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ben

Size

...	...	@@ -1,1 +1,0 @@
1		-40.4 KB

Content

image-20220830094657-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ben

Size

...	...	@@ -1,1 +1,0 @@
1		-53.4 KB

Content

image-20220830094929-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ben

Size

...	...	@@ -1,1 +1,0 @@
1		-90.4 KB

Content

image-20220830095131-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ben

Size

...	...	@@ -1,1 +1,0 @@
1		-25.7 KB

Content

image-20220830140537-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ben

Size

...	...	@@ -1,1 +1,0 @@
1		-35.2 KB

Content

image-20220830140629-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ben

Size

...	...	@@ -1,1 +1,0 @@
1		-48.4 KB

Content

image-20220830141138-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ben

Size

...	...	@@ -1,1 +1,0 @@
1		-82.9 KB

Content

image-20220830143348-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ben

Size

...	...	@@ -1,1 +1,0 @@
1		-35.9 KB

Content

image-20220830143511-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ben

Size

...	...	@@ -1,1 +1,0 @@
1		-46.3 KB

Content

Changes for page 12 PLC Protocol OLD

Summary

Details

Navigation

Table of Contents