search

armel / uv-k5-firmware-custom

This is a fork of Egzumer https://github.com/egzumer/uv-k5-firmware-custom
Apache License 2.0
345 stars 44 forks source link

feature request: TX-Lock custom range and/or PMR 446 + Freenet #217

Closed joernschmidt93 closed 1 month ago

joernschmidt93 commented 1 month ago

Hi,

It would be nice to have the possibility to customize the TX-lock range in chirp or maybe use one of the channel-mode scan-list as a TX-whitelist.

If this feature isn't possible, it would be great to have a selection for PMR446 + Freenet in the hidden menu.

In germany there is not only PMR 446 but also Freenet (2m-Band) as a license free frequency range and it would be nice to use it, without interrupting other frequencies by accident.

Channel 1 | 149,0250 MHz Channel 2 | 149,0375 MHz Channel 3 | 149,0500 MHz Channel 4 | 149,0875 MHz Channel 5 | 149,1000 MHz Channel 6 | 149,1125 MHz

armel commented 1 month ago

Hi,

This is a good question. Well, could you take a look to my last survey on my Youtube channel ?

Armel F4HWN.

joernschmidt93 commented 1 month ago

Hi Armel,

thanks for the quick response :)

just read your survey on youtube, the solution you suggested sounds great, if you can make it work this way, it would be just what i want.

I really appreciate what you are doing here

Joern

armel commented 1 month ago

Hi Joern,

Thank you. I'll work on this for the next release. So stay tuned :)

Armel F4HWN.

Titivi09 commented 1 month ago

100

Envoyé à partir de Outlook pour Androidhttps://aka.ms/AAb9ysg

From: Armel FAUVEAU @.> Sent: Wednesday, July 31, 2024 4:09:19 AM To: armel/uv-k5-firmware-custom @.> Cc: Subscribed @.***> Subject: Re: [armel/uv-k5-firmware-custom] feature request: TX-Lock custom range and/or PMR 446 + Freenet (Issue #217)

Hi Joern,

Thank you. I'll work on this for the next release. So stay tuned :)

Armel F4HWN.

— Reply to this email directly, view it on GitHubhttps://github.com/armel/uv-k5-firmware-custom/issues/217#issuecomment-2259504115, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BGNQM5XVGO357GXJWK5PEM3ZPBBM7AVCNFSM6AAAAABLVGQ7RCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJZGUYDIMJRGU. You are receiving this because you are subscribed to this thread.Message ID: @.***>

armel commented 1 month ago

Let me explain again...

In past, I added band plans to the F Lock menu to meet various requests: PMR, FRS/GMRS/MURS, etc. But adding new F Lock options always takes up a lot of memory: new options in the F Lock menu, storing frequencies (for the specialists, these are uint32_t each time, so very memory-consuming), etc.

Now, it must be acknowledged that it will be complicated, if not impossible, to offer band plans that could cover and meet all expectations. It's not feasible, as highlighted by the completely legitimate request regarding the addition of Freenet. There are too many variations from one country to another. Worse still, those who would want an LPD band plan would certainly want a PMR band plan as well, at the same time. And nothing has been planned to possibly combine multiple band plans from the F Lock menu. In short, to cut it short, F Lock has got to many huge limitations and is not scalable.

That's because I've removed the PMR and FRS/GMRS/MURS options. Right? Wait for it, and keep in mind that it saved me some memory space. In v3.2, which I've just released, this memory space has enabled me to add an extra channel parameter: TX Lock (just as we already have W/N, BusyC, Compnd, and other parameters).

By default, TX Lock would be set to ON. But, from a new menu (which I called TXLock), it's now possible to switch it to OFF. In that case, it's possible to force transmission, rather than having TX DISABLE, even if the frequency is outside the band plan set from the F Lock menu. Of course, if a frequency is within the band plan set from the F Lock menu and TX Lock is ON, transmission is fully possible. The F Lock band plan take priority here.

Here is a practical example based on users who only operate on the PMR band. I know there are many. Until v3.2, they activated the PMR option from the F Lock menu.

With the new modification, they just need to choose DISABLE ALL from F Lock. In short, lock everything in TX. This helps avoid mistakes.

Then, from Chirp or directly from the radio, they just need to set the TX Lock parameter to OFF on the 16 PMR memory channels to create an exception and allow transmission. The advantage is that if they also want to operate on the LPD band (433 MHz), they could also do so on the concerned channels. The same goes for Freenet, etc. In short, you have the keys, you decide...

I've posted a video explaining the principle... Activate subtitles if needed.

Armel F4HWN.