All graphs after running v1.41 for about 15 minutes:
After watching v1.41 the last 3 or so hours, I’d say there is a slight overall increase in messages/tracks (Mini @ 20 Mhz). CPU use is up approx 2%. We have a lot more room on the CPU, so if it needs to be loosened up a bit to make the buffer work a bit better, then let it fly.
I have an R2 en-route and will be more than happy to provide future tests @ 24Mhz showing side by side with my other rig as a watermark. It’s almost impossible to get decent results otherwise since traffic is dynamic, but I have two otherwise identical rigs that can be put to good use if/as needed.
Updated this morning and saw that the latest version is now airspy_adsb v1.42
So testing it now
Indeed, yet another version, testing it as well…
1.42 version installed !
v1.42 improves the 12MHz mode only. The rest is identical.
1 Like
I guess that explains why we see no change on the above 
Do you require a 12Mhz run?
Yes. Sorry, I forgot to publish what has actually changed.
Now the question is how good is 12MHz now?
v1.42 (20Mhz) → v1.41 (12Mhz) → v1.42 (12Mhz)
Mirror RTL Rig:
CPU:
Unfortunately my traffic happened to crater right as I made the switch between v1.41 >> v1.42 @ 12Mhz, but not seeing much there in all honesty in comparison to the watermark RTL. About 1% less CPU use, some signal strength differences. Not worse by any means, but not seeing much to the upside either @12Mhz. It’s so very tough to tell, even with a mirror rig.
Can please breakdown switch -r ?
That Avionics looks good, is that a program or ???
Jeff
For me, 12 MHz is about 40 msg/sec less than 20 Mhz when the message rate is in the 600-700 msg/sec range.
The way I test is to watch the SkyAware msg/sec counter. I then go in, edit the /etc/default/airspy_adsb. then I do an “sudo systemctl restart airspy_adsb dump1090-fa” and I wait for everything to reconnect and the SkyAware msg/sec to normalize. Usually about 15-20 seconds.
Mike
It’s rpi-monitor ( GitHub - XavierBerger/RPi-Monitor: Real time monitoring for embedded devices ) with some customization - scroll up a bit in this thread and you will see the code to add.
Would anybody like to tell me what the difference is here with the yellow section. Prior to switching to v.141 and then v.142, my “min/max” was quite often below the dark blue line. After switching to v.141 and v.142, my “min/max” is more in between the light blue and dark blue and sometimes even above the light blue.
You graphs installation is too new.
The yellow area is the min/max area of the last 7 days.
1 Like
The yellow section shows the minium and maximum over the preceding 7 days, so until you are in to the 8th day, you are likely to see numbers outside of that area. It’s a reasonable indicator as to whether you are seeing things outside the normal range, but things do fluctuate naturally a bit either side.
1 Like
Thanks for that. Looks handy to keep tabs of versions etc
How do you print the CPU usage by process ?
Thanks.
try top or htop. I think you can add a sort function. Not sure about CPU though.
sudo apt update
sudo apt install htop
htop
Press Shift-P to sort by CPU usage.
But i believe this question was about Rpi-Monitor.