Tune Mode: Two Tone - not saving

Flexed

Sup Hams!!

I really enjoy using the Two Tone mode. Since I'm one of the first in my crew using a FlexRadio, they can instantly tell whether I'm on the NET or not—at least until the rest of them catch up and get one too.

Here's where I could use a hand: I’ve set Tune Mode to Two Tone under Radio Setup > TX, and it works as expected. I save my profile, but when I power up the radio next time and reload the profile, the Two Tone setting isn’t retained.

Am I missing a step, or is this something the developers might have overlooked in the profile saving process?

KD0RC

Two tone mode is designed to let you look at your IMD. I don't think it was meant to be used to tune a tuner. The single tone tune takes a LOT less bandwidth. My guess is that this is working as intended (Flex can jump in and let me know how good my guess is...)

Mike-VA3MW

Two Tone is designed for IMD testing. It is not something that you would every day.

Here is an example where you can see the transmitted 2 tone signal and the IMD it produces. In the lower part you see the actual signal being transmitted.

Flexed

Thanks, that’s a valid description of the feature. However, it doesn’t directly address my question. To put it simply: does it allow saving or not?

Mike-VA3MW

The discussion was to not keep it as a persistance setting. If that is important to you, you may wish to add it to the new ideas area of the community and it doesn't hurt to explain why it is important to you. That way we can pass it on to engineering.

Flexed

Mike, I now fully comprehend that it’s not a persistence value. Initially, I believed I was making a mistake. Thanks again.

Mike VE3CKO

On this subject, is the Two-Tone feature available in the API? When the tune mode is changed in the Radio Setup I can get the state of the tune_mode and display it accordingly, but sending from node-red I either am using the wrong command or it's unavailable.

Using wireshark I see:

"transmit tune_mode=single_tone"

"transmit tune_mode=two_tone"

I've tried these and variants of these commands sent in my node-red flow have no effect.

Eric-KE5DTO

It looks like you already figured out the commands. What kind of application are you using? Is this a non-GUI client that is also not bound to a GUI client? This is likely why you aren't seeing behavior that you expect as the single/two tone is specific per client. Without the context of a GUI client, the command is somewhat ambiguous as to which client it might pertain. This is similar to many other transmit commands such as setting the RF Power or Tune Power.

I'm not familiar enough with how the Node Red flow works, but if there's an option to bind to your Maestro or SmartSDR instance, that might solve the issue for you.

KD0RC

@Eric-KE5DTO

Hi Eric, I am getting similar results as Mike, VE3CKO. I get a malformed command, even with a successful bind:

In a Windows C++ program, I send these commands:

sendResult = send(sock, "CD43 | client bind client_id=E08F5BB7-F75E-4940-8352-624F0BC84106\n", 67, 0);



sendResult = send(sock, "CD304 | transmit tune_mode=single_tone\n", 40, 0);

sendResult = send(sock, "CD305 | transmit tune_mode=two_tone\n", 37, 0);

And get these responses:

R43|0|0x43145D73|

R304|50000016||

R305|50000016||

Command 43 is showing the correct client handle in the bind response. Commands 304 and 305 are showing a malformed command response.

If I click the Two Tone Tune Mode in Settings in SmartSDR, I get the expected result:

S43145D73|transmit tune=0 tune_mode=two_tone tx_rf_power_changes_allowed=1 max_power_level=100

Can you shed any light on this? Since it works in SmartSDR, I am sure that Mike and I are just doing something incorrectly.

KD0RC

OK, I figured it out…

sendResult = send(sock, "CD304 | transmit s tune_mode=single_tone\n", 42, 0);

sendResult = send(sock, "CD305 | transmit s tune_mode=two_tone\n", 39, 0);

Mike, VE3CKO, you need to use the s or set to change the tune mode. I should have noticed that before! Anyway, give that a try. It seems to work whether or not you do a bind to the GUI client.

Eric, I guess my presumption at the end of my last post is correct - Mike and I were not formatting the commands correctly. :- )

Mike VE3CKO

Yes Les that did the trick, thanks, I thought I had tried adding the s but apparently not.