Velocidrone Transmitter Setup - This FPV Simulator Changed the Way I Fly 

Awesome! Great to hear that I was able to help you out.

Glad you got it working! Enjoy your simulated flights.

What Version of VelociDrone are you using? Thanks

@S Alan Thanks so much, I really appreciate the great feedback! I have only worked with quadcopters with the pixhawk 4 but I can try and walk through it with you. (also sorry for the long note and weird formatting) - Which power management board (PMB) are you using? docs.px4.io/v1.9.0/en/assembly/quick_start_pixhawk4.html#power this is the one I have (PM07). - From the above link there are two types of outputs, "MAIN outputs in PX4 firmware map to I/O PWM OUT port of Pixhawk 4 whereas AUX outputs map to FMU PWM OUT of Pixhawk 4." - Also take note of this table for later (found in the same link from above, scroll down a little): Airframe Reference Connection between Pixhawk 4 --> PM board MAIN: motor I/O PWM OUT --> I/O PWM IN MAIN: servo I/O PWM OUT --> FMU PWM IN AUX: motor FMU PWM OUT --> I/O PWM IN AUX: servo FMU PWM OUT --> FMU PWM IN - So as an example take a look at the X quadcopter that I used docs.px4.io/v1.9.0/en/airframes/airframe_reference.html#quadrotor-x. - For a quadcopter we use motors and not servos so based on the table from above we are looking at rows 1 and 3. In the diagram of the X quad we also see that the specific outputs are MAIN. This narrows are rows {1, 3} -> {1}. - So basically what you can see from the diagram is that the top left motor is 3 => Motor 3 => MAIN3. In another table from the above link there is line that is: "M3 I/O PWM OUT 3: connect signal wire to ESC of motor 3 here". - So we solder the ESC/motor to M3 on the PMB then apply the same steps for the other motors. By using the I/O PWM OUT --> I/O PWM IN the motors could be controlled through their respective ESCs. - Now for the plane. - Which plane frame are you using? - Looking at the standard plane for now docs.px4.io/v1.9.0/en/airframes/airframe_reference.html#standard-plane it appears that aileron, ..., flaps should be attached by MAIN meaning we are looking at rows 1 and 2 in my makeshift table from above. - We know that on this particular plane the only actual motor will be used for throttle which is MAIN3. This is row 1 in the table. So this motor would go from I/O PWM OUT --> I/O PWM IN and since this is an IO you solder the ESC to the M3 pad on the PMB (coincidentally same setup as above for motor 3 of the quad). - In order to control your flaps you use servos. These fall under I/O PWM OUT --> FMU PWM IN. - So you will need to attach your 3pin servo cables to the pin headers that are marked FMU-PWM-out on the silkscreen of the PMB. (I know I said FMU-PWM-in and FMU-PWM-out however in the docs it says that these are internally connected meaning that you can treat them as the same). - example, For aileron which is MAIN1 you would attach this servo to pin 1 of the FMU headers. You should double check the pin ordering via the PMB manual but I'm pretty sure pin 1 is on the bottom if you are looking at the board with the battery connector up top. elevator is MAIN2 so pin 2, etc. - One other important note is that the power line of pins for the FMU servos is not powered. In the docs it recommends grabbing the 5V BEC from your esc or getting it from your battery to power it. - Make sure you then have both IO and FMU cables attach to your pixhawk from the PMB. - Disclaimer, I have not actually done this for a physical plane so definitely double check this to make sure you aren't shorting wires when soldering, don't leave battery plugged in, etc (reading the docs will help you for future projects as well). Also let me know if you have any questions, the docs can be a little confusing and I had to read through it several times the better understand it. Once again thanks so much for the positive comment!

@@AlexFache Hey man! First off thanks so much for such a detailed and comprehensive response! Don't worry about the format it was great :) I have the same PMB the PM-07 but for some reason the links embedded in your comment above are not working but I found the same pages on the docs manually. I completely understand how the Pixhawk 4 and PM-07 board work and I have setup everything but I get stuck with seeing a response on the servo from the radio once everything is connected. I am sure the servo is getting power because once I connect my 1S Li-Po into the PM boards FMU output pins the servo centers it self but it does not respond to input from my radio. On QGroundControl I can monitor my radio input and all the values are correctly received by the pixhawk. I have read the docs over and over again but there must be something I am missing or doing wrong. Again thanks so much for the such a comprehensive response :D

I just modified the links, the [ ] messed them up. Check out this forum post discuss.px4.io/t/servos-dont-move/9644/2. You may have to switch the IO and FMU cables.

@@AlexFache oh that might be exactly what I am looking for! Will try it out as soon as I can and let you know. Thanks again :D

@@AlexFache Hey man, I tried what was on that forum post but still got nothing, I found another older post which said the same thing about switching IO and FMU cables. Perhaps I am missing something else...

What exactly is your problem? The setup is the same for the QX7.

@@AlexFache thank you for replying my comment, i have solved my controller problem..

Awesome! Glad you got it working.

im still blocked also even after updating the driver, on velocidfrone cant move the controls, what did you do to fix it?

@Invest with Stuph Just so I understand what you have tried, have you followed the steps I listed in the video description?

Don't worry that it's pretty difficult at first, even though you have a lot of experience with other sims, with drones the inputs/controls are dependent on one another so it may feel a little weird at first. When I first started flying my real quad it took a few weeks to get a feel for everything. I'd suggest trying basic maneuvers (fly in a square/circle/etc), try to follow a road, and be able to center yourself in between gaps (between adjacent buildings/trees/etc). Then when you're tackling the course obstacles fly very slow. There's no need to rush through it if you can't even line up in front of an obstacle/gap.

Super hard at first. Took me a whole year grinding to finally finish a technical track without crashing. Super worth it tho.

@@nozty update: It got easier. So much so its hard to imagine it was hard. Like riding a bike. I'm actually quite good now.