![Luna ODiSI 6 User Manual Download Page 86](http://html1.mh-extra.com/html/luna/odisi-6/odisi-6_user-manual_1949788086.webp)
ODiSI 6
ODiSI 6
User’s Guide
Page 85
Each segment vector contains the following information, formatted as JSON name/value
pairs.
Table 8-4 OMSP Segment Vector Information.
Description
JSON name
Value
Segment name
“segment name”
String. User defined in ODiSI
software.
Starting location
“location (mm)”
Decimal number indicating
the location in millimeters of
the first gage in the segment
vector.
Vector size
“size”
Integer. Number of gages
contained in the segment
vector.
This provides all of the information needed to parse the measurement data transmissions into
specific gage values.
•
The metadata message may contain a gage section, a segment vector section, or
both. A segment vector will always begin at a location for which there is also a named
gage.
•
The “system status” field indicates whether the system is currently acquiring and
producing data or is stopped. A value of “measuring” indicates that the system is
producing data. A value of “stopped” indicates that the system is not producing data.
When the system is stopped, the system will send Metadata Messages only. When
the system is measuring, it will send both Metadata and Measurement Messages.
•
No changes will be made to the sensor, gage, or segment configurations when the
system is processing. When the metadata messages indicate a system status of
“measuring”, the client can be guaranteed that this information will not change from
one metadata message to the next.
•
The client can also use the Metadata Message checksum to determine whether
changes have been made to the configuration. If a Metadata Message contains the
same information as the previously transmitted Metadata Message, its checksum will
remain the same as well.
•
When the system is in a “stopped” state, the sensor and gage configuration may be
changed by the ODiSI user. The metadata messages will reflect the current
configuration, but the client should be aware that this information may change.
•
The JSON portion of the Metadata Message is followed by a 16 bit CRC-16-ANSI
(0x8005) checksum, encoded as a 4-character hexadecimal number. The checksum
is calculated over the entire length of the JSON text, beginning with the starting curly