CHIRP

Thomas,

I find that once I choose a selection, I must click off onto another cell to make the selection "stick". To verify that the selection was properly made, click the [Go] button near the top left of the memory editor spreadsheet. If the value reverts back, it wasn't properly selected. If it stays put, it was.

Jim KC9HI

Its not a problem setting the settings in the gui. I have it set on multiple channeles. I save the image. When i try to open the file all CROSS goes to TSQL.

When i try to read back from radio with Cross set (and working) it comes in as TSQL as well. But on radio both R-CTCSS and T-CTCSS is enabled with the right tone.

So i guess it could be a image/memory parsing problem??

Its 0.3.1 and daily i have testet against. Not 0.3.0

Just did a new test.. Seems setting to TSQL and tone sets both R and T-CTCSS on Radio.... Hmm.. I could have been mistaken. But the reason for my report was that this did not work a few days ago.

Review these documents

http://chirp.danplanet.com/projects/chirp/wiki/MemoryEditorColumns
http://kc9hi.dyndns.org/uv5r/programming/CHIRP%20Guide.pdf

Look in the View menu and see if you have "Smart Tones" enabled? If you do, and you try to set a tone in the Tone column and then another tone in the ToneSql column without first setting Tone Mode to Cross, then Tone Mode will auto select Tone and then select TSQL. I also suggest that in the View menu you enable "Hide Unused Fields". It helps to show which columns are actually being used when changing the Tone Mode and Cross Mode settings.

If you still think there is a problem... provide the .img file uploaded to the radio and the .img file downloaded from the radio. If I can duplicate the issue here I would be happy to look into it.

Jim

This is still a problem. I am on an iMac running Mojave and the latest unified daily build. I have View->Hide Unused Fields and View->Smart Tone Modes both turned off. I have a BaoFeng UV-82HP, but I don't think that matters. If I try to enter a memory with cross as the Tone Mode, as long as the Tone and ToneSql values are different it seems to take it and things are OK. As soon as I try to enter a repeater with cross where the Tone and ToneSQL are the same value, things go bad. It shows that it has accepted it, but as soon as you do anything else it changes the memory to TSQL Tone mode.
You can easily repeat this by going to any empty memory in CHIRP, enter a frequency, change Tone Mode to cross, and let it default to 88.5 for both Tone and ToneSQL, and let it default everything else and then click somewhere else so the memory is saved. It all looks good at this point. Now simply toggle the Show Empty memory slots button. It changes the memory location you just entered from cross to TSQL. Any action seems to make the change, even saving to a file, where the saved data is Tone Mode TSQL and not the cross that you entered.

Another example: take any memory slot that has a cross repeater entry that is being honored where the Tone and ToneSql values are different. Change either Tone or ToneSql to be the same as the other. Click somewhere else so your memory slot is saved. Now toggle Show Empty and it will have changed your memory slot from cross to TSQL.

I believe this is a misunderstanding of when to use Cross vs TSQL. The definition of TSQL is that both TX and RX tones are the same and the tone to be used is in the ToneSql column. Setting a channel to Tone Mode: Cross and Cross Mode: Tone->Tone and both tones the same is the very definition of TSQL. So when CHIRP reads a radio image (loads an img file) with a channel in this configuration, it shows the channel as TSQL. Cross is only needed when you want the tones to be different from one another.

So I don't think this is an issue.

Brad Schuler wrote:

I believe this is a misunderstanding of when to use Cross vs TSQL. The definition of TSQL is that both TX and RX tones are the same and the tone to be used is in the ToneSql column. Setting a channel to Tone Mode: Cross and Cross Mode: Tone->Tone and both tones the same is the very definition of TSQL. So when CHIRP reads a radio image (loads an img file) with a channel in this configuration, it shows the channel as TSQL. Cross is only needed when you want the tones to be different from one another.

So I don't think this is an issue.

Exactly. If CHIRP didn't switch it to TSQL when both tones are the same, it would be a bug.

Jim KC9HI