Servers by jDrones

Omnibus F4 V5 & V6 Setup - Application Race Quad

Ah OK, sorry. So the old way before the BF targets were available. I had to do that with the 1st F4 Nano V6.

I get some more crap in the mail tomorrow and can rebuild my smaller quad. I am switching my PDB to one with a current sensor even though I am going to try to use the BLheli esc telemetry as a current sensor too. I am gong to set up BLheli as sensor monitor 1 and current sensor as monitor 2… after I calibrate it that is.

Interesting. The latest hwdef file for the F4 Nano V6 is supposed to enable ESC telemetry on Rx 4 but 1st attempt didn’t work for me with an Ori32 ESC.

Just heard back from Tridge and they added the bootloader to the auto build system so I assume soonish there will be a version of beta and latest with the "with_BL.hex so it can be flashed onto the f4 v6.

@dkemxr I havn’t gotten that far I fired my v5.1 with a soldering iron that was hotter then it needed to be. So my testing ended there.
Have you looked into the serial settings? ( SERIAL(3 or 4)_PROTOCOL ) It should be set to 16 for ESC Telemetry.
Hwddef.dat on the nanov6 was updated to inclued uart 4 rx for ESC Telemetry. There is also a test function to see if your getting info from the motors you can set. it might be new if you tried it a little while ago. You should see data in mission planner according to the video that sets the full debug. SERVO_BLH_TEST I would assume the motor test runs similar and you would see telemetry data.

Yep, have Serial 4 set for 16. I’m monitoring ESC telemetry in MP on the tuning screen but no data.

Check out this post and the whole thread on esc telemetry. This user has the nanov6. He says he had to comment out Uart4 and re-compile AP but i don’t think that may be needed anymore. The post was a month or so ago. I haven’t check in on this theory yet about i am pretty sure i saw it setup properly on the new v6 regular target. so they may have updated the hwdef for the nano as well as they are very similar. Also @Paul_Atkin1 confirmed a few posts down that he had it hooked up correctly but didn’t think he did the whole time. Due to the messages he saw in MP. … It might work if your on the master or new 3.6.1RC for the nanov6

MP still shows no esc data correctly in the status screen. it is plain broken. you need to arm the model and then look into the dataflash log into ESCx sections. if hooked up correctly - it will have those sections and values in them.

1 Like

UART4 mapped to Serial2! That did the trick, thanks Ryan! The data is now available on the tuning screen of Mission Planner. Not sure about current it looks a bit wonky but voltage and RPM are working. It could just be the update rate for the live graph.

Awesome Dave, Make sure to set the SERVO_BLH_TRATE to 10. Also check to see what you set your Protocol for the BLHELI that may affect your results. Recommended was Dshot150. Per http://ardupilot.org/copter/docs/common-dshot.html?highlight=blheli. I am going to try out Serial 2 on my v6 Regular when I get things soldered up hopefully tonight. Hopefully it is the same. I need to look over the hdwdef for the nano and regular side by side. I am assuming I need to use the LED pad for S.Bus on the FRSKY too like the nanov6.

“I am assuming I need to use the LED pad for S.Bus on the FRSKY too like the nanov6.”

Yes, that is correct.

1 Like

The regular V6 board also includes an additional uart (uart3), that can be used for example for a rangefinder in conjunction with gps etc. It also exposes pwm 5 and 6 (for example for servos).

I have not had time to make a description for the board yet. Note that uart4 is not a full uart, only rx (PA0 is used for rssi adc).

for example with use of 3 uarts:
esc-telemetry
SERIAL2_PROTOCOL

gps (enabling use of the 6 pin JST, gps with compass)
SERIAL3_PROTOCOL

lidar tfmini
SERIAL4_PROTOCOL (UART3)

1 Like

@dkemxr Got my blheli_32 Telmetry running aswell. My new problem, @ceitean might be able to help, is I want to use mavlink pass through on my Frsky. I would love to use inverted directly into my r9mm receiver so I don’t have to make an inverter cable. I have to read the docs on this R9mm but I am under the impression that it might have an un-inverted S.Port along with the inverted one. They made changes from the R9 mini. All that said it would be nice to know if someone had a mini or other frsky receiver.

Take this with a grain of salt as i know the OG docs don’t match up too well with the ardupilot hwdef’s.

We are using the LED for S.Bus not the labled S.Bus pin. I am assuming that the OG S.Bus (PA10) pin is now a normal UART as it is labled in the hwdef.dat file.

So I guess my question is can I get inverted RX and TX from the S.Bus(PA10) S.Port(PA9) pads UART1 (originally this is inverted according to the spec sheet) Or is there somewhere other then UART6 I can get an inverted signal.

I don’t want to use the UART6 with the JST connection as I will be messing with a GPS for a bit while tuning this thing. I know I could un-comment it in the HWDEF.DAT file and make it inverted again but I want to keep that free for the GPS like I said.

Ryan-I tried both the inverted and non-inverted Sport on an R9 slim for Frsky telemetry. No go either way for Frsky passthrough telemetry.

When you did this, did you have the Serial port set up for 10 (mavlink to frsky telem pass through) and did you combine the TX and RX wires to a single wire going into the S.Port on the r9 Slim? Did you also try the other UARTS that you had free to check if your numbering was off…like the UART 4 to SERIAL2 we borrowed from another thread.

I have a feeling this is our golden ticket whether we need to convert in between or not SERIAL4_PROTOCOL (UART3). The pixracer has an inverted uart and can just hook up to the S.Port so those of us with the non-inverted input or have modded for that on like the XRS should be able to do the same. In my head at least.

Rumor has it that the frsky passthrough will become available via soft-serial very soon. If you wait a couple of weeks it maybe easier to set up the frsky Telem.

Hmmm… thanks Matt . Is there somewhere we can follow this? I havn’t attempted to look yet but if you had a link off the top of your head without going out of your way, it would be rad.

The weather has been crappy in the Northeast US lately so i think I can wait a bit.

I am not sure of anywhere to follow the progress of this as I heard it from @iampete
Pete, care to weigh in?

its been merged on master now, you may still need to use a inverted for F405 boards, depends on hardware some boards have inverters built in, some work to be done on enabling and disabling them from software.
Follow the progress here:

1 Like

Now that I saw this I did see something about serial_n options but kind of pass over it as I was going down a different rabbit hole at the time. Thanks for the link.

Yes, I’m using passthrough protocol (10) on 3 Pixracers so have familiarity with that. Also with connecting Tx to Rx and trying all available UARTS. So far no go.

Servers by jDrones