Keep in mind sending TCP commands to the radio during TX WILL create a ¡°pop¡± in the audio. This is a known issue and Flex is aware. No known info as to when/if this will get addressed.?
Try to limit commands to the radio, especially during TX.?
Just a friendly reminder.?
Dave wo2x
Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Jan 2, 2022, at 7:12 PM, Alan Blind, WA9WUD <a.alan.blind@...> wrote:
?Stephen
On the subject of the next Flex Request Node.....I have a request:
Attached is a paper by ?John Linfor,d G3WGV, "Flex Application Programing Interface".
Below is an excerpt, that John says it is best to limit the rate of commands to 25ms to 50ms.
Could you build a command rate limiter into your Flex Request Configuration Node?
Alan. "WA9WUD"
===========================
Notes on sending commands to the API
Generally you can send commands to the radio as you please. Each command has a command number and the radio will execute them in the order they were sent, send back a receipt message with the same number and then progress to the next command. It is not necessary to wait for one command to be completed with response before sending the next command.
That said, it is not a good idea to flood the API with commands. A good example is fast VFO tuning using a spinner knob?with fairly small frequency steps. It¡¯s not hard to send hundreds or even?thousands of updates a second and that is a bad idea!
A realistic update rate for the radio is once every 25ms to 50ms. The radio seems comfortable with that. If you go faster than that you will likely start hearing odd audio clicks and other artefacts. The radio takes some time (typically around 50ms) to respond to commands, so nothing is gained by sending updates to the radio more often.
Dave wo2x