Should I expect a crash at some point?
Nervously I took the Spy 750 Y6 up for the first time in over 3 weeks (had a warm spell of 25F today).
In stab it flies great, then switching to poshold it seemed fine, but did the twitchy thing again for a few seconds here and there, then seemed to smooth out (subjective). I brought it down and hovered nearby where it stayed rock steady for a minute or so and landed.
So, what does it mean when INAVerr goes to 255 and stays there? From what I understand it is the FC not receiving data from the GPS properly. Apparently this copter has done it from day one since transplanting the PIxhawk and running on AC3.2 and 3.2.1, with the 3DR GPS and the current CSGShop Neo-M8N. These errors did not exist on the Y6B with 3.1.5 and the 3DR GPS.
Any help is appreciated.
Replies
My log is very large almost 27 MB.....there is a 7MB limit here ...how do I post my logs??
AKcopter,
If you post your log, I'd like to run it through Excel.
Very gppd!
I just check for M8N firmware update. There is none yet available.
Do you know of a way to set Arducopter to interface the GPS at a higher baud rate?
How about update rate?
I just checked for GPS parameters. There is a GPS_type1 and 2. Apparently you can have 2 GPS's. That might be interesting. My type is set to 1 : auto. Type 2 is Ublox.
I wonder what would happen if you set type to ublox.
According to the following reference, Pixhawk recognizes the Neo-M8N and automatically sets the parameters. All the user needs to is reset the GPS to default first using U-Center.
http://www.rcgroups.com/forums/showthread.php?t=2353323
Here's the raw data in Excel for INVerr
Here is the data as seen in MP. It's missing the time values, but I wanted to get this posted while I remember.......going to try another quick flight before it gets dark.
The first graph above should read "GPS"
I flew for ~6 minutes. The logging was changed to 'Almost All'.
I also changed the ins_mpu6k_filter from 0 (default) to 20. Default I believe is 42hz. I don't have issues with vibration, but have read that 20 can smooth out issues with "twitching" and such. It did seem to fly very well, but that's neither here no there for this topic.
I digress.
No logging was performed before arming. INAVerr was 255 straight across.
The GPS values, which I assume (nobody has said, just guessing) is the raw data used to capture the INAVerr. I'm not getting why in this case under PM it shows 255 throughout the flight, yet under GPS it varies. Having not studied the code to find how INAVerr is calculated, I'm probably totally off base. I don't care to learn the code, it reminds me of work too much :) (is there a detailed summary of how to analyze logs?) I just wanna fly and have confidence it will come back and in one piece.
And the kmz. No gaps? Huh?
Wow! I'm not alone. I'd have to look at the logs again, but it climbs to 255+ quite fast. The twitching may not be related, and not knowing what INAVerr really is about makes it worse. I think there is an issue in GPS modes because the copter flies fine in stab mode without simple/super simple mode.
CSGShop did not even attempt to explain what may be the problem, only place the blame on PIxhawk. I linked to DIY, but apparently they are not interested in helping.
I still have not uploaded the data and load into Excel, but the gaps are plainly visible. If you create a kmz file for Google Earth, look at the pattern of data gaps while in poshold.
I'm not ready to toss the CSGShop yet; will put the 3DR GPS back on and test, but I thought it was happening with it on as well; not positive to be honest. In any case, based on what I've observed and Randy's caution that it may be a real problem, my confidence level is about 5% right now to go back up. This copter has not been crashed yet, and I'd like to keep it that way especially due to mechanical failure.
In about a month I'll have another copter put together with a new FC/GPS to see how it goes, but it won't be a GPS from CSGShop this time.
Hi DG,
I too see "missing" datapoints in the KMZ file. See attached picture. They do not seem to be at the regular intervals you see them though, which could explain why your INAVErr seems to climb to 255 (the max) faster than mine (?).
Hans.
Is your satellite count good? I had one copter where the satcount would go to 0 for half a sec or so. The copter would fly away. I got rid of that gps to cure the problem, and have started using Neo M8N. Now I get 16-20 sats and constant reception.
If your connections are good, not routed near interference, twisted.....and I would guess it is not likely the wires, I would suspect GPS reception. There are definately not-so-good units out there.
They may be other ways to check this, which I dont know right off. There is a quality term for the gps. I have not used it. I simply lost sats.
-
2
-
3
-
4
-
5
-
6
of 6 Next