Firmware observations and suggestions

[Psynosaur]

Hi

Please find my observations regarding the operation via MQTT.

• When sending /tx/mute a value of 1 it quickly switches on PTT, this creates spurs on the spectrum.

• DATV-Red sends the broker this message twice to mitigate a reboot state, which is pass and PTT ON at 1MS.

• Could we please have the ability to modify the start up parameters of our plutos that would persist namely:

  • Callsign
  • PTT
  • IP addresses (TSInput, Longmynd, broker, etc.)
  • Gain
  • Modes
  • Rx
    • pass, webfft, etc
    • gain and frequency for spectrum plotter
  • Tx
    • dvbs2-ts, pass, etc...

• Rx spectrum

  • Please decouple symbol rates from Tx modulator

• longmynd

  • Allow n amount of longmynd clients to connect to broker
  • So that we may used as many tuners on a particular broker
  • Allow modification of all longmynd parameters via MQTT topic
  • Numerically controlled oscillator
  • Changes to a value that isn't the set value after a symbol rate change
  • mitigated by sending the set value 250ms after the SR change.

These are all the things currently that come to mind, please reach out if anything is unclear.

Thank you Ohan ZS1SCI

[Psynosaur]

Hi

When using the paho mqtt client the spectrum is strangely shaped and the DC line is visible in the middle.

Replace with https://unpkg.com/mqtt/dist/mqtt.min.js and this blob of JS.

pluto_url and callsign are injected from node-red.

Canvas labels frequencies and spans correctly without strange spurs, and updates when the topic changes

Update, this is a theory, perhaps it's because paho-mqtt already established a connection to the pluto broker locally on the device, and therefore the second client connection via paho-mqtt externally messes with the FFT?

kind regards

[Psynosaur]

please see my remarks om wiki regarding fw 0.3-17 and upwards.

Frequency is artificially capped at 2147.5MHz at topic cmd/pluto/ZS1SCI/rx/webfft/frequency

Frequency can be set to higher than that with topic cmd/pluto/ZS1SCI/rx/frequency but it seems you new cmd/pluto/ZS1SCI/rx/webfft/frequency topic has preference over it since it doesn't change frequency anymore on cmd/pluto/ZS1SCI/rx/frequency upto 6GHz like before

Web FFT(on pluto)

• Frequency labelling doesn't work, so its not getting info from broker.
• has no effect on onboard webfft on pluto network address.
  • cmd/pluto/ZS1SCI/rx/webfft/average
  • cmd/pluto/ZS1SCI/rx/webfft/rangemin
  • cmd/pluto/ZS1SCI/rx/webfft/rangemax

This is why DATV-Red maintains its own spectrum file with a different MQTT client.