Servers by jDrones

Omnibus F4 V5 & V6 Setup - Application Race Quad

gps
arducopter
chibios
copter-36

(Matt K) #21

Are you sure it is the WiFi telemetry? How many OSD screens have you enabled? If you have enabled more than one make sure that they are set up so as to be able to switch through the different screens. For example. If you switch through them by using set switch positions, make sure that no two Re on the same switch position. This will cause the osd to flicker really bad.

Which uart have you connected the telemetry to?


(Dennis Schanze) #22

Telemetry is on UART 1. It’s a 500mW 433mHz 3DR Clone that i had laying around. I think its the BEC to be honest.


(chris rey) #23

Hi, did some flight tests with Omnibus F4V5.1, happy with this. Was also able to connect camera. I’ve a 5V transmitter so I connected the RAM to 5V. Vin to camera and Vout to transmitter. But what is missing is OSD. Do I have to execute a specific operation in MP to display it? No OSD is displayed now. Even with OSD_TYPE set to 1. Running Beta8 arducopter.


(Matt K) #24

Hi Chris,
After setting OSD_Type to 1 you need to power cycle the board. Then the full OSD list of parameters will become available to you. You should now be able to see OSD1_ENABLE in the ful parameter tree. Set this to 1. You should now see your OSD (although a power cycle maybe required, can’t remember).
Matt


(chris rey) #25

I did OSD_TYPE=1, rebooted and then I’ve seen that OSD1_ENABLE was already set to 1. Let all other parameters to default, like OSD_CHAN=0 OSD_FONT=0. And still no OSD in my Goggles, strange…


(Matt K) #26

Which version of the firmware are you using? 3.6.0-rc8? If so, there is your problem. The on board osd for this board hasn’t been encorporated into the stable or beta releases yet. Try the dev build (that’s what I am running) and it should work.


(chris rey) #27

Running ArduCopter V3.6.0-rc10
OK, thanks, will try dev build, didn’t know, sorry.


(Matt K) #28

No problem. I am happy to help as much as I can :grin:
Try the latest build and see how you get on. Let me know if you have any problems and I can send you one of my builds that I know works :+1:


(chris rey) #29

Hi Matt, that was the solution, installing ArduCopter V3.7-dev, thanks a lot! But I think they should mention this somewhere in the Wiki


(Matt K) #30

Glad I could help :+1:

The trouble with updating the wiki is that the problem is specific to this board and is only temporary. The driver for the OSD chip on the omnibus F4 has already been written by one of the devs and it is in the master. It just takes time for any changes to trickle down through beta testing and finally into the stable release. Strictly speaking we are jumping ahead by using the dev build (at the risk of unstable performance).


(Ryan C Smith) #31

Thanks for the info @IAMMATT and everyone who has posted . I am going to jump onboard and test some things out when more parts show up. I am running an Omnibus F4 v5.1 and from what I can tell it is all but identical to the V6. Loaded f4pro copter 3.6 r10 now. I am going to move on to Master aka 3.7 dev now that I see this thread. Will start poking about after this weekend. Any one working on getting more uarts on the hardware def? I’ll track down a pin out and take some high def pictures before I start connecting this thing up so I can follow traces. Likely wont be able to do this till after this weekend. Got some camping and a wedding to attend to. Cheers