Thanks for the feedback. Hmm that is very strange that it needed to boot on the Pi 4 first…
It might be something to do with Raspberry Pi Imager overwriting stuff. We usually recommend people use Balena Etcher or or Win32DiskImager, because the Rpi Imager tends to overwrite certain things on the image.
I cannot view this option in the wideband scanner settings, only in normal scanner and in the decimators for single frequencies.
My apologies if it is there, I can be very absent-minded sometimes.
Thank you.
Thanks, will look into the squelching issue and fix those minor bugs.
Regarding audio, the audio can be muted by pressing on the speak icon in the Tune Frequency window. To get to that window just press on the frequency on the top left.
Is there any updated Wiki documentation on the V2 software which I can look at before asking questions?
One thing I have noticed on the updated Android app is that there is no “X” button on the screen to clear off the direction bearing lines when the screen gets cluttered.
Hello again,
In wideband scanner, I see a button labeled “start” and a check box labeled “enable”.
I am not sure, it seems that both are the same, arent they? I suppose there should be only one of them.
Regards,
German EA4GJA
If I understood it properly, scanner first watches for a busy channel. When it is found, it performs calibration at that frequency and then gets the direction where it arrives from.
It is OK, but it is too slow to catch very short transmissions. I would suggest: first calibrating, then listening and in the end DF.
If the dwell time is not very short, there will be fewer calibrations. It is better to spend time listening and DFing than calibrating 
Thank you again for your time and work.
Not yet. Once it comes out of beta in the next few weeks we’ll be updating the documentation.
The new Android app has the close button in the pull up menu.
The enable button enables the wideband scan mode. In wideband mode it will take the receiver out of coherent mode and try to stitch the 5 channels together, meaning it can simultaneously scan a wider bandwidth faster.
If it’s off, if the BW is less than 2.4 MHz, it will stay in coherent mode, scanning the live bandwidth. Otherwise it will continuously scan with one channel until it finds a signal, then go back into coherent mode.
Ah yes, very interesting feature. I would just say that I did not understand it at first. Perhaps it is my fault, I am very absent minded.
Would there be the same feature for the normal scanner (not wideband)?
If I understood OK, when you do not know the frequencies in advance, you use “wideband scanner”, with enable or without it to control if it goes out of coherent mode to watch more spectrum. With enable watches a wider band at once, without enable watches a narrower band but it is already in coherent mode, it is better to catch very short transmissions.
On the other hand, if you know the interesting frequencies in advance, you use “scanner” (normal scanner, not wideband one). You set the frequencies in the list. It would be very interesting to have the “enable” button here as well, with the same behaviour.
If you are interested in one single frequency, you do not use neither “scanner” nor “wideband scanner”, you use one decimator.
Am I right so far?
I think we have caught a bug in the squelch feature of the decimator. If I can use “scanner” with one single frequency in the list, this can be a workaround for now, but the frequency I am interested in transmits only very short bursts, about one second long, so I would need to be able to set “enable” checkbox, to have the radio on coherent mode all the time. If it cannot be done with “scanner”, I could use “wideband scanner” and it should work most times.
Perhaps “enable” could be renamed to a more informative text…
Thank you again.
@krakenrf_carl what is the status of the new digital decoder features described on the Github page? Is it just simple decoding for now? Or is there a software mechanism for discriminating between signals based their on digital metadata (for example RFDFing two P25 transmitters on the same frequency that have different NACs, site IDs etc).
Yes currently there is an unverified feature on the Github that should allow a P25 signal to be split up by ID. If you want to try it, just git pull in the latest code and rerun ./install.sh and it should pick up and install the new code.
Basically set a digital demodulator in the decimator for P254 box on the left, and then open the decoders and map. YOu should be able to click on the ID in the box on the map, and it should show the DoA for only that particular ID.
Tested only in simulation so far, not on live signals
Exceptionally neat! Can the new V2 features be tested out with the Pro Cloud Mapper yet? Or is that not until after V2 moves out of beta?