A device failing to alarm or restore properly can be the result of a number of different things. This is part 3 of a multiple week series and this week we will cover reading and analyzing the System Log.
TECH SUPPORT SUMMARY:
The system log can be a very valuable tool for installation, and can be especially useful troubleshooting sticky RF issues. Most of the data in the System Logs for all intents and purposes will be unreadable. The system log however can be used to identify a device ID, observe which locators are picking up a device you are testing, or verify whether or not a locator signal is getting back to the Master Receiver.
Step 1: Accessing System Log:
a) Select System Settings Tab
b) Select Systems Log
Step 2: Device ID’s:
a) Time Info – Date and time that the signal was processed by the cube. This section also covers the name of your server and the device reporting to the server as well. In the case of an alarm signal, it will always be MR-500.
b) Device Info – If the device is unlearned, it will show up in the system log as an “Unknown device”. Otherwise, it will have a system generated Account number. This section also displays the device type (EX: UT-3). Pendants will have WTC and most other devices will display UT-3. You will also see (ALARM) or (RESTORE) indicating what kind of signal it is.
c) Wireless Network info – The final section shows Flags (such as Power (P), Tamper (T) or Battery (B). It also shows the Locator and Repeater ID that is transmitting back to the MR-500. Here, you’ll notice both a Gen 3 and a Gen 4 Locator. Gen 3 locators have 3 digit ID’s while Gen 4 have 6 digit IDs. Then you’ll see the Master Receiver ID number. Finally, you’ll notice only the Gen 4 Locator (00001E) has an RSSI value. This will tell you if the signal from the transmitter to the Locator is strong or weak. For Response Care servers, the lower the value the higher the strength
Step 3: Locator Check-In:
This image displays what to look for in the system log when you hit the test button from the locator. Here you will be able to verify several features including Locator ID and name, but more importantly this will confirm if you are getting a signal back to the cube. NOTE: For Gen 4 systems, a locator test will only show up in the system log after they have been learned in to both the wireless network and the MR-500 itself.
Learning to read the system log can give you an invaluable tool for troubleshooting a suspected device or RF interference issue, among other things. You can use the system log to cross reference the accounts and the wireless network link to ensure you aren’t just held up by a programming error. When used in conjunction with the previous “My device won’t work” Tech Bulletins, the system log will aid in confirming or refuting suspected 433MHz or 900MHz RF coverage concerns.