Technical information

RMS NetLinx Virtual Device API
164
RMS Enterprise - NetLinx Programmer’s Guide
RMS Service Provider - Command API
RMS Service Provider Commands
RMS RFID System Management Commands (Cont.)
Command Description
RFID.TAG.ACQUIRED-
<rfid-reader-address>,
<rfid-tag-id>,
<rfid-tag-name>,
<rfid-tag-info>,
<rfid-tag-timestamp>,
<rfid-tag-signal-strength>,
<rfid-tag-battery-level>
After all the RFID tags have been registered, any subsequent RFID tag changes must be
communicated to the RMS server.
If a RFID tag is newly acquired, this command should be sent to the RMS client to update the RFID
tag with the RMS server.
RFID tag changes are temporarily buffered inside the RMS client and are forwarded to the RMS
server in batch to optimize the data communications with the server.
RFID.TAG.LOST-
<rfid-reader-address>,
<rfid-tag-id>,
<rfid-tag-name>,
<rfid-tag-info>,
<rfid-tag-timestamp>
After all the RFID tags have been registered, any subsequent RFID tag changes must be
communicated to the RMS server.
If a RFID tag is lost by a reader, this command should be sent to the RMS client to update the RFID
tag with the RMS server.
RFID tag changes are temporarily buffered inside the RMS client and are forwarded to the RMS
server in batch to optimize the data communications with the server.
RFID.TAG.UPDATE-
<rfid-reader-address>,
<rfid-tag-id>,
<rfid-tag-name>,
<rfid-tag-info>,
<rfid-tag-timestamp>,
<rfid-tag-signal-strength>,
<rfid-tag-battery-level>
After all the RFID tags have been registered, any subsequent RFID tag changes must be
communicated to the RMS server.
If a RFID tag has been updated, this command should be sent to the RMS client to update the RFID
tag with the RMS server.
RFID tag changes are temporarily buffered inside the RMS client and are forwarded to the RMS
server in batch to optimize the data communications with the server.
RMS Service Provider Commands
Command Description
SERVICE.HELP.REQUEST-
<message-body>
(,<location-id>)
This command can be sent to the RMS client to issue a help request to the RMS server. This help
request will show in the RMS hotlist and the appropriate service provider notifications will be issued.
The <location-id> parameter is optional.
• If provided, it scopes the service provider request to a specific location.
• If not provided, the location is scoped to that of the default location that the client gateway is
assigned to.
SERVICE.MAINTENANCE.
REQUEST-
<message-body>
(,<location-id>)
This command can be sent to the RMS client to issue a maintenance request to the RMS server. This
maintenance request will show in the RMS hotlist and the appropriate service provider notifications
will be issued.
The <location-id> parameter is optional.
• If provided, it scopes the service provider request to a specific location.
• If not provided, the location is scoped to that of the default location that the client gateway is
assigned to.