Chipkin™
Modbus® RTU Data Client
User Manual
3381 Cambie Street, #211
© 2018 Chipkin Automation Systems
Vancouver, BC, Canada, V5Z 4R3
All rights reserved
1-866-383-1657
Chipkin.com
Page 21 of 55
DATA LOGGING CONFIGURATION
This section describes how to setup the data client for data logging.
First, for data logging to work, there must be data. The data logging uses its own data table. By this
point you have seen 2 other data tables:
1.
da_data
–
this is the default data table used to store raw data read from the Modbus devices.
2.
da_data_mod
–
this is the mods data table used to store data that has been modified.
This third data table, da_data_logging, is used to store the data that will be logged and archived to csv.
There are a few ways to get the data for logging into the da_data_logging. This will be covered in the
next few sections,
4.4.1
–
Logging Raw Data
and
4.4.2
–
Logging Modified Data
.
Following these sections will be
4.4.3
–
Configuring Data Logging
, which will describe how to setup
the data client for logging.
Logging Raw Data
What we mean by logging raw data is that we will directly log the data that has been polled from the
devices. This can be useful if all the Modbus registers being read only has 16-bit values. For example:
percentages or on/off status.
Normally, this data is stored in da_data. To change it to store the values in da_data_logging, follow
these steps:
First, return to the “System Page” by clicking on the “System” link as shown in the image below:
Figure 4.3-1 - System Page Link
Next, find the “Database” side bar menu and click either the “ModbusTCPClient_tasks” link or the
“ModbusRTU_tasks” link depending on which protocol you are using. See image below:
