CHIRP

[Uploaded from CHIRP next-20250321]

Chirp Verrsion:

Connected / Downloaded data from IC-9700 to winders 11:

Connected with IC-9700 :

The!1, !2, !3 entries should be: “TONE (T) / TSQL (R)”

1, 147.195, Fult Co RPT,, Tone = 103.5, Tone Squelch = 103.5

2, 147.090. Def Co RPT (EL),, Tone = 123.0Hz, Tone Squelch = 107.2Hz

3, 146.820, Will Co RPT (FU),, Tone = 107.2Hz, Tone Squelch = 1`07.2Hz

I set radio memory address' 1, 2, 3 to TONE / TSQ then downloaded from
radio to Chirp.
as you will see in the screen shot, the entries are red back ground with
explanation point and address.

On previous downloads to windows it had deleted the TSQL and set them
back to Tone only. That's why none of the others show anything but Tone.
You mentioned that any changes would be made to the Radio as they are
entered which could explain the erasure.  I did not intentionally do it
or know I did it.

Thanks for the fast support.
Stan W8SRD

On 3/25/2025 5:42 PM, Dan Smith wrote:

Dan,

[Chirp log "debug.log 3/28/2025 2:20pm" is attached]
Back again with more results. I reloaded the repeaters from SDcard. and
then connected with Chirp.
All of the entries setup with TONE / TSQL at red and no data shown:

Then I drug the name column over in order to read the names.
No channel from 1 thru 3 show up until later down the list.!@#$%

All of the red lines are TONE / TSQL.
Definitely not right.

FYI, Thanks for your help.
Stan W8SRD

On 3/27/2025 10:28 PM, Stan DeGroff wrote:

Chirp Verrsion:

Connected / Downloaded data from IC-9700 to winders 11:

Connected with IC-9700 :

The!1, !2, !3 entries should be: “TONE (T) / TSQL (R)”

1, 147.195, Fult Co RPT,, Tone = 103.5, Tone Squelch = 103.5

2, 147.090. Def Co RPT (EL),, Tone = 123.0Hz, Tone Squelch = 107.2Hz

3, 146.820, Will Co RPT (FU),, Tone = 107.2Hz, Tone Squelch = 1`07.2Hz

I set radio memory address' 1, 2, 3 to TONE / TSQ then downloaded from
radio to Chirp.
as you will see in the screen shot, the entries are red back ground
with explanation point and address.

On previous downloads to windows it had deleted the TSQL and set them
back to Tone only. That's why none of the others show anything but Tone.
You mentioned that any changes would be made to the Radio as they are
entered which could explain the erasure.  I did not intentionally do
it or know I did it.

Thanks for the fast support.
Stan W8SRD

On 3/25/2025 5:42 PM, Dan Smith wrote:

Also, IC-7300 weird also:
Trying to select Digital on UpperSideBand

On 3/28/2025 2:27 PM, Stan DeGroff wrote:

Dan,

[Chirp log "debug.log 3/28/2025 2:20pm" is attached]
Back again with more results. I reloaded the repeaters from SDcard.
and then connected with Chirp.
All of the entries setup with TONE / TSQL at red and no data shown:

Then I drug the name column over in order to read the names.
No channel from 1 thru 3 show up until later down the list.!@#$%

All of the red lines are TONE / TSQL.
Definitely not right.

FYI, Thanks for your help.
Stan W8SRD

---

On 3/27/2025 10:28 PM, Stan DeGroff wrote:

Chirp Verrsion:

Connected / Downloaded data from IC-9700 to winders 11:

Connected with IC-9700 :

The!1, !2, !3 entries should be: “TONE (T) / TSQL (R)”

1, 147.195, Fult Co RPT,, Tone = 103.5, Tone Squelch = 103.5

2, 147.090. Def Co RPT (EL),, Tone = 123.0Hz, Tone Squelch = 107.2Hz

3, 146.820, Will Co RPT (FU),, Tone = 107.2Hz, Tone Squelch = 1`07.2Hz

I set radio memory address' 1, 2, 3 to TONE / TSQ then downloaded
from radio to Chirp.
as you will see in the screen shot, the entries are red back ground
with explanation point and address.

On previous downloads to windows it had deleted the TSQL and set them
back to Tone only. That's why none of the others show anything but Tone.
You mentioned that any changes would be made to the Radio as they are
entered which could explain the erasure.  I did not intentionally do
it or know I did it.

Thanks for the fast support.
Stan W8SRD

On 3/25/2025 5:42 PM, Dan Smith wrote:

Stan,

I appreciate the attempt at providing a lot of data, but we really need to focus on one thing at a time. The screenshots are not helpful, the debug log is really all I need.

I pulled out my IC9700 and have no problems loading TSQL memories. However, the first one yours is choking on has what appears to be invalid data in the tone mode field (invalid according to Icom's specs). I'm not sure how that has happened, or if the bits that are set actually indicate something important that Icom failed to document. Either way, please try the attached module using LoadingTestModules and update this bug with a new debug log after loading and trying.

Dan,
Log File Attached.
Position 1 : TONE / TSQL Replaced with DTCS,,,023, NN, +, 0.600000, FM

Stan W8SRD
419-345-4865

On 3/28/2025 5:51 PM, Dan Smith wrote:

Dan,
Ok, I think we have solved the issue, or at least know where it comes from.
Here are the different tone mode(s) the radio has.
The purpose of the "TONE(T)/DTCS(R)", "DTCS(T)/TSQL(R)" & "TONE(T)/TSQL(R)"
is to provide different tones for Tx & Rx.  Which I played with and
Chirp rejects. Chirp want's the same tone. Your system currently does
not contain multiple tone for RX & TX.
Number 2 address is a repeater with different tones, which I can work
around. none of the rest require it. So the only solution is up to you.
Add it or not, it's your product.

Here are the Commands (from CV-I manual) :

It looks like If tone "9" is used, the data needs to be handled as two
transfers TONE and TSQL.
This may or may not fit into your product plans. But, at least now we
know whats going on.
Thanks for your help Dan
Stan W8SRD
419-345-4865

On 3/28/2025 10:28 PM, Dan Smith wrote:

Stan, CHIRP does get both the tones, that is not the problem. It's the tone mode that is the problem. The Icom CIV manual shows 0-3 for the tone mode:

Can you link me (do not attach) to what CIV reference file you're looking at? I just re-downloaded the 2023 version from Icom's site and it does not show anything higher than "3" allowed in the tone mode field.

Ah, I see what you're looking at, in the current operating parameters (i.e. "read VFO") command:

Those extra values are not referenced in the description of the "read memory" command, which is what chirp is doing (of course). If the radio can really store that in a memory then that's an error in the manual. I'll work on something for you to test.

Interesting. That's why I said you would have to read all the tone
settings to discover what's going on.
Which would be a pain and still maybe not reach the right conclusion.
The code is set for the strange modes, but not implemented in the call
your using.
Setting the mode is there. But, ICOM did not finish the job. Could be
the manuals are not complete?

An engineer in retirement is a pain !!!  That I am.
Sorry.
Stan W8SRD
419-345-4865

On 3/29/2025 3:57 PM, Dan Smith wrote:

Interesting. That's why I said you would have to read all the tone
settings to discover what's going on.

Again, we're already reading all the information (from the memories) it's just interpreting the values within a memory that are outside of what the document says they can possibly be.

Which would be a pain and still maybe not reach the right conclusion.
The code is set for the strange modes, but not implemented in the call
your using.
Setting the mode is there. But, ICOM did not finish the job. Could be
the manuals are not complete?

The manual is clearly wrong even about the VFO parameters, because the values don't match what the radio actually uses. The manual says Tone(T)/TSQL(R) should be 9, but it's actually 7 (just tested with a real radio, and that matches your debug log).

Please try this updated module. It does not work for setting the weird modes yet as I have not been able to get the radio to accept any of these values, but it does return/decode them now. This module should at least (hopefully) decode your memories as expected.

Cool, that's correct. Unfortunately, it seems like the firmware in the radio is broken. Even if I send exactly the memory the radio has currently stored, it NAKs and refuses to let me set any of the cross modes. Between that and the obviously (doubly) wrong CI-V manual, I'm guessing Icom didn't prioritize finishing the implementation in this radio. Hopefully they can fix it in firmware.

I'm going to commit what I have so that at least it will decode things properly, and we'll hope that Icom can fix it at some point.

Okay, so CS-9700 images the radio like a VHF mobile instead of talking to it over CI-V like an HF radio. Since CHIRP uses the latter, I feel pretty confident that Icom's CI-V implementation is just broken (and obviously incorrectly-documented) in this radio. Hopefully they can fix it in a firmware update, but that's going to put a roadblock in the path for CHIRP supporting writing to these memories for the moment unfortunately.