I understand that LabView is an NI (National Instrument) product, but I assume that you are trying to connect LabView to Allen-Bradley ControlLogix PLC vis CIP protocol? Ethernet/IP set is the correct way to connect to the Allen-Bradley ControlLogix PLC. Just have to ensure that the CIP path and IP address are correctly defined configured in the LabView driver.
You can a detail article from my engineering blog below (using Agcromag device) xybernetics.com/techtalk/allen-bradley-plc-connecting-to-ethernet-ip-devices/ What generic module are you trying to use?
@@RabiGurungXybernetics When adding a device to the Ethernet BUS in the RSLogix, you can choose "Generic Ethernet IP Module" within the list. My objective is actually establish communication between a B&R PLC and an Allen Bradley PLC.
You will have to write to the output tags as input tags are only for reading. In the video the output tags would be Agcormag.O.Data[0], Agcormag.O.Data[1], Agcormag.O.Data[2], etc. And the input tags would be Agcormag.I.Data[0], Agcormag.I.Data[1], Agcormag.I.Data[2], Agcormag.I.Data[3] and Agcormag.I.Data[4].
@@adnan.iq1 In ProSoft space, when you import the L5K file from ProSoft, it will create a few Controller Tags. The ones that you'd be interested would be MBTCP.Data.ReadData[XX] and MBTCP.Data.WriteData[XXX]. MBTCP.Data.ReadData would be for you to read data from the ProSoft module. MBTCP.Data.WriteData allows you to write to the ProSoft Module. You can check out my RUclips video about this. Link provided below. Look at the video at 21:38 where I talk about these tags (MBTCP.Data.ReadData[XX] and MBTCP.Data.WriteData[XXX]) ruclips.net/video/8CF6zAwPF88/видео.html I have more ProSoft video coming over the next few days. One of which I will be demonstrate how to diagnose your ProSoft communication (on a live system) which can be a real pain. I hope this help!
@@RabiGurungXybernetics Thanks a lot! If you are planning Prosoft anytime soon , a video on ETHERNET/IP to BACnet could be a life saver for me. I am aware of BACnet, MODBUS, KNX but ETHERNET/IP is new to me.
@@adnan.iq1 To be honest, I have not worked on EtherNet/IP to BACNet but based on my experience working with a few ProSoft models for both media and protocol conversion, I know that the Allen-Bradley tag prefixes are different from ProSoft models but the suffixes are always the same, except when you gravitate towards using Allen-Bradley's PLC5 or the older version of SLC when they still use address based tagging.
Thanks for this, great explanation!
Thanks for leaving a comment.
Sir is this the way allen Bradley use implicit message?
Is this method used capable to stablish connection between PLC and LabVIEW?
I understand that LabView is an NI (National Instrument) product, but I assume that you are trying to connect LabView to Allen-Bradley ControlLogix PLC vis CIP protocol? Ethernet/IP set is the correct way to connect to the Allen-Bradley ControlLogix PLC. Just have to ensure that the CIP path and IP address are correctly defined configured in the LabView driver.
Hi, just saw that for configuration you entered 1280 instead of 128 as recommended by manual but thanks for the video
Good catch! Thanks for pointing it out.
Could we use this generic module to establish connection between two Allen-Bradley PLCs?
You can a detail article from my engineering blog below (using Agcromag device)
xybernetics.com/techtalk/allen-bradley-plc-connecting-to-ethernet-ip-devices/
What generic module are you trying to use?
@@RabiGurungXybernetics When adding a device to the Ethernet BUS in the RSLogix, you can choose "Generic Ethernet IP Module" within the list. My objective is actually establish communication between a B&R PLC and an Allen Bradley PLC.
How to do the reverse? How to send PLC values to gateway?
You will have to write to the output tags as input tags are only for reading.
In the video the output tags would be Agcormag.O.Data[0], Agcormag.O.Data[1], Agcormag.O.Data[2], etc.
And the input tags would be Agcormag.I.Data[0], Agcormag.I.Data[1], Agcormag.I.Data[2], Agcormag.I.Data[3] and Agcormag.I.Data[4].
@@RabiGurungXybernetics Shall be same for Prosoft's ETHERNET/IP to BACnet gateway?
@@adnan.iq1 In ProSoft space, when you import the L5K file from ProSoft, it will create a few Controller Tags. The ones that you'd be interested would be MBTCP.Data.ReadData[XX] and MBTCP.Data.WriteData[XXX].
MBTCP.Data.ReadData would be for you to read data from the ProSoft module.
MBTCP.Data.WriteData allows you to write to the ProSoft Module.
You can check out my RUclips video about this. Link provided below.
Look at the video at 21:38 where I talk about these tags (MBTCP.Data.ReadData[XX] and MBTCP.Data.WriteData[XXX])
ruclips.net/video/8CF6zAwPF88/видео.html
I have more ProSoft video coming over the next few days. One of which I will be demonstrate how to diagnose your ProSoft communication (on a live system) which can be a real pain.
I hope this help!
@@RabiGurungXybernetics Thanks a lot! If you are planning Prosoft anytime soon , a video on ETHERNET/IP to BACnet could be a life saver for me. I am aware of BACnet, MODBUS, KNX but ETHERNET/IP is new to me.
@@adnan.iq1 To be honest, I have not worked on EtherNet/IP to BACNet but based on my experience working with a few ProSoft models for both media and protocol conversion, I know that the Allen-Bradley tag prefixes are different from ProSoft models but the suffixes are always the same, except when you gravitate towards using Allen-Bradley's PLC5 or the older version of SLC when they still use address based tagging.