Page 8 of 71 FirstFirst ... 6789101858 ... LastLast
Results 71 to 80 of 707

Thread: Linux feeder software for Flightradar24 (Old software)

  1. #71
    Passenger
    Join Date
    May 2012
    Posts
    10
    Quote Originally Posted by SR-71 View Post
    Phil21, Anmer,

    first off, many thanks for your support.

    I compiled and started adsbox: it is working at localhost:30003 and showing on its embedded web site several planes.
    Moreover, connecting to the local port 30003, somewhat I guess is the Basestation messages, are shown:

    telnet localhost 30003
    Trying 127.0.0.1...
    Connected to localhost.
    Escape character is '^]'.
    MSG,3,,,471EA5,,,,,,,2450,,,41.89147,12.53118,,,0, 0,0,0
    MSG,5,,,4CA6C0,,,,,,,9600,,,,,,,,,,
    MSG,5,,,471EA5,,,,,,,2450,,,,,,,,,,
    MSG,5,,,3C6469,,,,,,,35000,,,,,,,0,0,0,0
    MSG,6,,,3C6469,,,,,,,,,,,,,6654,0,0,0,0
    MSG,5,,,471EA5,,,,,,,2450,,,,,,,,,,
    MSG,5,,,4CA96B,,,,,,,37000,,,,,,,,,,
    MSG,5,,,4CA8E9,,,,,,,4525,,,,,,,,,,
    MSG,3,,,4CA8E9,,,,,,,4525,,,42.01088,12.40982,,,0, 0,0,0
    MSG,4,,,4CA8E9,,,,,,,,214.0,127.0,,,-384,,0,0,0,0
    MSG,4,,,3C6469,,,,,,,,440.0,181.3,,,-128,,0,0,0,0


    On another window I started the feeder but it seems to me that it is not working:

    export FR24AUTHIP=83.140.247.20 ; ./fr24feed_x86_225 --fr24key=xxxxxxxxxx
    [i]FR24Feed v225 - built on Oct 8 2012/09:28:20
    [i]Downloading configuration...OK
    [i]Parsing configuration...OK
    [c]Interval: 5s
    [c]Latitude: 41.8499
    [c]Longitude: 12.4805
    [c]GND: YES
    [c]NonADSB: YES
    [i]Source defined as Basestation
    [n]ROM1@83.140.247.21:8099/UDP
    [n]connecting
    [b]connecting to localhost:30003
    [b]connected
    [b]working
    [n]waiting 10 seconds
    [n]ROM1@83.140.247.21:8099/UDP
    [n]connecting
    [n]waiting 15 seconds
    [n]ROM1@83.140.247.21:8099/UDP
    [n]connecting

    There is a way to check if the feeder is really working ?

    Edit: getting a trace with tcpdump I can see that the feeder is opening a connection (socket) to 83.140.247.21:8099 but the server i closing it soon after: maybe my key was disabled ?
    Hi all,

    Seem to have the same problem here, the feeder program doesn't succeed in connecting to 83.140.247.21:8099 since yesterday...

  2. #72
    Passenger SR-71's Avatar
    Join Date
    Oct 2012
    Location
    Rome, Italy
    Posts
    10
    Quote Originally Posted by perefouras View Post
    Hi all,

    Seem to have the same problem here, the feeder program doesn't succeed in connecting to 83.140.247.21:8099 since yesterday...
    The same issue has been signaled today even on the Windows feeder thread.

  3. #73
    Captain Anmer's Avatar
    Join Date
    Apr 2010
    Posts
    1,380
    Quote Originally Posted by SR-71 View Post
    The same issue has been signaled today even on the Windows feeder thread.
    Which I think is now fixed?
    Mike


    www.radarspotting.com

    Radarspotting since 2005

  4. #74
    Passenger
    Join Date
    Oct 2012
    Posts
    13
    Hmm. I just got a Mode-S Beast built this weekend, and am working with adsbox for the first time. This is coming from gr-air-modes.

    The device seems to work fine, but ADSBox is giving "junk" data for longitude?

    I'm running it like so:
    root@radar:~/adsbox# ./adsbox --serial /dev/ttyUSB0 --baud 3000000 --lat 45.01 --lon -93.39
    adsbox ADS-B decoder version 20120427.
    LONGITUDE: -93.390000
    Your lat 45.01000 lon -93.39000
    Init database.
    Using /dev/ttyUSB0 as input serial device.
    Run SBS-1 data server on port 30003
    Run HTTP server on port 8080

    It's output is something like: MSG,3,,,A7A25F,,,,,,,4925,,,44.82532,266.92599,,,0 ,0,0,0

    Note the 266.92599 longitude - which is obviously impossible. This seems to happen for *all* airplanes, and is in the ~266.xxx range most/all of the time.

    Any ideas? C is not a language I grok very well, but perhaps something wrong with the a negative longitude being supplied?

    -Phil

  5. #75
    Passenger SR-71's Avatar
    Join Date
    Oct 2012
    Location
    Rome, Italy
    Posts
    10
    Quote Originally Posted by Anmer View Post
    Which I think is now fixed?
    YES ! And indeed my setup as well finally worked !

  6. #76
    Passenger SR-71's Avatar
    Join Date
    Oct 2012
    Location
    Rome, Italy
    Posts
    10
    Quote Originally Posted by Phil21 View Post
    It's output is something like: MSG,3,,,A7A25F,,,,,,,4925,,,44.82532,266.92599,,,0 ,0,0,0

    Note the 266.92599 longitude - which is obviously impossible. This seems to happen for *all* airplanes, and is in the ~266.xxx range most/all of the time.
    Phil,

    looking to the code for "MSG,3" (adsb.c line 507) it seems that homelon is not used in order to compute the field of the message but only to detect values grossly out of range.

  7. #77
    Passenger
    Join Date
    Oct 2012
    Posts
    13
    Quote Originally Posted by SR-71 View Post
    Phil,

    looking to the code for "MSG,3" (adsb.c line 507) it seems that homelon is not used in order to compute the field of the message but only to detect values grossly out of range.
    Thanks SR-71, it got me started in the right direction.

    As someone on the Yahoo groups for the Mode-S Beast pointed out 266 = 360 = -93, which is the correct number I'm looking for. I feel rather stupid for not catching that myself! This is apparently a common error in software written by easterners for easterners, and now exposed to western longitudes.

    In case anyone else runs across this, the simple fix I put in place is at line 548:
    // Testing fix for Western longitudes
    if (rlon > 180) {
    rlon = rlon - 360;
    }

    I'll send this to the author for hopeful inclusion in the next release.

    Thanks!

    -Phil

  8. #78
    Passenger
    Join Date
    Nov 2012
    Posts
    1
    Hello all!

    My linux feeding software stops sending data packets after a while.
    Initialization and first time is ok, but sometime later is nothing in data packets for fr24. Below my logs and capture data.
    Code:
    [i]FR24Feed v225 - built on Oct  8 2012/09:38:58
    [i]Downloading configuration...OK
    [i]Parsing configuration...OK
    [c]Interval: 5s
    [c]Latitude: 51.8100
    [c]Longitude: 39.2200
    [c]GND: YES
    [c]NonADSB: YES
    [i]Source defined as Basestation
    [b]connecting to localhost:30003
    [b]connected
    [b]working
    [n]UUOO1@83.140.247.21:8099/UDP
    [n]connecting
    [n]connected
    [n]switching to UDP
    [n]working
    [i]sent 3 planes in 1 packets
    [i]sent 4 planes in 1 packets
    [i]sent 2 planes in 1 packets
    [i]sent 3 planes in 1 packets
    [i]sent 2 planes in 1 packets
    [i]sent 2 planes in 1 packets
    [i]sent 3 planes in 1 packets
    [i]sent 2 planes in 1 packets
    [i]sent 2 planes in 1 packets
    [i]sent 2 planes in 1 packets
    [i]sent 3 planes in 1 packets
    [i]sent 3 planes in 1 packets
    [i]sent 4 planes in 1 packets
    [n]pinging the server
    [n]disconnected
    [n]waiting 10 seconds
    [n]UUOO1@83.140.247.21:8099/UDP
    [n]connecting
    [n]connected
    [n]switching to UDP
    [n]working
    [n]ping
    [n]disconnected
    [n]waiting 5 seconds
    [n]UUOO1@83.140.247.21:8099/UDP
    [n]connecting
    [n]connected
    [n]switching to UDP
    [n]working
    [n]ping
    [n]disconnected
    [n]waiting 5 seconds
    [n]UUOO1@83.140.247.21:8099/UDP
    [n]connecting
    [n]connected
    [n]switching to UDP
    [n]working
    [n]ping
    [n]disconnected
    [n]waiting 5 seconds
    [n]UUOO1@83.140.247.21:8099/UDP
    [n]connecting
    [n]connected
    [n]switching to UDP
    [n]working
    [n]ping
    [n]disconnected
    [n]waiting 5 seconds
    wireshark dump:
    Code:
    No.     Time        Source                Destination           Protocol Length Info
          1 0.000000    192.168.254.11        83.140.247.20         TCP      74     36614 > http [SYN] Seq=0 Win=5840 Len=0 MSS=1460 SACK_PERM=1 TSval=17019898 TSecr=0 WS=4
          2 0.101861    83.140.247.20         192.168.254.11        TCP      62     http > 36614 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 WS=512
          3 0.101936    192.168.254.11        83.140.247.20         TCP      54     36614 > http [ACK] Seq=1 Ack=1 Win=5840 Len=0
          4 0.102169    192.168.254.11        83.140.247.20         HTTP     149    GET /key.php?key=xxx HTTP/1.1 
          5 0.204623    83.140.247.20         192.168.254.11        TCP      60     http > 36614 [ACK] Seq=1 Ack=96 Win=6144 Len=0
          6 0.208727    83.140.247.20         192.168.254.11        HTTP     955    HTTP/1.1 200 OK  (text/plain)
    ...skip...
         27 5.107349    192.168.254.11        83.140.247.21         UDP      154    Source port: 50884  Destination port: 8099
         28 9.880391    192.168.254.11        83.140.247.21         UDP      186    Source port: 50884  Destination port: 8099
         29 15.207248   192.168.254.11        83.140.247.21         UDP      122    Source port: 50884  Destination port: 8099
         30 19.899268   192.168.254.11        83.140.247.21         UDP      154    Source port: 50884  Destination port: 8099
         31 24.867885   192.168.254.11        83.140.247.21         UDP      122    Source port: 50884  Destination port: 8099
         32 29.887269   192.168.254.11        83.140.247.21         UDP      122    Source port: 50884  Destination port: 8099
         33 34.897004   192.168.254.11        83.140.247.21         UDP      154    Source port: 50884  Destination port: 8099
         34 40.000384   192.168.254.11        83.140.247.21         UDP      122    Source port: 50884  Destination port: 8099
         35 45.110461   192.168.254.11        83.140.247.21         UDP      122    Source port: 50884  Destination port: 8099
         36 49.887028   192.168.254.11        83.140.247.21         UDP      122    Source port: 50884  Destination port: 8099
         37 55.040418   192.168.254.11        83.140.247.21         UDP      154    Source port: 50884  Destination port: 8099
         38 59.967041   192.168.254.11        83.140.247.21         UDP      154    Source port: 50884  Destination port: 8099
         39 64.897060   192.168.254.11        83.140.247.21         UDP      186    Source port: 50884  Destination port: 8099
         40 64.897250   192.168.254.11        83.140.247.21         UDP      62     Source port: 50884  Destination port: 8099
         41 -3532.871830 192.168.254.11        83.140.247.21         TCP      74     52339 > 8099 [SYN] Seq=0 Win=5840 Len=0 MSS=1460 SACK_PERM=1 TSval=17029391 TSecr=0                                        42 -3532.761518 83.140.247.21         192.168.254.11        TCP      74     8099 > 52339 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460 SACK_PERM=1
         43 -3532.761425 192.168.254.11        83.140.247.21         TCP      66     52339 > 8099 [ACK] Seq=1 Ack=1 Win=5840 Len=0 TSval=17029402 TSecr=2653236365
         44 -3532.650661 83.140.247.21         192.168.254.11        TCP      82     8099 > 52339 [PSH, ACK] Seq=1 Ack=1 Win=14592 Len=16 TSval=2653236476 TSecr=17029402
         45 -3532.650611 192.168.254.11        83.140.247.21         TCP      66     52339 > 8099 [ACK] Seq=1 Ack=17 Win=5840 Len=0 TSval=17029413 TSecr=2653236476
    ...skip...
         57 -3502.272797 192.168.254.11        83.140.247.21         UDP      62     Source port: 49516  Destination port: 8099
    UDP packets in range 27-40 contain valid data with aircraft info, but begin from packet 57 and below no more data in it... But in the same time I see that my ADS-B receiver still receive data and success decode packets:
    Code:
    MSG,4,,,424046,,,,,,,,468.0,161.1,,,-64,,0,0,0,0
    MSG,5,,,14A571,,,,,,,30000,,,,,,,,,,
    MSG,3,,,424046,,,,,,,32975,,,50.76228,39.81483,,,0,0,0,0
    MSG,4,,,424046,,,,,,,,468.0,161.1,,,-64,,0,0,0,0
    MSG,5,,,424046,,,,,,,32950,,,,,,,,,,
    MSG,3,,,14A571,,,,,,,30000,,,50.69622,41.72417,,,0,0,0,0
    MSG,3,,,424046,,,,,,,32950,,,50.76107,39.81552,,,0,0,0,0
    MSG,4,,,424046,,,,,,,,468.0,161.1,,,-64,,0,0,0,0
    MSG,3,,,14F10E,,,,,,,13000,,,52.55776,38.87857,,,0,0,0,0
    MSG,5,,,14A571,,,,,,,30000,,,,,,,,,,
    MSG,3,,,424046,,,,,,,32950,,,50.75986,39.81621,,,0,0,0,0
    MSG,4,,,424046,,,,,,,,468.0,161.1,,,-64,,0,0,0,0
    MSG,5,,,424046,,,,,,,32950,,,,,,,,,,
    MSG,3,,,14A571,,,,,,,30000,,,50.69725,41.72211,,,0,0,0,0
    MSG,1,,,424046,,,,,,SBI1045 ,,,,,,,,0,0,0,0
    MSG,4,,,424046,,,,,,,,468.0,161.1,,,-64,,0,0,0,0
    MSG,3,,,14F10E,,,,,,,13000,,,52.55621,38.87894,,,0,0,0,0
    MSG,3,,,424046,,,,,,,32950,,,50.75786,39.81728,,,0,0,0,0
    MSG,5,,,424046,,,,,,,32950,,,,,,,,,,
    MSG,3,,,14A571,,,,,,,30000,,,50.69829,41.72073,,,0,0,0,0
    MSG,4,,,424046,,,,,,,,468.0,161.1,,,-64,,0,0,0,0
    MSG,4,,,424046,,,,,,,,468.0,161.1,,,0,,0,0,0,0
    MSG,3,,,14A571,,,,,,,30000,,,50.70000,41.71867,,,0,0,0,0
    MSG,4,,,424046,,,,,,,,468.0,161.1,,,0,,0,0,0,0
    MSG,4,,,424046,,,,,,,,468.0,160.9,,,-64,,0,0,0,0
    MSG,3,,,14A571,,,,,,,30000,,,50.70067,41.71761,,,0,0,0,0
    What are the problems with my installation? Any suggestions?
    Last edited by wizeman; 2012-11-16 at 08:14.

  9. #79
    Passenger
    Join Date
    Nov 2012
    Location
    Angers(France) LFJR1 devenu T-LFOT5
    Posts
    16
    Hello,

    On linux Ubuntu, I have compiled adsbox with success.

    On term :
    ubuntu1110@ACER:~$ lsusb
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 001 Device 006: ID 07c4:a604 Datafab Systems, Inc.
    Bus 002 Device 002: ID 145f:015e Trust
    Bus 004 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
    Bus 004 Device 003: ID 04fc:05da Sunplus Technology Co., Ltd
    Bus 005 Device 002: ID 046d:08f0 Logitech, Inc. QuickCam Messenger
    Bus 006 Device 003: ID 04d8:000a Microchip Technology, Inc. CDC RS-232 Emulation Demo <--- my MicroADSB

    I tried

    ubuntu1110@ACER:~$ > /dev/ttyACMO
    bash: /dev/ttyACMO: Permission non accordée
    ubuntu1110@ACER:~$ sudo -s
    [sudo] password for ubuntu1110:
    root@ACER:~# echo '#43.02' > /dev/ttyACMO
    root@ACER:~#

    try :
    ubuntu1110@ACER:~/ADSBOX/adsbox$ ./adsbox
    adsbox ADS-B decoder version 20120427.
    Init database.
    Using /dev/ttyS0 as input serial device.
    sbs-1 bind(): Address already in use
    Abandon



    new try

    ubuntu1110@ACER:~/ADSBOX/adsbox$ ./adsbox --serial /dev/ttyACMO
    adsbox ADS-B decoder version 20120427.
    Init database.
    Using /dev/ttyACMO as input serial device.
    sbs-1 bind(): Address already in use
    Abandon

    Where I am wrong ?
    Thank you
    Last edited by speedbird1960; 2012-11-21 at 11:03. Reason: word edit

  10. #80
    Passenger
    Join Date
    Nov 2012
    Location
    Angers(France) LFJR1 devenu T-LFOT5
    Posts
    16
    thank you, speedbird1960

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •