-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenGD77 channels power #507
Comments
First of all, thanks for reporting. It is certainly a bug. Unfortunately, I don't know, where the global power setting is stored and I don't have a OpenGD77 radio at hand. But you can help.
If the global power setting is stored in the codeplug on the radio, the difference should be visible. |
Also, I have fixed the power decoding of the channel power setting in the branch |
Ok, I'll try tomorrow. |
I did it... 0 size of diff. |
About 507-opengd77-channels-power. |
Yes, that was a bug in de- and then reencoding of the channels. You need to
reset all channels to "default", because they are now all explicitly set to
500mw.
Andrey ***@***.***> schrieb am Mi., 25. Dez. 2024, 14:59:
… About 507-opengd77-channels-power.
I read and wrote back codeplug. All channels were master power, became 500
mW. In Qdmr were default power, became low power, and no default.
—
Reply to this email directly, view it on GitHub
<#507 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACE6E7ECATVIXTU6RTB5KL2HK24JAVCNFSM6AAAAABUEXUSYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRRHEYDEMBWHE>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
Concerning the 0-diff. This means, the FW stores these settings somewhere
else. Those global settings should be stored in the codeplug. Maybe, we
should suggest that to the OpenGD77 guys.
Andrey ***@***.***> schrieb am Mi., 25. Dez. 2024, 14:19:
… I did it... 0 size of diff.
Another case, change the settings of one channel and compare?
—
Reply to this email directly, view it on GitHub
<#507 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACE6EYR3RJT2BDNTAEDSAT2HKWGVAVCNFSM6AAAAABUEXUSYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRRHA4DQOBUGQ>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
Global power settings not stored in codeplug. I change master power, restored settings -> download sawed codeplug (In Windows OpenGD CPS), and master power not changed. |
Qdmr does not read global power settings correctly. I change it, but Qdmr read High always. |
It clearly doesn't work correctly. I set default power on the channel, write to the radio, read from the radio and get low but not default. It seems that the channel power is read correctly, but is written incorrectly. If I change the channel settings in the radio, the program read correctly. |
Since the global power setting is not stored by the firmware inside the codeplug (for some unknown reason), I cannot read it. So, I default to "high". But since it is not stored, I cannot set it too. Therefore, this setting has no effect here. I consider this a bug in OpenGD77, I would make much more sense, to store the global power setting within the codeplug, if it is referenced (inside the channel settings) there. |
Thanks for this observation, it helps a lot. |
Added a unit test for this, qdmr appears to be self-consistent. That is, it is written such that the default power is read by qdmr correctly. This means, that the encoding of this setting is more complicated and the firmware interferes with the settings written to the device. |
Okay, can reproduce it in unit tests. It has nothing todo with the OpenGD77 codeplug but with the preprocessing of the codeplug. |
Should be fixed in the |
Yes, it's works now!!! |
Hi.
OpenGD77 have "Master" settings in channels power option. Master-min-low-midle-hi-max. After first codeplug upload from Qdmr I have min power of all channels now. Master must set as default, if power not setting in channels options.
That's great, do everything from Linux, no need to use Win :)
The text was updated successfully, but these errors were encountered: