User Manual

Table Of Contents
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2
GET NLS
Reply:
1
means that we have full access to the repeater network, and can get and set
parameters on other nodes.
Note! If node is not part of a repeater system, an error message will be produced:
“Error: Node not part of a repeater system, parameter not supported.
12.4.3 NMC – Node Master Capabilities
12.4.3.1 Overview
Display capabilities of the Node Master from a communications point of view.
12.4.3.2 Usage
Attribute Type: Read-Only
This attribute determines if master unit is a HUB (old) or a new generation Node
Masters with enhanced performance and functionality.
This parameter is used by System Slave to adjust certain parameters and behaviors
to the capabilities of the Node Master.
Format:
N
where
N=0 indicates that Node Master is a HUB unit with first version of controller.
N=1 indicates that Node Master is the enhanced Node Master with capabilities
matching the capabilities of the System Slave.
Example:
GET NMC
Reply:
1
meaning that node master has the full capabilities.
Note! If node is not part of a repeater system, an error message will be produced:
“Error: Node not part of a repeater system, parameter not supported.
12.4.4 RXQ – Status of Received Data Quality
Displays status of the RXQ alarm source.
12.4.4.1 Usage
Attribute Type: Read-Only
The system slave constantly runs statistics on the last 1000 data packets received
from the Node Master, and once per second calculates number of packets with
errors (such as CheckSum errors or illegal length of received data packets). If
percentage of correctly received packets decreases below a configurable threshold,
Common Commands and Attributes 90/123