Com'X 510 Internal IO module Interface using Modbus

[mykel]

Hi All,

Need your advise on how to read data connected to Com'X local AI/DI port using modbus TCP and to be Interfaced to EBO.

I read the user manual and it says that in order to access the internal AI/DI i need to use slave ID 255, but when trying it with EBO it is not possible to input 255.

Please refer to link User manual page 49.

https://www1.lk.dk/flipbooks/ComX%20510_User_Manual/content/ComX%20510%20User%20Manual.pdf 

Thank you.

[Bojan]

Hi, do you plan PME2020 integration with EBO. as it can read slave ID 255?

[mykel]

Hi Bojan,

we will only use the existing Com'X as a gateway to read 2 analog points and will not use PME.

[Romain_Polette]

Hello @mykel , 

This question seems for an EBO Expert.

@Benji is there a way to connect a Com'X510 to an Enterprise Server and read the Com'X Internal Registers through Slave ID 255 ?

Thanks.

[Benji]

Sure, you should be able to. Just add a TCP server device.

[mykel]

Hi Benji,

As i mentioned in my description, we did test it and there seems to be a warning when inputting 255 as Device ID and will not let us save it. Doing trial and error we found out that 248 will let us save the changes but will revert to INVALID after.

Please see screenshots below.

[mykel]

Hi Romain,

If EBO has a restriction with 255 ID, is it possible to change the Local Device ID of Com'X instead?

Trying to look for it in the settings but failed to locate.

Kindly advice.

Thank you.

[Randi_Dolan]

Hi,

The device ID of the Com'X is fixed at 255.  This is because it's a gateway and the Modbus standard states that it's ID is 255.

Randi

[mykel]

Hi @Benji,

If the slave ID is fix on 255 for Com'X, do we have a way to allow EBO to read this data?

Kindly advice.

[mykel]

Hi @Randi_Dolan ,

Thank you for confirming.