Verifying Wrs/Rsx Communications - Siemens Wireless Room Sensor Solution User Manual

Table of Contents

Advertisement

APOGEE Wireless User Guide

Verifying WRS/RSX Communications

Use the WRS HMI to verify communications between the WRS/RSX pair.
To verify WRS/RSX communications:
1. Connect a computer cable (540-143) from a computer to the RJ-11 port on the bottom of the WRS.
The WRS wakes up and remains active for the amount of time specified by its HMI/MMI port timeout
setting (factory default = 5 minutes). If the WRS returns to sleep mode before you are done, disconnect
and then reconnect the cable to the HMI port.
2. Start a HyperTerminal session, log on (1200 baud, 8 data bits, no parity, 1 stop bit, no flow control), and
then press ENTER to display the WRS prompt.
If there is no communication with the WRS, verify that the battery is properly inserted and the plastic
insulating strip is removed.
3. Verify WRS/RSX communications:
To test the communication link, type CHECK RSX and press ENTER.
The WRS sends a set of continuous messages to its bound RSX. The number of received
responses is used to calculate link quality. This takes about 2 to 60 seconds to complete.
To view the quality of completed communications over the past 10 minutes, type COMM WRS
and press ENTER. See Table 5 for desirable parameter values.
If the link quality or average transit time is poor, try moving the WRS and/or RSX (or just the antenna)
to reduce the transmission distance or improve the communications path.
4. Disconnect the computer from the WRS.
5. Repeat Steps 1 though 4 for all WRSs.
6. If desired, you can use the workstation features to define alarms for WRS low battery voltage and loss
of wireless communication events using the value of TEC point 99 (see Table 6 for details).
To verify RSX/TEC communications, see Verifying RSX/TEC Communications.
22
Table 5. Quality Communication Guidelines.
Parameter
Link Quality
Average Transit Time
Good Quality if Value is:
between 90% – 100%
less than 20 milliseconds
Siemens Building Technologies, Inc.
Revision Date: July 10, 2008

Advertisement

Table of Contents
loading

Table of Contents