Badger Meter Model 3700 Data Acquisition Server - Manual (Page 19)

19
6 No such device or address
9 Bad file descriptor
11 Resource temporarily unavailable
12 Cannot allocate memory
13 Permission denied
16 Device or resource busy
19 No such device
23 Too many open files in system
24 Too many open files
26 Text file busy
28 No space left on device
32 Broken pipe
101 Network is unreachable
110 Connection timed out
111 Connection refused
113 No route to host
129 Illegal function (function was not allowed by the slave
device)
130 Illegal data address (the data address is not allowed by
the slave device)
131 Illegal data value
132 Illegal response length
139 Device failed to respond (the Modbus device may be
off or disconnected)
160 Start log (entry in log file after Model 3700 starts up)
161 Stop log (entry in log file if Model 3700 is shut down
properly)
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
NULL. This preserves the column structure of the file, and allows
notation of invalid data. SqL databases often accept 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. At some point
in the future, the Model 3700 will be converted to report blank
fileds rather than “NULL” to make direct import of data from the
Model 3700 easier, as well as reduce the file size. Developers
intending to use data files from the Model 3700 should handle
both the word “NULL” as well as a blank column as indications
of an invalid data point.
Log Storage Capacity
The Model 3700 uses approximately 8 Mbytes 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.
We have measured a typical installation with 5 H8036 power
meters and 5 A8923 IO modules, and determined the system
will run for well over a hundred days with a 15 minute log cycle.
Changing the number of meters, the type of log data, or the
log cycle period will affect your results accordingly. Please
read Technote “TN-03” at www.dataindustrial.com for more
information about log file storage capacity.
When the Model 3700 storage area on the flash starts to run out
of space, the following action is taken:
• When the 8 Mbyte log file storage area is 75% full, the Model
3700 will immediately compress the log files and attempt to
upload the data to the BMO website or user specified site.
This action will not wait until the next scheduled upload
time.
• When the storage area is 95% full, the Model 3700 will
immediately attempt to upload the data, and if unsuccessful,
will purge the oldest (rotated) log data file.
Log files are deleted automatically if the Model 3700 has
successfully uploaded the log file to a database server using
the HTTP/Post protocol. If you do not configure the Model
3700 to automatically push the log files to your server, you must
manually delete them. To delete log files, refer to the FTP method
of downloading log files. One step detailed in the FTP section is
how to delete a log file from the Model 3700.
uploading data to the BMO Website
After the Model 3700 has been configured and has logged some
data, you will want to collect the data for analysis. There are
several ways of collecting the data from the Model 3700 including
the Building Manager Online service. Other methods are noted
in the data collection FAq. This section details configuring the
Model 3700 for use with the BMO service.
Step 1: First, use your browser to connect to the Model 3700.
Select the Modbus/Setup section from the menu on the left. In
the field titled Modbus Loop Name enter a name for this Model
3700 to uniquely identify it on the BMO website. Because the
BMO site can show multiple Model 3700 devices, it is important
to have a descriptive name in this field.
Step 2: Select the Log File Data, Setup/Upload menu option.
The following features are available:
• Model 3700 Serial Number: This is the serial number that
uniquely identifies this Model 3700. This number can not
be changed. When uploading data to the BMO website, this
serial number is used to identify the Model 3700 to the BMO
server.
• Scheduled upload time: This option allows you to control
when the Model 3700 will initiate the upload process. You
can select any hour of the day, and the Model 3700 will select
some time at random within that hour to start the upload.
The random feature allows multiple Model 3700 devices to
share a single dialup account or phone line by not starting
the dialout at the same time for all devices. If the Model
3700 is on a LAN connection (DSL, cable Modem, T1, etc)
an upload time of Hourly may be selected.
• Upload data on alarm status change will cause the Model
3700 to initiate the upload process if any point on any
modbus device enters or leaves an alarm state. This allows
the Model 3700 to send data when an alarm is detected, and
will upload that information to the BMO website in a timely
manner. The BMO website will then send email notifications