Bug #10455
closed1st row does not populate when cloning from radio
100%
Description
March 17, 2023
What is the behavior you are seeing?
When cloning the first row is numbered !1 and no data populated in the balance of the fields.
What is the behavior you were expecting?
No. Channel 1 showed no data.
Can you reproduce the problem all the time?
Yes with the Next and Legacy.
What are the steps required to reproduce the problem?
Clone from radio.
Is this specific to a certain radio model (driver) or something that you can reproduce with another radio?
Wouxon UV8D Plus. Only Wouxon I own.
Note: OEM software does not allow me to pick a com port so I cannot use it. Software issue?
It used to work with my Beelink computer.
RT systems software works.
Computer is a Evolve III, Windows 10Pro.
RT systems USB-K4Y and XLT Painless Programming Cable FTDI USB cables used. Both connected to the radio with Chirp.
Wesley Shimizu
KN6RHV@gmail.com
Files
| CHIRP Issues Wouxon UV8D Plus.txt (891 Bytes) CHIRP Issues Wouxon UV8D Plus.txt | |||
| Wouxun_KG-UV8D Plus_20230317.img (32.2 KB) Wouxun_KG-UV8D Plus_20230317.img | IMG file | ||
| UV8D Plus RT Systems Row 1.xlsx (9.11 KB) UV8D Plus RT Systems Row 1.xlsx | RT system Row 1 | ||
| clipboard-202304140858-ulwvs.png (109 KB) clipboard-202304140858-ulwvs.png | mems after updating the DCS decoding to be like the UV8H | ||
| clipboard-202304140859-gha13.png (29 KB) clipboard-202304140859-gha13.png | |||
| clipboard-202304140900-rwhut.png (33.5 KB) clipboard-202304140900-rwhut.png | |||
| kguv8dplus.py (41.7 KB) kguv8dplus.py | 8D Plus DCS decoding Read/Write + UHF lower Limit Change |
Updated by Dan Smith almost 2 years ago
Please attach a .img of your radio for examination.
Updated by Mel Terechenok over 1 year ago
Looking at the debug log, I suspect the driver is not detecting DCS codes properly.
For memory 1, a code of 1644.3 would likely be 0x403B in the radio. This is likely supposed to be DCS code D073. This would be consistent with the KG-UV8H and KG-935G encoding. We need the img and the tone the radio shows to determine the correct encoding scheme for DCS and polarity.
Updated by Wesley Shimizu over 1 year ago
Updated by Mel Terechenok over 1 year ago
- File clipboard-202304140858-ulwvs.png clipboard-202304140858-ulwvs.png added
- File clipboard-202304140859-gha13.png clipboard-202304140859-gha13.png added
- File clipboard-202304140900-rwhut.png clipboard-202304140900-rwhut.png added
in the posted img.... Memory 1 opens just fine in both Chirp-Next and Legacy with a DCS of D073N.
However memories 95, 96, 100, 102, 104, 106, 108 show Errors due to tone decoding.
Using the UV-8H/935G DCS decoding algo, all the tones are decoded correctly except Memory 1.
It seems like Memory 1 has different encoding for the tone than all the other memories.
Was memory 1 updated via chirp before the image was saved?
Was the browser feature or some other direct memory edit of the tone used for Mem 1?
With this image written to the radio, does the radio display the correct D073N tone for mem 1?
I can patch the driver to what I think the correct decoding is, but I can't explain the different encoding for Mem 1 vs the remaining mems.
these pics are after patching the DCS decoding to match what I think it is.
Updated by Mel Terechenok over 1 year ago
- File kguv8dplus.py added
Try this driver --- Change Tones on the radio and download from Radio to confirm Chirp accepts it correctly.
If that works, the same update can be made to enable proper writing of tones from Chirp to the radio.
Updated by Mel Terechenok over 1 year ago
- Assignee set to Mel Terechenok
- % Done changed from 0 to 50
Updated by Mel Terechenok over 1 year ago
Wesley - have you been able to test the updated driver and confirm whether or not it properly reads the TONE values programmed in the radio now?
Feedback is appreciated.
Updated by Wesley Shimizu over 1 year ago
I just tried to add a new repeater into the database, same issue. 20230515.
Wes
Updated by Mel Terechenok over 1 year ago
Wesley,
What I want to know is when you use the test driver ... if you change the DCS tone in a memory channel directly on the radio and then do a read from Chirp, does Chirp display the correct DCS tone.
I have not implemented the fix yet for changing a tone in Chirp and writing it to the radio.
I want to confirm that I have the correct decoding of tone values before making more changes.
Updated by Mel Terechenok over 1 year ago
- Related to Bug #6763: KG-UV8D Plus does not parse DCS entries added
Updated by Mel Terechenok over 1 year ago
- File kguv8dplus.py kguv8dplus.py added
Updated Driver to support Read/Write of DCS tones
Updated UHF Lower Limit to support some radios that come with 350MHz as lower limit
Updated by Mel Terechenok over 1 year ago
- Status changed from New to Closed
- % Done changed from 50 to 100
Applied in changeset github|91450800bf9b38ec68e307790eb4067a30d14505.