CHIRP - New Model # 1343

Transcription

1 CHIRP - New Model # 1343 Status: Closed Priority: Normal Author: Robert Elsinga Category: Created: 01/02/2014 Assignee: Robert Elsinga Updated: 06/28/2018 Due date: Chirp Version: Equipment Loan Offered: No Subject: Description Polmar DB-50M (Anytone AT-5888UV clone) Hi, I purchased a Polmar DB-50M, which is a clone of the Anytone AT-5888UV, with minor differences. The most important difference is that it supports 7 character channel names. I read the model name from the debug file: User selected AnyTone 5888UV on port COM9 Clone thread started 000: d d 00 IDB-50M. 008: e V I also read the Intek 2040 issue and tried to create a polmar-db50m.py file based on the intek.py file (changed the vendor, model and classname), but loading the module seems to time-out when reading the class PolmarDB50Madio(chirp_common.CloneModeRadio, chirp_common.experimentalradio): """Polmar DB-50M""" VENDOR = "Polmar" MODEL = "DB-50M" Is there a FAQ on how to create a *.py file yourself? I don;t mind tinkering a py file and I'm not scared of programming. Associated revisions Revision 2169:4f12abd6d77a - 01/04/ :22 am - Dan Smith [anytone] Add Polmar DB-50M clone support Fixes #1343 Revision 2170:e1eb3f50c25b - 01/04/ :31 am - Dan Smith [anytone] Add Polmar_DB-50M.img test image Related to #1343 History #1-01/02/ :17 am - Tom Hayward - Status changed from New to Feedback 01/09/2019 1/7

2 A timeout when reading the radio indicates Chirp doesn't understand the radio's protocol or the cable isn't working. Maybe it isn't a clone after all. You may need to sniff the protocol and compare to the Anytone code. Check [[Developers]] for more information. The mailing list or IRC would be a good place to ask your questions. #2-01/02/ :36 am - Robert Elsinga I will ask in the developer mailing list, if I can sniff the protocol without any additional hardware I will gladly do so. I can upload and download using the official software without any problems. I know what the (binary) frequency file which is used by the official software is made up of and I can create one from Excel through a hexeditor (to convert the hex-string to actual binary data, something Excel can't create). So maybe that will help too. #3-01/02/ :56 am - Dan Smith IMHO, the timeout is likely just because the proper ident string isn't being sent and the radio never responds, so CHIRP times out. If you see the new model in your model drop-down during clone, then it's loading it properly. I expect messing around in _ident will yield some progress. #4-01/02/ :15 pm - Robert Elsinga It is in the dropdown list after loading the py module. I noticed that I didn't change the response in _ident, now it is IDB-50M, like it is in the debug file. Still no joy though, load from radio does nothing. From the debug log: NOTE: driver re-registration enabled Registered Polmar_IDB-50M = PolmarDB50Madio Traceback (most recent call last): File "chirpui\mainapp.pyo", line 1357, in mh File "chirpui\mainapp.pyo", line 615, in do_download File "chirpui\mainapp.pyo", line 573, in _confirm_experimental File "chirpui\common.pyo", line 348, in show_warning File "chirpui\common.pyo", line 308, in _add_text TypeError: GtkTextBuffer.set_text() argument 1 must be string or read-only buffer, not None Traceback (most recent call last): File "chirpui\mainapp.pyo", line 1357, in mh File "chirpui\mainapp.pyo", line 615, in do_download File "chirpui\mainapp.pyo", line 573, in _confirm_experimental File "chirpui\common.pyo", line 348, in show_warning File "chirpui\common.pyo", line 308, in _add_text TypeError: GtkTextBuffer.set_text() argument 1 must be string or read-only buffer, not None But it didn;t even display the Experimental radio popup, which does show when querying the DB50M as a AT-5888UV. But the trackback suggests there is some sort of argument problem, but I didn't change any argument, only the class and response in _ident. I asked for a capture tool in the developers mailinglist, hope I get a response so I can start debugging. 01/09/2019 2/7

3 #5-01/02/ :18 pm - Dan Smith The string in the image file is not the same as what the radio expects to start the clone, IIRC. Get Portmon and you can watch exactly what the OEM software is doing. #6-01/02/ :18 pm - Robert Elsinga My changes to the intek.py file (now saved as polmar_db50.py): def _ident(radio): radio.pipe.settimeout(1) _echo_write(radio, "PROGRAM") response = radio.pipe.read(3) if response!= "QX\x06": print "Response was:\n%s" % util.hexprint(response) raise errors.radioerror("unsupported model") _echo_write(radio, "\x02") response = radio.pipe.read(16) _debug(util.hexprint(response)) if response[1:8]!= "IDB-50M": < only this line print "Response was:\n%s" % util.hexprint(response) raise errors.radioerror("unsupported model") class PolmarDB50Mradio(chirp_common.CloneModeRadio, chirp_common.experimentalradio): """Polmar DB-50M""" VENDOR = "Polmar" MODEL = "IDB-50M" BAUD_RATE = 9600 (all except first and last line) So no arguments changed. Must be somthing in the data, I guess. #7-01/02/ :20 pm - Robert Elsinga Dan Smith wrote: The string in the image file is not the same as what the radio expects to start the clone, IIRC. Get Portmon and you can watch exactly what the OEM software is doing. Okay. I thought the string in the debug logfile would be what I needed to change in the py file. Couldn't find the debug.log from the intek to compare. :) I will download portmon and check what the official software sends and receives. Will post the result here. #8-01/02/ :49 pm - Robert Elsinga 01/09/2019 3/7

4 Portmon is not supported on x64 systems and I'm running Win7 x64... Will try to locate another tool to monitor the serial comms... #9-01/02/ :50 pm - Dan Smith It works fine on x64 Windows 7. #10-01/02/ :55 pm - Robert Elsinga Strange, I downloaded version 3.03 which seems the latest. It shows Error 2 and quits or does not show any serial ports. The Serialcomms registry hyve only shows the 3 commports I have (one physical, 2 USB2serial Prolific ones). Do you have a link to the working one? #11-01/02/ :58 pm - Dan Smith See this (the first hit on google for "portmon windows 64"): There are answers below about how to make it run. #12-01/02/ :16 pm - Robert Elsinga Already found that one and tried all suggestions. Doesn't work. Every 2000/XP compatibility mode still shows error 2. Also copied from USB disk to fixed D: drive and still no joy. Ran from CMD box and/or as admin, nothing. :( Problem is, all my other machines are Win7 x64 or Windows Server 2008 x64. And i doubt it runs from VMware Workstation, but I might just install a Windows 7 x86 VM just to try... But that mght have to wait until next week. ;) Since I can export from my massive ( frequencies) Excel file to Chirp CSV format, I rather use Chirp than input the channels by hand (even if it's "only" about 300). I tried to hack the binary *.fre file together and it loads fine in the official software, but it won't upload. :( So I really want to get Chirp to work... Then I can upload the channels with Chirp, read from the radio and then alter all settings and upload the complete file to the radio. So any suggestion on how to get Portmon to work or an alternative is appreciated. Tried Api Monitor v2, but couldn't find the right calls to monitor for the serial data yet. #13-01/02/ :19 pm - Dan Smith Why wouldn't it work in VMware? It just hooks into Windows APIs, so I don't see why it would be specific to any hardware (or lack thereof). It works in virtualbox and KVM for me. I sure as hell don't have windows installed on any real hardware here :) #14-01/02/ :22 pm - Robert Elsinga Okay, will install Win7 x86 real soon and monitor from within the VM. Only thing I need is get the USB serial cable to work, but it is a generic Prolific one, so hope that works. If I can read the radio then I wil monitor the serial data and log it. 01/09/2019 4/7

5 Will report back when I have something to show. ;) Thanks for the support so far. :) #15-01/04/ :07 am - Robert Elsinga Okay, fired my XP SP3 x86 VM, installed the serial driver and the programming software and ran Portmon. I attached the logfiles (both captures in ASCII and HEX, without all status calls so only the read/written data). <edit, can't submit with the 4 logfiles attached, I placed them here for download: Is there anyone who has a similar capture of a AT-5888UV or Intek HR-2040? Then I could compare the way they read/write to the DB50M #16-01/04/ :14 am - Dan Smith - File Portmon_read_5888UV_hex.log.txt added - Assignee set to Robert Elsinga Here is a hex read from my Anytone. I think that from looking at your own log and the code, you should be able to suss out the differences pretty easily, but hopefully this will help. #17-01/04/ :46 am - Robert Elsinga Okay, I have compared the two files and they start of exactly the same with the sending PROGRAM and receiving PROGRAMSQ Ox06. Then the command sent is the same every time (0x , at least for the first couple of times I compred them), but the answer is different. Not a surprise, since it starts with a query for the model number. However, the length of the answer is the same (26). And later in the log, when querying the channels, the command seems to be the same for both models and theanswer is the same length. I cannot find any fundamental differences, which is not a surprise since both radio's share the same body. That could mean I can just change the intek.py file, but that didn't work... But I now know for sure the DB50M returns "DB-50M" as the model name (omitting the 0x0249 which is returned for both radios). Assuming the DB50M is behaving the same as the 5888UV or Intek HR2040, do I just need to change the model name and the class definition? #18-01/04/ :48 am - Dan Smith This sort of back-and-forth development discussion is much easier on the dev mailing list. Can you start a thread there and we'll pick up? Thanks! #19-01/04/ :52 am - Tom Hayward #20-01/04/ :56 am - Robert Elsinga Changed all occurrences of Intek to Polmar and HR-2040 to DB-50M the intek.py file, but reading the radio does nothing and the logfile starts this: NOTE: driver re-registration enabled Registered Polmar_DB-50M = PolmarDB50MRadio 01/09/2019 5/7

6 Traceback (most recent call last): File "chirpui\mainapp.pyo", line 1357, in mh File "chirpui\mainapp.pyo", line 615, in do_download File "chirpui\mainapp.pyo", line 573, in _confirm_experimental File "chirpui\common.pyo", line 348, in show_warning File "chirpui\common.pyo", line 308, in _add_text TypeError: GtkTextBuffer.set_text() argument 1 must be string or read-only buffer, not None Since the communication is exactly the same until the radio responds with the model name and I have the correct model name, it should at least get that. But I don;t even get the experimental warning, which is the first call in the class PolmarDB50MRadio(chirp_common.CloneModeRadio, chirp_common.experimentalradio): """Polmar DB-50M""" VENDOR = "Polmar" MODEL = "DB-50M" BAUD_RATE = May try to mirror the OEM behavior later _ranges = [ (0x0000, 0x8000), def get_experimental_warning(cls): return "FOO" What is next? I am no Python programmer, so real debugging is not a viable option for me at the moment... #21-01/04/ :57 am - Robert Elsinga Dan Smith wrote: This sort of back-and-forth development discussion is much easier on the dev mailing list. Can you start a thread there and we'll pick up? Thanks! As Tom responded, I already posted there, but no reply since then. And, as any user, I'm impatient. ;) #22-01/04/ :59 am - Dan Smith Sorry, I missed that you had done that. I just replied there, please, lets take the discussion to the list. #23-01/04/ :07 am - Robert Elsinga Check, responded there. Tnx! #24-01/04/ :30 am - Robert Elsinga Dan was a great help and added Polmar DB-50M support in the nightly build. Thanks! 01/09/2019 6/7

7 #25-01/04/ :31 am - Dan Smith - Status changed from Feedback to Closed - Target version set to Fixed in r2169 Files debug.log 4.8 kb 01/02/2014 Robert Elsinga polmar-db50m.py 12.1 kb 01/02/2014 Robert Elsinga Portmon_read_5888UV_hex.log.txt 2.2 MB 01/04/2014 Dan Smith 01/09/2019 7/7

8