[GreenKeys] WRU key code

Tue Oct 1 15:17:02 EDT 2019

Thanks to those coming to my rescue!  Sure a lot about the WRU function that I didn’t know, just making assumptions (😊) with how my standard 28 acts on the iTelex circuit.

Steve G./N4TTY

From: Russ Miller <wa3frp at gmail.com> 
Sent: Tuesday, October 1, 2019 2:56 PM
To: Steve Garrison <steve.n4tty at gmail.com>
Cc: ad7i <ad7i at ad7i.net>; Greenkeys <greenkeys at mailman.qth.net>
Subject: Re: [GreenKeys] WRU key code

Speaking specifically about the Teletype Model 28 Telex machine.  First, this was a rare item in the North American Telex networks. I doubt if any exist today, except for the machine that I use on the iTelex network here in Pennsylvania.  Most Telex machines were Teletype Model 32ASRs.  There were some Siemens T100 and T1000 machines.  There were also some Extel machines. But, a Teletype Model 28 on Telex was rare, even in the 1960s, 70s and 80s. 

Getting to the Teletype Model 28 as a Telex machine.  The keyboard is shown in the attached picture.  The Keyboard reflects the modified ITA2 standard used on the Telex network in Canada and the United States.  FIGS D was a German "iron cross".  The same was true for the Model 28 Typebox.   There are other differences. Note that FIGS V is ; and not =.  Note that FIGS Z is " and not +.  FIGS F, G and H are undefined in ITA2 but the North American Telex Network defined these as $, & and #. 

The Model 28ASR Telex Stunt Box uses a clever way to block the local answerback (Teletype LABD500) from being triggered when FIGS D is sent to a distant machine while, at the same time, allowing an incoming FIGS D to start the answerback message. 

There is a CCITT ITA2 standard but there are many modifications based on user requirements.  Remember that lots of Model 28 machines were used in Private Wire service on point to point or point to multipoint using dedicated WAN lines. 

Russ WA3FRP

iTelex 834328 WUTMPAM CHIL

On Tue, Oct 1, 2019 at 1:50 PM <steve.n4tty at gmail.com <mailto:steve.n4tty at gmail.com> > wrote:

Paul,

As Paul, W2TTY, indicates the 28s you’ve seen with “WRU” as the FIGS character on the “D” key was used in Telex communications.  The “$” on the FIGS “D” key was a standard communications setup (not Telex).  I have a “$” FIGS “D” key on all my 28s.  But I used them on the iTelex service from Henning and the guys in Germany.  If the other end type their “WRU” key the software on the iTelex board that sits on my intranet router sends back an “ANSWER BACK” message that is programmed right now as “30083 N4TTY” which I can change if I so desire on the iTelex board.  The iTelex board sends that ANSWER BACK sting back to the other end and also send it to my 28 so I can see what is happening.  Most Telex machines also had another key called the “HERE IS” key that also sent the same string of characters if you were initiating the ANSWER BACK instead of wait or expecting a “WRU.”

There was a drum with 12 or 13 (or so) blades that had each of the characters in the answerback string encoded on them.  I’ve never actually seen an ANSWER BACK mechanism on a 28, but would imagine that the reception of the FIGS D sequence would trip the mechanism and cause the string to be sent over the loop, which may have caused it to print locally as well as at the other end.  And if the operator pressed the HERE IS key the same think would happen.  I’m also guessing that the reception od the FIGS D suppressed printing until the ANSWER BACK drum kicked into action.  That way if you had a normal comms type box you probably would not see the “$.”

Others feel free to jump in and help me out here, as I’m definitely not an expert on the matter.

I can say that if I send an apostrophe from my keyboard they (real Telex machines) hear the bell on their end.  And if I send the BELL character they see an apostrophe.  And in reverse, if they send an apostrophe I hear my bell and if they send their bell I see an apostrophe.   A little disconcerting until you get used to it.  I tend to shy away from the apostrophe and the bell unless I really need them.  And for new iTelex users, especially across the pond, I find I have to sometimes explain this difference.

Steve G./N4TTY

iTelex  #: 30083

From: greenkeys-bounces at mailman.qth.net <mailto:greenkeys-bounces at mailman.qth.net>  <greenkeys-bounces at mailman.qth.net <mailto:greenkeys-bounces at mailman.qth.net> > On Behalf Of ad7i
Sent: Tuesday, October 1, 2019 12:31 PM
To: greenkeys at mailman.qth.net <mailto:greenkeys at mailman.qth.net> 
Subject: [GreenKeys] WRU key code

I know that for ITA2 TTYs that the WRU command is FIGS-D.  In looking at photos of what I presume to be USA Model 28 keyboards most have the D key marked "$ over D" (FIGS-D prints as $) but I have seen a few USA Model 28 with the D key marked as "WRU over D". 

In the USA was it typical for those TTY systems that made use of WRU/Answerback that FIGS-D was always used as the WRU command?  In the USA if a WRU command was received by a TTY would that received FIGS-D result in the "$" character being printed on the paper in addition to triggering the Answerback generator (if one was installed), or was FIGS-D a "command only, no key printed" type of thing?

thanks,

Paul, ad7i

______________________________________________________________
GreenKeys mailing list
Home: http://mailman.qth.net/mailman/listinfo/greenkeys
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:GreenKeys at mailman.qth.net <mailto:GreenKeys at mailman.qth.net> 

2002-to-present greenkeys archive: http://mailman.qth.net/pipermail/greenkeys/ <http://mailman.qth.net/pipermail/greenkeys/1998-to-2001> 
1998-to-2001 greenkeys archive: http://mailman.qth.net/archive/greenkeys/greenkeys.html
Randy Guttery's 2001-to-2009 GreenKeys Search Tool: http://comcents.com/tty/greenkeyssearch.html

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to wa3frp at gmail.com <mailto:wa3frp at gmail.com> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/greenkeys/attachments/20191001/55fa1783/attachment.html>