ForeFlight and Stratux both failed today

[denverpilot]

Took a quick trip to PUB today.

Fired up the Stratux at the hangar. Never came up with WiFi. Interesting. Tried a couple of reboots without success. Red LED was lit, green LED was behaving normally like it was indicating disk activity. LEDs on the two receivers were blinking occasionally.

Will hook a monitor and keyboard up and see what's barfing here at home and report back.

Meanwhile went to PUB and on the way back I started a descent from 10,500' going over the top of KCOS into KAPA and chuckled that I had a 178 knot groundspeed. Wheee. Took a picture of it.



Now check this out. Continued in and landed at APA. Look at the info bar at the bottom.



Guess I was still doing 178 sitting in front of the hangar.

Only the Nav info bar at the bottom froze. The rest of the app stayed operational including geolocation.

After restarting Foreflight with a complete kill, back to 0 knots.

 

[denverpilot]

Wrong photo on top. Here's the in flight high speed.

 

[denverpilot]

By the way note even in the in flight photo, the tape shows me through 7900 descending and the bar is already stuck at 9500.

 

[Shawn]

View attachment 44270

That is why we have all of those little round things to the right of your Ipad!

 

[denverpilot]

That is why we have all of those little round things to the right of your Ipad!

Hahaha I was using them, no worries there.

I just find the partial failure of Foreflight interesting.

Stratux I'm not as surprised at that. Haven't had a chance to book up a monitor yet.

 

[EdFred]

Lies! All lies! Apple products are infallible, off to AFB reform for you!

 

[G-Man]

Was it a Stratux error from sending bad data?
Or Foreflight processing and displaying incorrectly?

 

[denverpilot]

Was it a Stratux error from sending bad data?
Or Foreflight processing and displaying incorrectly?

Well, since the Stratux never came up properly and it was left in the car at the airport, I'm kinda doubting it.

(Two *completely separate* tech failures. Re-read. Heh.)

Foreflight's failure was all on its own.

And there's no evidence one way or another that it was Apple code or Foreflight code that has the bug. Just that it's there.

I think Foreflight just couldn't believe a 182 was doing 178 knots groundspeed and it passed out.

 

[denverpilot]

Foreflight bug report submitted. Will see if they need any other data.

Got Stratux hooked up in the identical config to an HDMI monitor and see what it was doing. Boot loop during hardware detection and activation.

On a hunch I unplugged one of the receiver dongles during the loop. Pi booted.

Power draw problem. Pi can't apparently feed two receivers and the wifi dongle (and a USB keyboard but it didn't matter if it was connected or not) enough current and not brown out.

Plugged the receiver back in and it immediately crashed and rebooted. Expected that.

Another hunch. Plugged Pi into the 2.1A output of my battery back instead of a 1A output (which I believe should have been sufficient).

Booted fine.

Now to finish off the troubleshooting properly I'll have to measure the actual current draw on the 1A port, just to see if this battery pack really allows a 1A draw on that port.

But anyway... Stratux is solved.



@murphey weren't you seeing something similar? Make sure you're feeding your Stratux with something that'll let it draw more than 1A of current.