Issue with pluto driver / Meteor qpsk demodulator

[raidfire99]

Hi the Meteor 2 qpsk demodulator is not working with the pluto driver.

Normally when you enable the demodulator it mutes the souud this doesn't happen with the pluto front end, tcp service shows as started but in reality the port is not opened and the imaging software cant see anything to connect to.

It looks like the iq stream is hardcoded to the audio bus and not routable internally to the demodulator.

tested on several versions of sdr# and qpsk demod plugin, fresh install of win10 sdr# and qpsk plugin, all exhibit same behaviour, demod is not routed, swap the frontend to rtl-sdr, airspy, iq file, demod runs no prob on all instances.

as a side note, soem access to the 3 basic filter parameters would be nice: enable/disable, auto on/off, load of iio ossiloscope filter file, currently im loading both sdrsharp and iio-oscilloscope, with oscilloscope open i am able to communicate with the back end and configure the filters while sdr# is running but the moment you stop and start sdr# you need to reload the filter file from oscilloscope as the pluto disconect / reconnect in sdr# forces the default boot config to be reloaded which is filter off, if this was part of the saved config of the front end it would be a big bonus to using the pluto as a standard sdr, also a switch to disable the auto tx on 2.4ghz would be great even if it just max attenuates.

[Manawyrm]

Hi!

Yes, unfortunately there's nothing I can do about the plugin thing:
#16 (comment)

I've noted the requested features (especially the auto TX disable) and will see what I can do.

[raidfire99]

Thanks for the feedback, i saw the post re 3rd party front ends, for anyone interested in meteor reception, you can use the baseband recorder to capture an iq stream with the pluto driver and replay the file as a wav source as a workaround for the demodulator issue.

as to features - i can always assist with beta testing, i have time available.

Regards,
Jay