Skip to Content

Changes for page 1 Communication

Last modified by Hunter on 2024/07/01 10:54
From version 231.1
edited by Theodore Xu
on 2023/04/23 15:42
Change comment: There is no comment for this version
To version 216.2
edited by Hunter
on 2023/03/18 15:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.AiXia
1 +XWiki.Hunter
Content
... ... @@ -520,91 +520,8 @@
520 520  The above are all the steps for establishing Ethernet communication between Wecon V-box with CompactLogix L1769 PLC.
521 521  
522 522  
523 -= **Micro850_FreeTag Protocol（new）** =
523 += **Allen-Bradley Ethernet DF1** =
524 524  
525 -This example introduces the establishment of Ethernet communication between Wecon V-box and 2080-LC50-48QWB,Micro850. It is introduced through three parts: PLC software configuration, V-box software configuration.
526 -
527 -(% class="wikigeneratedid" id="HSoftwareconfigurationofPLC" %)
528 -(((
529 -**Software configuration of PLC**
530 -)))
531 -
532 -(% class="wikigeneratedid" id="HPLCprogrammingsoftware" %)
533 -(((
534 -**1）PLC programming software：Connected Components Workbench™**
535 -
536 -(% style="text-align:center" %)
537 -[[image:software.png]]
538 -
539 -**2）New PLC project**
540 -
541 -Click New Project and select the PLC model.
542 -
543 -(% style="text-align:center" %)
544 -[[image:project create.png]]
545 -
546 -**3）Set Ethernet parameters**
547 -
548 -Follow the steps below to configure Ethernet parameters
549 -
550 -PLC IP address：192.168.39.56
551 -
552 -default gateway：192.168.39.1
553 -
554 -subnet mask：255.255.255.0
555 -
556 -(% style="text-align:center" %)
557 -[[image:Ethernet.png]]
558 -
559 -**4）connect PLC**
560 -
561 -**When downloading the setting, need to change the status of the PLC to PRG**
562 -
563 -(% style="text-align:center" %)
564 -[[image:conne ab plc.png]]
565 -
566 -**V-box software configuration**
567 -
568 -**1）V-box programming software**
569 -
570 -(% style="text-align:center" %)
571 -[[image:v-net client vers.png]]
572 -
573 -**2）Set communication port parameters**
574 -
575 -In the device list on the left, find the Vbox that communicates with the L1769, click it and select configuration,communication port configuration in the main interface to add a communication protocol.
576 -
577 -(% style="text-align:center" %)
578 -[[image:V-NET_Client_t2Rg2wpSoY.png]]
579 -
580 -The communication port is selected as Ethernet, the device type is selected as Allen-Bradley, the protocol is Allen-BradleyMicro850_FreeTag EthemetIP, and the IP is the internal IP address of the L1769 PLC. The port number is 44818.
581 -
582 -(% style="text-align:center" %)
583 -[[image:V-NET_Client_communication.png]]
584 -
585 -Export variables from PLC, select CSV file, comma delimited. After adding the protocol Allen-BradleyMicro850_FreeTag, click[[image:https://docs.we-con.com.cn/bin/download/V-BOX/V-Net/Training/1%20Communication/WebHome/image-20220714143838-2.png?rev=1.1||alt="image-20220714143838-2.png"]]icon add label.
586 -
587 -(% style="text-align:center" %)
588 -[[image:export1.png]]
589 -
590 -(% style="text-align:center" %)
591 -[[image:CCW.Shell_E5Cwj4tUL3.png]]
592 -
593 -(% style="text-align:center" %)
594 -[[image:V-NET_Client_iKKKhcgxm1.png]]
595 -
596 -**3）Engineering production**
597 -
598 -According to your own needs, use the V-NET client software to edit the required data monitoring points.
599 -
600 -(% style="text-align:center" %)
601 -[[image:V-NET_Client_KOR0AHEA4M.png]]
602 -
603 -
604 -)))
605 -
606 -== **Ethernet DF1 Protocol** ==
607 -
608 608  [[download link>>https://ftp.we-con.com.cn/Download/WIKI/V-BOX/Demo/%E9%80%9A%E8%AE%AF%E6%A1%88%E4%BE%8B/Allen-Bradley%20Ethernet%20DF1.zip]]
609 609  
610 610  = Create communication with **Crouzet PLC** =
... ... @@ -611,56 +611,9 @@
611 611  
612 612  == **CROUZET M3 (FBD)** ==
613 613  
614 -Support Series: Crouzet Millenium 3 CD12/CB12
615 -
616 616  **1）V-BOX setting**
617 617  
618 -|=Item|=Recommended |=Note
619 -|=Protocol|CROUZET M3 (FBD)|
620 -|=Connection|RS232|
621 -|=Baud rate|115200|
622 -|=Stop bits|1|
623 -|=Data bits|7|
624 -|=Parity|EVEN|
625 625  
626 -**2）Address List**
627 -
628 -|=**Type**|=**Device registers**|=**Format**|=**Range**|=Note
629 -|(% rowspan="4" %)Bit|I|I DD|1~~99|Input
630 -|SLIBit|SLIBit DD.dd|1.0~~24.15|Serial Link Input
631 -|SLOBit|SLOBit DD.dd|25.0~~48.15|Serial Link Output(Read only)
632 -|State|State D|1~~1|PLC state(Read only)
633 -|(% rowspan="5" %)Word|AI|AI DD|1~~99|Analog Input
634 -|SLIn|SLIn DD|1~~24|Serial Link Input
635 -|SLOut|SLOut DD|25~~48|Serial Link Output(Read only)
636 -|Time|Time D|1~~6|(((
637 -Time1: Second
638 -
639 -Time2: Minute
640 -
641 -Time3: Hour
642 -
643 -Time4: Day
644 -
645 -Time5: Month
646 -
647 -Time6: Year
648 -)))
649 -|Order|Order D|1~~1|(((
650 -Running command(Write only)
651 -
652 -~=2: Run mode; =1: Stop mode;
653 -)))
654 -
655 -**3）Cable Wiring**
656 -
657 -(% style="text-align:center" %)
658 -[[image:CrouzetRS232 VBox.png]]
659 -
660 -{{info}}
661 -**✎Note: **As the wiring diagram indicated, this protocol requires the DB9 serial port pin 4. But pin 4 is undefined for all V-Box, so it need the user to solder a Pull-up resistor to make the pin 4 working. As for how to solder the resistor on the motherboard, please contact with Wecon technical support for the details.
662 -{{/info}}
663 -
664 664  = Create communication with **Siemens PLC** =
665 665  
666 666  == **S7-200 Smart Ethernet Protocol** ==
... ... @@ -2080,86 +2080,6 @@
2080 2080  (% style="text-align:center" %)
2081 2081  [[image:1624342015914-382.png||height="486" width="800" class="img-thumbnail"]]
2082 2082  
2083 -== **Communicate with Modbus Meter** ==
2084 -
2085 -The following example is using the Linfee meter LNF96EY to demonstrate how to set up the Modbus communication.
2086 -
2087 -~1. Wiring the RS485 cable first. Because the pin 58 is A, the pin 59 is B for meter. Here we use the COM1 to connect. So the diagram like follows:
2088 -
2089 -(% style="text-align:center" %)
2090 -[[image:LinfeeTerminalDiagram.png]]
2091 -
2092 -2. Check the specific Modbus parameter in the communication menu from LED display.
2093 -
2094 -So from the following pictures, we can know the Meter Address is 85, Baud rate is 9600, CRC None.
2095 -
2096 -{{info}}
2097 -**✎Note: **Meter address usually corresponding to the Modbus Slave Station No. on the Modbus communication.
2098 -{{/info}}
2099 -
2100 -(% style="text-align:center" %)
2101 -[[image:MeterModbusAllView.png]]
2102 -
2103 -(% class="wikigeneratedid" %)
2104 -3. Set up the communication in the Configuration tab.
2105 -
2106 -(% class="wikigeneratedid" %)
2107 -Select the protocol as **ModBus RTU Slave (All Function)**. And set the communication parameters like below.
2108 -
2109 -(% style="text-align:center" %)
2110 -[[image:VNETCommunicationtabmeter.png]]
2111 -
2112 -(% class="wikigeneratedid" %)
2113 -4. Create new real-time monitoring tag accroding to Modbus manual
2114 -
2115 -(% class="wikigeneratedid" %)
2116 -Enter the address we want to read from the meter. The following table is intercept part of the manual for Linfee Modbus manual.
2117 -
2118 -(% class="wikigeneratedid" %)
2119 -**0x03/0x04 command data register address**:
2120 -
2121 -(% style="width:1142.22px" %)
2122 -|(% style="display:none" %) |=(% colspan="2" rowspan="1" style="width: 165px;" %)Address(% style="display:none" %) |=Description|=Data Format|=(% style="width: 254px;" %)Data Length(Word)|=(% style="width: 282px;" %)Remark
2123 -|(%%)(% style="display:none" %) (%%) HEX|(% style="width:107px" %)DEC|(%%)(% style="display:none" %) (%%) |(% style="width:100px" %) |(%%)(% style="display:none" %) (%%) |(% style="width:318px" %)
2124 -|(% style="width:107px" %)0x00|(% style="width:100px" %)0|Reserved| | |(% style="width:318px" %)
2125 -|(% style="width:107px" %)0x02|(% style="width:100px" %)2|Reserved| | |(% style="width:318px" %)
2126 -|(% style="width:107px" %)0x04|(% style="width:100px" %)4|Reserved| | |(% style="width:318px" %)
2127 -|(% style="width:107px" %)0x06|(% style="width:100px" %)6|Ua|float|2|(% style="width:318px" %)Phase Voltage data, Unit V
2128 -|(% style="width:107px" %)0x08|(% style="width:100px" %)8|Ub|float|2|(% style="width:318px" %)Phase Voltage data, Unit V
2129 -|(% style="width:107px" %)0x0A|(% style="width:100px" %)10|Uc|float|2|(% style="width:318px" %)Phase Voltage data, Unit V
2130 -|(% style="width:107px" %)0x0C|(% style="width:100px" %)12|Uab|float|2|(% style="width:318px" %)Line Voltage data, Unit V
2131 -|(% style="width:107px" %)0x0E|(% style="width:100px" %)14|Ubc|float|2|(% style="width:318px" %)Line Voltage data, Unit V
2132 -|(% style="width:107px" %)0x10|(% style="width:100px" %)16|Uca|float|2|(% style="width:318px" %)Line Voltage data, Unit V
2133 -|(% style="width:107px" %)0x12|(% style="width:100px" %)18|Ia|float|2|(% style="width:318px" %)Phase Current data, Unit A
2134 -|(% style="width:107px" %)0x14|(% style="width:100px" %)20|Ib|float|2|(% style="width:318px" %)Phase Current data, Unit A
2135 -|(% style="width:107px" %)0x16|(% style="width:100px" %)22|Ic|float|2|(% style="width:318px" %)Phase Current data, Unit A
2136 -
2137 -{{info}}
2138 -**✎Note: **We usually use the Data Type 4 for read the Modbus registers(Function Code 03)
2139 -{{/info}}
2140 -
2141 -For example, here we want to read the Phase Voltage Ua (Modbus offset 0006), the Modbus register main No. requires input decimal number, and check whether the actual address has one address offset, so the tag configured like the following screenshot:
2142 -
2143 -(% style="text-align:center" %)
2144 -[[image:VNETModbusTagSettings.png]]
2145 -
2146 -(% style="text-align:center" %)
2147 -[[image:VNETModbusTagByteSettings.png]]
2148 -
2149 -{{info}}
2150 -**✎Note: **If the read value is incorrect, please check whether need to change the Byte order.
2151 -{{/info}}
2152 -
2153 -Set the Modbus Slave Station No.
2154 -
2155 -(% style="text-align:center" %)
2156 -[[image:ModbusStationSettings.png]]
2157 -
2158 -If the communication is setup successfully, the tag will show green light.
2159 -
2160 -(% style="text-align:center" %)
2161 -[[image:Monitoringtaggreenlight.png]]
2162 -
2163 2163  == **MODBUS RTU Master** ==
2164 2164  
2165 2165  Select the protocol "Modbus RTU Master",
1679563870401-671.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Hunter
Size
... ... @@ -1,1 +1,0 @@
1 -39.3 KB
Content
1682233464031-639.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -15.9 KB
Content
CCW.Shell_E5Cwj4tUL3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -27.1 KB
Content
CrouzetRS232 VBox.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Hunter
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
Ethernet.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -45.5 KB
Content
LinfeeTerminalDiagram.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Hunter
Size
... ... @@ -1,1 +1,0 @@
1 -8.6 KB
Content
MeterModbusAddr.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Hunter
Size
... ... @@ -1,1 +1,0 @@
1 -562.5 KB
Content
MeterModbusAllView.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Hunter
Size
... ... @@ -1,1 +1,0 @@
1 -1.6 MB
Content
MeterModbusBaud.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Hunter
Size
... ... @@ -1,1 +1,0 @@
1 -444.0 KB
Content
MeterModbusPara.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Hunter
Size
... ... @@ -1,1 +1,0 @@
1 -532.0 KB
Content
ModbusStationSettings.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Hunter
Size
... ... @@ -1,1 +1,0 @@
1 -35.8 KB
Content
Monitoringtaggreenlight.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Hunter
Size
... ... @@ -1,1 +1,0 @@
1 -7.5 KB
Content
V-NET_Client setting.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -41.9 KB
Content
V-NET_Client_ADD.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -51.4 KB
Content
V-NET_Client_KOR0AHEA4M.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -14.2 KB
Content
V-NET_Client_TIiAymnjkx.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -12.8 KB
Content
V-NET_Client_communication.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -25.5 KB
Content
V-NET_Client_iKKKhcgxm1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -35.9 KB
Content
V-NET_Client_t2Rg2wpSoY.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -53.7 KB
Content
VNETCommunicationtabmeter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Hunter
Size
... ... @@ -1,1 +1,0 @@
1 -31.0 KB
Content
VNETModbusTagByteSettings.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Hunter
Size
... ... @@ -1,1 +1,0 @@
1 -31.2 KB
Content
VNETModbusTagSettings.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Hunter
Size
... ... @@ -1,1 +1,0 @@
1 -35.7 KB
Content
conne ab plc.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -43.1 KB
Content
export.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -115.2 KB
Content
export1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -115.2 KB
Content
project create.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -65.5 KB
Content
software.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -25.8 KB
Content
v-net client vers.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.AiXia
Size
... ... @@ -1,1 +1,0 @@
1 -13.1 KB
Content