Well after spending a year silently reading posts and forums here I decided to ask the community about a problem I am having. I have been testing out Paparazzi on it's own recently and since I work with FlightGear quite a lot I wanted to start to really work on building my own UAS. The problem is that no matter what info on a wiki or a forum I read, I cannot get the two to connect. Which is really strange since I have been doing the same thing essentially using a basic autopilot program (not written by me but adopted) and UAVPlayground for my work on a FlightGear version of the X-47B.

The problem is that the command '.../sw/simulator/launchsitl -a (airframe) -fg 127.0.0.1 -boot -norc' just will not get picked up by FlightGear, despite having the generic socket written in on "FGO" (a python FG launcher) --native-gui=socket,in,30,,5501,udp, with or without the localhost IP.

From my experience with the other software I used to get the X-47B to fly autonomously, I would need a protocol XML file for FlightGear located within the programs directory, however there is no such file in any of the directories for Paparazzi, though it does come with some planes to use. The reason I am using Paparazzi if mainly ease of use for real world UAS plus I think I want to try to get my X-47B project to get to use this (how I am not sure at this moment, an idea more or less), however the real purpose is to start building one this winter and spring, in time to do some flight tests in the summer.

Am I doing something wrong? Or am I just missing something obvious? The wiki page really does not offer much info on troubleshooting or detailed info on just how to do this, nor any forums.

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

Join diydrones

Email me when people reply –

Replies

  • Hello,

    What OS and detailed version of FlightGear are you using? How up to date is your Paparazzi code? Are you also using the option "--fdm=null" ?

    The native-gui is a built-in "native" protocol that doesn't need an additional xml protocol definition (these are needed for the generic protocol). More info about it can be found in the FG source, under src->Network->native_gui.hxx.

This reply was deleted.

Activity

DIY Robocars via Twitter
Jan 28
DIY Robocars via Twitter
RT @Heavy02011: ⁦@diyrobocars⁩ : A Home-brew computer club* for Connected Autonomous Driving. talk at #piandmore ⁦@PiAndMore⁩ on Jan 23rd h…
Jan 23
DIY Robocars via Twitter
RT @a1k0n: New blog post! Deep dive into my ceiling light based localization algorithm which runs in 1ms on a Raspberry Pi 3: https://t.co/…
Jan 23
DIY Robocars via Twitter
Great new guide to using @donkey_car https://custom-build-robots.com/donkey-car-e-book-en
Jan 23
DIY Robocars via Twitter
RT @chr1sa: The next @DIYRobocars virtual AI race is tomorrow morn at 9:00am PT. You can watch live on Twitch https://www.meetup.com/DIYRobocars/events/275268196/
Jan 22
DIY Robocars via Twitter
New version of Intel OpenBot! This resolves many of the issues with the first version, including a much smoother tr… https://twitter.com/i/web/status/1352395636369313798
Jan 21
DIY Drones via Twitter
Using ArduRover with an RTK GPS https://ift.tt/2N9I3RO
Jan 18
DIY Drones via Twitter
Jan 18
DIY Robocars via Twitter
Jan 18
DIY Robocars via Twitter
Jan 15
DIY Robocars via Twitter
Jan 15
DIY Drones via Twitter
Jan 14
DIY Robocars via Twitter
RT @Heavy02011: @diyrobocars : A Home-brew computer club* for Connected Autonomous Driving on Jan 23rd, 2021 https://www.meetup.com/Connected-Autonomous-Driving/events/275728684/ #Meetu…
Jan 14
DIY Robocars via Twitter
Jan 14
DIY Robocars via Twitter
RT @Heavy02011: ⁦@diyrobocars⁩ Autonomous Driving Assembly at #rC3. join us at https://rc3.world/rc3/assembly/diyrobocars-f1tenth/ ⁦@f1tenth⁩ ⁦@DAVGtech⁩ ⁦@DWalmroth⁩…
Jan 11
DIY Robocars via Twitter
RT @chr1sa: New car designs coming for our next @DIYRobocars @donkey_car virtual race on the 23rd. Choose any one you want at race time Le…
Jan 11
More…