Open jason0x21 opened 1 year ago
Short version if Ketil is intressed :) I hope he is! I´m not a coder but I do understand docker and scripts.
Use sdr-enthusiasts docker images they are in a separate class and easy to implement. No need to maintain end they have realy good support in their Discord channel.
I´m running this on Pi4 and X86_64 (intel nuc)
If interested I have config for tar1090+graphs with sdr-enthusiasts images :) basic the same method as described below with multifeeder.
Simpel howto:
git clone into local map multifeed, rootsfs folder and docker file is important.
The "run" file in /rootfs/etc/services.d/readsb)/run need the "LONG" changed to "LON" since balena-adsb use LON as Longitude parameter and sdr-enthusiasts use LONG as Longitude parameter or simply add an extra "Device Parameter" LONG same as LON uggly solution but doable.
Then in docker-compose.yml in balena root add: READSB_NET_CONNECTOR and MLAT_CONFIG are super important they are in separate lines ended with ; then choose services to feed, I added all but it simple to remove or add others.
multifeed: depends_on:
Then push to balena :)
Short version if Ketil is intressed :) I hope he is! I´m not a coder but I do understand docker and scripts.
Use sdr-enthusiasts docker images they are in a separate class and easy to implement. No need to maintain end they have realy good support in their Discord channel.
I´m running this on Pi4 and X86_64 (intel nuc)
If interested I have config for tar1090+graphs with sdr-enthusiasts images :) basic the same method as described below with multifeeder.
Simpel howto:
git clone into local map multifeed, rootsfs folder and docker file is important.
The "run" file in /rootfs/etc/services.d/readsb)/run need the "LONG" changed to "LON" since balena-adsb use LON as Longitude parameter and sdr-enthusiasts use LONG as Longitude parameter or simply add an extra "Device Parameter" LONG same as LON uggly solution but doable.
Then in docker-compose.yml in balena root add: READSB_NET_CONNECTOR and MLAT_CONFIG are super important they are in separate lines ended with ; then choose services to feed, I added all but it simple to remove or add others.
multifeed: depends_on: - dump1090-fa image: multifeed build: ./multifeed restart: always environment: - LAT= - LON= - ALT= - READSB_NET_CONNECTOR= dump1090-fa,30005,beast_in; feed.adsb.fi,30004,beast_reduce_plus_out; feed.adsb.one,64004,beast_reduce_plus_out; in.adsb.lol,30004,beast_reduce_plus_out; feed.theairtraffic.com,30004,beast_reduce_plus_out; feed.planespotters.net,30004,beast_reduce_plus_out; data.avdelphi.com,24999,beast_out; - MLAT_CONFIG= feed.adsb.fi,31090,39000; feed.adsb.one,64006,39001; in.adsb.lol,31090,39002; feed.theairtraffic.com,31090,39003; mlat.planespotters.net,31090; expose: - "39000" - "39001" - "39002" - "39003" - "31090" tmpfs: - /run/readsb - /var/log
Then push to balena :)
Hey Thanks so much can you upload the code to github so it just be easy as push it ?? For theairtraffic thanks
Hey Thanks so much can you upload the code to github so it just be easy as push it ?? For theairtraffic thanks
I got it working based on @drhanke's instructions (thanks!), feel free to use this branch: https://github.com/kk-sonata/balena-ads-b/tree/plus-theairtraffic
I'm a git novice but could submit a PR if I can figure it out.
Hey Thanks so much can you upload the code to github so it just be easy as push it ?? For theairtraffic thanks
I got it working based on @drhanke's instructions (thanks!), feel free to use this branch: https://github.com/kk-sonata/balena-ads-b/tree/plus-theairtraffic
I'm a git novice but could submit a PR if I can figure it out.
Thank you soo much it works great
Just one issue seems like theairtraffic not getting my MLAT feed but other website can seems odd
Wow :) happy it worked
Odd with theairtraffic tho, just checked my own feeds and no problem. Guess that this page confirming that no mlat is recieved ? https://theairtraffic.com/feed/myip/
If you select multifeeders log in balena and restart multifeeder, is the log telling any intresting info about connection to theairtraffic ?
getting an error message saying docker-multifeeder [2023/03/29 22:56:38][readsb] ERROR: Not a valid UUID: /usr/local/share/adsbexchange/adsbx-uuid docker-multifeeder [2023/03/29 22:56:38][readsb] Use this command to fix: sudo uuidgen > /usr/local/share/adsbexchange/adsbx-uuid seems odd When i do the command sudo uuidgen > /usr/local/share/adsbexchange/adsbx-uuid it says No such file or directory. i done cat /proc/sys/kernel/random/uuid and did a random number but that error message still shows up
Ah UUID and MLAT_USER is missing, just add in balena "Device Variables". Sorry missed to write about them! My bad :) UUID use same uuid as used to ADSBX or just copy text from console "cat /proc/sys/kernel/random/uuid"
MLAT_USER set to your radarname
Read more about them https://github.com/sdr-enthusiasts/docker-multifeeder
mlat-client: error: argument --lat: expected one argument is the new error
Diffrent forks don´t use same parameters, maybe need to learn gitbub to suggest some more changes so the diffrent containers has the same parameters :)
In the mlat run file changes need to be done to... I run older code, but when I check now they have changed, my code has three different.
/rootfs/etc/services.d/mlat-client/run
MLAT_PARAM+=(--lat "${READSB_LAT}") MLAT_PARAM+=(--lon "${READSB_LON}") MLAT_PARAM+=(--alt "${READSB_ALT}")
change to: (remove READSB) MLAT_PARAM+=(--lat "${LAT}") MLAT_PARAM+=(--lon "${LON}") MLAT_PARAM+=(--alt "${ALT}")
Works great and we are now feeding :) thank you soooo much
Great to hear that you were able to solve this, guys! It's been rather hectic at my end recently, so I have not been able to look into all the new ADSBx clones yet. But I will do it in the future when I have more time available. In the meantime, keep up the great work!
@ketilmo I would be happy to contribute a pr on this and the other service addition requests. But one thing I was thinking is that for any adsb-exchange clones, it maybe doesn't make sense to have very-similar containers per service?
maybe better to just have the single adsb-exchange container, and then populate different env variables which adds additional --net-connector outputs?
For compatible clones, with no additional installation stuff, it probably is not worth the extra bloat/overhead of several identical containers I guess. What do you think?
@shawaj I agree entirely with you, @shawaj. It's the best approach to support the increasing number of ADSBx clones that are appearing and which are all similar in their technical nature. And yes, pull requests are appreciated. 🥳
I've got these all working nicely for adsb. Just adding the MLAT and then will submit a PR 👌
It looks like the ADSB Exchange breakup has splintered in a few places, and adsb.fi is one of them. Could this be added as well as a target? Thanks!