MBTCP Client AOI on L33ER Compact Logix

frandESS

Lifetime Supporting Member
Join Date
Sep 2022
Location
Norway
Posts
14
Hi Friends,

I have an upcoming project were I need 20 pcs of ModBus TCP Clients / AOI. to control 10 devices

I use 20 transactions to control 10 devices, however some devices have SUNSPEC registers spread all over the address range, that we need to access - there for using 10 transaction / 2 MBTCP clients(AOI) for one unit to control.

Is this high number something that should be kept on an external HW instead, such as HMS or similar Modbus extender?

Reason for have it on PLS is that it goes way quicker to just fill in the correct transactions during commissioning (some trial and error)

Update of incoming values is ok to be set to 1000mS

PLC is L33ER Compact Logix, please feel free to share your knowledge on the topic.

Would like to hear comments here
 
While what you are doing maybe possible, I would use an hardware gateway.
Each AOI can handle up to 5 transactions. You can change this to 10, by changing the array size, but this will require to use 2000ms polling rate.

Using multiple AOIs for the same device maybe possible, but not all devices support multiple connections from the same IP address.

You can have up to 32 AOIs per controller, but most likely you will run out pf memory on this CompactLogix or will not have a room for any application code.
 
If I was doing that project, I would want to use a ProSoft MVI69E-MBTCP module. If you have trial and error to figure out some registers, the AOI would be good for that. Once that's figured out, I think it would be so much cleaner to have the module handle the communication and all you have to do in the PLC is unpack or repack the data for whatever you're doing with it.
 
Thank you so much for all valuable input.

I'm using an L36 on this project. I actually have some spare modules -Prosoft PLX31-EIP-MBTCP or HMS-EN2MB-2

I will dive into them and see how i can utilize the leftover modules :) Also ordered a few ProSoft MVI69E-MBTCP

Its always dirty using leftover parts

Thanks for all input regarding the AOI.It so simple to use - but eats some memory.
 
I haven't used that model, but the PLX31 should be about the same as using the in-chassis module. It looks like it does 10 clients, just enough for your application. Any expansion and you would have to double up devices under one client. The MVI69E does 20 clients.
 

Similar Topics

Hi, We have an application that has a device that goes through a reboot (appears un-graceful) What then happens is the MVI module appears to hang...
Replies
0
Views
75
Hi. I'm struggling over some basic stuff here. 41001 I is a 16 bits integer that I'm able to read with InTouch. What I need to do is to read...
Replies
1
Views
96
I'm trying to set up communications between a OI.MBTCP I/O server (for our historian) and a COMX510 that is on the same network , the COMX is also...
Replies
2
Views
654
Hi - I have a potential client who has a Wonderware / Aveva 2021 SCADA with the OI.MBTCP gateway installed. They want to get data out of their...
Replies
2
Views
827
I am configuring the Prosoft PLX32-EIP-MBTCP module for control Logix and DCS communication but the configurations are giving me an error. Anyone...
Replies
0
Views
1,021
Back
Top Bottom