Bug #10916
closedCorruption causes radio to not be able to transmit
100%
Description
OK, I have 2 radios.
radio 1 Baofeng BF-F8+
radio 2 Yaesu FT-2800M
Baofeng has a bunch of repeaters programmed in, both 2M and 70cm
Yaesu is 2m only, and was received with 2m stations/repeaters already programmed in.
Original config on Yaesu was saved and set aside.
You'll see some history on programming Chirp for the Yaesu 2800 in some bugs here.
- Again, saved original config on Yaesu, and copied all lines in Chirp from the Baofeng.
- Pasted into Yaesu config, replacing everything.
- Got error for non-2m stations. Figured OK, program just clipped those out, carry on.
- Seemed OK at first.
- After some further modifications, could no longer transmit, but could receive. Not even sure which stations this is on, but likely all. Only know for sure that 2m does not work on 146.970, since I could talk on the Baofeng, and confirm it was not working.
- Went back and reloaded original config, and transmit worked again.
- Edited config, pasting in other stations, and mixed results. Eventually, same symptoms after pasting in more stations, even if only using 2M stations.
- Tried original config, then cut most stations out. Still works on targeted station.
- Added in 2 stations at a time, and eventually it croaked again.
- Noticed TSQL instead of "TONE" in one column. This must have come over from "Query Source" on either Radio Reference or Repeaterbook, into the Baofeng, which did not notice it.
- Tried both deleting stations with the TSQL and also not copying those in, but that might not have been the source of the problem, as it continued.
Is there something in one of these lines files you can identify that is the problem?
Files
Updated by Doug Nelson 7 months ago
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?
Updated by Jim Unroe 6 months ago
- File which channels (1-4) transmit Yaesu_FT-2800M_20231025.img which channels (1-4) transmit Yaesu_FT-2800M_20231025.img added
Load the attached image file for testing. Which of the first 4 channels will transmit?
Updated by Doug Nelson 6 months ago
1 did not work at all.
2 worked
3 worked
4 worked. This one, multiple people said this one was most clear by far.
Updated by Jim Unroe 6 months ago
Thanks for the testing. Please test the attached driver module. You will likely have to repeat the steps that you previously performed to create the FT-2800M image.
See LoadingTestModules for instructions.
Updated by Doug Nelson 6 months ago
Open file, then load module? Or load module, then open file?
You want me to do this, then test the 4 again?
D.
Updated by Jim Unroe 6 months ago
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.
Updated by Doug Nelson 6 months ago
- File chirp_debug-guk9xtxe.txt chirp_debug-guk9xtxe.txt added
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
Updated by Jim Unroe 6 months ago
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.
Updated by Doug Nelson 6 months ago
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.
Updated by Doug Nelson 6 months ago
- File Yaesu2800_102923.img Yaesu2800_102923.img added
Here is the one I used.
channel 5 I think reached the repeater to get it to respond, but I did not hear any voice.
channel 18 showed 146.201 when I keyed the mic
same with channel 25.
Updated by Jim Unroe 6 months ago
- File ft2800_initialize_unknowns.py ft2800_initialize_unknowns.py added
- File test2 Yaesu_FT-2800M_20231025.img test2 Yaesu_FT-2800M_20231025.img added
Doug Nelson wrote in #note-14:
Here is the one I used.
channel 5 I think reached the repeater to get it to respond, but I did not hear any voice.
channel 18 showed 146.201 when I keyed the mic
same with channel 25.
Too many channels. I don't know which ones existed, which ones were working and which ones no longer work.
The fist 11 channels (0-10) indicate to me that the test driver wasn't loaded.
I think I noticed something that I missed on the previous test driver. So here is the latest revision. Plus I have attached a file with 3 channels. 1 was copied from the FT-2800M image. 2 was copied from the BF-F8HP image. 3 was keyed in directly.
Updated by Doug Nelson 6 months ago
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?
Updated by Doug Nelson 6 months ago
- File loaded-10015-i5tl99uv.py loaded-10015-i5tl99uv.py added
Nothing on all 3, though the screen looks like there is traffic.
At first, the radio came up with unreadable gibberish on the screen. Another reboot cleared that.
Can hear on the 2800 when I talk from HT. Checked on HT, and nobody can hear anything on all 3 stations, but can hear me fine on HT.
Couldn't find the log file this time, but there was a .py file there, so loaded that.
Updated by Doug Nelson 6 months ago
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.
Updated by Jim Unroe 6 months ago
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.
Updated by Doug Nelson 6 months ago
- File original good config Yaesu_FT-2800M_20230604 just one line with station.img original good config Yaesu_FT-2800M_20230604 just one line with station.img added
How about this?
This time, I took out all but the one station. Rebooted radio, It came up with a bunch of vertical lines. Shutting it off and turning it one did not help. Turned off power supply also, which did not help. Turned the dial, and another station was still showing. Rebooted againk, and it came up with just the one in the file. Then that one was unable to transmit also.
I am attaching that here. I was going to test it, and was hoping it would work, and then I would add a "dead station" and submit that, but did not get that far. Here you go.
Updated by Doug Nelson 6 months ago
Now, I am going back to put in the original file with no edits, just to make sure that still works.
It works.
Updated by Jim Unroe 6 months ago
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?
Updated by Jim Unroe 6 months ago
- File ft2800_initialize_unknowns.py ft2800_initialize_unknowns.py added
- File test3 Yaesu_FT-2800M_20231025.img test3 Yaesu_FT-2800M_20231025.img added
OK. I think I was able to answer those questions myself. I belive that I see the difference. Hopefully this one does it.
- Load the latest ft2800_initialize_unknowns.py test module
- Load the test3 Yaesu_FT-2800M_20231025.img file
- Upload to your radio
- Test
Channel 0 is the 'bad' channel
Channel 1 is the 'good' channel from the 'original' image
Channel 2 is a CHIRP entered channel
Channel 3 is the channel copy-and-pasted from the BF-F8+ image
1, 2 and 3 are now the same except 3 has Tone Mode = TSQL and Power = Low1 (as it should be based on the settings for the BF-F8+)
Updated by Doug Nelson 6 months ago
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.
Updated by Doug Nelson 6 months ago
OK.
0 did not work at all.
The remaining 3 all worked.
What did you find?
Thank you!
Updated by Jim Unroe 6 months ago
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
Updated by Doug Nelson 6 months ago
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.
Updated by Anonymous 6 months ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset github|33fd31028ec1127c784d72cf4ecf5e3f6e193f10.