Hi Alan, As the QSO Finder allows you to enter text after the frequency, I suggest adding an indication that freebeacon is running when you log in (e.g. "7.187 FB"). That won't need any updates to the QSO Finder or freedv.org website and will let the community ensure that it won't cause problems.
Regardless, I still highly recommend that you have it require a specific sequence of characters in the text string (not just one) to retransmit as unless PSK Reporter support is enabled, the text field is not sufficiently reliable. Thanks, -Mooneer K6AQ On Wed, Feb 23, 2022 at 2:09 AM Al Beard <bear...@unixservice.com.au> wrote: > *Hi Mooneer,* > > *I'd be happy with 10KHz up and that mentioned on QSO.freedv.org > <http://QSO.freedv.org> and www.freedv.org <http://www.freedv.org> so it > becomes "known".* > > *On the subject of trigger strings, with the error rate and still > acceptable audio, the trigger string* > *needs to be as short as possible, one character, not used in callsigns, > eg. @ or #.* > > *This also needs to be on our websites for new users to see.* > > *Please do so on the "digitalvoice" group.* > > *I truly don't want to cause interference on the "simplex" channel.* > > *BTW: my freebeacon here recorded about eight QSOs from the Activity Day:* > *www.unixservice.com.au/parrot/2020feb/ > <http://www.unixservice.com.au/parrot/2020feb/>* > *7177KHz mode 700D* > > *Mostly stations 600+Km away from me, very good audio.* > > *73* > > *Alan VK2ZIW* > > > *On Tue, 22 Feb 2022 23:17:39 -0800, Mooneer Salem wrote* > > Hi Alan, > > > > I'm CCing to digtialvoice so you can get additional feedback. > > > > Re: separate frequency--one option is to simply make the "standard" > freebeacon frequency 10KHz above the FreeDV frequencies (e.g. 14.246 MHz > instead of 14.236). We'd have to see how much impact that'd have on anyone > already using those, though. > > > > As for the trigger string, it might be sufficient simply to enable PSK > Reporter support in the FreeDV application. As that encodes in a manner > different than the normal text string, I would think that would cause > freebeacon to never match on any transmissions. However, if that's not > actually the case, it's possible we can figure out a way for it to detect > that encoding and auto-ignore. > > > > Thanks, > > > > -Mooneer K6AQ > > > > On Tue, Feb 22, 2022 at 3:22 PM Al Beard <bear...@unixservice.com.au> > wrote: > > >> >> >> > *Thanks,* >> > In the FreeDV Activity Day Announcement can we have an alternative >> frequency mentioned >> > for "freebeacon" and perhaps to require the "trigger" string to have >> say "#", never found in callsigns. >> > >> > My "freebeacon" here has never been set to have no trigger string. >> > But if it is triggered it's because it's received the string. That >> string is currently one character. >> > (and settable on the command line) >> > >> > PSK Reporter >> > =========== I don't expect my transmissions from here QF56HG to go >> anywhere outside Australia >> > or New Zealand and as such I have regularly mentioned my presence on >> VKspotter under "HF". >> > https://www.vkspotter.com/?action=home >> > >> > David here has acknowledged hearing my ident transmission so confirmed >> his Rx and decoding >> > the signal, is working. That's what beacons are for. >> > >> > Alan VK2ZIW >> > >> >> * > > * >> > *On Tue, 22 Feb 2022 13:03:50 +1100, David Grove wrote* >> > > Hi David & Mooneer >> > > >> > > First of all [UTF-8?]– thank you to both of you for all your work >> in advancing FreeDV/Codec2. [UTF-8?]It’s very much appreciated >> > > >> > > I like the idea of having a three-monthly activity day that, where >> feasible, occurs just after other major activities (Hamventions etc) >> > > >> > > On the activity day, I tried calling CQ on 7.177 MHz and 14.236 MHz >> on several different modes from my home QTH (QRN S3-5) a few times with no >> success. >> > > >> > > I also happened to be monitoring QSO finder when David, VK5DGR and >> Mel, K0PFX were testing on 14.246 MHz. Unfortunately, nothing was heard at >> my end on that frequency at the time. >> > > >> > > At the end of the activity day, I checked PSK reporter and was unable >> to find any reports of my callsign on FreeDV >> > > >> > > I did however hear Alan, [UTF-8?]VK2ZIW’s parrot on a couple of >> occasions on the day. However, Alan is about 20 Km from me, so the 40m >> signal was marginal >> > > >> > > Nevertheless, [UTF-8?]I’ll keep on trying to reduce the QRN levels >> at my place and [UTF-8?]I’ll keep installing the new versions of FreeDV >> as [UTF-8?]they’re released >> > > >> > > [UTF-8?]I’m looking forward to the next activity day >> > > >> > > Thanks again >> > > >> > > Regards >> > > >> > > >> > > David Grove [UTF-8?]– VK2DWG >> > > >> > > -----Original Message----- >> > > From: david <da...@rowetel.com> >> > > Sent: Tuesday, 22 February 2022 12:32 >> > > To: freetel-codec2@lists.sourceforge.net >> > > Subject: Re: [Freetel-codec2] Fwd: [Announcement] FreeDV Activity Day >> - February 19-20, 2022 >> > > >> > > > 1. It looks like May 28th-29th will be best for the next one as >> Dayton >> > > > is the weekend prior and there seem to be a fair number of other >> > > > contests across the rest of the month. Does that sound reasonable? >> > > >> > > Every 3 months sounds good. Like this time, I'll attempt to have a >> new experimental waveform/codec to try out in May. >> > > >> > > > 2. If you operated this one, how did it work out for you? >> > > >> > > I managed to receive Mel, k0pfx long path 20M here in South >> Australia, 1-4dB SNR on 700D. I positioned myself in a campground 200km SE >> of Adelaide (Parnka Point, in an area known as the Coorong) with sub S0 >> noise on 20m. Simple end fed dipole. >> > > >> > > I also monitored/took part in a few VK QSOs and was pleased to see >> the modems handling the HF channel quite well. >> > > >> > > Pretty happy about that :-) >> > > >> > > Thanks for organising the event Mooneer :-) >> > > >> > > - David >> > > >> > > >> > > >> > > _______________________________________________ >> > > Freetel-codec2 mailing list >> > > Freetel-codec2@lists.sourceforge.net >> > > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 >> > >> > --------------------------------------------------- >> > Alan VK2ZIW >> > Before the Big Bang, God, Sela. >> > OpenWebMail 2.53, nothing in the cloud. >> > >> > _______________________________________________ >> > Freetel-codec2 mailing list >> > Freetel-codec2@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 >> > > > > > > --------------------------------------------------- > Alan VK2ZIW > Before the Big Bang, God, Sela. > OpenWebMail 2.53, nothing in the cloud. > > _______________________________________________ > Freetel-codec2 mailing list > Freetel-codec2@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 >
_______________________________________________ Freetel-codec2 mailing list Freetel-codec2@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freetel-codec2
