Over last weekend I experienced Alan's beacon first hand. It was configured to broadcast every few minutes. The prompt did not identify it as a beacon, it sounded like Alan testing. When I called CQ on 7.177 it immediately responded to me with the same prompt. This was very confusing to me, until I figured out what was going on.
On the activity day weekend (and possibly at other times) in VK Alan's beacon was effectively blocking any use of FreeDV 7.177. Other users have had to shift +/- 3kHz in order to use FreeDV on 40m. I have emailed Alan several times asking him to disable his beacon or adjust it such that it does not interfere with other users of the band. Although I haven't checked the local regulations, I imagine a software device configured in such a way that it interferes with other users of the band is not permitted in Australia or any other country. BTW this is not https://github.com/drowe67/freebeacon - this is Alan's derivative. Despite several invitations over many years his code has not been reviewed and is not associated with the core FreeDV team. FreeBeacon does not broadcast, and would only respond if triggered by a special txt string. And it should be configured to identify itself. Can I suggest we close this topic? I don't think it warrants our time and attention either on this mailing list, or over the air. Just like FreeDV on 7.177 in VK, this topic seems to have taken over the list discussion, at a time when there are for more interesting initiatives going on. - David On Wed, 2022-02-23 at 12:44 -0800, Mooneer Salem wrote: > Hi Al, > > I added the qualifier "per FCC rules" in my last email to indicate > that this is a US specific thing. Other countries, of course, have > different rules. > > Anyway, regardless of where we all live, I'm sure we can agree that > it's just as important to be good stewards of our allocated RF > spectrum. Thus, we should do everything possible to minimize > interference to other users, FreeDV and non-DV alike. Something that > doesn't transmit back and simply uploads recordings somewhere seems > like it'd be the least likely to interfere with people, at least IMO. > > Thanks, > > -Mooneer K6AQ > > On Wed, Feb 23, 2022 at 12:36 PM Al Beard <bear...@unixservice.com.au > > wrote: > > Guys, > > > > This is an INTERNATIONAL email group, I'm in Australia and not > > subject to FCC rules. > > So please, please think outside the square! At least mention your > > country or state > > your callsign. > > > > We are trying to explore here, new technology! > > > > Alan VK2ZIW > > > > On Wed, 23 Feb 2022 13:46:37 -0500, David Tiller wrote > > > > As for CW, IIRC it's allowed everywhere on the ham bands per > > FCC rules. > > > > > > > > CW sent by a locally-controlled station is legal everywhere. CW > > sent by an automatically-controlled digital station (for purposes > > other than identification) is suspect. The part I mentioned > > specifically says RTTY or digital modes. CW is it's own animal, > > IIRC. Neither fish nor fowl, Data or Phone. > > > > > > > > > > > > On Feb 23, 2022, at 1:01 PM, Mooneer Salem <moon...@gmail.com> > > > wrote: > > > > > > > As for CW, IIRC it's allowed everywhere on the ham bands per > > > FCC rules. > > > > > > > > > > --------------------------------------------------- > > 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 _______________________________________________ Freetel-codec2 mailing list Freetel-codec2@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freetel-codec2
