Okay, sorry, I forgot this was started here since the discussion ended up all in the issue.
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 radio:
If you create a new .py file there and change the VENDOR and MODEL strings as you have, then CHIRP will register it and make it available for selection in the UI. If you see the right vendor/model in the drop-downs during the download part, you can be sure that you're running the code in that file.
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 (0x52 00 20 10, 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.
Probably the best thing to do to get bootstrapped is start dropping print statements into your module to help you understand where exactly it's getting stuck, and confirm what you're getting back from the radio in each step. Looking at the other code will help, but this should be most of what you want:
print util.hexprint(foo)
where "foo" is some string variable of data you just read from the radio.
I think you're doing your development in Windows, right? Did you get a full development environment setup or are you trying to shove your .py into the frozen zip each time you make a change?
--Dan