I do not think that this should be hardcoded in … Though I appreciate why this has been done. I can foresee further issues down the line especially with the 435 - 438MHz range. Sometimes it is desirable to use a repeater frequency that is offline... OR sometimes these hotspots are being used for "local area repeaters".
OK, I also think should not be hardcoded, but I received many requests about this, and many people are producing problems in satellite frequencies for their bad frequency selections. Could you open an issue about this?, I think this should be discussed and then decide a modification or just remove this.
I too understand the reason for implementing this policy as it protects the international satellite bands for the potential of interference but mmdvm users. I've not researched this in detail, but does every country have a dedicated satellite segment? Here in VK (Australia) this aligns with the WIA Recommended frequencies to avoid to prevent interference. So it's a +1 from me as this is the first thing I request of people who have just used the default frequency (iirc it used to be 435MHz the openspot uses 436MHz) I can also see why some would be unhappy with this move, but it's not too difficult to disable! (for those who are familiar with the code)
Is there indication back to MMDVM Host (e.g. PiStar) that the hotspot can't operate on the selected frequency
I agree that its probably a good idea to disable use of worldwide satellite frequencies, but this change should also be implemented in PiStar, as the majority of users are probably using PiStar and it could give instant feedback to tell them that those frequencies are reserved
I agree Roger, maybe a message from Pi-Star GUI could be nice to inform people when they enter a wrong frequency. With this change you will get a NAK from the modem (and MMDVMHost will not start), and without more information could be confusing for people without experience with MMDVM. Andy Taylor should know this.
Andy and the group
I have been using 433.00 for hotspots , It's already allocated for weak
signal and mixed modes, My Icom will not transmit below 443.000 so I'm
using 445.800, If I'm using my Icom , the allocation on 445.800 is for
simplex ,auxillary links and repeater linking, In my area there is no one
using that frequency, other than a spur from a paging company when there is
a band opening. I also do satellite work on occasion and I can imagine how
much qrm is present from hotspot users?
73 de Rick n9umj
On Sun, Oct 7, 2018 at 1:01 PM Andy CA6JAU ***@***.***> wrote:
OK, I also think should not be hardcoded, but I received many requests
about this, and many people are producing problems in satellite frequencies
for their bad frequency selections. Could you open an issue about this?, I
think this should be discussed and then decide a modification or just
remove this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<7020510#commitcomment-30802266>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACyl1h4GWcOyilhX2GJkBefRMFeQMK5lks5uijOGgaJpZM4XL7DB>
.
This comment has been minimized.
TheOriginalFreddoFrog repliedOct 7, 2018
I do not think that this should be hardcoded in … Though I appreciate why this has been done. I can foresee further issues down the line especially with the 435 - 438MHz range. Sometimes it is desirable to use a repeater frequency that is offline... OR sometimes these hotspots are being used for "local area repeaters".
This comment has been minimized.
juribeparada repliedOct 7, 2018
OK, I also think should not be hardcoded, but I received many requests about this, and many people are producing problems in satellite frequencies for their bad frequency selections. Could you open an issue about this?, I think this should be discussed and then decide a modification or just remove this.
This comment has been minimized.
vk7hse repliedOct 7, 2018
I too understand the reason for implementing this policy as it protects the international satellite bands for the potential of interference but mmdvm users. I've not researched this in detail, but does every country have a dedicated satellite segment? Here in VK (Australia) this aligns with the WIA Recommended frequencies to avoid to prevent interference. So it's a +1 from me as this is the first thing I request of people who have just used the default frequency (iirc it used to be 435MHz the openspot uses 436MHz) I can also see why some would be unhappy with this move, but it's not too difficult to disable! (for those who are familiar with the code)
This comment has been minimized.
juribeparada repliedOct 7, 2018
I am open for suggestions. Please see this: http://www.arrl.org/news/digital-mobile-radio-hotspots-may-be-interfering-with-satellite-uplinks-amsat-reports
This comment has been minimized.
vk7hse repliedOct 8, 2018
I support this move hence my +1
This comment has been minimized.
rogerclarkmelbourne repliedOct 8, 2018
Is there indication back to MMDVM Host (e.g. PiStar) that the hotspot can't operate on the selected frequency
I agree that its probably a good idea to disable use of worldwide satellite frequencies, but this change should also be implemented in PiStar, as the majority of users are probably using PiStar and it could give instant feedback to tell them that those frequencies are reserved
(VK3KYY)
This comment has been minimized.
juribeparada repliedOct 8, 2018
I agree Roger, maybe a message from Pi-Star GUI could be nice to inform people when they enter a wrong frequency. With this change you will get a NAK from the modem (and MMDVMHost will not start), and without more information could be confusing for people without experience with MMDVM. Andy Taylor should know this.
This comment has been minimized.
umj repliedOct 8, 2018