My situation is a bit unusual. I’ll have to fly the plane on a completely separate system than ArduPlane, but i want to use the latter for live and sd telemetry.
My big question is: will i be able to see the live flight data from these sensors and this flight controller, considering i won’t be flying the plane trough it?
The second one is, will this combination of sensors and controller record the flight data on the onboard sd?
I hope i’m posting this in the right place, and I want to thank everyone who will help!
Little update: I got word from Matek that the current sensor (I2C-INA-BM) doesn’t have default firmware that works with Arduplane, so i’d need to make one.
Do you think i could just use the built in power monitoring in the FC?
I bought the fc and the listed sensors, and for now I managed to get the IMU on the fc to show useful data in Mission Planner over wireless connection too.
In the next few days all other sensors will be connected to the F405-WTE, and I’ll try to configure them properly to see if I’m still able to get the data wirelessly (using the built in ESP8622 on the board).
I’m still having some issues with blackbox data recording. I’ve read that to start the recording the plane needs to be armed, but it refuses to do so until the GPS is properly calibrated (hard to do without having one installed ). If it still fails after that, I’ll try to flash the custom build firmware.
Thanks again to the both of you for helping me out. It’s beyond appreciated.
I’ll try to remember to post updates once they happen.
If it fails after that then post here and we’ll help you figure it out. GPS position takes a while to settle down, it’s not just satellite count. That said the M10Q has got positions for me inside buildings that other receivers would do nothing.
Just got done installing the sensors. It was a unpleasant job, mainly due to not having the right connectors. But, the GPS and all sensors are connected and working (except the external current sensor, the I2C-INA-BM).
I’ll try to calibrate all the sensor and arm the plane when i get the chanche. I’m still having issues saving the flight log and data to the sd card, but i’m still on the stock firmware build. I’m guessing I’ll have to flash a custom one.
Before doing that, though, I’ll try calibrating all the sensors properly so the Mission Planner will let me arm the plane (although I’ll never connect a RC to it). If that doesn’t fly (pardon my pun hehe) I’ll go for the custom firmware, I’ve seen there is a black box setting already.
I will keep you posted!
I was going off what is written in the wiki here: Plane BlackBox Logger using ArduPilot — Plane documentation
It states: “In order to function properly, it will need to auto arm itself in the air.”. I’ve been trying to force arm the plane while on my workbech, to see if it’ll record data.
Are you saying i don’t need to manually arm it? That the blackbox recording will start once the plane is in the air? Keep in mind ArduPilot will not see any throttle or control surfaces input, since the plane will be flown by a separate system
All the sensor are installed. I managed to calibrate the accelerometer, but the compass refuses to do so.
I start the calibration, then move the GPS module as described in the wiki. There’s only one of the three bars that shows progress by gradually “filling up” in green, but when it’s full it starts over.
My hypothesis is that i should calibrate the GPS once it’s in the plane, because my hands interfere with magnetic fields. Am I on the right track or am I missing something?
I get the following messages on my prearm checks:
compass not calibrated
logging failed
waiting for rc
After that i should be good to go, and the flight data should be recorded on the SD.
Any idea on what i should try @Allister ?
You’re not calibrating the GPS, it’s the compass. (It’s all in the same unit, I know, just make sure we’re on the same page)
When you do the compass calibration, the compass and the flight controller need to move together. This is always best if it’s done when mounted in the plane, so the relative angles between the two are fixed. If that’s not possible then you’ll want to mount them on a board or something so they are facing in the same relative direction as they will be in the plane and then do the calibration. Make sure you’re outside with a GPS position so you’re away from interference, and the GPS can set the local declination offsets.
For the logging error, make sure you have a good SD card installed in the flight controller. It may need formatting. It doesn’t need to be big or super fast, but I tend to stick to name-brand cards because some of the cheap ones are just that…
If logging is still an issue make sure the following are set:
INS_LOG_BAT_MASK,0
LOG_BACKEND_TYPE,O
LOG_FILE_BUFSIZE,16 ## but if that dosen't work go back and try 8
SRTL_POINTS,0
Since this is only for blackbox then you should be able to disable RC input.
THR_FAILSAFE,0
RC_PROTOCOL,0
And you might need to go into the ARMING_CHECK bitmask and set everything except RC Channels. (don’t worry about setting stuff you don’t have, it will ignore that)
You are my saviour. It’s all working correctly now.
I got the compass calibrated by mounting it and the fc to a board, like you suggested. Worked like a charm. Logging is also working properly, just had to format the SD card again and Voilà! There was no need in my case to remove the RC Channels from the arming checks, after changing THR_FAILSAFE,0 RC_PROTOCOL,0.
Last thing i need to do is find a way to make the external power sensor work. As for right now, i’ve connected it to the I2C port of the GPS, but i still have to figure out all the rest.
). If it still fails after that, I’ll try to flash the custom build firmware.