Bingo. Thanks again.
Oh my: the logic is in TWO places! D’oh! I should have noticed that.match_model is also required to reflect directory.register_format. *sigh*
The CHIRP .img file for Yaesu FT2D has a prefix ‘AH60M’ followed by 0xc0fd010002. I do see the postpended CHIRP metadata footer that’s mostly in binhex format.
The equivalent Yaesu Adms .ft2d filehas 22 hex bytes followed by 0xc0fd010002 (same digits; I think the valid length of the image is 0x0010fdc0. Adms also postpends a metadata footer. And if I read in a .ft2d file, I can write a CHIRP .img file, and it’ll have BOTH metadatas.
The FT-3D Adms does it differently. Another *sigh*
The SD-card image has none of these prefixes.
<SNIP>It's hard to say without seeing your code, but... did you make your match_model() also indicate that those files match?
<SNIP>I'm not sure what "CHIRP prefix" you mean exactly. There's a "metadata footer" that chirp adds to image files, but most drivers are (should be) 1:1 with the memory mapping of the radio until the end of memory and the metadata footer starts.
--Dan
_______________________________________________
Developers mailing list --
developers@lists.chirpmyradio.comTo unsubscribe send an email to
developers-leave@lists.chirpmyradio.com