I know that a pulse wave via the GPIO is different from processing antenna signals, but these external connectors/wifi/BT impact the Raspberry. Putting ferrite clamps on the ethernet cable and USB power cable contributed big time. It is amazing what a difference the “kill all rf”, disconnecting the HDMI cable, keyboard and mouse make. OT: I attached a Raspberry Pi to my scope and generated a pulse wave on the GPIO and compared it with a function generator. I have the wrong one with one port and no video out (I don’t want video out BTW) Unfortunately I was a little intoxicated when I was fed up with the poor performance of the $8 China dongle which led to purchasing the Radarcape.
#Planeplotter vnc trial#
It’s not a game of spending the most money, but trial and error for me. The Yagi might be the next step - I asked you in the other topic if some of your unused equipment was for sale. It wouldn’t surprise me if you made similar choices in the past after seeing pictures of your setup. Planeplotter (low shared antenna): 2111 aircraft 171k positionsĬoncerning core elements, I prefer to buy the best product because I know that the irritation of not making progress due to opting for the lower quality is greater than the pain of the price difference. Radarcape (high antenna): 1979 aircraft 286k positionsĪirspy (low shared antenna): 2244 aircraft 290k positions The Airspy connected to modesmixer2 and PiAware produces the highest number of positions and aircraft Planeplotter connected to the same source has a much lower message rate but a tenfold higher number of planes in the > 400km zone and Radarcape is lagging a bit.
Basically: an optimized and isolated Radatcape, and two configurations fed by the same antenna and ADSB_Spy.
#Planeplotter vnc Pc#
The Airspy is connected to a PC running ADSB_Spy which feeds Planeplotter and Modesmixer2 which feeds socat on a Piaware. I’m aware of the less-than-optimal location of the LNA. A second similar antenna is connected to 5 meter coax, an Uputronics ceramic LNA and an Airspy. To illustrate the previous remark: I have one antenna on a high pole mounted to the side of the house connected to a 3 pole filter and a radarcape. If you optimize for high numbers instead of high quality data, then it’s easy to split one feed, have it processed by different applications and merge it again as an example. What is your definition of a message? Does it include partial, incomplete or test messages as well or is it limited to the main type codes as 11/17/18? This document helped me to understand what you’re receiving and which signals are useful. The connector usually doesn’t have a typical resistance rating, but if you use 75 Ohm coax, you might introduce avoidable cable/insertion losses as the antenna and Prostick are optimized for 50 Ohm
#Planeplotter vnc software#
If it were indeed a hardware ‘issue’ (it really isn’t an issue since performance is pretty great), I’d suspect it to be the ProStick since the Pi runs at about 20% CPU.ī) Software limitations - I’ve read somewhere that the practical limit for dump1090 seems to be around 1600 messages per second, but can’t verify that claim. I’ve been thinking about this and have a few ideas:Ī) Hardware limitations - Either the ProStick or RPi can’t keep up with the amount of incoming messages.
I wouldn’t expect that aircraft broadcast more messages during nighttime for some reason. My question is: why is the percentage of aircraft without positions much higher during the day than during the night? The message rate per aircraft seems to be relatively low during the day when compared to nighttime, which also might be a contributing factor. As you can see, I’m averaging about 1300-1400 messages/s with 200-250 planes during the day.
0 kommentar(er)
