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

[Jeremy Reinertsen]

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