Subversion Repositories NaviCtrl

Rev

Go to most recent revision | Show changed files | Directory listing | RSS feed

Filtering Options

Rev Age Author Path Log message Diff
669 1992 d 4 h holgerb / 2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost"
 
668 1992 d 4 h holgerb / 2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost"
 
667 1992 d 4 h holgerb / 2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost"
 
666 1992 d 4 h holgerb / 2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost"
 
665 2000 d 8 h holgerb / 2.11d (10.09.2015)
- 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 = 14
 
664 2000 d 9 h holgerb / - small bugfix: the GPS-Configuration datastream was too long  
663 2000 d 10 h holgerb / 2.11c (10.09.2015)
- Automatic reduction of MAX-SAT if the GPS-Update rate drops
 
662 2000 d 10 h holgerb / Update WP for FollowMe  
661 2000 d 10 h holgerb / no change  
660 2043 d 9 h holgerb / 2.11b (29.07.2015)
- MAX_SAT_LEA4 = 12 (was before:15)
 
659 2057 d 8 h holgerb / 2.11a (13.07.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
 
658 2057 d 8 h holgerb / - Logfile: <GPSInfo> : UpdateFrequency, Flags and Type of Fix  
657 2058 d 0 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
- Note: Hexfile updated on 12.07.2015 might report "GPS-Fix Lost" instead of "No GPS Fix" -> that was fixed on 13th July
 
656 2058 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 2058 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 2058 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 2059 d 3 h holgerb / 2.10e reported "Update Rate"  
652 2059 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 2059 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 2059 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 2059 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 2059 d 5 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 2059 d 5 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 2059 d 5 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 2059 d 9 h holgerb / - new message: ERR38: "GPS Update Rate" if Update Rate is lower than 5Hz  
644 2059 d 9 h holgerb / - new message: ERR38: "GPS Update Rate" if Update Rate is lower than 5Hz  
643 2059 d 9 h holgerb / Counter: GPS-CRC Error  
642 2113 d 10 h holgerb / 2.10d (20.05.2015)
- Saving "AutoTrigger (AutoPhotoDistance) on SD-Card
 
641 2121 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 2121 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 2121 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 2121 d 8 h holgerb / 2.10c (12.05.2015)
- Bugfix: too many motor currents recorded in the logfiles
 
637 2121 d 9 h holgerb / SPEAK_CONNECTED  
636 2121 d 9 h holgerb / no changes  
635 2140 d 8 h holgerb / 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 2140 d 8 h holgerb / 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
 
633 2140 d 8 h holgerb / 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 2141 d 4 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
 
631 2141 d 4 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
 
630 2141 d 4 h holgerb / 2.10b (22.04.2015)
- Bugfix: CH-Speed was MAX and not the SD-Setting