Rev |
Age |
Author |
Path |
Log message |
Diff |
Changes |
894 |
2296 d 7 h |
holgerb |
/tags/ |
Update for 2.20h: The older V2.20h was the Betaversion 2.21 by mistake |
|
/tags/V2.20h
|
892 |
2296 d 7 h |
holgerb |
/tags/V2.20h/ |
Update for 2.20h: The older V2.20h was the Betaversion 2.21 by mistake
2.20a (25.04.2017 - 01.11.2017)
- variable baudrate on NC
- KopterTool: WP-Generator: Heading to next WP
- HoTT-Speech:
- Loading & Saving
- Camera REC-On & Off
- Replaced: HOTT_NEXT_WP -> HoTT_Starting _WP
- GimbalControl implemented -> Interface for BL-Gimbals
- HoTT-Speak: Save & Load
- External Control: EC_ONLY_IF_MOTOR_OFF 0x10 // use these Stick Positions only if the motors are not running -> this is used for calibrate etc. to make sure that full throttle not applied with running motors
- HoTT-Statustext in OSD-Data
- Mobile Menu -> separate Menu structure for use on Mobiles etc.
- corrected: leap seconds in UTC calculation
- Magnetic Field in OSD-Data
- SD-Card logging: Logfile does not stop, if the SD-Card switch opens
- New Waypoint direction option: Look into flight direction
- Do not use AutoTrigger on CH-Flight after Waypoint flight
- negative gimbal degrees possible -> attention: "AUTO" is now 121 - that will effect old waypoint tools
- Separate Failsafe-Altitude for RC-Lost
- wait 10 seconds at RC lost until fly back. Change Altitude during this time
- SD-Option "YawWithoutCarefree"
- variable baudrate on NC - up to 256000Bd
- No ASCII Encoding in GPX-File
- Mission Parameter in Waypoint Editor
- Trigger Bitmask
- Ignore-RC-Lost
- Delay Trigger (half of Waypoint Time)
- CH-Altitude
- Failsafe-Altitude
2.20c (13.11.2017)
- Menu[12] External Control
- Logging Gimbal Data in GPX
- Logging ExternalCtrl in GPX
2.20d (29.11.2017)
- Switching outputs on GinbalCtrl -> can control the Infrared Camera etc.
2.20e (04.12.2017)
- In case of logging abort -> close files and open new files after some seconds
2.20f (29.01.2018)
- writing SD-Card Speed in GPX-File
- writing the channel assignment into the logfile
- changing the <RCSticks> into the real channels instead of Potis (Nick, Roll, Yaw, Gas, CH5, CH6, CH7,...CH16
2.20g (28.02.2018)
- Licesefeature "IGNORE-RC-Lost" didn't work without the new Mission-Parameter Protocol
2.20h (12.03.2018)
- added the tag in the logfile: <!-- Redundant System: YES -->
- Compatiblity of loading the wpl-files set to version 3 & 4 to be able to load wpl-files created by KopterTool |
|
/tags/V2.20h
|
891 |
2296 d 8 h |
holgerb |
/tags/ |
This was the Betaversion 2.21 |
|
/tags/V2.20h
|
882 |
2360 d 8 h |
holgerb |
/tags/V2.20h/ |
2.20h (12.03.2018)
- added the tag in the logfile: <!-- Redundant System: YES -->
- Compatiblity of loading the wpl-files set to version 3 & 4 to be able to load wpl-files created by KopterTool |
|
/tags/V2.20h
|
876 |
2395 d 8 h |
ingob |
/tags/V2.20e/Hex-Files/ |
|
|
/tags/V2.20e/Hex-Files/Navi-Ctrl_STR9_V2_18b.hex
|
875 |
2395 d 8 h |
ingob |
/tags/V2.20f/Hex-Files/ |
|
|
/tags/V2.20f/Hex-Files/Navi-Ctrl_STR9_V2_18b.hex
|
874 |
2395 d 8 h |
ingob |
/tags/V2.20g/Hex-Files/ |
|
|
/tags/V2.20g/Hex-Files/Navi-Ctrl_STR9_V2_18b.hex
|
873 |
2402 d 7 h |
holgerb |
/tags/V2.20g/ |
2.20g (28.02.2018)
- Licesefeature "IGNORE-RC-Lost" didn't work without the new Mission-Parameter Protocol |
|
/tags/V2.20g
|
870 |
2432 d 7 h |
holgerb |
/tags/V2.20f/ |
2.20a (25.04.2017 - 01.11.2017)
- variable baudrate on NC
- KopterTool: WP-Generator: Heading to next WP
- HoTT-Speech:
- Loading & Saving
- Camera REC-On & Off
- Replaced: HOTT_NEXT_WP -> HoTT_Starting _WP
- GimbalControl implemented -> Interface for BL-Gimbals
- HoTT-Speak: Save & Load
- External Control: EC_ONLY_IF_MOTOR_OFF 0x10 // use these Stick Positions only if the motors are not running -> this is used for calibrate etc. to make sure that full throttle not applied with running motors
- HoTT-Statustext in OSD-Data
- Mobile Menu -> separate Menu structure for use on Mobiles etc.
- corrected: leap seconds in UTC calculation
- Magnetic Field in OSD-Data
- SD-Card logging: Logfile does not stop, if the SD-Card switch opens
- New Waypoint direction option: Look into flight direction
- Do not use AutoTrigger on CH-Flight after Waypoint flight
- negative gimbal degrees possible -> attention: "AUTO" is now 121 - that will effect old waypoint tools
- Separate Failsafe-Altitude for RC-Lost
- wait 10 seconds at RC lost until fly back. Change Altitude during this time
- SD-Option "YawWithoutCarefree"
- variable baudrate on NC - up to 256000Bd
- No ASCII Encoding in GPX-File
- Mission Parameter in Waypoint Editor
- Trigger Bitmask
- Ignore-RC-Lost
- Delay Trigger (half of Waypoint Time)
- CH-Altitude
- Failsafe-Altitude
2.20c (13.11.2017)
- Menu[12] External Control
- Logging Gimbal Data in GPX
- Logging ExternalCtrl in GPX
2.20d (29.11.2017)
- Switching outputs on GinbalCtrl -> can control the Infrared Camera etc.
2.20e (04.12.2017)
- In case of logging abort -> close files and open new files after some seconds
2.20f (29.01.2018)
- writing SD-Card Speed in GPX-File
- writing the channel assignment into the logfile
- changing the <RCSticks> into the real channels instead of Potis (Nick, Roll, Yaw, Gas, CH5, CH6, CH7,...CH16 |
|
/tags/V2.20f
|
868 |
2486 d 7 h |
holgerb |
/tags/V2.20e/ |
2.20a (25.04.2017 - 01.11.2017)
- variable baudrate on NC
- KopterTool: WP-Generator: Heading to next WP
- HoTT-Speech:
- Loading & Saving
- Camera REC-On & Off
- Replaced: HOTT_NEXT_WP -> HoTT_Starting _WP
- GimbalControl implemented -> Interface for BL-Gimbals
- HoTT-Speak: Save & Load
- External Control: EC_ONLY_IF_MOTOR_OFF 0x10 // use these Stick Positions only if the motors are not running -> this is used for calibrate etc. to make sure that full throttle not applied with running motors
- HoTT-Statustext in OSD-Data
- Mobile Menu -> separate Menu structure for use on Mobiles etc.
- corrected: leap seconds in UTC calculation
- Magnetic Field in OSD-Data
- SD-Card logging: Logfile does not stop, if the SD-Card switch opens
- New Waypoint direction option: Look into flight direction
- Do not use AutoTrigger on CH-Flight after Waypoint flight
- negative gimbal degrees possible -> attention: "AUTO" is now 121 - that will effect old waypoint tools
- Separate Failsafe-Altitude for RC-Lost
- wait 10 seconds at RC lost until fly back. Change Altitude during this time
- SD-Option "YawWithoutCarefree"
- variable baudrate on NC - up to 256000Bd
- No ASCII Encoding in GPX-File
- Mission Parameter in Waypoint Editor
- Trigger Bitmask
- Ignore-RC-Lost
- Delay Trigger (half of Waypoint Time)
- CH-Altitude
- Failsafe-Altitude
2.20c (13.11.2017)
- Menu[12] External Control
- Logging Gimbal Data in GPX
- Logging ExternalCtrl in GPX
2.20d (29.11.2017)
- Switching outputs on GinbalCtrl -> can control the Infrared Camera etc.
2.20e (04.12.2017)
- In case of logging abort -> close files and open new files after some seconds |
|
/tags/V2.20e
|
822 |
2683 d 7 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) |
|
/tags/V2.18a/Hex-Files/Navi-Ctrl_STR9_V2_18b.hex
|
818 |
2716 d 4 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 |
|
/tags/V2.18a/uart1.c
|
817 |
2716 d 4 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 |
|
/tags/V2.18a/uart1.c
|
816 |
2716 d 4 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 |
|
/tags/V2.18a/Hex-Files/Navi-Ctrl_STR9_V2_18a.hex
|
815 |
2716 d 4 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 |
|
/tags/V2.18a/Hex-Files/Navi-Ctrl_STR9_V2_18a.hex
|
812 |
2716 d 8 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 |
|
/tags/V2.18a
|
796 |
2852 d 7 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 |
|
/tags/V2.16a
|
756 |
3081 d 8 h |
holgerb |
/tags/V2.14e/Hex-Files/ |
2.14e (19.04.2016)
- no altitude limitation if altitude sensor is defective |
|
/tags/V2.14e/Hex-Files/Navi-Ctrl_STR9_V2_14e.hex
|
755 |
3081 d 8 h |
holgerb |
/tags/V2.14e/Hex-Files/ |
2.14e (19.04.2016)
- no altitude limitation if altitude sensor is defective |
|
/tags/V2.14e/Hex-Files/Navi-Ctrl_STR9_V2_14e.hex
|
753 |
3082 d 2 h |
holgerb |
/tags/V2.14e/ |
2.14e (19.04.2016)
- no altitude limitation if altitude sensor is defective |
|
/tags/V2.14e
|