Two feeds in the same Raspberry

[abcd567]

Oblivian:
The FR24 does not provide MLAT results feed back to dump1090 map, so what you said is right.

The FA does provide MLAT results feedback to dump1090 and it is that feedback which will be stopped by FA servers when the detect the user's feed is a combined feed of two or more receivers. The mlat planes will disappear from user's dump1090 map.

[Oblivian]

I think toward resulting data. And how it may effect results/my account.

To me, mlat is a bonus additional thing to supply in some situations, but not a necessity. (Theres always other feeders)
And wouldn't actually send multiple streams of mlat-able info (if at all) from a single location/ip/datasource if there was any chance of adding further jitter delays to one or the other subset of data.

They've said the server uses latest timed standard data in most cases. But the mlat implimentation hasn't been laid out other than the apparent? - it's a lot slower and server side and presumably performed different to the other sites. So how do we know if we are helping or hindering in situations where people are fiddling with multiple mlat (or standard) streams?

I imaging to most feeders other than the errors the status screen produce, mlat would likely be second in line to ensuring they get a free feeding account.

Simplicity over technical workarounds for little gain.

But that's just me. And clearly I'm alone on it.



Sent from my EML-L09 using Tapatalk

[abcd567]

You can't do MLAT with combine data from two dongles.
So two stations with the same coords are actually preferable.

This is exactly the reason which prompted me to develop the method to create & run two completely independent and data-wise isolated stations on same RPi.


OPTION 1 of 2: With dump1090-mutability



OPTION 2 of 2: With dump1090-fa

[wiedehopf]

That is designed for different locations. With different gps coords.

If you have 1 location, the best method is combine the data.

You can't do MLAT with combine data from two dongles.
So two stations with the same coords are actually preferable.

[Oblivian]

Thanks for the info!
I thought that for each account you are given one specific sharing key only.

That is designed for different locations. With different gps coords.

If you have 1 location, the best method is combine the data.

Sent from my EML-L09 using Tapatalk

[abcd567]

I'm not blaming the steps/instructions you wrote. In fact you write step by step much more clearly than what can be seen on other websites or youtube videos. I'm just saying that since there are two different decoders some people will find themselves installing one without removing all traces of the other. This is specially true when you config the system and re-configure it (if you need to add something else like another receiver) at a later stage.

OK, I will add instructions for using a clean image without any previous install, and will also mention that if someone has installed one type of dump1090 and want to switch to the other type of dump1090, he has to write the Raspbian image again.

Writing Raspbian image again is the fool-proof and headache-free method. Even with commands to remove one type of dump1090 is not fool-proof as even with these cleanup commands, something written/installed by script may still remain unremoved, and running the script again will create duplicate entries and failure.

[HF_ATL]

You can have both stations on the same account, just like flightaware.

To get a 2nd sharing key you just run sudo fr24feed --signup with the same email address but without putting in the sharing key you already have.
For FA if you don't have a feeder id configured anywhere, there will be a new one autogenerated which you can claim to add to your existing account.

Thanks for the info!
I thought that for each account you are given one specific sharing key only.

[wiedehopf]

My situation is that I have two different antennas in different locations on my house. To take the most advantage of covering area I decided to use two FR24 accounts. Otherwise I needed to run two Pi's with more energy wasted for no benefit. This way I can contribute more to FR24 feeding.

You can have both stations on the same account, just like flightaware.

To get a 2nd sharing key you just run sudo fr24feed --signup with the same email address but without putting in the sharing key you already have.
For FA if you don't have a feeder id configured anywhere, there will be a new one autogenerated which you can claim to add to your existing account.

[HF_ATL]

The instructions dont juat say "run the bash script". It tells first step is to write a raspbian image, and then run the script.

If people ignore the very first step in the guide,then they should not blame the script or the guide.

I'm not blaming the steps/instructions you wrote. In fact you write step by step much more clearly than what can be seen on other websites or youtube videos. I'm just saying that since there are two different decoders some people will find themselves installing one without removing all traces of the other. This is specially true when you config the system and re-configure it (if you need to add something else like another receiver) at a later stage.

[abcd567]

Most people don't feel the need to run 2 copies or uninstall dump1090. So it only adds to people running it, without knowing the consequences. And making more of a mess

The instructions dont juat say "run the bash script". It tells first step is to write a raspbian image, and then run the script.

If people ignore the very first step in the guide,then they should not blame the script or the guide.

[abcd567]

So do you advise me to run those command lines at this stage?
I've run "sudo rm /etc/lighttpd/conf-enabled/89-dump1090.conf", "sudo systemctl restart lighttpd" only.

No, please now do NOT run the commands I have suggested. These should have been run BEFORE running the 2 receiver script.

And you're right, I had dump1090-mutability before, that's why I got that issue... you really should add those command lines in the step by step tutorial to avoid this issue happening to other users. For anyone who lacks experience in linux environment like me that additional information will make big difference.

The instructions on Github page clearly say step 1 to be "write Raspbian image" and then run the bash script. If this instruction is followed, there will be nothing to remove, and removal commands are not needed.

1) Write Raspbian image to microSD card, enable SSH, enable WiFi (if needed), Power-up

(2) Serialize dongles as follows

(3) Run the following bash command:

[HF_ATL]

Since there is dump1090 mutability and dump1090fa decoders there can be always some mess.
Also not everyone come to a particular thread by the time that they are still in a clean fresh install thus many issues can easily appear for that reason.

Most people don't feel the need to run 2 copies or uninstall dump1090. So it only adds to people running it, without knowing the consequences. And making more of a mess

[Oblivian]

you really should add those command lines in the step by step tutorial to avoid this issue happening to other users. For anyone who lacks experience in linux environment like me that additional information will make big difference.

Most people don't feel the need to run 2 copies or uninstall dump1090. So it only adds to people running it, without knowing the consequences. And making more of a mess

[HF_ATL]

My situation is that I have two different antennas in different locations on my house. To take the most advantage of covering area I decided to use two FR24 accounts. Otherwise I needed to run two Pi's with more energy wasted for no benefit. This way I can contribute more to FR24 feeding.

You can have multiple stations per account on FR24 and FA.

But if it's the same location, another station is probably not required.
No matter enjoy the upgrade on both accounts i guess

[HF_ATL]

So do you advise me to run those command lines at this stage?
I've run "sudo rm /etc/lighttpd/conf-enabled/89-dump1090.conf", "sudo systemctl restart lighttpd" only.
And you're right, I had dump1090-mutability before, that's why I got that issue... you really should add those command lines in the step by step tutorial to avoid this issue happening to other users. For anyone who lacks experience in linux environment like me that additional information will make big difference.

Uninstalling dump1090-mutability leaves out lighttpd config saying /etc/lighttpd/conf-enabled cannot be remove as it is not empty. It also sometimes leaves /usr/share/dump1090-mutability/html because it is not empty.

For this reason I alwasys tell to issue 2 extra commands after removal/purge command, as shown below:

sudo dpkg --purge dump1090-mutability
sudo rm -rf /etc/lighttpd
sudo rm -rf /usr/share/dump1090-mutability

If after above commands, dump1090-fa or dump1090-mut v1.15 is installed, it becomes a clean install without any issues such as faced by HF_ATL
.