New Model #11270
opennew version of uv-k5 quansheng from F4HWN
0%
Description
Hi
i made a chirp driver for the firmware of F4HWN who is base on egzumer firmware for the uv-k5 radio,
i made the chirp driver with egzumer for his egzumer firmware before integrated in the chirp ( auto detect now )
i would like to add it to the chirp data base instead of load module when open chirp
take a look about it. i have the french driver and the english driver,
Many set doc have been implemented and help section
let me know what can be done
Files
| uvk5_egzumer_f4hwn.py (117 KB) uvk5_egzumer_f4hwn.py | driver in english | ||
| uvk5_egzumer_f4hwn_fr.py (118 KB) uvk5_egzumer_f4hwn_fr.py | driver in french | ||
| uvk5_egzumer_f4hwn_ver_2_7_0 (2).py (119 KB) uvk5_egzumer_f4hwn_ver_2_7_0 (2).py | driver for f4hwn version 2,7 | ||
| f4hwn feature.jpg (164 KB) f4hwn feature.jpg | screen shot chirp | ||
| f4hwn feature1.jpg (177 KB) f4hwn feature1.jpg | screen shot chirp 1 | ||
| f4hwn.packed.v2.7.bin (60 KB) f4hwn.packed.v2.7.bin | firmware of the f4hwn version 2,7 |
Updated by Dan Smith 8 months ago
What are the differences between this and the egzumer driver? If this adds more functionality from the egzumer variant, you need to subclass that radio and only change the things necessary. Duplicating the whole driver is not acceptable, as it creates a big maintenance burden for us. See how the egzumer driver subclasses the base driver and adds its new functionality.
Please describe how your driver differs so I can help you figure out how to subclass.
Also, don't create a french and english driver. Mark your strings like _("foo"). Then update the translation files with make -C chirp/locale clean all and then find/translate them in the fr.po file. That way it will also work for other languages.
Updated by Jocelyn Maheu 6 months ago
- File uvk5_egzumer_f4hwn_ver_2_7_0 (2).py uvk5_egzumer_f4hwn_ver_2_7_0 (2).py added
- File f4hwn feature.jpg f4hwn feature.jpg added
- File f4hwn feature1.jpg f4hwn feature1.jpg added
- File f4hwn.packed.v2.7.bin f4hwn.packed.v2.7.bin added
Hi,
Sory for late answers..
The firmware of f4hwn was start on the base on egzumer but it's now far a way from it
The driver for f4hwn add many feature, fix bug display, implement all the fly over ( set doc ) all over the feature, add many help user text
many change has been done all over.
the memory mapping change location for all the feature of f4hwn.
take a look about add feature and other, in picture
ok, for the french translation, i will take a look about it later if the implementation can be done.
let me know what can be done
Joc2
Updated by Dan Smith 6 months ago
As I mentioned, you need to subclass the egzumer or base driver and make your changes incrementally. I'm not interested in putting another whole copy of the driver into the tree that we have to maintain. The UV-K5 community needs to work on organizing the parallel forks of development and get some structure in place. Even if you have diverged from the egzumer way to some degree, there's much that can be shared between the drivers.