Technical information

RMS NetLinx Virtual Device API
127
RMS Enterprise - NetLinx Programmer’s Guide
Unicode Strings/Commands
RMS Enterprise supports Unicode characters for international installations. The RMS NetLinx Virtual Device API supports all
Send Commands sent to the RMS virtual device as NetLinx WIDECHAR character arrays. The entire command string including
the command header must be sent as a WIDECHAR array.
Example:
// this example includes a UNICODE string.
// to send UNICODE instructions to RMS, you must
// send a WIDECHAR data type to the SEND_COMMAND
SEND_COMMAND vdvRMS, _WC('SERVICE.HELP.REQUEST- 请把帮助 ')
Alternatively if Unicode is not needed, the Send Command can be sent as traditional ASCII character arrays (Strings).
Example:
// this example includes an ASCII string.
SEND_COMMAND vdvRMS, 'SERVICE.HELP.REQUEST-Please Send Help!')
Channel API
RMS Client Channels
RMS Client Channels
Channel Description
250 - CLIENT ONLINE
(Feedback)
This channel state represents the connectivity state of the RMS client with the RMS server.
The channel is set to ON if the client is currently connected and online with the RMS server.
Note: The client may be connected to the RMS server and thus be online, but may not yet have been
registered with the RMS server. Only after the client is registered is it allowed to participate in RMS
features and functions.
This channel cannot be set, it is supplied as a feedback (read only) property.
251 - CLIENT
REGISTERED
(Feedback)
This channel state represents the registration state of the RMS client with the RMS server.
The channel is set to ON if the client is currently online and registered with the RMS server.
This channel cannot be set, it is supplied as a feedback (read only) property.
249 - ASSET INITIALIZE /
REGISTRATION
(Feedback)
This channel state represents the state of the RMS client when it is ready to accept asset registra-
tions. This channel will become active (set to the ON state) after the RMS client establishes a con-
nection to the RMS server and determines that the client is registered to a location.
Note: This channel will be deactivated (set to the OFF state) if the RMS client looses connectivity
with the RMS server.
Assets that need to be registered and asset changes should only be communicated with the RMS
client after receiving this channel event or the notification event command: "ASSETS.REGISTER".
This channel cannot be set, it is supplied as a feedback (read only) property
248 - RFID INITIALIZE/
REGISTRATION
(Feedback)
This channel state represents the state of the RMS client when it is ready to accept RFID reader &
tag registrations and tag synchronization.
This channel will become active (set to the ON state) after the RMS client establishes a connection
to the RMS server, determines that the client is registered to a location, and determines that the
RMS system has been enabled for RFID capabilities.
Note: This channel will be deactivated (set to the OFF state) if the RMS client looses connectivity
with the RMS server.
RFID readers and tags should only attempt to register or communicate with the RMS client calls after
receiving this channel event or the notification event command "RFID.INITIALIZE".
This channel cannot be set, it is supplied as a feedback (read only) property
247 - VERSION REQUEST This channel receives a BUTTON PUSH event anytime the "?VERSIONS" query is submitted to the
RMS client. All RMS related modules should respond to this request by printing their name and ver-
sion to the master's TELNET console.
240 - CLIENT GATEWAY
ASSET LICENSED
(Feedback)
This channel state represents the asset licensed state of the RMS client with the RMS server.
The channel is set to ON if the client currently has an asset license assigned on the RMS server.
This channel cannot be set, it is supplied as a feedback (read only) property.