No data output

[HF_ATL]

Hello all,

I'm having some difficulties setting up the FR24feed+dump1090-fa.
I have a raspbian image. I installed dump1090-fa according to https://flightaware.com/adsb/piaware/install
I have two dongles (one FA blue and the other is a RTL-SDR v3), one with SN changed to 00000000 and the other with SN changed to 00000001.
Two dump1090-fa are installed, dump1090-fa and dump1090-fa-2
Dump1090-fa is using device index 00000000 and dumo1090-fa-2 is using device index 00000001.
FR24feed.ini is using dongle #0 and fr24feed-2.ini is using dongle #1.
Piaware conf is using device index 0. Gain set to 40.
I have changed the server port of the lighttpd to port 81 due to the fact that another software is using port 80.
The problem is that neither dongles receive any data. Map show no planes.
Http://ip:8754 shows Connected via UDP (beast-TCP, connected) but aircraft tracked/upload is 0.

Any help please diagnosing this issue?


Thank you in advance!

[HF_ATL]

Btw, rtl_test -t shows:

rtl_test -t
Found 2 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001
1: Realtek, RTL2832U, SN: 00000000

Using device 0: Generic RTL2832U OEM
usb_claim_interface error -6
Failed to open rtlsdr device #0.

[Oblivian]

There's your answer.

Usb in use something has it open already

[abcd567]

Dump1090-fa is using device index 00000000 and dumo1090-fa-2 is using device index 00000001.
FR24feed.ini is using dongle #0 and fr24feed-2.ini is using dongle #1.

Conflict.
2 dongles, but 4 programs configured to use them:

dump1090-fa
dump1090-fa-2
fr24feed
fr24feed-2


Please post contents of files
/etc/fr24feed.ini
/etc/fr24feed-2.ini


.

[HF_ATL]

Thank you both for your answers.
Usb is in use supposedly because the dump1090-fa and dump1090-fa were running at that time thus using the USB devices I suppose.
The contents of the fr24feeds are present in the image attached.
Btw I run the following command: journalctl | grep dump1090-fa which gives me the following output:


May 14 07:31:31 openwebrx dump1090-fa2[22055]: Thu May 14 07:31:31 2020 UTC dump1090-fa 3.8.1 starting up.
May 14 07:31:31 openwebrx dump1090-fa2[22055]: rtlsdr: no device matching '00000102' found.
May 14 07:31:31 openwebrx dump1090-fa2[22055]: rtlsdr: found 2 device(s):
May 14 07:31:31 openwebrx dump1090-fa2[22055]: 0: Realtek, RTL2838UHIDIR, SN: 00000001
May 14 07:31:31 openwebrx dump1090-fa2[22055]: 1: Realtek, RTL2832U, SN: 00000000
May 14 07:31:31 openwebrx systemd[1]: dump1090-fa2.service: Main process exited, code=exited, status=1/FAILURE
May 14 07:31:31 openwebrx systemd[1]: dump1090-fa2.service: Failed with result 'exit-code'.
May 14 07:32:01 openwebrx systemd[1]: dump1090-fa2.service: Service RestartSec=30s expired, scheduling restart.
May 14 07:32:01 openwebrx systemd[1]: dump1090-fa2.service: Scheduled restart job, restart counter is at 1196.
May 14 07:32:01 openwebrx dump1090-fa2[22164]: Thu May 14 07:32:01 2020 UTC dump1090-fa 3.8.1 starting up.
May 14 07:32:01 openwebrx dump1090-fa2[22164]: rtlsdr: no device matching '00000102' found.
May 14 07:32:01 openwebrx dump1090-fa2[22164]: rtlsdr: found 2 device(s):
May 14 07:32:01 openwebrx dump1090-fa2[22164]: 0: Realtek, RTL2838UHIDIR, SN: 00000001
May 14 07:32:02 openwebrx dump1090-fa2[22164]: 1: Realtek, RTL2832U, SN: 00000000
May 14 07:32:02 openwebrx systemd[1]: dump1090-fa2.service: Main process exited, code=exited, status=1/FAILURE
May 14 07:32:02 openwebrx systemd[1]: dump1090-fa2.service: Failed with result 'exit-code'.
May 14 07:32:32 openwebrx systemd[1]: dump1090-fa2.service: Service RestartSec=30s expired, scheduling restart.
May 14 07:32:32 openwebrx systemd[1]: dump1090-fa2.service: Scheduled restart job, restart counter is at 1197.
May 14 07:32:32 openwebrx dump1090-fa2[22258]: Thu May 14 07:32:32 2020 UTC dump1090-fa 3.8.1 starting up.
May 14 07:32:32 openwebrx dump1090-fa2[22258]: rtlsdr: no device matching '00000102' found.
May 14 07:32:32 openwebrx dump1090-fa2[22258]: rtlsdr: found 2 device(s):
May 14 07:32:32 openwebrx dump1090-fa2[22258]: 0: Realtek, RTL2838UHIDIR, SN: 00000001
May 14 07:32:32 openwebrx dump1090-fa2[22258]: 1: Realtek, RTL2832U, SN: 00000000
May 14 07:32:32 openwebrx systemd[1]: dump1090-fa2.service: Main process exited, code=exited, status=1/FAILURE
May 14 07:32:32 openwebrx systemd[1]: dump1090-fa2.service: Failed with result 'exit-code'.
May 14 07:33:02 openwebrx systemd[1]: dump1090-fa2.service: Service RestartSec=30s expired, scheduling restart.
May 14 07:33:02 openwebrx systemd[1]: dump1090-fa2.service: Scheduled restart job, restart counter is at 1198.
May 14 07:33:02 openwebrx dump1090-fa2[22373]: Thu May 14 07:33:02 2020 UTC dump1090-fa 3.8.1 starting up.
May 14 07:33:02 openwebrx dump1090-fa2[22373]: rtlsdr: no device matching '00000102' found.
May 14 07:33:02 openwebrx dump1090-fa2[22373]: rtlsdr: found 2 device(s):
May 14 07:33:03 openwebrx dump1090-fa2[22373]: 0: Realtek, RTL2838UHIDIR, SN: 00000001
May 14 07:33:03 openwebrx dump1090-fa2[22373]: 1: Realtek, RTL2832U, SN: 00000000
May 14 07:33:03 openwebrx systemd[1]: dump1090-fa2.service: Main process exited, code=exited, status=1/FAILURE
May 14 07:33:03 openwebrx systemd[1]: dump1090-fa2.service: Failed with result 'exit-code'.
May 14 07:33:33 openwebrx systemd[1]: dump1090-fa2.service: Service RestartSec=30s expired, scheduling restart.
May 14 07:33:33 openwebrx systemd[1]: dump1090-fa2.service: Scheduled restart job, restart counter is at 1199.
May 14 07:33:33 openwebrx dump1090-fa2[22488]: Thu May 14 07:33:33 2020 UTC dump1090-fa 3.8.1 starting up.
May 14 07:33:33 openwebrx dump1090-fa2[22488]: rtlsdr: no device matching '00000102' found.
May 14 07:33:33 openwebrx dump1090-fa2[22488]: rtlsdr: found 2 device(s):
May 14 07:33:33 openwebrx dump1090-fa2[22488]: 0: Realtek, RTL2838UHIDIR, SN: 00000001
May 14 07:33:33 openwebrx dump1090-fa2[22488]: 1: Realtek, RTL2832U, SN: 00000000

I do not know why but the system is looking for a SN 102 ("rtlsdr: no device matching '00000102' found") which is strange because nowhere I have entered this index number...

[Oblivian]

The hard config service-start files will have a --device-index 000000102
Hard specified. Need to find where.

Usually /etc/default/dump1090-fa

[HF_ATL]

Update: I found that there is another dump1090-fa instance: "sudo nano /etc/default/dump1090-fa2" which was pointed to SN102.
I have changed the ENABLED parameter to "no" to prevent it running in the boot and restarted the Pi.
Still the issue remain...

[Oblivian]

That's not always how services/Dump1090 starts.

systemctl list-unit-files | grep enabled
systemctl | grep running

You'll find them there. To disable from start it is
sudo systemctl disable <name of app>

[HF_ATL]

Thanks for the information. I have disabled it.
Now the command "systemctl list-unit-files | grep enabled" gives

.........
dump1090-fa.service enabled
..........
fr24feed-2.service enabled
fr24feed.service enabled


dump1090-fa-2 is not there. It is not expected, correct?

[Oblivian]

If you don't want it to start on boot anymore, that's correct

The | grep running one will show if it needs to be 'sudo systemctl stop <app>' too

[abcd567]

May 14 07:31:31 openwebrx dump1090-fa2[22055]:
rtlsdr: no device matching '00000102' found.

sudo nano /etc/default/dump1090-fa2" which was pointed to SN102.

I have changed the ENABLED parameter to "no" to prevent it running in the boot and restarted the Pi.
Still the issue remain...

1) Change ENABLED = no to ENABLED= yes
2) Change serial number of dongle 1 from 00000000 to 00000102 by following commands

sudo apt update
sudo apt install rtl-sdr
sudo systemctl stop piaware dump1090-fa dump1090-fa2

rtl_eeprom -d 1 -s 00000102

The last command above will generate lot of output.
The last line of output generated will be:
Write new configuration to device [y/n]?
Press y then press Enter key.

Put a sticker on dongle and write the serial number you have assigned.

Unplug, then replug both the dongles
REBOOT RPi

[HF_ATL]

1) Change ENABLED = no to ENABLED= yes
2) Change serial number of dongle 1 from 00000000 to 00000102 by following commands

sudo apt update
sudo apt install rtl-sdr
sudo systemctl stop piaware dump1090-fa dump1090-fa2

rtl_eeprom -d 1 -s 00000102

The last command above will generate lot of output.
The last line of output generated will be:
Write new configuration to device [y/n]?
Press y then press Enter key.

Put a sticker on dongle and write the serial number you have assigned.

Unplug, then replug both the dongles
REBOOT RPi

Since I'm not at the location of the Pi I can't phsically unplug/plug the dongles.
Is there another way of solving this issue without going that route please?
At the moment I have one dongle with SN 0 and the other with SN 1.

Thank you

[abcd567]

Yes there is another way, but not preferable.
Your dongle's current serial numbers (SN) are 0000001 and 00000000 as you showed in your previous post

rtl_test -t
Found 2 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001
1: Realtek, RTL2832U, SN: 00000000

If you cannot modify dongle's serial numbers to match the one in the files /etc/default/dump1090-fa and /etc/default/dump1090-fa2, then change device-index in files to match the dongle's existing serial number.

STEP-1

sudo nano /etc/default/dump1090-fa

Scroll to following line of the file opened:

RECEIVER_OPTIONS="--device-index 00000101 --gain -10 --ppm 0 --net-bo-port 30005"

(1) Change 00000101 to dongle's current serial number 00000001 (caution: make sure that the serial number is 8 digits)
Save and close the file.


STEP-2

sudo nano /etc/default/dump1090-fa2

Scroll to following two lines of the file opened:

ENABLED=no
RECEIVER_OPTIONS2="--device-index 00000102 --gain -10 --ppm 0 --net-bo-port 31005"

(1) Change ENABLED=no to ENABLED=yes
(2) Change 00000102 to dongle's current serial number 00000000 (caution: make sure that the serial number is 8 digits)

Save and close the file.



REBOOT RPI

Check status of both the instances of dump1090-fa

sudo systemctl status dump1090-fa2

sudo systemctl status dump1090-fa

[HF_ATL]

Thanks again for all of your support!


/etc/default/dump1090-fa and /etc/default/dump1090-fa-2 have already index number 00000000 and 00000001 so no change made there. Both have ENABLED=yes

/etc/default/dump1090-fa2 is not there anymore so SN 102 is not an issue anymore.

"sudo systemctl status dump1090-fa" and "sudo systemctl status dump1090-fa-2" show both as active, both running.

Both maps (dump1090-fa and dump1090-fa-2) are showing as expected but no planes in the map.

ip:8754 show FR24 link connected, beast-tcp with the correct ip. Aircraft tracked and uploaded are both showing 0.

[abcd567]

No planes in the map may be due to very few flights in the area due to current Corona Virus epidemic and lock down.
Keep watching map at regular intervals, you may see a plane.

You said:

/etc/default/dump1090-fa2 is not there anymore

"sudo systemctl status dump1090-fa" and "sudo systemctl status dump1090-fa-2" show both as active, both running.

Your statements above are conflicting.
If /etc/default/dump1090-fa2 is not there anymore, then how can sudo systemctl status dump1090-fa-2 can show active?
May be the instance started before you removed /etc/default/dump1090-fa2 is still running.
When you reboot Pi, dump1090-fa2 would fail to start.

To confirm, restart dump1090-fa2, and again check status.

sudo systemctl restart dump1090-fa2

sudo systemctl status dump1090-fa2