We are planning to use a PLX32 EIP MBTCP with EIP Class 3 Server, the PLX32 gateway as a server and both PLC and DCS as clients. Would you have another video, or a tech note that we can reference to start with? Thank you!
This is so much better than the one on Prosofts own site. I struggled with the translation between the AOP and the Gateways internal mapping. Still find it funny that I have to map the registers to make the registers start at 40001 instaed os 42001. Why thats not the default still eludes me.
Very well explained, I just have one question The EIP Class 3 Clients : we need them for what and what if we dont want to do any changes on th EIP Controller program other than just activating the EIP interface
You definitely can. The PLX31 gateway has imbedded CIP and PCCC clients and you could use the gateway as your client and have the AB controller operating as a server. The tags only have to exist in the controller and if it's a CLX/CMX (using PCCC), the logic mapping has to be done.
so while doing class-3 communications we don,t need PLX31(hardware)....? and if i want to do both class-1 and class-3 communications at a time how to do it..? and you have any other video that explain about MBTCP Client with PLC....?
So, the the PLX31 is a protocol converter. This means if you need to change EIP to Modbus TCP, you will need the PLX3x hardware. The module can support concurrent connections on EIP, class 1 and/or class 3. You can do both at the same time, just configure the Class 1 module connections and write MSG commands in your logic for Class 3 communication. Feel free to email any questions to support.ap@prosoft-technology.com. We would be happy to help.
We are planning to use a PLX32 EIP MBTCP with EIP Class 3 Server, the PLX32 gateway as a server and both PLC and DCS as clients. Would you have another video, or a tech note that we can reference to start with? Thank you!
Excellent tutorial. It's been a while since I've used one of these and I was looking for a good review. This was spot on. Thanks for posting!
Thank u so much. Very much helpful. Keep uploading more topics. 👌🏻👌🏻
This is so much better than the one on Prosofts own site. I struggled with the translation between the AOP and the Gateways internal mapping. Still find it funny that I have to map the registers to make the registers start at 40001 instaed os 42001. Why thats not the default still eludes me.
Very good presentation, thanks so much.
Very well explained,
I just have one question
The EIP Class 3 Clients : we need them for what
and what if we dont want to do any changes on th EIP Controller program other than just activating the EIP interface
You definitely can. The PLX31 gateway has imbedded CIP and PCCC clients and you could use the gateway as your client and have the AB controller operating as a server. The tags only have to exist in the controller and if it's a CLX/CMX (using PCCC), the logic mapping has to be done.
Awesome!
so while doing class-3 communications we don,t need PLX31(hardware)....?
and if i want to do both class-1 and class-3 communications at a time how to do it..?
and you have any other video that explain about MBTCP Client with PLC....?
So, the the PLX31 is a protocol converter. This means if you need to change EIP to Modbus TCP, you will need the PLX3x hardware.
The module can support concurrent connections on EIP, class 1 and/or class 3. You can do both at the same time, just configure the Class 1 module connections and write MSG commands in your logic for Class 3 communication.
Feel free to email any questions to support.ap@prosoft-technology.com. We would be happy to help.
NIIIICEEEEE
Nice (Y)