boatbod
Member
the -x volume parameter where in the command line does it go?
Order of parameters doesn't matter as long as all are specified prior to the log redirection sequence "2> stderr.2"
the -x volume parameter where in the command line does it go?
You likely need different parameters for --gains, --args or -SMy op25.sh file:
./rx.py --nocrypt --args "rtl" --gains 'lna:36' -S 960000 -q 0 -x 2.5 -T trunk.tsv -d 0 -v 1 -2 -V -U 2> stderr.2
This works for my RTL SDR, but I can't get it to work properly with my HackRF. I changed the args from "rtl" to "hackrf", but it still doesn't talk to the device. The OP25 app starts, but it doesn't seem to see the control channel and the tsbks remain at zero. Please note the HackRF works with gqrx. Any ideas why this won't work?
sdrplay is supported by gr-osmocom driver so it should be possible to make the Rsp1a work with op25. Whether or not it works on a rpi4 I cannot say for sure, but if the rsp1a works with other apps on the rpi4 then op25 should as well.Will a Sdr Play Rsp1a work with op25? On a pi4?
sdrplay is supported by gr-osmocom driver so it should be possible to make the Rsp1a work with op25. Whether or not it works on a rpi4 I cannot say for sure, but if the rsp1a works with other apps on the rpi4 then op25 should as well.
You will need different command line parameters, but other than the driver name I don't know what they need to be.
--args "sdrplay"
--gains ??????
Did not try this and I really don't need GQRX.Can you make it work with GQRX?
I was never able to get OP25 to work with my RSP1a on a Pi4. Works great with GQRX however. I am now using SDR usb dongles exclusively with no problems at all on a Pi4.I can see the device on the Raspberry Pi 3 :
######################################################
## Soapy SDR -- the SDR abstraction library ##
######################################################
Found device 0
driver = sdrplay
label = SDRplay Dev0 RSP1
But still op25 is not starting with --args "sdrplay" nor with --args "rtl"
With --args 'soapy=0,driver=sdrplay' the op25 starts but "Waiting for data... " is displayed.
Anyone ?
Did not try this and I really don't need GQRX.
Did not try this and I really don't need GQRX.
Understood, but my point for asking is that GQRX uses the gr-osmocom driver the same as op25, so whatever parameters work with gqrx should also work with op25.I was never able to get OP25 to work with my RSP1a on a Pi4. Works great with GQRX however. I am now using SDR usb dongles exclusively with no problems at all on a Pi4.
Understood, but my point for asking is that GQRX uses the gr-osmocom driver the same as op25, so whatever parameters work with gqrx should also work with op25.
The "waiting for data" message is generated by the http terminal when it hasn't been sent any updates from the trunking code. This might be as simple as the app not being tuned correctly so no TSBKs are being received. Have you looked at the specturum (fft) plot #1 to see if there in any signal being received?Okay, I've tried with --args 'miri=0,driver=sdrplay' and tried 'miri=0' . same thing. the op25 starts, but "Waiting for data... " is displayed.
No information in FFT and it still showing "waiting for data" in FFT page too.The "waiting for data" message is generated by the http terminal when it hasn't been sent any updates from the trunking code. This might be as simple as the app not being tuned correctly so no TSBKs are being received. Have you looked at the specturum (fft) plot #1 to see if there in any signal being received?
Yup. If there's no signal in the fft plot there won't be any tsbks to receive so the "waiting for data" will stay there forever.No information in FFT and it still showing "waiting for data" in FFT page too.
How can i find what to put in values of -N 'IFGR:20,RFGR:8' or -N 'IFGR range:20,RFGR range:8' ?
sys.stderr.write("gain: name: %s range: start %d stop %d step %d\n" % (name, g_range[0].start(), g_range[0].stop(), g_range[0].step()))