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

Results:

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

Total 3 documents matching your query.

1. [TRLog] Packet splits (score: 1): Author: n6tr@teleport.com (Tree N6TR); Date: Tue, 14 Oct 1997 11:10:08 -0700 (PDT); I am working on the routine to decode QSX information from packet spots. This is a tedious procedure to write - making sure any of the "accepted" ways of recording this information will work. I am pl; /archives//html/TRLog/1997-10/msg00052.html (7,140 bytes)
2. [TRLog] Packet splits (score: 1): Author: vr2bg@harts.org.hk (VR97BrettGraham); Date: Wed, 15 Oct 1997 02:23:54 +0000; Syntax I've seen for a specific split: "QSX:+5", "QSX +5", "QSX up", "QSX up 5", "up" (which doesn't seem to mean 1 kHz anymore), "up 5". For spread splits: "QSX:+5 to +7", "QSX +5 to +7", "up 5 to 7; /archives//html/TRLog/1997-10/msg00057.html (7,675 bytes)
3. [TRLog] Packet splits (score: 1): Author: n6tr@teleport.com (Tree N6TR); Date: Mon, 20 Oct 1997 08:53:33 -0700 (PDT); Last night - TR learned how to deal with packet split information. It will take the info and insert it in the band map. An x will appear after the frequency to indicate QSX data is included. If you s; /archives//html/TRLog/1997-10/msg00092.html (7,337 bytes)

Current List: 1 - 3
Page: [1]