Raspberry Pi type B + DVB-T Dongle to feed FR24

[loplo]

Thanks for the heads up, piopawlu

[milair]

At least I know my RPi is rebooting as per Peter's setup, its now up and running again by itself. Just out of interest I wonder how many feeders dropped out ? Surely if it was a largish number someone would have wondered where all the data had gone ??

John

[HermanZA]

Are all the Feeders using either a PI or from a Linux box, able to feed to FR? I am having issues ever since Thursday afternoon. Multiple reboots and checking of settings does not help. Mail to support@fr also not answered yet, neither by a human or a system confirming reception of the mail.


[n]FAKM1@223.27.20.12:8099/TCP
[n]connecting
[n]waiting 90 seconds
[n]FAKM1@83.140.21.66:8099/TCP
[n]connecting
[n]waiting 90 seconds

[Jayant]

Are all the Feeders using either from a PI or from a Linux box, able to feed to FR? I am having issues ever since Thursday afternoon. Multiple reboots and checking of settings does not help. Mail to support@fr also not answered yet, neither by a human or a system confirming reception of the mail.

My Pi feeder connected back automatically once the resolver issue was sorted out. I have it set to reboot twice a day due to unrelated problems with my setup so it reconnected after the next boot.

Best
Jayant


Sent from my GT-I9500 using Tapatalk 2

[Jayant]

I saw a couple of posts here mentioning that the fr24.sh script doesn't put a date stamp on the log entries. There are several ways to do this, but the easiest way is probably to put a tiny bit of inline shell-script into the commandline in the script.

If you change the last line of the script a little (the one which starts fr24feed_arm-le_233s), it should do the trick:

/home/pi/fr24feed_arm-le_233s --fr24key=your_key_goes_here 2>&1 | while read line; do echo $(date +"%d-%m-%y - %H:%M:%S") "$line"; done > /tmp/fr24feed.log &

The bit in bold is the part I've added. It's working on my Pi, but I suggest you backup your working script before playing around, unless you're comfortable with shell scripting.

You can also play around with the format string - it's fairly straight-forward. I've formatted the date string English style, but our US based friends may want to switch %d and %m around :-)

Best
Jayant

[HermanZA]

Brilliant Jayant! Thanks.

[peterhr]

My feed on pi is working well.

Sent from my Nexus 4 using Tapatalk

[Dundee]

Dear ALL,

I just received a FlightFeeder kit from other aviation company which allow me sharing data to other site by providing several Output [Basic AVR / RAW ADS-B (TCP port 30002), SBS/Basestation Format (TCP port 30003)], is that possible for to me sharing data to FR24 here by using raspberry pi only?

Is that OK for me just d/l the image file created by peterhr (like just modify basestation ip of fr24.sh, etc)?
I haven't bought raspberry pi yet but I will if the technical issue is solved...

Regards,
Dundee

[peterhr]

Dear ALL,

I just received a FlightFeeder kit from other aviation company which allow me sharing data to other site by providing several Output [Basic AVR / RAW ADS-B (TCP port 30002), SBS/Basestation Format (TCP port 30003)], is that possible for to me sharing data to FR24 here by using raspberry pi only?

Is that OK for me just d/l the image file created by peterhr (like just modify basestation ip of fr24.sh, etc)?
I haven't bought raspberry pi yet but I will if the technical issue is solved...

Regards,
Dundee

That would work, just have to use fr24feed with a parameters to tell it the port basestation 30003 machine.

Sent from my Nexus 4 using Tapatalk

[HermanZA]

Those of you feeding with a Pi or Linux system, please advise what does your log show:
Are you connected (if applicable) to the FR24 system via TCP or UDP ? Just do: tail -f /tmp/fr24feed.log


[i]FR24Feed v233 - built on Jul 9 2013/11:22:46
[i]Downloading configuration...
02-02-14 - 18:00:01 [i]Removed 0 of 3 AC
02-02-14 - 18:00:01 [b]disconnected
02-02-14 - 18:00:01 [i]waiting 5 seconds
02-02-14 - 18:00:06 [i]Source defined as Basestation
02-02-14 - 18:00:06 [b]connecting to 192.x.x.188:30003
02-02-14 - 18:00:06 [b]connected
02-02-14 - 18:00:06 [b]working
02-02-14 - 18:00:30 [n]FAKM1@83.140.21.66:8099/TCP
02-02-14 - 18:00:30 [n]connecting
02-02-14 - 18:00:30 [n]waiting 90 seconds
02-02-14 - 18:02:00 [n]FAKM1@83.140.21.66:8099/TCP
02-02-14 - 18:02:00 [n]connecting

[T-EDDM2]

UDP....

Gesendet von meinem C6903 mit Tapatalk

[HermanZA]

Do we have any idea how to force the feeder into UDP mode?
Presume that is my problem, mine wants to feed in TCP and not UDP.

[T-EDDM2]

Maybe a preset issue at Fr24? When you look at your logfile you see that it's downloading the configuration. I can't remember a TCP /UDP setting in the Fr24.sh file. I think you should ask the support...

Gesendet von meinem C6903 mit Tapatalk

[peterhr]

[i]FR24Feed v233 - built on Jul  9 2013/11:17:49
[i]Downloading configuration...OK
[i]Parsing configuration...OK
[c]Interval: 5s
[c]Latitude: 52.4xxxx
[c]Longitude: -1.89xxx
[c]GND: YES
[c]NonADSB: YES
[i]Source defined as Basestation
[b]connecting to 192.168.0.132:30003
[e]could not connect to BS
[i]waiting 5 seconds
[n]defined 3 servers
[n]EGBB19@83.140.21.66:8099/UDP
[n]connecting
[n]waiting 13 seconds
[i]Source defined as Basestation
[b]connecting to 192.168.0.132:30003
[b]connected
[b]working
[i]Data feed time difference OK abs(17:17:24.590 - 17:17:24.597)=0
[i]Removed 3 of 3 AC
[n]EGBB19@223.27.20.12:8099/UDP
[n]connecting
[n]connected
[n]switching to UDP
[n]working
[i]sent 6 planes in 1 packets
[i]sent 4 planes in 1 packets
[i]sent 12 planes in 1 packets
[i]sent 13 planes in 1 packets
[i]sent 13 planes in 1 packets
[i]sent 13 planes in 1 packets

[HermanZA]

Well, I am not getting much responce from support@fr24 ever since Thursday.