Rev |
Age |
Author |
Path |
Log message |
Diff |
Changes |
750 |
3068 d 17 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 |
|
/tags/V2.14d
|
747 |
3092 d 16 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 |
|
/tags/V2.14c
|
745 |
3099 d 14 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 |
|
/tags/V2.14b
|
741 |
3113 d 19 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 |
|
/tags/V2.14a
|
684 |
3239 d 14 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° |
|
/tags/V2.12a
|
669 |
3263 d 15 h |
holgerb |
/tags/V2.10f/Hex-Files/ |
2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost" |
|
/tags/V2.10f/Hex-Files/Navi-Ctrl_STR9_V2_10f.hex
|
668 |
3263 d 15 h |
holgerb |
/tags/V2.10f/Hex-Files/ |
2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost" |
|
/tags/V2.10f/Hex-Files
|
667 |
3263 d 15 h |
holgerb |
/tags/V2.10f/ |
2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost" |
|
/tags/V2.10f
|
657 |
3329 d 11 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 |
|
/tags/V2.10e/Hex-Files/Navi-Ctrl_STR9_V2_10e.hex
|
656 |
3329 d 11 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 |
|
/tags/V2.10e/Hex-Files/Navi-Ctrl_STR9_V2_10e.hex
|
655 |
3329 d 22 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 |
|
/tags/V2.10e
|
653 |
3330 d 14 h |
holgerb |
/tags/ |
2.10e reported "Update Rate" |
|
/tags/V2.10e
|
652 |
3330 d 15 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 |
|
/tags/V2.10e/Hex-Files/Navi-Ctrl_STR9_V2_10e.hex
|
651 |
3330 d 15 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 |
|
/tags/V2.10e
|
649 |
3330 d 15 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 |
|
/tags/V2.10d
|
648 |
3330 d 16 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 |
|
/tags/V2.10d
|
641 |
3392 d 17 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 |
|
/tags/V2.10c
|
635 |
3411 d 19 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 |
|
/tags/V2.10b/Hex-Files/Navi-Ctrl_STR9_V2_10b.hex
|
634 |
3411 d 19 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 |
|
/tags/V2.10b/Hex-Files/Navi-Ctrl_STR9_V2_10b.hex
|
632 |
3412 d 15 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 |
|
/tags/V2.10b
|