Re: [Paparazzi-devel] FTDI Utility Board

[Gareth Roberts]

Hi Arnaud,

There will probably be a function in your flight plan called SetNavRefHere  
or SetGroundRefHere (something like that) which will be called just after  
the GPS has initialized.  If not have a look in the example flight plans,  
one will have the required block.
This will then set the HOME waypoint to the aircraft's current location  
(it'll jump off the screen of GCS, so you'll have to click "center A/C" to  
get to it).

If your other waypoints are defined in terms of x, y then they will jump  
too relative to the HOME waypoint.  If like most people your waypoints are  
not relative to takeoff point you need to define them in terms of lat/lon.

The lat/lon in the file header is used in simulation as the start point.
I'd recommend setting it to the centre of your flying field or roughly  
where you take off from - it prevents that disconcerting jump when the GPS  
locks on and saves having to click "center A/C".

The default position even with the SetNavRef... until the GPS locks on  
will be that lat/lon (which is why if you are testing indoors it'll seem  
wrong).

Make sure if you change them you keep the number of decimal places the  
same; there is no other reason I see that you would be unable to upload.
If uploading after changing the lat/lon gives you an error, let us know  
what it is and attach your flight plan file.

Cheers,
Gareth


On Thu, 21 Apr 2011 19:28:53 +0100, arnaud dumas <address@hidden>  
wrote:

> Hi,
>
> Please find attached the GPS message. And here the header of the flight  
> plan
>
> <flight_plan alt="75" ground_alt="0" lat0="43.46223" lon0="1.27289"
> max_dist_from_home="1500" name="Basic" security_height="25">
>
> Apparently there is a pb with the reference of the GPS. How can I fix it?
> On the other hand, when I change lat0 and lon0, I can't "upload"anymore,
> why?
>
> I have also try the ir sensors. Actually the vertical one seems to work  
> fine
> but the horizontal one tends to freeze on particular values like 500 or  
> 0, I
> thought it was a bad link somewhere but I checked carefully and found
> nothing apparent even though I still think there is a bad contact  
> somewhere.
> Did you ever hear about this kind of pb?
>
> Have a good day,
>
> Respectfully,
>
> Arnaud
>
>
>
>
>
> 2011/4/21 arnaud dumas <address@hidden>
>
> > Hi David,
> >
> > Thanks for your answer.
> >
> > >> I got paparazzi on PPZUAV store : this one
> > https://store.ppzuav.com/osc/index.php?cPath=2&osCsid=kn378i2ildj4qmkqrigrlpuhv5
> > but it's actually a bit more compicated. I didn't get it myself, I get  
> > it
> > from a former group of students of my school, so that the kit wasn't
> > complete and I had to complete it. That's why I did the following  
> > mistake.
> >
> > I finally got PPZ working yesterday night : no blank pb anymore. I was
> > mistaken with wiring : I thought that the serial port of the tiny board
> > should be connected to the J2 port of the FTDI board but looking at it  
> > more
> > thorougly (drawing myself the schematic of the utility board) I realise  
> > that
> > the FTDI board was not supposed to be emdebbed.  With hindsight I find  
> > that
> > some photographs are confusing about that. Anyway it's now quite well
> > working and I'm really relieved. After understanding the wiring pb, I  
> > had no
> > pb with the airframe (I modified tinyFw.xml ni the CodeReorg section).
> >
> > I have now three leds blinking, a red, an orange and a green.
> >
> >  The GPS is working too (at least in relative movements) but I'm not  
> > sure
> > of its reference point : how does it get its reference point? There is  
> > one
> > given in the flight_plan, but the one I got in GCS is quite different :  
> > I
> > will give you the exact values after next try (I've quite forgotten them
> > right now).
> >
> > I will now connect the ir sensors and servos. Will keep you in touch  
> > with
> > my advance,
> >
> > Bis bald,
> >
> > Respectfully
> >
> > Arnaud
> >
> > 2011/4/20 David Conger <address@hidden>
> >
> > > Hello,
> > >
> > > That link is last updated 2009 (from what I just saw). A lot has  
> > > happened
> > > since then :) ... "without success" is pretty vague... to help you I  
> > > know I
> > > would need something specific to tell you to do.
> > >
> > > "PPZUAV assembled kit"? Did you buy the PCB and assemble it or did you  
> > > buy
> > > one assembled by PPZUAV?
> > >
> > > Yes, FTDI utility has two LED. One for power the other for XBee signal.
> > > Color doesn't matter. If the power one is on it's powered and if the  
> > > XBee
> > > one is on XBee is transmitting/recieving. The XBee LED is up top by  
> > > the XBee
> > > sockets. If it is off maybe your XBee needs configuring? I notice when
> > > programming the XBee in X-CTU software it goes out ... then back on  
> > > after.
> > >
> > > Here's a schematic for that board.
> > >
> > > Regards,
> > > David C.
> > >
> > >
> > >
> > > On Apr 19, 2011, at 8:33 AM, arnaud dumas wrote:
> > >
> > > Hi,
> > >
> > > I haven't solved my pb yet.
> > >
> > > Where can I can find documentation about the LED on FTDI Board and Tiny
> > > Board (I have a PPZUAV assembled kit).
> > > In particular, I have no led blinking on the FTDI board, does it mean  
> > > that
> > > it's not powered? I supposed it was by the three threads link between  
> > > the
> > > serial port on tiny board and the FTDI board but I'm not so sure  
> > > anymore.
> > > I have always the GCS blank pb.
> > >
> > > On the other hand, I've rigourously followed the instructions given in  
> > > *
> > > paparazzi*.mannberg.co.uk
> > >
> > > without success
> > >
> > > I do need help please!
> > >
> > >
> > > Respecfully,
> > >
> > > Arnaud
> > >
> > >
> > > _______________________________________________
> > > Paparazzi-devel mailing list
> > > address@hidden
> > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
> > >
> > >
> > >
> > > _______________________________________________
> > > Paparazzi-devel mailing list
> > > address@hidden
> > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel