@nostromo123 thanks kalle, will do!
@FINNIGAN imho that board isn‘t really much more of a pita than any other board. it‘s a small board with limited ressources though. there‘s two full uarts + I2C when using ALT_CONFIG = 1, just like on the original V6 version.
@nostromo grazie, amico: you just confirmed that i need a board with some UART more… Maybe can you help me concerning the Runcam Hybrid setup? If i’m not wrong i need TWO uarts for this stuff…
Another question: after flashing th board, i cannot enter in DFU mode anymore, i cannot fix the drivers. How i can solve this issue? I cannot re-flash the board wit a different firmware…
Hi Finnigan.
I am new to AP and learning. Only build a demo board (flying wing) with the Nano 6.1
Sure you can flash different firmware. For flashing a different version of AP, just flash using Mission Planner. I personally prefer QGroundControl. For flashing INAV etc., you have to bridge the boot connection on the board …
br KH
Search for “runcam hybrid” on the forums - there is a thread that explains what works and what doesn’t
I’ve read a lot of things, MANY things but sincerely i don’t understand if i MUST connect both the hybrid’s RX/TX outputs or i can manage the cam functions manually. What i REALLY need is the 4K cam on-off switch on my radio.
You can only connect to one UART - the driver does not support both at the same time. You need to connect to the bigger set of pads. With the latest 4.1 this should give you what you want.
THANK YOU!!! The bigger set means HD Tx/Rx, right?
Yes
More words here because
My issue is that once bridged the pads the FC enters in DFU mode but the drivers are missing and my pc don’t recognize the DFU mode. So i cannot flash anything.
I tried the Driver Fixer (working if flashed with INAV or BF) but now don’t recognize the board in “normal” mode and cannot fix the drivers.
Bricked.
Hi Finnigan.
Do I understand you right, you want to flash from AP 4.0.7 to AP development master 4.10?
Here are two screenshots from doing so on QGC.
Disconnect BT here and power off. Connect direct via USB and flash 4.10.
Easy like that …
But I have to admit, I am on Linux. No hassle.
br
Have to admit, tried it under WIN 10 and had some difficulties myself.
First with zadig installed winUSB driver for Omnibus Nano v6.
Now in WIN device manager an add. USB device ‘omnibus nano’ showed up, BUT the com port was missing. So no connection.
So had a closer look at that ‘omnibus nano’ entry in device manager. Told me, something is missing, so I did an update on it and this entry vanished and additional COM port ArduPilot showed up, No it is also working under WIN 10.
br
No, i already have the latest version installed, simply i cannot flash another firmware like BF or Inav
OK.
Activated BOOT
Connected to my LINUX machine
~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046a:b092 Cherry GmbH
Bus 001 Device 005: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
Bus 001 Device 003: ID 046a:b090 Cherry GmbH Keyboard
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Started INAV 2.5 and selected FireworksV2 as recommended
Ready for flashing
And this is the same situation here under WIN 10
I am not going to flash the FC, because I don’t want INAV on it.
To your problem Finnigan I would say. OK, so your Nano is bricked, or you are using a faulty USB cable or maybe your computer is not working/not set up as expected. With the few information, you are giving, I can not say more …
Good luck and br.
As the message says.
(What firmware ver. are you using and what QGC version??)
or
br
Update GQC. The Daily build would be the best choice.
Well:
the firmware is the latest stable version, flashed through the latest QGC version for windows (i cannot flash with MP or APM planner)
Then ignore that message. The version of Ardupilot you are using doesn’t have that parameter name. It’s not really a bug or an issue just differences in how QGC interacts with Ardupilot firmware. QGC is PX4’s native Ground Station and Mission planner is Ardupilot’s native Ground station. Obviously they can interact but there are delays in development.
Daily QGC builds here:
https://docs.qgroundcontrol.com/master/en/releases/daily_builds.html
many thanks, my friend: i’m testing these 3 different “ground stations” and this is my first Ardubuild.
My problem is that the FC doesn’t detect the compass (Integrated: Beitian BN.880).
I also tried to swap the TX-RX wires but doesn’t work.
i followed this diagram…
I’m concerned.
Tx/Rx wouldn’t fix the compass it’s I2C so it would be the SCL/SDA pins to reverse.
