| Rev |
Age |
Author |
Path |
Log message |
Diff |
Changes |
| 935 |
1425 d 7 h |
holgerb |
/tags/V2.22a/ |
2.22a (25.05.2020)
- Possibility to send the HomePosition via 's'-Command (Type = 5) - only with licese
- WAYPOINT-EVENT = 255 -> Cameratrigger continously ON (or OFF -> Depends on the IDLE-Bit)
- NMEA Input for external GNSS-Systems (RTK-GPS etc.)
- parse NMEA Data into GPS-Coordinates
- Fly with NMEA GPS Data possible
- Autotrigger everx x-Meters can be used without RC and without BL
- Repeat the WP-List x times (SETTINGS.INI)
- Logfile: <LaserAltCorr> correction, uncorrected value <\LaserAltCorr>
- Send compass-value to Gimbalcontrol for better Yaw stability and drift compensation
- Yaw Value of the Gimbal is now the compass-direction of the gimbal
- GimbaCtrl compatiblity changed --> Needs GimbalCtrl V1.04
- show ControllerID
- internal resolution of Baro altitude changed from 5cm to 10cm to allow Waypoint flight > 1600m
- Maximum altitude for Waypoints is now 3200m above starting point
- Altimeter Setpoint in dm
- Bugfix: Max-Altitude in simulation
- Bugfix: NaviData.Variometer in simulation
- Altimeter in data protocol to KopterTool now in Meters [m] instead of [5cm] -> still compatible to old tools (FLAG_ALTIMETER_M)
- new Parameters for Laser
- Bugfix: if WPL-Files with old Version 3 are loaded from SD-Card, -1 is now a valid camera angle and 121 is 'AUTO'
- Bugfix: WPL Fileversion now '4' if written by NC to SD-Card
- Bugfix: PointList[i].CamAngle is now a s8 instead u8 if written by NC to SD-Card
- if compiled as Follow-Me Transmitter: 121 is 'AUTO' -> warning old Follow-Me transmitter won't set the camaera angles correctly
- OrientationGyroCompassCorrected --> in case the rotated front direction in the setting is used
-> HoTT
-> Logfiles |
|
/tags/V2.22a
|
| 899 |
2136 d 9 h |
holgerb |
/tags/V2.20h/Hex-Files/ |
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/Hex-Files/Navi-Ctrl_STR9_V0_28M.hex
|
| 898 |
2136 d 9 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
/tags/V2.20h/Hex-Files/Navi-Ctrl_STR9_V0_28M.hex
|
| 897 |
2136 d 9 h |
holgerb |
/tags/ |
Update for 2.20h: The older V2.20h was the Betaversion 2.21 by mistake |
|
/tags/V2.20h
|
| 896 |
2136 d 9 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
|
| 894 |
2136 d 9 h |
holgerb |
/tags/ |
Update for 2.20h: The older V2.20h was the Betaversion 2.21 by mistake |
|
/tags/V2.20h
|
| 892 |
2136 d 9 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 |
2136 d 9 h |
holgerb |
/tags/ |
This was the Betaversion 2.21 |
|
/tags/V2.20h
|
| 882 |
2200 d 10 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 |
2235 d 9 h |
ingob |
/tags/V2.20e/Hex-Files/ |
|
|
/tags/V2.20e/Hex-Files/Navi-Ctrl_STR9_V2_18b.hex
|
| 875 |
2235 d 9 h |
ingob |
/tags/V2.20f/Hex-Files/ |
|
|
/tags/V2.20f/Hex-Files/Navi-Ctrl_STR9_V2_18b.hex
|
| 874 |
2235 d 9 h |
ingob |
/tags/V2.20g/Hex-Files/ |
|
|
/tags/V2.20g/Hex-Files/Navi-Ctrl_STR9_V2_18b.hex
|
| 873 |
2242 d 9 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 |
2272 d 9 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 |
2326 d 8 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 |
2523 d 9 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 |
2556 d 6 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 |
2556 d 6 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 |
2556 d 6 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 |
2556 d 6 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 |
2556 d 10 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 |
2692 d 9 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 |
2921 d 9 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 |
2921 d 9 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 |
2922 d 3 h |
holgerb |
/tags/V2.14e/ |
2.14e (19.04.2016)
- no altitude limitation if altitude sensor is defective |
|
/tags/V2.14e
|
| 750 |
2941 d 5 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 |
2965 d 4 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 |
2972 d 2 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 |
2986 d 7 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 |
3112 d 2 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 |
3136 d 3 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 |
3136 d 3 h |
holgerb |
/tags/V2.10f/Hex-Files/ |
2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost" |
|
/tags/V2.10f/Hex-Files
|
| 667 |
3136 d 3 h |
holgerb |
/tags/V2.10f/ |
2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost" |
|
/tags/V2.10f
|
| 657 |
3201 d 23 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 |
3201 d 23 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 |
3202 d 10 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 |
3203 d 2 h |
holgerb |
/tags/ |
2.10e reported "Update Rate" |
|
/tags/V2.10e
|
| 652 |
3203 d 3 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 |
3203 d 3 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 |
3203 d 3 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
|