CHIRP

Edit/Update (nov 20 2019 11:12)

Hi everybody, i complete my previous post/request :

I tried to add the concerned frequency in the .img file got from the "just out the box",
(first case mentioned) and unfortunately i also had the error (mentioned in 2nd case).

I also tried to set one memory in the Puxing's app, and send it to the radio, and then get
it from Chirp (like i did manualy on the radio), and like first time, the frequency appears
correctly in the memory, but it's impossible to modify the memory (same error). But no
problems with the settings tab (options are available in it). :-s

Sorry for the lack of precisions on my 1st message, i didn't tried these manips before ! :-s

But i'm passionnated, and a kind of "fanatic" ;-) . So i tried to edit the semi-functionnal
.img file (where the settings are available, and where it's not possible to add certain
frequencies (the ones i wanted, of course.... :-s ;-) )).

And i finally i reached my goal (to have my frequencies/ctcss/dcs/names in memories, and
being able to have acces to settings). But it's not real a solution, far from this, even
not for me because i still can't edit memories in Chirp (still the error of course).

But for the interested, here is what i discovered and did (like a kind of ugly workaround) :

It was not easy, not practical, but i "tweaked" the .img file i got from the radio with one
memory configured directly from the radio (same if the file came from the Puxing app got
from : http://www.radioshop888.com/shop_displaynews.php?id=292&locate=1 , direct dl
link : http://pic.radioshop888.com/abc/software/PUXING/2012032241652581.rar ) and
completed with several valid memories added in chirp "on demand".

So, i edited the file with an hexadecimal editor (HdX, from https://mh-nexus.de/en ,
dl link : https://mh-nexus.de/downloads/HxDSetup.zip ) and here is what i found/did :

Each 128 memories (at least for this radio) are stored on 16 bytes from the begining of
the file up to 128. So i added the memories i wanted.

The names of the memories are at the offsets 0x800 / 0x808 and so on with a multiple of
16 (0x810 / 0x818, 0x820 / 0x828...). So i named my memories as i wanted.

And the last, but not the least thing, even important, because if it's not set correcly,
the memories are not seen in Chirp, the positions of memories used are stored at
offsets 0xC20 and 0xC30. I calculated and set the corrects values.

And then i loaded the file in Chirp, and it was correct. So i sent the datas to my radio
and i successfully tested it. :-)

That's not marvellous and it was somewhere mostly for fun because i could use the
Puxing's soft, but it function. :-) At least i learnt how Chirp store part of it's datas ! ;-).

I join a tiny .txt file with explanations about all i discovered and did.

I don't consider me as a develloper (not yet ! ;-) ), but perhaps i could help !?.
If so, tel me HERE please ! ;-)

Sincerely,

Ti'R.

The empty Settings tab problem occurs (with any radios) if there's an out-of-range parameter in the radio. That's why you got the settings back after a reset. This is a known problem.

The 6.25 kHz step issue should be followed up on. Apparently this radio does support it - perhaps it's a bug in Chirp.

Thanks for your suggestions! You might want to review the Wiki: Developers. Thanks!