Type definitions for readability
Type Definitions
-
types.FieldObject
-
Field definition. Certain type-specific properties are required.
Properties:
Name Type Argument Description nameString Unique name for the field within a Message
typeString A valid field type value from FieldType
descriptionString <optional>
Optional description
sizenumber <optional>
Type-specific requirement/interpretation
optionalboolean <optional>
Flag allowing optional presence of the field
fixedboolean <optional>
Type-specific optional flag for fixed-size
string,dataorarrayitemsArray.<String> <optional>
Required for
enumtype onlyfieldsArray.<Field> <optional>
Required for
arrayandbitkeylisttypes -
types.FieldTypeObject
-
Enumeration of types (placeholder)
-
types.MessageObject
-
Message definition. Typically include 1 or more
Fieldbut could represent a 2-byte command.Properties:
Name Type Argument Description messageKeynumber Directionally-unique within Service [0..255]. 2nd byte of raw payload sent over-the-air.
nameString Unique within Service
descriptionString <optional>
Optional description
fieldsArray.<Field> List of Fields comprising the message content
-
types.NimoCodecObject
-
NIM Codec definition
Properties:
Name Type Description nimoCodecKeyObject Common tag indicating NIM codec definition
Properties
Name Type Description servicesArray.<Service> The list of Service definitions
-
types.ServiceObject
-
Servicedefinition must have at least 1Messagein uplink or downlink. Message keys can be reused between uplink or downlink though the intent is to match downlink command with uplink response.Properties:
Name Type Argument Description serviceKeynumber Unique within NimCodec [0..255]. 1st byte of raw payload sent over-the-air. 0..15 reserved for system use.
nameString Unique within NimCodec
descriptionString <optional>
Optional description
uplinkMessagesArray.<Message> <optional>
Mobile-Originated Messages
downlinkMessagesArray.<Message> <optional>
Mobile-Terminated Messages