It seems that currently you are mostly talking about the telemetry right now. But in the beginning of the post you were actually referring to compass calibration issues (I was really looking specifically for that), so I hope you don’t mind me asking, if anyone had any issues calibrating a compass in OMNIBUS F4 Nano V6?
So I’ve installed the latest stable version of Ardupilot for the F4 Nano V6, and connected my Matek M8Q-5883 GPS (which already comes with a mag).
I’ve soldered:
SDA (GPS) to RX3 (FC)
SCL (GPS) to TX3 (FC)
RX (GPS) to TX6 (FC)
TX (GPS) to RX6 (FC)
When I start the on board calibration, when is about to reach 100% it resets to 0%. I’ve tried to relax the calibration to be more permissive, but it always gives me the same result.
Any ideas what I could be missing. I normally use BF, so my knowledge of ardupilot is kind-of limited.
Did you fix your problem in the end? I have had no-end of problems with compass calibrations in the past. I don’t have a ‘silver bullet’ answer for how to get it to work. You obviously have your compass connected correctly otherwise the compass calibration wouldn’t start at all. A few common checks that I try are below:
Make sure your compass and flight controller are correctly aligned. Note that the board alignment arrow doesn’t always match the silk screen on the board, and they do sometimes vary between AC and BF. I have the same compass as you so can tell you that the compass orientation matches the printed arrow. I don’t have a nano fc but I know that its bigger brother the F4 V6 the board orientation is does not align to the same direction as BF.
Make sure mission planner is up to date.
Switch off all other compass drivers other than the one for your compass using COMPASS_TYPEMASK parameter (note that a reboot is required for this to take effect).
Switch to master firmware to see if it is an issue that has already been fixed but hasn’t trickled down to stable yet.
quick question maybe you can help. I have been trying to figure out how to get my dsmx rc input working on the omnibus f4 v6. I assumed it needed to be on tx1 according to this page: https://blog.dronetrest.com/omnibus-f4-v6-flight-controller-guide/
what I am now wondering is do I need to set something in apm or do I need to change this hwdef file so that the board uses ppm?
I don’t use Spektrum gear so I haven’t done anything with DSMX, thus I don’t have a complete answer for you. I do know that others have had problems getting it working.
That link you posted is for betaflight/inav. Ardupilot often does things a bit differently to those, so I would be careful following that guide.
Have you tried soldering to sbus/rc-in pins and setting BRD_RADIO_PROT to 2?
I changed the board protocol and no luck with it set to dsm2/dsmx I have gotten these receivers to work with ardupilot using bbbmini/pocketpilot and navio2. I dont know if the note mentioned on the link above regarding ppm still applies. it mentions setting things to half duplex. However the settings for that seem to be a slider and I dont want to assume that half way is half duplex.
Made sure it was connected to tx1 looking at the hardware definition I would assume that is used for rcinput.
I should have answered before but in the meantime I was on holidays and away from this build.
I was trying to do the on-board calibation since the “Live Calibration” didn’t seem to be available in the new version of Mission Planner but after all there’s a way to still calibrate the the compass using Live Calibration, which is holding CRTL key while clicking on the “Compass Calibration” in the Mandatory Hardware. This will actually display once again the Live Validation which allowed me to calibrate, “successfully” the compass.
I did contact Matek and they told me:
“It is neither FC nor compass module issue.
Try “live calibration””
@IAMMATT with the omnibus f4 v6 aio should I be using the labeled pads on the board to set it up? I have been trying to figure out what port on the v6 board I should be using for sbus.
Looking at the hwdef.dat file here, I can see that there are comments that rcin can be on the led strip and sbus can be on uart 6. Have you tried the labeled sbus pins first? If you have and that didn’t work, try the led and/or uart 6 pins.
Still concerning the OMNIBUS F4 Nano V6, After playing around with the 3D printer a little bit to get a few parts for the camera gimbal and legs for the quad, I decided to go and install the newest version of arducopter firmware ( 3.6.11) in the OMNIBUS F4 NANO V6.
Now… I’m not sure anymore if it ever worked… but I’m having some trouble getting the Battery monitor to work. As soon as I try to activate it I get “This feature is not enabled in your firmware”.
So… that’s definitely not a good sign. Have you ever got this kind of error? What I found in on the net is that most of the times people with similar problems just end up trying different firmwares and sometimes it works and nobody knows why.
I accidentally upgraded to 4.0, but now my Beitian BN-880 is in Bad signal health. Maybe version 4 does not support omnibus V4? Or do I have to change some parameters?
I would recommend posting about it here as this is where you are most likely to get help with this:
To answer your question it should work and you shouldn’t need to do anything with parameters as there are param conversion functions that handle this automatically when you upgrade from older to newer code versions. So long as you don’t use the ‘load params’ button in mission planner after flashing the new firmware.
