40
14 LOG FILE DATA
138 Gateway Path Unavailable (the Modbus/TCP gateway may be misconfigured)
139 Device Failed to Respond (the Modbus device may be off or disconnected)
140 Received invalid Modbus data checksum
141 Received response from unexpected device
142 Received unsolicited query, assume another Modbus master device is present
143 Modbus device probe function received some good responses and some failures
160 Start log (Entry in log file after DAS starts up)
161 Stop log (Entry in log file if DAS is shut down properly)
162 System time changed, caused logger to restart logging for intervals
163 System auto-restart
164 Log entry corrupt
165 Modbus device restart detected
192 Modbus device does not match the device type in the configuration file
193 Modbus device’s serial number changed
(could be two devices with the same Modbus address)
Low/High Range Alarms:
This number is a hex representation showing which data points are out of range.
0x01 shows data point 1 in alarm state. 0x04 shows data point 3 in alarm state.
Data Points:
Data points are shown in the same order as the modbus device configuration display in the
modbus/device list page. Data is displayed in floating point form. When a specific point is unavailable
(4A4P-M broken wire alarm) or the point is not supported as part of the configuration (phase B current on a
single phase H8163 meter hookup) the point will be logged as blank. This preserves the column structure of
the file, and allows notation of invalid data. SQL databases often accept blank or NULL as a valid entry in a
data table to represent invalid data.
For data exported from the BMO website, the columns that are invalid (NULL) are reported as blank fields.
This makes it easier to import into MS Excel as blank cells. With the current firmware, the DAS will report
blank fileds rather than “NULL” to make direct import of data from the DAS easier, as well as reduce the file
size. Developers intending to use data files from the DAS should handle both the word “NULL” as well as a
blank column as indicatio ns of an invalid data point.
14.3 Log Storage Capacity
The DAS uses approximately 8 MB of flash disk for log file storage. As data from the Modbus meters is
collected, it is appended to log files on this flash chip. Once a day (at the first call out period for uploading
data) the log files are “rotated”. This action renames each log file and compresses the old file using gzip.
The net result is a smaller file for storage or modem/ethernet transfer.
Because the files are compressed, the actual size of the data on the flash chip will vary depending on the
data itself. For example, if a device is reporting 25KWh, it will use fewer bytes than a log entry
that has 9,999,999KWh.
The number of meters/sensors, type of log data, and log cycle frequency will all affect how long the DAS will
be able to store the data.
WEB
VERSION
