Inovonics Wireless Corporation 3B6OTPMTX User Manual
Confidential
11
Chapter 4
Registration
4.1 Registration Overview
Every device is programmed with a four-byte unique identification (UID)
number. The UID is sent with every message, indicating the device which
transmitted it. The UID is made up of a one-byte market identification (MID)
number and a three-byte serial number. The bar code label on each printed
circuit board includes the eight digit serial number. For example the bar code
label “00991240-2028B-1” begins with the eight-digit serial number:
00991240. Converting this number to hexadecimal yields: 0F 20 08. Preceding
this serial number with the MID (A0), the MID for submetering devices, for
example) gives the UID: A0 0F 20 08, and will appear in every RF message
sent by the device.
number. The UID is sent with every message, indicating the device which
transmitted it. The UID is made up of a one-byte market identification (MID)
number and a three-byte serial number. The bar code label on each printed
circuit board includes the eight digit serial number. For example the bar code
label “00991240-2028B-1” begins with the eight-digit serial number:
00991240. Converting this number to hexadecimal yields: 0F 20 08. Preceding
this serial number with the MID (A0), the MID for submetering devices, for
example) gives the UID: A0 0F 20 08, and will appear in every RF message
sent by the device.
The purpose of registration is to associate the unique ID in the wireless device
with specific application functionality, such a descriptive name, the location
and point supervision. It is recommended that all wireless transmitters,
transceivers and repeaters be registered. To ensure wireless devices are
registered only when intended, the application controller should have a
specific registration mode.
with specific application functionality, such a descriptive name, the location
and point supervision. It is recommended that all wireless transmitters,
transceivers and repeaters be registered. To ensure wireless devices are
registered only when intended, the application controller should have a
specific registration mode.
4.2 Registration Procedure from the End User’s
Perspective
Perspective
1. The application controller is placed in registration mode, ready to associate
the device’s UID with application functionality.
2. The application controller prompts the end user to enter application specific
information and send a registration message from the device.