COM16. ModbusTCP Client via Allen-Bradley CompactLogix PLC

[@edsonchrispim4243]

Thank you very much ! Really well explained ! This video helped me a lot to solve my modbus doubts using compactlogix !

[@electricalautomation]

Glad it helped! Welcome!

[@patilvikranta]

Very well explained, thank you. Keep publishing similar knowledge base videos.

[@electricalautomation]

Thank you, I will be. Welcome more friends come to my channel!

[@kasperalexandersen4324]

Thank u for this, helped alot in a project im working on! I will follow u for future knowledge, i enjoyed ur work alot!

[@electricalautomation]

Welcome to view more videos in my channel! Glad they could be helpful!

[@bhagyodayasinghjadhav]

Very well explained, very nice video

[@electricalautomation]

Thanks my friend, hope it could help

[@chret27]

Why doesn’t the rung go green when I connect to the PLC?

[@fishpond01]

great video thank you

[@electricalautomation]

Glad you enjoyed it

[@ambekarsusheelkumar5671]

THIS VIDEO WAS VERY HELPFUL, BUT MY DOUBT IS IF WE READ 2 DEVICES LIKE 2 MFM BOTH HAS SAME HOLDING REGISTER ADDRESS THEN HOW DO WE READ? WILL THE DATA GETS OVERLAPPED. PLEASE SOLVE THIS.

[@electricalautomation]

If you have two or multiple devices. there would be two ways and they are very common. 1. using different instance and call the function block. 2. program by yourself and control the connection parameters and reading buffer by different target object.

[@renaco1145]

Hi, I want to write to the PLC that is not exactly in the same network IP. Is this still possible? then Ethernet connection between two different Ethernet switches makes sense or I need to do modify the communication network?

[@electricalautomation]

You need router for crossing different IP segments

[@karthikvhiremath1886]

Hi Thanks for this... Modbus TCP communication setup video. Can I able read REAL values.... Through this communication...

[@electricalautomation]

REAL has 4 bytes, so you can send a REAL as 2 words by using 2 registers

[@karthikvhiremath1886]

@@electricalautomation Thank you so much, I will try this

[@mekbots7607]

what about if you need to send custome tcp modbus msg?

[@muthiahgk3311]

Hi, I am getting sts_overlap and st_overload error and i'm not getting the data. What to do?

[@electricalautomation]

I think you instant block from each FB is overlap. Pls check your program.

[@rajkrishna336]

Very useful content- thanks. I’m trying to implement this on a 5380 CompactLogix to read the measurements from Yokogawa WT1800E power meter. I have a question. In order to read the power meter data, I need to combine set of Two INT to REAL data at the PLC. How can I do that? I prefer ST programming if possible. Thanks in advance for your help.

[@electricalautomation]

Not quite sure the "combine set of Two INT to REAL data ", how and which way you combine two INT to Real. If you have a real data 9876543.12, you can x1000, then convert 98765312 into DINT, then split DINT into two INT/WORD to transfer to PLC. Then PLC use the same backward way to restore the data to REAL.

[@rajkrishna336]

@@electricalautomation Thanks for the response. I did find a way to do this by using COP instruction. COP instruction will combine and convert two adjacent INT array to REAL array.

[@electricalautomation]

@@rajkrishna336 Glad to hear you found solution

[@yangrong7868]

thank you so much, make it very easy

[@electricalautomation]

Thanks for watching! Welcome!

[@acheydent1255]

Thanks, Verry good tutorial. One question : If the client want to communicate with 8 servers, is it mean we need to create 8 clients ? and Is it mean we need ( 93 + 7*20) Kb ? Best Regards

[@electricalautomation]

If answer shortly, I would say yes. But you also need to check the TCP connection resources from the specification of your CPU. 8 should be OK for the mainstream CompactLogix. An alternative way is that using one Client AOI FB. Then program the sequence loading the 8 of IPs and data into this AOI data buffer one by one. But I don't think someone would like to do this.

[@acheydent1255]

Thank a lot,

[@hichamcool76]

Thanks for this nice videos, I have a question for you : The data is limited at 1024 (coils 0 at 1023 coils....), if I want read data greater than 1024 (for example adresse registre 1030, 12680...) what can I do ?

[@electricalautomation]

Hi Bud, a quick answer, you may set the "start" from a higher start, then the total still the 1024. 1024 is the buffer length from the AOI function block but you can set the start modbus address. I haven't got a chance to test this, pls let me know if that works

[@hichamcool76]

Unfortunately, it doesn't work

[@electricalautomation]

@@hichamcool76 I recommend you contact AB support for your case.

[@flavioscarazzato6088]

Hi, very good tutorial! Can I do this Modbus TCP Client communication using the same physical port that already communicates with a 1734-AENT Ethernet/IP remote? Both the EtherNet/IP remote and the Modbus TCP equipment are in the same IP range.

[@electricalautomation]

Yes, I think you can, a physical port can be shared used.

[@javi787dreamliner]

Hi mate, How can i solved fault -8?

[@kebynmarkumanaramirez2920]

same man, you solved it? :(

[@electricalautomation]

Please check your instance (may be double instance, and also check if the port is blocked) In the manual "Modbus TCP Client - AOI based code for ControlLogix v 2.04.00" it explain the '-8' code, also you can find the more details in this link literature.rockwellautomation.com/idc/groups/literature/documents/at/enet-at002_-en-p.pdf#page=51

[@matheusviana4152]

Is it possible to comunicate with two modbus slave devices?

[@electricalautomation]

Yes

[@kebynmarkumanaramirez2920]

How can i solved fault -8?, nice video btw :)

[@electricalautomation]

Please check your instance (may be double instance, and also check if the port is blocked) In the manual "Modbus TCP Client - AOI based code for ControlLogix v 2.04.00" it explain the '-8' code, also you can find the more details in this link literature.rockwellautomation.com/idc/groups/literature/documents/at/enet-at002_-en-p.pdf#page=51