Hello all, I am currently trying to compile the paparazzi source code into a shared library, but am having difficulty in making this work. Does anyone here have experience in doing this or could provide guidance on where the appropriate arguments could be added to the build? I tried multiple places as early in the build however could not get it to create the shared library.
hi @adamczer shared lib of what exactly?
@flixr, I am trying to make the airborne and simulation a shared library. The reason for this is to eventually port the paparazzi functionality to java. My desire is to call things over jni and eventually move the airborne modules over to java, and continue to use JSBsim through jni for simulation purposes.
hm... the simulation is not meant to be compiled into a shared lib (as it contains a main)
not sure though if it really makes sense to compile all that into one lib
correct, by simulation I meant the calls from paparazzi to the JSBSim, I would have to alter the run to functionality of the ui to call the newly created jar. Thanks for the advice I will try that make file.
I have to admit that I don't quite understand the reason for calling this from java though...
but then I'm not familiar with Java/C integration at all...
The nps main init/ execution cycle would be replaced by a Java execution. All the calls that exist from this point of entry could then be called directly allowing for testing of framework prior to completing a full Java implementation. Its basically so I can swap out one component at a time and make sure I did not mess up something while porting. Does that make more sense?
the approach does make more sense now, yes :-) still wondering why you want to port it to java though... but maybe that's just because I'm biased against java ;-)
Thanks again for the help
no problem, hope that something like that works out
hi I am new to the paparazzi I was following installing instruction
There was some effort to port paparazzi to that a long time ago but it was not finalized
As libopencm3 has support for the f3 by now the port should be quite streight forward if you know how to do embedded programming :)
true, sorry, I misread it
With imitation I meant IMU
Autocorrect hits once again:)
Hello, I am using the Optitrack system at TU Delft and have some problems with flying at higher altitudes. To be more precise, when I'm flying the Bebop between 2.5-3 meters fix alt. the altitude can vary ALOT when going from one waypoint to another and the drone can also completely deviate from the flight plan and start accelerating into the net (both on the sides and in the roof). At lower altitudes 1-2 m everything is working fine. Does anyone have any idea what can cause this?
Optitrack is not a perfect system. If you fly higher, the drone is seen by less cameras which may result in difficulty with tracking. The best option you have is probably to recalibrate the arena before flying.
we’re in the process of building a Flying Arena in ENAC, (est: july 2017) with optitrack or a similar kind of system. Hopefully, we’ll end up contributing to the tracking code.
Okay, so you don't think there is anything in the flightplan/airframe that can cause this behaviour? And there's also no way (except calibration) to amend or decrease the amplitude of the problem?
When creating new messages, is there a particular section to create them in? Which message.XML file? I found 2 different ones in the PaparazziUAV install. Then, do I need to rebuild paparazzi after creating them?