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.
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.
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:
gps (enabling use of the 6 pin JST, gps with compass)
@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:
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.
I need to get some things wired up here but I might check out the master sooner or later. But I have been busier then I want to be so it has been a bit slow going.
I have a teensey 3.2 sitting around i might try out Eric’s mav2frskyS.Port on the R9-mm. I don’t want to have to run something that big in the long run.
I might order the part for an inverter, the max3232 thingy for rs3232 to ttl with rectifying diodes.
If we get the functions working on our boards in stable i can use the cable in another drone.
I know on the craft and theory page they only list the R9 full size as an option for their solution. Which is weird since the R9 series has been out for a bit. Maybe they didn’t want to mess with the connector on the Slim and Slim+ since the R9 full is a normal servo connector (R9 is a smaller market the the 2.4 X series stuff).
EDIT: This issue thread on GIT HUB explains a lot, check it out.
Thanks for the link. I have an F4 Nano for the bench now so I’ll do some more experimentation with a spare R-XSR that has both inverted and non-inverted Sport’s.I have a couple adapter cables (one C&T) but like you I don’t want to use it on tiny 130 build. There is barely enough space for components as it is.
Got around to soldering and testing some things on a rain cold day. Just tested OSD…Works on Master like before but not on v3.6.2 stable. Omnibus v6 regular.
So I think this is how we are supposed to be hooking this up.
Read the whole thread to see the issues getting worked out.
If you run master aka 3.7.DEV then you can get the inverted to work without extra hardware.
If you have an uninverted option like a few R9 series then you should be good.
If you use ESC telemetry and a GPS it seems we can’t do this as we are out of UARTS as UART 3 SERIAL4_ is RX only
S.Bus and TX1 are abandon?
If they worked normally as they should in BF then we woulnd’t have an issue when 3.7 goes stable or If this feature gets back ported to 3.6.X
I Just threw my XSR on my build and I am going to mess around with this tomorrow. I dind’t want to open my R9mm as i got some r9 Mini’s on the way and I am going to sell off my R9mm.
Hi, as i was not following that - what is the benefit of r9 mini vs r9-mm?