Новости:

Форум Infotex WeaponMod

Просмотр сообщений

В этом разделе можно просмотреть все сообщения, сделанные этим пользователем.


Сообщения - KC1WXU

Страницы: [1] 2 3
1
If you do not receive this error, the update is not required.



Thank you!

2
Should I be downloading the OpenGD77_DM32_20260711_addid_2018.zip in the previous post as an updated version of the Firmware, or is it relatively unchanged from the original 20260711 build?

3
While the original developer is loosely involved, the majority of the work is being done by Koshak and Andynvkz.  Roger is the original OpenGD77 developer and has helped as well, but the DMR and reverse engineering stuff have largely been Koshak and Andy.

4
Roger's answer was to send me back to this website.  He apparently has nothing to do with the OpenDM32, which is the DM32 version of OpenGD77.

He is helping in the background, for example, creating an updated version of the CPS to support the radio.
I think that once the code base is more stable and a github can be set up, we'll be in better shape.
Actually, OpenGD77 has never been able to support certain DMR features like SMS-style messaging and such.  Maybe once this code is stable and can be put in a github, someone can even figure that one out.

Meanwhile, I'm grateful for what we have and what the volunteers here have done.  I can't imagine it is easy.

5
      The official OpenGD77 Forum has been closed to new posts and converted to an archive due to heavy bot traffic

You can reach out to Roger VK3KYY/VK2KYF by email.  He is one of the devs behind the original OpenGD77.

6
How is this firmware improved over the stock firmware?  Are there any added features not in the stock firmware?

I couldn't even program the DM-32 until after switching to this firmware because the factory/stock CPS and firmware were extremely buggy.

OpenGD77 was originally created for the Radioddity GD-77 but also ported to a few Baofeng handsets.  Some clubs in my area have produced codeplugs of all of the analog and DMR repeaters in the region, specifically using Open GD77 because of the simplicity and flexibility over other codeplugs.

For a somewhat older, but detailed list of features, check out this link
https://github.com/LibreDMR/OpenGD77_UserGuide/blob/master/OpenGD77_User_Guide.md

7
OK, that makes sense.

8
Are you saying that the Invalid Channel error is supposed to be there in the "correct" version, or is that an additional issue that needs to be cleared?

9
When changing the modulation type for a channel, the selection is not properly saved or retained. After saving or changing channels, the modulation field either becomes blank/null or automatically defaults to FM+.

I wonder if this is just a display issue or if it actually impacts the modulation type.  This could partially explain the quiet/squelch issues on aviation frequencies if those frequencies are not switching to the AM modulation.

10
I think all of us participate in this in our own ways.  The vast majority of any praise and credit goes to the developers who volunteer their time and energy to do this.

I looked at the original firmware in Ghidra and went cross-eyed.  :D  I thought, hey maybe I can poke around and find something in either the Alpha firmware or the original firmware to help.  But, memory allocations and commands are just something I do not have enough knowledge on right now to make a difference.

Any bugs/testing I do is not a slight against the developers or a demand for functions/fixes.  I've worked in customer service/troubleshooting positions my entire professional career.  Finding, documenting, and troubleshooting bugs is something I DO have some level of skill in.  So, if that is how I can help, it is how I will help.  Granted, my limited radio experience sometimes results in  me making mistakes as well, but the good intent is there.

I don't think any of us expect perfection or a bug-free experience with the alpha, ore even beta releases.  The alpha alone is a vast improvement upon the stock firmware and especially the stock CPS which made programming impossible.

Keep up the great work here everyone!


11
If I had the latest OPENGD77 CPS Source, which I believe is in .net based I can help troubleshoot this array issue. I have been a .net developer for over 20 years. I see this GitHub but it is over 6 years old. Is there 2026 source available?  https://github.com/VR2VYE/OpenGD77CPS. I suppose I could take a shot with ILSpy or JetBrains or a similiar tool if need be. Thanks

You can reach out to the dev directly by email, his name is Roger VK3KYY/VK2KYF.  He is pretty responsive and has been working on this firmware port as well.

Part of the issue is right now OpenDM-32 does NOT fully remove the old firmware but incorporates it in the background in order to retain the calibration data in the stock firmware.  Eventually, the goal is to ONLY be running the OpenDM-32 firmware without the necessity for the original BaoFeng in any capacity.

12
Thank You!

13
I have a very interesting issue that is inconsistent.

I use a KVM switch to use the same monitors and keyboards for both my work and home computers.
About 1 in 7 times, when I press the PTT button on the DM-32 it interferes with the KVM switch and both of my computer monitors go blank.

Now, this is clearly an RF interference issue that is combination of the radio hardware/firmware and the KVM switch not being well-shielded.

I don't know if this is something that can be fixed in the firmware or if it is just a weird quirk of using the radio near other electronics.

14
This is the cable I use/have that works with the DM-32

https://baofengtech.com/product/pc03/

15
Even when I was on the stock firmware, I had to buy a BTECH PC03 cable to work with the DM-32.  It seems to be very particular about which wire it uses.  My other FTDI didn't work with it.

Страницы: [1] 2 3