Subversion Repositories NaviCtrl

Rev

Go to most recent revision | Show changed files | Details | Compare with Previous | Blame | RSS feed

Filtering Options

Rev Age Author Path Log message Diff
822 2501 d 2 h holgerb /tags/V2.18a/Hex-Files/ 2.18b (23.05.2017)
- Serial connection to MK3Mag fixed (the NC was connecting back to GPS after 5 Seconds because of GPS Data timeout)
 
818 2533 d 22 h holgerb /tags/V2.18a/ 2.18a (13.12.2016 - 18.04.2018)
- MASTER and SLAVE in Logfile description
- Flyzones implemented
-> Settings option: FlyZoneRequired
-> Settings option: Land Outside Flyzone
- Galileo Support - MK-GNSS V4
- Slave: wait 3sec for GPS-Cfg (instead 1,5sec)
- Show "CalibrationError" Message
- Try GPS-Init after some seconds. It seems that sometimes the GPS-Module needs longer to wake up
- OSD-Data Packet 13 (HomePos)
-> Type of Satfix (3Bits)
-> Flag:Boat-Mode
-> OSD3_FLAG_HOTSHOE
- Logfile doesn't Stop in case of GPS-Failure: "Invalid"
- Re-Init GNSS-Module in case of failure
- set datarate and packet abo if "Autoconfig" is deactivated on SD-Card
- smaller gps-cfg: don't set abos of packets that are not activated
- Disable Putchar() if connectet to FC
 
817 2533 d 22 h holgerb /tags/V2.18a/ 2.18a (13.12.2016 - 18.04.2018)
- MASTER and SLAVE in Logfile description
- Flyzones implemented
-> Settings option: FlyZoneRequired
-> Settings option: Land Outside Flyzone
- Galileo Support - MK-GNSS V4
- Slave: wait 3sec for GPS-Cfg (instead 1,5sec)
- Show "CalibrationError" Message
- Try GPS-Init after some seconds. It seems that sometimes the GPS-Module needs longer to wake up
- OSD-Data Packet 13 (HomePos)
-> Type of Satfix (3Bits)
-> Flag:Boat-Mode
-> OSD3_FLAG_HOTSHOE
- Logfile doesn't Stop in case of GPS-Failure: "Invalid"
- Re-Init GNSS-Module in case of failure
- set datarate and packet abo if "Autoconfig" is deactivated on SD-Card
- smaller gps-cfg: don't set abos of packets that are not activated
- Disable Putchar() if connectet to FC
 
816 2533 d 23 h holgerb /tags/V2.18a/Hex-Files/ 2.18a (13.12.2016 - 18.04.2018)
- MASTER and SLAVE in Logfile description
- Flyzones implemented
-> Settings option: FlyZoneRequired
-> Settings option: Land Outside Flyzone
- Galileo Support - MK-GNSS V4
- Slave: wait 3sec for GPS-Cfg (instead 1,5sec)
- Show "CalibrationError" Message
- Try GPS-Init after some seconds. It seems that sometimes the GPS-Module needs longer to wake up
- OSD-Data Packet 13 (HomePos)
-> Type of Satfix (3Bits)
-> Flag:Boat-Mode
-> OSD3_FLAG_HOTSHOE
- Logfile doesn't Stop in case of GPS-Failure: "Invalid"
- Re-Init GNSS-Module in case of failure
- set datarate and packet abo if "Autoconfig" is deactivated on SD-Card
- smaller gps-cfg: don't set abos of packets that are not activated
- Disable Putchar() if connectet to FC
 
815 2533 d 23 h holgerb /tags/V2.18a/Hex-Files/ 2.18a (13.12.2016 - 18.04.2018)
- MASTER and SLAVE in Logfile description
- Flyzones implemented
-> Settings option: FlyZoneRequired
-> Settings option: Land Outside Flyzone
- Galileo Support - MK-GNSS V4
- Slave: wait 3sec for GPS-Cfg (instead 1,5sec)
- Show "CalibrationError" Message
- Try GPS-Init after some seconds. It seems that sometimes the GPS-Module needs longer to wake up
- OSD-Data Packet 13 (HomePos)
-> Type of Satfix (3Bits)
-> Flag:Boat-Mode
-> OSD3_FLAG_HOTSHOE
- Logfile doesn't Stop in case of GPS-Failure: "Invalid"
- Re-Init GNSS-Module in case of failure
- set datarate and packet abo if "Autoconfig" is deactivated on SD-Card
- smaller gps-cfg: don't set abos of packets that are not activated
- Disable Putchar() if connectet to FC
 
812 2534 d 3 h holgerb /tags/V2.18a/ 2.18a (13.12.2016 - 18.04.2018)
- MASTER and SLAVE in Logfile description
- Flyzones implemented
-> Settings option: FlyZoneRequired
-> Settings option: Land Outside Flyzone
- Galileo Support - MK-GNSS V4
- Slave: wait 3sec for GPS-Cfg (instead 1,5sec)
- Show "CalibrationError" Message
- Try GPS-Init after some seconds. It seems that sometimes the GPS-Module needs longer to wake up
- OSD-Data Packet 13 (HomePos)
-> Type of Satfix (3Bits)
-> Flag:Boat-Mode
-> OSD3_FLAG_HOTSHOE
- Logfile doesn't Stop in case of GPS-Failure: "Invalid"
- Re-Init GNSS-Module in case of failure
- set datarate and packet abo if "Autoconfig" is deactivated on SD-Card
- smaller gps-cfg: don't set abos of packets that are not activated
 
796 2670 d 2 h holgerb /tags/V2.16a/ 2.16a (05.12.2016)
- ERR 43: Parachute input
- Don't rise on first WP if the MK is alreay flying above 3m when activating the WP #1
- "Rise on first Waypoint" can be disabled by Parameter
- Logfile doesn't Stop in case of GPS-Failure
- OEM-String for customers who build MikroKopters under other brand-names
- GPX-File: ASCII instead of UTF-8
- Sometimes a camera-trigger-position was not transmitted in OSD-Frame
- the structure of the CAN-Data was smaller that it could be
- two structures in the navi data were changed in size to be devidible by 3
- \n\r replaced by \r\n
- use the real GPS-Position instead the Intertial-Filtered-Position as long as we have a waypoint as target
- 1MBit Baudrate for SD-Card readings -> about 5 times faster FTP communication
- Bugfix for Checksum calculation (Bug was only in Betaversion 2.15)
- FC Temperature mesurement implemented for FC3.0
- Baro temperature compensation implemented for FC3.0
- Kompensation factor and FC temperature in Logfile
- FC temperature in the logfile (before and after the flight)
- new flag: NC_TO_FC_SWITCHOFF_IF_LANDED
- Landing points implemented
-> landing point are also Failsafe-Points
- PointList_WPBegin has now an index where to start
- write WP_Radius into Logfile
- LaserCtrl supported
- write Laser distance into Logfiles
- faster Error-Message in case of SPI Errors
 
756 2899 d 2 h holgerb /tags/V2.14e/Hex-Files/ 2.14e (19.04.2016)
- no altitude limitation if altitude sensor is defective
 
755 2899 d 2 h holgerb /tags/V2.14e/Hex-Files/ 2.14e (19.04.2016)
- no altitude limitation if altitude sensor is defective
 
753 2899 d 20 h holgerb /tags/V2.14e/ 2.14e (19.04.2016)
- no altitude limitation if altitude sensor is defective
 
750 2918 d 22 h holgerb /tags/V2.14d/ 2.14d (31.03.2016)
- There were still problems: When using one MKGPS V3.5 on two redundant NCs, it could happen that the configuration of the GPS failed
 
747 2942 d 21 h holgerb /tags/V2.14c/ 2.14c (07.03.2017)
- Bugfix: When using one MKGPS V3.5 on two redundant NCs, it could happen that the configuration of the GPS failed
 
745 2949 d 19 h holgerb /tags/V2.14b/ 2.14b (29.02.2016)
- comment in the triggerlog: Longitude and Latitude mixed
- bugfix: external compass was not detected correctly on NC2.x
 
741 2964 d 0 h holgerb /tags/V2.14a/ 2.14 (21.10.2015 - 15.02.2016)
- Version for FC3.0 and 2.x
- prepared for Canbus (Master/Slave)
- Menu: Gyro removed and Analog 5-7 added
- Menu: Settings Name in main menu [0]
- internal compass: variable attitude
- SPI:
- Structures changed to 20 Bytes Payload
- huge block transfer implemented (for Parameter set)
- Settingsfile from FC to NC via SPI
- serial communication processed directly by NC:
'b':// submit extern control
'y':// serial Channels
'g':// request for the externalControl
'p':// request for the PPM_In-Daza
- GPX-Logfile: Settingsname in Logfile
- New: FC_STATUS3_CALIBRATION_DONE
- Menu.c: Showing Slave Status data
- Menu:Trigger Input
- Logfile for Camera-Trigger events (only FC3.0)
- GPS-Config: GPS with dual connector supported
- Errors:
40: RC-Voltage
41: Power Supply
42: ACC not calibratetd
- Uart:
- NC reads and processes SerialPoti
- NC reads and processes ExternalControl
- NC sends PPM_In[]
- CRC Checksum in GPX Logfile
- Menu[30] = CamCtrl
- CamCtrlCharacter in Hott-Menu
- CamCtrlCharacter Shows external TriggerCounter
- CamCtrl supported for NC 2.1
- fixed: sometimes "ERR:BL Seftest" after switch on without any reason
- CamCtrlCharacter in OSD Dataframes
- CamCtrl Shoots always one first Photo when switching to Middle Position
- size of the Settings-Data adjusted
- size of HugePacket reduced to 200 Bytes
- descend in failsafe-case starts as soon as the MK is closer than 35m to FS-Point
- Waypoints:
- Bugfix: if the climbing speed is AUTO: do not report "target reached" until the altitude is reached
- rise on first Waypoint before moving position -> max.20m
 
684 3089 d 19 h holgerb /tags/V2.12a/ 2.12a (13.07.2015 - 12.10.2015)
- new message: ERR38: "GPS Update Rate" if Update Rate is lower than 5Hz
- Logfile: <GPSInfo> : UpdateFrequency, Flags and Type of Fix
- Only for Simulation: Bugfix: Rotation direction of relative Waypoints
- MAX_SAT_LEA4 = 11 -> that improves the GPS-performance regarding data rate
- small improvement for FollowMe-Communication
- Automatic reduction of MAX-SAT if the GPS-Update rate drops
- small bugfix: the GPS-Configuration datastream was too long
- MAX_SAT_LEA 6 & 8 = 15
- Improved behaviour regaring "GPS Fix lost"
- more keywords for compression
- Uart-Buffer increased from 1024 to 1500 bytes
- Bit to inform the FC if the UART is switched to FC
- reading 8 Analog channels instead of 7
- GPS-System: Japanese QZSS can be activated by SD-Paramerter
- Used Satellite system can be selected: 1:GPS+GLNAS 2:GPS+BEIDOU 3:GPS 4:GLNAS 5:BEIDOU (only GPS V3)
- Logfile: <GNSS_System>-Setting
- KopterTool: manual compass offset limited to 5°
 
669 3113 d 20 h holgerb /tags/V2.10f/Hex-Files/ 2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost"
 
668 3113 d 20 h holgerb /tags/V2.10f/Hex-Files/ 2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost"
 
667 3113 d 20 h holgerb /tags/V2.10f/ 2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost"
 
657 3179 d 16 h holgerb /tags/V2.10e/Hex-Files/ 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
- Note: Hexfile updated on 12.07.2015 might report "GPS-Fix Lost" instead of "No GPS Fix" -> that was fixed on 13th July
 
656 3179 d 16 h holgerb /tags/V2.10e/Hex-Files/ - Note: Hexfile updated on 12.07.2015 might report "GPS-Fix Lost" instead of "No GPS Fix" -> that was fixed on 13th July  
655 3180 d 3 h holgerb /tags/V2.10e/ 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 3180 d 19 h holgerb /tags/ 2.10e reported "Update Rate"  
652 3180 d 20 h holgerb /tags/V2.10e/Hex-Files/ 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 3180 d 20 h holgerb /tags/V2.10e/ 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 3180 d 20 h holgerb /tags/ 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 3180 d 21 h holgerb /tags/V2.10d/ 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
 
641 3242 d 22 h holgerb /tags/V2.10c/ 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
 
635 3262 d 0 h holgerb /tags/V2.10b/Hex-Files/ 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
 
634 3262 d 0 h holgerb /tags/V2.10b/Hex-Files/ 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
 
632 3262 d 20 h holgerb /tags/V2.10b/ 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
 
629 3265 d 0 h holgerb /tags/V2.10a/Hex-Files/ 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
 
628 3265 d 0 h holgerb /tags/V2.10a/Hex-Files/ wrong version info  
627 3265 d 2 h holgerb /tags/V2.10a/ 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
 
579 3453 d 21 h holgerb /tags/V2.08a/ 2.08a (10.10.2014)
- FC.StatusFlags3 added -> RedundanceMode moved into the flags
- BoatMode
- Calibration Data in Logfile
- Bugfix in NMEA
- No further climbing to CH-Altitude if CH-Position is reached (but still descending if nessecary)
- Bugfix: descending to Coming home Altitude was stopped when the CH-Position was reached
- RC-Failsafe: descend at Home-Point even if "Vario-Failsafe" was not selected in the settings
- Bugfix: WP-Event was sometimes triggered two times
- Bugfix: the shown WP-Distance was not correct in simulation
- removed: min WP-Event time -> the "WAIT_FOR_OUT1" makes it anyway
- NEW: WP-Timeout implemented
- new logging entry: "Gas" + "HoverGas"
 
575 3522 d 23 h holgerb /tags/V2.07b_Beta/ 2.07b (05.08.2014)
- FC.StatusFlags3 added -> RedundanceMode moved into the flags
- BoatMode
- Calibration Data in Logfile
- Simulation implemented
 
563 3536 d 2 h holgerb /tags/V2.06i/Hex-Files/ 2.06i (23.07.2014)
- Bugfix: Click on "Home" must cancel Waypoint flight
 
562 3536 d 2 h holgerb /tags/V2.06i/Hex-Files/ 2.06j (23.07.2014)
- Bugfix: Click on "Home" must cancel Waypoint flight
 
555 3555 d 0 h holgerb /tags/V2.06i/Hex-Files/ Bugfix: negative Altitude  
554 3555 d 0 h holgerb /tags/V2.06i/Hex-Files/ Bugfix: negative Altitude  
552 3557 d 21 h holgerb /tags/V2.06i/Hex-Files/ 2.06g (28.05.2014)
- <ele_raw> added in the logfiles
- <ele> can be negative now

2.06h (23.06.2014)
- additional information in GPX Info field
- BL SW-Version in GPX info

2.06i (01.07.2014)
- Bugfix: after deleting waypoints via "GPS-Free" it could happen that the next WP flight would not release photos at Waypoint 1