Re: [digitalradio] Re: Making RSID de rigueur, for Olivia
In fldigi we (well, Stelios did the work) went further: when you turn on RSID, it's still off for PSK-31, PSK-63, RTTY, and CW. It would be good if Patrick FC6TE and Simon HB9DRV would do the same; that is, make it easy to turn on for the uncommon modes, yet have it off for the common ones unless special action is taken. Leigh/WA5ZNU On 02/27/2010 12:23 PM, obrienaj wrote: Gavin, what software are u using ? Mine (Multipsk) can be set to allow RS ID by modes... I can exclude BPSK31 RS ID alerts. Andy K3UK --- In digitalradio@yahoogroups.com, Gaving0...@... wrote: Agreed, it is handy for all digi modes.except psk31..why do people insist on using RSID for modes we all know? It gets damned annoying seeing little boxes popping up on my screen to tell me it has heard a psk31 signal.Qpsk even i could accept, but psk31 using rsid for psk31 is just dumb. So just use it for the more exotic modes please! --- In digitalradio@yahoogroups.com, obrienajk3ukandy@ wrote: I want to embark on a campaign to make RSID de rigueur, for Olivia. It is nice to see Olivia continue to be used as a mode , a very effective mode. However, Olivia users need to remind themselves that there are 10 common sets tones/bw, and despite their appearance in a waterfall, it is not easy to determine which Olivia variant it is. RS ID makes that so much easier. Please use it, it will increase your chances of a someone returning to your CQ. Andy K3UK
Re: [digitalradio] FCC comments further on ROS
On 03/01/2010 04:06 PM, Andy obrien wrote: Thank goodness sanity has prevailed! Leigh/WA5ZNU From Jose's web site http://rosmodem.wordpress.com/2010/03/02/fcc-ros-legal-in-usa/ FCC: ROS LEGAL IN USA By José Alberto Nieto Ros ... According to the technical paper and the audio file attached, we conclude that ROS can not be viewed as Spread Spectrum and it would be encompassed within the section 97.309 (RTTY and data emissions codes). Try Hamspots, PSKreporter, and K3UK Sked Page http://www.obriensweb.com/skedpskr4.html Suggesting calling frequencies: Modes 500Hz 3583,7073,14073,18103, 21073,24923, 28123 . Wider modes e.g. Olivia 32/1000, ROS16, ALE: 14109.7088. Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/digitalradio/ * Your email settings: Individual Email | Traditional * To change settings online go to: http://groups.yahoo.com/group/digitalradio/join (Yahoo! ID required) * To change settings via email: digitalradio-dig...@yahoogroups.com digitalradio-fullfeatu...@yahoogroups.com * To unsubscribe from this group, send an email to: digitalradio-unsubscr...@yahoogroups.com * Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
Re: [digitalradio] Running WSPR and WSJT with VOX-type PTT under Linux
I sent a patch in to WSJT converting from DTR/RTS based RS232 PTT to a serial command string (as an option); I showed sending TX; and RX; for example. They said no thanks, and don't support hamlib either. Not much you can do... Leigh/WA5ZNU This has only been tested on Ubuntu 8.10 with a strong likelihood of being true for other Linux's as well. What the situation is in Windoze land I wouldn't know. The facts are: you can't just leave PTT Port empty, as the programs won't Tx in that case, something needs to be entered that looks sufficiently like a serial port to satisfy the PTT function of the program. Since the ports of WSJT and WSPR I've dealt with for Linux already had /dev/ttyS0 in that field, and they worked even though there was no actual HW behind that, everything looked healthy to me. (I'm using a SignaLink USB since I'm using (mostly) a computer with no built-in RS-232c ports, I could use a USB-RS232C converter at the price of adding to the cable fest, but I choose this route instead) If you want to know how to modify the SignaLink USB to decent specifications look here: http://www.frenning.dk/OZ1PIF_HOMEPAGE/SignaLinkUSB-mods.html The thing which has been giving me the willies, is that either program would invariably fail after a longer (several hours) or shorter period of time - shorter if a failure has already happened on the boot of the OS. Failure mode is invariably address out of bounds in array indexing. This finally let me onto the theory that although the kernel would accept the port manipulation commands, it would just stack them away somewhere until it couldn't handle any more, whereupon the application would be given a bogus reference and wham. I then tried an old trick from my Unix days: in every *nix like OS there is a /dev/null device, a character device that can't ever overflow, because all commands and data sent to it are immediately discarded, sent to the grounding rod so to speak. I'm happy to report that WSPR has just survived my 24 hour torture test (25% Tx/Rx ratio), using /dev/null as the bogus PTT Port, and that I've just started the same test of WSJT7 in WSPR QSO-mode. -- Vy 73 de OZ1PIF/5Q2M, Peter ** CW: Who? Me? You must be joking!! ** email: peter(no-spam-filler)@frenning.dk http://www.frenning.dk/oz1pif.htm Ph. +45 4619 3239 Snailmail: Peter Frenning Ternevej 23 DK-4130 Viby Sj. Denmark ***
