SW_DevMCP

Device Module "MCP"

The "MCP" Module (= Central Management Program? ) builds the central control instance for all the other modules. All modules read and write from/to a shared buffer, and the main routine telex.py hands out the buffer contents to all enabled device modules in sequence. Each device module can/react on the contents of the buffer which may hold text or commands, and finally write its results back to the buffer for further recognition/processing by the other modules (and MCP).

MCP contains the central "heartbeat" of the system, it monitors the different states of piTelex, issues commands to the other modules depending on the actual state, reads result codes from the modules and updates the current state of the system.

There are five main states:

State	Name	Description
ZZ	Sleeping	StandBy, Teleprinter off, waiting for action
Z	Offline	Teleprinter may be on (depending on module)
WB	Dialing "WählBereit"
A	ActiveInit	Connection established, printer start command sent
AA	ActiveReady	Connection established, printer ready

Commands are identified by a preceeding , therefore issuing <ESC>-A<Enter> e.g. in the screen modules will switch on the teleprinter and will output someting like <MCP:TP1><piT:AA>. These are messages from different modules. To the left of the colon is the abbreviated module identifier, to the right the output of the module. In the above example MCP reacts to our A command by giving the command to switch in the teleprinter; after execution of the 'printer on' command the RPiTTY module sends message AA (printer ready).

Module Information

System

System	Comments
RPi	OK
PC Linux	OK
PC Windows	OK
Mac	OK

Dependencies

Python Module	Install	Anaconda
-	?	?

Command Line Arguments

none

Config File Parameter

none

Description

TODO

Implementation

TODO