Motorola 68P02958C00-B - Manual (Page 293)

C-1
Software Diagnostics Output
This section lists the diagnostics which are available for the various MOSCAD RTU devices. The
messages are listed as they appear on the screen, with %% signs in the text to represent the device’s
current alphanumeric values.
The description which follows the diagnostics messages, provides an explanation for the variables.
Terms that are used frequently in diagnostics are described below:
Term Explanation
Device A MOSCAD/MOSCAD-L software module.
Instance (of a device) A device may appear more than once in
MOSCAD/MOSCAD-L, each carrying a
unique name.
Level A group of diagnostic checks. Up to 100 (0
through 99) levels can be custom-defined for
each device.
PIN table A pointer which allows “cabling” between
two devices during run time.
Address Numeric sum of Site ID and System
Address.
Tick Time measurement unit, equal to 10 ms.
TRANSPORT MUX DEVICE = TRNINT
## 16 LEVEL = 0
Mini Session Channels : %% 1
Master Channels : %% 2
Slave Channels : %% 3
1. Number of logical mini-sessions that serve the RTU applications. A mini-session is an API layer that
serves the RTU-to-RTU communications, event bursts, and setcall.
2. The number of logical channels above the Presentation layer from which the RTU can initiate
communications. In an RTU there are no such logical channels as there is no application that can
initiate a call. Control centers (e.g. MCP-M) do have such applications such as schedulers and
command dispatchers.
3. The number of logical channels above the Presentation layer through which the RTU reacts to calls
simultaneously (such as error logger, diagnostics, D.B. monitor, process monitor, date and time,
download). The RTU does not need more than 2-4 channels for regular and orderly activity.