Feed not working after Win 10 upgrade and loading of latest fr24feed application

[marcmcmillin]

Hello all,

I had this same issue and I found a solution that worked for me.

Edit the fr24feed.ini file to include the additional arguments for mr-dump.exe:

receiver="dvbt"

fr24key="75586f4dcf67a3db"

path="mr-dump1090.exe --device-index 1"

bs="no"

raw="no"

logmode="1"

mlat="no"

mlat-without-gps="no"

[johntk56]

I have a problem like this :

Output from mr-dump1090 is

--------------------------------------------------------
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
Found Rafael Micro R820T tuner
Max available gain is: 49.60
Setting gain to: 49.60
Exact sample rate is: 2000000.052982 Hz
Gain reported by device: 49.60
----------------------------------------------------------

Then in one 1 out of 25 it shows traffic
- it is the same result with 2 different dongles
- where do I look for at solution

John

[abcd567]

The solution: include this line on fr24feed.ini. Between Raw and logmode lines

procargs="--device-index 1 --net --net-http-port 8080"

I had the same problem and this solved it

That solution refers to the problem of the update of win10 that prevents fr24feed from working and does not recognize the usb

Good idea to add Parameter --device index 1 in file fer24feed.ini. Easy method. Thanks.

The dump1090 by default connects to device with index 0. In ALL versions of Windows and RPi, DVB-T dongle is allotted device index 0 by default, and dump1090 connect to it without any problem.

Win10 creates a garbage USB with device index 0, and real DVB-T gets device index 1. By default, dump1090 tries to connect to device with index 0, which is a garbage, and fails to connect to it. Adding Parameter --device index 1 in "procargs" changes default behavior of dump1090 and it now connects to device index 1 which is real DVB-T.

An alternative to editing file fr24feed.ini is to add this argument in settings page using a browser.
(1) Type localhost:8754/settings.html in browser's address bar and press Enter key. The settings page will open.
(2) In settings page in field "Process arguments", add argument --net --device index 1
(3) Click "Save" and then "Restart" buttons. Both buttons are at bottom-right corner of settings page.

FR24 Settings via Browser - Win10.png

.
Please note that on settings page in browser, clicking "Save" button saves the new settings in file fr24feed.ini.
If you now open this file in Notepad, you will see the line procargs ="--net --device index 1" added there.

FR24 Settings via fr24feed.ini file - Win10.png

[mariomc112]

That solution refers to the problem of the update of win10 that prevents fr24feed from working and does not recognize the usb

[mariomc112]

The solution: include this line on fr24feed.ini. Between Raw and logmode lines

procargs="--device-index 1 --net --net-http-port 8080"

I had the same problem and this solved it

[abcd567]

How can I use this setup to monitor the information that it receives without looking on the flightradar general map?

There are two ways to do it. Use either Method-1 OR Method-2.

METHOD-1:
Edit file fr24feed.ini and add a new line shown below:
procargs="--net --net-http-port 8080"

Save the file fr24feed.ini, and Restart the fr24feed.exe



.


METHOD-2:
In your browser, type localhost:8754/settings.html and in the blank row "Process arguments" add following entry:
--net --net-http-port 8080

Now click Save button and then Restart button, both at bottom right of the settings page.



.
.
.
TO SEE THE MAP:
After adding "Process Arguments" by Method-1 or Method-2, and restarting the fr24feed.exe, type localhost:8080 in your browser, and the map will display.

[abcd567]

Got it running after I unplugged the device physically. If that has to be done every time something goes down, well then it's just a piece of cheese.

You dont have to unplug-replug the dongle every time. This happens rarely, if the dongle was either not inserted fully, or it was pulled out slightly due to pull by antenna cable.

Often this problem is caused due to more than one instances of fr24feed.exe and mr-dump1090 running in background. In such case, you have to first close ALL instances of these two apps, then restart fr24feed.exe.

Alt+Ctrl+Delete > Task Manager > Details Tab > scroll down to find fr24feed.exe and mr-dump1090.exe, and "End Task" all the instances. Now run fr24feed.exe.

[Oblivian]

I have the "Quality USB 2.0 Digital DVB-T SDR+DAB+FM HDTV Tuner Receiver RTL2832U+R820T2 SCA"

It's running OK since 6 hours. This model has a tiny connector for the antenna. Must figure out its name and build a better antenna for outdoors use.
How can I use this setup to monitor the information that it receives without looking on the flightradar general map?

Mcx or rpsma connectors.

Look in above link for graphical dump1090 output and vrs(virtual radar server)

Sent from my XT1092 using Tapatalk

[AMdinSTratus]

How can you tell its not showing? Because an actual RTL supported device is normally presented to Dump1090 (when drivers loaded) as the correct name


The garbage one is something W10 appears to do to something else USB related that systems come with. And visible when they are present or not.

Sure the one you have isn't overheating or is actually the right sort of device/Chipset?

I have the "Quality USB 2.0 Digital DVB-T SDR+DAB+FM HDTV Tuner Receiver RTL2832U+R820T2 SCA"

It's running OK since 6 hours. This model has a tiny connector for the antenna. Must figure out its name and build a better antenna for outdoors use.
How can I use this setup to monitor the information that it receives without looking on the flightradar general map?

[Oblivian]

It was mentioned somewhere that if the device doesn't show up on the first menu, it's probably already running the right drivers and overwriting them could cause irreversible damage. Should I try zadig on it anyways?
How can you tell that the stick isn't showing? It says that 1 device is found but god knows what those symbols means.

Got it running after I unplugged the device physically. If that has to be done every time something goes down, well then it's just a piece of cheese.

How can you tell its not showing? Because an actual RTL supported device is normally presented to Dump1090 (when drivers loaded) as the correct name
https://forum.flightradar24.com/thre...ll=1#post94712

The garbage one is something W10 appears to do to something else USB related that systems come with. And visible when they are present or not.

Sure the one you have isn't overheating or is actually the right sort of device/Chipset?

[AMdinSTratus]

Got it running after I unplugged the device physically. If that has to be done every time something goes down, well then it's just a piece of cheese.

[AMdinSTratus]

mrdump2.png
As mrDump shuts down the same second it displays the results, it's really hard to printscreen it but this is what I got after running the device through zadig. I actually managed to get it to feed after about 8 pings, then I restarted the program and it's back to the "connection terminated" process.
Just lovely.

[AMdinSTratus]

It was mentioned somewhere that if the device doesn't show up on the first menu, it's probably already running the right drivers and overwriting them could cause irreversible damage. Should I try zadig on it anyways?
How can you tell that the stick isn't showing? It says that 1 device is found but god knows what those symbols means.

[Oblivian]

My PC is doing this also and this issue only occurred after completing a Win10 update. I either try and resolve or roll back the update if possible

Edit: This is now working, since going into Zadig, it shows no devices but can see the USB once 'List all devices' is selected. I'd suggest something in the win10 update cause this to reset.

That'd be why I mentioned use the method

W10 updates both security updates and drivers. Often blacklisting or installing what it thinks your devices need. Which is why Zadig was needed to be re-run on Windows 7 to 10 upgrades. Same thing, major versions are as good as a fresh driver re-check install

[lujoki]

Same problem

Fault with USB stick (it's not even showing ) or drivers already specified

Need to test stick elsewhere or use zadig show hidden device method from their site

Sent from my GT-I9300 using Tapatalk

My PC is doing this also and this issue only occurred after completing a Win10 update. I either try and resolve or roll back the update if possible

Edit: This is now working, since going into Zadig, it shows no devices but can see the USB once 'List all devices' is selected. I'd suggest something in the win10 update cause this to reset.