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
815 968d 22h 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
 
812 969d 02h 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
 
796 1105d 01h 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
 
756 1334d 01h holgerb /tags/V2.14e/Hex-Files/ 2.14e (19.04.2016)
- no altitude limitation if altitude sensor is defective
 
755 1334d 01h holgerb /tags/V2.14e/Hex-Files/ 2.14e (19.04.2016)
- no altitude limitation if altitude sensor is defective
 
753 1334d 19h holgerb /tags/V2.14e/ 2.14e (19.04.2016)
- no altitude limitation if altitude sensor is defective
 
750 1353d 21h 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 1377d 20h 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 1384d 18h 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 1398d 23h 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 1524d 18h 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 1548d 19h holgerb /tags/V2.10f/Hex-Files/ 2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost"
 
668 1548d 19h holgerb /tags/V2.10f/Hex-Files/ 2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost"
 
667 1548d 19h holgerb /tags/V2.10f/ 2.10f (18.09.2015)
- Improved behaviour regaring "GPS Fix lost"
 
657 1614d 15h 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 1614d 15h 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 1615d 02h 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 1615d 18h holgerb /tags/ 2.10e reported "Update Rate"  
652 1615d 19h 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 1615d 19h 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
 

Show All