Com 'X510 Comms Issue

[sesa195147_brid]

Hi all

I am wondering if someone can assist with an issue between a Com 'X510 and the on site LM50 water pulse meter.

The Com'X510 is connected via Ethernet to 2 x LM50 Pulse Meter Centraliser units, these are 3rd party devices and as a result do not have a predefined template within the Com'X510 Device Library. We have tested a template created prior to the site visit but this unfortunately did not work. We simplified and recreated a new custom template but this also failed to read the Modbus TCP registers of the LM50. 　

We turned to the SE Buildings Automation Server (as Buildings are assisting with commissioning) and with this we were able to communicate with the LM50 and read the data we were expecting almost immediately. From here we looked at the the network diagnostics page where we found the Com'X510 identified that there was some kind of generic error or out-of-service message with the communication between the Com'X510 and the LM50s and as a result refused to read the data automatically. We briefly managed to resolve this error and data was read automatically but it disconnected shortly thereafter and we received a "Timed Out" message from within the Com'X510's web interface. We do not know how we managed to get this temporarily working, any attempts to replicate our success was met with the same error and failure to communicate. 　

At this stage we realised that through the diagnostics web page of the Com'X510 we were able to successfully poll a bank of the LM50s memory registers and read data, we compared this to what we saw from the SE Buildings Automation Server and we did indeed see the same data and therefore verified that the Com'X510 can indeed read the data from the LM50s over ethernet but due to this "error" it saw was unwilling to automatically poll the bank of registers defined in out template. In addition to this we swapped the Com'X510 with another and verified this issue persisted, once again pointing to firmware or configuration and not faulty hardware.　

We systematically worked through every ethernet configuration option we could find in both the Com'X510 and LM50s to try and solve the issue but we were unable to do so, we even temporarily swapped the ethernet switch on site but no success. Given that this LM50 was apparently the most critical device for the end customers billing needs, we configured the Buildings Automation Server to take a snap-shot of the data within the devices that can be compared to another in the future to define the individual usage of each apartment. 　

We decided at this stage that we were not going to figure the LM50s out and to move on to the final issue of the Gas Meter pulse input. This appeared to be simple enough as I had configured a custom dry contact input in the past in bench testing. However, when creating a dry contact the unit presented us with errors stating that it was unable to do so, this persisted through hard resets of the hardware. We eventually managed to create a KYZ type of pulse meter which was not a perfect fit but could suit our purposes. The Com'X510 then flagged this dry contact with a comms error as it did with the LM50s. I'm not sure how you can have a communications issue with an ON/OFF signal but the unit found a way. 　

It is very much worth nothing that this comms error was flagged on every single custom device we added to the library. We finally created a contactor input which is the simplest device type possible on the Com'X and a comms error was flagged, even though we were able to use a wire link to close the circuit simulating the contactor's auxiliary and see the Com'X510s web interface reflect this change in real-time.　

For us on site this really cemented the theory that there is something not 100% with the Com'X510 and its ability to use devices from the custom library. Any assistance with this would be appreciated.

Thanks

Marcus

[Anonymous user]

Hi Marcus,

I'm sorry you ran into so much trouble while attempting to commission your site. I would be happy to help you get things working properly. Do you have a way for us to access a LM50 remotely to help define the custom model?

Thank you,

Colton Peltier