LMI Technologies Gocator 1100 Series, Руководство пользователя

Страница: 158 / 250

Protocols • 158 Gocator 1100 & 1300 Series
Registers
Modbus registers are 16 bits wide and are either control registers or output registers.
Control registers are used to control the sensor states (e.g. start, stop or calibrate a sensor), and the
output registers report the sensor states, stamps, and measurement values and decisions. The user
can read multiple output registers using a single Read Holding Registers or a single Read Input Registers
command. Likewise, the user can control the state of the sensor using a single Write Multiple Register
command.
Control registers are write-only, and output registers are read-only.
Register Map Overview
Register
Address
Name Read/Write Description
0 - 124 Control Registers WO Registers for Modbus commands. Refer to Control
Registers (page 158) for detailed descriptions.
300 -371 Sensor States RO Report sensor states. Refer to Output Registers (page
159) for detailed descriptions.
900 - 999 Stamps RO Return stamps associated with each range data.
Refer to Output Registers (page 159) for detailed
descriptions.
1000 - 1060 Measurements & Decisions RO 20 Measurement and decision pairs. Refer to
Measurement Registers (page 161) for detailed
descriptions.
c
ontRol
R
egiSteRS
Control registers are used to operate the sensor. Register 0 stores the command to be executed.
Register 1-21 contain parameters for the commands. The Gocator executes a command when the value
in Register 0 is changed. To set the parameters before a command is executed, the user should set up
the parameters and the command using a single Multiple Write register command.
Control Register Map
Register
Address
Name Read/Write Description
0 Command Register WO Command register. Refer to the Command Register
Values table below for more information.
1 – 21 Configuration Filename WO Null-terminated filename.
Each 16-bit register holds a single character.
Only used for Load Configuration Command.
Specifies the complete filename, including the file
extension ".cfg", ".set" or ".tfm": e.g. "test.cfg" (must
be null terminated).
If you specify a file ending with the ".cfg" extension,
only a configuration will be loaded, unless you are
switching from a configuration whose calibration was
performed with Source set to Current Configuration
in the Layout panel (see "Transformation Sources" on
page 78 for more details) to a configuration that
uses global transformations. In the latter case, global
transformations will also be loaded.
If you specify a file ending with the ".set" extension,
a configuration and the transformations that were
associated with it by performing calibration using
Current Configuration will be loaded.
The values used for the Command Register are described below.