CHIRP

I will try this. Are there instructions on how to attach the debug log? Also, can "Next" and "Legacy" open the same configuration? I would like to grab what I have set up for my Baofeng and copy/paste into the 2900 configuration. If I can open that config using "Legacy", that would be very helpful. Otherwise, I also can't get the .csv import to work, so cannot use that as a workaround.
Thank you.

See How_To_Report_Issues. Images of the radio will be open-able in both versions yes. However, it's the cloning that needs work, not so much the rest. If you can download and upload in legacy and not next, that's (likely) all we need to fix.

So, wouldn't that be considered a new model for "Next", since it is not supported currently? I'm new to this, but trying to help.
Thanks.

No, it's already supported. You see it in the download model selection box right? The bulk of the driver is already present and working, you can open images of the radio you have captured by other means (like -legacy). It's the cloning to and from the radio that likely needs tweaking in -next but has not yet been tested to even know. It might work fine as it is (we won't know unless you test it).

Please, just try it and create a bug with a debug log if it doesn't work and we can go from there. If it does work, then create a "CHIRP-next report" according to the "how you can help" instructions I provided earlier so we can update the front page to say it works.

I will take a look at it as soon as I can. Waiting on cable to come in. In the meantime, where can I find a list of changes ("changelog") from one nightly "Next" version to another?

Looking back on this ticket, if it says "supported", it could be with either version, or possibly both versions of Chirp?

I think it might be beneficial to users and developers alike, if one could check off a checkbox indicating what version ("Next" or "Legacy") they are using, and further, the date of the version.

Then, it would make more sense for everyone involved, and allow programmers to group issues by which distribution, etc.

Just a suggestion.

Thank you.

I'm wondering how many of the changes you made for the 2800 will apply to the 2900 and maybe other models.

Sorry, I don't have those, so cannot test for you, but I am posting here in case anyone else wants to try it.

Best of luck.

Doug Nelson wrote in #note-9:

I'm wondering how many of the changes you made for the 2800 will apply to the 2900 and maybe other models.

Sorry, I don't have those, so cannot test for you, but I am posting here in case anyone else wants to try it.

Best of luck.

If nothing else, you might want to let people know that import is now working on "Next" version over in these bugs:

• Bug #2303 Yaesu FT-2800M can't read header.
• Bug #2477 Error when reading Yaesu FT-2800M
• Bug #3335 Yaesu FT-2800 can't read header
• Bug #3909 Yaesu FT-2800M can't read header
• Bug #3919 Yaesu FT-2800M can't read header
• Bug #5061 Yaesu FT-2800M, can't put into clone mode

Having trouble transmitting on the local repeater. The antenna I'm using works fine with Baofeng HT radios. Receive works fine on the FT-2800M, just transmit seems to be an issue.