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
755 2920 d 0 h holgerb /tags/V2.14e/Hex-Files/ 2.14e (19.04.2016)
- no altitude limitation if altitude sensor is defective
 
753 2920 d 18 h holgerb /tags/V2.14e/ 2.14e (19.04.2016)
- no altitude limitation if altitude sensor is defective
 
750 2939 d 20 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 2963 d 19 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 2970 d 17 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 2984 d 22 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 3110 d 18 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 3134 d 18 h holgerb /tags/V2.10f/Hex-Files/ 2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost"
 
668 3134 d 18 h holgerb /tags/V2.10f/Hex-Files/ 2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost"
 
667 3134 d 18 h holgerb /tags/V2.10f/ 2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost"
 
657 3200 d 14 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 3200 d 14 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 3201 d 1 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 3201 d 17 h holgerb /tags/ 2.10e reported "Update Rate"  
652 3201 d 18 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 3201 d 18 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 3201 d 18 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 3201 d 19 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 3263 d 20 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 3282 d 22 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 3282 d 22 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 3283 d 19 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 3285 d 22 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 3285 d 22 h holgerb /tags/V2.10a/Hex-Files/ wrong version info  
627 3286 d 0 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 3474 d 19 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 3543 d 21 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 3557 d 0 h holgerb /tags/V2.06i/Hex-Files/ 2.06i (23.07.2014)
- Bugfix: Click on "Home" must cancel Waypoint flight
 
562 3557 d 0 h holgerb /tags/V2.06i/Hex-Files/ 2.06j (23.07.2014)
- Bugfix: Click on "Home" must cancel Waypoint flight
 
555 3575 d 23 h holgerb /tags/V2.06i/Hex-Files/ Bugfix: negative Altitude  
554 3575 d 23 h holgerb /tags/V2.06i/Hex-Files/ Bugfix: negative Altitude  
552 3578 d 19 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
 
551 3578 d 19 h holgerb /tags/V2.06i/Hex-Files/ wrong file  
550 3578 d 20 h holgerb /tags/V2.06i/ 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
- NEO-8 supported

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
 
546 3612 d 20 h holgerb /tags/V2.06f/ 2.06f (10.05.2014)
- Parameter.CamOrientation also used for relative waypoints
 
543 3639 d 0 h holgerb /tags/V2.06d/ 2.06d (02.05.2014)
- Bugfix: Waypoint Events
- Bigfix: Last character of the WP-List-Name was missing on the LCD
 
539 3642 d 1 h holgerb /tags/V2.06b/ 2.06b (29.04.2014)
- Bugfix: The logfile stopped for five seconds if an error occurred
 
538 3642 d 1 h holgerb /tags/ 2.06b (29.04.2014)
- Bugfix: The logfile stopped for five seconds if an error occurred
 
537 3642 d 1 h holgerb /tags/ 2.06b (29.04.2014)
- Bugfix: The logfile stopped for five seconds if an error occurred
 
535 3661 d 22 h holgerb /tags/V2.06a/ 2.06a (09.04.2014)
- prepared for single points
- added the dPH-Course into the Logfile
- dPH-Speed as parameter on SD-Card
- Position Accuracy as parameter on sd-card
- POI and Camera-Direction: Setpoint -= Geomag
- KML: added the name of the Track
- AutoPhoto over altitude implemented
- WP-Event on Auto-Position-Distance incresed from 6 to 10
- WP-Speed: Auto implemented
- copy license to EEPROM implemented
- License handling by PC implemented
- Logfile: "BL:V3" added
- Logfile: NotReadyCnt implemented
- Logfile: don't show data of unused motors
- Logfile: "(Redundance)"
- Added "R" in virtal Menu in case of redundance
- Logfile: Angle Nick and Roll in 0.1°
- Logfile: Milliseconds added in Timestamp
- MAX_RANGE, MAX_ALTITUDE and DESCEND_RANGE removed from SD-card and moved into MK-Settings
- Logfile: License and Settings Info added
- Bugfix: "ERR25:WP-Range" when using CH and distance >250m
- Don't fly to Waypoint #1 if out of Range