Results 1 to 4 of 4

Thread: Connection Terminated

  1. #1
    Passenger
    Join Date
    Sep 2018
    Posts
    4

    Connection Terminated

    I just recently received and installed a NooElec NESDR Mini 2. I used zadig and installed the dongle with the libusbK driver. I then downloaded and installed fr24feed and the initial setup went just fine but then when I went to launch it again it was giving me connection terminated message. I closed down the app and even went into task manager to make sure everything was shut down and tried it again. Still the same error message. I then tried running it as admin and that didn't help. I restarted my and tried again but still got the same message. My question is what is the device supposed to show up as in device manager and what category is it under?

    Code:
    [main][i]FR24 Feeder/Decoder
    [main][i]Version: 1.0.19-15/generic
    [main][i]Built on Feb  6 2018 10:20:41 (???/Windows/i386)
    [main][i]Running on: Windows10.0
    [main][i]Local IP(s):
    [main][i]Copyright 2012-2018 Flightradar24 AB
    [main][i]Had to remove this line because it contained a link
    [main][i]Reader thread started
    [master][i]Starting processing thread
    [reader][i]Initializing reader
    [time][i]Synchronizing time via NTP
    [httpd][i]Server started, listening on 0.0.0.0:8754
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe  --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [time][i]Time synchronized correctly, offset +2.0214 seconds
    [main][i]Feed Network client started
    [main][i]RAW data server started
    [feed][i]Downloading configuration
    [raw][i]Initializing server
    [raw][i]Starting server on 0.0.0.0:30002
    [feed][c]Interval: 5s
    [feed][c]Latitude: 42.1630
    [feed][c]Longitude: -76.8959
    [feed][c]GND: YES
    [feed][c]NonADSB: YES
    [feed][c]Timestamps: optional
    [feed][c]Max range AIR: 350.0nm
    [feed][c]Max range GND: 100.0nm
    [feed][i]defined 4 servers
    [stats][i]Stats thread started
    [feed][n]KELM1@185.218.24.24:8099/UDP
    [feed][n]connecting
    [feed][n]connected via UDP (fd 980)
    [feed][n]working
    [reader][i]Connection terminated
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe  --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe  --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated

  2. #2
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    4,172
    Run dump1090.exe from same folder, not fr24feed.exe and find the true background error message

    Chances are you need to follow the w10 guide and specify USB device number in command

    Sent from my XT1092 using Tapatalk
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  3. #3
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    4,172
    https://forum.flightradar24.com/showthread.php?p=94712

    Sent from my XT1092 using Tapatalk
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  4. #4
    Passenger
    Join Date
    Sep 2018
    Posts
    4
    Thanks it was Windows 10 picking up an extra device. I used the "--device-index 1" and it worked.

Posting Permissions

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