yup - good antennas does not differ that much. the radarcape simply produces lots more. but what really increased my dongle message rate about nearly 40% was an amplifier. maybe you should try one too …
Hi, now i haven’t been on here for about a month and noticed my position has dropped from position 70-80 to now being position 430. I get that now M-LAT stats are now being included, my questions would be:
I understand why i have move down the leaderboards, what I don’t get is why my aircraft seen has dropped dramatically since this M-LAT stuff. Look at my Daily Collection Graphs, avgeraging 3500 - 4500 a day, now it only sees 1500-2000, that is a huge drop! Nothing my end changed, it dropped on the 18th, the same day as this update.
Why can’t there be separate leaderboards for ADS-B, M-LAT and then a combined one.
You call this section of the website My ADS-B, you might as well rename it to My M-LAT. Wouldn’t it be more fair to make it so the ADS-B results are weighted more on the stats, i.e seeing 3 M-LAT aircrafts is equivalent to 1 ADS-B, to me that would be fairer as it takes at least 3 people with M-LAT to give the same data as 1 person with ADS-B.
You call this section of the website My ADS-B, you might as well rename it to My M-LAT. Wouldn’t it be more fair to make it so the ADS-B results are weighted more on the stats, i.e seeing 3 M-LAT aircrafts is equivalent to 1 ADS-B, to me that would be fairer as it takes at least 3 people with M-LAT to give the same data as 1 person with ADS-B.
mlat does not affect the total; if mlat stopped working tomorrow, the totals would not change, all that would happen is that aircraft would move from “mlat” to “other”.
The first piaware I built (NooElec NESDR Mini 2 dongle) frequently had this error. I started saving the log files each day and realized that it seemed to occur at similar times each day. The box sat on a windowsill and the times corresponded to periods such as sunrise, the time of direct sunlight, the time when the sun passed below adjacent buildings, nightfall, etc. Some amount of searching later and I came to understand the temperature reference as well as the advantage of a dongle with a TCXO.
The problem isn’t the temperature of the Pi, it’s the temperature of the crystal oscillator in the dongle and the issue isn’t about absolute temperature but temperature stability. Any change to the temperature will cause a frequency change in the crystal. When the temperature changes and the resulting frequency change is too large, this will result in the clock instability error.
The best way to fix this problem is to replace your dongle and spend $2 to $4 more on one with a Temperature Compensated Oscillator (TCXO) such as the NooElec NESDR Mini 2+ 0.5PPM TCXO or the RTL-SDR Blog R820T2 RTL2832U 1PPM TCXO. I have used both of those and never seen the clock instability problem. In fact, the latter dongle and that first piaware just spend a couple of months outdoors in temperatures ranging from -12°C to 21°C with frequent 10° swings and never gave an error.