You need to be a member of diydrones to add comments!

Join diydrones


  • Thanks for the fast reply.


    What are dependencies for oooark package ? I have already Flightgear 1.9.1, Scicos. Any thing else required ?

  • Developer
    Sorry for the delay. I've been working on simplifying the build system. Ill get a package up by tonight.
  • Is n't it packaged yet ??
    I still can not install the project because of the error I mentioned regarding cmake.

    I hope that you upload a package of it.
  • Thank you very much for your reply.

    I tried to to do what you said but when I did the step of "cmake . " I got the following errors:

      /usr/share/cmake-2.6/Modules/CMakeDetermineCXXCompiler.cmake:128 (CMAKE_DETERMINE_COMPILER_ID)
      CMakeLists.txt:3 (project)

    -- The CXX compiler identification is unknown
    -- Check for working C compiler: /usr/bin/gcc
    CMake Error: Unknown extension ".c" for file "/home/mostafa/oooark/CMakeFiles/CMakeTmp/testCCompiler.c".  TRY_COMPILE only works for enabled languages.
    Currently enabled languages are: C CXX
    See PROJECT command for help enabling other languages.
    -- Check for working C compiler: /usr/bin/gcc -- broken
    CMake Error at /usr/share/cmake-2.6/Modules/CMakeTestCCompiler.cmake:32 (MESSAGE):
      The C compiler "/usr/bin/gcc" is not able to compile a simple test program.

      It fails with the following output:



      CMake will not be able to correctly generate this project.
    Call Stack (most recent call first):
      CMakeLists.txt:3 (project)

    -- Configuring incomplete, errors occurred!




    Do you know what is going wrong ? Sorry, but my knowledge about linux is basic

  • Developer

    Isn't packaged yet but this should work:

    1. git clone git://

    cd oooark

    cmake .


    2. launch oooark, cd  "oooark source directory"/scicoslab, type exec loader.sce

  • Developer

    You'll have to build from source. Its still in development.

    I'll get a package up tonight that should work for you. Let me know if you have any problems.

  • Hello Everyone

    I installed both scicos and oooark packages on my ubuntu karmic koala 9.1. But I have no clue where to start things to work.

    Thetutorial video in which oooark is operated from a shell, shows that it is under
    a directory called Projects/oooark/scicoslab/scripts , but after I had installed oooark
    on my computer, I did not find such dirctory.


    Can anyone help ?

  • Developer
    I'm developing a HIL block for ardupilotmega in scicoslab, it should be finished by the end of today. The ardupilotmega config files only needs to take PID gains. The plane length etc is part of the dynamics which ends up affecting the gains. The JSBSimComm block that I have set up will model the physics for any plane modeled using a JSBSim xml file. This includes many planes already in the JSBSim library and planes in flight gear. I have also made my own custom EasyStar UAV JSBSim model. You can use the JSBSim flight dynamics model then to tune the gains for an autopilot.
  • James,
    so you have just +1 simulation tool for EXISTING AP code. And this EXISTING AP code supported Easy Star and may be 2 models. But any current AP config files doesnt suppot so parameters like: weight, wingspan, plane lenght and so on.
    And my question is it possible to make a AP based by phisics model (non Easy Star only) ?
    Or modify current code for use it parameters?
  • Developer
    The fdm I'm using is JSBSim. The easy star model is currently using the air force datcom predicted stability derivatives. Unlike x-plane, which computed aerodynamics on the fly, JSBSim uses stability derivative tables to calculate the aerodynamic forces. The advantage to JSBSim is that you can increase the fidelity of the model beyond the predictions in x-plane by incorporating actual wind tunnel data. We have an easy star wind tunnel aerodynamic data set that we will be switching to soon. The software I have created allows you to trim any JSBSim model. So far I've tested the 737, A320, f16, c172p, EasyStar. The scicoslab block talks to JSBSim to calculate the derivatives and then scicoslab does the actual integration. The block also manages udp communications with flight gear so that you can see what is going on. The next step is hardware in the loop. This will basically replace the backside successive loop closure controller that you see the video with an ardupilotmega communications block. The block will send the current state of JSBSim to the Ardupilotmega and will request the actuator positions be sent back so that JSBSim can calculate the state derivative and scicoslab can integrate to find the state trajectories. This will simplify controller design and verification for APM.
This reply was deleted.