SW_DevScreen - fablab-wue/piTelex GitHub Wiki

Device Module "Screen"

Module Information

System

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

Dependencies

Windows:

Python
Module
Install Anaconda
colorama pip install colorama conda install colorama

Linux:

Python
Module
Install Anaconda
termios ? ?

Command Line Arguments

-S
--noscreen

Use this argument to disable the screen

Config File Parameters

Param Default Values Description
show_BuZi true false / true If true, show special characters for Bu / Zi on Screen
show_capital false false / true if true, use capital letters on screen
show_ctrl true false / true if true, show control sequences on screen
show_info false false / true if true, show additional info on screen
show_line true false / true if true, mark the maximum line length by a „|“ in column 69 on screen

Description

The screen module lets you communicate with the connected teletype over ASCII-terminal and keyboard of the computer running piTelex. It can be accessed directly over the computer's display and keyboard connectors or via ssh (Windows: PuTTY). In most application cases, this module should be enabled.

This way the output of the teletype can be monitored and keystrokes can be sent to the printer as well as to piTelex. These keystrokes may consist of simple text, but may also contain commands to control the teletype or thr behaviour of piTelex.

If show_ctrl is set to True, screen will output system status messages which are described here

Setting show_info to True will output a lot of additional internal information from line state changes to print buffer fill grade. This is mostly useful for debugging purposes by the experts....

Quick keys for console operation:

Key <ESC>-Sequence function description
<Insert> <ESC>at<enter> AT start outgoing call ("Anruf-Taste")
<Del> <ESC>st<enter> ST end an (outgoing) call ("Schluss-Taste")
<Home> <ESC>lt<enter> LT enter local mode ("Lokal-Taste")
Ctrl-C <ESC>exit<enter> Stop piTelex
@ WRU Request answerback ("Kennungsgeber") from remote machine
# ID Send local answerback ("Kennungsgeber")
_ ZV
LF
Line Feed
\ WR
CR
Carriage Return
% Bell ring the bell of the connected teletype
$ Expands to "The quick brown fox jumps over the lazy dog."
<backspace> Expand to "e e e"

More short commands

The following <cmd>s can be used, embedded between <ESC>and <Enter>:

cmd Description
ry print 1 row of "ryryryry...."
fox print "the quick brown fox jumps over the lazy dog"
pelze print "kaufen sie jede woche vier gute bequeme pelze xy 1234567890"
abc print "abc...xyz 12...90 .,-+=/()?'%"
a1 print "a1b2c3d4....x4y5z%"
lorem print 7 lines of blind text ("lorem·ipsum·dolor·sit·amet,·consectetur·adipisici·elit,...")
logo print piTelex logo as Baudot Art (takes 8 lines)
test print 6 lines of ".-=x=-.-=x=-. ...."
date print DateTime String
font enter font mode. In font mode, all entered characters are recoded so that they can be
punched to tape in a human-readable baudot-art representation, see Font Mode
cli enter cmdline interface, see CmdLine Interface
read read, if necessary convert, and print the contents of <file>, see below

Reading files (read)

read <basename> allows for reading and inserting the contents of a file <basename>.<ext>, which must be located in or below a subdirectory ./read of piTelex and may have one of the following extensions. depending on the extension, piTelex performs different actions:

Extension Action
txt ASCII Text in UTF-8 encoding, insert into stream
pix,pox Convert file to binary format and write the contents to <basename>.bin
bin,ls Convert binary file to text on the fly and insert into stream

<basename> will be converted to lower case before looking for the file, so "PiTelex" and "pITElex" will both refer to a file with basename "pitelex".

Note: Starting piTelex in foreground (from the shell) will lead you immediately to the screen interface, if enabled.

If piTelex is running in background, you can connect to it's screen output by means of screen or byobu. See Software installation for details

Note: Most of these commands are not directly provided by device Screen, but because they will in most cases be used from the screen interface, they are described here for convenience.

⚠️ **GitHub.com Fallback** ⚠️