b3nn0 / stratux Goto Github PK

1. Stratux version:Stratux Europe Edition 1.6r1-eu018

2. Stratux config:

   SDR

   • single
   • [x ] dual

   GPS

   • [x ] yes
   • no
     type:

   AHRS

   • [x ] yes
   • no

   power source: Battery

   usb cable:

3. EFB app and version: (e.g., WingX Pro7 8.6.2)

   EFB platform: (e.g., iOS 9.2)

   EFB hardware: (e.g., iPad Mini 2)

4. Description of your issue: the aircraft I fly has a built-in PaW, stratux is set up with the ICAO Hex and Pilotaware is set with the same Hex however my own ship is shown as a red target.

is it possible for the own ship filtering to act upon Paw traffic too?

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.

1. Stratux version: 1.6r1-eu019

2. Stratux config: ADSB and UAT SDRs

   SDR

   • single
   • [x ] dual

   GPS

   • [x ] yes
   • no
     type:

   AHRS

   • [x ] yes
   • no

   power source: External Battery

   usb cable: high power

3. EFB app and version: (e.g., WingX Pro7 8.6.2) Foreflight 12.5

   EFB platform: (e.g., iOS 9.2) iOS 13.5.1

   EFB hardware: (e.g., iPad Mini 2) iPad Pro 10.5

4. Description of your issue:
   Would it be possible to connect the Stratux to Foreflight as an X-Plane source knowing that Foreflight receives X-Plane data on UDP port 49002 or 49001? The following official Foreflight link shows that these are the ports used by Foreflight to receive X-Plane data:
   https://foreflight.com/support/support-center/category/about-foreflight-mobile/204115525

Foreflight users have asked for years that Foreflight stops disconnecting the app from the device's cellular network when connected to an ADSB device. For European users, this is essential because we don't have UAT towers to receive weather data in flight but can pick up a cellular signal here and there to update that info. Foreflight when connected to X-Plane maintains cellular connectivity, which would solve all the current problems associated with connecting to a Stratux:
(1) We would get traffic and AHRS from the Stratux
(2) Everything else from the cellular network.

Any guidance would be appreciated and would take your amazing build to a whole new level with IFR pilots in Europe. Thanks in anticipation.

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.

1. Stratux version: stratux-v1.6r1-eu019-52df50d6

2. Stratux config:

   SDR

   • single
   • dual

   GPS

   • yes
   • no
     type: Stratux GPYes 2.0 u-blox 8 GPS unit

   AHRS

   • yes
   • no

   power source: Ekrist Powerbank 26800mAh

   usb cable: Renkforce K-1470 Strom-Kabel Raspberry Pi 1,50m

3. EFB app and version: Foreflight v12.5 (56546)

   EFB platform: iOS 13.5.1

   EFB hardware: iPad Pro (12,9 inches, 3rd generation)

4. Description of your issue:

After updating from eu12 to eu19 Stratux "disconnects" from Foreflight at least several times per flight. WiFi connection is not lost. Rebooting the Stratux resolves the issue. Several minutes later (varying between 2 and 90mins) the disconnect happens again.
I have not changed any of the hardware and the issue never presented itself under eu12 or before that.
I have a feeling (which I cannot prove) that this happens again and again at roughly the same locations (e.g. flying over the Ruhr valley in Germany).

stratuxlog.txt

1. Stratux version:
   stratux-v1.6r1-eu013

2. Stratux config:

   SDR

   • single
   • [ X] dual

   GPS

   • [ X] yes
   • no
     type: TRIG TN72 via FTDI serial<->USB

   AHRS

   • yes
   • no

   power source: 2.1A 5V Samsung charger

   usb cable:

3. EFB app and version: (e.g., WingX Pro7 8.6.2)
   EasyVFR 4.0
   EFB platform: (e.g., iOS 9.2)
   Windows 10
   EFB hardware: (e.g., iPad Mini 2)
   Desktop PC

4. Description of your issue:
   TRIG TN72 GPS not detected. Status window tells me "Serial port (Not communicating)"
   Linux kernel shows FTDI converter recognized and connected as ttyUSB0

Jan 29 12:17:07 raspberrypi kernel: [ 162.530574] usb 1-1.2: Product: AvMap USB Serial Converter
Jan 29 12:17:07 raspberrypi kernel: [ 162.530586] usb 1-1.2: Manufacturer: FTDI
Jan 29 12:17:07 raspberrypi kernel: [ 162.530597] usb 1-1.2: SerialNumber: A7VHM9ZE
Jan 29 12:17:07 raspberrypi kernel: [ 162.542374] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
Jan 29 12:17:07 raspberrypi kernel: [ 162.542634] usb 1-1.2: Detected FT232RL
Jan 29 12:17:07 raspberrypi kernel: [ 162.547323] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0

NMEA output shows when opening ttyUSB0:

pi@raspberrypi:~ $ cat /dev/ttyUSB0
$GPRMC,,V,,,,,,,,,,N,V29
$RAIM,000000,000000,000000,000000,000000,000000,000000,000000,111,0,000000003A
$GPGGA,,,,,,0,00,,,M,,M,,*66
$ACVT,0,,,,,,1C
$GPVTG,,T,,M,,N,,K,N2C

The system does detect a no-brand GPS through a PL2303 converter on the same USB port

1. Stratux version:Stratus Eu 1.6R 021

2. Stratux config:Sdr SoftRF GPS dongle

   SDR

   • [x ] single
   • dual

   GPS

   • [x ] yes
   • no
     type: SoftRF dongle

   AHRS

   • yes
   • [x ] no

   power source:external battery

   usb cable: high power

3. EFB app and version: (e.g., WingX Pro7 8.6.2)
   None: using Android tablet and browser
   EFB platform: (e.g., iOS 9.2)

   EFB hardware: (e.g., iPad Mini 2)

4. Description of your issue:
   I have updated the stratux EU to latest version (1.6R1 021), and the only option I have is the OGN (not connected) while I am using a SoftRF dongle as GPS and traffic receiver on USB port.
   It was working flawlessly with previous version (018).

I am using a SoftRF dongle and baro sensor.
I have tried OGN protocol out on SoftRF, but it is not working either ( only GPS position seems to be taken in account through USB port)

Hope it helps.

Jeremy
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.

Hello @b3nn0,
after our conversation a couple of days ago, I started researching ways to shutdown the system safely.
I don't know how to send an improvement to the repository. In lieu, I created a wiki here.
Anyhow, here is the solution I found .
Although you might not be interested, others may be.

A more direct shutdown method, without the need to access the web interface.

Place the links you need in the home screen of your device (both Android and iOS). The links appear like any other app.

To add the links:

• open the browsers menu
• select "Add to Home Screen"
• assign an appropriate name

When you need to shutdown, simply press on the home screen button and the Stratux will shutdown.

A blank page will open in a browser - this is normal. After a few seconds, the device performs the required function.

Shutdown: http://192.168.10.1/shutdown

Reboot: http://192.168.10.1/reboot

The icons on the home screen act as push buttons triggering the above mentioned commands.

iOS only:

A more elegant way on iOS involves the creation of a custom profile with Apple Configurator loaded with the links and personalized icons.

The profile is then transferred to the device where the icons are then displayed.

Yellow = Reboot / Red = Shutdown

1. Stratux version: Stratux Europe Edition 1.6r1-eu020

2. Stratux config:

   SDR

   • dual

   GPS

   • yes
     type:

   AHRS

   • yes

3. Description of your issue:
   If I go to the webinterface -> settings and enable "868 MHz (Flarm)", change the page to something else and come back, flarm is disabled again. I can do the same for 978 MHz and the change is persistent.

Hi,
Stratux has rudimentary support for SoftRF. This is implemented by

• starting a dump1090 process with --net-only
• reading SoftrRF dump1090 output via Serial, forwarding it to dump19090
• reading traffic from dump1090

This has a couple of drawbacks:

• it interferes with the dump1090 process for the SDRs, so you can only have EITHER a SoftRF connection OR a 1090ES SDR enabled
• We have two GPS in the device, the SoftRF one is ignored for Stratux

Is it worth implementing better Support for SoftRF (especially the T-Beam)?

Benefit:

• We can easily transmit Flarm
• We can also receive OGNTP and PilotAware if desired
• We could use the SoftRF builtin GPS for Stratux
• The second SDR would be free for UAT reception

Drawbacks:

• SoftRFs Flarm reception range seems to be quite a bit worse than the OGN stack with an SDR
• Another PCB - different case is needed (could provide a 3D printable model that fits a Stratux+SoftRF build)

Implementation:
I think it would make most sense to parse the SoftRF NMEA stream instead of the dump1090 stream, as it provides more information.

Another possibility would be to just slightly improve the current support to not start its own dump1090 if we already have 1090ES enabled - so that both work in parallel.

1. Stratux version: 1.5b2-eu010

Foreflight is not displaying attitude information.

I received some questions over time about serial output.
Stratux is already able to dump GDL90 via Serial. However, it only supports the CP2102 USB dongle provided by Stratux, or if you want to use a custom CP2102, you need to change its serial to work with Stratux.

It might be of interest to

• Support more different dongles. From a code perspective, it wouldn't be any different to handle an FTDI or similar (or even the Raspi's serial pins if 3.3v is enough and the AHRS module isn't used)
• Instead of dumping GDL90 via Serial, we might want to make it possible to dump Flarm-NMEA aswell, as some avionics seem to prefer that (which?)

Implementing the first is fairly simple. Add a few udev rules for different dongles to make them available under a well-known location, then open that as our serial port (only one serial supported for the beginning.

Implementing the second is trivial - add a settings switch and a simple if-condition in the serial code to dump Flarm-NMEA instead of GDL90.

Any opinions on this? If you would like to see this, let me know. And also let me know why you want/need this so I get a feeling for the priority. Do you need support for different baud rates?

Spoiler: With a quick try, I was able to easily receive Flarm-NMEA via minicom on a second RasPi, using an FTDI set to 3.3v on the transmitting side and the on-board pins on the receiving side - but it's not userfriendly as of yet. GPS was disconnected here, so coordinates don't show.

i think it would be a good idea if stratux monitored the aerodrome traffic like radar.

• on my latest stratux it's not possible to view the OSM Map (Radar). ->yes stratux ist online with internet. why? ...
• but is it possible to copy a offline map for example map of traffic ciruit etc. ... as overlay? -> this would be nice!
  This would be a feature for a ground station yes, not in the air.

thank's for you great work!

best regards an blue sky,
Karsten

1. Stratux version: Stratux Europe Edition 1.6r1-eu018

2. Stratux config: ADSB and UAT SDRs

   SDR

   • single
   • dual

   GPS

   • yes
   • no
     type: internal

   AHRS

   • yes
   • no

   power source: power source: External Battery

   usb cable: high power

3. EFB app and version: Foreflight 12.4, Skydemon iPad 3.13.6.238 (both latest versions)

   EFB platform: iOS 13.5.1

   EFB hardware: iPad Pro 10.5

4. Description of your issue:
   Hello: I posted this on a closed issue but received no replies, so I deleted my previous post and opened a new one. I did the following steps (copied from the closed issue):
   Edit /etc/network/interfaces
   Type:
   sudo pico /etc/network/interfaces

Inside file uncheck and add:

allow-hotplug wlan1
iface wlan1 inet dhcp
pre-up sleep 5
wpa-ssid your_phone_hotspot_name
wpa-psk your_wifi_password
Edit /etc/sysctl.conf
sudo pico /etc/sysctl.conf

Uncheck line:

net.ipv4.ip_forward=1
Start NAT
sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"
Set Routing over NAT by typing one by one:
sudo iptables -t nat -A POSTROUTING -o wlan1 -j MASQUERADE
sudo iptables -A FORWARD -i wlan1 -o wlan0 -m state --state RELATED,ESTABLISHED -j ACCEPT
sudo iptables -A FORWARD -i wlan0 –o wlan1 -j ACCEPT

Copy Routing into file
sudo sh -c “iptables-save > /etc/iptables.ipv4.nat”

Edit Stratux wifi setting in /usr/sbin/stratux-wifi.sh so it can use copy of routing file that we created every time it restart. In file find lower down:
sudo pico /usr/sbin/stratux-wifi.sh

Find these lines inside file and add one in this place :

sleep 2
wLog "Restaring DHCP services"
/bin/systemctl restart isc-dhcp-server
iptables-restore < /etc/iptables.ipv4.nat # ADD THIS LINE TO SET ROUTING
}

Reboot or shutdown device
sudo shutdown now

I put screenshots of everything I typed in the terminal and the files I modified so you can see that everything in there matches the steps above. The dongle is connected to the internet and I can ping websites from the raspberry pi, but I can not get the internet to be forwarded to my iPad or my android phone when connected to the Stratux Wifi. The pics of the modified files and the steps in the terminal are in the following link:
https://drive.google.com/drive/folders/1-ZDHWY_5nnjk_lGwgUpfz8jxh7gDwn_U?usp=sharing

Any help would be greatly appreciated!

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.

1. Stratux version: Stratux Europe Edition 1.6r1-eu016 EXPERIMENTAL pi4b 2Gb

2. Stratux config:

   SDR

   • single
   • [ x] dual

   GPS

   • [ x] yes
   • no
     type:

   AHRS

   • [x ] yes
   • no

   power source: USB C mains adaptor

   usb cable: yes!

3. EFB app and version: (e.g., WingX Pro7 8.6.2) SkyDemon 3.13.7

   EFB platform: (e.g., iOS 9.2) ios 13.5.1

   EFB hardware: (e.g., iPad Mini 2) Iphone 11

4. Description of your issue:
   While testing the reception of PilotAware (PaW) I was unable to see the PaW unit however the OGN message rate remains 30+ while my PaW is switched on. Checking the logs it shows Invalid Data from OGN multiple times. The ICAO hex is correct 405CA6 is what my PaW is set to.

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
'stratux (1).log'
.

2020/06/03 20:56:08 - Mode-S Distance factors (<5000, <10000, >10000): 2500.000000, 2800.000000, 3000.000000
2020/06/03 20:56:08 - Last IMU read: now, Last BMP read: now
2020/06/03 20:56:08 Invalid Data from OGN: {"sys":"PAW","addr":"405CA6,"acft_type":"8","time":1591214167,"rx_time":0.894,"lat_deg":52.7412529,"lon_deg":0.5501548,"alt_msl_m":24,"track_deg":0,"speed_mps":0.0,"SNR_dB":45.5}
2020/06/03 20:56:10 Invalid Data from OGN: {"sys":"PAW","addr":"405CA6,"acft_type":"8","time":1591214169,"rx_time":0.651,"lat_deg":52.7412529,"lon_deg":0.5501541,"alt_msl_m":24,"track_deg":0,"speed_mps":0.0,"SNR_dB":45.2}
2020/06/03 20:56:12 Invalid Data from OGN: {"sys":"PAW","addr":"405CA6,"acft_type":"8","time":1591214171,"rx_time":0.528,"lat_deg":52.7412453,"lon_deg":0.5501552,"alt_msl_m":24,"track_deg":0,"speed_mps":0.0,"SNR_dB":47.2}
2020/06/03 20:56:13 Invalid Data from OGN: {"sys":"PAW","addr":"405CA6,"acft_type":"8","time":1591214172,"rx_time":1.142,"lat_deg":52.7412453,"lon_deg":0.5501540,"alt_msl_m":24,"track_deg":0,"speed_mps":0.0,"SNR_dB":48.2}
2020/06/03 20:56:15 Invalid Data from OGN: {"sys":"PAW","addr":"405CA6,"acft_type":"8","time":1591214174,"rx_time":0.815,"lat_deg":52.7412453,"lon_deg":0.5501562,"alt_msl_m":24,"track_deg":0,"speed_mps":0.0,"SNR_dB":48.0}
2020/06/03 20:56:15 Invalid Data from OGN: {"sys":"PAW","addr":"405CA6,"acft_type":"8","time":1591214174,"rx_time":0.815,"lat_deg":52.7412453,"lon_deg":0.5501562,"alt_msl_m":24,"track_deg":0,"speed_mps":0.0,"SNR_dB":48.5}

1. Stratux version: v1.6r1-eu019

2. Stratux config:

   SDR

   • single
   • dual

   GPS

   • yes
   • no
     type: External USB u-blox 8 GNSS

   AHRS

   • yes
   • no

   power source: powerbank

   usb cable:

3. EFB app and version: (e.g., WingX Pro7 8.6.2)

   EFB platform: (e.g., iOS 9.2)

   EFB hardware: (e.g., iPad Mini 2)

4. Description of your issue:
   This is a known issue discussed on reddit already. There is a problem with calibrating the new AHRS V2.0 sensors. The error message when trying to calibrate is:

Set AHRS Sensor Orientation: Failed!
There was an error: couldn’t read accelerometer: couldn’t determine biggest accel from 0.000 0.000 0.000
The orientation failed. Please try again.
<<<

There is an update for the cyoung-Stratux-version found at http://updates.stratux.me/builds. It will be rolled into the main image shortly. I would highly appreciate, if this update could be implemented into the European Version as well.

panic: embd: your host ": ARMv7 Processor rev 3 (v7l)" is not supported at this moment. request support at https://github.com/kidoman/embd/issues

Hi

Anyone know how to fix in a RPi 4b?

The file /web/img/world.png fills the mediterranean sea and the baltic sea with the 'land' - color so it appears as a land mass. Accordingly it shows up in the GPS view.

Moin.

Just installed your latest version 'Stratux Europe Edition 1.5b2-eu002' and change the UDP/IP for AirNav Pro use. https://github.com/0sander/stratux_air_nav_pro
Like it very much, especially the radar option in the web-interface.

But.. the FLARM option is not working... (I've enabled the option on the setting page).

And if I test the latest release of PepperJo 'stratux-v1.5b2-flarm-fe12ed3.zip', FLARM is displayed in the Traffic list (green).

Maybe I did something wrong?

So I could use PepperJo's image but I like the other options you give.

Hope you can help me out with this problem :-)

It would be great if one could update to a new release using the web interface of stratux.
If I understand correctly, the update shell script in the releases should be usable for that, correct?

If you think this is a useful feature and give me some pointers for how to implement it, I would also be willing to contribute.

In the original Stratux repository, there is a lengthy discussion from 2017 regarding Flarm-NMEA output:
cyoung#489
aswell as initial work done:
cyoung#560

While this seems not entirely needed these days, since most EFBs now support GDL90, I want to discuss if bringing these patches to a usable level in modern Stratux would still be worth it?
From the discussion, I take that Flarm-NMEA supports bearingless targets (which GDL90 does not) and this actually seems to be implemented in many EFBs.

• Is it still the case that SkyDemon can only work with FLARM if it is present under 192.168.1.1?
• How about using a different protocol? What does PilotAware's protocol offer and is it documented? Or any other that might be useful?

Feel free to discuss...

The beta implementation of the X-Plane interface for Garmin Pilot worked quite well for me.

Can you implement the interface in the normal version?

1. Stratux version: 1.6r1-eu013 (45f6549)

2. Stratux config:

   SDR

   • single
   • [ ✓] dual

   GPS

   • [✓ ] yes
   • no
     type:vk162

   AHRS

   • ✓ yes
   • no

   power source: external battery

   usb cable:

3. EFB app and version: (e.g., WingX Pro7 8.6.2)
   Foreflight 12.1.1 and Skydemon
   EFB platform: (e.g., iOS 9.2)
   iOS 13.3.1
   EFB hardware: (e.g., iPad Mini 2)
   iPad air (3rd generation)

4. Description of your issue:
   Traffic is shown in Skydemon, but at the same time the device is not found in Foreflight and therefore no traffic is shown. The original Stratux version provides traffic to foreflight without problem.

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.

1. Stratux version: 1.6r1-eu021

2. Stratux config:

   SDR

   • single
   • dual

   GPS

   • yes
   • no
     type: u-blox NEO-M9N connected to ttyAMA0

   AHRS

   • yes
   • no

   power source: 2A wall adapter

3. Description of your issue:
   I am trying to bring up my NEO-M9N at the native ttyAMA0 port. Generally it is working, but is not recognized as a u-blox module and thus is not configurated like it should be. I mean thinks like update raten and all the other u-blox features that the "normal" GNSS modules don't have.

What I have tried to do:
Since connecting the NEO via USB creates a symbolic link ttyACM0 -> ublox9, I tried to create this link manually while having connected the NEO to the ttyAMA0. That let stratux think a NEO-M9N module has been connected (see gps.go; line 218). The further reconfiguration seems to work online on the USB port, but not on the ttyAMA0. I have compare the configurations from line 355-374 (file gps.go) to my settings in u-center. All seems to be identical.

I ran a little test.
First, stopping stratix via stxstop. Then I connected my NEO-M9N via USB. The symbolic link to ublox9 has been created automatically. Then I started "cat /dev/ublox9" and got the following output:

$GBGSV,1,1,00,1*76

$GNGLL,,,,,,V,N*7A

$GNRMC,,V,,,,,,,,,,N,V*37

$GNVTG,,,,,,,,,N*2E

$GNGGA,,,,,,0,00,99.99,,,,,,*56

$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99,1*33

$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99,2*30

$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99,3*31

$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99,4*36

While catting, I started stratux via "stxstart". The n9n has been detected and reconfigured immediately so that the cattting output changed to:

$PUBX,04,000033.00,101119,33.00,2079,18D,0,0.000,1666
$PUBX,03,05,1,-,,,16,000,2,-,,,18,000,3,-,,,08,000,4,-,,,15,000,6,-,,,13,00036
$PUBX,00,000033.20,0000.00000,N,00000.00000,E,0.000,NF,5303301,3750000,0.000,0.00,0.000,,99.99,99.99,99.99,0,0,028
$PUBX,00,000033.30,0000.00000,N,00000.00000,E,0.000,NF,5303301,3750000,0.000,0.00,0.000,,99.99,99.99,99.99,0,0,029
$PUBX,03,05,1,-,,,16,000,2,-,,,17,000,3,-,,,08,000,4,-,,,15,000,6,-,,,13,00039
$PUBX,03,05,1,-,,,16,000,2,-,,,17,000,3,-,,,08,000,4,-,,,16,000,6,-,,,13,0003A
$GNGGA,,,,,,0,00,99.99,,,,,,56
$PUBX,00,000033.50,0000.00000,N,00000.00000,E,0.000,NF,5303301,3750000,0.000,0.00,0.000,,99.99,99.99,99.99,0,0,02F
$PUBX,03,05,1,-,,,16,000,2,-,,,17,000,3,-,,,08,000,4,-,,,16,000,6,-,,,13,0003A
$PUBX,03,04,1,-,,,15,000,2,-,,,17,000,3,-,,,08,000,6,-,,,13,00016
$PUBX,03,04,1,-,,,15,000,2,-,,,17,000,3,-,,,08,000,6,-,,,13,00016
$PUBX,03,04,1,-,,,15,000,2,-,,,17,000,3,-,,,08,000,6,-,,,13,00016
$PUBX,03,04,1,-,,,15,000,2,-,,,16,000,3,-,,,08,000,6,-,,,13,000*17
$GNGGA,,,,,,0,00,99.99,,,,,,*56

I think the problem is, that when I fake a USB-connected module by manually creating the symlink "ublox9", stratux is reconfiguring the module and then waiting for messages that are only send via the USB output of the NEO and not the UART.

How to deal with that issue ?
One solution would be a simple textbox next to GSP on/off switch under Settings -> Hardware where the device can be configured. If I connect the NEO via USB, it would be "/dev/ublox9". By connecting via the native serial port I could change it to "/dev/ttymAMA0" and stratux would configure the module in that way that the correct message output would be pushed through the NEOs UART.

In the latest version the OGN Device DB is incorporated which is another great feature. What procedure shall be used for updating this database?

1. Stratux version:Stratux Europe Edition 1.6r1-eu013 with fix for issue #47

2. Stratux config:

   SDR

   • single
   • [x ] dual

   GPS

   • [ x] yes
   • no
     type: stratux internal

   AHRS

   • [x ] yes
   • no

   power source: Battey

   usb cable: Short 150mm

3. EFB app and version: (e.g., WingX Pro7 8.6.2)

   EFB platform: (e.g., iOS 9.2) IOS13

   EFB hardware: (e.g., iPad Mini 2) iphone 11

4. Description of your issue:
   In both Skydemon and on the stratux traffic page the the ICAO Hex address is shown but not decoded / looked up to display the Registration / tail number.

2020/06/06 21:43:05 GPS attitude: Average delta time is 0.10 s (9.8 Hz)
2020/06/06 21:43:05 New message: $GPRMC,204305.30,A,5244.45526,N,00033.00686,E,0.6,257.3,060620,,,A55
2020/06/06 21:43:05 New message: $GPGGA,204305.30,5244.45526,N,00033.00686,E,1,5,1.00,6.4,M,45.8,M,,6F
2020/06/06 21:43:05 New message: $GPGSA,A,3,,,,,,,,,,,,,1.0,1.0,1.033
2020/06/06 21:43:05 FLARM - ICAO target 405CA6 (405CA6) is 70.6 meters away at 277.9 degrees
2020/06/06 21:43:05 New message: $PFLAA,3,9,-69,1,1,405CA6!405CA6,0,0,0,0.0,859
2020/06/06 21:43:05 New message: $PFLAU,1,1,2,1,3,-82,2,1,70*71
2020/06/06 21:43:05 stats [started: 16 minutes ago]
2020/06/06 21:43:05 - Disk bytes used = 2.1 GB (29.1 %), Disk bytes free = 5.2 GB (70.9 %)
2020/06/06 21:43:05 - CPUTemp=49.39 [27.87 - 54.23] deg C, MemStats.Alloc=3.1 MB, MemStats.Sys=20 MB, totalNetworkMessagesSent=394
2020/06/06 21:43:05 - UAT/min 0/0 [maxSS=0.00%], ES/min 1/1, Total traffic targets tracked=1
2020/06/06 21:43:05 - Network data messages sent: 0 total, 0 nonqueueable. Network data bytes sent: 0 total, 0 nonqueueable.
2020/06/06 21:43:05 - Last GPS fix: now, GPS solution type: 1 using 5 satellites (8/22 seen/tracked), NACp: 9, est accuracy 11.00 m
2020/06/06 21:43:05 - GPS vertical velocity: 0.46 ft/sec; GPS vertical accuracy: 22 m
2020/06/06 21:43:05 - Mode-S Distance factors (<5000, <10000, >10000): 2500.000000, 2800.000000, 3000.000000

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.

1. Stratux version: v19

2. Stratux config:

   SDR

   • single
   • [X ] dual

   GPS

   • [ X] yes
   • no
     type:

   AHRS

   • [ X] yes
   • no

   power source:
   stable certified Raspberry PowerSupply

   usb cable:

3. EFB app and version: (e.g., WingX Pro7 8.6.2)
   ForeFlight

   EFB platform: (e.g., iOS 9.2)

   EFB hardware: (e.g., iPad Mini 2)

4. Description of your issue:
   Hi I can not enable the Flarm option any more, as soon as I leave the page, it got disabled again.
   The "raw" config file does not change as well.
   Changing the 1090 and 978 Options to on or off works.

Version 15 was ok, there was a "Flarm" option in the "raw" config as well, later versions it is missing

For tracking and anti-collision purposes I am having on board FLARM/OGN device together with Stratux and Mode S transponder. I realized, I can file FLARM/OGN hex code on the field for mode s transponder hex code and it works the same way (particular device is not send as nearby traffic). Would be possible in the future release increase number of devices instead of one?

The last couple of versions were based on an original Stratux image.
I.e. a script fetched the latest Stratux image, checked out the European version from git, installed it and that's it.
However, the base of the original Stratux image (Raspbian Jessie) is quite ancient by now.

I've done some tests and see no reason why we should stick with such an old version. I've created a Stratux Image that is based on the most recent Raspbian Stretch image and it works quite well.

Benefits:

• more control of what is on the image
• Raspberry PI 3b+ support (not supported by Jessie)
• better future-proofing
• Possibly better drivers and firmware

Risks:

• Maybe some consequences I don't see yet? In my tests, it all looked good.
• Limited upgradability: The newer Stratux upgrade files (.sh scripts) will still work on the older images. However, they can of course not upgrade the Raspbian base image, just the Stratux software. This means there will be more variance in the software that people are running. Some will have done a clean install of the new Raspbian base, some will be on an old Jessie Stratux that has been upgraded to the latest Stratux code.
• Possibly more testing of update files needed against both base system versions (or deprecate the old one as "unsupported but probably working")

Some things need to be evaluated: https://github.com/b3nn0/stratux/wiki/RaspberryPI-3-b---Testing (anyone using a Stratux with OLED screen?)

My opinion: either go for it, or wait for the new Buster release and go with that (Debian Buster will likely be released in July, Raspbian will likely follow 2-3 months later, I would guess).

What are your opinions about this?

Hi,
again, I'm looking for opinions:
Personally, I do not like the fact that I have to connect to the Stratux Wifi hotspot for the system to work.
Reasons:

• Android devices will not be able to connect to the internet via mobile network simultaneously
• iOS devices can, but it requires changing the DHCP configuration on the Stratux via SSH
• The Stratux, in practice, never has an internet connection (except if people take it home and connect it via ethernet)

Motivation for other connection options:

• EFB devices can keep their internet connection via mobile network
• the stratux could potentially use that same internet connection during flight, to potentially do a ton of nice things:
• We could connect to an Mlat service (e.g. adsbexchange or something) and fetch mlat traffic from there and publish it via GDL90/Flarm-NMEA
• We could potentially fetch weather over the internet and therefore simulate UAT-WX
• We could potentially enable easier online updates or update notifications

Possible implementations:

• Wifi tethering
  the Stratux connects to it as a client. I personally already do it this way, but it's not a simple configuration. Getting the implementation right is probably difficult.
• Bluetooth connection:
  The Pi3 already has bluetooth on-board. However, most EFBs will not accept GDL90 via BT directly. Could we convince EFB manufacturers to implement this?
• Bluetooth Tethering
  That should probably work the best. We still use sockets for communication, so the EFB should be easily compatible. So my vote would be for this, if it is possible.

Challenges:

• BT tethering is probably not exactly straight forward, especially with respect to pairing, etc. It will require significant work.
• Additionally, i'm not sure if it is possible to set the IP Address for the Stratux to 192.168.1.1, as some EFBs require it for Flarm-NMEA. GDL90 should work just fine.
• Since we are not the DHCP provider any more, we need to have a different mechanism for discovering the clients that should receive GDL90. This should be doable by reading the ARP table - that's probably enough.

EDIT:
I have done some tests. Connecting via Bluetooth PAN (tethering) works quite well, the network speed is absolutely fast enough for our purpose.
BUT: The raspberry's BT/WiFi chip is a mess.
Using only BT OR WiFi works just fine. But if the Wifi hotspot is running, the bluetooth connection becomes quite unstable and is dropping regularly when there is not a constant data stream sent over bluetooth. Quite annoying.

1. Stratux version: stratux-v1.6r1-eu016

2. Stratux config:

   SDR

   • single
   • [x ] dual

   GPS

   • [x ] yes
   • no
     type:

   AHRS

   • [x ] yes
   • no

   power source: Anker 10000

   usb cable: standard

3. EFB app and version: Skydeamon

   EFB platform: Android
   EFB hardware: Huwaei M5

4. Description of your issue:

Hi
With new update I decided to buy TTGO T-beam board and BMP280 as would like to try it out. Don't think many people has done such an upgrade so guide is no were to be found. Can you shed some light how to get this working together? I presume t-beam need to be loaded with OGN tracker, than pairing it with BMP280? . Will it just work after plugin into stratux usb.....well i think it need a bit of tweaking?

Any sugesstions will be great!

• Set the a secend ip adress to the wlan0 interface (192.168.1.1/24 command "ifconfig wlan0:1 192.168.1.1/24"). i have add the command to the script /etc/rc.local
• change the dhcp server settings
  the answer with the network setting:
  ipadresse 192.168.10.X with network mask 255.255.0.0

you can use the stratux with foreflight (GDL90) and skydemon (FLARM with AIRCONNECT) with out change the setting.

1. Stratux version: 1.5b2-eu008 BETA

2. Stratux config:

   SDR

   • single
   • dual

   GPS

   • yes
   • no
     type: u-blox 8

   AHRS

   • yes
   • no

   power source: -

   usb cable: -

3. EFB app and version: SkyDemon
   EFB platform: Android 9
   EFB hardware: Nokia 6

4. Description of your issue:
   Traffic relative altitudes are ok if I'm using GDL90 and MSL altitude in stratux settings. If I'm using FLARM with AirConnect in SkyDemon, FLARM targets are shown as as too high (today +300ft @ QNH 1018). ADS-B targets are fine. Looks like a sign error in FLARM-NMEA code to me.

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.

GDL90

FLARM-NMEA

Traffic Page

Pressure Altitude

GPS Page

Description of your issue:
Hello, I have been testing new release (eu18) and I am having two issues with OGN/FLARM reception.

1. Relative altitude is showed wrong on OGNs with baro sensor (OK-YUL 02 showing 425ft instead of 800-900ft, the other one 24A8F0 is SoftRf device with only GPS source and the altitude is correct 900ft)
2. HEX code filtering do not work if the device is in OGN database, if it is not in the database filter is ok.

Please see atached pictures one is version eu13 and the second one eu18 with the some conditions.

1. Stratux version: 1.6r1-eu021
2. Stratux config:
   SDR
   • single
   • dual
     GPS
   • yes
   • no
     AHRS
   • yes
   • no

Questions and Suggestions:
I apologise if some questions/suggestions/issues are obvious or have already been discarded.
Not sure about the feasibility, but anyway, they would make it an almost perfect product, totally autonomous as well.
.

Reception, Decoding and Displaying:

• it would greatly help to have a diagram containing all the steps the information go through from reception to being displayed/relayed.
• apart from ADS-B, does it receive and decode pure FLARM, OGN or OGN-R?
• Bearingless targets - working criteria?
  .

FLARM/OGN data:
Is it displayed together with ADS-B in Foreflight?
.

Traffic advisories:

• Add support for a mini speaker and output of Radar page sound.
• Add support for a mini display / led indicator much like a FLARM .
  .

Shutdown:

• more convenient shutdown command - linkable button to iOS home screen (like a bookmark that when pressed issues the shutdown command)?
• even better, support for a push switch (not to cut power, but to issue the shutdown command)
  .

Explanation/Help menus

• Improve explanation/help menus, especially regarding EU-specific functions and toggle buttons action.
• what are those sources marked with only a letter "e"?
  .

Ownship:
drop down menu for multiple HEX, only one active at a time (fleet) - same issue at cyoung/stratux, not relying on software to hide crucial information
.

Update script
Does the update .sh file only affects the Stratux services or does it overwrite any changes to the OS? (root pwd, wifi config)
.

Stat. page:
It would be useful/interesting to have access to some graphs regarding the Rpi status, particularly regarding Temperature and fan operation.
Something along the line of either:
https://github.com/jprochazka/adsb-receiver/wiki/Performance-Graphs
https://github.com/XavierBerger/RPi-Monitor
.

WiFi:
WPA2 instead of WPA (or is it because WPA2 requires more resources?)
.

Internet connection - is the following correct?

• Smart WiFi toggle - I could only find this reference and nothing more, does this apply to Stratux as well?
  "Stratus 3’s Smart WiFi feature, it’s telling the iPad that while WiFi is being used for short range data transfer, there is no internet connection. That allows the iPad to use its internal LTE radio (if available) while staying connected to Stratus."

• Multiple WiFi sticks - WiFi client mode
  . Raspberry Pi as passthrough for Internet data + inject Stratux data:
  . I am only worried about this:
  . . - Application expecting Flarm-NMEA ... - what issue might it cause, say in Foreflight? Isn't stratux configured merge ADS-B and OGN/FLARM data in a single stream?
  . . - Update may wipe everything?

1. Stratux version: Stratux Europe Edition 1.6r1-eu016 EXPERIMENTAL

2. Stratux config: ADSB and UAT SDRs plus a SoftRF USB Dongle

   SDR

   • single
   • [x ] dual

   GPS

   • [x ] yes
   • no
     type:

   AHRS

   • [x ] yes
   • no

   power source: External Battery

   usb cable: High load

3. EFB app and version: Foreflight 12.4, Skydemon iPad 3.13.6.238 (both latest versions)

   EFB platform: iOS 13.5

   EFB hardware: iPad Pro 10.5

4. Description of your issue: Stratux Europe Edition 1.6r1-eu016 EXPERIMENTAL does not show traffic at all in Foreflight, but works fine with Skydemon. The previous version of Stratux software works fine with both Foreflight and Skydemon. Skydemon shows ghost aircraft warnings with both codes for mode S and SoftRF dongle transmitter entered into the Stratux software (not specific to the latest version of Stratux software).

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.

I looks like, that the FLARM targest are not shown on the nice Web-Radar from TomBric.

At least one EFB (EasyVFR4) is able to receive traffic information from GDL90 and FLARM protocols at the same time. For bearingless targets, it creates doubled targets. It also shows dummy aircraft, even if the EFB is able to receive FLARM messages - which as I understand from previous discussions are better than GDL90.

It would nice if Stratux had a switch to limit output protocol (GDL90 or FLARM) at least for traffic information.

Hi!
I can't get AirNAV Pro ATTITUDE to work with Stratux EU edition. Works perfect with non EU Stratux.
Since version 1.4 when upload image with flarm capability can't use AHRS data.

@b3nn0

Please check the diagram.

I created a wiki, if there is an error, let me know and I will rectify it.

Unfortunately, there is no other way to contact you directly.

Thanks.

Stratux EU receives data from the following systems:

• Mode A/C (no position)

• Mode S

• 1090 MHz ADS-B ES

• 978 MHz UAT ground stations (TIS-B + FIS-B Wx, if enabled, US only, require a 3rd SDR)

• OGN

• FANET

• PAW

Stratux EU acts in a similar fashion to an OGN ground station, but airborne, decoding the "messages" locally.

"It receives any of the relevant protocols on the 868Mhz band, including everything that OGN receives + FANET + PilotAware."

No use of OGN-R is made.

These are ideas for features. Should any of you be interested in pursuing any of the feature below, please feel free to do so.
I must mention that I am not sure about the feasibility of such ideas.
Apologies if some points have already been discarded or implemented.
Please, correct me if I wrote something which is not correct.
.

Reception, Decoding and Displaying:

• diagram containing all the steps the information go through from reception to being displayed/relayed.
  .

Signals received

• Stratux acts in a similar fashion to an OGN ground station, but airborne.
• It receives OGN "messages", decodes them locally and merge them into the data output.

.

Traffic advisories:

• Add support for a mini speaker and output of Radar page sound.
• Add support for a mini display / led indicator much like a FLARM [Or just use a SoftRF SkyView].
  .

Shutdown & Reboot:

• support for a physical push switch (not to cut power, but to issue the shutdown command)
  .

Shutdown & Reboot from device home screen - Already working - see my wiki at cyoung/stratux:

• Link the following URLs to your device home screen to allow for easy shutdown:
  Shutdown: http://192.168.10.1/shutdown
  Reboot: http://192.168.10.1/reboot
  .

Explanation/Help menus

• Improve explanation/help menus, especially regarding EU-specific functions and toggle buttons action.
• what are those sources marked with only a letter "e"?
  .

Stat. page:

• Useful/interesting to have access to some graphs regarding the Rpi status, particularly regarding Temperature and fan operation.
• Something along the line of either:
  https://github.com/jprochazka/adsb-receiver/wiki/Performance-Graphs
  https://github.com/XavierBerger/RPi-Monitor
  .

Multiple WiFi sticks - WiFi client mode

• Raspberry Pi as passthrough for Internet data + inject Stratux data
• permanently add the function, better if toggled via the interface.

1. Stratux version: stratux-v1.6r1-eu015-27843b2e

2. Stratux config:

   SDR

   • single
   • [x ] dual

   GPS

   • [x ] yes
   • no
     type:

   AHRS

   • [x ] yes
   • no

   power source: anker

   usb cable:

3. EFB app and version: (e.g., WingX Pro7 8.6.2)

   EFB platform: (e.g., iOS 9.2)

   EFB hardware: (e.g., iPad Mini 2)

4. Description of your issue:

Hi all

Iam not able to configure my usb wifi dongle. Has been using stratux as pass thru internet dev and wifi usb connecting to my phone. i was working fine on older versions but since direct wifi added it stopped. USB wifi D is beeing seen by stratux as iwconfig is showing wlan1 present. Wpa_supplicant.conf has been filled with correct details, routing tables has been set ,NAT also set ,but like shown below wlan1 is failing when ifup function is run.

If i run "ifup" on wlan1 it gives:

sudo ifup wlan1
wpa_supplicant: /sbin/wpa_supplicant deamon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
ifup:failed to bring up wlan1

In /etc/network/interface I did unchecked and edited as usual:
allow-hotplug wlan1
iface wlan1 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Also it might be worth adding in future versions as i think a lot of people have tablet without internet ,but has a mobile that can run hotspot.

thanks
Mike

1. Stratux version: https://www.amazon.com/gp/product/B01LZTZ06C/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
   I replaced the low power SDR with the older version to work with the FLARM build

2. Stratux config: Stratux Europe Edition 1.6r1-eu013

   SDR

   • single
   • dual

   GPS

   • yes
   • no
     type: internal GPYes WAAS GPS receiver

   AHRS

   • yes
   • no

   power source: External battery

   usb cable: High load

3. EFB app and version: Foreflight latest version 12.2.1 (e.g., WingX Pro7 8.6.2)

   EFB platform: iOS 13.4.1 (e.g., iOS 9.2)

   EFB hardware: iPad Pro 10.7 inch (e.g., iPad Mini 2)

4. Description of your issue:
   I connected a preconfigured SoftRF USB dongle with GPS and FLARM NMEA in. I can see OGN traffic in the Stratux software radar but not in Foreflight. Is there a way to make OGN traffic visible in Foreflight? Thank you so much for your great contributions to the European GA community!

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.

1. Stratux version: v1.6r1-eu021

2. Stratux config:

   SDR

   • single
   • dual
     978Mhz and 1090Mhz

   GPS

   • yes
   • no
     type: Internal u-blox 8

   AHRS

   • yes
   • no
     AHRS 2.0

   power source: Anker 10,000mAh slim

   usb cable: Amazon Basics Short USB-C to Micro USB

3. EFB app and version: (e.g., WingX Pro7 8.6.2) Foreflight v12.11

   EFB platform: (e.g., iOS 9.2) iOS 14.2

   EFB hardware: (e.g., iPad Mini 2) iPad mini 5 cellular

4. Description of your issue:

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.

Please add support for the new UAT 978Mhz Low Power v3 that are now being sold with the Stratux kits. I didn't have an issue on the "US" version but it has a lack of development at the moment so I'm trying out this version in hopes that the handling of the new AHRS 2.0 chip is better. If it's not, at least more hope it will be better eventually due to more regular development.

All work is greatly appreciated!

I have been testing new release (eu19) and still having issues with altitude reporting for devices with baro sensor. Now on ground altitude randomly changing from 0ft to 1500ft. Please see attached log file (test device OGN with baro 26A74C).
'stratux.log'

1. Stratux version: 1.6r1-eu016

2. Stratux config:

   SDR

   • single
   • dual

   GPS

   • yes
   • no
     type:

   AHRS

   • yes
   • no

   power source:

   usb cable:

3. EFB app and version: (e.g., WingX Pro7 8.6.2) Skydemon

   EFB platform: (e.g., iOS 9.2) iOS 12.4.5

   EFB hardware: (e.g., iPad Mini 2) iPad Mini 2

4. Description of your issue:

After flashing to new version GPS is working but on the status page status is connected
stratux.log

Recent clients 0
SDR devices 0
Messages
1090ES 0
OGN(disconnected) 0

1. Stratux version: v1.6r1-eu011

2. Stratux config:

   SDR

   • single
   • dual

   GPS

   • yes
   • no
     type: UBlox NEO-M8N

   AHRS

   • yes
   • no

   power source: 2A-Powerbank

   usb cable:

3. EFB app and version: (e.g., WingX Pro7 8.6.2) Skydemon

   EFB platform: (e.g., iOS 9.2) iOS

   EFB hardware: (e.g., iPad Mini 2) iPad Mini 4 Cell

4. Description of your issue:

The Raspi kann not booting with this Image Version. I sea only a rainbow image on the monitor( conected via HDMI-Interface). The standard image vom cyoung is booting and creat a WIFI-Network. The Raspi is a 3B Model

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.

1. Stratux version: 1.6r1-eu20

2. Stratux config:

   SDR

   • single
   • [x ] dual

   GPS

   • [ x] yes
   • no
     type: USB u-blox 7 GNSS receiver (NMEA-UBX protocol)

   AHRS

   • [ x] yes - GY-91
   • no

   power source:

   usb cable:

3. EFB app and version: (e.g., WingX Pro7 8.6.2)

   EFB platform: (e.g., iOS 9.2)

   EFB hardware: (e.g., iPad Mini 2)

4. Description of your issue:

After moving from version eu19 to eu20 the AHRS Sensor is no longer working. Also version eu21 has this issue for me. It is a DY-91 that I got in 2017 that always worked fine until version eu19.
stratux.log shows this:
2020/05/27 08:05:34 - stratux-wifi.sh - Running Stratux WiFI Script.
2020/05/27 08:05:34 - stratux-wifi.sh - Killing Hostapd services
2020/05/27 08:05:35 - stratux-pre-start.sh - Running Stratux Updater Script.
2020/05/27 08:05:35 - stratux-pre-start.sh - Exited without updating anything...
2020/05/27 08:05:35 - stratux-wifi.sh - Stopping DHCP services
2020/05/27 08:05:40 - stratux-wifi.sh - Restarting DHCP services
2020/05/27 08:24:41 Stratux v1.6r1-eu020 (8bd3bc5) starting.
2020/05/27 08:24:42 Entered uatReader() ...
2020/05/27 08:24:42 can't read settings /etc/stratux.conf: open /etc/stratux.conf: no such file or directory
2020/05/27 08:24:42 Developer mode set
2020/05/27 08:24:42 getDHCPLeases(): open /var/lib/dhcp/dhcpd.leases: no such file or directory
2020/10/05 09:46:17 Could not identify MPU. v=c8, v2=73.
2020/10/05 09:46:18 GPS detected: u-blox NMEA position message seen.
2020/10/05 09:46:18 GPS attitude: Error calculating speed regression from UBX position messages
2020/10/05 09:46:18 GPS attitude: Error calculating speed regression from UBX position messages
2020/10/05 09:46:18 setting system time to: '20201005 08:46:18.100 UTC'
2020/10/05 09:46:18 Time set from GPS. Current time is 2020-10-05 09:46:18.105416979 +0100 BST m=+9.969315362
2020/10/05 09:46:18 setting system time to: '20201005 08:46:18.700 UTC'
2020/10/05 09:46:18 Time set from GPS. Current time is 2020-10-05 09:46:18.708399843 +0100 BST m=+10.328135778
2020/10/05 09:46:21 Could not identify MPU. v=c8, v2=73.
2020/10/05 09:46:25 Could not identify MPU. v=c8, v2=73.
2020/10/05 09:46:29 Could not identify MPU. v=c8, v2=73.
2020/10/05 09:46:33 Could not identify MPU. v=c8, v2=73.
2020/10/05 09:46:37 Could not identify MPU. v=c8, v2=73.
2020/10/05 09:46:41 Could not identify MPU. v=c8, v2=73.
2020/10/05 09:46:43 stats [started: 31 seconds ago]
2020/10/05 09:46:43 - Disk bytes used = 2.1 GB (6.6 %), Disk bytes free = 29 GB (93.4 %)
2020/10/05 09:46:43 - CPUTemp=36.48 [35.94 - 37.55] deg C, MemStats.Alloc=2.4 MB, MemStats.Sys=11 MB, totalNetworkMessagesSent=0
2020/10/05 09:46:43 - UAT/min 0/0 [maxSS=0.00%], ES/min 0/0, Total traffic targets tracked=0
2020/10/05 09:46:43 - Network data messages sent: 0 total, 0 nonqueueable. Network data bytes sent: 0 total, 0 nonqueueable.
2020/10/05 09:46:43 - Last GPS fix: now, GPS solution type: 1 using 8 satellites (9/13 seen/tracked), NACp: 10, est accuracy 5.20 m
2020/10/05 09:46:43 - GPS vertical velocity: -0.27 ft/sec; GPS vertical accuracy: 10.4 m
2020/10/05 09:46:43 - Mode-S Distance factors (<5000, <10000, >10000): 2500.000000, 2800.000000, 3000.000000
2020/10/05 09:46:43 - Last IMU read: now, Last BMP read: now
2020/10/05 09:46:45 Could not identify MPU. v=c8, v2=73.
2020/10/05 09:46:49 Could not identify MPU. v=c8, v2=73.
2020/10/05 09:46:53 setting system time to: '20201005 08:46:53.200 UTC'
2020/10/05 09:46:53 Time set from GPS. Current time is 2020-10-05 09:46:53.20542126 +0100 BST m=+44.784327498
2020/10/05 09:46:53 Could not identify MPU. v=c8, v2=73.
2020/10/05 09:46:55 setting system time to: '20201005 08:46:53.200 UTC'
2020/10/05 09:46:53 Time set from GPS. Current time is 2020-10-05 09:46:53.201105182 +0100 BST m=+47.348422655
2020/10/05 09:46:55 setting system time to: '20201005 08:46:53.700 UTC'
2020/10/05 09:46:53 Time set from GPS. Current time is 2020-10-05 09:46:53.702420026 +0100 BST m=+47.370708250
2020/10/05 09:46:53 setting system time to: '20201005 08:46:54.200 UTC'
2020/10/05 09:46:54 Time set from GPS. Current time is 2020-10-05 09:46:54.200962851 +0100 BST m=+47.389258431
2020/10/05 09:46:54 setting system time to: '20201005 08:46:54.700 UTC'
2020/10/05 09:46:54 Time set from GPS. Current time is 2020-10-05 09:46:54.700916833 +0100 BST m=+47.408478971
2020/10/05 09:46:54 setting system time to: '20201005 08:46:55.200 UTC'
2020/10/05 09:46:55 Time set from GPS. Current time is 2020-10-05 09:46:55.200996272 +0100 BST m=+47.427871249
2020/10/05 09:46:55 setting system time to: '20201005 08:46:55.700 UTC'
2020/10/05 09:46:55 Time set from GPS. Current time is 2020-10-05 09:46:55.700936875 +0100 BST m=+47.450168219
2020/10/05 09:46:56 setting system time to: '20201005 08:46:56.200 UTC'
2020/10/05 09:46:56 Time set from GPS. Current time is 2020-10-05 09:46:56.200906369 +0100 BST m=+47.768079392
2020/10/05 09:46:57 Could not identify MPU. v=c8, v2=73.
2020/10/05 09:47:01 Could not identify MPU. v=c8, v2=73.
2020/10/05 09:47:05 Could not identify MPU. v=c8, v2=73.
2020/10/05 09:47:09 Could not identify MPU. v=c8, v2=73.
2020/10/05 09:47:13 stats [started: 1 minute ago]

If there is any help I can provide, let me know! Thank you!

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.

1. Stratux version: v1.5b2-eu004

2. Stratux config:

   SDR

   • single
   • [x ] dual

   GPS

   • [ x] yes
   • no
     type:

   AHRS

   • [x ] yes
   • no

   power source:

   usb cable:

3. EFB app and version: (e.g., WingX Pro7 8.6.2)

   EFB platform: (e.g., iOS 9.2)

   EFB hardware: (e.g., iPad Mini 2)

4. Description of your issue:
   Just wondering if the FLARM data are also send thru GDL90 to the EFB?

It would be great to have a full-screen page of just the AHRS attitude indicator that could fill the screen on a phone.

As an author of something that uses the Stratux box (Stratux for Android) , I was curious about the bearingless targets.
I can see that there is a switch in the settings that can enable/disable it, but It does not really seem to do anything.
The estimated range is always attached to the WebSocket output regardless of this switch.
As for GDL90, your text implies that this also includes estimated range int the traffic report. However the specification for GDL90 (or at least the version I have) do not have a field for this.
Is it transmitted as a different/custom package?

Basically I think that it should not be op to the Stratux box to do these estimations, but if you can disable it in the Stratux I see no harm in having it as a feature the user can choose from. (but it should not transmit the data when disabled)

I did some tinkering with the range-estimation based on receiver strength myself, but a lot of logging later, I still have not been able to come up with a good enough algorithm.
Regards Lars