<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Physical placement of VOXL2 in quadcopter]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">I'm looking to translate the physical VOXL2, from the cg of the drone, along the +X axis by about 15 centimeters.</p>
<p dir="auto">We see that PX4 has the option to specify this type of transform via EK2_IMU_POS_X,Y,Z parameters.</p>
<p dir="auto">For implementation, would we simply need to incorporate 1) the physical voxl2 translation<br />
2) the imu_px4 translation between voxl2 and imu_px4 (specified <a href="https://docs.modalai.com/voxl2-onboard-sensors/" rel="nofollow ugc">here</a>)</p>
<p dir="auto">into EK2_IMU_POS_X? Are there any other transforms to include or some steps I've missed / not considered?</p>
<p dir="auto">Have y'all had experience in running such a setup, where the placement of the FC is not at the CG of the drone? I see that PX4 supports it, but I'm not sure how well it is actually performs.</p>
]]></description><link>https://forum.modalai.com/topic/4818/physical-placement-of-voxl2-in-quadcopter</link><generator>RSS for Node</generator><lastBuildDate>Wed, 07 Oct 2026 07:34:20 GMT</lastBuildDate><atom:link href="https://forum.modalai.com/topic/4818.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 16 Oct 2025 17:13:08 GMT</pubDate><ttl>60</ttl></channel></rss>