Bug #871
closedFT-817ND 60 Meter channel 3 location M603 re-defaulted on CLONE exit (?)
0%
Description
I just noticed a problem when I read back the memories and special registers of my FT-817ND after changing the M603 60 meter channel. I put the transceiver into clone mode and can load the modified frequency down into the transceiver. If it does not exit clone mode, but instead remains in clone mode and then do a read from the receiver back into Chirp, the frequency looks just like we want it to with the new frequency. However, as soon as I press Power to restart the radio, it seems like the transceiver firmware puts the original frequency back into place. This would be really dumb, but is there a way other than the power button to exit clone mode that I should do. It works when writing all of the other modes and registers, but the 60 meter channel change is being stubborn. :-/
I have one of the first FT-817ND (US version) that came off of the assembly line when production resumed in mid 2012 after the manufacturer having to recover from the water damage that occurred. I read elsewhere that they needed to locate a new LCD supplier, so I do not know what if any differences there may be in the firmware from pre-tsunami flood versions. It works great, but I just recently realized that the newly set third 60 meter channel frequency change doesn't stay in place.
Has anyone else seen this? I use Chirp on a fully service packed and updated Win XP Pro box with the Yaesu/RT Systems USB-62B cable. So now I'm wondering if this is a new FT-817ND firmware lockdown, or if there is something that I have missed. Therefore I don't know if this is a Chirp bug, or something weird in the FT-817ND. Thanks for any suggestions or ideas. Let me know if there are any test procedures that you would like me to do. In the mean time, I'm going to get my old Vista 32 box back up and try it there in case it is some sort of XP thing.
73
de Jack AK4UV
Updated by Filippi Marco about 12 years ago
- Status changed from New to Incomplete
I'd like to investigate this a little more but I need your help.
There are two separate test I would try
came out of clone mode switching off the radio by disconnecting it from power then switch it on as usual then check if the hange did stay in place; please be carefull DON'T DISCONNECT RADIO WHILE CLONING IS IN PROGRESS, wait for the clone operation to finish.¶
After programming the radio and switching it off by power button, restart it again in clone and download to chirp to see if the value is still there¶
Let me know the results, this can help us determine when, exactly, the radio overwrite the memory.
Updated by Jack Swindell about 12 years ago
Interesting find: IF I do both of the following:
- Use 9600 Baud
- Have the 12 Volt charger plugged into the back of the transceiver
THEN the write is successful and is NOT returned to the default 60 meter frequency after power cycling. Maybe this is like some sort of protection for the normally read only flash settings. Good question, but if I do both of these things, it works. Therefore this is not any kind of Chirp bug, but it is a quirk of at least my build of FT-817ND. Has anyone else run into this? Oh well, I'm baffled but happy.
de Jack AK4UV
Updated by Tom Hayward about 12 years ago
Is this repeatable? I've seen lots of inconsistency programming Yaesu rigs before. Works one time and not the next, without changing any inputs. Before jumping to any conclusions, we should be sure that the results are consistent.
Updated by Filippi Marco about 12 years ago
- Status changed from Incomplete to Rejected
- Model affected changed from (All models) to FT817ND
Well ... I don't really understand how the 9600 setting can be of any influence (communication in clone is always and only at 9600) but anyway your finding confirm my suspect that there's nothing I can do in Chirp.
The best news here is that M60x memories are not reset at +each+ power cycle.
I close this issue as refused but you are welcome to report more info (if any) and we'll eventually reopen it.
Updated by Art Witmans almost 12 years ago
Had the same problem. Looks like it's a bug in the FT817. I discovered the following ''fix'':
1-Download From Radio.
2-Edit frequency M603.
3-Save file.
4-Shut down FT817ND
5-Master Reset FT817's CPU (home)+(power on).
6-Upload To Radio the edited file.
That did it for me!
Regards, Art