New Model #10530
openQYT KT-5000
Added by Janos Barabas about 2 years ago. Updated about 1 month ago.
0%
Description
Please add support for this model, or inform me if it is compatible with one of the previous models
Files
btech.py (188 KB) btech.py | Piotr F., 03/25/2025 03:19 PM | ||
btech.py (195 KB) btech.py | Piotr F., 03/27/2025 07:29 AM |
Updated by Dan Smith over 1 year ago
- Has duplicate New Model #10963: QYT KT5000 support (parallels #10530) added
Updated by Jim Moss over 1 year ago
Have radio, program cable and QYT CPS link for testing and addition to Chirp! I am willing to forward all for testing.
Updated by Alexandre J. Raymond 11 months ago
- Subject changed from QYT KT-5000 not yet supported to QYT KT-5000
- I read the instructions above set to Yes
Updated by Alexandre J. Raymond 11 months ago
- Equipment Loan/Gift Offered set to Yes
Updated by Piotr F. about 1 month ago
Very rudimentary support for it is in https://github.com/iwane-pl/chirp/tree/qyt-5000
Memories can be programmed. I didn't make out the settings map yet.
Updated by Piotr F. about 1 month ago
If someone wants to reverse the settings map, it can be done even without the radio itself - the QYT CPS saves a binary dump of memory on disk when editing. One can change the options in the CPS and compare resulting saved files to work it out.
Updated by Dan Smith about 1 month ago
Piotr, if you attach the .py
file here other users can load it with LoadingTestModules and give you feedback.
Also, I much prefer basic drivers and incremental progress, so please feel free to propose a PR when it's minimally useful. I often put in my own drivers when just basic memory operations are possible.
Updated by Piotr F. about 1 month ago
OK. I wasn't sure how to proceed, so I left it on the branch in my fork.
The driver is just another class and some edits in btech.py
. I attached it.
It can program memories and doesn't crash when switching to the settings tab. One can also program the static message on the display.
Before I propose a PR, I'd like to have at least usable settings page. Unless we're OK with it showing some unrelated settings (as VFO C, which this radio doesn't have).
Updated by Dan Smith about 1 month ago
You can just override get_features()
for your subclass and make it indicate no features. Something like:
class KT5000(...):
...
def get_features(self):
rf = super().get_features()
rf.has_settings = False
return rf
Then you can iterate until you're happy and we can merge settings fixes with a change to flip that to true (or, remove the get_features()
override).
Updated by Piotr F. about 1 month ago
If this is the case... :)
I added the snippet you posted. Pull request is here: https://github.com/kk7ds/chirp/pull/1302
Needs polishing still.
Updated by Michael Knight about 1 month ago
I have this radio and I would be interested in supporting this development as a beta tester if it helps.
Thanks for your effort!
Updated by Piotr F. about 1 month ago
Michael,
Good to know that someone's willing to test it :) I have the settings page more-or-less done too (atteched) - it'll go to another Pull Request later.
I lack time to invest in proper testing of the driver. Worked out the settings page based on the QYT CPS software, still need to upload something to my radio using it.
#TODO:
- verify if it works :D
- ANI
- FM radio presets
- unjungle (the if-ology is horrible in there...)
Updated by Dan Smith about 1 month ago
Michael, use LoadingTestModules to try out the modules attached here locally.
Updated by Michael Knight about 1 month ago
I already gave a try.
So far what I was able to test, works.
FM presets I dunno how to save them so don't know either how to verify it.
The term (or feature) unjungle I dunno what it is so no idea how I can test it :(
Updated by Piotr F. about 1 month ago
Thanks for testing!
That TODO list is not a list of "what to test", sorry for confusion. All the options need testing, as I only verified that I don't brick the radio with uploads :) Most of the options seem to work fine, as much as I needed them in my radio.
The list was more like "what's still to do in the settings page". "Unjungling" is for code. There's a jungle of conditions in it... I shouldn't have written the comment in a hurry... :)
Anyway, what I've already noticed is that "TX in multi-standby" (TMRTX) doesn't work properly.