Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TenTec\]\s+An\s+example\s+of\s+changing\s+Orion\s+firmware\s+to\s+meetexpectations\s+of\s+the\s+operator\.\s*$/: 7 ]

Total 7 documents matching your query.

1. Re: [TenTec] An example of changing Orion firmware to meetexpectations of the operator. (score: 1)
Author: "Grant Youngman" <nq5t@comcast.net>
Date: Thu, 08 Jul 2004 09:19:49 -0500
I kind of liked this idea. It was simple to grasp after a few minutes of taking the time to understand it. As someone else pointed out yesterday, there are good reasons for bandwidth and/or pbt and
/archives//html/TenTec/2004-07/msg00206.html (9,358 bytes)

2. Re: [TenTec] An example of changing Orion firmware to meetexpectations of the operator. (score: 1)
Author: "Ken & Linda Burrough" <w8keb@1st.net>
Date: Thu, 8 Jul 2004 13:17:45 -0400
Scott don't change the Orion Firmware. If you must change the Firmware then please make it so I can default back to the present firmware set up. Ken/w8keb No, that is not correct - it was by design.
/archives//html/TenTec/2004-07/msg00214.html (11,483 bytes)

3. Re: [TenTec] An example of changing Orion firmware to meetexpectations of the operator. (score: 1)
Author: Duane A Calvin <ac5aa@juno.com>
Date: Thu, 8 Jul 2004 14:46:55 -0500
I appreciate the design point of having two receivers, not two VFO's, and the potential flexibility that this provides us as users. This does bring up the difficulty of how to manage the added comple
/archives//html/TenTec/2004-07/msg00219.html (8,936 bytes)

4. Re: [TenTec] An example of changing Orion firmware to meetexpectations of the operator. (score: 1)
Author: ac5e@comcast.net
Date: Thu, 08 Jul 2004 20:29:33 +0000
Well, while Duane has a point I would personally prefer the option of having the frequency, mode, and bandwidth all transfer with the press of a button. The O's second receiver is plenty good enough
/archives//html/TenTec/2004-07/msg00222.html (11,042 bytes)

5. Re: [TenTec] An example of changing Orion firmware to meetexpectations of the operator. (score: 1)
Author: "Merle Bone" <merlebone@charter.net>
Date: Thu, 8 Jul 2004 19:29:40 -0500
Phil Howlett said: " the way the radio is now it is user vicious." The Orion is my first Ten-Tec rig and I enjoy reading this reflector and often learn things from it. I have to say that I think Phil
/archives//html/TenTec/2004-07/msg00240.html (10,473 bytes)

6. Re: [TenTec] An example of changing Orion firmware to meetexpectations of the operator. (score: 1)
Author: Duane A Calvin <ac5aa@juno.com>
Date: Thu, 8 Jul 2004 21:59:24 -0500
Hmm, this is odd. I'm still waiting for someone to explain why this simple quick QSX function is somehow counter to the Orion's new design point? One is a design point, the other is a usability featu
/archives//html/TenTec/2004-07/msg00249.html (12,121 bytes)

7. Re: [TenTec] An example of changing Orion firmware to meetexpectations of the operator. (score: 1)
Author: "Mark Erbaugh" <mark@microenh.com>
Date: Mon, 12 Jul 2004 09:57:40 -0400
Scott, How does one define what is a property of the VFO and what is the property of the receiver? I would assume from the design that BW and PBT are functions of the receiver that the VFO should be
/archives//html/TenTec/2004-07/msg00347.html (9,261 bytes)


This search system is powered by Namazu