User manual
Phoenix
32
User Manual www.RealmCtrl.com
48
6.5.1.3. The “NetLinx Diagnostics” section allows enabling and disabling of
debugging and diagnostics messages when connected to the NetLinx master
via Telnet or serially through the Program Port. For viewing NetLinx
messaging levels, RealmCtrl recommends usage of the Indigo Telnet client
developed by ShadeBlue Software (see www.ShadeBlue.com). Before any
messages can be viewed, the “MSG ON” command must be entered first.
Then, the following messaging levels may be enabled and disabled from
within the NetLinx Diagnostics section:
• [Control Logics] – messaging related to source Control Logics as defined
on the {Server/Configuration}/Sources Tab (see section 4.2.4). If this level
is enabled, messages relating to source control such as infrared channel
pulses, protocols, and general control messages will be displayed whenever a
source is controlled by any means.
• [General Messaging] – messaging related to the many functions
accomplished by Phoenix and any control events that occur as a result of end
user commands. This level governs the most copious messaging level.
Basically, it describes what Phoenix is doing by using understandable
terminology. When troubleshooting any issue, this messaging level should be
enabled.
• [Incoming Protocol] – if this level is enabled, NetLinx will display the
command protocol transmitted to Phoenix Server by the control system.
Protocol is displayed in hexadecimal format. This messaging level is typically
used only by RealmCtrl Engineers when troubleshooting problems.
• [Outgoing Protocol] – if this level is enabled, NetLinx will display the
command protocol transmitted from Phoenix Server. Protocol is displayed in
hexadecimal format. This messaging level is typically used only by RealmCtrl
Engineers when troubleshooting problems.
• [Path of Execution] – displays information regarded to the many function
calls that occur during normal operation of Phoenix. This messaging level is
primarily used by RealmCtrl Engineers when troubleshooting issues that may
be attributed to errors within the NetLinx code. By examining the Path of
Execution messaging, RealmCtrl can determine whether the NetLinx code is
executing the proper functions at any given time. Under normal
circumstances, this messaging level should be disabled. Otherwise, the
Telnet client will be barraged with messaging.
• [Pushes and Releases] – displays messaging pertaining to end-user
control events. Whenever a user presses or releases a button using a
handheld remote control, a touch panel, the web client interface, or any other
user interface employed at your facility, messages indicating the device and
the command will be displayed in the Telnet or terminal client.
• [Queue Engine] – displays very technical messages related to the Phoenix
event-driven architecture. Queue Engine messaging is typically used only by
RealmCtrl NetLinx Developers when troubleshooting particularly complicated
issues pertaining to the NetLinx control engine.
• [Remote Msgs - General] – if this level is enabled, NetLinx will display
messages pertaining to Remote systems that are communicating with the
Head End. Whether the Remote systems are communicating via TCP/IP or