MikroKopter - Forum » MikroKopter - general » English: PublicBeta V2.15

English: PublicBeta V2.15

Neues Thema Antwort

Seite: 1 2 >

Autor Neuer Beitrag
Entwickler, Admin
Registriert seit: Feb 2006
Beiträge: 5790
Ort: Ostfriesland
Hello,

we habe a new Beta-Version.

Most important changes:

SD-Card:
Five times higher data rate when reading the Logfiles from SD-Card (only via direct MKUSB-Connection / not via wireless datalink)

Parachute:
Input for parachute release -> brakes the motors to zero rpm in case of a Parachute release and makes the logfiles entries
This is a License feature and can not be activated accidentaly.

Calibration values:
Better check of the calibartion values. Compares the values to the offset-Points strored via the last ACC-Calibration.
Differences >0,5% will give an error message.
This avoids wrong offset values if the MK is moving during calibration.

Waypoint-information in Jeti-Menu

User image

* Waypoint x / y
* Distance to that point
* waiting time at target
* current Altitude
* Altitude setpoint

Error compensation of the altitude sensor

The temperature error of the altitude sensor of FlightControl V3 can be compensated now.
The factor is x cm per °C

Note: this is not possible in older FC 2.x, because the baro sensor has no temperature sensor.
FlightControls purchased after 1st October 2016 will already be calibrated in our factory

User image


OEM-String
OEM-String for companies who build MikroKopters under other brand-names

User image

User image


Auto switch off after landing

The MK switches off after the following auto-landings:
1. auto landing via switch on the transmitter
2. auto landing after RC lost failsafe
3. auto landing at undervoltage
4. Waypoint (Landing Point)


Landing Points

There is a new type of Waypoints: Landing Points

User image

The MK flies to the set altitude (i.e. 15m). After reaching the position, the MK lands vertically.
The motors will switch off after landing.
A landing point acts also as Failsafe-Point

Regards,
Holger


Here the complete ChangeLog:

FlightControl
FC 2.15
- Parachute-Input for FC3.0 -> fast swicth off on IO1 (License feature required)
- Fixed: PPM_Diff[] could contain a value if the channels are > 128. That had effect to the Motor-Switch function.
- New Bit: CFG3_RISE_FIRST_WAYPOINT -> "Rise on first Waypoint" can be disabled by Parameter
- OEM-String for customers who build MikroKopters under other brand-names
- REDUNDANT_SLAVE: small Bugfix -> sometimes "SL23: Motor Restart" before liftoff
- Redundance_Master: small Bugfix -> Lost of serial bus not reported
- set GPS-Switch to FREE if GPS is deactivated in the settings
- unlimited Failsafe-Time possible if License is installed
- CamCtrlCharacter in Text-Telemetry
- last Gyro calibration values stored in EEPROM
- do not accept a calibration if the zero-values have > 0,3% error compared to the ACC-Calibration
- \n\r replaced by \r\n

NaviControl
- 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
- FC temperature in the logfile (before and after the flight)
« Bearbeitet von HolgerB am 19.10.2016 16:24. »
Mitglied
Registriert seit: Nov 2012
Beiträge: 244
Ort: Ankara
Dear Holger,

1-Can the Calibration Values comparison for ACC-calibration be applied for Gyro-Calibration to understand MK is moving during calibration (To prevent bad gyro calibration).

2- Is it possible to log Home-Point (I know that the first line of log-file gives this, the point (Home Point) that MK finds the 6 and more satellites and Waypoints (P1-P2-P3-..etc) Latitude - Longitude into SD card ?

Thanks for new firmware

Regards
Mehmet
« Bearbeitet von mehmetyldz87 am 23.09.2016 12:09. »
Entwickler, Admin
Registriert seit: Feb 2006
Beiträge: 5790
Ort: Ostfriesland
1. yes, it is the Gyro-calibration what I am talking about.
The Gyro-calibration data is also written into the EEPROM during ACC-Calibration

2. do you want it in the header of the Logfile?
Mitglied
Registriert seit: Aug 2010
Beiträge: 115
Ort: Taiwan
Hello mikrocopter team :

Thank you all for the new firmware

Best Regards
Mitglied
Registriert seit: Nov 2012
Beiträge: 244
Ort: Ankara
HolgerB meinte
1. yes, it is the Gyro-calibration what I am talking about.
The Gyro-calibration data is also written into the EEPROM during ACC-Calibration

2. do you want it in the header of the Logfile?


1- Ok :)

2- Yes, I want it in the header of the LogFile.

Also , last request.

In this version , Do you plan to apply this request ?

http://forum.mikrokopter.de/topic-50969.html


Thanks for your time and support

Regards
Mehmet
Mitglied
Registriert seit: Sep 2015
Beiträge: 132
Thx Holger!

Best regards
Peter
Mitglied
Registriert seit: Jun 2011
Beiträge: 82
Please add a setting to take into account the Z GPS data (will be used for calculating altitude when using RTK GPS).

Please add a setting to activate aggressive waypoint route following in order to compensate wind while flying waypoints with RTK GPS. The copter will come back to the route line when wind have pushed it away instead of flying straight to the next waypoint in diagonal.
« Bearbeitet von alex54 am 28.09.2016 14:05. »
Entwickler, Admin
Registriert seit: Feb 2006
Beiträge: 5790
Ort: Ostfriesland
Error compensation of the altitude sensor

The temperature error of the altitude sensor of FlightControl V3 can be compensated now.
The factor is x cm per °C
First this factor must me measured.

Note: this is not possible in older FC 2.x, because the baro sensor has no temperature sensor.

Step 1: Start calibration

User image

Press the last key in the virtual menu.

Step 2: warm up FlightControl slowly

User image

This works pretty well by a lamp.

User image

If the heating is too fast, you get a message "Heater off!"

User image

If the value dT (warming in °C) reaches at least 13°C, you will get the message "Wait...".

User image
Switch off the heater now and wait for the "Okay" message

Step 3: Save calibration data

You can see the factor in x cm per °C now

User image

Press the last key to save.

The value can be changed later by the KopterTool also.

User image

User image
« Bearbeitet von HolgerB am 30.09.2016 14:36. »
Mitglied
Registriert seit: Sep 2013
Beiträge: 37
Thank you for this calibration, Holger. Is there a new pressure sensor on the latest V3.0 FlightCtrls?
Entwickler, Admin
Registriert seit: Feb 2006
Beiträge: 5790
Ort: Ostfriesland
dleroi meinte
Is there a new pressure sensor on the latest V3.0 FlightCtrls?

No, it is the same type.
But the pressure sensors on the FlightControls will be already be calibrated from now on.

The calibration factor will be stored in the EEPROM and the temperature compensation will be active if the Firmware V2.15 or newer is installed.
Mitglied
Registriert seit: Sep 2013
Beiträge: 37
This is a great new feature.

Is the temperature signal from the "do not connect" pins of the pressure sensor, or from a temperature sensor on the FC board?
Mitglied
Registriert seit: Nov 2012
Beiträge: 244
Ort: Ankara
Dear Holger,

What is your idea about post #5 ?
Entwickler, Admin
Registriert seit: Feb 2006
Beiträge: 5790
Ort: Ostfriesland
Update 19.10.2016

Auto switch off after landing

The MK switches off after the following auto-landings:
1. auto landing via switch on the transmitter
2. auto landing after RC lost failsafe
3. auto landing at undervoltage
4. Waypoint (Landing Point)


Landing Points

There is a new type of Waypoints: Landing Points

User image

The MK flies to the set altitude (i.e. 15m). After reaching the position, the MK lands vertically.
The motors will switch off after landing.
A landing point acts also as Failsafe-Point
Mitglied
Registriert seit: Nov 2012
Beiträge: 244
Ort: Ankara
Dear @HolgerB

When do you plan to publish the final version ( v2.16) firmware ? and again What are your thoughts on these issues? ( #5 )

Regards
Mehmet
Mitglied
Registriert seit: Nov 2012
Beiträge: 244
Ort: Ankara
And do you plan to prepare a tutorial and documentations wiki page for developers with new firmware V2.16?
Entwickler, Admin
Registriert seit: Feb 2006
Beiträge: 5790
Ort: Ostfriesland
Hello,

we have a new Beta-Version

Laser Sensor

externer Link:
User image
(We will have this units in our shop soon)

The laser sensor measures the distance to an object in cm.
The value is only displayed and stored in the logfile.
It is e.g. for doing measurements by camera.
Marine researchers use it for determine the size of whales.

User image

The values are displayed here:
- Analogdata
- virtual display
- Logfile (camera log and GPX)
- HoTT-Telemetry

This is how a logfile looks like when crossing a house:

User image


Others:
Earlier error message in case of SPI communication problems (between NC and FC)
« Bearbeitet von HolgerB am 02.12.2016 13:26. »
Mitglied
Registriert seit: Nov 2012
Beiträge: 244
Ort: Ankara
Will the laser sensor be used only for collecting the data, or will it affect the altitude stabilization algorithm?
Entwickler, Admin
Registriert seit: Feb 2006
Beiträge: 3799
Ort: Ostfriesland
mehmetyldz87 meinte
Will the laser sensor be used only for collecting the data, or will it affect the altitude stabilization algorithm?


Zitat
The value is only displayed and stored in the logfile.
Mitglied
Registriert seit: Nov 2012
Beiträge: 225
Ort: Landshut,BY
IngoB meinte
mehmetyldz87 meinte
Will the laser sensor be used only for collecting the data, or will it affect the altitude stabilization algorithm?


Zitat
The value is only displayed and stored in the logfile.


:D

...aber vielleicht ja doch irgendwann...?
Das Interesse diesbezüglich ist sicherlich GROSS! ;)

Cheers,

Steph
Mitglied
Registriert seit: Feb 2015
Beiträge: 106
Ort: Brazil, Florianopolis, SC
Hi Holger,

Very good this accessory!
Can you pass more technical details of the laser sensor?

I want to study for the use of the laser sensor to calculate the tree distance of the high voltage line during the inspection using MK Copter.

Thanks,

João Marcelo
Mitglied
Registriert seit: Sep 2013
Beiträge: 37
João,

It is this one:

http://www.lightware.co.za/shop/en/drone-altimeters/51-sf11c-120-m.html

-Don
Mitglied
Registriert seit: Feb 2015
Beiträge: 106
Ort: Brazil, Florianopolis, SC
dleroi meinte


Thank´s Don.
Mitglied
Registriert seit: Jul 2012
Beiträge: 29
hey guys i have one set-up on my gimbal using pixhawk for measuring distance is sent to a to a fpv screen. You can check out my set-up here

http://forum.freeflysystems.com/index.php?threads/laser-altimeter.8366/
Mitglied
Registriert seit: Nov 2012
Beiträge: 244
Ort: Ankara
Dear @HolgerB

Could you share us a video with new features ?
« Bearbeitet von mehmetyldz87 am 29.11.2016 10:46. »
Mitglied
Registriert seit: Nov 2012
Beiträge: 244
Ort: Ankara
Dear @Holger

Do you plan to produce a I2C splitter for FC 3.0 ? or Is there a different method? How we will use the CamCtrl/I2C and Laser Distance Sensor same time?

Also SF11 laser distance sensor + I2C Interface is too expensive!!!!
« Bearbeitet von mehmetyldz87 am 02.12.2016 08:46. »

Neues Thema Antwort

Seite: 1 2 >

MikroKopter - Forum » MikroKopter - general » English: PublicBeta V2.15