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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TenTec\]\s+CW\s+keying\s+weight\s*$/: 4 ]

Total 4 documents matching your query.

1. [TenTec] CW keying weight (score: 1): Author: mark@microenh.com (Mark Erbaugh); Date: Wed, 16 Jan 2002 08:07:31 -0500; This is for the serious CW ops out there. I'm working on a rig control program for the Pegasus. The Pegasus lets you adjust the length of the dits, dahs and element spaces independently. I have figur; /archives//html/TenTec/2002-01/msg00216.html (7,773 bytes)
2. [TenTec] CW keying weight (score: 1): Author: cjm@qvssoftware.com (Carl Moreschi); Date: Wed, 16 Jan 2002 09:12:11 -0500; Mark, The CW weight adjustment is to make up for slow keying characteristics of a particular transceiver. What you are striving for is the end result coming out of the transceiver is a perfect 3 to 1; /archives//html/TenTec/2002-01/msg00217.html (9,061 bytes)
3. [TenTec] CW keying weight (score: 1): Author: N4NT@chartertn.net (Mike Hyder); Date: Wed, 16 Jan 2002 09:18:45 -0500; Dot length = space length. Dash length = length of two dots AND the space between them (3 dot lengths total). A pretty fair speed check can be made by counting dashes for five seconds. Setting weight; /archives//html/TenTec/2002-01/msg00218.html (9,343 bytes)
4. [TenTec] CW keying weight (score: 1): Author: n4lq@iglou.com (Steve Ellington); Date: Wed, 16 Jan 2002 17:23:21 -0500; Mark I think the bottom line is that you're going to have to make the weight adjustable over the range of 'choppy as a chicken' to 'everything runs together'. The only way to really tell what's comin; /archives//html/TenTec/2002-01/msg00223.html (9,000 bytes)

Current List: 1 - 4
Page: [1]