ezio wrote:I have added it too to the logs converter
It doesn't work on my Note 3
I can't open .mission file in the program (log converter), it sees .el1 files only.
ezio wrote:I have added it too to the logs converter
NNagib wrote:ezio wrote:I have added it too to the logs converter
It doesn't work on my Note 3
I can't open .mission file in the program (log converter), it sees .el1 files only.
dawagner wrote:I have the Multiwii pro 3.0 with version 2.3, when I connect to the ez-gui the mission planner disappears. Do I have to comment this out in the sketch file for the mission planner stuff to work. Or does mission planner just not work with 2.3?
dawagner wrote:Does this firmware disable gps hold and RTH? They no longer work even though I have them setup as aux positions.
dawagner wrote:Did you ever get the POI working ezio? Mine seems to only look at the poi for the single way point that it was programmed by. The rest of the flight the copter faces the waypoint.
NNagib wrote:@ezio, I use full version of ez-gui and log converter. These are wonderful apps, indeed. I have a question for you:
is there a simple way to load a .mission file in google earth? I create .kml file manually sometimes, but that's boring.
I would like to compare mission and logged flight path in google earth. Tnx
carlonb wrote:Hi Guys,
It's possible try Autolanding without enabling or selecting any waipoint but only using an RC switch ?
What do I need to enable in GUI ?
I've already read all this thread, but I've not found detailed info.
Thanks
Carlo
stronnag wrote:carlonb wrote:Hi Guys,
It's possible try Autolanding without enabling or selecting any waipoint but only using an RC switch ?
What do I need to enable in GUI ?
I've already read all this thread, but I've not found detailed info.
Thanks
Carlo
You need to assign a TX switch to the land function. The following works for me (indeed I used it today). Beeper is optional, of course.
stronnag wrote:carlonb wrote:Hi Guys,
It's possible try Autolanding without enabling or selecting any waipoint but only using an RC switch ?
What do I need to enable in GUI ?
I've already read all this thread, but I've not found detailed info.
Thanks
Carlo
You need to assign a TX switch to the land function. The following works for me (indeed I used it today). Beeper is optional, of course.
stronnag wrote:I usually LAND from POSHOLD, and put the throttle down as MW-nav is controlling it. It seems (or may be it's my imagination) to power off quicker that way.
Just my experience, not really sure what the rules are.
Code: Select all
#define LAND_DETECT_THRESHOLD 40 //Counts of land situation
#define BAROPIDMIN -180 //BaroPID reach this if we landed.....
//Check if we landed or not
void check_land()
{
// detect whether we have landed by watching for low climb rate and throttle control
if ( (abs(alt.vario) < 20) && (BaroPID < BAROPIDMIN)) {
if (!f.LAND_COMPLETED) {
if( land_detect < LAND_DETECT_THRESHOLD) {
land_detect++;
}else{
f.LAND_COMPLETED = 1;
land_detect = 0;
}
}
}else{
...
...
}
}
}
DorsetFlyer wrote:I think I must have been unlucky with dud HobbyKing flight controllers. I would be tearing my hair out if I had any to spare! I shall get a genuine Crius AIO. Hope the ones advertised by the likes of Good Luck Buy are the real McCoy and not some other dodgy offering.
stronnag wrote:Indeed, disarm appears to be somewhat random.
carlonb wrote:stronnag wrote:Indeed, disarm appears to be somewhat random.
Hi stronnag and @eosbandi,
Now I understood why the disarm appears random after autoland, this because of your own P term in alt hold PID.
I realized that #define BAROPIDMIN -180 (in GPS.cpp Land detection routine - see code in my previous post -) is strictly related to the P term of altitude hold PID (it was logical to get there before).
If P=6.4 as per default, BaroPID will decrease under -180, so the autoland can disarm the motors.
In my tests, my P was 2.3 so, my BaroPID stop to decrease at -112, so no disarm happened.
Will be a good solution, to make it working without changing #define BAROPIDMIN, to pre-calc (if possible) and then assign to BAROPIDMIN the min pre-calculated value with the P of users in order to avoid the issue where do not disarm if the P of altitude hold is changed from default or too low.
Is this an Eosbandi job ?
Cheers
Carlo
-ralf- wrote:Welcome back, András .... we missed you
EOSBandi wrote:Hi Carlo,
You are perfectly correct. I'll change the baropidmin into a configurable parameter.
EOSBandi wrote:-ralf- wrote:Welcome back, András .... we missed you
Thanks,
I'm slowly getting traction again... it was a rough couple of months...
Now, I'm catching up with the changes in the repo, and integrate them to the navi codebase... eventually i'll check in navi code to the main repo....
Andras
Alexinparis wrote:EOSBandi wrote:-ralf- wrote:Welcome back, András .... we missed you
Thanks,
I'm slowly getting traction again... it was a rough couple of months...
Now, I'm catching up with the changes in the repo, and integrate them to the navi codebase... eventually i'll check in navi code to the main repo....
Andras
Hi Andras,
I'm glad to see you again here
I begun some times ago to merge your nav code in the main repo, but no check in so far
what would you prefer ?
- you think it will be easier for you and I let you do it
- or I finish the most properly I can the integration based on the current nav code
-ralf- wrote:Welcome back, András .... we missed you
-ralf- wrote:OK, r1694 is online ......
-It doesn't run on 328er or 32u4 platforms
-there is no MultiWiiConf, it works with EZ-GUI and WinGUI-Navi-Beta
Right?
Code: Select all
void GPS_bearing(int32_t* lat1, int32_t* lon1, int32_t* lat2, int32_t* lon2, int32_t* bearing) {
int32_t off_x = *lon2 - *lon1;
int32_t off_y = (*lat2 - *lat1) / GPS_scaleLonDown;
*bearing = 9000 + atan2(-off_y, off_x) * 5729.57795f; //Convert the output redians to 100xdeg
if (*bearing < 0) *bearing += 36000;
}
carlonb wrote:Hi friends,
It's almost 2 or 3 weeks that I use navi b7 from Eosbandy and looking at the code I've not understood this:
GPS.cpp fileCode: Select all
void GPS_bearing(int32_t* lat1, int32_t* lon1, int32_t* lat2, int32_t* lon2, int32_t* bearing) {
int32_t off_x = *lon2 - *lon1;
int32_t off_y = (*lat2 - *lat1) / GPS_scaleLonDown;
*bearing = 9000 + atan2(-off_y, off_x) * 5729.57795f; //Convert the output redians to 100xdeg
if (*bearing < 0) *bearing += 36000;
}
Why GPS_scaleLonDown is applied to lat ? I think it must be applied to Lon
EOSBandi wrote:carlonb wrote:Hi friends,
It's almost 2 or 3 weeks that I use navi b7 from Eosbandy and looking at the code I've not understood this:
GPS.cpp fileCode: Select all
void GPS_bearing(int32_t* lat1, int32_t* lon1, int32_t* lat2, int32_t* lon2, int32_t* bearing) {
int32_t off_x = *lon2 - *lon1;
int32_t off_y = (*lat2 - *lat1) / GPS_scaleLonDown;
*bearing = 9000 + atan2(-off_y, off_x) * 5729.57795f; //Convert the output redians to 100xdeg
if (*bearing < 0) *bearing += 36000;
}
Why GPS_scaleLonDown is applied to lat ? I think it must be applied to Lon
in this case scaleLonDown is actually streches the latitude to match longitude and this converts the local area to a normal grid, so atan2 can be used...
It was Jason Short's original idea back in 2010.... (http://diydrones.com/forum/topics/getbe ... erstanding)
(originally it was int32_t off_y = (*lat2 - *lat1) * GPS_scaleLonUp; Where GPS_scaleLonUp was 1/scaleLonDown....
carl1864 wrote:I'm trying this Nav version for the first time, but after hours, I cannot get it to work.
I had a fully working quad with multiwii 2.3, on a crius aiop board, and using the EZ Gui App to configure over bluetooth.
However after attempting to use this nav version, I am completely unable to connect to EZ Gui. I just get constant "No Data Recieved" Errors, even though I have nav protocol selected. I've tried the latest b7, as well as b5 baro fix. I cleared EEPROM multiple times, have compiled both nav versions multiple times, I made sure EZ Gui is updated, double checked all settings in config.h to match my working settings from version 2.3.
Anyone have any idea what the problem is?