Wondering if I could get a detailed explanation into the following.
Using the EM4800 configuration tool I configure 15 minutes recording intervals (under intervals tab) to log Wh, VARh, VAh, demand.
To reduce the frequency of the "uploading data..." message that appears on the device display when the meter attempts to FTP is logs (This is rather annoying for field techs trying to see readings from the front panel) I set the "Reporting schdule" period to 60 minutes.
Energy interval data is logged every 15 minutes however cummulative energy is only logged every hour in this case. Setting the "Reporting schedule" to 15 minutes results in the cummulative energy values being logged now every 15minutes.
So the "Reporting Schedule" appears to be directly tied to the interval that cummulative energy values are logged at instead of the recording interval. Why???
This is on EM4800 running v1.46 firmware.
As I understand matters your reporting interval should be set at the max log interval.
If you set at 1 hour then you expect 4 values for 15 min interval and 1 value for 1 hr interval.
However, if you set the report interval less the the maximum log interval it causes the 1hr log to be reported at 15 min intervals.
Interval values apply an integrator reset at the end of each interval whereas accumulative integrator values never reset (except at max rollover) so in the end it does not matter.
In other ION meters which may have several logs I have found that if you set one log to log at say 30 min and the other to log at 5 min then when you look at the 30 min log from and each contains the same log variable then the PME database it will contain the 5 min values. This is a known issue within PME as it only stores the same data value for each variable once even though there are two physically separate logs on the meter? Weird but true
Values are not saved in the database based on the recorder it came from but against the source and measurement. This means any data logged from a particular register on the device, even if it comes from different recorders, will be saved against the same source and measurement. One side effect of this is if two recorders with the same input register but with different periods then the data will appear to be the superset of all the recorders.
Correct and which is a pain in the butt. The only way to get rid of this is to do SQL filtering via the Vista Query Wizard but which does not work as I have shown and raised elsewhere.
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!