0.4.0

What's Changed

• Update README.md by @realtimepeople in #97
• Transmit commands between Frontend <-> and a to the Sensor connected XCSOAR by @MaxBaex in #99
• Configuration file format to .ini standard changed. by @realtimepeople in #92
• Merge temp by @realtimepeople in #102
• CAN gateway functionality isolated for better portability. by @MaxBaex in #100
• Work by @realtimepeople in #103
• Using Lib Version https://github.com/larus-breeze/sw_algorithms_lib/releases/tag/v0.1.2

Full Changelog: 0.3.2...0.4.0

0.3.2

What's Changed

• ESP32 Firmware: Add sending NMEA data via both UART interfaces. by @realtimepeople in #89
• Bugfix crashes when no gnss fix by @realtimepeople in #90
• Bugfix: String terminator missing in Larus-NMEA string which caused incorrect or no wind sentences via NMEA.
• Using Lib Version https://github.com/larus-breeze/sw_algorithms_lib/releases/tag/v0.1.1

Full Changelog: 0.3.1...0.3.2

0.3.1

What's Changed

• Firmware update without using any micro-controller programming hardware using a firmware image "larus_sensor_V2_image.bin" on the microSD.
• New setup parameter for sensor_config.txt :
  "34 Horizon_active = 1.0".
  Setting it to "0.0" will disable the output of roll and pitch angle to
  support disabling the artificial horizon during competition flights.
• Sensor writes signed *.EEPROM-file now in preparation of IGC certification.
• EEPROM Parameter Integrity enforced.
• Parameter Name corrected -> SensTilt_Pitch. by @realtimepeople in #87
• Using Lib Version https://github.com/larus-breeze/sw_algorithms_lib/releases/tag/v0.1.0

Full Changelog: 0.3.0...0.3.1

0.3.0 - do not use -

New

• Implemented Firmware Update Feature
• Introduced magnetic model which removed the need for inclination and declination parameters in the sensor_config.txt file
• Bluetooth/WIFI Name appended by 4 Byte HEXCODE
• Updated documentation.

What's Changed

• added led signal meaning in readme. #71 by @MaxBaex in #72
• Klaus work by @realtimepeople in #64
• added a few more DGNSS configuration informations to the readme by @MaxBaex in #70
• changed submodule to relative path by @MaxBaex in #69
• ESP32: Code cleaned up and switches installed by @Blaubart in #74
• added some very basic information to a esp32 readme.md file. Removed … by @MaxBaex in #77
• Issue 68 by @MaxBaex in #78
• moved ESP32 software licence to correct folder by @MaxBaex in #80
• Correct HW Version for image loader by @Simsys in #81
• Remove pack.toml from git version control and generate it during the build process by @MaxBaex in #83
• append bluetooth name / wifi ssid with a unique id based on the esp32… by @MaxBaex in #85
• Sha256: Integrate horizon deactivation mechanism. by @realtimepeople in #84

New Contributors

• @Blaubart made their first contribution in #74
• @Simsys made their first contribution in #81

Full Changelog: 0.2.3...0.3.0

0.2.3

What's Changed

• Non functional: Restructured repository directories in #55
• Functional: sensor.readings : Added output for DGNSS data if available in #62

Full Changelog: 0.2.2...0.2.3

Prerelease

What's Changed

• Lib update. by @realtimepeople in #52
• Fix EEPROM Bug #47 by @MaxBaex in #54
• Mag calibration values eeprom writing occurrences reduced during flight.
• Generate uin32_t versioninformation with python build script for CAN distribution #48
• SD Logging Feature updated

Full Changelog: 0.2.1...0.2.2

2nd prerelease for hw 2.0

Improved robustness in case there is a distorted unrealistic GNSS signal by clipping the output values in the NMEA formatters.

Fixed a bug which caused that parts of the DGNSS driver have been used for the M9N module.

There are rarely some crashes caused by the FPU detecting a float, running out its value range (NaN). The system recovers quickly from these crashes. The FPU exception could be disabled by flushing all NaNs to 0. We decided to keep this exception active in order to track the occurrences.

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.

3rd Reinsdorf

0.1.1

Bugfix: Delay logging until SAT fix available.

2nd version for Reinsdorf

FS test version.

FPU exception deactivated.
Circling detected from abs airframe rotation.