Serial protocol does not conform to documentation

[buttim]

Apparently if I modify sonde type and frequency in the app, the command sent via Bluetooth to the ESP32 does not include the / separator between commands as documented in the MySondyGoAPI.pdf document

Expected:

Code: Select all

o{f=401.568/tipo=4}o

Actually received:

Code: Select all

o{f=401.568tipo=4}o

[IZ4PNN]

mmmm.... very strange...
In this case only the frequency would have to change and the radiosonde change would not work.
I will check.
What do you use to read the bluetooth commands from the App?

[buttim]

I simply programmed an ESP32 to offer a Bluetooth connection under the name MySondyGo-XXXXXXXXXXXX. It dumps on (USB serial what comes from the BT connection. I must say I several times changed both frequency and radiosonde type on my radio and cant remember of any problem

[IZ4PNN]

Could it be your way of looking at communication that ignores the "/" ?

[buttim]

Hardly. I simply dump every character that I get from the UART.
In a different case I do see the /s (the message body is: rs41.rxbw=1/m20.rxbw=4/m10.rxbw=0/pilot.rxbw=0/dfm.rxbw=5/freqofs=6)

[IZ4PNN]

Hi Buttim,
I checked in the code.
In fact this can happen, I didn't remember using this solution

It is a solution used for the App, it only works for f= followed by tipo=, it is not mentioned in the API because the / can be used without problems.

Then:
o{f=401.568/tipo=4}o
It's equal to:
o{f=401.568tipo=4}o

Sorry, my memory is starting to falter ..

[buttim]

I really think you should mention it in the API doc (or maybe it would be even better to silently correct the app when the next version is ready)