Main Menu

Recent posts

#1
AirNav Radar Discussion / Re: Database Update Requests
Last post by Runway 31 - Today at 07:18:38 PM
Thanks Carlos

Alan
#2
AirNav Radar Discussion / Re: Database Update Requests
Last post by Runway 31 - Today at 07:12:12 PM
I-CUND was added in yesterday John, thanks

Alan
#3
AirNav Radar Discussion / Re: Database Update Requests
Last post by Runway 31 - Today at 07:11:01 PM
Thanks X

Alan
#4
AirNav Radar Discussion / Re: Map Options: Radar Mode
Last post by Runway 31 - Today at 07:05:06 PM
Doesnt look like its available on the app, suggest you ask Airnac whether it will become available

Alan
#5
AirNav Radar Discussion / Map Options: Radar Mode
Last post by nomad23 - Today at 05:15:33 PM
Hello,

I really enjoy using the Radar Mode option for viewing aircraft.  I see that it appears only when using the web interface and not on any app (iOS).  Am I missing something to check or is this functionality limited only to the web version?  If so, are there any future plans to add it to your apps?

Many thanks,
Chris
#6
AirNav Radar Discussion / rbfeeder 1.0.17+trixie uses 10...
Last post by cs.dk - Today at 09:22:18 AM
Setup (two identical feeders, same behaviour on both):
- Raspberry Pi 5, Raspberry Pi OS Trixie (arm64), kernel 6.18.60+rpt-rpi-v8
- rbfeeder 1:1.0.17+trixie (arm64), latest from the AirNav repo
- Airspy Mini -> airspy_adsb -> readsb; rbfeeder takes Beast input from readsb on localhost
- MLAT client built manually (no Trixie package)

Problem:
At night, when the airspace is empty, rbfeeder goes to exactly 100% of one core and stays there until the next aircraft appears. As soon as messages arrive again, CPU drops back to a few percent. readsb, airspy_adsb and the other feeders (FlightAware, FR24) are unaffected.

Example from last night (Feeder I), CPU sampled every minute:
- 02:45-02:46: 245 packets/min sent, rbfeeder at a few %
- 02:47: packets drop to 20, then 1-2 per minute
- 02:47-03:23: rbfeeder at 99.8-100.5% of one core, 0 aircraft, 0.0 msg/s from readsb
- 03:24: an aircraft appears (93, then 245 packets/min), CPU back to normal

The same happened at 01:23, 01:41 and 03:59, and on Feeder II at 02:53-03:17 and 03:59-04:05 - always exactly when the message rate hits zero.

The journal shows nothing unusual during the spikes: only the normal "Statistics updated every 60 seconds" lines, plus a single MLAT server reconnect at 03:00:01 (reconnected after 11 s), which does not line up with the spike.

It looks like a busy-wait/polling loop when the Beast input is idle, instead of blocking on the socket. Is this a known issue, and is a fix planned? For now I am limiting the service with CPUQuota=20% as a workaround.

Happy to provide more logs or test a build.
#7
AirNav Radar Discussion / Re: Database Update Requests
Last post by X - Today at 08:31:38 AM
Quote from: Runway 31 on November 20, 2026, 06:42:21 PMThanks X, can you confirm the routing for SYL461. Using 2 Moscow airports UUEE-UUWW-

Should be UEEE-UUWW

X
#8
AirNav Radar Discussion / Re: Database Update Requests
Last post by jdsd - Today at 06:57:29 AM
Morning Alan

Please add I-CUND 300AE8  Piper Seneca II  34-79700108

Thanks
John
#9
AirNav Radar Discussion / Re: Database Update Requests
Last post by CarlosAbreu - Today at 01:48:45 AM
Alan

20-11-2026 Updated file in attach.

Carlos
#10
AirNav Radar Discussion / Re: Database Update Requests
Last post by Runway 31 - November 20, 2026, 06:48:55 PM
Thanks Carlos

Alan