cyoung / stratux

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

Sporadically stops ignoring own aircraft #848

Open azjoe67 opened 2 years ago

azjoe67 commented 2 years ago
  1. Stratux version: 1.6r1-eu027

  2. Stratux config:

    SDR

    • [ ] single
    • [x] dual

    GPS

    • [x] yes
    • [ ] no type: VK-162 G-Mouse

    AHRS

    • [x] yes
    • [ ] no

    power source: 25,800mAh power brick

    usb cable: Stratux Serial Adapter CP2102

  3. EFB app and version: AvMap EKP-V 1.13.101R

    EFB platform: EKP-V

    EFB hardware: EKP-V connected via RS-232 @ 38,400 baud using the FLARM protocol strings

  4. Description of your issue: All is normal until about 30 - 45 minutes after power on. Then Stratux STOPS ignoring my own aircraft and show it as traffic. I have my HEX code properly inputted in the settings. Sometimes, after a few minutes, it will START ignoring my own aircraft again. Other times it continues to display my plane as traffic right on top of me until I power cycle the Stratux.

I'll gather the logs the next time I go to the hangar.

If possible, enable "Replay Logs", reproduce the problem, and provide a copy of the logs in http://192.168.10.1/logs/stratux/ and http://192.168.10.1/logs/stratux.log.

b3nn0 commented 2 years ago

Yes, please provide the log files. It will be logged if the ownship config ignoring is intentional and why

azjoe67 commented 2 years ago

I didn't realize that those logs are disabled by default. I've enabled them and I'll upload them next time I fly as it has happened every time I fly. Might not be until the end of the week, but stay tuned .....

azjoe67 commented 2 years ago

Maybe a stupid question, but how do you enable the logs? I've turned them on in Settings, but they don't appear anywhere. I've tried using Persistent Logs, but that didn't seem to do anything either. stratux.log exists and is viewable but http://192.168.10.1/logs/stratux/ returns a 404 error.

b3nn0 commented 2 years ago

Persistent logging needs to be on, yes. Then they are under /logs iirc. The file I need is indeed stratux.log. Also, are you flying in the US or somewhere else? (OGN or UAT?)

azjoe67 commented 2 years ago

I'm in the US, Arizona specifically. The EKP-V only understands FLARM when it comes to traffic. (I'm a beta tester for them) I've got 868 disabled, 978 & 1090 enabled. So far seems to be working pretty well. The only real issue I've seen is my "shadow plane" issue. As for the logs, I've got persistent turned on, replay turned on. But when I go into logs, all I see are: auth.log btmp daemon.log fancontrol.err fancontrol.log kern.log lastlog messages private/ stratux.log syslog user.log wtmp

Where's the replay log?

b3nn0 commented 2 years ago

You don't need replay logs to identify your problem. The stratux.log is enough. However, since you are in the US: Do you have ADS-B out? If not, this might just be your own TIS-B shadow. In that case, Stratux can't do anything about it. You would need ADS-B out in that case.

azjoe67 commented 2 years ago

Yes, I have ADS-B In/Out: uAvionix Echo.

OK, It does look like the Stratux.log is being persistent. I see multiple startups in the log. After I fly again and see the problem, I'll post the Stratux.log here.

azjoe67 commented 2 years ago

I've got a bunch of logs, and it did do it again. How do I upload them? I don't see a way to upload.