CHIRP

Will look tonight. Did you find something specific? If so, was it something an end user could/should see, or did some corruption creep in programatically?

It did not work.

Doug

Doug Nelson wrote in #note-3:

It did not work.

Doug

OK. I will try to give it another look tomorrow.

1 did not work at all.
2 worked
3 worked
4 worked. This one, multiple people said this one was most clear by far.

Open file, then load module? Or load module, then open file?
You want me to do this, then test the 4 again?

D.

Doug Nelson wrote in #note-8:

Open file, then load module? Or load module, then open file?
You want me to do this, then test the 4 again?

D.

You will load this file as described in the instructions. Then CHIRP should be temporarily 'fixed' for the FT-2800M. Create a new FT-2800M image file like you did before. Then upload it to your radio to see if it solved the problem.

Doug Nelson wrote in #note-10:

OK
ran latest Chirp "next"
did the load module from issue 10916
found original file that came with radio (known good)
did a save as to create a new working file (named workingfile10292023)
added lines from another config file, which works on Baofeng radio, some of which did not come over due to 2M only
uploaded to radio, reboot radio
did not work
attached log

What I need is a copy of the image file that was uploaded into the radio.

Wait, that one is working, or at least partially working. Hold on a sec. So many changes, I grabbed a working one I made after the last one blew up.

The first group was from the original working config. The other 2 were from Baofeng BF-F8+ and Baofeng GT-5R.

I'll use yours, doing same instructions as above.

run latest Chirp "next"
loaded module from issue 10916 (2023-10-29T16:37:03Z)
saved your latest file test2 Yaesu_FT-2800M_20231025.img
opened test2 Yaesu_FT-2800M_20231025.img with Chirp next
uploaded test2 Yaesu_FT-2800M_20231025.img to radio
rebooted radio

funny, it took a sec to start loading. Maybe just me being impatient.
Do I do anything with that File ft2800_initialize_unknowns.py ? Or is that what comes in when I do load module?

Using the regular CHIRP, provide an image with 2 adjacent channels with the same frequency. One that works and one that doesn't.

I can go get my original FT-2800 file that works for all, then cut out everything but the one we're looking at.

Would it be OK to just grab one of your non-working ones, and paste that immediately after?

Thanks.

Doug Nelson wrote in #note-19:

I can go get my original FT-2800 file that works for all, then cut out everything but the one we're looking at.

Would it be OK to just grab one of your non-working ones, and paste that immediately after?

Thanks.

Yes. That would be fine. Just make sure to confirm with your radio that one works and the other doesn't. Thanks.

Now, I am going back to put in the original file with no edits, just to make sure that still works.

It works.

Doug Nelson wrote in #note-22:

Now, I am going back to put in the original file with no edits, just to make sure that still works.

It works.

OK. This is not exactly what I was looking for. I was looking for an image with a good channel and bad channel for the same frequency/channel that I could compare.

So is this single channel a bad channel? If yes, then which channel on the "original file" is the matching working channel?

It gave the vertical lines again after reboot. Then I hit the A/N button, and it shows "FITCH" (one of the old stations, which wasn't even one of the 4 you sent in this file. Finally, after going around the dial a couple times, the "FITCH" went away.

There is a net and traffic on the repeater right now, so I will have to test a little later.

OK.
0 did not work at all.
The remaining 3 all worked.

What did you find?
Thank you!

Doug Nelson wrote in #note-26:

OK.
0 did not work at all.
The remaining 3 all worked.

What did you find?
Thank you!

There are 4 areas in a channel's memory structure that are labeled 'unknown'. The first area is 4 bytes long. It is very obvious that it is set to /xFF/xFF/xFF/xFF in a good channel and set to /x00/x00/x00/x00 in a bad channel. When I hex edited first image for you to test, I changed areas 1, 3 and 4 to use /xFF but accidentally overlooked area 2 (leaving it set to /x00). That worked.

Then when I made the test driver module I assumed all unknown areas got initialized to /xFF so I coded it that way. That is when you reported it not working at all. When I reviewed your new image this morning, I noticed that area 2 looked like it always /x00/x00 for a good channel. So I made the update to initialize area 2 to /x00/x00. Success!

So I am glad that we finally isolated the problem. We may not know what these 4 areas are used for, but it is now very obvious that if they are not initialized a certain way, the radio is not happy.

I've probably got time to create a formal patch and get it submitted yet tonight. In the mean time, just use the test driver module whenever you need to edit your FT-2800M

Thank you SO much for your patience and persistance. Sometimes, I am coming from work or kids or the dog or other things, and am not fully on task here. Other times, I am totally OCD, but maybe in a different direction than you were heading. Glad we were able to work together to get this. It looks like this will do it. I hope it is able to help others with this radio. I think the Yaesu 2900 and 2980 are similar to or derivatives of this one. This will also help Chirp to flourish and help more people out.

My patch has been submitted, accepted and merged. The changes should be in the next CHIRP build.