Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Omni\s+V\s+\&\s+FSK\s+Conclusion\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Omni\s+V\s+\&\s+FSK\s+Conclusion\s*$/: 3 ]

Total 3 documents matching your query.

1. [RTTY] Omni V & FSK Conclusion (score: 1): Author: edw3nr at nexband.com (Ed); Date: Mon Apr 7 18:25:05 2003; First off, thanks to everyone that was good enough to answer and pass along advice. Also to the ops that had to listen to my solid carrier. Now to the "fix" for the Omni V and FSK. Looked at the sche; /archives//html/RTTY/2003-04/msg00050.html (7,662 bytes)
2. [RTTY] Omni V & FSK Conclusion (score: 1): Author: wa9als at starband.net (WA9ALS - John); Date: Mon Apr 7 20:18:02 2003; the call is In the manual for Brian Beezley's RITTY program, he mentions that you MIGHT be able to just send the com port output to the FSK pin without a transistor switch. I've done that, through a; /archives//html/RTTY/2003-04/msg00052.html (7,492 bytes)
3. [RTTY] Omni V & FSK Conclusion (score: 1): Author: chen at mac.com (Kok Chen); Date: Mon Apr 7 21:20:47 2003; There is a big difference here. While the Yaesu and Icom rigs use a simple pull-down signal (and may or may not work, or blow up, when feeding them with RS-232 signals) the Ten-Tec Omni rigs' FSK inp; /archives//html/RTTY/2003-04/msg00054.html (7,235 bytes)

Current List: 1 - 3
Page: [1]