CHIRP

Please try the attached module, using the instructions in LoadingTestModules. Please try download first. If that works, grab the image and be sure to save it in case upload fails as the radio will reset in that situation. Capture and attach the resulting debug log after testing, even if everything works.

Also, we don't have a test image for this radio, so if you have one from a previous version of chirp, that would be helpful. Or of course, if this works, with the current version.

Some progress. Was able to upload radio, but radio shows err on front panel afterwards. A brief red flash on the chirp screen before displaying the image received.

Cannot copy memory items from my 7900 image to the 8100 image.

Built a couple of mems by hand, cannot upload to radio. Get error message Failed to clone: Failed to communicate with the radio: block not ack'ed: b'\x06' and err on ft8100 again.

Also,after trying to download from radio, tried opening the saved 2 channel memory image and copying the 2 images to the download image, would not copy.

Here's another module to try to address things in the latest debug log. I still want a .img file, captured either with the first module or this one.

Thanks for helping!

Here are the original that was downloaded, and the test one I tried to send to the radio.

Thanks for the images. I found several other memory-editing issues in the driver with them and have fixed those up.

I gotta be honest with you, this driver is ancient and not well-maintained. Since we didn't have a test image to go with it, it wasn't running tests and thus there were a number of issues with it. Some of those I could resolve, but not all.

So here's an updated driver module to try which hopefully makes it a lot better. I'll be glad to take another debug log and report with this one if you can. Thanks for the help, I'm sure any other FT-8100 users out there appreciate it too :)

The last .py was much better. Can upload and download VHF no problem. However, UHF channels not so much. Tried to add a UHF repeater, and got error that the frequencies were out of ranger. Put the repeater into the radio and it uploaded OK, but try to copy and paste one or add by hand on the UHF side of Chirp and got the frequency error again.

Still, very good progress.

Here's a fixed version where both sides have the same frequency ranges, renamed to "left" and "right". If my assumption above is correct, hopefully this is right. Let me know.

Thanks!

Nope, we lost ground. Can't copy into either VHF or UHF from my other radio image. Can enter UHF frequency manually however. Also, getting ERR on radio again when downloading into Chirp, and red flash at end of load.

Sorry. The FT8100 is usually set up as left/right VHF/UHF. You can change this dynamically using the buttons to VHF/VHF or UHF/UHF. You may only transmit on the "Main" channel, which you can select dynamically as well. At this point you can use the memory for that band on either side.

I have been saving the .py files in the same download area, and so they get re-numbers with the highest number being the latest pull. I was using the "load Module" menu item from FILE to bring them in. I will use the HELP method and retry the operations.

As a further comment, the FT8100 does support split mode (weird offsets) but only within the same BAND. (IE VHF TX must be in TX range, UHF TX must be in UHF range. The FT7900 does allow splits between VHF and UHF, but is not full duplex and the memories are common, no separated. In the image attached the memory 80 (145.800) was added manually to the radio with a split TX of 145.000. I modified the py you sent to enable the split choice on duplex and it did show up (but with weird offset). I saw the comment in the py module that this is not figured out yet, but thought I'd let you know. The py file I loaded this time is your original, no changes.

I was able to copy in a vhf and uhf channel from the FT7900, and they got sent correctly to the radio. This is excellent!

Bill
Bill

Okay, I did some more reading of the manual last night and made some more changes. I think those all line up with your explanation. So, give this latest one a shot if you would. If this is good (or at least almost good) I'd like to get this merged tonight for a build tomorrow.

We can iterate on some of the details (like the split thing) in a separate effort. The radio's support for >1GHz also needs some attention.

Thanks!

Applied in changeset github|fc76242c20a37b939f6b880372d9ff0922455df1.

I agree this is working quite well. Funny that the mem 80 is coming in as split, when it is not a choice, hi hi.

Do you want me to open a new bug on supporting the split feature of the radio? I am definitely will to work with you more on this.

Thanks again for the excellent work, now I can much more simply program this beast.

Bill