-
Key: GEMS-14
-
Legacy Issue Number: 12767
-
Status: closed
-
Source: Amergint Technologies ( Rob Andzik)
-
Summary:
There are two questions regarding hex_value types in the GEMS-ASCII PSM.
- Hex value arrays are not well defined and the concept is complicated.
- Can we use a 0xFFFF notation?
Suggestions:
Yes, the 0xFFFF notation can be used but it should be optional. ''(e.g. FAFA is the same as 0xFAFA)''
As for arrays, this is a little complicated. Suggestions are as follows:
- Restrict arrays of hex_values to be the same bit length
- Move the bit length to the parameter value: e.g. hex_value[2]=22.FAF320,15.EB90 would specify an array with a 22 bit field and a 15 bit field
RT Logic's recommendation is to use the 2nd option.
-
Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
-
Disposition: Resolved — GEMS 1.0
-
Disposition Summary:
The GEMS PIM hex_value definition will be updated to make clear that all hex_values contained in arrays of hex_values must be of the same bit length.
The ASCII PSM definition will be updated to make clear what formats are allowable for hex_values. -
Updated: Fri, 6 Mar 2015 20:58 GMT
GEMS — 9.1.1.1 Need to clarify how hex_value types are specified in the ASCII PSM
- Key: GEMS-14
- OMG Task Force: Ground Equipment Monitoring Service 1.0 (GEMS) FTF