Recent Posts

Pages: [1] 2 3 ... 10
General Discussion / Re: fw_coptercontrol_ibus14ch question
« Last post by TheOtherCliff on January 28, 2020, 04:23:38 pm »
"Nsis" program
This is the program that packages up all the files into a single executable LibrePilot installation program.  It is automatically used in the final step of building all the source code.  You should not need to know anything about it, just like you don't know anything about the GCC compiler that turns the C/CPP language source code into GCS and firmware.  You can build and run the source code without it if you only need LibrePilot on this one computer.

If you do the command:
Code: [Select]
make packageor in Windows you maybe do:
Code: [Select]
mingw32-make packagethen it will build all LibrePilot programs and use them to make a LibrePilot installation program that you can take to any computer (that has same OS) to install it there.  This LibrePilot installation program is the same kind that we make for users to install, so they don't have to build from source code.  You can use this to easily install this same full LibrePilot package on other computers without actually installing any of the stuff that is needed to build the source code.

If you only need LibrePilot on the one computer where you build the source code, then the only thing that running the LibrePilot installation program will do for you is to make some desktop / menu shortcuts.  You can skip running the LibrePilot installation program and just run the GCS from the command line (same directory where you do the make commands) like this instead if you want:
Code: [Select]
General Discussion / Re: fw_coptercontrol_ibus14ch question
« Last post by chartel on January 27, 2020, 06:34:24 pm »
Hello Cliff
I have ventured to do the building source code.
I did exactly as described and it seems to me that everything is going well,
I also change the file (pios_board.h) with notepad ++ (thanks jdl).
However in the final part I do not understand.

(this part)
"Then GCS software:
Finally all files are packaged using the Nsis software installer.

I think I have to do something else with the "Nsis" program,
but I can't find information. can you give me a tip?
General Discussion / Re: fw_coptercontrol_ibus14ch question
« Last post by jdl on January 27, 2020, 09:32:07 am »
It's probably a good idea to use a simple text editor like Notepad rather than a word processor like Office.

I'd recommend Notepad++ instead of Windows Notepad.
General Discussion / Re: fw_coptercontrol_ibus14ch question
« Last post by TheOtherCliff on January 26, 2020, 05:47:22 pm »
Here is some info on getting started building the source code.  I understand if you don't want to go there though.  :)

It should be a 1 hour task (other than the downloading and the building which depend on internet and PC speed), but plan on a day and you may hit snags and have to ask for help on top of that.

There are several non-developer users who build from source code, maybe it would help for them to comment on difficulty.  There is a set of instructions to follow to make sure you have all the needed compilers, etc. installed on your computer. The main developer document page is here (but just skip this and go to install pages below):

Individual pages on how to install these tools for your OS are here:

The link to the code change from another thread is here:

That bitbucket link in effect says says there is only one file to change for revolution FC (based on where ever you installed the source code):
and go to line 279 and change the 10 to a 14
It's probably a good idea to use a simple text editor like Notepad rather than a word processor like Office.
That is all that is required to make this fix, although a one line change in the GCS makes it easier to use GCS.  The GCS change was not done for the original user and he got it working.  :)  in the thread here:

The other file changes get it working for the other flight controllers.

99% RSSI ... You should try setting your transmitter to "range check mode" (reduced power) and moving the transmitter far enough away that it starts to lose control.  Sometimes RSSI is actually implemented as "good packet percent", and when that is consistently below 99% at all, you are really very close to the edge and should turn back.  On the other hand, maybe something is wrong...
Applications - FPV / Re: Next r782 + Revo + MinimOSD + Oplink - RSSI 100% ?
« Last post by karla on January 26, 2020, 05:18:15 am »
Thanks for all useful input.
With help of your posted config osd file and the panel pictures, I was able to figure out most of the fields I want, and avoid others I don't need for the moment.

You may consider to get rid of some of the fields currently set in your OSD panel:

1. Value in LOS is almost the same as Distance_To_Home (next to big thick arrow pointing home).
Yes, if just adding the field "Home Direction", then I get both the direction and the Distance_To_Home.

2. Ha (or Ba) (height above home point)- on the left, and Alt (absolute GPS altitude) - on the right - do you need then both the same time?
This was another matter, by just adding the field Altitude, I get both HA and ALT.
Tried to put the HA part behind some other field to hide it, but that makes two values flicker so better just display it.

3. Vgnd and V3d. Again, they are most of time close to each other. Vgnd is GPS speed (ground projected). V3d is the speed in the direction of flight in 3d space. It can noticeably bigger than ground speed when diving, for example. I personally prefer to leave only V3d in my OSD.
I see you have discarded field for Airspeed (Vair)? It displays data from Pitot tube sensor!
Yes, by just adding the one field Air Speed, I got both airspeed and ground speed, no need for anything else.

The non-stop GO HOME NOW! alarm from the very beginning of flight makes me think you hadn't setup the battery capacity in the OSD Setup menu, I'm I right? To enter setup menu, toggle the switch for channel 7 to Panel3 position while disarmed.
You were right. It worked as you said.

Is your voltage sensor well calibrated? Or you've just launched with not fully charged battery?
Voltage sensor reasonable calibrated and accurate (not 100% happy with it), this was the 3rd flight with same lipo pack.

Current consumption seems too high to me while disarmed! Is the current sensor calibrated?
I have an Attopilot 50V/90A sensor on this plane and kept the VoltageFactor and currentFactor as specified in our Wiki.
Then I try to get the zero point to match true voltage and current. For voltage it works okay. For current though the sensor changes over time (maybe when it warms up). It shows too high values initially and then gradually comes down over say 5-10 min. And after a takeoff with full power it is realistic. Seems to be a balance of wrong initially and correct later in flight or vice versa.

OSD flickers and I see some noise in the video feed under higher throttle, if you don't have low esr caps connected to the power lines of the ESC, adding some can help with these issues. Also, placing a 1000uF/6.3V capacitor just on MinimOSD power pads helps with disappearing OSD text.
Yes, and its getting worse. No capacitors.
Read up on it and will definitely try your recommendation.

The temperature sensors (LM335z) I've mentioned are intended to monitor the temperatures of ESC and motor and warn when going to overheat. Their data is only processed in MinimOSD, not passed to Revo FC.
Got it  :)
Hardware / Re: [CC3D] Using FlexiPort as input port
« Last post by TheOtherCliff on January 25, 2020, 10:26:18 pm »
You will find Flexiport etc. pinout here:

I assume you want to use DSM.  Your Input page lines must be set to DSM, not PWM.

Positive and negative wires are obvious and must be correct.  The other wire is the receiver sending a signal, so it goes to the Flexiport input pin which looks like pin 4.  :)

From memory.  I think the following is correct.

Some protocols use 1000-2000 and some use other number ranges.  I would configure CC3D to set up the receiver as DSM on Flexiport (on Hardware page), save and reboot CC3D.  Power with flight battery via ESC/BEC (so that the RC receiver gets power) and USB connection (so GCS is connected), then run "Start Transmitter Setup Wizard" on the Input page.  Save when done.  After running that wizard, your Input page transmitter stick and switch "number ranges" will be set correctly and you can see those as needed.

Note that your ESCs and servos etc. still usually need to have a number range of 1000-2000 and those are set on the Output page.  Your transmitter (Input page) could be let's say 800-1800 and your servo could be 1000-2000 and it would be translated automatically.  1300 (middle) on the transmitter would be 1500 (middle) on the ESC / servo for example when using Manual mode where there is the closest thing to a direct connection.
General Discussion / Re: fw_coptercontrol_ibus14ch question
« Last post by chartel on January 25, 2020, 09:51:23 pm »
hello cliff.
Thanks for your quick response and help.
I've been researching and for me this programming field seems complicated, although it seems like a simple thing, just changing a few parameters, but I don't even know how to start.
I bought a fli14 + receiver that has rssi on channel 14 on ibus, at the moment what appears on osd is 99% signal always.
I will research how to have the analog signal, but I do not know if it is possible with this receiver. I'm new on this drone hobby.
Hardware / [CC3D] Using FlexiPort as input port
« Last post by mikmas on January 25, 2020, 02:39:43 pm »
I have problems with PWM input* so i decided to try DSM (FlexiPort), but nowhere i can find technical details about this.
I figured out it have 4 pins - +, -, TxD, RxD which is one of the simplest protocols in my opinion, but no more informations. In Input tab in OpenPilot on dropdown list i have DSM (FlexiPort), but how this DSM protocol looks? How to send command for example "set throttle on 1500, roll on 1000, and so on..."? I will be glad for strict technical documentation of this FlexiPort/MainPort DSM IO.

* in OpenPilot/LibrePilot suddenly i get no value changes. First time it works (attachment 1, nastawy.png) and now whatever i send on PWM channels i have no response (attachment 2, no-reaction.png)
General Discussion / Re: fw_coptercontrol_ibus14ch question
« Last post by TheOtherCliff on January 24, 2020, 09:33:55 pm »
That firmware is for CC3D.  The rest of that thread has additional info and links (e.g. bitbucket link to code changes).

I see that the code change has not been merged into the standard code base ("next") yet, so you would probably need to build it yourself or get a dev to build it.  And build it for whatever version you are using (e.g. 16.09 or next:r782).

The most straightforward way is if you can build / compile the source code yourself.  You just merge that simple set of changes into your code and build it.  That way you also know you get the correct matching version.

As I understand, there are also hardware mods where you can get analog RSSI out of some kinds of receivers.  That may also be worth looking into.
General Discussion / fw_coptercontrol_ibus14ch question
« Last post by chartel on January 24, 2020, 03:38:10 pm »
Good afternoon
Does this firmware work with the revolution flight controller and librepilot next? Because when I try to do Firmware Rescue, I get a message that this firmware is not for revolution.
My question is, if I can still install the firmware
Pages: [1] 2 3 ... 10