New Model #10925
openNew Model Support for Wouxun KG-Q10G GMRS radio
90%
Description
Add support for the new KG-Q10G GMRS radio which is based off of the Wouxun KG-Q10H Amateur radio.
Files
Updated by Mel Terechenok about 1 year ago
- Related to New Model #10692: Wouxun KG-Q10H added
Updated by Mel Terechenok about 1 year ago
- Related to deleted (New Model #10692: Wouxun KG-Q10H)
Updated by Mel Terechenok about 1 year ago
- File kgq10h b2p3.py added
Beta 2.3
Limit Area Message and Top Message to 12 characters - Consistent with Wouxun CPS to prevent random dropping of chars 13-15 on radio display
Enable FM/NFM/AM mode selection via the Channel Memory UI -
AM mode options of AM Rx or AM Rx+Tx(Q10H Only) must be set in the channel properties--Extra tab (AM Mode options only shown when AM Mode is selected)
KG-Q10G only supports AM Rx mode
Various clean up items for Chirp tests
Include support for KG-Q10G GMRS Version.
See the Q10H page for more details on driver history
https://chirp.danplanet.com/issues/10692
How to load test drivers
Enter Issue #10925 and select the Beta driver
Updated by Phillip Onfri about 1 year ago
Mel Terechenok wrote in #note-5:
Beta 2.3
Limit Area Message and Top Message to 12 characters - Consistent with Wouxun CPS to prevent random dropping of chars 13-15 on radio display
Enable FM/NFM/AM mode selection via the Channel Memory UI -AM mode options of AM Rx or AM Rx+Tx(Q10H Only) must be set in the channel properties--Extra tab (AM Mode options only shown when AM Mode is selected)
KG-Q10G only supports AM Rx modeVarious clean up items for Chirp tests
Hi Mel, I just got the KGQ10G and I loaded the beta driver and when I go to download, it gives me a dialog that I selected the wrong option but it mentioned the correct radio. Using the same red cable I use for the KG-Q10H.
Include support for KG-Q10G GMRS Version.See the Q10H page for more details on driver history
https://chirp.danplanet.com/issues/10692How to load test drivers
Enter Issue #10925 and select the Beta driver
Mel Terechenok wrote in #note-5:
Beta 2.3
Limit Area Message and Top Message to 12 characters - Consistent with Wouxun CPS to prevent random dropping of chars 13-15 on radio display
Enable FM/NFM/AM mode selection via the Channel Memory UI -AM mode options of AM Rx or AM Rx+Tx(Q10H Only) must be set in the channel properties--Extra tab (AM Mode options only shown when AM Mode is selected)
KG-Q10G only supports AM Rx modeVarious clean up items for Chirp tests
Include support for KG-Q10G GMRS Version.
See the Q10H page for more details on driver history
https://chirp.danplanet.com/issues/10692How to load test drivers
Enter Issue #10925 and select the Beta driver
Updated by Mel Terechenok almost 1 year ago
Phillip Onfri --- what radio are you trying to read from when you got the error message?
Please provide details if you wish to have me help you.
By the picture you posted, the only thing I can tell you is that the radio you tried to read from did not identify as the Q10G.
Duplicate the issue and post your debug.log
Updated by Phillip Onfri almost 1 year ago
- File Screenshot 2023-11-09 at 10.14.27 AM.png Screenshot 2023-11-09 at 10.14.27 AM.png added
- File chirp_debug-75buo5bx.txt chirp_debug-75buo5bx.txt added
Mel Terechenok wrote in #note-7:
Phillip Onfri --- what radio are you trying to read from when you got the error message?
Please provide details if you wish to have me help you.
By the picture you posted, the only thing I can tell you is that the radio you tried to read from did not identify as the Q10G.
Duplicate the issue and post your debug.log
So the radio is a KG-G10G, which I selected after loading the beta module. This radio is fresh out of the box so I haven't done anything to it or added any new data. I have attached a few pics for you. Thanks for the help.
Updated by Phillip Onfri almost 1 year ago
Phillip Onfri wrote in #note-8:
Mel Terechenok wrote in #note-7:
Phillip Onfri --- what radio are you trying to read from when you got the error message?
Please provide details if you wish to have me help you.
By the picture you posted, the only thing I can tell you is that the radio you tried to read from did not identify as the Q10G.
Duplicate the issue and post your debug.log
So the radio is a KG-G10G, which I selected after loading the beta module. This radio is fresh out of the box so I haven't done anything to it or added any new data. I have attached a few pics for you. I'm also using the latest chirp available. Thanks for the help.
Updated by Phillip Onfri almost 1 year ago
Phillip Onfri wrote in #note-9:
Phillip Onfri wrote in #note-8:
Mel Terechenok wrote in #note-7:
Phillip Onfri --- what radio are you trying to read from when you got the error message?
Please provide details if you wish to have me help you.
By the picture you posted, the only thing I can tell you is that the radio you tried to read from did not identify as the Q10G.
Duplicate the issue and post your debug.log
So the radio is a KG-Q10G, which I selected after loading the beta module. This radio is fresh out of the box so I haven't done anything to it or added any new data. I have attached a few pics for you. I'm also using the latest chirp available. Thanks for the help.
Updated by Mel Terechenok almost 1 year ago
- File kgq10h b2p3 disable model check to get radio image.py added
Phillip Onfri wrote in #note-10:
So the radio is a KG-Q10G, which I selected after loading the beta module. This radio is fresh out of the box so I haven't done anything to it >>or added any new data. I have attached a few pics for you. I'm also using the latest chirp available. Thanks for the help.
OK - Please do a couple things for me. Turn off the radio... then press and hold the 6 button while turning on the radio and report back to me what the firmware revision is on the last line of the info displayed. It should be something like VD1.01 or some other later version number.
Then try reading from the radio with the following test driver that disables the model check for downloads. I am concerned that there may be a new firmware that changed the radio memory that I will have to handle. If you are able to read from the radio, save the image that was read from your radio and add it to this ticket so I can analyze the information. The driver should not let you write to the radio, but just in case please don't try until I can take a look at what is going on with your radio.
Updated by Phillip Onfri 12 months ago
Mel Terechenok wrote in #note-11:
Phillip Onfri wrote in #note-10:
So the radio is a KG-Q10G, which I selected after loading the beta module. This radio is fresh out of the box so I haven't done anything to it >>or added any new data. I have attached a few pics for you. I'm also using the latest chirp available. Thanks for the help.OK - Please do a couple things for me. Turn off the radio... then press and hold the 6 button while turning on the radio and report back to me what the firmware revision is on the last line of the info displayed. It should be something like VD1.01 or some other later version number.
Then try reading from the radio with the following test driver that disables the model check for downloads. I am concerned that there may be a new firmware that changed the radio memory that I will have to handle. If you are able to read from the radio, save the image that was read from your radio and add it to this ticket so I can analyze the information. The driver should not let you write to the radio, but just in case please don't try until I can take a look at what is going on with your radio.
FIRMWARE: VD1.02
DEBUG LOG: Could not upload cause it says it exceeds size. THis is a clean log with just the radio read. Interesting.
DATA DUMP: Wouxun_KG-Q10G_20231110_Phillip.img
It's interesting that all I see is rows 11 to 999 and no data on the radio but there's is CD and all the GMRS data on it from the factory. Wonder if it just needs to get reset or something.
Updated by Phillip Onfri 12 months ago
Phillip Onfri wrote in #note-12:
Mel Terechenok wrote in #note-11:
Phillip Onfri wrote in #note-10:
So the radio is a KG-Q10G, which I selected after loading the beta module. This radio is fresh out of the box so I haven't done anything to it >>or added any new data. I have attached a few pics for you. I'm also using the latest chirp available. Thanks for the help.OK - Please do a couple things for me. Turn off the radio... then press and hold the 6 button while turning on the radio and report back to me what the firmware revision is on the last line of the info displayed. It should be something like VD1.01 or some other later version number.
Then try reading from the radio with the following test driver that disables the model check for downloads. I am concerned that there may be a new firmware that changed the radio memory that I will have to handle. If you are able to read from the radio, save the image that was read from your radio and add it to this ticket so I can analyze the information. The driver should not let you write to the radio, but just in case please don't try until I can take a look at what is going on with your radio.
FIRMWARE: VD1.02
DEBUG LOG: Could not upload cause it says it exceeds size. THis is a clean log with just the radio read. Interesting.
DATA DUMP: Wouxun_KG-Q10G_20231110_Phillip.imgIt's interesting that all I see is rows 11 to 999 and no data on the radio but there is CB and all the GMRS data on it from the factory. Wonder if it just needs to get reset or something.
Updated by Mel Terechenok 12 months ago
- File clipboard-202311102026-raaei.png clipboard-202311102026-raaei.png added
- File clipboard-202311102027-rysof.png clipboard-202311102027-rysof.png added
- File clipboard-202311102028-r3aag.png clipboard-202311102028-r3aag.png added
- File clipboard-202311102033-5gpk9.png clipboard-202311102033-5gpk9.png added
Phillip Onfri wrote in #note-13:
It's interesting that all I see is rows 11 to 999 and no data on the radio but there is CB and all the GMRS data on it from the factory. Wonder if it just needs to get reset or something.
What you are seeing is actually an exclamation point before the numbers not a 1 -- !1 - !999 indicating errors for each and every channel memory.
That is because the image file is both incomplete and contains useless data, which explains why you are failing the Model Check as there is no data from the radio at the location where the radio identity is stored.
Here is what your image contains - only 512 bytes ( should be 32768) and all the bytes have a value of 40.
I have confirmed that this is not specifically related to the new Q10G firmware as the Beta2.3 driver was used on a new firmware radio and everything worked as expected.
I don't know what is going on, but I wonder if your radio has a communication problem or if you have a cable problem. Do you have a windows machine where you could try the Wouxun CPS to see if you get any valid data? Or do you have another cable? Does your cable work with any other radios? What cable are you using?
If the Wouxun CPS can't read from the radio, or a new cable doesn't solve the problem - you could try a Reset ALL. If that doesn't work, you may want to contact BTWR to see if there is anything they can do.
At this point, there is nothing I can do to Chirp to help you.. We need to figure out the reason for the bad data communication issue before Chirp will ever be usable for you on that radio.
Updated by Phillip Onfri 12 months ago
- File Screenshot 2023-11-11 at 7.00.36 AM.png Screenshot 2023-11-11 at 7.00.36 AM.png added
- File Wouxun_KG-Q10G_20231111_Good_Read_Phillip.img Wouxun_KG-Q10G_20231111_Good_Read_Phillip.img added
Mel Terechenok wrote in #note-14:
Phillip Onfri wrote in #note-13:
It's interesting that all I see is rows 11 to 999 and no data on the radio but there is CB and all the GMRS data on it from the factory. Wonder if it just needs to get reset or something.
What you are seeing is actually an exclamation point before the numbers not a 1 -- !1 - !999 indicating errors for each and every channel memory.
That is because the image file is both incomplete and contains useless data, which explains why you are failing the Model Check as there is no data from the radio at the location where the radio identity is stored.
Here is what your image contains - only 512 bytes ( should be 32768) and all the bytes have a value of 40.
I have confirmed that this is not specifically related to the new Q10G firmware as the Beta2.3 driver was used on a new firmware radio and everything worked as expected.
I don't know what is going on, but I wonder if your radio has a communication problem or if you have a cable problem. Do you have a windows machine where you could try the Wouxun CPS to see if you get any valid data? Or do you have another cable? Does your cable work with any other radios? What cable are you using?
If the Wouxun CPS can't read from the radio, or a new cable doesn't solve the problem - you could try a Reset ALL. If that doesn't work, you may want to contact BTWR to see if there is anything they can do.
At this point, there is nothing I can do to Chirp to help you.. We need to figure out the reason for the bad data communication issue before Chirp will ever be usable for you on that radio.
So the cable that ti use is the infomus RED cable :-). I know the cable works as it can read and upload to my KG-Q10G just fine using the same driver. So I did a reset on the radio and got it to communicate and download the data successfully. Not sure what the deal was with this radio but I suspected a reset might help because of the way that it came packaged it looked used. Athenena was on it and it was just not packaged the way all the other radios I get are. I do however see symbols in the data. I have posted a pic and a download for your reference. I will try try to write to the radio to make sure its fine. Thank you again Sir for all your work and what you do for the community. Much appreciated.
Updated by Mel Terechenok 12 months ago
Glad you got it working. I was not aware you had another radio that was working fine. I am aware of the symbol issue at the end of the channel names. It is due to the channel names from Wouxun not always blanking out all the unused characters in the name. I will update the driver to clean this up so the extraneous data is ignored by chirp. Let me know if you have any other issues.
Updated by Mel Terechenok 12 months ago
- File deleted (
kgq10h b2p3 disable model check to get radio image.py)
Updated by Mel Terechenok 12 months ago
- File kgq10h b2p4.py added
Beta 2.4
Fix extraneous characters stored in Channel Names on some radios from the factory.
Updated by Phillip Onfri 12 months ago
Mel Terechenok wrote in #note-16:
Glad you got it working. I was not aware you had another radio that was working fine. I am aware of the symbol issue at the end of the channel names. This is due to the channel names from Wouxun not always blanking out all the unused characters in the name. I will update the driver to clean this up so the extraneous data is ignored by chirp. Let me know if you have any other issues.
Upload (write) to the radio work like a charm. Just took the radio out for a spin and it's working as expected. Again thank you so much for all your work Sir.
Updated by Mel Terechenok 10 months ago
- Status changed from New to In Progress
- % Done changed from 0 to 90
Updated by Mel Terechenok 10 months ago
- File Screenshot 2024-01-08 181419.png Screenshot 2024-01-08 181419.png added
- File kgq10h b2p6.py kgq10h b2p6.py added
To see all "Extra" settings in Memories Tab - Click View-->Show Extra Fields
Fix AM Mode column to always show in Memories Tab when Show Extra Fields is enabled regardless of FM or AM mode selection.
Fix Call Group column to show up in the Channel Memories Tab.
Just as when editing Extra Fields via the properties menu, To change between AM/FM/NFM you must first switch the Mode entry. When Mode = AM... Only then will AM Mode changes be accepted.
Still working on getting the color picker palette working as well as other driver cleanups that are required for official inclusion into Chirp.
Updated by Mel Terechenok 9 months ago
- Related to New Model #11151: Please add Wouxun KG-Q10G added