{"id":144,"date":"2020-10-07T16:43:30","date_gmt":"2020-10-07T14:43:30","guid":{"rendered":"http:\/\/disorder.dk\/wonderware\/?p=144"},"modified":"2020-10-07T16:43:30","modified_gmt":"2020-10-07T14:43:30","slug":"modbus-tcp-between-codesys-controllers","status":"publish","type":"post","link":"https:\/\/disorder.dk\/wonderware\/2020\/10\/07\/modbus-tcp-between-codesys-controllers\/","title":{"rendered":"MODBUS TCP between Codesys controllers"},"content":{"rendered":"\n

This is a example code of how to set up Master <– Slave communication between two Codesys Runtime controllers. This example was made in Codesys version 3.5.16.20 . This example is intentionally set up as one-way communication, so you have to repeat the Master\/Slave setup in both controllers or change the configuration to use R\/W registers, but that is out of the scope for this example.<\/p>\n\n\n\n

It is assumed that the reader of this article has a basic understanding of the MODBUS protocol. At least to understand the reasons for swapping around WORD data types and know about Big Ending, Little Endian, Most Significant Byte (MSB) and Least Significant Byte (LSB).<\/p>\n\n\n\n

Naming convention in this example should be tailored to your project, to make it more easily disgustingly as to which controllers you have data from and to.<\/p>\n\n\n\n

Network interface<\/h2>\n\n\n\n

Right-click on the Codesys controller and select “Add Device…” and add a Ethernet interface for the MODBUS protocol to work on.<\/p>\n\n\n\n

\"\"
Codesys Ethernet interface<\/figcaption><\/figure>\n\n\n\n

Right-click the Ethernet interface and select “Add Device…” and add a MODBUS TCP Master if you are on the Master PLC or jump a few steps down and add a MODBUS TCP Slave Device to the Slave PLC.<\/p>\n\n\n\n

\"\"
Codesys MODBUS TCP Master interface<\/figcaption><\/figure>\n\n\n\n

Right-click the MODBUS TCP Master interface and select “Add Device…” and add a MODBUS TCP Slave.<\/p>\n\n\n\n

\"\"
Codesys MODBUS TCP Slave interface<\/figcaption><\/figure>\n\n\n\n

Right-click the Ethernet interface and select “Add Device…” and add a MODBUS TCP Slave Device if you are on the Slave PLC.<\/p>\n\n\n\n

\"\"
Codesys MODBUS TCP Slave Device interface<\/figcaption><\/figure>\n\n\n\n

The Ethernet interface on both Codesys controllers is to be configured. In this example I am going to use the same network interface as the controllers connect to the SCADA platform on. I have selected the first Ethernet port of the controllers, X000, br0, Eth0 it can have many different names.<\/p>\n\n\n\n

\"\"
Selecting the network interface to use for the MODBUS TCP communication.<\/figcaption><\/figure>\n\n\n\n

On the Master PLC there is also a few settings for the MODBUS TCP Master and Slave interfaces. In this example I use a high timeout limit, adjust it to your application and most importantly, remember to tick on Auto-reconnect, you do not want to go online on each controller after a power-cut to re-enable MODBUS communication.<\/p>\n\n\n\n

\"\"
Codesys MODBUS TCP Master interface settings<\/figcaption><\/figure>\n\n\n\n

On the MODBUS TCP Slave interface we have to set up the IP-address of the Slave PLC, timeout and port. Port 502 is default.<\/p>\n\n\n\n

\"\"
Codesys MODBUS TCP Slave interface settings<\/figcaption><\/figure>\n\n\n\n

Programming<\/h2>\n\n\n\n

A new type is made. It is a Union type called “Modbus2WordReal” and it will be used for data type conversion between WORD and REAL, with the freedom to switch around on WORD[0] and WORD[1] to account for MSB\/LSB when communicating with various MODBUS devices. This new type is used in both Master and Slave PLC.<\/p>\n\n\n\n

\"\"
Codesys Union data type for WORD to REAL conversion and vice versa<\/figcaption><\/figure>\n\n\n\n

Some global variables are also needed in the GVL to make them accessible throughout the controllers programs. Only the From\/Receive variables are used in this example.<\/p>\n\n\n\n

\"\"
Master PLC GVL<\/figcaption><\/figure>\n\n\n\n

I was a little more structured in the Slave PLC and added some comment structure to make it easier to read the code.<\/p>\n\n\n\n

\"\"
Slave PLC GVL<\/figcaption><\/figure>\n\n\n\n

On the Master PLC the MODBUS TCP Slave has to be configured with the new variables in its Modbus Slave channel tab. Notice that the Channel names I gave them corresponds to the READ Offset, that is written out in hex, 16#0200 = 512 written in decimal in the editor when adding new channels. Read Input Registers \/Function Code 04) is used.<\/p>\n\n\n\n

\"\"
Codesys MODBUS TCP Slave configuration of the channels<\/figcaption><\/figure>\n\n\n\n

On the Slave PLC we have to set up the corresponding registers for them to match between Master and Slave. The MODBUS TCP Slave Device has settings for defining number of registers and offset on start addresses.<\/p>\n\n\n\n

\"\"
Codesys MODBUS TCP Slave Device interface configuration<\/figcaption><\/figure>\n\n\n\n

MODBUS TCP Slave Device I\/O Mapping shows why I named the variables as I did, to match the registers used.<\/p>\n\n\n\n

\"\"
Codesys MODBUS TCP Slave Device I\/O Mapping<\/figcaption><\/figure>\n\n\n\n

The program of the Master PLC is a simple WORD_AS_BIT conversion from the received register 512 and it is converted into 16 single bits that can be used in your other programs in the controller. For register 513+514, notice how the WORD conversion to REAL and possibility of swapping the two WORD around is done with the Union data type. Here it is just a local instance of the PRG_MODBUS_TCP program as I would add the REAL variable on the output of the MOVE block.<\/p>\n\n\n\n

\"\"
Master PLC MODBUS receiving program and Union data type conversion<\/figcaption><\/figure>\n\n\n\n

The program of the Slave PLC is a simple BIT_AS_WORD conversion from the 16 single bits that can be used in your other programs in the controller to be transmitted to register 512. For register 513+514, notice how the possibility of swapping the two WORD around is done with the Union data type. Here it is just a local instance of the PRG_MODBUS_TCP program.<\/p>\n\n\n\n

\"\"
Slave PLC MODBUS transmitting program and Union data type conversion<\/figcaption><\/figure>\n\n\n\n

Test of MODBUS TCP communication<\/h2>\n\n\n\n

A small test program was written in the Slave PLC PRG_MODBUS_TCP program to generate a alternating switching bit and a analog value that kept changing, here with a triangle waveform 0 to 1000 over 60 seconds. Notice how the REAL value is written into the Union using the .AsReal attribute to write into the correct part of it.<\/p>\n\n\n\n

\"\"
Codesys test program generating values to be transmitter from the slave<\/figcaption><\/figure>\n\n\n\n

Looking at the transmitting program, it can be seen that the REAL value is now represented as two WORD that is transmitted in each their register.<\/p>\n\n\n\n

\"\"
Codesys MODBUS TCP Slave PLC program<\/figcaption><\/figure>\n\n\n\n

The result of our hard work is now seen in the Master PLC that receives the data perfectly fine and the transmitted WORD registers is translated into BIT and REAL values to be used.<\/p>\n\n\n\n

\"\"
Codesys MODBUS TCP Master PLC program<\/figcaption><\/figure>\n\n\n\n

MODBUS TCP communication is simple and easy to configure in Codesys Development System V3.<\/p>\n","protected":false},"excerpt":{"rendered":"

This is a example code of how to set up Master <– Slave communication between two Codesys Runtime controllers. This example was made in Codesys version 3.5.16.20 . This example is intentionally set up as one-way communication, so you have to repeat the Master\/Slave setup in both controllers or change the configuration to use R\/W<\/p>\n

Continue Reading “MODBUS TCP between Codesys controllers”<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":165,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[37],"tags":[34,45,46,44,40,42,43,41],"class_list":["post-144","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-codesys","tag-codesys","tag-communication","tag-ethernet","tag-ip","tag-modbus","tag-modbus-tcp","tag-network","tag-tcp"],"jetpack_featured_media_url":"https:\/\/disorder.dk\/wonderware\/wp-content\/uploads\/2020\/10\/codesys_modbus.jpg","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/disorder.dk\/wonderware\/wp-json\/wp\/v2\/posts\/144","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/disorder.dk\/wonderware\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/disorder.dk\/wonderware\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/disorder.dk\/wonderware\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/disorder.dk\/wonderware\/wp-json\/wp\/v2\/comments?post=144"}],"version-history":[{"count":3,"href":"https:\/\/disorder.dk\/wonderware\/wp-json\/wp\/v2\/posts\/144\/revisions"}],"predecessor-version":[{"id":166,"href":"https:\/\/disorder.dk\/wonderware\/wp-json\/wp\/v2\/posts\/144\/revisions\/166"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/disorder.dk\/wonderware\/wp-json\/wp\/v2\/media\/165"}],"wp:attachment":[{"href":"https:\/\/disorder.dk\/wonderware\/wp-json\/wp\/v2\/media?parent=144"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/disorder.dk\/wonderware\/wp-json\/wp\/v2\/categories?post=144"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/disorder.dk\/wonderware\/wp-json\/wp\/v2\/tags?post=144"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}