New Model #11281
openLANCHONLH HG-UV98 (updated version)
Added by Steve Case 8 months ago. Updated 8 months ago.
0%
Description
Unable to connect to LANCHONLH HG-UV98. I have tried both legacy and chirp-next but both yield this error:
Incorrect model: 000: 50 33 4c 4c 13 10 08 f8 P3LL...., expected 'P3107\x00\x00\x00'
The HG-UV98.exe software reads the radio just fine.
My radio firmware is V1.2_210517
Hardware V1.0.1
I also tried pressing the side buttons while turning the radio on, but that did not work either.
Files
| debug.log (1.33 KB) debug.log | Steve Case, 04/02/2024 04:20 PM | ||
| chirp_debug-g88jr12l.txt (7.95 KB) chirp_debug-g88jr12l.txt | Steve Case, 04/02/2024 04:37 PM | ||
| chirp_debug-_uz1x9xk.txt (3.74 KB) chirp_debug-_uz1x9xk.txt | Steve Case, 04/02/2024 04:52 PM | ||
| hg_uv98.py (25.7 KB) hg_uv98.py | Test module with different model string | Dan Smith, 04/02/2024 04:58 PM | |
| chirp_debug-mlsjdq76.txt (8.52 KB) chirp_debug-mlsjdq76.txt | Steve Case, 04/02/2024 05:02 PM |
Updated by Dan Smith 8 months ago
- Chirp Version changed from legacy to next
Your debug log was not properly captured and so it has nothing useful inside. Please reproduce the problem and then capture the log, per How_To_Report_Issues.
Also, this radio was just recently reported as working with next, so I'm surprised to hear there are issues. Since it's behaving the same with legacy, and given the nature of the message, I'd suspect a new firmware version maybe. How old is the radio?
Updated by Dan Smith 8 months ago
That debug log seems to show only you opening a file or something, so again no useful information.
Please do the following:
- Open CHIRP
- Radio->Download, choose the radio, click okay
- After the error occurs, click okay or whatever is necessary to go back to the main screen
- Go to Help->Show Debug Log Location, then grab that file and upload it here
If the radio is new and has a new firmware, the only thing we can really do is modify the current driver to accept that new firmware and have you test to see if it works. That could go poorly, depending on any changes they've made. Are you interested/willing to try that?
Updated by Steve Case 8 months ago
- File chirp_debug-g88jr12l.txt chirp_debug-g88jr12l.txt added
[2024-04-02 19:35:25,135] chirp.logger - DEBUG: CHIRP next-20240401 on Win32 (Unknown 10.0:22635) (Python 3.10.8)
[2024-04-02 19:35:25,185] chirp.wxui - DEBUG: Using locale: en_US (276)
[2024-04-02 19:35:25,188] chirp.wxui - DEBUG: Translation loaded=True for CHIRP: en_US (de,el,en_US,es,fr,hu,it,ja_JP,nl,pl,pt_BR,ru,tr_TR,uk_UA,zh_CN) from C:\Program Files (x86)\CHIRP\chirp\locale
[2024-04-02 19:35:25,192] chirp.wxui - DEBUG: Translation loaded=False for wxstd: en_US (af,an,ar,ca,ca@valencia,co,cs,da,de,el,es,eu,fa_IR,fi,fr,gl_ES,hi,hr,hu,id,it,ja,ka,ko_KR,lt,lv,ms,nb,ne,nl,pl,pt,pt_BR,ro,ru,sk,sl,sq,sv,ta,tr,uk,vi,zh_CN,zh_TW)
[2024-04-02 19:35:25,522] main - INFO: Python/3.10.8 // Windows/Windows-10-10.0.22635-SP0 // CHIRP/next-20240401 // wx/4.2.0 msw (phoenix) wxWidgets 3.2.0
[2024-04-02 19:35:25,522] chirp.wxui - WARNING: Developer mode is enabled
[2024-04-02 19:35:25,555] chirp.wxui.main - DEBUG: Recent is now ['C:\Users\steph\Documents\Radio\HG-UV98.csv']
[2024-04-02 19:35:25,805] chirp.wxui.main - INFO: Server reports next-20240401 is latest
[2024-04-02 19:35:30,616] chirp.drivers.fake - DEBUG: Opening C:\Program Files (x86)\CHIRP\chirp\drivers....\tests\images\Baofeng_UV-17.img
[2024-04-02 19:35:30,616] chirp.drivers.fake - ERROR: Unable to open image, fixture will not work
[2024-04-02 19:35:30,616] chirp.drivers.fake - DEBUG: Opening C:\Program Files (x86)\CHIRP\chirp\drivers....\tests\images\Baofeng_UV-17Pro.img
[2024-04-02 19:35:30,616] chirp.drivers.fake - ERROR: Unable to open image, fixture will not work
[2024-04-02 19:35:30,636] chirp.wxui.clone - DEBUG: All system ports: [{'device': 'COM9', 'name': 'COM9', 'description': 'Standard Serial over Bluetooth link (COM9)', 'hwid': 'BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_VID&00010075_PID&0100\8&A9DB96C&0&C418E9A222D6_C00000000', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': 'Microsoft', 'product': None, 'interface': None}, {'device': 'COM10', 'name': 'COM10', 'description': 'Standard Serial over Bluetooth link (COM10)', 'hwid': 'BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_LOCALMFG&0000\8&A9DB96C&0&000000000000_00000002', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': 'Microsoft', 'product': None, 'interface': None}, {'device': 'COM5', 'name': 'COM5', 'description': 'USB Serial Port (COM5)', 'hwid': 'USB VID:PID=0403:6001 SER=A10KAMM9A', 'vid': 1027, 'pid': 24577, 'serial_number': 'A10KAMM9A', 'location': None, 'manufacturer': 'FTDI', 'product': None, 'interface': None}]
[2024-04-02 19:35:32,198] chirp.wxui.clone - DEBUG: Using port 'COM5'
[2024-04-02 19:35:32,198] chirp.wxui.clone - DEBUG: Selected
[2024-04-02 19:35:32,236] chirp.wxui.clone - DEBUG: Serial opened: Serial
[2024-04-02 19:35:32,247] chirp.drivers.hg_uv98 - DEBUG: 0008 P>R: 000: 4e 69 4e 48 53 47 30 4e NiNHSG0N
[2024-04-02 19:35:32,761] chirp.drivers.hg_uv98 - DEBUG: ident string was b'P3LL\x13\x10\x08\xf8'
[2024-04-02 19:35:32,762] chirp.wxui.clone - ERROR: Failed to clone: Incorrect model: 000: 50 33 4c 4c 13 10 08 f8 P3LL....
, expected b'P3107\x00\x00\x00'
Traceback (most recent call last):
File "chirp\wxui\clone.py", line 77, in run
File "chirp\drivers\hg_uv98.py", line 351, in sync_in
File "chirp\drivers\hg_uv98.py", line 216, in do_download
File "chirp\drivers\hg_uv98.py", line 203, in do_ident
chirp.errors.RadioError: Incorrect model: 000: 50 33 4c 4c 13 10 08 f8 P3LL....
, expected b'P3107\x00\x00\x00'
[2024-04-02 19:35:35,579] chirp.wxui.clone - WARNING: Stopping clone thread
[2024-04-02 19:35:44,455] chirp.wxui.developer - DEBUG: Fetched attachments for issue 11179 (status 200)
[2024-04-02 19:35:44,455] chirp.wxui.developer - DEBUG: Found 2 valid module attachments from issue 11179
[2024-04-02 19:35:45,738] chirp.wxui.developer - DEBUG: Fetched info for user 3 (status 200)
[2024-04-02 19:35:45,738] chirp.wxui.developer - DEBUG: User chose attachment {'id': 10676, 'filename': 'hg_uv98.py', 'filesize': 26278, 'content_type': 'text/x-python-script', 'description': '', 'content_url': 'https://chirpmyradio.com/attachments/download/10676/hg_uv98.py', 'author': {'id': 3, 'name': 'Dan Smith'}, 'created_on': '2024-02-19T22:56:16Z'}
[2024-04-02 19:35:45,738] chirp.wxui.developer - DEBUG: Fetching attachment URL https://chirpmyradio.com/attachments/download/10676/hg_uv98.py
[2024-04-02 19:35:46,742] chirp.wxui.developer - DEBUG: Wrote attachment to C:\Users\steph\AppData\Local\Temp\loaded-10676-p4u4njpa.py
[2024-04-02 19:35:46,744] chirp.directory - INFO: driver re-registration enabled
[2024-04-02 19:35:46,752] chirp.wxui.main - INFO: Loading module C:\Users\steph\AppData\Local\Temp\loaded-10676-p4u4njpa.py SHA256 d085be7e876208eb4e99609c7dedecca075e8357210342be31ccbe2c6b0c7b68
[2024-04-02 19:35:46,757] chirp.directory - WARNING: Replacing existing driver id `Lanchonlh_HG-UV98'
[2024-04-02 19:35:50,299] chirp.drivers.fake - DEBUG: Opening C:\Program Files (x86)\CHIRP\chirp\drivers....\tests\images\Baofeng_UV-17.img
[2024-04-02 19:35:50,299] chirp.drivers.fake - ERROR: Unable to open image, fixture will not work
[2024-04-02 19:35:50,299] chirp.drivers.fake - DEBUG: Opening C:\Program Files (x86)\CHIRP\chirp\drivers....\tests\images\Baofeng_UV-17Pro.img
[2024-04-02 19:35:50,299] chirp.drivers.fake - ERROR: Unable to open image, fixture will not work
[2024-04-02 19:35:50,316] chirp.wxui.clone - DEBUG: All system ports: [{'device': 'COM9', 'name': 'COM9', 'description': 'Standard Serial over Bluetooth link (COM9)', 'hwid': 'BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_VID&00010075_PID&0100\8&A9DB96C&0&C418E9A222D6_C00000000', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': 'Microsoft', 'product': None, 'interface': None}, {'device': 'COM10', 'name': 'COM10', 'description': 'Standard Serial over Bluetooth link (COM10)', 'hwid': 'BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_LOCALMFG&0000\8&A9DB96C&0&000000000000_00000002', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': 'Microsoft', 'product': None, 'interface': None}, {'device': 'COM5', 'name': 'COM5', 'description': 'USB Serial Port (COM5)', 'hwid': 'USB VID:PID=0403:6001 SER=A10KAMM9A', 'vid': 1027, 'pid': 24577, 'serial_number': 'A10KAMM9A', 'location': None, 'manufacturer': 'FTDI', 'product': None, 'interface': None}]
[2024-04-02 19:35:51,747] chirp.wxui.clone - DEBUG: Using port 'COM5'
[2024-04-02 19:35:51,747] chirp.wxui.clone - DEBUG: Selected
[2024-04-02 19:35:51,776] chirp.wxui.clone - DEBUG: Serial opened: Serial
[2024-04-02 19:35:51,787] chirp.loaded.loaded-10676-p4u4njpa - DEBUG: 0008 P>R: 000: 4e 69 4e 48 53 47 30 4e NiNHSG0N
[2024-04-02 19:35:51,817] chirp.loaded.loaded-10676-p4u4njpa - DEBUG: ident string was b'P3LL\x13\x10\x08\xf8'
[2024-04-02 19:35:51,818] chirp.wxui.clone - ERROR: Failed to clone: Incorrect model: 000: 50 33 4c 4c 13 10 08 f8 P3LL....
, expected b'P3107\x00\x00\x00'
Traceback (most recent call last):
File "chirp\wxui\clone.py", line 77, in run
File "C:\Users\steph\AppData\Local\Temp\loaded-10676-p4u4njpa.py", line 351, in sync_in
self._mmap = do_download(self)
File "C:\Users\steph\AppData\Local\Temp\loaded-10676-p4u4njpa.py", line 216, in do_download
do_ident(radio)
File "C:\Users\steph\AppData\Local\Temp\loaded-10676-p4u4njpa.py", line 203, in do_ident
raise errors.RadioError(
chirp.errors.RadioError: Incorrect model: 000: 50 33 4c 4c 13 10 08 f8 P3LL....
, expected b'P3107\x00\x00\x00'
[2024-04-02 19:35:55,406] chirp.wxui.clone - WARNING: Stopping clone thread
Updated by Dan Smith 8 months ago
Okay, why are you loading the module from the other issue? That code was merged into the build, so you should not be loading something older.
Can you please confirm that the same behavior happens if you don't do that step? You need to restart chirp to clear it. Please grab and attach (just attach, no need to paste the content in here) a debug log without loading the module.
Updated by Steve Case 8 months ago
- File chirp_debug-_uz1x9xk.txt chirp_debug-_uz1x9xk.txt added
Yes, the same behavior even without loading the module.
Updated by Dan Smith 8 months ago
- File hg_uv98.py hg_uv98.py added
Okay, thanks for confirming. I'm attaching a test module that changes the identification string to the one your radio is reporting. That should allow you to download from it. If so, please attach a debug log from doing so and the .img file you capture and save.
Then please look through and see if the default memories look correct. Go to the settings tab and note any errors that get displayed and/or any values that look very strange (non-printable characters, nonsense huge values for things that should be small, etc). Please note any of those things here.
Uploading back to the radio if everything looks good is at your own risk, but if nothing looks out of place, it's probably reasonable to expect it to be okay. I would test that before making any changes to any values to make sure that you can restore the radio to the backup you capture from the first download.
Updated by Steve Case 8 months ago
- File chirp_debug-mlsjdq76.txt chirp_debug-mlsjdq76.txt added
Error communicating with radio
Radio sent 54 bytes (expected 160)
Updated by Dan Smith 8 months ago
- Tracker changed from Bug to New Model
- Subject changed from LANCHONLH HG-UV98 to LANCHONLH HG-UV98 (updated version)
- Chirp Version deleted (
next) - Model affected deleted (
LANCHONLH HG-UV98) - Platform deleted (
Windows) - Debug Log updated
- Equipment Loan/Gift Offered set to No
Okay, yeah, that indicates that it's more than just the firmware string. The different firmware is actually behaving differently during the clone, basically like a totally different radio. Unfortunately that means it'll take a motivated developer with access to one of these newer radios to fix it. It's unfortunate that the chinese radio manufacturers continue to sell different radios under the same name to keep their search history alive.
So, I'll change this to a "new model" request so that if such a motivated developer shows up, they can use this to implement it.
Sorry!