Flightaware on Odroid C2

No, the mlat issue is due to the defective mlat-client supplied from RadarBox24 repositories when installed by following command

sudo apt install mlat-client

Workaround is to build mlat-client from source-code

Step-1: Install required packages (dependencies and build tools)

sudo apt update -y

sudo apt install -y git curl build-essential debhelper python-dev python3-dev 

Step-2: Download source code

cd 

git clone https://github.com/mutability/mlat-client.git

Step-3 Issue following 3 commands to build

cd mlat-client 

sudo apt install -y dh-python 

sudo dpkg-buildpackage -b -uc 

Step-4: Above command will take some time to build package. After the package is built, install it by following command

cd 

sudo dpkg -i mlat-client_*.deb 

Step-5: IMPORTANT: Put your mlat-client on hold so that it is NOT replaced by RB24 defective copy during any manual or automatic upgrades.

sudo apt-mark hold mlat-client

Step-6: Restart rbfeeder

sudo systemctl restart rbfeeder   

Step-7: After 15 minutes, check status of mlat on following page:

(Replace xxxxxx by your actual station number)

http://radarbox24.com/stations/EXTRPIxxxxxx

 

 

Thanks abcd567

Mlat now also working on radarbox.

I am very happy with al the answers, on my own it was never happened.

1 Like

Sorry that i must ask agian to help me.

today i have installed a new antenna, so i powered off the odroid. after installing the antenna i started the odroid again. but there is no data send to the different flight sites.

after looking i get this error on my odroid

“unable to resolve host odroid: Temporary failure in name resolution”

so i looked on the net and found that i have to set the etc/hosts file

but after editing that file i get the error

" File ‘/etc/hosts’ is unwritable "

how can i fix this?

Can you link that advice?

i can find it on many sites.
but i can not edit the hosts file, because it is read only. not only this file, but the whole file system

maybe it is better to do a complete fresh install

May be during reboot, the file system has been mounted as “read-only”

Before attempting fresh install, issue following command to make the file system “read-write”

sudo mount -o remount,rw /

 

Does not work. i get now the following error:

sudo: unable to resolve host odroid: Temporary failure in name resolution
mount: /: cannot remount /dev/mmcblk0p2 read-write, is write-protected.

Switch to user root and try

sudo su 

mount -o remount,rw / 

If above fails, then try REBOOT and check

pi@raspberrypi:~ $ mount | grep " on / "

## If read-write is restored, then above command should output following:
/dev/mmcblk0p2 on / type ext4 (rw,noatime)   

i did switch to user root, but it was the same.

so i finaly formated the sd card and now flashing ubuntu 20.04 again on the sd card.

i wil follow all above to install all the feeds, the only one i am missing is flightradar.
I did it myself but don’t know how i did that.

can you give me the script for flightradar for ubuntu 20.04 ?
Sorry , i see it now. it was the workarround.

The bash script to install FR24 fedder is as follows:

sudo bash -c "$(wget -O - http://repo.feed.flightradar24.com/install_fr24_rpi.sh)"

 

The above command sometimes fails due to issue with Flightrrdar24 key-server not supplying gpg key. In this case directly download the .deb package by wget command and after download, install it by sudo dpkg -i command. Both these commands are given below:

wget http://repo-feed.flightradar24.com/rpi_binaries/fr24feed_1.0.29-10_armhf.deb  

sudo dpkg -i fr24feed_1.0.29-10_armhf.deb   

NOTE:
(1) You must install dump1090-fa BEFORE installing FR24 and RB24
(2) Even if you have already installed dump1090-fa, you will get this warning when FR24 installation completes. Just ignore it:

Setting up fr24feed:armhf (1.0.29-10) ...
You don't seem to have any dump1090 installed. On the fr24feed start it will automatically install dump1090-mutability.

 

Sorry that i have to ask again to fix a problem.

Today i received a filer, i installed the filter and after that odroid wasn’t working anymore.
aftyer hours i decided to install everything again.

everything is now working, exept radarbox:
there are no planes send to the site, and the site saYS I AM OFFLINE.
strange.
i have restarted the feeder, that didn’t help

i have installed the right key.

does anybody know what is wrong?

this is the output of sudo systemctl status rbfeeder

● rbfeeder.service - RBFeeder Service
Loaded: loaded (/lib/systemd/system/rbfeeder.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2022-08-12 17:57:14 UTC; 4min 56s ago
Process: 35224 ExecStartPre=/bin/mkdir /var/run/rbfeeder (code=exited, status=1/FAILURE)
Process: 35226 ExecStartPre=/bin/chown rbfeeder:rbfeeder /var/run/rbfeeder (code=exited, status=0/SUCCESS)
Process: 35228 ExecStartPre=/bin/touch /var/log/rbfeeder.log (code=exited, status=0/SUCCESS)
Process: 35230 ExecStartPre=/bin/chown rbfeeder:rbfeeder /var/log/rbfeeder.log (code=exited, status=0/SUCCESS)
Process: 35232 ExecStartPre=/bin/chown rbfeeder:rbfeeder /etc/rbfeeder.ini (code=exited, status=0/SUCCESS)
Process: 35234 ExecStartPre=/bin/setfacl -m u:www-data:rwx /etc/rbfeeder.ini (code=exited, status=0/SUCCESS)
Process: 35236 ExecStart=/usr/bin/rbfeeder (code=exited, status=1/FAILURE)
Main PID: 35236 (code=exited, status=1/FAILURE)

Aug 12 17:57:14 odroid systemd[1]: rbfeeder.service: Scheduled restart job, restart counter is at 5.
Aug 12 17:57:14 odroid systemd[1]: Stopped RBFeeder Service.
Aug 12 17:57:14 odroid systemd[1]: rbfeeder.service: Start request repeated too quickly.
Aug 12 17:57:14 odroid systemd[1]: rbfeeder.service: Failed with result ‘exit-code’.
Aug 12 17:57:14 odroid systemd[1]: Failed to start RBFeeder Service.

looks like the problem is solved.
I found on the net:

sudo apt update
sudo apt install netbase
sudo systemctl restart rbfeeder

als set the key again, and i see airplanes on the site.

Possibly configuration of rbfeeder is wrong.
What is output of following command?
(Replace actual values of key, lat, and lon by xxxxx when posting here)

cat /etc/rbfeeder.ini

 

 

Radarbox is working again, i did it with this commands i found on the net.

sudo apt update
sudo apt install netbase
sudo systemctl restart rbfeeder

So radar bos is working again, but MLAT not.

I have build the mlat client so as earlier in this post, but it didn’t work
Do you have suggestions for that?

cat /etc/rbfeeder.ini

[client]
network_mode=true
log_file=/var/log/rbfeeder.log

key=05c7984w35trdstgvgbvdvfgeJKHYF

sn=EXTRPI251855

[network]
mode=beast
external_port=30005
external_host=127.0.0.1

[mlat]
autostart_mlat=true
#mlat_cmd=/usr/bin/python3.9 /usr/bin/mlat-client

[dump978]
#dump978_enabled=true

1 Like

I think MLAT is working now.
looks like my postion was not entered. after i did that is was working.

1 Like

Please edit your post and replace actual value of key by xxxxxxx

 

Oops, I have missed this part of your post .

 

Usually Radarbox24 MLAT does NOT start showing on map immediately after start of rbfeeder. It takes about 5 minutes to 1/2 hour to start showing. Seems their MLAT Servers take time to synchronize and updating the map.

 

You can check If MLAT has been successfully started by rbfeeder by following method:

To check if mlat is active, run status command:

sudo systemctl status rbfeeder  

If mlat-client is working OK, the output of status command should contain two lines under CGroup as shown below. The 2nd line is for starting the mlat-client

CGroup: /system.slice/rbfeeder.service
             ├─1477 /usr/bin/rbfeeder
             └─1494 /usr/bin/python3.9 /usr/bin/mlat-client --input-type dump1090 --input-connect 127.0.0.1:32457 --server mlat1.rb24.com:40900 --lat 43.5xxxxx --lon -79.6xxxx --alt 155 --user EXTRPI000008 --results beast,connect,127.0.0.1:32004 

 

If line “/usr/bin/python3.9 /usr/bin/mlat-client” is missing, Reboot RPi and check again, it should appear now

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.