Easergy T300 - Modbus TCP connection to Comx510?

[Anonymous user]

I would like to ask about the Modbus TCP configuration on Easergy Builder.

Currently i am connecting the CL110 sensor to ComX510 and use modbus TCP to send out the temperature value of CL110 to Easergy Builder T300 HU250. 

Easergy Builder T300 modbus TCP configuration

I can get the value through the third party tools modbus poll which means that i have no issue of broadcasting the valve from ComX510 (attached photo).

On Easergy Builder side,  i had created the Modbus TCP channel and added the modbus registers address, and setup the details in coreDB (IR:4000:F), but i still cannot show the valve on the web console page.

And i have found that there is even no traffic can be showed on the 'Traces" page.

would like to ask is there any steps that i may missed.

Many thanks for your help.

Best Regards,

Tony Leung

Hong Kong - Schneider

[JYPOC]

Hello Tony,

1. Since this is technical support stuff, did you reach out to them (SM EUR Global-NA-Tech-Support (global-na-tech-support@schneider-electric.com)? If not, please do so.

2. From my side, is there a reason why you cannot connect the CL110/TH110 directly to Easergy T300 using the new option called ZigBee module for Easergy HU250? Easergy T300 firmware version 2.7 supports that module and the configuration embeds all the data provided by CL110/TH110.

Take care! 

[Anonymous user]

Hi Jean Yves, thanks for your reply, we are actually have difficulties on connecting ANY "Modbus TCP" device to the HU250, not just the comx510.

We had also tried to connect the PM8210 power meter to the HU250 on easergy builder with Modbus TCP, but we also failed,

so we think that we did something wrong on the configuration on easergy builder instead of hardware issue.

Take care and thanks for your kind assistance.

Tony Leung

[Anonymous user · Accepted solution]

Problem has been solved.

[Pete_Vivers]

Hi Tony,

It is good news that the problem has been solved. Would you care to share the solution with the community so they can all benefit from your experience ?

[Christian_Luyo]

Hello @Anonymous user  could you please share the solution for the modbus TCP matter? I am currently having a project to integrate a ZoloGate through Modbus TCP with HU250.

[Anonymous user]

Hello Pete, it should work perfectly if you follow my screen shoot in my question. 

just to ensure that you type the IR:4000:F under the coreDB, if your data is "status" type data then put it under status page, if it is "analog" type data sheet then you put it under the analog page data sheet.

guys feel free to give me an email see if I can help with it regarding this modbus TCP connection with HU250

tony.leung@non.se.com

cheers

Tony Leung

[TomBerry]

Just to expand on Tony's answer

Internally CoreDB "Status" variables store the data as integers

CoreDB "Analog: variables store the data as 64bit floating point 

The Modbus mapping is defined with an optional suffix that indicates the data format.

The default of no suffix means the data is 16 bit integer, so it can be stored as either a Status or an Analog.  

Suffix :F means the data will be retrieved from 2 consecutive registers, and stored using a 32 bit floating point format, so it should be stored as an Analog variable.