search

cyoung / stratux

Aviation weather and traffic receiver based on RTL-SDR.
BSD 3-Clause "New" or "Revised" License
1.06k stars 362 forks source link

v0.7b3 Web UI traffic page shows nothing #282

Closed GrayFlyer closed 8 years ago

GrayFlyer commented 8 years ago

The status page shows up to 1725 msg (at home), iFly shows 1090 traffic moving, traffic page blank. Both red and green ((ConnectState)) buttons on.

Ergonomicmike commented 8 years ago

First, did you close and/or clear your cache's browser? I didn't get any Traffic in the web UI until I did that.

Had you done any git pulls before upgrading to v0.7b3? I had done an *.sh update from v0.7b2 to v0.7b3 and that didn't entirely work for me. (Even tho I saw v0.7b3 on the status page.) It was because I had done git pulls beforehand and/or also because I had inserted some .go files from AvSquirrel. I had to rename the files I had added and then I did a git pull and everything is working as advertised. (I see the cool new icons in the Traffic page.)

If you still can't get Traffic to display correctly, then I suggest re-imaging back to 0.7b1 and either doing the .sh update or git pull. (But not both.)

Update: As I review this, does the last *.sh update to the latest version of Stratux? Or do users have to incrementally update - first to v0.7b2 and then v0.7b3?

GrayFlyer commented 8 years ago

I cleared the browser cache, and have not done any git pulls. I did upgrade0.7b3 via .sh from 0.7b2 which was via .sh from v0.7b1. What do the red and green ((ConnectState)) buttons both being on mean?

Ergonomicmike commented 8 years ago

I don't know what both red & green mean. There's another guy in the reddit who is reporting the same problem. (But he didn't mention the red/green. Only that he didn't get any traffic.)

I noticed with v0.7b3 that it takes longer for the Traffic page to populate. It's almost like it either has to have enough consistent traffic or perhaps a certain number of targets to get started. I've had to wait a minute or two.

Some browsers and/or OS's are not compatible with the web UI. On my old Nook HD+, running Android JB, I get a message about needing some type of web GL and the GPS page doesn't paint correctly. I presume that you're using the same tablet that you've always used? But if you have another browser or tablet, try that and see what happens. Traffic displays fine for me.

Ergonomicmike commented 8 years ago

If all else fails, I suggest re-imaging to v0.7b1 and then doing git pull to the latest. That's ultimately what I had to do to see the new Target icons.

ghost commented 8 years ago

What do the red and green ((ConnectState)) buttons both being on mean?

It's a sign that one of the scripts is breaking. As @Ergonomicmike says, this will happen with sufficiently old browsers. A page that works fine in Chrome or iOS 9 Safari will completely break on an old Android 2.3 phone or first-generation iPad I have sitting around.

What browser and OS are you running on? Can you copy / paste the user agent string from the bottom of the Logs page?

GrayFlyer commented 8 years ago

Thanks guys! It turned out to be the Dolphin browser. I tried Chrome and the traffic page works just fine. The tablet is a Samsung Tab S, running Android 5.0.2

BTW, I also tried it on my rooted Fire using the Silk browser and it works fine there.

cyoung commented 8 years ago

It was broken for previous version on Dolphin, wasn't it?

GrayFlyer commented 8 years ago

I can't say for sure, but it probably was. I flew v0.7b2 using Silk on my Fire and it was fine, I thought I ran it at home on the Tab S with Dolphin, but maybe not. I've had problems with the Web Ui and Dolphin before, and just forgot to use Chrome. The problem Dolphin is the latest version.

Did you ever fly v0.7b2 with iFly to see if you got the repeated loss of ground stations that I was getting? I haven't flown since, but when I do it will be with b3.

cyoung commented 8 years ago

Haven't tested it yet

Ergonomicmike commented 8 years ago

I flew iFly. (A v9.4 release candidate, IIRC.) No problems.

GrayFlyer commented 8 years ago

I was also flying with a v9.4.x beta connected to my 720 and an Android tablet. They were going in and out of ground link reception together. How many devices were you connected to on your flight?

Ergonomicmike commented 8 years ago

I was flying 63rc1 and had only one tablet (Android) that flight. Planning to fly Wed w/ 65rc2 w/ two tablets. It's on my Test Card to check the Connections page every now & then to see if I get what you got.

GrayFlyer commented 8 years ago 
If you don't already have it selected, there is an ADSB Status
instrument available on iFly and it also pops a banner warning on
loss of ground stations after so many seconds.

On 2/24/2016 1:10 AM, Ergonomicmike
  wrote:

  I was flying 63rc1 and had only one tablet (Android) that
    flight. Planning to fly Wed w/ 65rc2 w/ two tablets. It's on my
    Test Card to check the Connections page every now & then to
    see if I get what you got.
  —
    Reply to this email directly or view
      it on GitHub.
Ergonomicmike commented 8 years ago

(Update: Technically, I think this comment belongs in https://github.com/cyoung/stratux/issues/267. Moderator, feel free to move it.)

Okay, I had my first "GrayFlyer" disconnect message today in iFly. (At least, the first that I've seen.)

To answer @GrayFlyer directly, yes, I have had the ADS-B Instrument up ever since the Stratux.

Today I got your disconnect message. I was descending into a back country airport in the desert SW. (P23, Seligman, AZ.) When I got the disconnect message in iFly's Connection window, it showed two towers, but no Connection. I quickly switched to the Towers page in the Stratux UI. Both towers had a signal strength below 400. (Then down to one tower at 272.) The disconnect message went away when the signal strength came up to 500 for a short time.

Frankly, it might be that this is expected behavior with iFly. Weak signals, no data. (IIRC, the release notes in the v9.4 betas for iFly have mentioned tweaking the ADS-B stuff.) Not quite the same as displaying a disconnect when there are no towers around. More conservative. Unless this happens to me again with a tower booming in, I don't see it as a problem at this point.

(Update: {Update: Wrong. See comment below.} For this flight today, I had also lowered the gain of the SDR's to 42 dB. (6 dB from max.) I did this primarily for the 1090 SDR. But since tgain controls both, I presume the 978 gain might have suffered a bit in the boonies. Although, to be fair, it's unrealistic to expect to receive any towers at 2000' AGL near Seligman. Having said that, I've never seen so much 1090 traffic as today. And still coming in from 50 miles out!)

Ergonomicmike commented 8 years ago

Apparently I am fooling myself that I lowered the gain of the SDR. Axtel4 had asked what my dump-1090 log showed. It reports a max gain of 49.60 and that my gain is set for 49.60. So tgain in sdr.go not working? Or tgain is only affecting the gain of the 978 SDR? (I looked in the uat log for a listing of gain, but did't see anything about it.)

cyoung commented 8 years ago

Old browser issues.