gereic/gxaircom

Multifunctional, compatible DIY aviation proximity awareness, variometer and messaging system with FANET+, FLARM and OGN support.

GxAirCom

GxAircom aims to be a complete and open source implementation of the FANET+ (Fanet + Flarm) protocol running on readily available cheap lora modules and interfacing with mobile phones via Bluetooth. It can also act as a Fanet ground station and broadcast recieved FANET information to OGN.

For information and documentation see:

• The PDF quick guide and the The PDF Documentation
• Further information can be found in the wiki and the docs folder. E.g.:
  • The list of supported hardware
  • The list of supported smartphone software
  • How to update the firmware
  • See the video tutorials

Similar/ related projects are:

• The SoftRF project, which has wider hardware and protocol support, but implements only the subset of the FANET protocol that broadcasts and receives locations. It also cannot broadcast FANET and FLARM at the same time.
• The Skytraxx FANET Source. The original reference implementation of the FANET standard and upstream of the standard protocol specification and documentation.

gxaircom's Issues

GPS fix with the T-Beam V1.1

on first start the T-Beam V1.1 will show a blinking GPS light but:

• no GPS position on the webpage
• no GPS position is transmitted over FANET
• no GPS position can be obtained over Bluetooth with LK8000

fix

• enter the webpage
• hit settings save and reboot (with unchanged settings)
• now GPS works as expected

this behaviour can be reproduced in a persistent manner

This seems to be a known issue with the T-Beam and can be fixed with a GPS reset.
Xinyuan-LilyGO/LilyGo-LoRa-Series#28

set FANET status "landed ok" after landing and pilot confirmation

i as a user should be asked after landing, if the landing was ok and everything is fine
AND can confirm this message by pressing a hardware button on the device (on ttgo beam v1.1 - IO38)
THEN the fanet status "landed ok" will be set automatically

(this feature is a "copy" of the handling in skytraxx fanet instruments)

Not building Web-Helper Issue

Hello, @gereic

When building the latest file vi Atom IO using platform IO the web page is not working when trying to access the board... what have I missed here

baro ms5611 with GY-63

Hello, I've bought a new Baro board GY-63 (ms5611) and can see the appropriate section in the web console (Vario) but without values. In the documentation I figured out, that only the GY-86 was implemented. Has the GY-63 other specifications or is my module corrupt?

acc-sensor calibration not working for me

I have a LILYGO® TTGO T-Beam V1.1 and a Heltec Wifi Lora 32 board and two gy-86 modules. The software is the current 4.9.0 version. On both systems the calibration process hangs at the last step - this is endlessly requested again. I have already cross-swapped the two GY-86 modules.

I have tried to analyse the problem. I reloaded the software after deleting the flash:

esptool.py -p /dev/ttyUSB0 erase_flash
esptool.py -p /dev/ttyUSB0 write_flash 0x1000 bootloader_dio_40m.bin 0x8000 partitions.bin 0xe000 boot_app0.bin 0x10000 firmware_v4.9.0_psRam.bin 0x3d0000 spiffs_v4.9.0.bin

The sensor is found when booting:

Terminal bootlog /dev/ttyUSB0:
...
[I][main.cpp:536] oledPowerOn(): Heltec-board
[I][main.cpp:2487] taskBaro(): starting baro-task
[I][main.cpp:3663] taskStandard(): GPS Baud=9600,8N1,RX=12,TX=15
[I][main.cpp:4329] taskEInk(): stop task
[I][Baro.cpp:409] initMS5611(): found sensor MS5611
[I][Baro.cpp:423] initMS5611(): MPU6050 connection successful
[E][Preferences.cpp:492] getBytesLength(): nvs_get_blob len fail: axScale NOT_FOUND
[E][Preferences.cpp:492] getBytesLength(): nvs_get_blob len fail: ayScale NOT_FOUND
[E][Preferences.cpp:492] getBytesLength(): nvs_get_blob len fail: azScale NOT_FOUND
[I][Baro.cpp:447] initMS5611(): tempcorrection: t0=20.00 z0=0.00 t1=0.00 z1=0.00
[I][Baro.cpp:449] initMS5611(): Initializing DMP...
[I][Baro.cpp:457] initMS5611(): gyro not calibrated
[I][Baro.cpp:467] initMS5611(): acc offsets ax_offset=-332,ay_offset=1003,az_offset=1852
[I][Baro.cpp:482] initMS5611(): scale ax_scale=1.00,ay_scale=1.00,az_scale=1.00,
[I][Baro.cpp:483] initMS5611(): acc offsets ax_offset=0,ay_offset=0,az_offset=0
[I][Baro.cpp:484] initMS5611(): gyro offsets gx_offset=0,gy_offset=0,gz_offset=0
[I][Baro.cpp:537] calcClimbing(): Kalman_settings sigmaP=0.1000,sigmaA=0.6000
...

Under Settings "settings view" set to expert and "use accelerometer " to true(checked).

after reboot

Values are shown in the info area - sensor lies flat on the table:
accel -720,15030,17066
gyro x -1,-1,-1
acc z 1.90

If I then start the calibration under settings, the different orientations of the device/sensor are requested.

Terminal log /dev/ttyUSB0:

[I][WebHelper.cpp:49] onWebSocketEvent(): [0] Received text with size=11 paylod: {"page":10}
[I][WebHelper.cpp:59] onWebSocketEvent(): page=10
[I][WebHelper.cpp:486] onWebSocketEvent(): [0] type=10
[W][main.cpp:2528] taskBaro(): baro max=148ms
[I][WebHelper.cpp:49] onWebSocketEvent(): [0] Received text with size=14 paylod: {"calibAcc":1}
[I][WebHelper.cpp:49] onWebSocketEvent(): [0] Received text with size=15 paylod: {"calibAcc":11}
-765
14850
17080
-23
-23
-23
[I][WebHelper.cpp:49] onWebSocketEvent(): [0] Received text with size=15 paylod: {"calibAcc":11}
-1130
14497
-16076
-20
-20
-20
[I][WebHelper.cpp:49] onWebSocketEvent(): [0] Received text with size=15 paylod: {"calibAcc":11}
295
-1579
-20
-9
-9
-9
[I][WebHelper.cpp:49] onWebSocketEvent(): [0] Received text with size=15 paylod: {"calibAcc":11}
-85
31005
1150
-29
-29
-29
[I][Baro.cpp:139] calibrate(): ayMax=31005
[I][WebHelper.cpp:49] onWebSocketEvent(): [0] Received text with size=15 paylod: {"calibAcc":11}
-15999
14208
2302
-26
-26
-26
[I][WebHelper.cpp:49] onWebSocketEvent(): [0] Received text with size=15 paylod: {"calibAcc":11}
16769
14792
433
-23
-23
-23
[I][WebHelper.cpp:49] onWebSocketEvent(): [0] Received text with size=15 paylod: {"calibAcc":11}
16737
14821
1489
-23
-23
-23

The last step "please put module down" button "press when done" is requested endlessly.

I tried to understand the source code and got stuck in Baro.cpp line 128..153.
For me, both sensors are out of range - where do the values 5000 and 10000 come from?

meansensors();
if ((abs(mean_ax) <= 5000) && (abs(mean_ay) <= 5000) && (mean_az > 10000)){
azMax = mean_az;
log_i("azMax=%d",azMax);
}
if ((abs(mean_ax) <= 5000) && (abs(mean_ay) <= 5000) && (mean_az < -10000)){
azMin = mean_az;
log_i("azMin=%d",azMin);
}
if ((abs(mean_ax) <= 5000) && (mean_ay > 10000) && (abs(mean_az) <= 5000)){
ayMax = mean_ay;
log_i("ayMax=%d",ayMax);
}
if ((abs(mean_ax) <= 5000) && (mean_ay < -10000) && (abs(mean_az) <= 5000)){
ayMin = mean_ay;
log_i("ayMin=%d",ayMin);
}
if ((mean_ax > 10000) && (abs(mean_ay) <= 5000) && (abs(mean_az) <= 5000)){
axMax = mean_ax;
log_i("axMax=%d",axMax);
}
if ((mean_ax < -10000) && (abs(mean_ay) <= 5000) && (abs(mean_az) <= 5000)){
axMin = mean_ax;
log_i("axMin=%d",axMin);
}
if ((axMin != 0) && (axMax != 0) && (ayMin != 0) && (ayMax != 0) && (azMin != 0) && (azMax != 0)){

Change values - other ideas ?

NEO-M8N GPS compatible?

Hi I just received one of this:

TTGO T-Beam ESP32 868 MHz NEO-M8N GPS WiFi

it has a different gps module the Neo m8n, is it compatible or should I import a different library and compile source again?

thanks,

Martino

dB signal strength in OGN data packets

Today I was watching out for dB signal strength of targets on glidertracker.de. They showed up with zero dB (see screenshot). Something must be wrong. Does OGN perhaps not like the triple digit figures that GXAircom is reporting ? On OGN receivers based on an SDR a great signal would probably be somewhere around 50dB, but never in the triple digits.

1.6.0

two issues on 1.6.0 and one issue from the previous version:

db reporting:

• db numbers in OGN now just show as zero

Settings;
Updated a T-Beam T22 V1.1 from the previous version. The unit had been configured as an air- unit. After the update the settings were no longer present. The pilot field for example was empty, but the header of the webpage still showed the pilot name that had been present in the settings of the previous version. Re-entering the pilot name and operating mode (air-mode, OGN tracking) doesn't work. After saving and rebooting the settings are not retained. Also the entire 'info' screen lacks any information. Also tried physically to physically restart (unplug power) the unit - with the same effect.

Previous version - occasionally stops reporting traffic
Occasionally the unit would loose connection to the OGN. The station would disappear from the station map and cease reporting traffic. When I returned to the unit everything on the outside looked normal. The display was on and I could also access the unit via the webpage. A reboot then brought everything back to normal again. Strangely, during on of these dropouts the base station was still updating heartbeat packets to the airwhere map website and was transmitting out FANET status packets (these were picked up by neighbouring OGN receiver).

.bin filenames

With V4.x.x I do not understand the .bin file names any more.
Is there a way to decipher them?

Add meaningful Readme

Hi there,

I've heard some positive things about this project, but it's really hard to dig deeper as there seems to be no documentation about it's abilities?

I would have liked to see:

• Some information about what the software does, which hardware it requires and where to find further documentation in the Readme.md file
• A link to a website (if it exists) somewhere

I guess some of this already exists, as people seem to be able to use it - but this documentation is definitely lacking in the repository

Not an issue but a feature... TTGO T-Beam on "Non PS Ram" version

Hello Gerald.

I was having some issues with only one of the ttgo t-beam devices (v1.1), specifically my personal flying device. After some time (not measured but seems like more than 30 minutes) the device gets frozen. screen on but unresponsive to button short press and no broadcasting data through bluetoot, and not being received by the other gxaircom devices around. So I need to hold power for 10 secs (no screen shutoff secuence). It will turn off (but blue light still lit) and then I will turn it on again and it will start working.

So I decided to try the "non psram" version to see if this particular device has some psram issues that are freezing the unit.

So far, the non psram is running without any issues, so I also upgraded a few other user´s t-beams to "non ps Ram 4.6.1.

It seems that it´s stable enough to go with it. I will try to run some extra conection tests to see if everything is good.

Recommended Beeper?

Hi,

which is the recommended Beeper/Buzzer to use? Is there a loud/well working model?

Thanks,
Bernd

1.7.0

Did a bit of testing:
In OGN groundstation mode receive strength (db) is not transmitted to OGN
In groundstation mode targets were not showing up on the Airwhere map.

2.9" e-paper case

I have the makings for one of these https://github.com/gereic/GXAirCom/blob/master/doc/bilder_videos/GxAirCom_am_eink.jpg
Except the stl for the case.
Any help here?

send groundstation location in OGN groundstation mode

Have not been able to spot my GXAirCom groundstation on the OGN maps (gliderradar). I believe this is because GXAirCom probably doesn't send a groundstation beacon to OGN. The default of the Raspberry implementations seems to be to send a groundstation beacon every five minutes. The protocol is described here: http://wiki.glidernet.org/wiki:ogn-flavoured-aprs
A groundstation beacon would be great, as this would enable OGN range analysis tools to plot the receiver range of GXAirCom.

Heltec LoRa Module - Battery Status

When attaching a full loaded 3.7 V 1800mAh Lithium Polymer Battery to the Heltec LoRa Modul, The Battery Status is shown as empty on the OLED Display.

Wrong ID read from softrf Fanet

Don't know if it is a real issue or maybe a problem of softrf mark ii firmware but I get the wrong ID from all my devices set to fanet while receiving with GXAir.

Eg. device real ID 0D3724 read as 073724

change screen orientation in general settings

due to different cockpit setups, it could happen, that you need you device horizontally or vertically or upside down..

i as a user would like to change the screen orientation to have more flexibility on cockpit setups
changes should apply for the supported screen types

Case for pigtail anteanna connectors

Based on your case I've created a case version for an antenna connection using a pigtail, which is shipped with some of the t-beam models (like the one I have here with the M8N ublox module).

Feel free to use/integrate it - or if not please provide your own version of such a case.
I'm using openscad because thats what I know 👍

Files are here:
https://shell.bzed.at/~bzed/.publish/2020-11-24-pSoA3siqqOY/

Kobo

@gereic is there a kick start guide on the Kobo interface ? curious as I have one spare and would like to hook it up, happy to do a write up on this to help others if I could have a bit of direction on getting started,

Great work on the fuel meter, iv had a few stumbles with the sensor but slowly getting there now..

Matt

BME280 - occasional wrong humidity readings

I did have a couple of instances on Windy where briefly extremely high humidity (121318%, etc.) values were reported. I don't know the cause. In the technical literature for the sensor it is reported that the sensor can get 'stuck' after prolonged exposure to high humidity. Users report sticking the sensor into an oven briefly and drying out the sensor. In my case I just had to take it indoors to dryer climate for a couple of minutes. Perhaps it could be considered to have the software reject values that can't make sense because they are outside of the range of conditions existing on earth. That way a malfunctioning sensor will not cause data pollution.

Most likely this is only to happen with humidity readings, as this is the most delicate element of the sensor. Therefore reporting a value of 100% until the sensor returns to normal operation (reports values of below 100%) would be a working solution.

PSRAM issue on TTGO Lora32 (T3_v1.6)

When flashing 1.4.4 the device stays in a boot-loop. As i understand the log, it has to do with initializing the non-existent psram

Rebooting...
ets Jun  8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:8896
load:0x40080400,len:5828
entry 0x400806ac
[W][esp32-hal-psram.c:30] psramInit(): PSRAM init failed!
Guru Meditation Error: Core  0 panic'ed (IllegalInstruction). Exception was unhandled.
Memory dump at 0x401303b0: 00000000 00000040 00004000
Core 0 register dump:
PC      : 0x401303b4  PS      : 0x00060030  A0      : 0x800fc28b  A1      : 0x3ffbbc80
A2      : 0x8001f880  A3      : 0x8001f880  A4      : 0x4008897c  A5      : 0x00000001
A6      : 0x00060c20  A7      : 0x00000000  A8      : 0x800fb458  A9      : 0x3ffbbc60
A10     : 0x00000020  A11     : 0x00000001  A12     : 0x3ffcaf72  A13     : 0x00000001
A14     : 0xffffffff  A15     : 0x00000000  SAR     : 0x0000000f  EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000  LBEG    : 0x400014fd  LEND    : 0x4000150d  LCOUNT  : 0xfffffffe

Backtrace: 0x401303b4:0x3ffbbc80 0x400fc288:0x3ffbbca0 0x400ff7a7:0x3ffbbcd0 0x40091bb1:0x3ffbbcf0

Device is ok. SoftRF works.

Gitter Community

Hi,

I'm playing a bit with your code and I would like to try to help if I can or at least contribute.
I started actually with the softrf project before but from what I see your project is more close to paragliding.

I'm testing a bit of all hardware, just received the heltec esp32 v2 and I do have a T-Beam V1.1.

I do have some questions any chance we can have a chat or is there a Gitter room to discuss about developments?

Thanks,

Martino.

unable to install on a TTGO T3 V1.6

On the TTGO T3 V1.6 the versions prior to the AM/GS version split will install. However newer versions will not start (both if flashed over USB or if updated over the web interface).

Fuel meter window

@gereic

Have been testing the fuel meter and the vibration from the engine is creating quite a lot of noise on the sesnor..

Iv written a small section of window sampling code which works well to filter out the noise, is this something that could be implement... to the voltage spikes are smoothes out giving a average reading....

TTGO platform IO error

Hey, can any one assist getting this error after flashing

Invalid data in APRS stream

In the APRS stream of the OGN we often see complete invalid messages from GXAirCom devices (wind from 2147483647 degree...):

FNTFBACA4>OGNFNT,qAS,Sonthofen:/084427h5807.34S/00232.69W_2147483647/2147483647g2147483647 0.0dB
FNT060001>OGNFNT,qAS,Huenenb2:/084351h5807.34S/16053.67E_2147483647/2147483647g2147483647 0.0dB
FNT060001>OGNFNT,qAS,HuenenWX:/084435h5807.34S/00000.23E_2147483647/2147483647g2147483647 0.0dB

But also these messages are invalid:
FNT085890>OGNFNT,qAS,WyPgvNw:/084545h4756.32N/01444.20E_359/004g006t070r4310p30830h54b10176 0.0dB

We see r4310 (=1094mm rain in the last hour), but the rainfall of the last hour is defined as 'rxxx' so we have just 3 digits. Same for p30830.

All these beacons are ignored by the python-ogn-client library. Please check out the APRS specification: http://www.aprs.org/doc/APRS101.PDF

eink 2.9 still not working for me

Following
#36

I desoldered the two resistors but still not working the display.. I tested the display and it works with arduino nano.

Should I remove or also do the bridge after removing the resitors?

any other idea why it doesn't work? exact same setup except I have also the BMP20 maybe?

Here my connections

Thanks,

Martino

Originally posted by @Martenz in #36 (comment)

Connect 2.9" eink?

I have connected to
******* E-Ink *********
BUSY 33
RST 4
DC 32
CS 15
CLK 0
DIN 2
Can anyone confirm these connections are still correct?
With 2 boards and 2 screens same result, until I dropped the set pictured, otherwise no response on the screen.
This on 4.4.0 & 4.5.1 & now firmware_v4.6.1_nopsRam.bin.
Is this screen not supported?
Or does it need 5v? I had read that would be a bad idea.
I have seen the photo of an apparently working set.
Any one got a comment?

T-SIM7000 as am - connection redundancy

Hi,

Would it also be possible to use the SIM7000G as a tracker? Or is this already tested?
Using the functionality it should be possible to both have FANET signals sent over LoRa while at the same moment sending data to a traccar server. Offering connectivity and tracking in more situations or conditions.

Sincerely

Version 4.8.5.

How did i get my hands on version 4.8.5?

I can´t find it anymore. I´m pretty sure i got it from dev. Now I see we are "down" to 4.7.1

FANET Aircraft shown with name of received weather station

Hello Gerald,
great work - I really like it.

Trying with build 4.3.1 (binary download). I am operating a local Skytraxx FANET Windstation with ID 01:011D and name "wGer" and also turned on Skytraxx 2.1 with ID: 11:2BBB, name "MaRe".
(See attached.)

On '/neighbours.html' the SkyTraxx 2.1 is shown with the name of the Windstation.
Investigating further my self.

Kind Regards
Manfred

Flashing FW v4.6.1 does not work on T-beam v1.1

I tried flashing firmware version 4.6.1 from the bin directory in this repo but it does not work after the restart. It loops in the GXAircoom logo and then restarts then loop continues.

Can anyone test and confirm?

connect to WiFi: always try to reconnect

The menu choice connect to wifi:connect (always try to reconnect) can't be saved persistently. It will always returns to 'try only once'.

FANET temperature shows too high (double) value

The test setup: LILYGO® TTGO ESP32 SX1276 LoRa V1.0 with BME280 temperature/pressure/humidity sensor. No other sensors are connected. https://www.aliexpress.com/item/32845370112.html?spm=a2g0s.9042311.0.0.27424c4dzkWaJT

The issue: on the webpage of the TTGO the temperature value and all other values are shown correctly. However the temperature value that is received via FANET (viewed on the gliderradar.com website) is exactly double the correct temperature. The other values (humidity, pressure) that are received over FANET are correct.

Another small issue: as soon as I set a temperature (K) offset, the board website starts to show extreme (many digit) figures.

LilyGo T-Watch board compatibility

Hi,

I just got one of these LilyGo T-Watch including Lora, GPS, wifi and bluetooth:

https://it.aliexpress.com/item/33038999162.html?spm=a2g0o.productlist.0.0.654a12b27nXXyp&algo_pvid=4da35557-3c3f-4cd0-bcef-c2d20887209b&algo_expid=4da35557-3c3f-4cd0-bcef-c2d20887209b-1&btsid=2100bde116148632475175498e00ee&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_

do you think it will be possible to configure also this board to have it working with GxAirCom?

I tested a flash of the firmware and the only thing that works of course is wifi and GxAir wifi interface.. the screen is a tft so I imagine it will need some recode for displaying data but to enable Lora and GPS I guess it can be done setting the correct pins..

thanks

T-SIM7000G - reconnect after battery depleted

The test scenario:
T-SIM7000G in sleep sunset to sunrise mode
let the battery deplete until the device no longer reports to OGN
plug in USB to recharge the battery

Symptoms:
even after several days with USB connected and the battery charge light showing a full charge, the device would not reconnect to OGN
after disconnecting USB and letting the device sit for 19 hours still no connection to OGN

Observations:
the 'Status' LED next to the Sim Antenna lights up solid red
the 'Netlight' LED next to the 'Status' LED blinks slowly (about every two seconds)

After removing and re-inserting the battery everything is back to normal. The device connects to OGN and the 'Netlight' LED blinks at a fast pace (I didn't try the power switch).

Course and Speed being reported for OGN groundstation

When the position is reported by GXAirCom in the 5 minute position beacon signal of a groundstation to OGN, this also includes course and speed. I don't see the other groundstations doing this. Their message format ends with A=XXXXXX
Is this necessary ? Could this perhaps prevent the OGN Range Tool (https://ognrange.glidernet.org/) from recognising GXAirCom as a valid ground station ?

Version 4.8.0_UTC Time wrong

Flashed my TTGO (V1.1) unit to FW 4.8.0. today. Reading through the info screen I found the UTC Time reverted to 1970-01-01. At first I thought this would be updated following GPS-fix, however after getting a good fix it remained at this date.

Previous software was erased before flashing and unit was reset and restarted before starting this issue.

2nd, minor issue is the functionality of the menu option, "Basic, Advanced and Expert". This does not show anything different in the menu layout??

FANET

I have two T-Beams for testing.
The T-Beams with GXAirCom installed can see each other, but while my Skytraxx 2.1 can see both T-Beams they cannot see the Skytraxx.
I cannot find a setting to fix this, so is it a firmware issue?

Oled TTGO T Beam

Hello,

Okay so the new PIO file is working with out errors...

Just one issue regardless if I flash Via Esptool.py or Platform IO the Oled just won't stay in the setting in the Web page.... every thing else saves and sticks just the oled won't...

Have tried a few thing but it just won't stick..

Iv set the Oled as per the pinout

Trying to build in VCS via PIO

Hey,

Getting an issue with web access after uploading via PIO on Mac M1

E][WebHelper.cpp:565] onPageNotFound(): [192.168.4.2] HTTP GET request of /favicon.ico

An ideas....

Striped down version

Hello all,

I'm looking to use a very stripped down version of GXaircom to send some very basic data over espnow

In essence using a small ttgo board..

I plan on sending information from the flarm to a wireless display..

Simply only air traffic needs to be communicated and its bearing in a 10km range of the board GPS position...

I plan on having a simple config page where craft type can be selected and the protocol option of OGN or Flarm and that's it.

The board would then send over esp now..

The incoming crafts long and lat and that's all I need.. I think to show up on a small screen....

Does any of the protocals work in this way..

Any advice on getting started would be appreciated..

GPS fix on LILYGO TTGO T-Beam V1.1

The GPS lock performance on the LILYGO TTGO T-Beam V1.1 (SX1272) can be unpredictable. Often the GPS light on the PCB will blink, but the web interface will not show a GPS lock. Strangely a reboot on the web interface will then predictably result in a GPS position lock being established. This makes it a bit difficult to use as a tracking device, as one can never be certain whether a GPS position has been successfully established. It can't be the antenna hardware, as connecting an active antenna doesn't change the GPS behaviour. Only a reset of the device after a GPS lock has been established will always work.

baro altitude on XCSOAR (Kobo)

Hello,
I'm using an BMP280 on TTGO TBEAM with GXAirCom version 4.8.0 via UDP connected to an Kobo with XCSoar
On the web-console I can see the pressure data but XCSOAR isn't able to interpret. I tried in LK8000 and it works fine.
Would it possible to add the altitude data form the BMP in a XCSOAR readable format?
Cheers - Thomas

T-SIM7000G doesn't connect to LTE

At the moment the T-SIM7000G will only connect to the GSM network, but not to LTE. I came across this when my provider switched off the GSM data network a couple of weeks ago.

Volume not affected by second button

Hi I added both BME280 and Passive buzzer to TBeam v1.1, and GxAir 4.7.2

everything is working except for the volume, should it change pressing the middle button? I see the icon change from low to high volume but seems my buzzer is always the same.

Moreover it would be nice to add also "no volume'' at all to disable the buzzer with the button also, so

OFF - Low - Mid - Hig cycle of the button

thanks

Martino

failure to wake up from sunset to sunrise sleep

Last night I set up three boards (TTGO 1.0, TTGO 1.3 and T-Sim7000G) on 1.9.1 to go to sleep from sunset to sunrise by using the respective option. They all failed to wake up the next morning. The are no longer registering on OGN. They don't show up on Wifi.
All are powered over USB. In the the T-Sm7000G the battery was in and the board was connected to USB power.
Other observations.
On the TTGO 1.0 the red led on the mainboard is blinking as usual. However the chipset feels cold. When operating and online, the chipset would be warm.
On the TTGO 1.3 the green led on the board is on as usual. However the chipset also feels cold.
The same applies to the T-Sim 7000G.
Other observations: with 1.9.0 and 1.9.1 the boards would not automatically reboot after an update of the firmware over the web frontend. The boards appeared to 'hang' and required a hard reboot (by pulling USB power). The same also happenend to me wiht the TTGO 1.0 after I changed the sleep setting on the website.
In another test on 1.9.0 the T-Sim 7000G would not start without a battery in the battery compartment. Night sleep mode was not enabled for this test. Power draw over USB was 7.5mA, which would be typical for a deep sleep mode.
To complete the diagnostic picture I will now also run the T-Sim 7000G for a night just on battery power.

GPS coordinates are not updating in GS mode

Testing GroundStation mode on T-beam v1.1.

According to the PDF doc the coordinates should be automatically set using GPS if they are set to zeroes in the settings. But this does not seem to work. When checking i the INFO page after startup the coords are still zeroes.

Another issue is that the GS is not visible on the OGN network but the test aircraft is showing up. I can see other GS on the map but not mine.

I am using GXaircom v 4.7 from bin/dev directory in the repo.

Trouble getting GPS signal

Hi,
first thank you very much for that great project.

I'm having trouble getting a GPS signal with my new TTGO Meshtastic T-Beam V1.1 ESP32.
I flashed the most recent software and made the recommended settings. Everything looks good so far except it won't get a GPS signal. Display shows NO GPS-FIX and web ui shows all zeros in the gps status.

logs from serial monitor:
https://gist.github.com/landorg/4d21363e9cf004ec99cdcccf31236bff

Any idea what could be wrong here or tips to debug?
Thanks

EDIT: added logs with additional output over serial enabled to gist