1st prerelease for hw version 2.0

Flashed STM32 and ESP32_sketch_BT_WLAN.ino and connected GNSS Antenna:

No-SD-Card Inserted

• Red GNSS PPS LED shows working GNSS
• Only blue System LED blinks
• Connection via Bluetooth is possible, but no data is transmitted

Reset after inserted a SD-Card with only the file Configuration_files/sensor_config.txt on the sd_card :

• GNSS PPS, blue System and after a while blue GNSS leds are blinking
• NMEA Data is received via Bluetooth.
• There are no flight data record files on the SD-Card.
• There are empty crashdump files and eeprom dump files recored on the sd-card

Retest with an additional "enable.logger" dummy file on the sd-card to enable flight data logging

• the sd-card led starts blinking
• a 230225_094824.f37 flight data file is recorded.

Do we need to remove the sensor_config.txt file after an initial configuration from the sd-card to prevent resetting changed calibration parameters in the eeprom after every reboot? #36 Renamed file to _disabled_sensor_config.txt on the sd card

• There are always two flight data (f.37) files recorded after a system start. A small one after 1 minute runtime and a second one for the remaining uptime.
• There are also two eeprom ore more dump files recorded for a single power cycle.
• It seems that there is one reset happening during startup it no sensor_config.txt file exists.

Content from sd card after running some time:

• Why do we have *.f92 and crashdump files?
• Why *.f37 files now? Does this break compatibility?

Tested with another 12V Power Supply via RJ45 instead of the USB Power Supply. Sensor consumes (active sd card logging) around 126 - 140mA with Bluetooth connected and 92 - 102mA with no paired Bluetooth connection.

• Resets still occur from time to time so they are not related to a unstable power supply.
• observed 13 Resets in 84 minutes
• It seems that resets are happening more frequently if the GNSS antenna is moved indoors.