| Rev |
Age |
Author |
Path |
Log message |
Diff |
| 656 |
2106 d 0 h |
holgerb |
/ |
- Note: Hexfile updated on 12.07.2015 might report "GPS-Fix Lost" instead of "No GPS Fix" -> that was fixed on 13th July |
|
| 655 |
2106 d 11 h |
holgerb |
/ |
2.10c (12.05.2015)
- Bugfix: too many motor currents recorded in the logfiles
- Bugfix: Don't rise at undervoltage if CH-Altitude is higher than actual altitude
2.10d (20.05.2015)
- Saving "AutoTrigger (AutoPhotoDistance) on SD-Card
2.10e (13.07.2015)
- debug-data[13] = GPS CRC Error
- new message: ERR38: "GPS Update Rate" if Update Rate is lower than 5Hz
- No error message "GPS-Fix lost" if GPS-Fix is lost for < 0,5 sec |
|
| 654 |
2106 d 11 h |
holgerb |
/ |
2.10c (12.05.2015)
- Bugfix: too many motor currents recorded in the logfiles
- Bugfix: Don't rise at undervoltage if CH-Altitude is higher than actual altitude
2.10d (20.05.2015)
- Saving "AutoTrigger (AutoPhotoDistance) on SD-Card
2.10e (13.07.2015)
- debug-data[13] = GPS CRC Error
- new message: ERR38: "GPS Update Rate" if Update Rate is lower than 5Hz
- No error message "GPS-Fix lost" if GPS-Fix is lost for < 0,5 sec |
|
| 653 |
2107 d 3 h |
holgerb |
/ |
2.10e reported "Update Rate" |
|
| 652 |
2107 d 4 h |
holgerb |
/ |
2.10d (20.05.2015)
- Saving "AutoTrigger (AutoPhotoDistance) on SD-Card
2.10e (13.07.2015)
- debug-data[13] = GPS CRC Error
- new message: ERR38: "GPS Update Rate" if Update Rate is lower than 5Hz
- No error message "GPS-Fix lost" if GPS-Fix is lost for < 0,5 sec |
|
| 651 |
2107 d 4 h |
holgerb |
/ |
2.10e (13.07.2015)
- debug-data[13] = GPS CRC Error
- new message: ERR38: "GPS Update Rate" if Update Rate is lower than 5Hz
- No error message "GPS-Fix lost" if GPS-Fix is lost for < 0,5 sec |
|
| 650 |
2107 d 4 h |
holgerb |
/ |
2.10e (13.07.2015)
- debug-data[13] = GPS CRC Error
- new message: ERR38: "GPS Update Rate" if Update Rate is lower than 5Hz
- No error message "GPS-Fix lost" if GPS-Fix is lost for < 0,5 sec |
|
| 649 |
2107 d 4 h |
holgerb |
/ |
2.10e (13.07.2015)
- debug-data[13] = GPS CRC Error
- new message: ERR38: "GPS Update Rate" if Update Rate is lower than 5Hz
- No error message "GPS-Fix lost" if GPS-Fix is lost for < 0,5 sec |
|
| 648 |
2107 d 4 h |
holgerb |
/ |
2.10e (13.07.2015)
- debug-data[13] = GPS CRC Error
- new message: ERR38: "GPS Update Rate" if Update Rate is lower than 5Hz
- No error message "GPS-Fix lost" if GPS-Fix is lost for < 0,5 sec |
|
| 647 |
2107 d 4 h |
holgerb |
/ |
2.10e (13.07.2015)
- debug-data[13] = GPS CRC Error
- new message: ERR38: "GPS Update Rate" if Update Rate is lower than 5Hz
- No error message "GPS-Fix lost" if GPS-Fix is lost for < 0,5 sec |
|
| 646 |
2107 d 4 h |
holgerb |
/ |
2.10e (13.07.2015)
- debug-data[13] = GPS CRC Error
- new message: ERR38: "GPS Update Rate" if Update Rate is lower than 5Hz
- No error message "GPS-Fix lost" if GPS-Fix is lost for < 0,5 sec |
|
| 645 |
2107 d 8 h |
holgerb |
/ |
- new message: ERR38: "GPS Update Rate" if Update Rate is lower than 5Hz |
|
| 644 |
2107 d 8 h |
holgerb |
/ |
- new message: ERR38: "GPS Update Rate" if Update Rate is lower than 5Hz |
|
| 643 |
2107 d 8 h |
holgerb |
/ |
Counter: GPS-CRC Error |
|
| 642 |
2161 d 10 h |
holgerb |
/ |
2.10d (20.05.2015)
- Saving "AutoTrigger (AutoPhotoDistance) on SD-Card |
|
| 641 |
2169 d 6 h |
holgerb |
/ |
2.10a (11.11.2014 - 20.04.2015)
- SD-card flush() after every GPX-block
- GPX-Logging start at Motor run (can be disabled by SD-Setting)
- Changed: GPS version detection
- Logfile:
- <GeoMag> with one comma value
- <GpsVersion> in Logfile
- <Compass> with one comma value
- <Receiver> Receiver type in logfile
- <MagSensor> Magnetsensor type in logfile
- <Kalibr.> Sensor Data at ACC-Calibration (Boat-Values)
- SPI communication optimized -> some Data are faster, some are slower
- BL-State (Current, Temperature,...) are now faster transferred for Logging
- Altimeter in Data3D (serial data)
- ComingHome: automatic Direction change
- allows Yawing without CareFree (Yawing at Coming Home)
- LSM303D implemented
- bugfix: uBat in 16Bit
- AnalogLable CRC implemented -> KopterTool doesn't need to read them every time
- new structures for the NC-OSD-Dataframe
- splitted in small parts for higher efficency
- some more data:
- LipoCount
- SpeakHoTT
- VarioCharacter
- GpsCharacter
- WP_OperatingRadius now in 16Bit
- UBat now in 16Bit
- BL_MinOfMaxPWM
- ShutterCounter implemented
- ShutterPosition transmitted in OSD-Data (only if the data link can transmit more than 200Bytes per secons)
- AutoPhotoDistance as Parameter for Waypoints
- FailsafePosition in Waypoint list
- 16 Motors
- Logfile:<ShutterCnt>
- New Error Messages:
35: FAILSAFE-Position
36: ERR:Redundancy
37: Redundancy test
- MaxFlying Range and Descend Range in Navi-Dataframe
- HoTT speaks "100m" after 100m distance or Altitude (25m Hysteresis)
-> can be disabled by SETTINGS.INI -> "HOTT_SPEAK_100M"
- SD-Parameter: AUTO_WP_EVENT -> value for the WP-Event Trigger at Auto-Distance [10ms]
- Simulation: Descend at undervoltage
2.10b (22.04.2015)
- Bugfix: CH-Speed was MAX and not the SD-Setting
- Logfile: the output Flag was sometimes longer active than required
2.10c (12.05.2015)
- Bugfix: too many motor currents recorded in the logfiles
- Bugfix: Don't rise at undervoltage if CH-Altitude is higher than actual altitude |
|
| 640 |
2169 d 6 h |
holgerb |
/ |
2.10c (12.05.2015)
- Bugfix: too many motor currents recorded in the logfiles
- Bugfix: Don't rise at undervoltage if CH-Altitude is higher than actual altitude |
|
| 639 |
2169 d 6 h |
holgerb |
/ |
2.10c (12.05.2015)
- Bugfix: too many motor currents recorded in the logfiles
- Bugfix: Don't rise at undervoltage |
|
| 638 |
2169 d 8 h |
holgerb |
/ |
2.10c (12.05.2015)
- Bugfix: too many motor currents recorded in the logfiles |
|
| 637 |
2169 d 8 h |
holgerb |
/ |
SPEAK_CONNECTED |
|