Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TenTec\]\s+Acom\/Orion\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TenTec\]\s+Acom\/Orion\s*$/: 3 ]

Total 3 documents matching your query.

1. [TenTec] Acom/Orion (score: 1): Author: n1eu@netscape.net (Barry N1EU); Date: Fri, 31 Dec 2004 20:22:04 -0500; I just wanted to share some anecdotal data on Orion/Acom compatibility. For the past few months I've been using the Orion/Acom2000A combination in qsk/keying loop mode with no problems whatsoever. Th; /archives//html/TenTec/2004-12/msg01355.html (7,711 bytes)
2. Re: [TenTec] Acom/Orion (score: 1): Author: "Michael Tope" <W4EF@dellroy.com>; Date: Fri, 31 Dec 2004 18:13:39 -0800; It might be the extra group delay from the filter, Barry. You might try substituting a long piece of coax for the Dunestar filter. A generic 5 pole high-pass with a 1.7 MHz cutoff will have about 100; /archives//html/TenTec/2004-12/msg01357.html (9,563 bytes)
3. Re: [TenTec] Acom/Orion (score: 1): Author: n1eu@netscape.net (Barry N1EU); Date: Fri, 31 Dec 2004 21:29:15 -0500; The problem and solution are also present on the higher bands and reducing drive has no effect. I'm just going to leave the filter inline, where it normally sits. I reported this info to potentially; /archives//html/TenTec/2004-12/msg01358.html (10,768 bytes)

Current List: 1 - 3
Page: [1]