[chirp_users] ctcss tones written wrong? (ft-817nd)
Hi,
I've just gotten a FT-817nd and started playing around with it using Chirp. Everything is looking great except one problem. It looks like if I create a memory entry with a CTCSS tone setting and it is written to a previously empty channel, when looking at that channel on the radio I will see a random 16 bit number (ie, 26654) instead of a formatted tone value (like "77.0"). (they don't appear to match; three channels all set to a 100.0hz tone will show three different random-looking numbers on the radio.) It does not transmit a correct CTCSS tone. There don't appear to be any other data errors.
If I overwrite the value using the radio, it then works fine. If I clone the radio to Chirp and then write it back immediately, the values are all still good, but I don't know if this is because it already contains valid contents or because i'm now writing valid contents.
Fwiw I am using debian linux and the daily build package from the apt repo, but the same thing appears to happen with the 0.2.2 tarball from the site. Further info: it is a recent-ish US model that's been MARS modded (no special channels) and thus I am using the "FT-817ND (Intl versions)" instead of the US version hardware type.
Anyway, I'm happy to try any suggested experiments or provide any further info if it would help. I also have a paid copy of FTBasicMMO which does write tones correctly, for comparison, but i'd much prefer to keep using chirp.
thanks for a fine piece of software! eric
Hi Thanks for the report, I'll have a look at this today. I think you already provided enough info to easily reproduce it.
I filed issue #163 for this, should you have any further info please add it directly there http://chirp.danplanet.com/issues/163
73 de IZ3GME Marco
On 06/05/2012 00:24, ag6eb@limpoc.com wrote:
Hi,
I've just gotten a FT-817nd and started playing around with it using Chirp. Everything is looking great except one problem. It looks like if I create a memory entry with a CTCSS tone setting and it is written to a previously empty channel, when looking at that channel on the radio I will see a random 16 bit number (ie, 26654) instead of a formatted tone value (like "77.0"). (they don't appear to match; three channels all set to a 100.0hz tone will show three different random-looking numbers on the radio.) It does not transmit a correct CTCSS tone. There don't appear to be any other data errors.
If I overwrite the value using the radio, it then works fine. If I clone the radio to Chirp and then write it back immediately, the values are all still good, but I don't know if this is because it already contains valid contents or because i'm now writing valid contents.
Fwiw I am using debian linux and the daily build package from the apt repo, but the same thing appears to happen with the 0.2.2 tarball from the site. Further info: it is a recent-ish US model that's been MARS modded (no special channels) and thus I am using the "FT-817ND (Intl versions)" instead of the US version hardware type.
Anyway, I'm happy to try any suggested experiments or provide any further info if it would help. I also have a paid copy of FTBasicMMO which does write tones correctly, for comparison, but i'd much prefer to keep using chirp.
thanks for a fine piece of software! eric _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
I uploaded a patch that will be included in next days build. Please download it, test and report results. I expect it to set correctly the tone frequency now, it does in my 817 at least ;)
To correct with chirp any "dirty" memory generated from previous version the easiest way is to literally import the image into itself. Open the image, File->Import, select the image, then click "all" to select all memories and then import.
tnx agian for your report
73 de IZ3GME Marco
On 06/05/2012 00:24, ag6eb@limpoc.com wrote:
Hi,
I've just gotten a FT-817nd and started playing around with it using Chirp. Everything is looking great except one problem. It looks like if I create a memory entry with a CTCSS tone setting and it is written to a previously empty channel, when looking at that channel on the radio I will see a random 16 bit number (ie, 26654) instead of a formatted tone value (like "77.0"). (they don't appear to match; three channels all set to a 100.0hz tone will show three different random-looking numbers on the radio.) It does not transmit a correct CTCSS tone. There don't appear to be any other data errors.
If I overwrite the value using the radio, it then works fine. If I clone the radio to Chirp and then write it back immediately, the values are all still good, but I don't know if this is because it already contains valid contents or because i'm now writing valid contents.
Fwiw I am using debian linux and the daily build package from the apt repo, but the same thing appears to happen with the 0.2.2 tarball from the site. Further info: it is a recent-ish US model that's been MARS modded (no special channels) and thus I am using the "FT-817ND (Intl versions)" instead of the US version hardware type.
Anyway, I'm happy to try any suggested experiments or provide any further info if it would help. I also have a paid copy of FTBasicMMO which does write tones correctly, for comparison, but i'd much prefer to keep using chirp.
thanks for a fine piece of software! eric _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
On Sun, May 06, 2012 at 12:35:16PM +0200, Marco IZ3GME wrote:
I uploaded a patch that will be included in next days build. Please download it, test and report results. I expect it to set correctly the tone frequency now, it does in my 817 at least ;)
To correct with chirp any "dirty" memory generated from previous version the easiest way is to literally import the image into itself. Open the image, File->Import, select the image, then click "all" to select all memories and then import.
tnx agian for your report
73 de IZ3GME Marco
I will give it a try once it appears in the daily. (don't see changes in the repo yet)
On a related subject, looking at the memory structure for the 817 it looks possibly like the state of the attenuator and "IPO" (preamp on/off) is stored per-channel? Having the ability to specify, load, and save these in the config and/or CSV files would be pretty useful. For example, I live in a noisy area and want to have IPO on (preamp off) for most lower HF freqs, but not higher ones.
eric
On 06/05/2012 00:24, ag6eb@limpoc.com wrote:
Hi,
I've just gotten a FT-817nd and started playing around with it using Chirp. Everything is looking great except one problem. It looks like if I create a memory entry with a CTCSS tone setting and it is written to a previously empty channel, when looking at that channel on the radio I will see a random 16 bit number (ie, 26654) instead of a formatted tone value (like "77.0"). (they don't appear to match; three channels all set to a 100.0hz tone will show three different random-looking numbers on the radio.) It does not transmit a correct CTCSS tone. There don't appear to be any other data errors.
If I overwrite the value using the radio, it then works fine. If I clone the radio to Chirp and then write it back immediately, the values are all still good, but I don't know if this is because it already contains valid contents or because i'm now writing valid contents.
Fwiw I am using debian linux and the daily build package from the apt repo, but the same thing appears to happen with the 0.2.2 tarball from the site. Further info: it is a recent-ish US model that's been MARS modded (no special channels) and thus I am using the "FT-817ND (Intl versions)" instead of the US version hardware type.
Anyway, I'm happy to try any suggested experiments or provide any further info if it would help. I also have a paid copy of FTBasicMMO which does write tones correctly, for comparison, but i'd much prefer to keep using chirp.
thanks for a fine piece of software! eric _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Hi Eric
I will give it a try once it appears in the daily. (don't see changes in the repo yet)
Usually it takes a day or two for Dan to push changes to repository, a mail will then be send by the build system to this list.
On a related subject, looking at the memory structure for the 817 it looks possibly like the state of the attenuator and "IPO" (preamp on/off) is stored per-channel? Having the ability to specify, load, and save these in the config and/or CSV files would be pretty useful. For example, I live in a noisy area and want to have IPO on (preamp off) for most lower HF freqs, but not higher ones.
You are right, IPO and ATT are stored in memory, I must say I didn't test that much but I know where they are. I didn't support them at first as there are no controls for them in chirp (yet). I have other things in my todo list but if you file a feature issue i will (probably) work on this as soon as i'll have time.
73 de IZ3GME Marco
On Sun, May 06, 2012 at 12:35:16PM +0200, Marco IZ3GME wrote:
I uploaded a patch that will be included in next days build. Please download it, test and report results. I expect it to set correctly the tone frequency now, it does in my 817 at least ;)
To correct with chirp any "dirty" memory generated from previous version the easiest way is to literally import the image into itself. Open the image, File->Import, select the image, then click "all" to select all memories and then import.
tnx agian for your report
73 de IZ3GME Marco
Marco, As far as I can tell, the problem I reported is not happening any more with the patch. It's not impossible that something else is preventing it from surfacing but what triggered it before no longer does: uploading to a memory location in the radio from a newly entered location in chirp.
On 06/05/2012 00:24, ag6eb@limpoc.com wrote:
Hi,
I've just gotten a FT-817nd and started playing around with it using Chirp. Everything is looking great except one problem. It looks like if I create a memory entry with a CTCSS tone setting and it is written to a previously empty channel, when looking at that channel on the radio I will see a random 16 bit number (ie, 26654) instead of a formatted tone value (like "77.0"). (they don't appear to match; three channels all set to a 100.0hz tone will show three different random-looking numbers on the radio.) It does not transmit a correct CTCSS tone. There don't appear to be any other data errors.
If I overwrite the value using the radio, it then works fine. If I clone the radio to Chirp and then write it back immediately, the values are all still good, but I don't know if this is because it already contains valid contents or because i'm now writing valid contents.
Fwiw I am using debian linux and the daily build package from the apt repo, but the same thing appears to happen with the 0.2.2 tarball from the site. Further info: it is a recent-ish US model that's been MARS modded (no special channels) and thus I am using the "FT-817ND (Intl versions)" instead of the US version hardware type.
Anyway, I'm happy to try any suggested experiments or provide any further info if it would help. I also have a paid copy of FTBasicMMO which does write tones correctly, for comparison, but i'd much prefer to keep using chirp.
thanks for a fine piece of software! eric _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Marco, As far as I can tell, the problem I reported is not happening any more with the patch. It's not impossible that something else is preventing it from surfacing but what triggered it before no longer does: uploading to a memory location in the radio from a newly entered location in chirp.
Tnx, I'll close the bug issue.
73 de IZ3GME Marco
participants (3)
-
ag6eb＠limpoc.com -
Marco Filippi IZ3GME -
Marco IZ3GME