Replies: 6 comments 2 replies
-
Sorry... Forgot to add computer side info: MacBook Pro 14,1 I see that 0.12.0 is available, but don't see anything mentioning this in the change log, nor do I see any way to update qDMR to that version to try. |
Beta Was this translation helpful? Give feedback.
-
I did see that 0.12.0 is available on Homebrew, so I'm installing that right now. |
Beta Was this translation helpful? Give feedback.
-
On 0.12.0, I'm getting a read error. This causes the entire codeplug read to be disregarded. |
Beta Was this translation helpful? Give feedback.
-
This explains it. The pre-0.12 version did not check the model. It assumed
a GD77 or RD-5R, because the other devices weren't supported back then.
However, the 0.12.0 does not support OpenGD77 on the UV380. You have to
wait for the 0.12.1 coming soon for that.
W0SZH ***@***.***> schrieb am Mi., 1. Jan. 2025, 16:23:
… I did see that 0.12.0 is available on Homebrew, so I'm installing that
right now.
—
Reply to this email directly, view it on GitHub
<#534 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACE6EYLHLSPIQZLLBLK53D2IQCABAVCNFSM6AAAAABUOW7WXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRXGA2DSMZUGM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Thanks. I'll be eagerly awaiting that release. The CPS software for this radio is the only reason I still have a Windows machine and I'm desperately wanting to ditch that and just stick with my *NIX computers. Thanks Hannes! |
Beta Was this translation helpful? Give feedback.
-
Just checked to see, and was able to get the new release. Thanks for do the work to get the device supported. I'm able to pull the existing code plug and all looks good. Appreciate all the hard work. |
Beta Was this translation helpful? Give feedback.
-
I'm using a TYT MD-UV390 with OpenGD77 (build 20240908143155). When I pull the existing codeplug, I'm seeing a lot of strange characters--like there's an encoding issue. The really strange thing, is that my first large block of channels are all analog. It's only once I start with digital channels that the issue pops up--which makes me think it could be a memory block not being what is expected, as not only are the channel names mangled, the Tx/Rx frequencies, timeout, Rx only, and various other settings are no longer set properly.
Here is the start of my channels, which all look good:
This is where things start going wrong. Once there's an issue, even my analog channels are now not showing correctly:
All other DMR data also appears to be mangled/not the correct memory offset:
Beta Was this translation helpful? Give feedback.
All reactions