K
We manufacture 3-phase revenue grade meters with embedded ethernet connectivity. Internal table structure is based on the ANSI C12.19 data tables, which is also an open protocol. We are planning to integrate the Modbus protocol.
Our first issue is that most of the information is read-only such as current billing values, last reset values, voltage, current and power factor by phase, load profile data etc. and the quantity of values far exceeds 125. Most are floating point.
So the question is how to do an optimal register mapping?
The second question is how to present the time series data such as load profile data. A single day's read is 96 interval readings with time stamp and status values for each interval. This is per channel. We are supporting 2 channels but can easily go to 5 or more.
Any direction and guidance would be appreciated.
Regards,
Keith Mistry
Our first issue is that most of the information is read-only such as current billing values, last reset values, voltage, current and power factor by phase, load profile data etc. and the quantity of values far exceeds 125. Most are floating point.
So the question is how to do an optimal register mapping?
The second question is how to present the time series data such as load profile data. A single day's read is 96 interval readings with time stamp and status values for each interval. This is per channel. We are supporting 2 channels but can easily go to 5 or more.
Any direction and guidance would be appreciated.
Regards,
Keith Mistry