CHIRP

Found the log, if this is what you are looking for:

[2023-06-03 00:24:40,602] chirp.logger - DEBUG: CHIRP next-20230531 on Win32 (Unknown 10.0:19045) (Python 3.10.8)
[2023-06-03 00:24:40,712] chirp.wxui - DEBUG: Using locale: en_US (276)
[2023-06-03 00:24:40,721] chirp.wxui - DEBUG: Translation loaded=True for CHIRP: en_US (de,el,en_US,es,fr,hu,it,nl,pl,pt_BR,ru,tr_TR,uk_UA,zh_CN) from C:\Program Files (x86)\CHIRP\chirp\locale
[2023-06-03 00:24:40,730] chirp.wxui - DEBUG: Translation loaded=False for wxstd: en_US (af,an,ar,ca,ca@valencia,co,cs,da,de,el,es,eu,fa_IR,fi,fr,gl_ES,hi,hr,hu,id,it,ja,ka,ko_KR,lt,lv,ms,nb,ne,nl,pl,pt,pt_BR,ro,ru,sk,sl,sq,sv,ta,tr,uk,vi,zh_CN,zh_TW)
[2023-06-03 00:24:41,149] main - INFO: Python/3.10.8 // Windows/Windows-10-10.0.19045-SP0 // CHIRP/next-20230531 // wx/4.2.0 msw (phoenix) wxWidgets 3.2.0
[2023-06-03 00:24:41,166] chirp.wxui.main - INFO: Ignoring dist stock conf DE Freenet Frequencies.csv because same name found in user dir
[2023-06-03 00:24:41,166] chirp.wxui.main - INFO: Ignoring dist stock conf EU LPD and PMR Channels.csv because same name found in user dir
[2023-06-03 00:24:41,166] chirp.wxui.main - INFO: Ignoring dist stock conf FR Marine VHF Channels.csv because same name found in user dir
[2023-06-03 00:24:41,166] chirp.wxui.main - INFO: Ignoring dist stock conf KDR444.csv because same name found in user dir
[2023-06-03 00:24:41,166] chirp.wxui.main - INFO: Ignoring dist stock conf NOAA Weather Alert.csv because same name found in user dir
[2023-06-03 00:24:41,166] chirp.wxui.main - INFO: Ignoring dist stock conf SE Jaktradio 155MHz.csv because same name found in user dir
[2023-06-03 00:24:41,166] chirp.wxui.main - INFO: Ignoring dist stock conf UK Business Radio Simple Light Frequencies.csv because same name found in user dir
[2023-06-03 00:24:41,166] chirp.wxui.main - INFO: Ignoring dist stock conf US 60 meter channels (Center).csv because same name found in user dir
[2023-06-03 00:24:41,167] chirp.wxui.main - INFO: Ignoring dist stock conf US 60 meter channels (Dial).csv because same name found in user dir
[2023-06-03 00:24:41,167] chirp.wxui.main - INFO: Ignoring dist stock conf US CA Railroad Channels.csv because same name found in user dir
[2023-06-03 00:24:41,167] chirp.wxui.main - INFO: Ignoring dist stock conf US Calling Frequencies.csv because same name found in user dir
[2023-06-03 00:24:41,167] chirp.wxui.main - INFO: Ignoring dist stock conf US FRS and GMRS Channels.csv because same name found in user dir
[2023-06-03 00:24:41,167] chirp.wxui.main - INFO: Ignoring dist stock conf US MURS Channels.csv because same name found in user dir
[2023-06-03 00:24:41,167] chirp.wxui.main - INFO: Ignoring dist stock conf US Marine VHF Channels.csv because same name found in user dir
[2023-06-03 00:24:41,598] chirp.wxui.main - INFO: Server reports next-20230602 is latest
[2023-06-03 00:33:47,057] chirp.wxui.clone - DEBUG: Using port 'COM7'
[2023-06-03 00:33:47,057] chirp.wxui.clone - DEBUG: Selected
[2023-06-03 00:33:47,066] chirp.wxui.clone - DEBUG: Showing pre_download prompt
[2023-06-03 00:33:57,119] chirp.wxui.clone - DEBUG: Setting flag for prompt pre_download
[2023-06-03 00:33:57,448] chirp.wxui.clone - DEBUG: Serial opened: Serial(port='COM7', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=0.25, xonxoff=False, rtscts=False, dsrdtr=False) (rts=True dtr=True)
[2023-06-03 00:34:00,069] chirp.drivers.ft2800 - DEBUG: Header:

[2023-06-03 00:34:00,069] chirp.wxui.clone - ERROR: Failed to clone: Failed to communicate with radio: Failed to read header
Traceback (most recent call last):
File "chirp\drivers\ft2800.py", line 201, in sync_in
File "chirp\drivers\ft2800.py", line 51, in _download
Exception: Failed to read header

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "chirp\wxui\clone.py", line 66, in run
File "chirp\drivers\ft2800.py", line 205, in sync_in
chirp.errors.RadioError: Failed to communicate with radio: Failed to read header
[2023-06-03 00:34:06,737] chirp.wxui.clone - DEBUG: Using port 'COM7'
[2023-06-03 00:34:06,737] chirp.wxui.clone - DEBUG: Selected
[2023-06-03 00:34:06,745] chirp.wxui.clone - DEBUG: Showing pre_download prompt
[2023-06-03 00:34:13,544] chirp.wxui.clone - DEBUG: Setting flag for prompt pre_download
[2023-06-03 00:34:13,855] chirp.wxui.clone - DEBUG: Serial opened: Serial(port='COM7', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=0.25, xonxoff=False, rtscts=False, dsrdtr=False) (rts=True dtr=True)
[2023-06-03 00:34:16,513] chirp.drivers.ft2800 - DEBUG: Header:

[2023-06-03 00:34:16,513] chirp.wxui.clone - ERROR: Failed to clone: Failed to communicate with radio: Failed to read header
Traceback (most recent call last):
File "chirp\drivers\ft2800.py", line 201, in sync_in
File "chirp\drivers\ft2800.py", line 51, in _download
Exception: Failed to read header

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "chirp\wxui\clone.py", line 66, in run
File "chirp\drivers\ft2800.py", line 205, in sync_in
chirp.errors.RadioError: Failed to communicate with radio: Failed to read header
[2023-06-03 00:34:43,414] chirp.wxui.clone - DEBUG: Using port 'COM7'
[2023-06-03 00:34:43,414] chirp.wxui.clone - DEBUG: Selected
[2023-06-03 00:34:43,422] chirp.wxui.clone - DEBUG: Showing pre_download prompt
[2023-06-03 00:34:53,657] chirp.wxui.clone - DEBUG: Setting flag for prompt pre_download
[2023-06-03 00:34:53,990] chirp.wxui.clone - DEBUG: Serial opened: Serial(port='COM7', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=0.25, xonxoff=False, rtscts=False, dsrdtr=False) (rts=True dtr=True)
[2023-06-03 00:34:56,604] chirp.drivers.ft2800 - DEBUG: Header:

[2023-06-03 00:34:56,604] chirp.wxui.clone - ERROR: Failed to clone: Failed to communicate with radio: Failed to read header
Traceback (most recent call last):
File "chirp\drivers\ft2800.py", line 201, in sync_in
File "chirp\drivers\ft2800.py", line 51, in _download
Exception: Failed to read header

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "chirp\wxui\clone.py", line 66, in run
File "chirp\drivers\ft2800.py", line 205, in sync_in
chirp.errors.RadioError: Failed to communicate with radio: Failed to read header
[2023-06-03 00:35:00,646] chirp.wxui.clone - WARNING: Stopping clone thread

If you could attach debug logs as files instead of pasting them, that would be better, thanks.

You filed this bug against -legacy and reported the legacy version, but your debug log is from -next (which is what we need). As mentioned, we'll only fix things in -next, so I'm confused about the report here. Were you trying to say you get the same behavior in -legacy as -next? If so, I'll flip this to -next.

Either way, it looks to me like you're not initiating the clone from the radio side as the PC never receives anything. I notice that this driver doesn't give you instructions like it does for most other Yaesus, so I should fix that. The Yaesu won't behave like your other radios where you just need to have it on and CHIRP can start the transfer. Here's the rough procedure you need to do:

1. Put the radio in clone mode
2. Start the download from CHIRP, CHIRP starts waiting
3. Push one of the buttons on the radio to start the clone TX before CHIRP times out

The button to push to start the TX from the radio differs among models, so you'll need to look in the manual. I think you're missing step 3, which is why CHIRP reports nothing was received from the radio.

I assume since they are both broken in the same way, and you are not doing development on the older, legacy system, that you want me to just focus on the "Next" version?
Thanks.

Dan Smith wrote in #note-6:

The message you're getting (and your debug log) shows that chirp isn't getting anything from the radio at all - not a single byte. So neither version is showing any sign of being broken because it's not getting that far. Reasons for this are:

OK, will tackle these.

1. You're using the wrong COM port
   I've got that right.

2. There's a physical connectivity problem
   Everything is good physically. The computer sees the cable, and it is a brand new cable and firmly clicks into radio.

3. You're not doing the button dance properly (like choosing RX instead of TX or something)
   Checking again now.
   You are going to have to elaborate on "set radio to clone" directions. I get the TX RX, but when I hit MHz to transmit, it gives the error.

4. Something is up with your cable or the driver for it

Until you've got a debug log showing it's receiving something from the radio (and doing something wrong with it) there's nothing I can fix for you.
As soon as it goes to transmit, it gives the error.

Going to need more step by step instructions. At what point do I hit "OK" on computer, then hit buttons on radio?

I await your next steps to troubleshoot this in "NEXT" version.

Okay yep, that error screenshot is a "next problem" that I can fix. However your latest debug log is not from a situation where you hit that problem, it is again the situation where you got nothing from the radio. So please try to reproduce the problem again until you get that same error on the screen and then capture the debug log after that and attach.

Dan Smith wrote in #note-13:

Okay yep, that error screenshot is a "next problem" that I can fix.

However your latest debug log is not from a situation where you hit that problem, it is again the situation where you got nothing from the radio.

It is all I have to offer you.

So please try to reproduce the problem again until you get that same error on the screen and then capture the debug log after that and attach.
Every time, it does the same thing. As soon as I hit the "T" to transmit, the error pops up. So, it is doing something to cause the error on the PC. But, apparently, it does not get to Chirp. Is there a way to diagnose the driver is correct?

Thanks.

Dan Smith wrote in #note-19:

I also added radio-specific download instructions for this one, so please check that those look right as well.

I will check next go-around. Was not looking closely enough, but I did notice something changed. Will do next time.

Both recent debug logs show nothing at all received from the radio. Your earlier one (marked o4u803t1) is the only one I've seen you show that has received anything from the radio.

Dan Smith wrote in #note-19:

Okay yep it got farther and hit another thing. Here's another one attached to try.

I also added radio-specific download instructions for this one, so please check that those look right as well.

Maybe you could add those to the next release, to save the extra steps in testing?
It is not like those small tweaks would break anything else.
Thanks.

I have to stop here for a while. Be sure to capture and save a .img file. The upload process will be another can of worms and your radio will be reset in the process until we get it right. If that's not a problem you can try that and see what happens.

I dunno what the warn message means, likely the radio isn't getting some ack it expects back. We'll have to treat that separately, but let's wait until I have looked at the log to see if maybe it's something failing right at the end.

It doesn't look like you loaded the module in the session where you tried the upload. Loading the module makes it active until you quit chirp, so if you quit chirp, opened your image and then uploaded, it's still using the old driver. You need to load the module before you open the .img file and before you attempt the upload.

One final thing. Chirp's 1st column is "Frequency". The second column is "Name". The radio seems to display the frequency, not the label. On the older, original config, it displayed the label. If I get into the programming area called "labeling memories" here: https://www.manualslib.com/manual/186232/Yaesu-Ft-2800m.html?page=33#manual , it shows the label from the "Name" column. I just can't seem to get it to display these. Not sure if it is coming over like that, or if it is something I need to tell the radio to do somehow. Any ideas?

OTHERWISE, thank you SO much for your patience and help on this. I hope this work is able to help others as well. One more supported model soon for the "Next" group.

This is because the radio has a flag in memory to display the name or the frequency and chirp doesn't support setting that flag (for that radio). But, since this is a different issue, let's (i.e you) open another bug (let's use a bug not a feature) for that and we can work it separately. When you do I'll explain the procedure I need you to do to suss out that flag (hopefully).

Doug Nelson wrote in #note-30:
...

On the download instructions, you should say it is "Flashing Tx Rx, then Tx MHz, then Rx LOW", and then you hit MHz to send, and hit LOW to receive from the computer." (or however that is best worded).

Think you could get this language added in? It would make it more clear to people, since that is exactly what is being displayed.

I did add another step for "flashing TX/RX" since the version you saw. I want to be judicious with those descriptions because the translators need to be able to convey the same meaning in roughly the same amount of text in all the other languages we support. Some of the radios also have different markings and messages in other markets, and the translators rarely have access to the radios they're translating for. "TX/RX" and "Flashing" is probably fairly universal and straightforward, so I added that.

Dan Smith wrote in #note-40:

I did add another step for "flashing TX/RX" since the version you saw. I want to be judicious with those descriptions because the translators need to be able to convey the same meaning in roughly the same amount of text in all the other languages we support. Some of the radios also have different markings and messages in other markets, and the translators rarely have access to the radios they're translating for. "TX/RX" and "Flashing" is probably fairly universal and straightforward, so I added that.

I see you added a "step 5", but it starts at the end of the 4th line, not on its own line; for both send and receive.

It is flashing "R" for receive, not RX.

Actually, it is a solid "R" after hitting LOW button.

Doug Nelson wrote in #note-43:

Actually, it is a solid "R" after hitting LOW button.

Just making sure you saw this.

Doug Nelson wrote in #note-44:

Doug Nelson wrote in #note-43:

Actually, it is a solid "R" after hitting LOW button.

Just making sure you saw this.
Did not see a change come through.

Still need to add the "R".