Console House UDS 4 Mode Specifikace stáhnout pdf (Strana 13)

DESCRIPTION AE/LZB 119 1892 R1A

SOFTWARE

Microsoft Windows NT Workstation

The C3 Maestro console for Windows NT product

utilizes Microsoft’s Windows NT Workstation operating

system software (version 3.51 or later). This operating

system was chosen primarily for its built-in graphical user

interface support, advanced networking ability including

server/client operation and PC-AT computer platform

operating capability.

For a factory-new console system, Windows NT is

installed on the PC’s hard disk drive by Ericsson or by an

Ericsson-approved vendor. In some cases, the Ericsson-

approved vendor may also be the manufacturer of the

personal computer.

For additional information on Windows NT, including

custom configurations which influence how the console

application operates, refer to the Installation And Set-Up

Manual included within this manual set or see the

Administrator’s Manual, AE/LZB 119 1897.

Console Application On-Line Programs

The C3 Maestro console application software consists

of three (3) main executable programs. All three are utilized

when the console is on-line with the CEC/IMC Digital

Audio Switch (the console-to-CIM serial control data link is

active); therefore, they are considered the “on-line”

programs. The following block diagram illustrates program

interaction. For specific program file names and detailed

information, refer to the Administrator’s Manual,

AE/LZB 119 1897.

PERSONAL COMPUTER

GRAPHICAL

USER

INTERFACE

(GUI)

DISPATCH

MANAGER

COMMUNICA-

TIONS

INTERFACE

SERIAL CONTROL DATA

TO/FROM CIM

ENHANCED

AUDIO

ENCLOSURE

INPUTS FROM MIC

PTT BUTTONS,

FOOTSWITCHES,

DISPATCH

KEYBOARD, ETC.

OUTPUT DEVICES

(RELAYS, ETC.)

SERIAL

PORT

SERIAL

PORT

START-UP

INITIALIZATION

DATA FROM HARD

DISK DRIVE

DATABASE DATA

TO/FROM

HARD DISK

DRIVE

VIDEO

SIGNALS TO

MONITOR

POINTING DATA

FROM

MOUSE/TRACK-

BALL

VIDEO

PORT

MOUSE

PORT

INTERNAL

AUDIO

CONTROL

CIRCUITS

NOTE:

AUDIO INPUTS

AND OUTPUTS

NOT INDI-

CATED.

NOTES:

1. “OS” = OPERATING SYSTEM.

2. HARDWARE CIRCUITS NOT

INDICATED.

Figure 1 – C3 Maestro On-Line Program Interaction

NOTE

In some specialized cases, the GUI on-line program

may be replaced by or connected to a third-party

software application such as a Computer-Aided

Dispatch (CAD) peer-to-peer application. Cases of

this type are beyond the scope of this manual.

Dispatch Manager

The Dispatch Manager is the console’s main executable

on-line program. It links the other two on-line programs—

the GUI and the Communications Interface—together, it

maintains console databases and it performs many other

important functions for the console application.

The Dispatch Manager directly communicates with the

GUI and the Communications Interface by sending and

receiving data messages via operating system “pipes.” In

most all cases, the Dispatch Manager processes messages, as

needed, before passing data to the GUI or to the

Communications Interface.

Typically, data messages sent to the GUI are messages

which the Dispatch Manager has received from the

Communications Interface which originated from either the

console’s CIM within the CEC/IMC or from the console’s

audio system. Examples include, respectively, a radio-

originated call message from the CIM, and a console desk

microphone PTT button pressed message from the Enhanced

Audio Enclosure. Other messages sent to the GUI from the

Dispatch Manager include unit/group/conventional/console

entity database information and system error messages.

Data messages which the Dispatch Manager receives

from the GUI are primarily user input-type messages which

the Dispatch Manager must process and act upon

accordingly. The GUI receives mouse/track-ball (and/or

touch-screen) actions from the Windows NT operating

system, processes them as needed and then, if required

passes a corresponding user input-type message to the

Dispatch Manager. Examples include a module/entity select

action, a selected module/entity PTT action, module/entity

volume change actions, and many actions which involve PC

hard disk drive database file reads. Not all mouse/track-ball

actions which the GUI receives from the operating system

are passed on to the Dispatch Manager. Examples include

module picks, module page changes and command panel

changes.

Data messages which the Dispatch Manager sends to

the Communications Interface are primarily user input-type

messages which it has received from the GUI, processed,

and must be passed on to the CIM and/or the Enhanced

Audio Enclosure for processing. Examples include

mouse/track-ball generated console-originated call request

(PTT key/unkey) messages which must pass to the CIM and

NOTE

1 2 ... 8 9 10 11 12 13 14 15 16 17 18 ... 29 30

Komentáře k této Příručce

Žádné komentáře

Console House UDS 4 Mode Specifikace Strana 13

Komentáře k této Příručce