Open Solo 2.5-RC2 is out

Pedals2Paddles · Oct 6, 2017

So when you tap the Wipe package, what does it do?

David Boulanger · Oct 6, 2017

Pedals2Paddles said:
So when you tap the Wipe package, what does it do?

Wipe did nothing. At the moment I have installed open solo on it again. Nothing else would do anything. I now have 3.5.3 on it and will give the parameters a look over before I fly. May take the gimbal off. Wipe, loading 3.5.3 did absolutely nothing.

David Boulanger · Oct 7, 2017

Pedals2Paddles said:
@USMC86, your problem is not the same. You didn't load the parameter files.

@David Boulanger The logs just stop shortly after you takeoff. They show no errors or failures. They just stop in mid-air. This usually indicates a sudden loss of electrical power, or that the pixhawk just shut down. I also see "long loop" errors in the log analyzer, which I think should never happen. That indicates some code in ArduCopter is dragging it's feet slowing the processor down. In 5 years, I've never seen that. This leads me to believe the FW installed on the Pixhawk may just be corrupt.

1. Install the Wipe package in Solex and reboot. It will install and do it's beeping and boopping thing.
2. Install the ArduCopter 3.5.3 package in solex and reboot. Again it will beep and boop
3. Install the ArduCopter 3.5.x parameters package in Solex. Also install the Here and landing gear if you have any of those modes. Reboot.
4. Recalibrate as usual since everything is wiped out.
5. Do a low and slow test flight and shoot some logs over.

I suspect that will take care of it.

For some reason the Wipe and rest of the process is doing as expected this morning. Lots of beeping and tones.

David Boulanger · Oct 7, 2017

Baker 6 3.5.0
O.K.. The Wipe and reload of 3.5.3 plus parameters all went good this morning. After a quick bench test I still have that PM fail with some slow looping. What I find interesting is... Look at the 3.5.0 logs I have put here from late August. Four great flights with my Green Cube Solo. All had the same failure on the auto analyzer yet flew great.

carpy · Oct 7, 2017

David Boulanger said:
Baker 6 3.5.0
O.K.. The Wipe and reload of 3.5.3 plus parameters all went good this morning. After a quick bench test I still have that PM fail with some slow looping. What I find interesting is... Look at the 3.5.0 logs I have put here from late August. Four great flights with my Green Cube Solo. All had the same failure on the auto analyzer yet flew great.

Hmm...I see no smoking guns when comparing parameters except MOT_THST_HOVER is a little interesting (< is 3.5.0, > is 3.5.3):

24c24
< PARM RTL_ALT 3100
---
> PARM RTL_ALT 3300
66a67,68
> PARM ARMING_VOLT_MIN 0
> PARM ARMING_VOLT2_MIN 0
78c80
< PARM ACRO_YAW_P 1.39999998
---
> PARM ACRO_YAW_P 1
114,116c116,119
< PARM COMPASS_OFS_X 69.8881302
< PARM COMPASS_OFS_Y 83.5095291
< PARM COMPASS_OFS_Z 90.0958557
---
> PARM LGR_STARTUP 0
> PARM COMPASS_OFS_X 68.3698044
> PARM COMPASS_OFS_Y 79.645607
> PARM COMPASS_OFS_Z 87.375824
127,129c130,132
< PARM COMPASS_OFS2_X -90.4185028
< PARM COMPASS_OFS2_Y -46.1617126
< PARM COMPASS_OFS2_Z 169.054718
---
> PARM COMPASS_OFS2_X -95.7375031
> PARM COMPASS_OFS2_Y -56.2915878
> PARM COMPASS_OFS2_Z 126.891701
236c239
< PARM ATC_ACCEL_Y_MAX 9800
---
> PARM ATC_ACCEL_Y_MAX 7000
312,313c315,316
< PARM AHRS_TRIM_X -0.0125908917
< PARM AHRS_TRIM_Y -0.0089816507
---
> PARM AHRS_TRIM_X -0.0130557138
> PARM AHRS_TRIM_Y -0.0091167139
376c379
< PARM GND_ABS_PRESS 101648.234
---
> PARM GND_ABS_PRESS 101421.141
381c384
< PARM GND_ABS_PRESS2 101616.32
---
> PARM GND_ABS_PRESS2 101388.422
437c440
< PARM MOT_THST_HOVER 0.265781194
---
> PARM MOT_THST_HOVER 0.643509209
597,600c600,603
< PARM STAT_BOOTCNT 17
< PARM STAT_FLTTIME 1502
< PARM STAT_RUNTIME 9929
< PARM STAT_RESET -504921568
---
> PARM STAT_BOOTCNT 9
> PARM STAT_FLTTIME 33
> PARM STAT_RUNTIME 3639
> PARM STAT_RESET -504921600

David Boulanger · Oct 7, 2017

I don't know. It was just the first two flights with open solo and 3.5.2 that it shut down a few feet up and crashed. After that it seemed O.K.. Plan on trying tomorrow if the wind is down. I have to research what this PM slow looping thing is. Seems like I've had it all the time with the Green Cube but all was well.

David Boulanger · Oct 7, 2017

PM = Performance Management. Read a little about it on Arducopter.org. I wonder if I got a bad cube?

XevetS · Oct 7, 2017

Just ordered a green cube from proficnc they are back in stock..

David Boulanger · Oct 7, 2017

That's where I got mine from. Can't figure this out.

XevetS · Oct 7, 2017

David Boulanger said:
That's where I got mine from. Can't figure this out.

Ill keep you posted on my install, where do they ship from anyway? I'm in northern Florida btw nature coast.

David Boulanger · Oct 7, 2017

XevetS said:
Ill keep you posted on my install, where do they ship from anyway? I'm in northern Florida btw nature coast.

Overseas somewhere.

carpy · Oct 7, 2017

David Boulanger said:
PM = Performance Management. Read a little about it on Arducopter.org. I wonder if I got a bad cube?

I don't think so. I get it too (without the green cube). I'll see if I can dig into the log analyzer code and see what's going on.

XevetS · Oct 7, 2017

David Boulanger said:
Overseas somewhere.

Oh ok that narrows it down?

carpy · Oct 7, 2017

carpy said:
I don't think so. I get it too (without the green cube). I'll see if I can dig into the log analyzer code and see what's going on.

Geez, anyone know what this stuff means.

ardupilot/TestPerformance.py at master · ArduPilot/ardupilot · GitHub

David Boulanger · Oct 8, 2017

XevetS said:
Oh ok that narrows it down?

Asia if IIRC.

USMC86 · Oct 8, 2017

The Green Cube is amazing. It’s like going from a tricycle to a bicycle- Solo is a lot more responsive.

David Boulanger · Oct 8, 2017

I just got back from a test flight. Will down load logs. Flew great. The one variable that seemed to cause my problems was the testing the 9dbi alfa antennas.

Pedals2Paddles · Oct 8, 2017

It is not possible for alfa antennas to cause what you're experiencing. I think that was coincidence.

David Boulanger · Oct 8, 2017

Pedals2Paddles said:
It is not possible for alfa antennas to cause what you're experiencing. I think that was coincidence.

Could be. I will post a log of todays 3.5.3 flight in a little while.

David Boulanger · Oct 8, 2017

Solo 3.5.3 good flight
Here is the log from today. So from what I have been able to come up with is this. No problems with Green Cube flying wise on 3.5.0, 3.5.2, 3.5.3. Except two take offs failing at about 2 or 3 feet in altitude and crashing to the ground. Both crashes happened with a certain type of antenna. Just did more bench testing and if I turn off the battery or disconnect it while armed the Gopro continues to record video. In both my crashes, If you want to call them that, the Gopro stop recording the moment the props stopped spinning. Leading me to speculate that for some reason I disarmed a few feet above ground on takeoff. I do still have this PM failure with some slow looping but in all of my flights, 2 hrs worth with the green cube, I have had this and all has been well.