[chirp_devel] Question about FT-1D v FT2D
I’m back from vacation and trying the FT2D again. I’m stuck on the memory label field. When read from the FT2D using the FT-1D format, the label comes out gibberish. Most other memory fields jibe quite nicely. I’ve tried reading the source, but got lost in pythonese (translates and rshift and object details I just don’t know yet.)
SO…. when I look at the raw memory image coming from the FT2D, the memory labels (and the memory bank names) are in straight ASCII. (I too have not tried anything in Japanese format.) But when I get that image into chirp using FT-1D template, the labels come out as mostly-unprintable characters. It looks to me as if translation or decrypting of some sort is happening.
Here’s an example [from my memory 0] memory image shows ‘APRS US‘, with the standard 0xFF packing 00002d40 00 13 14 43 90 c0 00 00 41 50 52 53 20 55 53 ff |...C....APRS US.| 00002d50 ff ff ff ff ff ff ff ff 00 06 00 0c 00 0d 00 18 |................|
chirp shows ‘:’ BUT, the chirp browser shows the correct ASCII, presumably in python's Unicode string. 0041 0050 0052 0053 0020 0055 0053 x x x x x x x x x
Bank names are also gibberish, although the chirp browser seems to show them to be stored as ASCII bytes rather than python strings, although with the same 0xFF packing.
What happened between chirp browser and chirp? It’d seem to be straightforward to get the ASCII printed! Help please.
Declan Rieb, WD5EQY
Look at how the ftm3200d driver extends the FT1D one and uses ascii for encoding instead of the custom format the ft1d does. You can probably do the same thing.
On Sat, Jun 24, 2017 at 5:27 PM NNN Wx via chirp_devel < chirp_devel@intrepid.danplanet.com> wrote:
I’m back from vacation and trying the FT2D again. I’m stuck on the memory label field. When read from the FT2D using the FT-1D format, the label comes out gibberish. Most other memory fields jibe quite nicely. I’ve tried reading the source, but got lost in pythonese (translates and rshift and object details I just don’t know yet.)
SO…. when I look at the raw memory image coming from the FT2D, the memory labels (and the memory bank names) are in straight ASCII. (I too have not tried anything in Japanese format.) But when I get that image into chirp using FT-1D template, the labels come out as mostly-unprintable characters. It looks to me as if translation or decrypting of some sort is happening.
Here’s an example [from my memory 0] memory image shows ‘APRS US‘, with the standard 0xFF packing 00002d40 00 13 14 43 90 c0 00 00 41 50 52 53 20 55 53 ff |...C....APRS US.| 00002d50 ff ff ff ff ff ff ff ff 00 06 00 0c 00 0d 00 18 |................|
chirp shows ‘:’ BUT, the chirp browser shows the correct ASCII, presumably in python's Unicode string. 0041 0050 0052 0053 0020 0055 0053 x x x x x x x x x
Bank names are also gibberish, although the chirp browser seems to show them to be stored as ASCII bytes rather than python strings, although with the same 0xFF packing.
*What happened between chirp browser and chirp? It’d seem to be straightforward to get the ASCII printed! Help please*.
Declan Rieb, WD5EQY
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
I used the label-encoding code straight from the ftm3200d. It worked correctly right off the bat. (so far, I’ve commented away the rest of the 3200d code.) Thanks, Wade.
Now for the memory banks: those data are at a different offset than in the FT-1D.
BTW, I’ve also got development working directly in Mac OS X. I plan to write up the few things I needed to do so it can be included in the OS X-centric instructions on the development site (unless others have already done so or if it’s intuitively obvious to the rest of the world.)
On Jun 24, 2017, at 19:45, Wade Simmons wade@wades.im wrote:
Look at how the ftm3200d driver extends the FT1D one and uses ascii for encoding instead of the custom format the ft1d does. You can probably do the same thing.
Chirp/Python development on Mac OS (Sierra) is not intuitive to me so a quick start guide, tips and tricks, would be much appreciated. It has been a while but I recall having issues with libxml2 and pygtk. I did not get very far. Thanks!
Keith
On Jun 24, 2017, at 9:11 PM, NNN Wx via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
I used the label-encoding code straight from the ftm3200d. It worked correctly right off the bat. (so far, I’ve commented away the rest of the 3200d code.) Thanks, Wade.
Now for the memory banks: those data are at a different offset than in the FT-1D.
BTW, I’ve also got development working directly in Mac OS X. I plan to write up the few things I needed to do so it can be included in the OS X-centric instructions on the development site (unless others have already done so or if it’s intuitively obvious to the rest of the world.)
On Jun 24, 2017, at 19:45, Wade Simmons <wade@wades.im mailto:wade@wades.im> wrote:
Look at how the ftm3200d driver extends the FT1D one and uses ascii for encoding instead of the custom format the ft1d does. You can probably do the same thing.
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
Hello Declan,
Thanks for working on the FT2 support and when you get closer, I can help beta test your code. Curious though, will your code support both the cable communication AND microSD-card methods?
--David KI6ZHD
On 06/24/2017 02:27 PM, NNN Wx via chirp_devel wrote:
I’m back from vacation and trying the FT2D again. I’m stuck on the memory label field. When read from the FT2D using the FT-1D format, the label comes out gibberish. Most other memory fields jibe quite nicely. I’ve tried reading the source, but got lost in pythonese (translates and rshift and object details I just don’t know yet.)
SO…. when I look at the raw memory image coming from the FT2D, the memory labels (and the memory bank names) are in straight ASCII. (I too have not tried anything in Japanese format.) But when I get that image into chirp using FT-1D template, the labels come out as mostly-unprintable characters. It looks to me as if translation or decrypting of some sort is happening.
Here’s an example [from my memory 0] memory image shows ‘APRS US‘, with the standard 0xFF packing 00002d40 00 13 14 43 90 c0 00 00 41 50 52 53 20 55 53 ff |...C....APRS US.| 00002d50 ff ff ff ff ff ff ff ff 00 06 00 0c 00 0d 00 18 |................|
chirp shows ‘:’ BUT, the chirp browser shows the correct ASCII, presumably in python's Unicode string. 0041 0050 0052 0053 0020 0055 0053 x x x x x x x x x
Bank names are also gibberish, although the chirp browser seems to show them to be stored as ASCII bytes rather than python strings, although with the same 0xFF packing.
*What happened between chirp browser and chirp? It’d seem to be straightforward to get the ASCII printed! Help please*.
Declan Rieb, WD5EQY
participants (4)
-
David Ranch -
Keith Klamm -
NNN Wx -
Wade Simmons