[Getting know Modbus TCP mapping to remote I/O on Vision OPLC]

Hi, thanks for your reply.

Could you please lead to the help file or manual where this info is...  I think it is configured as a slave (server) on the TCP port (which I'm going to use), becuase there is a client somewhere in the network that works with it.  But the point is the mapping of remote i/o points to mb_tcp points  - is automatic ?  (i32 --> (matches)  MB Digital Input 0, I33 --> MB DI1...., O32 --> MB_Coil 0 etc...) OR  matching has always to be done in the project configuration.

[Getting know Modbus TCP mapping to remote I/O on Vision OPLC]

Good day everyone!

We're a SI (that has not much experince  with the Unitronics PLCs.. )  and  met Vision PLC HMI panel 1040 in the field.

We need to read some I/O points from the remote I/O modules, connected to the OPLC's i/o exp. port .  For integration with another system. 

From the FAQs I've read the module allows 4 connections, and Modbus TCP 502 port as well.  Please advise if there are some mapping  rules for remote i/o modules to the OPLC's Modbus TCP memory? 

Is this mapping is set in the project (that we don't have...) or there is some formula like,  X (pos_of_the_module)* mem_space_occupied_by_the_module + offset inside the module, to get the MB TCP address of the remote i/o point? 

Thanks for help in advance.