[chirp_devel] Initial Yaesu FT-857 testing

[Marco IZ3GME]

On 27/01/2012 00:04, David Ranch wrote:
>
> Hello Macro, Dan,
>
> Here are my initial results. As you can see, a bit more work needs to be
> done. If you need me to do some additional tests, please let me know.

Thanks David for your precise report

>
> If I configured chirp and it sat there waiting for a while (30 seconds)
> without starting the Clone on the radio, it eventually throws an error:
[...cut...]
>
> A chirpw timeout was expected but the user dialog box on the GUI should
> be made to be less cryptic

Ok, the exception is more developer than user oriented right now, will 
change it at least for the first block

>
> If I tried again, with starting the Cloning on the radio, the cloning
> image begins to go to
> to Chirp but at the end, the radio says "Clone mode: ERROR" though Chirp
> seems to be happy:
>

This is not good: it means that the radio was expecting a ACK which 
never arrived (or which has been lost).
I have to investigate this.


> Looking in the resulting Chirp GUI, the downloaded memories look ok except

good news good news, i need good news  ;)


> no power levels were saved. Maybe this isn't saved on a per-memory basis?

Right, as far as I know they are saved per-band

> I don't see any of the HOME memories in the GUI

Righ, only regular memories are supported (as of today)

> I don't see any Memory group support in the GUI: valid groups a "Ma"
> through "Mj"
> -- need to test more as I didn't have any

memory group are not supported (yet)

> Did not try the split memory yet
> -- need to test as I didn't have any

This is the area that needs most of investigation.

> Sending from Chirp to the radio
>
> Transfer starts and seems to run fine up until the 99% mark:
>
> Chirp completes yet the FT857 is stuck where the radio's LCD shows a
> "full download bar" saying "clone mode: Sending" yet it never completes
>

I would not expect it to work after the failure during clone in.
There must be a packet more than expected ...


> Had to turn off radio to exit the "Sending" screen
>
> Upon restart, all memories and FT857 system settings were lost

I'm sorry, I should warn you not to clone back to radio if the clone in 
operation does not finish correctly.

> --> Sure would be nice if the program could also handle the higher level
> menu settings at lease just as a binary blob and allow to be able to
> restore or not-restore that when uploading back to the radio

The clone operation has no option: it simply send the whole memory of 
the radio. We change the content of the memories area but the rest of 
the blob is left as is, eg this the reason for wich you have to start 
with a clone.

> This seems to be the same behavior that Kurt KC9LDH saw with his FT-817

Right: seems that in both case we have clone protocol errors.
I will investigate Kurt log and see if I found something interesting.

> -----------------
> Misc
>
> In the Radio dialog, it's not remembering the last serial port I used.
> Specifically, I have my port named via UDEV as /dev/ft857_prog

Dan, can you take a look at this?

> Chirp About --> Credits doesn't show Marco

You are so precise in testing you scares me ;)
Thanks

73 de IZ3GME Marco