Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Trlog\]\s+Radio\s+interface\s+work\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Trlog\]\s+Radio\s+interface\s+work\s*$/: 4 ]

Total 4 documents matching your query.

1. [Trlog] Radio interface work (score: 1): Author: Tree <tree@kkn.net>; Date: Mon, 17 May 2004 14:11:36 -0500; Well - as you no doubt have noticed, there haven't been any updates for awhile. I am continuing to work on the major effort of fixing the radio interface issues with a more elegant solution. Unfortun; /archives//html/TRLog/2004-05/msg00018.html (7,032 bytes)
2. Re: [Trlog] Radio interface work (score: 1): Author: alan.kaul@att.net; Date: Tue, 18 May 2004 02:36:06 +0000; Tree, As long as you are looking at POST, would you consider stripping out frequenncy data (for those of us who collect it in the raw log) and recombine it with the mhz info from the cabrillo log to; /archives//html/TRLog/2004-05/msg00021.html (8,505 bytes)
3. Re: [Trlog] Radio interface work (score: 1): Author: "George & Tammy Perkins" <gperkins@tampabay.rr.com>; Date: Mon, 17 May 2004 23:42:29 -0400; I agree with this request... that would be awesome if this request could happen... right now it is a very manual process to capture this info... If your taking requests, I second this motion! Thanks; /archives//html/TRLog/2004-05/msg00022.html (10,172 bytes)
4. RE: [Trlog] Radio interface work (score: 1): Author: "Mike Gilmer" <n2mg@eham.net>; Date: Mon, 17 May 2004 23:53:50 -0400; It would be a "most excellent" thing if the complete frequency data were automatically captured and made available to, and recorded in, the Cabrillo log. As it stands, if one does not turn on the cor; /archives//html/TRLog/2004-05/msg00023.html (8,502 bytes)

Current List: 1 - 4
Page: [1]