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

Results:

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

Total 1501 documents matching your query.

221. Re: [Orion] Re: [TenTec] Topband: BDR redux (score: 1): Author: Sinisa Hristov <shristov@ptt.yu>; Date: Thu, 05 Feb 2004 18:41:06 -0500; This is true. It's certainly better to have a separate AGC threshold, as in Orion. Unfortunately, AGC Threshold control on Orion is an ergonomic disaster. It should have had a knob assigned to itself; /archives//html/Orion/2004-02/msg00008.html (7,526 bytes)
222. Re: [Orion] Re: [TenTec] Topband: BDR redux (score: 1): Author: "Grant Youngman" <nq5t@comcast.net>; Date: Thu, 05 Feb 2004 17:52:59 -0600; The crash of the Hindenburg was a disaster. The threshold control can be set up to be one button push away ... Not sure I understand why adjusting THRESHOLD should have any impact on S-Meter indicat; /archives//html/Orion/2004-02/msg00009.html (7,676 bytes)
223. Re: [Orion] Re: [TenTec] Topband: BDR redux (score: 1): Author: Sinisa Hristov <shristov@ptt.yu>; Date: Thu, 05 Feb 2004 19:26:57 -0500; That's exactly too much for me :-) I'm not sure either, just a though that it's position should be indicated in relation to signal levels presented on the S meter. Those 5-digit microvolts (with ~1 d; /archives//html/Orion/2004-02/msg00010.html (7,475 bytes)
224. [Orion] Orion raspy on CW? (score: 1): Author: "Charlie, W0YG" <w0yg@myawai.com>; Date: Mon, 9 Feb 2004 14:10:59 -0000; I have a neighbor, well I say neighbor but he must be 15 miles away, that complains about my raspy note on CW with my Orion. I don't hear it when listening to the monitor nor does another neighbor, j; /archives//html/Orion/2004-02/msg00011.html (6,996 bytes)
225. [Orion] Orion raspy on CW (score: 1): Author: Bill Tippett <btippett@alum.mit.edu>; Date: Mon, 09 Feb 2004 11:49:03 -0500; complains about my raspy note on CW with my Orion. Possibly the problem is caused by leaving his NB on? If your neighbor 1 mile away doesn't hear it, it is probably not there but in the 756 RX for so; /archives//html/Orion/2004-02/msg00012.html (6,535 bytes)
226. [Orion] Re: Orion raspy on CW? (Charlie, W0YG) (score: 1): Author: "D.W. Fearn" <dwfearn@dwfearn.com>; Date: Mon, 09 Feb 2004 15:04:23 -0500; A few months ago I was getting reports of awful keying with my Orion. Some described it as "fractured" and un-readable. On 80M one guy about 200 miles away said I had key clicks over the entire band.; /archives//html/Orion/2004-02/msg00013.html (9,517 bytes)
227. [Orion] Re: Orion keying (score: 1): Author: "bob" <finger@goeaston.net>; Date: Tue, 10 Feb 2009 05:58:45 -0500; I too had a "keying failure" on my Orion. When sending a string of dahs the output falls off and comes back up again. It was somewhat visible on the ALC indidcator, but was very obvious when viewed o; /archives//html/Orion/2004-02/msg00014.html (6,984 bytes)
228. [Orion] Re: Orion Digest, Vol 5, Issue 4 (score: 1): Author: "Charles W. Shaw" <chas.shaw@verizon.net>; Date: Tue, 10 Feb 2004 18:09:39 +0000; Bob, W9GE wrote: I too had a "keying failure" on my Orion. When sending a string of = dahs the output falls off and comes back up again. It was somewhat = visible on the ALC indidcator, but was very; /archives//html/Orion/2004-02/msg00015.html (7,762 bytes)
229. [Orion] CW anomaly? (score: 1): Author: Ralph Irish <w8roi@peoplepc.com>; Date: Tue, 10 Feb 2004 17:05:38 -0500; To all The closest thing to a 'defect' in the CW system I've run across is that when sending something from the CW memory, and adjusting anything else from the "MULTI" button, the CW speed changes. I; /archives//html/Orion/2004-02/msg00016.html (6,543 bytes)
230. [Orion] Raspy CW note (score: 1): Author: "Charlie, W0YG" <w0yg@myawai.com>; Date: Wed, 11 Feb 2004 16:31:28 -0000; OK I have a better grip on what is termed "raspy". I had another friend about a mile away, get on the phone with me while I transmitted on 160M. I tested my rig both barefoot and with a full legal li; /archives//html/Orion/2004-02/msg00017.html (8,471 bytes)
231. [Orion] Orion's AGC THRESHOLD is in error by 21 (9) dB (score: 1): Author: Sinisa Hristov <shristov@ptt.yu>; Date: Wed, 11 Feb 2004 13:34:15 -0500; Orion's AGC Threshold control is useful for avoiding AGC action on noise peaks. Such an action tends to intermodulate a weak signal with noise, significantly reducing readability. The same benefit wa; /archives//html/Orion/2004-02/msg00018.html (8,629 bytes)
232. [Orion] Orion keying (score: 1): Author: "bob" <finger@goeaston.net>; Date: Tue, 10 Feb 2009 05:42:39 -0500; I too had a "keying failure" on my Orion. When sending a string of dahs the output falls off and comes back up again. It was somewhat visible on the ALC indidcator, but was very obvious when viewed o; /archives//html/Orion/2004-02/msg00019.html (6,962 bytes)
233. [TenTec] Orion Update (score: 1): Author: "Jim" <ke4wy@zoomtown.com>; Date: Wed, 11 Feb 2004 17:49:04 -0500; Orion 1.369 update is available for download. Jim _______________________________________________ TenTec mailing list TenTec@contesting.com http://lists.contesting.com/mailman/listinfo/tentec; /archives//html/Orion/2004-02/msg00020.html (6,643 bytes)
234. [Orion] Orion 1.369 available now (score: 1): Author: Bill Tippett <btippett@alum.mit.edu>; Date: Wed, 11 Feb 2004 17:52:16 -0500; http://www.rfsquared.com/Orion/orionmain.htm Version 1.368 - Not Released - Expanded 60M band to 5.425 to include Norways 5.410 and 5.420 allocations. - Modified tuning code to reduce the tuning stut; /archives//html/Orion/2004-02/msg00021.html (7,472 bytes)
235. [TenTec] Orion AGC settings (score: 1): Author: Bill Tippett <btippett@alum.mit.edu>; Date: Thu, 12 Feb 2004 09:02:28 -0500; W4ZV for underlining their significance. For some reason Sinisa posted a third on the Orion reflector, so here are all three together (in order): <http://dayton.akorn.net/pipermail/tentec/2004-Februa; /archives//html/Orion/2004-02/msg00022.html (10,522 bytes)
236. [Orion] Version 1.369 installed (score: 1): Author: "Charles W. Shaw" <chas.shaw@verizon.net>; Date: Thu, 12 Feb 2004 17:35:47 +0000; Howdy to All, Last night I installed 1.369, but not without some frustration. Each time I started the setup, it would go part way and then fail. Each time I shut down and began again, it would go fur; /archives//html/Orion/2004-02/msg00023.html (7,167 bytes)
237. [Orion] Orion control with RigBlaster Pro? (score: 1): Author: Martin Ewing <martin@aa6e.net>; Date: Sat, 14 Feb 2004 13:15:25 -0500; Hello, all! Does anyone have the magic jumpering that allows a RigBlaster Pro to control the T/R mode on the Orion? This ought to be easy, but the documentation is not clear on how to get a simple pu; /archives//html/Orion/2004-02/msg00024.html (6,701 bytes)
238. [Orion] partial communications with radio (score: 1): Author: Eric Scace K3NA <eric@k3na.org>; Date: Sat, 14 Feb 2004 17:26:08 -0500; I am attempting to stuff new firmware into my new Orion. The update application on the computer complains that communication is lost with the radio. The port is set for 56k, 1 stop bit, no parity, an; /archives//html/Orion/2004-02/msg00025.html (7,211 bytes)
239. [Orion] orion serial port (score: 1): Author: HeathlinerSB@aol.com; Date: Sat, 14 Feb 2004 17:26:39 EST; Hi all! I need help to configure the serial port for TT Orion. Page 29 of the manual tells only, that there is one. But i need following data: Speed: How many Bd? Data bits? Stop bits (1 or 2) Parity; /archives//html/Orion/2004-02/msg00026.html (6,228 bytes)
240. RE: [Orion] partial communications with radio (score: 1): Author: "BarryG" <n1eu@myway.com>; Date: Sat, 14 Feb 2004 20:13:32 -0500 (EST); Eric, my WriteLog settings are "AUTO" for baud rate and CommPTT is "NO". I didn't have to make any other settings and my INI file doesn't have settings for the COM port I'm using (COM5). For N1MM Log; /archives//html/Orion/2004-02/msg00027.html (8,104 bytes)

Current List: 221 - 240
Page: [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]