I just downloaded 1.0.19-14 from the web. I set it up and about 30 minutes the programs crashes. When I say it crashes it gives you that screen that the program has stopped working. Then it gives you the option of either closing it or checking for a solution online. This is on a Win 7 Pro 64 bit machine running a USB Stick. I did install the drivers and the program runs. I guess I should also add that I'm using Zadig 2.3 drivers. I noticed it's crashing after the program updates the time offset. Then it says already locked and asks to close the program or look online.
Announcement
Collapse
No announcement yet.
Program Crashes After About 30 Minutes
Collapse
X
-
Program Crashes After About 30 Minutes
Last edited by devolic1025; 2018-02-04, 20:16.Receiver: FlightAware Pro Stick Plus
Antenna: DPD Productions ADS-B Blade Indoor AntennaTags: None
-
If you have the word localhost in IP address. Try changing to 127.0.0.1 and retest.
If no change, swap to beast instead of avr.
It helps tell them if the localhost bug is in windows port too.Posts not to be taken as official support representation - Just a helpful uploader who tinkers
Comment
-
Originally posted by Rod View PostBut if you are using dump1090.exe receiver-type "beast" make no sense - it should be “avr-tcp”.
Beast type is a data format, not necessarily from a mode-s beast device. And as such another option with mlat tagging included.Posts not to be taken as official support representation - Just a helpful uploader who tinkers
Comment
-
Well of course, we're taking TCP modes having issues by most people here
I thought everyone would figure out my suggestion was Naturally swayed toward beastTCP as the alternate.
If you use the web config its more obvious as the examples are shown and uses dropdown which clearly a USB source would need more fields and not localhost like I suggest adjusting.
But that's the secondary test. My first is to not use the word localhost
It was discovered some time ago on pi (where windows version is spawned from) when it disconnects for inactivity or TCP close, reconnect was failing on different port/format
I use different hardware so some more tests from users need to be done.Posts not to be taken as official support representation - Just a helpful uploader who tinkers
Comment
-
Originally posted by Rod View PostMakes no sense for me.
If you have receiver="beast" in the ini file then fr24feed takes data from USB port and not from the TCP output from dump1090.
reciever="beast-tcp"
host="127.0.0.1:30005"
NOT
receiver="beast"Last edited by abcd567; 2018-02-05, 22:40.
Comment
-
Word has it, Keep an eye on http://feed.flightradar24.com in the next day or so for updated to attempt resolve.Last edited by Oblivian; 2018-02-06, 08:15.Posts not to be taken as official support representation - Just a helpful uploader who tinkers
Comment
Comment