[Paparazzi-devel] Re: Best approach for implementing heartbeat to external failsafe device (2010 OBC).

[Adam Amos]

Thanks guys, Okay So to clarify what I have to do is... create a condition
whereby if any of the following events occur the heartbeat signal will stop
thus triggering the failsafe.

Loss of GPS for more that 30 seconds.
Loss of telemetry for more than 120 seconds.
Cross the mission boundary. 
Engine failure.  

To get started I have successfully used sectors and an exception (as per the
wiki) to detect if the UAV leaves the mission boundary. However I am unable
to find an example of how I could integrate this exception with a hardware
port (via a module?). If somebody could point me in the right direction it
would be much appreciated.


Adam Amos
Student Engineer | RescueRobotics.com.au
address@hidden
Ph: +61424 642 578 
 



-----Original Message-----
From: address@hidden
[mailto:address@hidden
On Behalf Of address@hidden
Sent: Thursday, August 19, 2010 8:27 PM
To: address@hidden
Subject: Paparazzi-devel Digest, Vol 77, Issue 38

Send Paparazzi-devel mailing list submissions to
        address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
or, via email, send a message with subject or body 'help' to
        address@hidden

You can reach the person managing the list at
        address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Paparazzi-devel digest..."


Today's Topics:

   1. IRC (Reto B?ttner)
   2. Re: Spektrum Satellite dropping connection (Todd Sandercock)
   3. Best approach for implementing heartbeat to       external failsafe
      device (2010 OBC) (Adam Amos)
   4. RE: Best approach for implementing heartbeat      toexternal
      failsafe device (2010 OBC) (address@hidden)
   5. Re: Best approach for implementing heartbeat      toexternal
      failsafe device (2010 OBC) (Jeremy Reinertsen)
   6. Re: Best approach for implementing heartbeat to   external
      failsafe device (2010 OBC) (David Carlson)


----------------------------------------------------------------------

Message: 1
Date: Wed, 18 Aug 2010 21:09:15 +0200
From: Reto B?ttner <address@hidden>
Subject: [Paparazzi-devel] IRC
To: address@hidden
Message-ID:
        <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

is anybody in the paparazzi community using IRC or is everyone using
the mailing list?

Cheers, Reto



------------------------------

Message: 2
Date: Thu, 19 Aug 2010 08:22:22 +0930
From: Todd Sandercock <address@hidden>
Subject: Re: [Paparazzi-devel] Spektrum Satellite dropping connection
To: "address@hidden" <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset="us-ascii"

Also watch out for your standard issues that occur with spektrum and carbon.

Todd

On 19/08/2010, at 3:19 AM, Marko Thaler <address@hidden> wrote:

> Hello Eric,
> 
> Thank you for the information and for writing a new parser. I am looking
forward to test the new code.
> 
> Kind regards,
> 
> Marko
> 
> On Wed, Aug 18, 2010 at 7:00 PM, Eric Parsonage <address@hidden>
wrote:
> Hi Marko
> 
> There is a bug in the current parser for both lisa and booz when using a
satellite receiver. I believe that the behaviour you are seeing is due to
this bug. 
> I am currently in the process of writing code to support a pair of
satellite receivers (on lisa) . Hopefully this will be ready in the next few
days. 
> 
> Regards 
> 
> Eric
> 
> 
> On 19/08/2010, at 2:09 AM, Marko Thaler wrote:
> 
>> It would be nice to use the main unit and the Satellite together, but at
the moment Lisa/L only supports the use of the Satellite RX with it`s serial
communication protocol. Thanks anyway!
>> 
>> On Wed, Aug 18, 2010 at 6:24 PM, Edixon Giraldo <address@hidden>
wrote:
>> I was experiencing similar problems with a Spektrum AR7000 Rx.  The
reason it was happening to me was because I disconnected the satellite Rx
and was using just the main unit.  As soon as I reconnected the satellite, I
never lost connection anymore.  I don't know if that is your case, but,
check it out. 
>>  
>> Date: Wed, 18 Aug 2010 18:11:18 +0200
>> From: address@hidden
>> To: address@hidden
>> Subject: [Paparazzi-devel] Spektrum Satellite dropping connection
>> 
>> 
>> Hello everybody,
>> 
>> My setup is Lisa/L with Spektrum Satellite receiver and Futaba T9CP with
Spektrum DSM2 transmitter module. For telemetry I am using 2.4GHz XBee Pro
Series 2 modules.
>> 
>> After a couple of hours of setting up and testing all the systems I have
started to notice the RC link was constantly dropping connection. When the
problem started to occur the quad battery voltage was 11.4V and the
transmitter was at 9.4V. The funny thing is that when I was moving the
sticks the link was solid. However, when there was no stick movement the
connection was dropping out (switching between OK, LOST and REALLY_LOST). I
have reset the board a couple of times and the problem was reproducible.

>> 
>> Has anybody experienced anything similar? What is your experience with
Spektrum system and possible XBee interference (both 2.4GHz)?
>> 
>> I have just recently switched to Spektrum modules because of Lisa/L
support. Previously I was using Jeti Duplex which was rock solid.
>> 
>> Thank you for your help.
>> 
>> Kind regards,
>> 
>> Marko
>> 
>> 
>> _______________________________________________ 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
>> 
>> 
>> _______________________________________________
>> 
>> 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
> 
> 
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.nongnu.org/archive/html/paparazzi-devel/attachments/20100819/26
5573e2/attachment.html

------------------------------

Message: 3
Date: Thu, 19 Aug 2010 18:56:08 +1000
From: "Adam Amos" <address@hidden>
Subject: [Paparazzi-devel] Best approach for implementing heartbeat to
        external failsafe device (2010 OBC)
To: <address@hidden>
Message-ID:
        <address@hidden@rescuerobotics.com.au>
Content-Type: text/plain;       charset="us-ascii"

Hi All

I need some advice on the best way to output a heart beat signal in the form
a voltage transition at regular intervals of at least 1Hz which will be
interpreted by an external failsafe device (Millswood Engineering).

My current thoughts are to try and use a module to oscillate a 1V signal on
the SPI port of my TWOG. Or alternatively simply attach the clock signal of
the SPI port to the external failsafe device. 

Is this the correct approach? 

Adam Amos
Student Engineer | RescueRobotics.com.au
address@hidden
Ph: +61424 642 578 




------------------------------

Message: 4
Date: Thu, 19 Aug 2010 11:20:57 +0200
From: <address@hidden>
Subject: RE: [Paparazzi-devel] Best approach for implementing
        heartbeat       toexternal failsafe device (2010 OBC)
To: <address@hidden>
Message-ID:
        <address@hidden>
Content-Type: text/plain;       charset="us-ascii"

Hi Adam,
I guess you're preparing for the Outback Challenge.
I looked into this aspect and believe that the 1Hz pulse from LED1 is
sufficient. Do you concur?
Mark

-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of Adam Amos
Sent: Thursday, 19 August 2010 10:56 AM
To: address@hidden
Subject: [Paparazzi-devel] Best approach for implementing heartbeat
toexternal failsafe device (2010 OBC)

Hi All

I need some advice on the best way to output a heart beat signal in the
form
a voltage transition at regular intervals of at least 1Hz which will be
interpreted by an external failsafe device (Millswood Engineering).

My current thoughts are to try and use a module to oscillate a 1V signal
on
the SPI port of my TWOG. Or alternatively simply attach the clock signal
of
the SPI port to the external failsafe device. 

Is this the correct approach? 

Adam Amos
Student Engineer | RescueRobotics.com.au
address@hidden
Ph: +61424 642 578 


_______________________________________________
Paparazzi-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel



------------------------------

Message: 5
Date: Thu, 19 Aug 2010 19:53:33 +1000
From: "Jeremy Reinertsen" <address@hidden>
Subject: Re: [Paparazzi-devel] Best approach for implementing
        heartbeat       toexternal failsafe device (2010 OBC)
To: <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
        reply-type=original

Hi Adam,

You have a couple of options here:

- Use the 1 Hz pulse from LED1. This is a little awkward as you will need to

connect to the TP1 which is not connected to one of the board connectors.

- Use the serial port output (TXD1) and assume that an autopilot failure 
would result in no driving of serial output. Serial telemetry messages are 
sent at least once per second so the pin will change states often enough to 
reset the failsafe.

- Use the PPM signal from SERV_RST or SERV_CLK signals from connector J4. As

above, this would assume that autopilot failure would result in no changes 
to these pins. The advantage of this method is that you probably aren't 
already using J4 so it's easy to connect to these outputs.

Cheers and good luck with your OBC entry.


----- Original Message ----- 
From: "Adam Amos" <address@hidden>
To: <address@hidden>
Sent: Thursday, August 19, 2010 6:56 PM
Subject: [Paparazzi-devel] Best approach for implementing heartbeat 
toexternal failsafe device (2010 OBC)


> Hi All
>
> I need some advice on the best way to output a heart beat signal in the 
> form
> a voltage transition at regular intervals of at least 1Hz which will be
> interpreted by an external failsafe device (Millswood Engineering).
>
> My current thoughts are to try and use a module to oscillate a 1V signal 
> on
> the SPI port of my TWOG. Or alternatively simply attach the clock signal 
> of
> the SPI port to the external failsafe device.
>
> Is this the correct approach?
>
> Adam Amos
> Student Engineer | RescueRobotics.com.au
> address@hidden
> Ph: +61424 642 578
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
>


----------------------------------------------------------------------------
----



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.851 / Virus Database: 271.1.1/3080 - Release Date: 08/19/10 
04:35:00




------------------------------

Message: 6
Date: Thu, 19 Aug 2010 13:19:33 +0300
From: David Carlson <address@hidden>
Subject: Re: [Paparazzi-devel] Best approach for implementing
        heartbeat to    external failsafe device (2010 OBC)
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Isn't there also a switchable 5V supply on the CAM port?  Seems you 
should be able to toggle this at a 1 Hz rate.

Buzz

On 08/19/2010 11:56 AM, Adam Amos wrote:
> Hi All
>
> I need some advice on the best way to output a heart beat signal in the
form
> a voltage transition at regular intervals of at least 1Hz which will be
> interpreted by an external failsafe device (Millswood Engineering).
>
> My current thoughts are to try and use a module to oscillate a 1V signal
on
> the SPI port of my TWOG. Or alternatively simply attach the clock signal
of
> the SPI port to the external failsafe device.
>
> Is this the correct approach?
>
> Adam Amos
> Student Engineer | RescueRobotics.com.au
> address@hidden
> Ph: +61424 642 578
>
>
> _______________________________________________
> 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


End of Paparazzi-devel Digest, Vol 77, Issue 38
***********************************************
No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.5.441 / Virus Database: 271.1.1/3080 - Release Date: 08/18/10
18:35:00