Airspy用のADS-B feeder設定
使用機材
FlightawareのPiawareをインストール
- いくつか導入するfeederのうち、Piawareが中核となるよう導入する。
- しかし、Piawareは現時点では32bit版しかリリースされていないため、Flightawareのフォーラムを参考にして、abcd567a氏が64bit用にコンパイルしたPiaware 7.2を利用する。
$ sudo wget -O /etc/apt/sources.list.d/abcd567a.list https://abcd567a.github.io/rpi/abcd567a.list $ sudo wget -O /etc/apt/trusted.gpg.d/abcd567a-key.gpg https://abcd567a.github.io/rpi/KEY2.gpg $ sudo apt update $ sudo apt install piaware $ sudo apt install dump1090-fa $ sudo apt install piaware-web $ sudo piaware-config feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx $ sudo reboot
64bit版Raspberry Pi OSに32bit版のパッケージを導入できるようにする
$ sudo dpkg --add-architecture armhf $ sudo apt update $ sudo dpkg --print-architecture
arm64
$ sudo dpkg --print-foreign-architectures
armhf
Flightradar24のfeederをインストール
- なんだかんだで、webサービスはFlightradar24が使いやすいので導入してfeedしておく
$ sudo bash -c "$(wget -O - https://repo-feed.flightradar24.com/install_fr24_rpi.sh)"
______ _ _ _ _ _ _____ ___
| ___|| |(_) | | | | | | / __ \ / |
| |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
| _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
| | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
\_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
__/ |
|___/
[main][i]FR24 Feeder/Decoder
[main][i]Version: 1.0.30-3/generic
[main][i]Built on Sep 1 2022 09:40:07 (HEAD-00021a4.git/Linux/static_armel)
[main][i]Running on: debian11
[main][i]Local IP(s): 192.168.xxx.xxx,xxxx::xxxx:xxxx:xxxx:xxxx
[main][i]Copyright 2012-2022 Flightradar24 AB
[main][i]https://www.flightradar24.com
[main][i]DNS mode: PING
Welcome to the FR24 Decoder/Feeder sign up wizard!
Before you continue please make sure that:
1 - Your ADS-B receiver is connected to this computer or is accessible over network
2 - You know your antenna's latitude/longitude up to 4 decimal points and the altitude in feet
3 - You have a working email address that will be used to contact you
4 - fr24feed service is stopped. If not, please run: sudo systemctl stop fr24feed
To terminate - press Ctrl+C at any point
Step 1.1 - Enter your email address (username@domain.tld)
$:example@example.com
Step 1.2 - If you used to feed FR24 with ADS-B data before, enter your sharing key.
If you don't remember your sharing key, you can find it in your account on the website under "My data sharing".
https://www.flightradar24.com/account/data-sharing
Otherwise leave this field empty and continue.
$:xxxxxxxxxxxxxxxx
Verifying sharing key...OK
Step 1.3 - Would you like to participate in MLAT calculations? (yes/no)$:
IMPORTANT: For MLAT calculations the antenna's location should be entered very precise!
Step 3.A - Enter antenna's latitude (DD.DDDD)
$:35.xxxxxx
Step 3.B - Enter antenna's longitude (DDD.DDDD)
$:139.xxxxxx
Step 3.C - Enter antenna's altitude above the sea level (in feet)
$:xxx
Using latitude: xx.xxxx, longitude: xxx.xxxx, altitude: xxxft above sea level
We have detected that you already have a PiAware application installed. We can therefore try to automatically configure the FR24 feeder to use existing receiver configuration, or you can manually configure all the parameters.
Would you like to use autoconfig (*yes*/no)$:yes
Step 6 - Please select desired logfile mode:
0 - Disabled
1 - 48 hour, 24h rotation
2 - 72 hour, 24h rotation
Select logfile mode (0-2)$:2
Saving settings to /etc/fr24feed.ini...OK
Settings saved, please run "sudo systemctl restart fr24feed" to use new configuration.
Installation and configuration completed!
ADS-B Exchangeのfeederをインストール
- Flightradar24やFlightaware、Radarboxなどのように有料サービスを売るのが目的ではなく、多くの機能を利用料不要で運営している（好き！）
- プライベート機も国有機も軍用機も一切の忖度せずフィルタリングしない男気あるサービス（好き！）
- Flightradar24などのログは補完処理などが施されるが、ADS-B Exchangeは基本的には受信した生データを保存・公開しているとのこと（好き！）
$ sudo bash -c "$(wget -O - wget https://adsbexchange.com/feed.sh)"
Thanks for choosing to share your data with ADS-B Exchange! ADSBexchange.com is a co-op of ADS-B/Mode S/MLAT feeders from around the world. This script will configure your current your ADS-B receiver to share your feeders data with ADS-B Exchange. Would you like to continue setup?
Please enter a unique name to be shown on the MLAT map (map.adsbexchange.com/mlat-map)(the pin will be offset for privacy) Example: "william34-london", "william34-jersey", etc. Disable MLAT: enter a zero: 0
For MLAT the precise location of your antenna is required. A small error of 15m/45ft will cause issues with MLAT! To get your location, use any online map service or this website: https://www.mapcoordinates.net/en Enter your receivers precise latitude in degrees with 5 decimal places. (Example: 32.36291) Enter your receivers longitude in degrees with 5 decimal places. (Example: -64.71492) Enter your receivers altitude above sea level including the unit, no spaces: in feet like this: 255ft or in meters like this: 78m We are now ready to begin setting up your receiver to feed ADS-B Exchange. Do you wish to proceed? New UUID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
feederだけであればこれで完了。アップロードした統計が見たい場合はstatsもインストールする。
$ sudo bash -c "$(wget -O - wget https://raw.githubusercontent.com/adsbxchange/adsbexchange-stats/master/stats.sh)"
Using existing valid UUID (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) from /usr/local/share/adsbexchange/adsbx-uuid ##################################### xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx ##################################### https://www.adsbexchange.com/api/feeders/?feed=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx #####################################
Radarboxのfeederをインストール
- 軍用機のフィルタリングがFlightradar24より甘いので、軍用機マニアにはわりと重宝されているらしい
- 地図プロットの使いやすさは、Flightradar24 > Radarbox > ADS-B Exchange > Flightawareという感じなので入れておく
$ sudo bash -c "$(wget -O - wget http://apt.rb24.com/inst_rbfeeder.sh)"
!!!! IMPORTANT !!!! By default, RBFeeder is configured to connect to your local dump1090 instance (localhost, port 30005). If you want to use a USB RTL-SDR dongle instead, please run this command: sudo rbfeeder --set-network-mode off --no-start Then, restart the daemon: sudo systemctl restart rbfeeder After a few seconds, RBFeeder will connect to the AirNav servers and you can view your sharing-key with this command: sudo rbfeeder --showkey If you already have a sharing-key from previous a installation, you can set the same key using this command: sudo rbfeeder --setkey ?your sharing key?
既存の共有キーを入力しておく
$ sudo rbfeeder --setkey ********************************
これだけだとMLAT演算に協力できないので、MLAT用のソフトも導入しておく。
$ sudo apt install mlat-client
Installation finished.
MALT用に設定を書き換える
- MLAT演算用の座標
lat: 緯度（小数点以下6桁以上）lon: 経度（小数点以下6桁以上）alt: 標高（海抜何mか。整数）
- MLATプログラム起動用
mlat_cmd: コメント解除する
$ sudo vi /etc/rbfeeder.ini
[client] network_mode=true log_file=/var/log/rbfeeder.log key=******************************** sn=EXTRPI****** # Add these information # 'alt' key accepts integer value only. Floating-point causes error. lat=**.****** lon=***.****** alt=** [network] mode=beast external_port=30005 external_host=127.0.0.1 [mlat] autostart_mlat=true # uncomment this line mlat_cmd=/usr/bin/python3.9 /usr/bin/mlat-client [dump978] #dump978_enabled=true
Airspy専用のADS-Bデコーダーの導入
$ sudo bash -c "$(wget -O - https://raw.githubusercontent.com/wiedehopf/airspy-conf/master/install.sh)"
ADS-B受信状況の統計情報収集ツールの導入
- 最近はGrafanaで可視化する見た目のかっこいいツールもあるようだが、セットアップの簡単な古典的なものを導入する
$ sudo bash -c "$(wget -q -O - https://raw.githubusercontent.com/wiedehopf/graphs1090/master/install.sh)"
All done! Graphs available at http://192.168.xxx.xxx/graphs1090 It may take up to 10 minutes until the first data is displayed
Raspberry Pi + GPS HATでGPS時刻に同期する
使用機材
Raspberry Pi OSのインストール
- Raspberry Pi OSのDLページからRaspberry Pi Imagerをダウンロードしてインストール
- 以下の設定でインストール
- OS: Raspberry Pi OS Lite (64bit)
- SSH: 有効化する
- User: ユーザー名とパスワードを事前に設定
- Locale: Asia/Tokyo, jp
- Telemetry: 有効化しない
設定
システム設定
$ sudo raspi-config
6 Advanced OptionsA1 Expand Filesystem
3 Interface OptionsI5 I2CWould you like the ARM I2C interface to be enabled?: Yes
I6 Serial PortWould you like a login shell to be accessible over serial?: NoWould you like the serial port hardware to be enabled?: Yes
GPS+RTC HAT（RTC用）
i2c用ツールの導入
$ sudo apt-get install i2c-tools $ sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- 42 -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- 52 -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --
$ sudo vi /boot/config.txt
# Add this line dtoverlay=i2c-rtc,rv3028
$ sudo reboot $ sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- 42 -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --
$ sudo apt-get -y remove fake-hwclock $ sudo update-rc.d -f fake-hwclock remove $ sudo systemctl disable fake-hwclock $ sudo vi /lib/udev/hwclock-set
#!/bin/sh # Reset the System Clock to UTC if the hardware clock from which it # was copied by the kernel was in localtime. dev=$1 #if [ -e /run/systemd/system ] ; then # exit 0 #fi #/sbin/hwclock --rtc=$dev --systz #/sbin/hwclock --rtc=$dev --hctosys
GPS+RTC HAT（GPS用）
$ sudo apt-get install pps-tools $ sudo vi /boot/config.txt
# Add these lines dtoverlay=disable-bt dtoverlay=pps-gpio,gpiopin=18
$ sudo vi /etc/modules
# Add this line
pps-gpio
$ sudo reboot $ sudo ppstest /dev/pps0
trying PPS source "/dev/pps0" found PPS source "/dev/pps0" ok, found 1 source(s), now start fetching data... source 0 - assert 1663939406.000000195, sequence: 30492 - clear 0.000000000, sequence: 0 source 0 - assert 1663939407.000001610, sequence: 30493 - clear 0.000000000, sequence: 0 source 0 - assert 1663939408.000001377, sequence: 30494 - clear 0.000000000, sequence: 0 source 0 - assert 1663939409.000002274, sequence: 30495 - clear 0.000000000, sequence: 0 source 0 - assert 1663939409.999999356, sequence: 30496 - clear 0.000000000, sequence: 0 source 0 - assert 1663939410.999997753, sequence: 30497 - clear 0.000000000, sequence: 0
GPSDの導入（GPSデバイスとの通信、PPSの管理）
$ sudo apt-get install gpsd gpsd-clients $ sudo vi /etc/default/gpsd
# Devices gpsd should collect to at boot time. # They need to be read/writeable, either by user gpsd or the group dialout. DEVICES="/dev/ttyAMA0 /dev/pps0" # Other options you want to pass to gpsd GPSD_OPTIONS="-n -s 115200" # Automatically hot add/remove USB GPS devices via gpsdctl USBAUTO="false" # Start the gpsd daemon automatically at boot time # START_DAEMON="true"
$ sudo systemctl enable gpsd.service $ sudo systemctl restart gpsd.service $ sudo systemctl enable gpsd.socket $ sudo systemctl restart gpsd.socket
Chronyの導入（ntpdの代替）
$ sudo apt-get install chrony $ sudo vi /etc/chrony/chrony.conf
# Welcome to the chrony configuration file. See chrony.conf(5) for more # information about usable directives. # Include configuration files found in /etc/chrony/conf.d. confdir /etc/chrony/conf.d # Use Debian vendor zone. #pool 2.debian.pool.ntp.org iburst # Use time sources from DHCP. sourcedir /run/chrony-dhcp # Use NTP sources found in /etc/chrony/sources.d. sourcedir /etc/chrony/sources.d # This directive specify the location of the file containing ID/key pairs for # NTP authentication. keyfile /etc/chrony/chrony.keys # This directive specify the file into which chronyd will store the rate # information. driftfile /var/lib/chrony/chrony.drift # Save NTS keys and cookies. ntsdumpdir /var/lib/chrony # Uncomment the following line to turn logging on. #log tracking measurements statistics # Log files location. logdir /var/log/chrony # Stop bad estimates upsetting machine clock. leapsecmode slew # This directive enables kernel synchronisation (every 11 minutes) of the # real-time clock. Note that it can’t be used along with the 'rtcfile' directive. rtcsync # Step the system clock instead of slewing it if the adjustment is larger than # one second, but only in the first three clock updates. makestep 1 3 # Get TAI-UTC offset and leap seconds from the system tz database. # This directive must be commented out when using time sources serving # leap-smeared time. leapsectz right/UTC # NICT server ntp.jst.mfeed.ad.jp minpoll 6 maxpoll 16 iburst # Reference Clock refclock SHM 0 refid SHM0 offset 0.053 noselect refclock SHM 1 refid SHM1 pps prefer trust refclock SHM 2 refid SHM2
$ sudo systemctl enable chrony
$ sudo systemctl start chrony
$ sudo systemctl disable systemd-timesyncd.service
$ chronyc tracking
Reference ID : 53484D31 (SHM1) Stratum : 1 Ref time (UTC) : Fri Sep 23 14:24:36 2022 System time : 0.000000257 seconds slow of NTP time Last offset : -0.000000327 seconds RMS offset : 0.000000577 seconds Frequency : 10.477 ppm fast Residual freq : -0.001 ppm Skew : 0.023 ppm Root delay : 0.000000001 seconds Root dispersion : 0.000012924 seconds Update interval : 16.0 seconds Leap status : Normal
$ chronyc sources -v
.-- Source mode '^' = server, '=' = peer, '#' = local clock. / .- Source state '*' = current best, '+' = combined, '-' = not combined, | / 'x' = may be in error, '~' = too variable, '?' = unusable. || .- xxxx [ yyyy ] +/- zzzz || Reachability register (octal) -. | xxxx = adjusted offset, || Log2(Polling interval) --. | | yyyy = measured offset, || \ | | zzzz = estimated error. || | | \ MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== #? SHM0 0 4 377 18 +30ms[ +30ms] +/- 221us #* SHM1 0 4 377 19 -427ns[ -734ns] +/- 192ns #- SHM2 0 4 377 19 -427ns[ -427ns] +/- 194ns ^? ntp2.jst.mfeed.ad.jp 2 12 377 623 -3354us[-3362us] +/- 64ms
$ chronyc sourcestats -v
.- Number of sample points in measurement set.
/ .- Number of residual runs with same sign.
| / .- Length of measurement set (time).
| | / .- Est. clock freq error (ppm).
| | | / .- Est. error in freq.
| | | | / .- Est. offset.
| | | | | | On the -.
| | | | | | samples. \
| | | | | | |
Name/IP Address NP NR Span Frequency Freq Skew Offset Std Dev
==============================================================================
SHM0 6 3 80 -27.678 120.093 +32ms 608us
SHM1 7 5 98 -0.000 0.033 -5ns 442ns
SHM2 7 5 98 -0.000 0.032 -5ns 434ns
ntp2.jst.mfeed.ad.jp 37 20 277m -0.014 0.057 -3814us 340us
ひとりごと
- RTC, PPS, GPSDの導入辺りまではわりと問題なく進む
- 今回はNTPDではなくChronyを選択したが、設定の難易度は大きくは変わらない
- NTPDとChronyの設定で違うこと（はまりやすいポイント）
- Chronyは、
refidの文字数が4文字までに制限されている - Chronyは、NTPDのような疑似IPによるローカルクロックデバイス指定ではなく、
refclockなどと指定する
- Chronyは、
- 公式ドキュメントやソースコードのコメント依ると・・・、
- GPSDのShared memoryによる時刻提供は、1つのGPSデバイスに対して2つのshmアドレスを割り当て、#0がNMEA（時刻含まれているが精度低い）で#1がPPS（精度が高く、時刻情報もマージされている）とのことらしい
The magic pseudo-IP address 127.127.28.0 identifies unit 0 of the ntpd shared-memory driver (NTP0); 127.127.28.1 identifies unit 1 (NTP1). Unit 0 is used for in-band message timestamps and unit 1 for the (more accurate, when available) time derived from combining in-band message timestamps with the out-of-band PPS synchronization pulse. Splitting these notifications allows ntpd to use its normal heuristics to weight them.URL
- しかしなぜか#2が存在し、しかも#2も時刻とPPSがマージされているらしい
- 以前にNTPDで同様の構築をした際も、SHMの#2 (127.127.28.2)を使用したら上手くいった（#1だと上手く同期できなかった）
- 今回は、GPSDのntpshmmonコマンドで確認したところ、#1と#2はほぼ同じ情報だったので、#1で設定してみた
- GPSDのShared memoryによる時刻提供は、1つのGPSデバイスに対して2つのshmアドレスを割り当て、#0がNMEA（時刻含まれているが精度低い）で#1がPPS（精度が高く、時刻情報もマージされている）とのことらしい
$ sudo ntpshmmon ntpshmmon: version 3.22 # Name Seen@ Clock Real L Prc sample NTP0 1663940758.092924225 1663940758.092887892 1663940757.999768955 0 -20 sample NTP1 1663940759.000949950 1663940758.999994201 1663940759.000000000 0 -20 sample NTP2 1663940759.000978172 1663940758.999994201 1663940759.000000000 0 -20 sample NTP0 1663940759.092384292 1663940759.092269478 1663940758.999768494 0 -20 sample NTP1 1663940760.000883420 1663940759.999994188 1663940760.000000000 0 -20 sample NTP2 1663940760.000910475 1663940759.999994188 1663940760.000000000 0 -20 sample NTP0 1663940760.093384713 1663940760.092514074 1663940759.999768036 0 -20 sample NTP1 1663940761.000252488 1663940760.999996509 1663940761.000000000 0 -20 sample NTP2 1663940761.000281691 1663940760.999996509 1663940761.000000000 0 -20
