LMI Technologies Gocator 1100 Series, User Manual

Page: 165 / 250

Protocols • 165 Gocator 1100 & 1300 Series
AssemblyObject(Class0x04)
The Gocator Ethernet/IP object model includes 3 different assembly objects: Command, State and
Sample.
All assembly object instances are static. Data in a data byte array in an assembly object are stored in the
Big Endian format.
c
ommand
o
bject
The command object is used to start, stop, calibrate and switch configuration on the sensor.
Command Assembly
Information Value
Class 0x4
Instance 0x310
Number of Attributes 3
Length 32 bytes
Supported Service 0x10 (Write Single Attribute)
Attributes 1 and 2 are not implemented. These are not required for static assembly object.
Attribute 3
Attribute Name Type Value Description Access
3 Command Byte Array See Below Commands parameters
Byte 0 - Command. See table below for
specification of the values.
Byte 1-31 - Used for load configuration
command
Get, Set
Command Definitions
Value Name Description
0 Stop running Stop the sensor. No action if the sensor is already stopped
1 Start Running Start the sensor. No action if the sensor is already started.
2 Alignment Calibrate Start the calibration process:
Byte 1 of the Sensor State Assembly will be set to 1 (busy) until the calibration process
is complete, then back to zero.
3 Travel Calibrate Start the travel calibration process:
Byte 1 of the Sensor State Assembly will be set to 1 (busy) until the calibration process
is complete, then back to zero
4 Clear Calibration Clear the calibration
5 Load Configuration Load a configuration file. Bytes 1 - 31 for the filename: one ASCII character per byte.
File name 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.