Com'X510 Loss Of Logging Data When Reconfiguring Logging Parameters

[KuanKhoon]

Good Morning to all,

After running the Com'X510 for a substantial period of time (>6 months), I decided to take the plunge to start increasing the number of logged parameters of a couple of energy meters as well as the PM8240 integrated onto the Com'X510 on my test setup integrated to my home electrical feeder. This is to push the

In the interest of saving readers for having to crawl through 80000+ lines of log file, I shall only show the "transition period" for which the some data truncation has occurred. The first data dump was done for the PM8000 logging on the Com'X510 on 31st December 2015,

Error	UTC Offset (minutes)	Local Time Stamp	Active energy delivered (Wh)	Reactive energy delivered (VArh)
0	480	31-10-15 8:00	1092903	8763
0	480	31-10-15 8:01	1092913	8763
0	480	31-10-15 8:02	1092915	8763

----- 86394 rows between the above and below -----   

0	480	30-12-15 7:57	2079830	18095
0	480	30-12-15 7:58	2079838	18095
0	480	30-12-15 7:59	2079848	18095

----- End of 31 December 2015 Dump out -----

I then stopped the logging on 4th January 2016 to add in a few more parameters to the device logging setting (namely active power, reactive power, current A THD, current B THD, current C THD) on top of the existing active energy delivered and reactive energy delivered. The logging was restarted at 4th January 2016 @ 1405hrs. Upon my 5th January 2016 dump out, this is what I saw,

Error	UTC Offset (minutes)	Local Time Stamp	Power Factor ()	Active Power (W)	Reactive Power (VAr)	Current A THD ()	Current B THD ()	Current C THD ()	Active energy delivered (Wh)	Reactive energy delivered (VArh)
0	480	04-01-16 14:05	0.78644675	431.3904114	-338.8045959	0.501566172	0.499643385	0.61425072	39718	204
0	480	04-01-16 14:10	0.789593041	435.6111755	-338.5344849	0.503642499	0.50883168	0.612590015	39755	204
0	480	04-01-16 14:15	0.792244196	439.9801636	-338.8825378	0.505291283	0.514780343	0.616975844	39791	204

---- Continued for another 213 entries -----

Note the fact that I did not do any further data dumping since 31st December 2015 to 4th January 2016, hence the data in that period is lost. This is something that the end users, commissioning engineers, etc. should know before hand before carrying out such an action. I have gone through the entire Com'X510 documentation, there are only general warnings on potential loss of data, but nothing specific to tell the user that they WILL lose data if they carry out certain actions / requests.

For those who noticed, I also changed the logging interval from 1 minute to 5 minutes, of which I reliably know will not cause loss of data as shown from the logging of my other devices with no logging parameters modified.

Conclusion from the above findings and observations,

1) Suggest that documentation team insert a warning clause in the Com'X 510 documentation at the location indicated by the red rectangle, that if the user were to change logging parameters of a device will previously logged data, the data will be lost.

2) Do we have a method to do a full dump out the Com'X510? Previously for the EGX300, we have the ability of using FTP into the device to dump out everything from the beginning of time. However for the Com'X510, there are no such facility to access previously logged data. The FTP upload only send incremental data without the ability to select sending the entire log file like that of the EGX300.

Best Regards,

Tan Kuan Khoon

Senior Product Specialist

Partner & Industry Business

[sesa72458]

I also would like to see a method to get the logged data from the Com'X510, one of my customers is concerned that if he loses the periodic published data, there will be no way for him to get another copy even when it exists in the 510.

Regards,

Steven Yan

[JamesJeanette · Accepted solution]

Hello KK/Steven.

I will pass along your feedback for consideration.  Thank you for sharing.

I do have good news to share in terms of how to export data from the Com'X.  We are adding this ability into the next release (currently planned for April time-frame).  You will have the ability to choose the device, topics, and date range to perform a "Historical Log Export" and be able to save this as a .CSV file to your PC.  This should address your request above.

Thanks,

James

Robert Jennings

Katie Cullen