<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.paparazziuav.org/w/index.php?action=history&amp;feed=atom&amp;title=Cam_Footprint</id>
	<title>Cam Footprint - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.paparazziuav.org/w/index.php?action=history&amp;feed=atom&amp;title=Cam_Footprint"/>
	<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Cam_Footprint&amp;action=history"/>
	<updated>2026-05-08T03:48:21Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.37.1</generator>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Cam_Footprint&amp;diff=23893&amp;oldid=prev</id>
		<title>Rijesh: Added cam footprint page</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Cam_Footprint&amp;diff=23893&amp;oldid=prev"/>
		<updated>2017-10-18T22:22:19Z</updated>

		<summary type="html">&lt;p&gt;Added cam footprint page&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;The paparazzi GCS has the ability to plot a camera footprint onto the map.&lt;br /&gt;
By default the footprint will be for a camera pointing straight down.&lt;br /&gt;
&lt;br /&gt;
The camera's horizontal field of view and vertical field of view can be set in the airframe file:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;section name=&amp;quot;CAM&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;define name=&amp;quot;CAM_HFV&amp;quot; value=&amp;quot;65.1&amp;quot;/&amp;gt;&lt;br /&gt;
    &amp;lt;define name=&amp;quot;CAM_VFV&amp;quot; value=&amp;quot;40.2&amp;quot;/&amp;gt;&lt;br /&gt;
  &amp;lt;/section&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A gimbaled camera will need to send a pan/tilt message to the server. A [[Pan_Tilt_Camera|cam point module]] is available that will point a pan/tilt camera using servos.&lt;br /&gt;
&lt;br /&gt;
If a custom gimbal and module is being used, then the custom module will need to send the CAM message to the server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
     &amp;lt;message name=&amp;quot;CAM&amp;quot; id=&amp;quot;20&amp;quot;&amp;gt;&lt;br /&gt;
        &amp;lt;field name=&amp;quot;pan&amp;quot; type=&amp;quot;int16&amp;quot; unit=&amp;quot;deg&amp;quot;/&amp;gt;&lt;br /&gt;
        &amp;lt;field name=&amp;quot;tilt&amp;quot; type=&amp;quot;int16&amp;quot; unit=&amp;quot;deg&amp;quot;/&amp;gt;&lt;br /&gt;
        &amp;lt;field name=&amp;quot;target_x&amp;quot; type=&amp;quot;int16&amp;quot; unit=&amp;quot;m&amp;quot;/&amp;gt;&lt;br /&gt;
        &amp;lt;field name=&amp;quot;target_y&amp;quot; type=&amp;quot;int16&amp;quot; unit=&amp;quot;m&amp;quot;/&amp;gt;&lt;br /&gt;
      &amp;lt;/message&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The server code is capable of mixing a full 3 axis gimbal with modifications. The modifications required to do this involve sending the new rotation in the cam message and enabling the use of that field in server.ml. The Quaternion used in the mixing takes Tait-Bryan as input angles.&lt;/div&gt;</summary>
		<author><name>Rijesh</name></author>
	</entry>
</feed>