-
Notifications
You must be signed in to change notification settings - Fork 10
SW_MultipleInstances
It is possible to run more than one piTelex process simultaneously on the same host in order to control two ore more teletypes, as long as the host provides sufficient CPU, memory and I/O ressources. Even an older Raspberry Pi is able to manage two or three TW39 teletypes (ED1000 machines need much more computing power).
-
The hardware interfaces must exist separately for each teleytpe.
-
Each teletype MUST use different hardware ports (GPIO-lines / USB-Ports / sound cards)
-
In order to receive incoming connections, each teletype MUST own separate TCP-Ports
-
It is recommended to also separate the logfiles, archives a.s.o. (if enabled) to avoid messing up the entries of the different teletypes / piTelex instances.
-
A single software installation is sufficient. Just call
telex.py
with different configuration files for each teletype. For example:./telex.py -c t100.json ./telex.py -c fs220.json ./telex.py -c t68d.json
See here for ideas on how to manage these instances as simultaneous background processes which automagically start at boot time.
![](img/piTelexLogo80.png)
- Local use
-
i-Telex
- tbd
- Advanced Topics
- Acccess SD-Card from Windows
- Show INET Address in Console
- Off-button for RPi
- Multiple piTelex Instances
- Mail notification on new telex
- Circumvent DS-Lite restrictions
-
TW39 (current loop)
-
ED1000 (FSK modulation)
-
V.10 (TeKaDe FS200, FS220)
-
SEU-M-board based
- with Austrian AGT (Ö-AGT, current loop)
- inside LO2000, LO2001, LO3000 (SEU-B replace)