[GreenKeys] BARTG Multyterm
Jim Hammock
ki0dn at hotmail.com
Sun Nov 30 15:14:46 EST 2014
Thanks to Sam for very FB files he sent my way. This is amazing group and has been a big reason for me working in a dedicated M28 ASR station in my future shack.
Very 73 es tnx for all encouragement,
Jim Hammock
GySgt USMC (Ret.)
KI0DN
> On Nov 30, 2014, at 10:03, greenkeys-request at mailman.qth.net wrote:
>
> Send GreenKeys mailing list submissions to
> greenkeys at mailman.qth.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman.qth.net/mailman/listinfo/greenkeys
> or, via email, send a message with subject or body 'help' to
> greenkeys-request at mailman.qth.net
>
> You can reach the person managing the list at
> greenkeys-owner at mailman.qth.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of GreenKeys digest..."
>
>
> When replying, please enter correct subject line, and delete all digest text except the portion related to subject.
>
> Today's Topics:
>
> 1. Re: Military Time -vs- UTC (Dave F via GreenKeys)
> 2. Military Time -vs- UTC (Dave F via GreenKeys)
> 3. Fwd: Military Time -vs- UTC (Dave F via GreenKeys)
> 4. Re: Replying to list WAS Re: Need ASR33 repair help, in Ann
> Arbor MI (Nick England)
> 5. Re: Military Time -vs- UTC (Sheldon Daitch)
> 6. Paper tape expertise (Gabriel Egan)
> 7. BARTG Multyterm Info (Jim Hammock)
> 8. Free Model 14 RO in Orlando (Studio8H)
> 9. Re: Replying to list (WA5CAB--- via GreenKeys)
> 10. Re: BARTG Multyterm Info (Sam Hallas)
> 11. Re: Replying to list (Chris Elmquist)
> 12. Latest Radio Shack News (David Kirk)
> 13. email change (Teletypeparts via GreenKeys)
> 14. Re: Replying to list (drlegendre .)
> 15. Re: Need ASR33 repair help, in Ann Arbor MI
> (Teletypeparts via GreenKeys)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 29 Nov 2014 00:04:04 -0500
> From: Dave F via GreenKeys <greenkeys at mailman.qth.net>
> To: greenkeys at mailman.qth.net
> Subject: Re: [GreenKeys] Military Time -vs- UTC
> Message-ID: <b681f.55b5f12d.41aaadc4 at aol.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Sheldon:
>
> Your experience with the Army Reserve using "L" for "local" time must be a
> local unit
> thing. You didn't indicate whether or not they were using the 12 or 24 hour
> clock.
>
> Actually, note that the letter "J" in years past, was deliberately omitted
> from the
> list of time zones. There were two reasons for this.
>
> a. "J" was reserved for "local" time in the OBSERVERS particular locale or
> specific area where the time is/was being observed.
>
> b. Someone decided that the "J" or "j" resembled the letter "I" or "i" too
> much.
> Not sure who dreamed that one up, but I do recall that "J" time zone was a
> reserved
> slot for "local" time, and this is what your Army Reservists "should" be
> using. Time
> keeping in the Army was more or less a function of the Signal Corps, so if
> your
> unit is other than Signal, they might not have known this little tidbit.
> Check with
> your unit's Chief Signal Officer and tickle his memory for fun.....
>
> c. See ACP-121 (I), Communications Instructions, General, Chapt 3, para 326
> and 327
> specifically. ACP-121 (I) is available online as a .pdf file and explains
> it nicely.
>
> Stay well.
>
> Dave in SC
> M/SGT, US Army (Ret),
> Communications Operations Chief, PMOS 31Z5M
> ----------------------------------------------------------------------------
> ------------------------------------------------------------
>
>
>
>
> In a message dated 11/28/2014 3:23:34 P.M. Eastern Standard Time,
> SDAITCH at bbg.gov writes:
>
>
>
>
> ____________________________________
>
>
>
>
>
> My experience when on my Army Reserve trips to Yokota AB is that many
> folks would try to use L for local time, which is an issue, as there is a very
> valid lima time zone.
>
> 73
> Sheldon
>
>
>
>
>
>
>
>
>
>
>
>
>
> Dave:
>
> The "J" time zone is used to allow the time-observer to use his "local"
> time from
> wherever he is currently located at the time he wants to tell time.
>
> Originally, the "J" time zone was skipped on purpose because it resembled
> the "I"
> too much in the alphabets. LIkewise, there was no Cyrillic (Russian)
> equivalent
> for the letter "J", so that letter and a referenced time zone was dropped
> or omitted
> in years past. Being retired now, I am not sure what they are doing now or
> if the "J" time
> zone has been restored.
>
> Hope this helps too,
>
> Dave in SC
> M/SGT US Army (Ret)
> Communications Operations Chief, 31Z5M
>
> ----------------------------------------------------------------------------
> -------------------------------------------------------------------
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ______________________________________________________________
> 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
>
> 2002-to-present greenkeys archive:
> http://mailman.qth.net/pipermail/greenkeys/
> 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
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.qth.net/pipermail/greenkeys/attachments/20141129/5e4c6d30/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 29 Nov 2014 00:11:46 -0500
> From: Dave F via GreenKeys <greenkeys at mailman.qth.net>
> To: greenkeys at mailman.qth.net
> Subject: [GreenKeys] Military Time -vs- UTC
> Message-ID: <b68de.28a36bfd.41aaaf92 at aol.com>
> Content-Type: text/plain; charset="us-ascii"
>
>
>
>
>
> Sheldon:
>
> Your experience with the Army Reserve using "L" for "local" time must be a
> local unit
> thing. You didn't indicate whether or not they were using the 12 or 24
> hour clock.
>
> Actually, note that the letter "J" in years past, was deliberately omitted
> from the
> list of time zones. There were two reasons for this.
>
> a. "J" was reserved for "local" time in the OBSERVERS particular locale or
> specific area where the time is/was being observed.
>
> b. Someone decided that the "J" or "j" resembled the letter "I" or "i" too
> much.
> Not sure who dreamed that one up, but I do recall that "J" time zone was a
> reserved
> slot for "local" time, and this is what your Army Reservists "should" be
> using. Time
> keeping in the Army was more or less a function of the Signal Corps, so if
> your
> unit is other than Signal, they might not have known this little tidbit.
> Check with
> your unit's Chief Signal Officer and tickle his memory for fun.....
>
> c. See ACP-121 (I), Communications Instructions, General, Chapt 3, para
> 326 and 327
> specifically. ACP-121 (I) is available online as a .pdf file and explains
> it nicely.
>
> Stay well.
>
> Dave in SC
> M/SGT, US Army (Ret),
> Communications Operations Chief, PMOS 31Z5M
> ----------------------------------------------------------------------------
> ------------------------------------------------------------
>
>
>
>
> In a message dated 11/28/2014 3:23:34 P.M. Eastern Standard Time,
> SDAITCH at bbg.gov writes:
>
>
>
>
> ____________________________________
>
>
>
>
>
> My experience when on my Army Reserve trips to Yokota AB is that many
> folks would try to use L for local time, which is an issue, as there is a very
> valid lima time zone.
>
> 73
> Sheldon
>
>
>
>
>
>
>
>
>
>
>
>
>
> Dave:
>
> The "J" time zone is used to allow the time-observer to use his "local"
> time from
> wherever he is currently located at the time he wants to tell time.
>
> Originally, the "J" time zone was skipped on purpose because it resembled
> the "I"
> too much in the alphabets. LIkewise, there was no Cyrillic (Russian)
> equivalent
> for the letter "J", so that letter and a referenced time zone was dropped
> or omitted
> in years past. Being retired now, I am not sure what they are doing now or
> if the "J" time
> zone has been restored.
>
> Hope this helps too,
>
> Dave in SC
> M/SGT US Army (Ret)
> Communications Operations Chief, 31Z5M
>
> ----------------------------------------------------------------------------
> -------------------------------------------------------------------
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ______________________________________________________________
> 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
>
> 2002-to-present greenkeys archive:
> http://mailman.qth.net/pipermail/greenkeys/
> 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
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.qth.net/pipermail/greenkeys/attachments/20141129/6985dc4c/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 29 Nov 2014 00:33:12 -0500
> From: Dave F via GreenKeys <greenkeys at mailman.qth.net>
> To: SDAITCH at bbg.gov, WA5CAB at cs.com, greenkeys at mailman.qth.net
> Subject: [GreenKeys] Fwd: Military Time -vs- UTC
> Message-ID: <b6b8e.50029c4f.41aab498 at aol.com>
> Content-Type: text/plain; charset="us-ascii"
>
>
>
>
>
> Sheldon:
>
> See my comments in red below:
>
> In a message dated 11/28/2014 3:16:27 P.M. Eastern Standard Time,
> SDAITCH at bbg.gov writes:
>
> Guess I might be one of those unwashed US civilians, as I've heard for
> many years that military time meant using the 24-hour clock as the typical use
> of time in the US armed forces is to always designate time in the 24-hour
> clock format.
> I would not suggest that you are "unwashed". No one faults people who
> don't know.
> Within the US military, troops also use the 12 hour clock when telling
> time casually,
> i.e. when not involved in, or participating in an official military
> operation.
>
> All US soldiers are taught the 24 hour clock in BASIC training. They may
> be briefed
> on ZULU time in their initial training, but may not necessary use it in
> their regular
> jobs or MOS once they get a specific assignment
>
> Presumably, all other services in the US military teach the same thing in
> so far
> as time keeping is concerned. We all use the same time, whether local, 12
> hour,
> 24 hour, Zulu, GMT, CUT, UTC, or whatever......and in many parts of the
> world,
> one might hear terms such as 0800A (Alpha time, Germany), or 0900H (Hotel
> time,
> Vietnam, if memory still serves).
>
> Time "zones" references are purely military; I have never heard many
> civilian
> operators using the letters of the alphabet to refer to any world time
> zone. They do it
> the hard way, by adding +/- to "local" times......
>
>
> A convention that we tend to use at work is that if the time is designated
> in the 12-hour clock format, with AM or PM, it means local time. If we
> used the 24-hour clock format, it means UTC. This is particularly the
> convention used at our stateside operations.
>
> The 24 hour clock does NOT refer or infer that it means UTC.
> Regular or "local" time can use the 24 hour clock and this is used in many
> parts
> of the world instead of the 12 hour clock
>
> UTC (Zulu) time ALWAYS uses the 24 hour clock. No exceptions that I am
> aware of.
>
>
>
> UTC vs local time does tend to be a bit more complex when we live in a
> country which is usually using the 24-hour clock format, but we will also use
> context to determine whether it is local time or UTC - dealing with
> non-program issues, it is local time, program issues, always UTC.
> The 24 hour clock is easy to learn. Just remember that it changes when you
> get to ONE in the afternoon (1 PM). At that time, the 12 hour clock stops
> and 1 PM becomes
> 1300 hrs. You just count from there until you get to 12:00 midnight which
> is 2400.
>
>
> VOA seems to have gotten away from designating any times in its normal
> programming, perhaps because not all air shows are live and some are repeats,
> so any hour specific times would be in error for the repeats.
>
> One live show, BORDER CROSSINGS, which does not have an air repeat, the
> host of that show, Larry London, does designate the broadcast timing in the
> VOA format, universal time.
>
> I hope some of this is helpful to you.......
>
>
>
> INT ZBZ ....QRV....K
>
> Dave
>
>
>
> 73
> Sheldon
>
> ____________________________________
>
> From: GreenKeys <greenkeys-bounces at mailman.qth.net> on behalf of WA5CAB---
> via GreenKeys <greenkeys at mailman.qth.net>
> Sent: Friday, November 28, 2014 8:20 PM
> To: greenkeys at mailman.qth.net
> Subject: [GreenKeys] Military Time -vs- UTC
>
>
>
>
> Another thing that indicates that the information on that website was
> written by an unwashed US civilian is that I never heard anyone but a US
> civilian refer to the 24-hour clock as "military time". Although other countries
> do sometimes or even mostly use the 12-hour clock, most people living in
> them know about the 24-hour clock and don't automatically call it "military
> time". The first times I ever heard the time being routinely reported on the
> 24-hour system was probably on either the BBC or maybe Radio Havana.
>
> Robert Downs - Houston
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ______________________________________________________________
> 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
>
> 2002-to-present greenkeys archive:
> http://mailman.qth.net/pipermail/greenkeys/
> 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
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.qth.net/pipermail/greenkeys/attachments/20141129/0318633c/attachment-0001.html>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 29 Nov 2014 08:59:36 -0500
> From: Nick England <navy.radio at gmail.com>
> To: "drlegendre ." <drlegendre at gmail.com>
> Cc: "GreenKeys at mailman.qth.net" <GreenKeys at mailman.qth.net>
> Subject: Re: [GreenKeys] Replying to list WAS Re: Need ASR33 repair
> help, in Ann Arbor MI
> Message-ID: <D36B5A76-F563-4D31-A013-67FE875FB76A at gmail.com>
> Content-Type: text/plain; charset=us-ascii
>
> You are quite right and I should have included a plea to definitely "reply-all" whenever there is ANY content potentially usefu/onteresting to others in the group. It is only the truly frothy stuff I was decrying.
> Greenkeys is a wonderful and amazing resource, both in the real-time discussions and in the archives. Ever since I was given my first 28ASR (thanks Bill!), I have been pestering the list with newbie questions and receiving patient, deeply experienced, and immensely knowledgable help. And I truly appreciate all the useful info that gets posted for the archival record. Thanks, friends!
> Cheers,
> Nick, with 11 working machines so far but definitely still a newbie
>
>
>> On Nov 28, 2014, at 9:34 PM, "drlegendre ." <drlegendre at gmail.com> wrote:
>>
>> Nick, All,
>> But you do agree, that technical Q&A type exchanges are almost always worth the group's time? I mean to say, the sole purpose of this list - and the Internet et al - is the free exchange of information.
>>
>
>
> ------------------------------
>
> Message: 5
> Date: Sat, 29 Nov 2014 16:31:35 +0000
> From: Sheldon Daitch <SDAITCH at bbg.gov>
> To: "NNN7DXB at aol.com" <NNN7DXB at aol.com>, "WA5CAB at cs.com"
> <WA5CAB at cs.com>, "greenkeys at mailman.qth.net"
> <greenkeys at mailman.qth.net>
> Subject: Re: [GreenKeys] Military Time -vs- UTC
> Message-ID: <1417278699450.88522 at bbg.gov>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Dave,
>
>
> Our convention at work is if it is a 24 clock time it is understood to be UTC, especially in our stateside operations. That may not be the convention in many other places,, but sorry, that is the way we do it. It is especially important in our studio operations, where work schedules, studio times, program times in the program side of the house, all are done in local time AM or PM- Washington, DC.
>
>
> Bottom line, if someone tells me an event happens at 3PM, it will be local time - if the event occurs at 1500, it is 1500UTC - that is the way we do it at our operations. Our operational memos use the 24-hour clock format and UTC is not specified, but it is understood. It's been that way for at least 35 years.
>
>
> I didn't mean that I have trouble figuring UTC vs local time. In over 20 years of living outside the US, I've been accustomed to the local time generally being a 24 hour clock format and I can almost always determine whether UTC vs local time is used by context outside of work - but I do clarify, if there is any issue.
>
>
> 73
>
> Sheldon
>
>
> ________________________________
> From: NNN7DXB at aol.com <NNN7DXB at aol.com>
> Sent: Saturday, November 29, 2014 8:33 AM
> To: Sheldon Daitch; WA5CAB at cs.com; greenkeys at mailman.qth.net
> Subject: Fwd: [GreenKeys] Military Time -vs- UTC
>
>
>
>
> Sheldon:
>
> See my comments in red below:
>
> In a message dated 11/28/2014 3:16:27 P.M. Eastern Standard Time, SDAITCH at bbg.gov writes:
>
>
> A convention that we tend to use at work is that if the time is designated in the 12-hour clock format, with AM or PM, it means local time. If we used the 24-hour clock format, it means UTC. This is particularly the convention used at our stateside operations.
>
> The 24 hour clock does NOT refer or infer that it means UTC.
> Regular or "local" time can use the 24 hour clock and this is used in many parts
> of the world instead of the 12 hour clock
>
> UTC (Zulu) time ALWAYS uses the 24 hour clock. No exceptions that I am aware of.
>
>
>
> UTC vs local time does tend to be a bit more complex when we live in a country which is usually using the 24-hour clock format, but we will also use context to determine whether it is local time or UTC - dealing with non-program issues, it is local time, program issues, always UTC.
>
> The 24 hour clock is easy to learn. Just remember that it changes when you
>
> get to ONE in the afternoon (1 PM). At that time, the 12 hour clock stops and 1 PM becomes
> 1300 hrs. You just count from there until you get to 12:00 midnight which is 2400.
>
>
> Dave
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.qth.net/pipermail/greenkeys/attachments/20141129/08b74276/attachment-0001.html>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 28 Nov 2014 16:26:52 +0000
> From: Gabriel Egan <mail at gabrielegan.com>
> To: greenkeys at mailman.qth.net
> Subject: [GreenKeys] Paper tape expertise
> Message-ID: <5478A24C.9070704 at gabrielegan.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Has anyone on this list got expertise
> with high-speed paper tape punch/readers,
> specifically the GNT-5601? Or know someone
> who might? I'm trying to get this device
> to communicate with one of Mike Douglas
> wonderful Altair 8800 clone computers.
>
> The GNT-5601 is a weird beast with a full
> QWERTY keyboard and a Byzantine mini-operating
> system for programming the serial ports and
> of course there are too many options with
> questions suited to CNC applications of the
> device that I don't know how to answer.
> I have the full manual and can get the thing
> to punch from the Altair, but the tape it
> punches can't thereafter be read back in.
>
> Gabriel Egan
> Leicester, England
>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 28 Nov 2014 18:16:49 -0600
> From: Jim Hammock <ki0dn at hotmail.com>
> To: "greenkeys at mailman.qth.net" <greenkeys at mailman.qth.net>
> Subject: [GreenKeys] BARTG Multyterm Info
> Message-ID: <BLU436-SMTP20638E7658CE5260E1D3C4CF77F0 at phx.gbl>
> Content-Type: text/plain; charset="us-ascii"
>
> Just got a Multyterm from down under. A look through the WWW and the BARTG website failed to turn up manual, schematic. Or hookup info.
>
> Any help would be appreciated.
>
> Regards,
>
> Jim Hammock
> GySgt USMC (Ret.)
> KI0DN
>
> ------------------------------
>
> Message: 8
> Date: Sat, 29 Nov 2014 08:47:54 -0500
> From: Studio8H <mail at studio8h.com>
> To: greenkeys at mailman.qth.net
> Subject: [GreenKeys] Free Model 14 RO in Orlando
> Message-ID: <23E4EBB3-4B45-409A-86E0-A0516AE435EF at studio8h.com>
> Content-Type: text/plain; charset=us-ascii
>
> I have a Model 14 strip printer which has been printing from ITTY quite nicely.
> It is left over from a project rebuilding another Model 14 from scratch.
> It is complete (Receive-only, no keyboard, does not have its own loop supply, of course).
> And the price is right: you pick it up.
> It will be listed in a yard sale in a week, so if you have an interest, let me know soon.
> I do not want to deal with shipping it.
>
> Dan
> KD4WLI
>
>
>
>
> ------------------------------
>
> Message: 9
> Date: Sat, 29 Nov 2014 12:19:54 -0500
> From: WA5CAB--- via GreenKeys <greenkeys at mailman.qth.net>
> To: greenkeys at mailman.qth.net
> Subject: Re: [GreenKeys] Replying to list
> Message-ID: <bf174.194cd9b7.41ab5a3a at cs.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Chris,
>
> OK. I think that we've about beaten this subject into the ground, anyway.
> But I do see now that I was not considering the possibility that you might
> be using an older rather than newer mail manager. I will add that I forgot
> to add that besides top or bottom posting, there is also interleaved, which
> is likely better if there are more than 3 or 4 different questions to
> answer. And that at least we don't have the problem here that exists in all of
> the Yahoo groups where maybe 2% of the users run it in BBS mode and usually no
> one on the receiving end except another BBS mode user has a clue as to whom
> the reply was actually made. :-( And my opinion on "glass tty" is "why
> bother". Or maybe "hangin's too good for 'em". :-)
>
> Robert Downs - Houston
> wa5cab dot com (Web Store)
> MVPA 9480
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.qth.net/pipermail/greenkeys/attachments/20141129/6fe5209b/attachment-0001.html>
>
> ------------------------------
>
> Message: 10
> Date: Sat, 29 Nov 2014 17:24:24 +0000
> From: Sam Hallas <s.hallas at ntlworld.com>
> To: Jim Hammock <ki0dn at hotmail.com>, "greenkeys at mailman.qth.net"
> <greenkeys at mailman.qth.net>
> Subject: Re: [GreenKeys] BARTG Multyterm Info
> Message-ID: <547A0148.1030403 at ntlworld.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Jim Hammock wrote:
>> Just got a Multyterm from down under. A look through the WWW and the BARTG website failed to turn up manual, schematic. Or hookup info.
>> Any help would be appreciated.
>
> Jim,
>
> I find I have saved Multiterm material from the time when I was on the
> BARTG committee.
>
> I have a Construction and Operation Manual by Ken Godwin, G0PCA and
> various articles from the BARTG journal between 1991 and 1993.
>
> I'll send the manual to you direct. The other items are a ragbag of
> image files, some text conversions without the diagrams etc. They'll
> need some work. The whole bundle is about 10 MB zipped, but when PDFed
> will boil down to much less.
>
> Sam
>
>
>
> ------------------------------
>
> Message: 11
> Date: Sat, 29 Nov 2014 12:24:43 -0600
> From: Chris Elmquist <chrise at pobox.com>
> To: WA5CAB at cs.com
> Cc: greenkeys at mailman.qth.net
> Subject: Re: [GreenKeys] Replying to list
> Message-ID: <20141129182443.GR2076 at n0jcf.net>
> Content-Type: text/plain; charset=iso-8859-1
>
>> On Saturday (11/29/2014 at 12:19PM -0500), WA5CAB--- via GreenKeys wrote:
>>
>> OK. I think that we've about beaten this subject into the ground, anyway.
>> But I do see now that I was not considering the possibility that you might
>> be using an older rather than newer mail manager.
>
> Ya. Ya. No worries. I'll just offer that my email software is not older
> it's just different. In fact, I'm betting that the version 1.5.23 of
> Mutt I am using, released on March 12, 2014, is way newer than most of
> the email client software others are running ;-)
>
> 73, Chris N?JCF
> --
> Chris Elmquist
>
>
> ------------------------------
>
> Message: 12
> Date: Sat, 29 Nov 2014 12:03:56 -0700
> From: David Kirk <david at kirk.net>
> To: greenkeys at mailman.qth.net
> Subject: [GreenKeys] Latest Radio Shack News
> Message-ID: <547A189C.1010908 at kirk.net>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> It doesn't look good:
>
> http://www.bloomberg.com/news/2014-11-18/hedge-fund-monarch-said-to-end-talks-on-radioshack-loan.html
>
> An interesting tale of Radio Shack from the inside as an employee:
>
> http://www.sbnation.com/2014/11/26/7281129/radioshack-eulogy-stories
>
> Finally, every Radio Shack catalog online. Its amazing I can't remember
> names of people I work with but I can remember these products and pages
> from decades back:
>
> http://www.radioshackcatalogs.com/
>
>
> ------------------------------
>
> Message: 13
> Date: Sat, 29 Nov 2014 15:00:14 -0500
> From: Teletypeparts via GreenKeys <greenkeys at mailman.qth.net>
> To: greenkeys at mailman.qth.net, greenkeys-owner at mailman.qth.net,
> gil at baudot.net, gil at vauxelectronics.com
> Subject: [GreenKeys] email change
> Message-ID: <8D1DA2639C16481-1C68-2FC3B at webmail-va002.sysops.aol.com>
> Content-Type: text/plain; charset="us-ascii"
>
>
> Gil,
>
> I am changing my email address to teletypeparts at comcast.net
>
> Could you please enable that email address for me please.
>
> I would like to keep the aol email enabled for awhile if possible.
>
> You and members will be getting a bulk mail from me with the above info as well.
>
> Thanks,
>
> Wayne
> KB1FDW
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.qth.net/pipermail/greenkeys/attachments/20141129/4ca3909f/attachment-0001.html>
>
> ------------------------------
>
> Message: 14
> Date: Sat, 29 Nov 2014 19:38:16 -0600
> From: "drlegendre ." <drlegendre at gmail.com>
> To: Chris Elmquist <chrise at pobox.com>
> Cc: greenkeys at mailman.qth.net
> Subject: Re: [GreenKeys] Replying to list
> Message-ID:
> <CAFjrmd6nAe22Eq8rdXLegvkXeMRP4WdvmyHsGLid_mRnFt4QqA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> "Lucky we didn't say anything about the dirty knife!"
>
>> On Sat, Nov 29, 2014 at 12:24 PM, Chris Elmquist <chrise at pobox.com> wrote:
>>
>>> On Saturday (11/29/2014 at 12:19PM -0500), WA5CAB--- via GreenKeys wrote:
>>>
>>> OK. I think that we've about beaten this subject into the ground,
>> anyway.
>>> But I do see now that I was not considering the possibility that you
>> might
>>> be using an older rather than newer mail manager.
>>
>> Ya. Ya. No worries. I'll just offer that my email software is not older
>> it's just different. In fact, I'm betting that the version 1.5.23 of
>> Mutt I am using, released on March 12, 2014, is way newer than most of
>> the email client software others are running ;-)
>>
>> 73, Chris N?JCF
>> --
>> Chris Elmquist
>> ______________________________________________________________
>> 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
>>
>> 2002-to-present greenkeys archive:
>> http://mailman.qth.net/pipermail/greenkeys/
>> 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
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.qth.net/pipermail/greenkeys/attachments/20141129/af12560f/attachment-0001.html>
>
> ------------------------------
>
> Message: 15
> Date: Sat, 29 Nov 2014 14:55:55 -0500
> From: Teletypeparts via GreenKeys <greenkeys at mailman.qth.net>
> To: drlegendre at gmail.com, GreenKeys at mailman.qth.net
> Subject: Re: [GreenKeys] Need ASR33 repair help, in Ann Arbor MI
> Message-ID: <8D1DA259EC51CE5-1C68-2FBC3 at webmail-va002.sysops.aol.com>
> Content-Type: text/plain; charset="us-ascii"
>
>
> Keith,
>
> With the 33 ASR in full duplex, 4 wire, the distributor is only used when the tty is sending to a computer or device in LINE mode. If you want a copy of what you are sending you have to enable your computer or device to echo back the copy. In half duplex, 2 wire the printer will print whatever you are sending. Most 33's in half duplex are also using 60 MA current loop. There are always exceptions to the common above modes.
>
> In LOCAL mode the 33 is using the distributor all the time. The distributor is a carbon brush faceplate with 1 start bit (always a space) and 8 character bits (mark or space depending on what contacts are selected in the KB, TR or AB)
> and one stop bit that is two bits long. After a character is typed the dist stays in the stop segment to keep the 33 printer current loop closed.
>
> Hope this helps.
>
> Wayne
> KB1FDW
>
>
>
> -----Original Message-----
> From: drlegendre . <drlegendre at gmail.com>
> To: Teletypeparts <teletypeparts at aol.com>; GreenKeys <GreenKeys at mailman.qth.net>
> Sent: Fri, Nov 28, 2014 12:28 am
> Subject: Re: [GreenKeys] Need ASR33 repair help, in Ann Arbor MI
>
>
> Wayne,
>
>
> For those of us not in-the-know, could you briefly explain the function of the 'distributor' in these machines? Is this a mechanical rotary contactor, the likes of an automotive distributor - less the spark gap, of course? Does it use carbon brushes / wipers and so forth?
>
>
> @All
>
>
> How the +HECK+ do you reply in-thread to a greenkeys post? I'm used to communicating with other lists via gmail, where if I hit the 'Reply' field, it sends my reply to the list, and properly threads it. With greenkeys. my replies always go directly, and personally to the last poster - rather than the list et al.
>
>
> If you're seeing this post, it's because I tacked a greenkeys reply to the To: field in the mail, which is actually pointed to Wayne / Teletypeparts. Are you all seeing this, properly threaded? If not, how do I handle this properly via gmail?
>
>
> I can only imagine the duplicate threads and other havoc my alleged contributions might be creating. Thank you for your deference on this occasion of my newbishness. ;-)
>
>
> -ML
>
>
>
> On Thu, Nov 27, 2014 at 10:04 AM, Teletypeparts via GreenKeys <greenkeys at mailman.qth.net> wrote:
>
> Keith,
>
> I dont live near your location but I can give you a few tips.
>
> Dont type too much without inspecting the rubber hammer that hits the typewheel. If the rubber hammer falls of or disintegrates you will ruin the typewheel quickly.
>
> Most 33 troubles can be found by visual inspection. No adjustments unless you have exhausted the visual stuff. Look for things out of place like contacts in the keyboard, tape reader and answerback.
>
> There should be nothing in the machine that needs force to fix or correct. Go slow.
>
> 33's that have been sitting a long time usually have congealed grease on the codebars and other areas that need freeing up. The codebars ride on slotted round bars on each end and in the middle. I use "Breakaway" in those areas very carefully sprayed on. Very Carefully!
>
> Dont spray any solvents into the keyboard contacts or other plastic contact areas. Use a pipe cleaner with some contact cleaner sprayed on the pipe cleaner and clean carefully. You may not need to do this. Remember that the kybd, TR and AB contacts are all in parallel feeding the distributor. Thats why its good to be able to test the printer from another source before assuming that you have printer problems when the problem might be in one of the three subassemblies that feed the distributor.
>
> Most 33's come with 20 MA full duplex (4 wire) setup in the UCC-6. You need a current loop to RS 232 adapter to connect to a computer. Some computers have a current loop interface in them. PDP's etc. Ask on Greenkeys.
>
> I will include some pics that might help identify stuff.
>
> Happy Thanksgiving from Vermont where we have 4 to 8 inches snow overnight.
>
> Wayne
> KB1FDW
>
> distributor
>
>
> kybd contacts
>
>
>
> codebars
>
>
>
> UCC-6
>
>
>
>
>
> ______________________________________________________________
> 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
>
> 2002-to-present greenkeys archive: http://mailman.qth.net/pipermail/greenkeys/
> 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
>
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.qth.net/pipermail/greenkeys/attachments/20141129/4bb7a4c5/attachment.html>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: Distributor.jpg src=
> Type: image/pjpeg
> Size: 83039 bytes
> Desc: not available
> URL: <http://mailman.qth.net/pipermail/greenkeys/attachments/20141129/4bb7a4c5/attachment.bin>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: kybd contacts.JPG
> Type: image/pjpeg
> Size: 319194 bytes
> Desc: not available
> URL: <http://mailman.qth.net/pipermail/greenkeys/attachments/20141129/4bb7a4c5/attachment-0001.bin>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: Codebars.JPG src=
> Type: image/pjpeg
> Size: 378787 bytes
> Desc: not available
> URL: <http://mailman.qth.net/pipermail/greenkeys/attachments/20141129/4bb7a4c5/attachment-0002.bin>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: UCC 6 View.jpg
> Type: image/pjpeg
> Size: 474505 bytes
> Desc: not available
> URL: <http://mailman.qth.net/pipermail/greenkeys/attachments/20141129/4bb7a4c5/attachment-0003.bin>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> GreenKeys mailing list
> GreenKeys at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/greenkeys
>
>
> ------------------------------
>
> End of GreenKeys Digest, Vol 130, Issue 20
> ******************************************
More information about the GreenKeys
mailing list