Good evening,
My last test with my Penguin (2.74b) was a complete failure. Or maybe I failed IT (still learning the ropes). Anyhow, when I switched from Manual to Auto to fly my written course, the AP cut throttle in half and went a completely different direction than WP1. It also would not maintain its altitude.
Is there a way someone here could look at my logs and tell me if I have an error in my set-up? Heck, even looking at my logs, I'm not sure what to look for. What does ATT, CTUN, and NTUN stand for?
Thank you for your time and knowledge, in advance.
Chris
[EDIT]
Apparently I can only download 3 files...? There are 11 total. If more information/ logs are needed, let me know.
Replies
Hey Chris,
If your learning curve is anything like over at the DragonLink thread, you will be teaching us how its done in a few months. I don't have time to try to solve your issue tonight, but maybe I can answer a few questions. The first .log might have the needed data, but the other ones are too small to be useful, so they can be tossed. A log is generated anytime the APM is powered up, so lots of junk ones are made and they have no useful timestamp which makes it a real bitch to find the useful one.
TUN stands for tuning. NTUN is Navigation Tuning, and I'm guessing CTUN is Control Tuning. ATT stands for attitude. They just like catagories that data types are grouped under. On the Mission Planner Log Browser, if you click on one of the header cells across the top of the data you will see a filter for these catagories. If you select ATT for example, you will then see the headers change to the data types of: Roll, Pitch, and Yaw. Now click and highlight anyone of the cells below the header row, then click Graph this Data Left and you will see that data type graphed for the whole flight. You can zoom in on an event, and graph multiple data types against each other. It doesn't help that none of the TECS data has any titles, so there is no way to know what data you are looking at. Paul?!
Now figuring out exactly what you need to graph to find your problem is a tougher question. Hopefully someone else can help. The telemetry logs are much easier to deal with than the .log files. I am guessing that you are an FPV guy that didn't see the need for telemetry. I was too, but know I always fly with telemetry. The tlogs and tuning are one reason, but its also good redundancy.