Com'X 510 - Native Driver Editing/Communication Issue

[engenharia_memt]

Hello, 

I have two questions about Com'x 510 energy server: 

1 - Is it possible to edit a native driver for a downstream device in Com'x 510? I mean,  without creating a custom device, I would like to apply a scale in the energy modbus register (currently read in Wh for BCPM circuit channels, I wish it to be read in kWh) in the original device driver and keep it working properly after this change.  

2 - Is there any known issue related to the way that Com'x manages the packets which it reads from downstream devices (through modbus/TCP or modbus/RTU)? I can explain it by telling you two specific cases that I noticed in two different customers.

i - The first customer has some third party devices (ABB REF 615) that are being read by Com'x 210 via modbus/TCP in one ethernet port. In this case, the data logging is activated in Com'x because we intend to give more reliability to the collected data once the connected devices are physically close to the Com'x. The CSV files are exported to the server and later PME get them to its database via ETL. The customer requested us to available real time readings in PME because of operational reasons. But, when we do this, Com'x starts to work strangely and lose rows of data in the CSV files (the values come as null). 

ii - The second customer has Com'x 510 and BCPM A as downstream devices connected in RS485 port. The same way that reported above, the data logging is configured in the Com'x and also there are real time requests coming from PME. However, many times the .CSV files come with missing data.

I would be very greatful if anybody could give me some insights on where could be the problem in these cases or wheather there is a workaround for those. 

Thanks in advance! 

[Randi_Dolan]

Hello,

To answer your first question, no, you cannot modify the built in driver for a device without creating a custom model.  The Com'X manages all data in base SI units.  This is why the Energy readings are in Wh and not kWh.

In response to your second question, it was recently brought to our attention that if a data value is reported as "NaN" or as an invalid value from the device, this will invalidate the entire entry, as indicated with error code 19.  This issue will be resolved with the next firmware release.  If you are experiencing a different issue, you should contact the Customer Care Center with assistance in troubleshooting the issue you are seeing.

Regards,

Randi

[engenharia_memt]

Hello, 

Thank you for your reply! 

What would be your suggestion to have all the meters in the same base unit? I know that there aren't too many options, but using ETL to divide the energy readings by 1000 before loading them into DB would be a good path way? 

About the second problem, we are performing some more tests in order to verify if our case matches the error and characteristics that you mentioned. 

We keep you informed in this post. 

Thanks!

[Randi_Dolan]

Hi,

If you are using the Com'x built-in device models, they should all be in the same units.  However, if you are using a custom model, you will have to change the scaling in the custom model.

Please let me know if you need further assistance.

Randi