Telexforum.de

After a break of a couple of years, I revisit the Pi-Telex system.

Thanks to Wolfram's "Idiot Guide" I was able to get the Pi Zero working with the software, and the ==TELEX== message appears after starting telex.py (autostart not yet working)

Connected T68, with FSG to the O-AGT, but machine runs constantly.

PUTTY SSH into system, and there is "Chatter" from pi-Telex, which results in the T68 rattlng and printing rubbish.

I am sure that the problem here is most likely related to the telex.json settings that I have.

pi-telex json.JPG

Some help would be appreciated, I'm well out of my comfort zone here

I send you this evening my t68 config

Autostart is working - i did not realise that pi can of course do more than one thing at a time

byobu screen shows it running happily

here my configuration telex.json
It is fpr testing
for standard you just need to use the parts archive and i-telex from original
and no babelfish of course.
But the # SEU-M - TW39-teletype should work.
after altering your telex.json open the byobu-screen and stop telex with ctrl+c
this stops telex.service and restarts it with new settings automaticly

Code: Alles auswählen

# Configuration examples for piTelex
# 2023-03-15
# requirements: commentjson, argparse (additional requirements per section are listed there)
#
# This file can be used as a starting point for piTelex installations using the default hardware configuration.
# Screen and log module should be enabled always for testing and debugging purposes.
# Archive module, if enabled, saves a prettyprint transcript of each connection.
#
# enable the TTY module(s) that correspond to your TTY type.
# Disable ("enable": false,) or optionally delete unused modules or entries.
#
#########################################################
# For detailed configuration infos see the wiki pages !!!
#########################################################
#
# Additional modules are described in the telex_Example_XXX.json files
#
{
  "devices": {
    
    
        # SEU-M - TW39-teletype with FSG using an Austrian AGT (OeAGT) with SEU-M-card as controller
        # Note: SEU-M-card (with aRPi) is a replacement of a SEU-B ord SES-B-card
        "RPiTTY_SEU-M_Oe_AGT-TW39": {
          "type": "RPiTTY",
          "enable": true,
          "mode": "AGT-TW39",
          "pin_txd": 17,
          "pin_rxd": 27,
          "pin_relay": 22,
          "inv_relay": true,
          "pin_power": 9,
          "inv_power": false,
          "pin_number_switch": 10,
          "inv_number_switch": true,
          "WB_pulse_length": 60,
          "baudrate": 50,
          "coding": 0,                 # 0=ITA2
          "loopback": false
        },

    

  # Module type "i-Telex"

    "i-Telex": {
      "type": "i-Telex",
      "block_ascii": true,
      "enable": true,
      # "port": 64321,
      "centralex": true,
      "centralex_srv": "tlnserv2.teleprinter.net",
      "centralex_port": 49491,
      "tns_dynip_number": 123456, # Subscriber number registerd at TNS
      "tns_pin": 123456
    },

    ###########################################################################

    "log": {
      "type": "log",
      "enable": true,
      "filename": "./piTelex.log"
    },

    ###########################################################################

    "archive": {
      "type": "archive",
      "enable": true,
      "path": "archive/",
      "send_email": false,
      "email_sender": "54353_hoeck_d@wolfhenk.de",
      "smtp_server": "mail.wolfhenk.de",
      "smtp_port": 587,
      "smtp_user": "username",
      "smtp_password": "password",
      "recipient": "spam@wolfhenk.de"
      },

    ##########################################################################

      "babelfish": {
        "type": "babelfish",
        "enable": false,
        "openai_api_key": "sk-proj-get_your_own_api_key",
        "Zielsprache": "swahili"
      }

    #########################################################################

    },

  ###########################################################################

  "wru_id": "54353 hoeck d",
  "wru_replace_always": false,
  "dial_timeout": 0,
  "continue_with_no_printer": false,
  "errorlog_path": "./",
  "welcome_msg": false  #Prints out a ed1000 style timestamp on connection
}

Thanks Wolfram, I will make some adjustments to my configuration and report back.

Okay, so some changes made, though these appear to be related to the call, clear and dial buttons, which are combined with the machine.

Current status:

Machine is continually switched on, and line current is always present - I am unable to clear this state and put the T68 into a stopped condition.

Invoking the CLI on PiTelex makes the machine rattle and print rubbish.

More to do I guess

What version of piTelex are you using ? See the version info in the Startup message, e.g.

 -= TELEX (Rev. 001d 2025-04-05 17:05) =-

Rev 002b 2025-05-25 15:30

M1ECY hat geschrieben: ↑Fr 29. Aug 2025, 19:49 Rev 002b 2025-05-25 15:30

This should be OK.... Hmmm....

So, to be clear, the T68 here has a built in FSG, and works perfectly on I-Telex.

Running a Pi ZeroW, which seems to boot fine, is visible on my network, and piTelex appears to be running ok.

O-AGT seems outwardly to be okay, though no refurbishment work has taken place.

Telexforum.de

Pi-Telex - O-AGT - T68 with internal FSG

Pi-Telex - O-AGT - T68 with internal FSG

Pi-Telex - O-AGT - T68 with internal FSG

Pi-Telex - O-AGT - T68 with internal FSG

Pi-Telex - O-AGT - T68 with internal FSG

Pi-Telex - O-AGT - T68 with internal FSG

Pi-Telex - O-AGT - T68 with internal FSG

Pi-Telex - O-AGT - T68 with internal FSG

Pi-Telex - O-AGT - T68 with internal FSG

Pi-Telex - O-AGT - T68 with internal FSG

Pi-Telex - O-AGT - T68 with internal FSG