Project

General

Profile

Actions

Bug #10616

closed

Cannot get Yaesu FT-2800M to send its file to PC

Added by Doug Nelson about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
06/02/2023
Due date:
% Done:

100%

Estimated time:
Chirp Version:
next
Model affected:
Yaesu FT-2800M
Platform:
Windows
Debug Log:
I read the instructions above:

Description

Get: "Failed to communicate with radio: Failed to read header"

Started radio while holding MHz, Low, D/MR buttons. TX/RX flashes/alternates.

Go to get file from radio, and get the above message.

This is using software:
CHIRP legacy-20221217
downloaded as a .zip file, and run from the subsequent folder.

See also older bug:
https://chirp.danplanet.com/issues/5061

See also more recent bugs:
https://chirp.danplanet.com/issues/10605
https://chirp.danplanet.com/issues/5667

Please let me know what I can do to help test this.


Files

chirp_debug-ktpqvcdp.txt (5.38 KB) chirp_debug-ktpqvcdp.txt Doug Nelson, 06/02/2023 10:32 PM
chirp_debug-7z4xwm1g.txt (4.08 KB) chirp_debug-7z4xwm1g.txt Doug Nelson, 06/02/2023 10:32 PM
chirp_debug-mmcnrpxq.txt (6.54 KB) chirp_debug-mmcnrpxq.txt Doug Nelson, 06/02/2023 10:32 PM
chirp_debug-3_oi9ph3.txt (5.31 KB) chirp_debug-3_oi9ph3.txt Doug Nelson, 06/02/2023 10:48 PM
downloadsteps.JPG (36.4 KB) downloadsteps.JPG Doug Nelson, 06/03/2023 09:10 AM
port setup1.JPG (39.6 KB) port setup1.JPG Doug Nelson, 06/03/2023 09:10 AM
chirp_debug-udb__eg6.txt (2.77 KB) chirp_debug-udb__eg6.txt Doug Nelson, 06/03/2023 09:12 AM
chirp_debug-3_oi9ph3.txt (5.31 KB) chirp_debug-3_oi9ph3.txt Doug Nelson, 06/03/2023 09:12 AM
chirp_debug-17tjkt6_.txt (4.08 KB) chirp_debug-17tjkt6_.txt Doug Nelson, 06/03/2023 10:26 AM
newerrorafterhittingTonradio.JPG (43.4 KB) newerrorafterhittingTonradio.JPG Doug Nelson, 06/03/2023 10:29 AM
chirp_debug-ojq33b32.txt (2.77 KB) chirp_debug-ojq33b32.txt Doug Nelson, 06/04/2023 08:28 AM
chirp_debug-jnc9qiaz.txt (6.64 KB) chirp_debug-jnc9qiaz.txt Doug Nelson, 06/04/2023 08:28 AM
chirp_debug-xaj7y4p3.txt (2.77 KB) chirp_debug-xaj7y4p3.txt Doug Nelson, 06/04/2023 08:28 AM
ft2800.py (8 KB) ft2800.py 963ddeec Dan Smith, 06/04/2023 10:31 AM
debug.log (3.97 KB) debug.log Doug Nelson, 06/04/2023 10:46 AM
debug.log (6.68 KB) debug.log Doug Nelson, 06/04/2023 10:51 AM
clipboard-202306041351-dbzbr.png (14.4 KB) clipboard-202306041351-dbzbr.png Doug Nelson, 06/04/2023 10:51 AM
chirp_debug-o4u803t1.txt (2.77 KB) chirp_debug-o4u803t1.txt Doug Nelson, 06/04/2023 10:52 AM
ft2800.py (8.79 KB) ft2800.py bc228573 Dan Smith, 06/04/2023 10:55 AM
chirp_debug-9nh1kdb6.txt (5.96 KB) chirp_debug-9nh1kdb6.txt Doug Nelson, 06/04/2023 11:17 AM
debug.log (5.96 KB) debug.log Doug Nelson, 06/04/2023 11:18 AM
aftersecondmodulerun.JPG (21.9 KB) aftersecondmodulerun.JPG Doug Nelson, 06/04/2023 11:19 AM
chirp_debug-4nys7jci.txt (6.3 KB) chirp_debug-4nys7jci.txt Doug Nelson, 06/04/2023 11:54 AM
chirp_debug-_niwcutq.txt (6.3 KB) chirp_debug-_niwcutq.txt Doug Nelson, 06/04/2023 11:54 AM
debug.log (6.3 KB) debug.log Doug Nelson, 06/04/2023 11:55 AM
chirp_debug-avplk8az.txt (7.87 KB) chirp_debug-avplk8az.txt Doug Nelson, 06/04/2023 11:59 AM
debug.log (7.87 KB) debug.log Doug Nelson, 06/04/2023 12:01 PM
ft2800.py (9.2 KB) ft2800.py 25d9492f Dan Smith, 06/04/2023 12:44 PM
debug.log (7.22 KB) debug.log Doug Nelson, 06/04/2023 12:51 PM
chirp_debug-9vx578e0.txt (7.22 KB) chirp_debug-9vx578e0.txt Doug Nelson, 06/04/2023 12:52 PM
newerror.JPG (23.2 KB) newerror.JPG Doug Nelson, 06/04/2023 12:52 PM
chirp_debug-cjrrzwh5.txt (7.22 KB) chirp_debug-cjrrzwh5.txt Doug Nelson, 06/04/2023 12:54 PM
ft2800.py (9.2 KB) ft2800.py 0cf683d6 Dan Smith, 06/04/2023 01:05 PM
chirp_debug-cqf3r248.txt (72.3 KB) chirp_debug-cqf3r248.txt Doug Nelson, 06/04/2023 01:41 PM
debug.log (72.3 KB) debug.log Doug Nelson, 06/04/2023 01:42 PM
DownloadInstructions.JPG (27.5 KB) DownloadInstructions.JPG Doug Nelson, 06/04/2023 01:42 PM
06042023_SEND_ERROR.JPG (34.9 KB) 06042023_SEND_ERROR.JPG Doug Nelson, 06/04/2023 02:11 PM
chirp_debug-ziffi7tj.txt (149 KB) chirp_debug-ziffi7tj.txt Doug Nelson, 06/04/2023 02:12 PM
debug.log (149 KB) debug.log Doug Nelson, 06/04/2023 02:12 PM
debug.log (81.4 KB) debug.log Doug Nelson, 06/04/2023 04:17 PM
chirp_debug-m2yvaasg.txt (81.4 KB) chirp_debug-m2yvaasg.txt Doug Nelson, 06/04/2023 04:19 PM
Actions #1

Updated by Doug Nelson about 1 year ago

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

Actions #2

Updated by Dan Smith about 1 year ago

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.

Actions #3

Updated by Doug Nelson about 1 year ago

I could not find any debug logs, other than what I found under the help menu (in Next) Help:Open debug log.

I filed this against legacy, because I wanted to try that first, since you said that was working. It did NOT work for me. I got the same results in both if I remember correctly. I filed the "Next" logs, because that is all I could find.

I do the startup of the radio while holding in the 3 buttons. It comes up with flashing TX RX , then TxMHZ , then RX LOW. I go to receive file, and it gives the error.

Now I've found the "Show debug log location", so I'll load them in.

Actions #4

Updated by Doug Nelson about 1 year ago

Just tried again in both versions. I now see where I can hit on button to turn the radio to R for receive, and T for transmit (to Chirp). Same results with both legacy and next. Can't communicate, and can't read headers.

Actions #5

Updated by Doug Nelson about 1 year ago

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.

Actions #6

Updated by Dan Smith about 1 year ago

  • Chirp Version changed from legacy to next

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:

  1. You're using the wrong COM port
  2. There's a physical connectivity problem
  3. You're not doing the button dance properly (like choosing RX instead of TX or something)
  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.

Actions #7

Updated by Doug Nelson about 1 year ago

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?

Actions #10

Updated by Doug Nelson about 1 year ago

Latest:
I have it down to a science now.
All systems go.

In Chirp NEXT:
I go to Radio:Download from radio.
Port/Vendor/Model all correct.
Hit OK.
Go to next screen, follow all 4 steps.

On radio:
Hit the MHz button to get "T" (for transmit) button on radio.
As soon as I hit "T", the error pops up on computer, so obviously a signal is getting sent from radio to computer.
Ends there.

Actions #11

Updated by Doug Nelson about 1 year ago

Just tried again. This time I unplugged, and plugged back in the USB-to-mic cable, THEN hit the "T" button.

Actions #12

Updated by Doug Nelson about 1 year ago

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

Actions #13

Updated by Dan Smith about 1 year ago

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.

Actions #14

Updated by Doug Nelson about 1 year ago

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.

Actions #15

Updated by Doug Nelson about 1 year ago

Just tried it again (morning).
First time, the error came up on computer screen before I even did anything on the radio.
Second time, same behavior. Attaching log files with date and time close to just now, when I did it.

Actions #16

Updated by Dan Smith about 1 year ago

Here's a module to try. It likely won't solve everything but it will solve some of it and hopefully get farther. Instructions for loading are: LoadingTestModules. Please load it, attempt, and capture the debug log in that order in one chirp session.

Actions #17

Updated by Doug Nelson about 1 year ago

Dan Smith wrote in #note-16:

Here's a module to try. It likely won't solve everything but it will solve some of it and hopefully get farther. Instructions for loading are: LoadingTestModules. Please load it, attempt, and capture the debug log in that order in one chirp session.

Did it. "Module loaded successfully"

Added debug log as requested/instructed. I think in the past, I was getting them from the tmp directory, which Help menu sends you to.

Actions #18

Updated by Doug Nelson about 1 year ago

Just tried the import after doing this module import thing.
Picture of resultant error attached.
Latest log from new location attached.
Latest log from "Help" menu attached. (C:\Users\username\AppData\Local\Temp)

Actions #19

Updated by Dan Smith about 1 year ago

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.

Actions #20

Updated by Doug Nelson about 1 year ago

OK. Errored again.
Adding both logs and an image of the fail.

Actions #21

Updated by Doug Nelson about 1 year ago

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.

Actions #22

Updated by Dan Smith about 1 year ago

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.

Actions #23

Updated by Doug Nelson about 1 year ago

Just tried again to make sure I did it right. I did not unplug the cord and plug it in again, I just left it in. Maybe I'll unplug to follow exact instructions.

Actions #24

Updated by Doug Nelson about 1 year ago

Just tried again after unplugging.
This time, it errored before I even got to hit the MHz button to transmit/transfer.
I then left Chirp window open, and restarted radio, then tried again.

Actions #25

Updated by Doug Nelson about 1 year ago

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.

Actions #26

Updated by Dan Smith about 1 year ago

Still getting nothing from the radio in any of those attempts, unlike the earlier one where we did receive the header from the radio and got into the download phase.

I'm attaching an update that increases the timeout on the chirp side to give you more time to hit the button on the radio. I dunno if that's what you're struggling with, but maybe it will help.

As I mentioned before, this radio is extremely finicky with this process, very much more so than even the standard amount of finickiness that yaesus present.

Actions #27

Updated by Doug Nelson about 1 year ago

New error this time, plus radio now says "WARNING" instead of "ERROR".

Actions #29

Updated by Dan Smith about 1 year ago

Yep, another thing needing fixed, new version attached.

Actions #30

Updated by Doug Nelson about 1 year ago

Hooray! Was able to get the 0000 and receive a file.

Still, it left a warning on the radio "WARN08".

I will attach logs in case there are errors I don't see, or any tweaks. But, we are getting closer.

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).

Actions #31

Updated by Dan Smith about 1 year ago

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.

Actions #32

Updated by Doug Nelson about 1 year ago

Dan Smith wrote in #note-31:

I have to stop here for a while.

No problem. This has sucked some of my time as well. Got some lime down on my lawn in between.

Be sure to capture and save a .img file.
DONE! (saved it in 2 different places, as I learned that lesson by saving to the original's location once. ONCE!)

Then I modified my newly downloaded config, by copying/pasting in some settings from a couple good profiles on 2 Baofengs.

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.

Oh-oh. I did try it, and got some issues.
See attached snip for the first one. Will also attach logs.

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.

OK. I will likely stop here for a while myself.
Progress.

Actions #33

Updated by Dan Smith about 1 year ago

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.

Actions #34

Updated by Doug Nelson about 1 year ago

Got the 0000, and "PASS".

Attaching logs, in case you see any anomolies.

Thank you!

Actions #35

Updated by Dan Smith about 1 year ago

  • Assignee set to Dan Smith
  • Target version set to chirp-py3

Yep, log looks clean. I'll queue this up.

Actions #36

Updated by Doug Nelson about 1 year ago

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.

Actions #37

Updated by Dan Smith about 1 year ago

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).

Actions #38

Updated by Dan Smith about 1 year ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions #39

Updated by Doug Nelson about 1 year ago

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.

Actions #40

Updated by Dan Smith about 1 year ago

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.

Actions #41

Updated by Doug Nelson about 1 year ago

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.

Actions #42

Updated by Doug Nelson about 1 year ago

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

Actions #43

Updated by Doug Nelson about 1 year ago

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

Actions #44

Updated by Doug Nelson about 1 year ago

Doug Nelson wrote in #note-43:

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

Just making sure you saw this.

Actions #45

Updated by Doug Nelson about 1 year ago

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.

Actions #46

Updated by Doug Nelson about 1 year ago

Still need to add the "R".

Actions

Also available in: Atom PDF