dev/null for telex

[levend]

the method suggested by Volker is working more or less correctly, I was able to fake a remote device. This question I believe is now settled. Thanks for the suggestion and the help.

[kerk1v]

the method suggested by Volker is working more or less correctly, I was able to fake a remote device. This question I believe is now settled. Thanks for the suggestion and the help.

Yes, sorry, I forgot you can't use "000" as the local number in userlist.csv, PiTelex then goes into a CLI mode whose utility I haven't figured out yet.

Glad to have been of help!
Regards, and feel free to telex me, 48822 sama e.

[kerk1v]

I will definitely step forward and purchase a complete i-telex kit in 2022, but right now the budget for my "strange" hobbies have deplepted.

How strange? Amateur Radio, vintage and / or modern electronics and IT and the like won't be considered strange here, so let's hear from them.

I can start:

I for instance collect fountain pens, mostly modern, most quite affordable like the Lamy Safari annual special edition(s) which I have complete since around 2005 costing 20-24 EUR each or the annual Pelikan matching the "Ink of the year" which comes for around 120-140 in a nice presentation box and with the matching ink. But I also have some vintage and NOS pens from the 1960ies-70ies, all bought for under 40 EUR.

I also use fountain pens for my daily writing needs.

Regards,

[DF3OE]

Pelikan fountain pens are made here in my home town Peine and of course, I have a few of them... even some not really cheap ones...
I used to know someone who worked there...

[MKeuer1959]

Hello Balazs,

good idea to use the I-Telex next year.
I found the i-Telex-cards inside the Reichelt box with Jan's (https://telexforum.de/memberlist.php?mo ... file&u=121) front covers a real "fire-and-forget-system".

[Fernschreiber]

Hello Balasz,
There is indeed a service for sending and playback. It is intended for transmitting "Baudot-Arts" to my platform to get them into the baudot-art server . You have to give in a filename of your choice to save the data, so nobody else can call them. After transmission there is an option to play data back to see if they are correct. It happens all in one session, there is no callback. You can do it as much as you like, if you always use the same filename, the file will be overwritten. If the session breakes for some reason, just dial new, enter the filename and choose replay.
just feel free to use it by calling 881199. Hope it is reacheable by your pi-telex.

Regards
Willi

[levend]

Hello Willi

Thanks for the suggestion, i just tried your service. Unfortunately it's again an incompatibility issue with piTelex. Please see the attached screenshot for the results. What not visible but also observed is the very slow arrival of characters from the remote.
I'm more and more tempted to make that purchase to the proper i-telex interface....

F2ACC901-BC18-4ECC-BCEF-80B4C4C514BB_1_201_a.jpeg

[kerk1v]

Hello Willi

Thanks for the suggestion, i just tried your service. Unfortunately it's again an incompatibility issue with piTelex. Please see the attached screenshot for the results. What not visible but also observed is the very slow arrival of characters from the remote.
I'm more and more tempted to make that purchase to the proper i-telex interface....

F2ACC901-BC18-4ECC-BCEF-80B4C4C514BB_1_201_a.jpeg

I had the same problem with PiTelex when accessing many of Willi's services. I also had the issue with slow arrival of characters (as low as 1 per second). It seems the PiTelex handshake routines are not 100% compatible, despite Fred's efforts to work with the developer to make it 100% compatible.

Since I have the original I-Telex, no problems whatsoever

I also know Fred is working on implementing I-Telex on smaller, cheaper microcontrollers (ESP8266) but it's in very early beta stage.

P.S.: Feel free to use and abuse my header!

Regards,

[Fernschreiber]

Hello Balazs and Volker and all,

unfortunately it does not seem to work proper. If characters receive very slowly, the information in acknowledgepakets seem to be wrong aud slow it down. I put a lot of work into that mechanism to get it right, make sure to get a fluently stable transmission over 45 Minutes (Baudot-Arts or KLKL-List) by checking the Ack's and calculate speed according to not stress the unknown RX-Buffer too much. If there are no Acks (which is OK as well) the speed is fixed to 50 Baud, no matter what happens at the far end. If there are Acks it 's difficult to distinguish between valid/invalid values, I have to accept them beleving they make sense. I can state little proudly that my servers seem to interwork with i-telex (and its protocol) very well.
I had so much fruitful discussions with (thanks to)Fred to get things running, possible incomatibilities will be investigated and solved as quickly as possible.
@ Balazs: do yourself a pleasure and switch to proper i-telex System to avoid problems in the future.

Regards
Willi

[BjoernS]

Hello everyone

Just a comment from a "biased bystander".

Most bugs, or just initially not implemented parts of the spec, have been fixed (I might've had a part in this), but in the ExperimentalFeatures-2020-10 branch. I've recently tried again convincing Jochen to promote those changes to master branch, but, alas, failed.

Several users, including Jochen and me, are running piTelex on the current experimental branch without major issues (AFAIK), so try it if you'd like (after cloning the repos, git checkout ExperimentalFeatures-2020-10). Also, development is ongoing, feel free to contact us (via forum or github) if you think you've found a bug or a part of the i-Telex protocol spec that's not fulfilled.

Best regards


Björn