Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TenTec\]\s+Orion\s+v2\.059d\s+\-\s+cw\s+rise\s+time\s+measurements\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TenTec\]\s+Orion\s+v2\.059d\s+\-\s+cw\s+rise\s+time\s+measurements\s*$/: 2 ]

Total 2 documents matching your query.

1. [TenTec] Orion v2.059d - cw rise time measurements (score: 1): Author: "Bob Cunnings" <bob.cunnings@gmail.com>; Date: Sun, 17 Sep 2006 16:58:59 -0600; I wanted to see if v2.059d improved the accuracy of the cw rise/fall time setting, so I took a scope home this weekend and looked: Rise time results in ms, average of 5 measurements: Indicated Measur; /archives//html/TenTec/2006-09/msg00425.html (8,166 bytes)
2. Re: [TenTec] Orion v2.059d - cw rise time measurements (score: 1): Author: Martin AA6E <aa6e@ewing.homedns.org>; Date: Sun, 17 Sep 2006 19:18:43 -0400; Bob, Your data are in pretty fair agreement with my rough measurements on 2.056: http://blog.aa6e.net/2006/07/orion-keyclick-checks.html . Risetime isn't the only thing to consider for keyclick poten; /archives//html/TenTec/2006-09/msg00426.html (9,097 bytes)

Current List: 1 - 2
Page: [1]