Anonator

  • *
  • 36
  • UAAV experimenting
Re: Compatible fc
« Reply #15 on: February 20, 2019, 09:48:50 pm »
Trying to checkout omnibus_f3_f4, but errors.

>MyLibrePilot/librepilot$ git fetch && git checkout omnibus_f3_f4
error: pathspec 'omnibus_f3_f4' did not match any file(s) known to git.

Please tell what silly mistake I have made...
Ubuntu 18.04LTS.  F450 Quad.  3 Fixed wing planes.  Revo and OmniF4 flight controllers.

Re: Compatible fc (Omnibus F4)
« Reply #16 on: February 20, 2019, 10:43:35 pm »
I did
  git clone https://bitbucket.org/mindnever/librepilot.git
  (must do "cd librepilot" here)
  git checkout omnibus_f3_f4
  make -j4 gcs
  make -j4 omnibusf4
  make -j4 bl_omnibusf4_hex

Maybe you are looking in librepilot/librepilot.git instead of mindnever/librepilot.git (you must clone mindnever's private repo) or had not changed directories to the one which has ground and flight directories in it.

Anonator

  • *
  • 36
  • UAAV experimenting
Re: Compatible fc
« Reply #17 on: February 20, 2019, 11:28:24 pm »
Thanks Cliff :)  Cloned step missed lol.

Google Earth not working.  Getting loads of errors as below...

Reply error:  "Error transferring http://khms0.google.com/kh/v=810&hl=en-AU&x=964190&y=618805&z=20&s=Galileo - server replied: Not Found" QUrl("http://khms0.google.com/kh/v=810&hl=en-AU&x=964190&y=618805&z=20&s=Galileo")
Reply error:  "Error transferring http://khms2.google.com/kh/v=810&hl=en-AU&x=964190&y=618804&z=20&s=Galile - server replied: Not Found" QUrl("http://khms2.google.com/kh/v=810&hl=en-AU&x=964190&y=618804&z=20&s=Galile")
QMutex: destroying locked mutex
QMutex: destroying locked mutex
Ubuntu 18.04LTS.  F450 Quad.  3 Fixed wing planes.  Revo and OmniF4 flight controllers.

Re: Compatible fc
« Reply #18 on: February 21, 2019, 01:03:23 am »
Try 823 instead of the default of 810.  In particular, set an environment variable called GCS_GOOGLE_SAT_VERSION to 823

In Linux, I can run the GCS from the source root directory with the command:
GCS_GOOGLE_SAT_VERSION=823  ./build/librepilot-gcs_release/bin/librepilot-gcs
« Last Edit: February 25, 2019, 04:08:52 am by TheOtherCliff »

Anonator

  • *
  • 36
  • UAAV experimenting
Re: Compatible fc
« Reply #19 on: February 25, 2019, 02:19:16 am »
Thanks again Cliff.  GoogleEarth working.  Is there a list of ENV variables with options?
Ubuntu 18.04LTS.  F450 Quad.  3 Fixed wing planes.  Revo and OmniF4 flight controllers.

Re: Compatible fc
« Reply #20 on: February 25, 2019, 04:04:17 am »
$ find ground -type f -exec grep -Hi getenv \{\} \;
ground/gcs/src/libs/utils/synchronousprocess.cpp:    const QByteArray path = qgetenv("PATH");
ground/gcs/src/libs/eigen/test/main.h:    char *env_EIGEN_REPEAT = getenv("EIGEN_REPEAT");
ground/gcs/src/libs/eigen/test/main.h:    char *env_EIGEN_SEED = getenv("EIGEN_SEED");
ground/gcs/src/libs/eigen/bench/spbench/spbenchsolver.cpp:    if(getenv("EIGEN_MATRIXDIR") == NULL){
ground/gcs/src/libs/eigen/bench/spbench/spbenchsolver.cpp:    matrix_dir = getenv("EIGEN_MATRIXDIR");
ground/gcs/src/libs/eigen/bench/btl/generic_bench/btl.hh:    _config = getenv ("BTL_CONFIG");
ground/gcs/src/libs/opmapcontrol/src/core/providerstrings.cpp:    QString envVersion = qgetenv("GCS_GOOGLE_SAT_VERSION").constData();
ground/gcs/src/libs/gstreamer/gst_util.cpp:    qDebug() << "gstreamer - plugin system path:" << qgetenv("GST_PLUGIN_SYSTEM_PATH_1_0");
ground/gcs/src/libs/gstreamer/gst_util.cpp:    qDebug() << "gstreamer - plugin path:" << qgetenv("GST_PLUGIN_PATH_1_0");
ground/gcs/src/libs/extensionsystem/pluginmanager.cpp:    QByteArray ba = qgetenv("QTCREATOR_TEST_DIR");


Now as to what each one does, it would be best to examine the code or Google it, but you can certainly make educated guesses.  There is little here that is useful to a typical user.  The Eigen stuff looks like it is in test code.  The only env var that I have heard tweaked is GCS_GOOGLE_SAT_VERSION

Re: Compatible fc
« Reply #21 on: May 11, 2019, 09:34:38 pm »
LOL I was just about to ask whether this controller works with LibrePilot.
Great to know! These ones are very cheap so a good way to start I think!

Re: Compatible fc
« Reply #22 on: May 11, 2019, 10:58:29 pm »
There is a private developer branch that has support for Omnibus F4.  It is not part of 16.09 or even next yet.

Anonator

  • *
  • 36
  • UAAV experimenting
Re: Compatible fc
« Reply #23 on: October 14, 2019, 11:06:33 am »
https://www.readytoflyquads.com/flip32-f4

These are cheap, will they work with Omnibus version?

ps what will it take to integrate/merge the omnibus into main as Revo hard to get now and many ver Omnibus
Ubuntu 18.04LTS.  F450 Quad.  3 Fixed wing planes.  Revo and OmniF4 flight controllers.

Re: Compatible fc
« Reply #24 on: November 07, 2019, 05:15:52 am »
Sorry.  I missed this question and just noticed it.

That link seems to claim that this board is treated by RaceFlight as if it were an OpenPilot Revo.  Of course it does not have an RFM22B telemetry module, baro, or mag, and it has some extra features not on a normal Revo.

The linked RTFQ ad says "The Revolution ... is a 6DOF with gyroscope/accelerometer only, no magnetometer and no pressure sensors and no radio link."  Since each of those three things is obviously untrue for a real Revolution board, they must be talking about their board.  I greatly suspect that their board would not work with LP Revo code and would fail because of the missing sensors.  It may be fairly easy to change the LP code to skip the missing sensors, but then you would basically have an overgrown CC3D that can't do GPS flight modes but does support advanced features like RC receiver signal protocols, MavOSD, AutoTune, etc.

From the beginning of the ad; read it for a chuckle and what about those claims:  :)
Quote
Tons of features in one board with a wounder full layout. Flip F4 ; Flip32 F4 With the low noise Gyro, optimal gyro placement recommended , and not an overly super inventive gyro that will require chasing down the PID tune

There is already a private dev fork that supports Omnibus F4 Pro (V?).  The board version that has OSD, current sensor, baro, BEC, SDCard (unsupported?).  At least that is the board that I have that it works with (it may support other boards too).  This fork also supports some F3 CPU targets.  This fork has not been merged back into the main code (next) because the simple way to do that adds more code in a direction that makes it difficult to add more boards.  At least we (developers) should make some decisions and decide to spend some serious dev time (that we don't really have) on it.  Doing it what might be a better way is a large effort and no one here is paid.  :)

Next already supports some F3 boards.
« Last Edit: November 07, 2019, 05:45:01 am by TheOtherCliff »