Gateways and Energy Servers
Schneider Electric support forum to share knowledge about product selection, installation and troubleshooting for EcoStruxure Panel Server, PowerTag, Com'X, Link150…
User | Count |
---|---|
81 | |
46 | |
28 | |
28 |
Link copied. Please paste this link to share this article on your social media post.
Good Morning,
I have a site that is using several com’x 210s to count pulses from wages devices around the site, and we have noticed anomalies in the data.
The device is set up in PME to log every 15 minutes, but we keep getting gaps in the logged data, sometimes this gap is a couple of hours, other times it is nearly a whole day.
The opposite is also true, the logging may work for 3 hours, or a couple of days, but again this is completely random.
There is no sign of any comms issues, and as far as we can see there is nothing wrong with the device type.
We have also set a couple of the COM’x to send their on board logged data out as a csv file, and these appear to be full, with no gaps anywhere in the day.
Any idea what could be causing this, or any suggestions on how to fix it would be appreciated.
Thanks
Link copied. Please paste this link to share this article on your social media post.
Hi @Andy_Hubert ,
I confirm also these tests on my own system.
Logical Devices created from a Customized Com'X driver are working without any gaps compared to Logical Devices created from native Com'X Driver.
Example below. My Com'X and associated pulse meters are the sames, I only used 2 different driver versions.
@Anirban is this possible to consider an update of the Com'X Wage driver on PME ? The current settings for UpdateRates = 300 and Staleness Threshold = 120 are leading to have some gaps in the data.
@Andy_Hubert do not forget to put this thread as solved.
Thanks.
Romain
Link copied. Please paste this link to share this article on your social media post.
Good morning Andy,
Just a thought, its not the marked space ratio? ie the flow speeds up and the Com'X is not able to catch the pulse?
Just a though 🙂
KRF Mark
Link copied. Please paste this link to share this article on your social media post.
Hi @Andy_Hubert ,
What is your PME version ?
Are you using the default Com'X_WAGES driver for PME ? Or did you customize this driver ?
Did you create Logical Devices for your Pulse Meters ?
Com'X data logging + .csv publication and PME data logging are 2 different (and independent) processes. PME driver will only read some Modbus registers of the Com'X and log the values into its ION_Data database.
If the DI of the Com'X can detect your Pulse Meters and publish .csv, the issue seems more between Com'X and PME (communication ? ION Services ?).
Check with the Diagnostic Viewer if you can see some issues with the Log Inserter or other services.
Check also for some Warnings or Errors on the System Log (Management Console).
Regards,
Link copied. Please paste this link to share this article on your social media post.
Hi,
just to answer our questions
What is your PME version ? PME 2020
Are you using the default Com'X_WAGES driver for PME ? Or did you customize this driver ? we have tried both the default driver and custom versions, and both behave the same.
Did you create Logical Devices for your Pulse Meters ? Yes.
We have also checked the logs, and there are no events relating to either the loginserter or device comms.
Thanks
Andy
Link copied. Please paste this link to share this article on your social media post.
Hello @Andy_Hubert ,
I had a remote session with Michail this morning concerning your issue.
I updated some parameters in its ComX Custom Drivers according to https://www.se.com/my/en/faqs/FA210245/
I propose to let the system run for 48 hours and have an update of the situation just after.
Regards,
Romain
Link copied. Please paste this link to share this article on your social media post.
Hi,
I made this change to one of the device types on my site, and in 8 days since I did this there have been no gaps in the data.
Thanks for the resolution.
Andy
Link copied. Please paste this link to share this article on your social media post.
Hi @Andy_Hubert ,
I confirm also these tests on my own system.
Logical Devices created from a Customized Com'X driver are working without any gaps compared to Logical Devices created from native Com'X Driver.
Example below. My Com'X and associated pulse meters are the sames, I only used 2 different driver versions.
@Anirban is this possible to consider an update of the Com'X Wage driver on PME ? The current settings for UpdateRates = 300 and Staleness Threshold = 120 are leading to have some gaps in the data.
@Andy_Hubert do not forget to put this thread as solved.
Thanks.
Romain
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.