FRStack does not present CWSPEED in StreamDeck+

dale0131

FRStack 3.7.38.75

FRStack Stream Deck V1_3

Trying to control CWSPEED from the StreamDeck+
I can see CWXSPEED but not CWSPEED

FRStack3 shows it in the rest call help document

What gives?

Another question, is it possible to toggle iambic mode from the streamdeck?

Erik Carling EI4KF

Ah ha, thanks Dale and Len for that explanation. I'd not given it much thought before.

With the buttons, the level is controllable by the ClickParam function - press for +1 or -1 for example. But for knobs I can only suggest that you email Mark W3II.

Erik Carling EI4KF

My probably mistaken belief is that CWSPEED is the same as CWXSPEED. I have never programmed CWXSPEED but have always used CWSPEED.

Anyway it works.

Yes, Iambic mode can be controlled from StreamDeck.

With a 2nd button for Iambic B. It may be possible to toggle but not tried it.

dale0131

Interesting, …

I am trying to probram one of the knobs, not a button, but i did learn something.

BTW, CWSPEED and CWXSPEED are different. The former is the speed of the iambic paddles, the latter the speed at which phrases stored in the CWX menu items.

But, I do see CWSPEED in the buttons, but not the level items.

This would seem to be an oversight.

Thanks!

KD0RC

CWSPEED and CWXSPEED are different, but can be synchronized:

If you want to keep them separate, turn off Sync.

dale0131

Thanks guys, for the assistance.

Of course, the place the REST API belongs is in the radio itself itself (and tuner, and amplifier, and antenna genius).

Are you guys at Flex listening?

dale0131

Refer to the image provided by Erik Carling EI4KF

Leave the Title blank, use "Speed" for the prefix and "+" or "-" for the suffix. You get a button with "Speed" in the top line, the actual speed in the middle and "+" or "-" on the bottom.

KD0RC

Hi Dale, the Flex API makes every function of the radio available to anyone who can write a program. This API is text-based and exists in the radio itself. They even have a library (FlexLib) available for C# and the Windows .net environment.

I assume that the REST API uses the Flex API under the covers to actually control the radio.

The Node Red guys have done an enormous amount of work behind the scenes to make Node Red a viable way to access the radio. Ultimately, it uses the Flex API.

dale0131

I am aware of the Flex API and have downloaded it as well as the documentation. I can program better than most.

REST API is a web based API and is not only a bit easier to program, but third party devices such as the Elgato Streamdecks have a REST interface with which to access RESTful devices, included power control devices (Most IP controllable devices, including a lot of Alexa compatible stuff). It has become the standard for IP control of external devices.

Further, Both FRStack and Stackmaster provide a third party REST interface to be used with the Elgato devices. They did a fine job, but theirs is somewhat streamdeck centric.

IMO, the natural place for software which controls a device is within the device. As such, an entire movement has sprung up to make that possible, the (in)famous "Internet of Things", which is basically an Arduino type device with a WiFi interface built in which is used in many devices, including light bulbs.

I suspect going from the API existent in the Flex to a REST API is child's play and I rather suspect Flex has it on their "to do list".