<?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[Eview GNSS Engineering]]></title><description><![CDATA[Eview GNSS Engineering]]></description><link>https://eviewgnss.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 14:57:51 GMT</lastBuildDate><atom:link href="https://eviewgnss.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[RTK GNSS on a ROS 2 robot: driver, robot_localization and Nav2 checklist]]></title><description><![CDATA[Getting centimetre-level RTK onto an outdoor robot is half hardware, half frames and covariances. Most "my robot drifts / spins / jumps when GNSS comes in"…]]></description><link>https://eviewgnss.hashnode.dev/rtk-gnss-on-a-ros-2-robot-driver-robot-localization-and-nav2-checklist</link><guid isPermaLink="true">https://eviewgnss.hashnode.dev/rtk-gnss-on-a-ros-2-robot-driver-robot-localization-and-nav2-checklist</guid><category><![CDATA[ros2]]></category><category><![CDATA[robotics]]></category><category><![CDATA[gnss]]></category><dc:creator><![CDATA[Eview GNSS]]></dc:creator><pubDate>Thu, 12 Nov 2026 05:18:04 GMT</pubDate><content:encoded><![CDATA[<p>Getting centimetre-level RTK onto an outdoor robot is half hardware, half frames and covariances. Most "my robot drifts / spins / jumps when GNSS comes in" problems come from a handful of configuration mistakes, not from the receiver. This is the checklist we run through when integrating an RTK receiver with ROS 2 (Humble or Jazzy), robot_localization and Nav2.</p>
<p><em>Disclosure: I work at Eview GNSS, which makes Septentrio-based RTK and dual-antenna heading receivers for robots.</em></p>
<h2>1. Get clean data out of the receiver first</h2>
<p>Before touching ROS, confirm on the receiver's own web UI or software that you have:</p>
<ul>
<li><strong>RTK fixed</strong> (not float) with your correction source, at the update rate you want (10 Hz is plenty for most ground robots; 20 Hz+ for fast ones).</li>
<li><strong>Heading</strong>, if you use a dual-antenna receiver, with the antenna baseline entered correctly.</li>
<li><strong>Correct antenna positions</strong> relative to the receiver's reference point.</li>
</ul>
<p>If it's not stable here, it won't be stable in ROS.</p>
<h2>2. Pick and configure the driver</h2>
<p>For Septentrio-based receivers, the maintained ROS 2 driver is <strong>septentrio_gnss_driver</strong> (available as a binary package for Humble and Jazzy). Other receiver families have their own drivers; the checklist below still applies.</p>
<p>Driver checklist:</p>
<ul>
<li><input disabled type="checkbox" /> Connection type and port match the receiver (USB, serial or TCP/IP). TCP over Ethernet avoids most serial bandwidth problems.</li>
<li><input disabled type="checkbox" /> Output rate set explicitly, not left at default.</li>
<li><input disabled type="checkbox" /> Publish the standard messages your stack needs: <code>sensor_msgs/NavSatFix</code> for position and, for dual-antenna, a heading/attitude output (pose or IMU-style orientation).</li>
<li><input disabled type="checkbox" /> <code>frame_id</code> set to a real link in your URDF (for example <code>gnss_link</code>), not left as <code>gnss</code> with no transform.</li>
<li><input disabled type="checkbox" /> Corrections: either configure NTRIP in the receiver itself (simplest) or feed RTCM from ROS. Don't do both.</li>
</ul>
<h2>3. URDF and TF: the step people skip</h2>
<ul>
<li><input disabled type="checkbox" /> Add <code>gnss_link</code> to the URDF at the <strong>antenna phase centre</strong> position relative to <code>base_link</code>. A 40 cm lever arm on a robot that turns on the spot shows up as a 40 cm circle in your GNSS track.</li>
<li><input disabled type="checkbox" /> For dual-antenna heading, note which antenna is "main" and the baseline direction. Add the mounting yaw offset to the driver or to your heading conversion.</li>
<li><input disabled type="checkbox" /> Check with <code>ros2 run tf2_ros tf2_echo base_link gnss_link</code>.</li>
</ul>
<h2>4. Heading conventions</h2>
<p>This catches almost everyone once:</p>
<ul>
<li>GNSS heading: <strong>0° = north, clockwise positive</strong>.</li>
<li>ROS (REP 103 / REP 105, ENU): <strong>yaw 0 = east, counter-clockwise positive</strong>.</li>
</ul>
<p>So yaw (rad) = π/2 − heading (rad), wrapped to ±π. If your robot drives 90° off or mirrors left/right, this is why. robot_localization's navsat_transform also has a <code>yaw_offset</code> parameter for IMUs that report 0 at north.</p>
<h2>5. Covariances must be honest</h2>
<p>The EKF weighs inputs by their covariance, so:</p>
<ul>
<li><input disabled type="checkbox" /> Use the receiver's reported accuracy (RTK fixed ≈ 0.01–0.02 m horizontal), not zeros and not a fixed 1 m.</li>
<li><input disabled type="checkbox" /> When the fix drops to float or standalone, the covariance <strong>must</strong> grow. A driver that keeps reporting 2 cm while in float will drag the filter off.</li>
<li><input disabled type="checkbox" /> Never publish zero covariance; the filter treats it as infinite confidence.</li>
</ul>
<h2>6. robot_localization: dual EKF + navsat_transform</h2>
<p>The standard pattern (see the robot_localization docs):</p>
<table>
<thead>
<tr>
<th>Node</th>
<th>world_frame</th>
<th>Inputs</th>
</tr>
</thead>
<tbody><tr>
<td><code>ekf_local</code> (odom)</td>
<td><code>odom</code></td>
<td>wheel odometry, IMU (continuous, no jumps)</td>
</tr>
<tr>
<td><code>ekf_global</code> (map)</td>
<td><code>map</code></td>
<td>wheel odometry, IMU, <strong>GNSS odometry from navsat_transform</strong></td>
</tr>
<tr>
<td><code>navsat_transform</code></td>
<td>–</td>
<td><code>NavSatFix</code>, IMU/heading, filtered odometry → outputs <code>odometry/gps</code></td>
</tr>
</tbody></table>
<p>navsat_transform checklist:</p>
<ul>
<li><input disabled type="checkbox" /> <code>magnetic_declination_radians</code>: set for your site if your heading source is magnetic; 0 if it is true heading from dual-antenna GNSS.</li>
<li><input disabled type="checkbox" /> <code>yaw_offset</code>: match your heading convention (see section 4).</li>
<li><input disabled type="checkbox" /> <code>zero_altitude: true</code> for flat ground robots.</li>
<li><input disabled type="checkbox" /> <code>wait_for_datum</code> / datum: fix the datum if you want repeatable map coordinates between runs (field robots, farm rows).</li>
<li><input disabled type="checkbox" /> <code>two_d_mode: true</code> in both EKFs for ground robots.</li>
<li><input disabled type="checkbox" /> Only fuse GNSS <strong>position</strong> (x, y) in <code>ekf_global</code>. Fuse heading from the IMU/dual-antenna source, not twice.</li>
</ul>
<h2>7. Nav2 with GPS waypoints</h2>
<ul>
<li><input disabled type="checkbox" /> Global costmap in <code>map</code> frame, local in <code>odom</code>; rolling-window costmaps work well outdoors where there is no prior map.</li>
<li><input disabled type="checkbox" /> Use the GPS waypoint following support in Nav2 (convert lat/lon to the map frame through navsat_transform's <code>fromLL</code> service) rather than converting coordinates yourself.</li>
<li><input disabled type="checkbox" /> Tune <code>xy_goal_tolerance</code> to what RTK actually gives you; 0.1 m is realistic, 0.01 m is not with real motion.</li>
</ul>
<h2>8. Test like it will fail</h2>
<ul>
<li><input disabled type="checkbox" /> Drive a known straight line or a surveyed point; compare.</li>
<li><input disabled type="checkbox" /> Turn on the spot: the GNSS track should not draw a circle (lever arm check).</li>
<li><input disabled type="checkbox" /> Drive under trees or next to a building: watch covariance grow and the EKF lean on odometry, without jumps when RTK comes back.</li>
<li><input disabled type="checkbox" /> Log the raw receiver data alongside your rosbag. It makes post-analysis possible when something goes wrong.</li>
</ul>
<h2>Quick troubleshooting</h2>
<table>
<thead>
<tr>
<th>Symptom</th>
<th>Likely cause</th>
</tr>
</thead>
<tbody><tr>
<td>Robot position jumps when RTK fixes</td>
<td>Covariance too large in float / too small in fix; or datum reset</td>
</tr>
<tr>
<td>Heading 90° off or mirrored</td>
<td>NED vs ENU convention, yaw_offset</td>
</tr>
<tr>
<td>GNSS track draws circles when turning</td>
<td>Missing or wrong <code>gnss_link</code> lever arm</td>
</tr>
<tr>
<td>Drift in <code>odom</code> frame</td>
<td>GNSS fused into the local EKF (it should only be in the map EKF)</td>
</tr>
<tr>
<td>Works in the open, fails near buildings</td>
<td>Multipath; check fix type and let covariance rise</td>
</tr>
</tbody></table>
<hr />
<p>If you're choosing hardware for an outdoor robot, we've summarised receiver options for robots here: <a href="https://gnss-solutions.com/applications/robotics-gnss/">GNSS for robotics</a>, and the <a href="https://gnss-solutions.com/product/hb56-gnss-receiver/">HB56</a> is our compact RTK receiver used on ROS 2 robots.</p>
]]></content:encoded></item><item><title><![CDATA[RTK corrections for farm machines: own base vs network RTK vs PPP]]></title><description><![CDATA[An RTK receiver on a tractor, sprayer or farm robot is only as good as the corrections it gets. The receiver measures satellites to within millimetres of…]]></description><link>https://eviewgnss.hashnode.dev/rtk-corrections-for-farm-machines-own-base-vs-network-rtk-vs-ppp</link><guid isPermaLink="true">https://eviewgnss.hashnode.dev/rtk-corrections-for-farm-machines-own-base-vs-network-rtk-vs-ppp</guid><category><![CDATA[gnss]]></category><category><![CDATA[agriculture]]></category><category><![CDATA[robotics]]></category><dc:creator><![CDATA[Eview GNSS]]></dc:creator><pubDate>Tue, 10 Nov 2026 02:29:06 GMT</pubDate><content:encoded><![CDATA[<p>An RTK receiver on a tractor, sprayer or farm robot is only as good as the corrections it gets. The receiver measures satellites to within millimetres of carrier phase, but without corrections it can only place itself to within a metre or two. The correction source decides three things: how accurate your lines are, whether they repeat next season, and what happens in the corner of the field with no mobile signal.</p>
<p><em>Disclosure: I work at Eview GNSS, which makes Septentrio-based RTK receivers, including base stations.</em></p>
<p>There are three ways to get corrections onto a farm machine. Here's how they compare.</p>
<h2>Quick comparison</h2>
<table>
<thead>
<tr>
<th></th>
<th>Network RTK (NTRIP)</th>
<th>Your own base station</th>
<th>PPP / satellite service</th>
</tr>
</thead>
<tbody><tr>
<td>Typical accuracy</td>
<td>1–3 cm</td>
<td>1–3 cm</td>
<td>3–20 cm (service-dependent)</td>
</tr>
<tr>
<td>Time to accuracy</td>
<td>Seconds</td>
<td>Seconds</td>
<td>Several minutes to tens of minutes</td>
</tr>
<tr>
<td>Needs at the machine</td>
<td>Mobile data + NTRIP client</td>
<td>Radio receiver or mobile data</td>
<td>Satellite or internet delivery</td>
</tr>
<tr>
<td>Coverage limit</td>
<td>Distance to network station; mobile coverage</td>
<td>Radio range or your own caster</td>
<td>Near-global</td>
</tr>
<tr>
<td>Repeatable year to year</td>
<td>Yes, if the network datum is stable</td>
<td>Yes, if the base coordinates are fixed and surveyed</td>
<td>Usually, within the service accuracy</td>
</tr>
<tr>
<td>Ongoing work</td>
<td>Subscription admin (some networks are free)</td>
<td>Look after the base hardware</td>
<td>Subscription admin</td>
</tr>
</tbody></table>
<h2>1. Network RTK (NTRIP)</h2>
<p>A network of permanent reference stations streams corrections over the internet. The machine's receiver or guidance display logs into a <strong>caster</strong>, picks a <strong>mountpoint</strong> (a single station, or a virtual one built for your position), and receives RTCM messages over mobile data.</p>
<p><strong>It works well when:</strong></p>
<ul>
<li>you have reliable mobile coverage across every field, not just at the yard;</li>
<li>the nearest station is within about 20–30 km (with single-station mountpoints, error grows by roughly 1 ppm of the distance);</li>
<li>you'd rather not install or maintain hardware.</li>
</ul>
<p><strong>What to check:</strong></p>
<ul>
<li>Your display or receiver has an NTRIP client, or you have a modem that can feed corrections into the receiver over serial.</li>
<li>The message format. RTCM 3.x MSM (MSM4 or MSM7) is standard now; older networks may still send legacy messages that some receivers handle badly.</li>
<li>What the receiver does when mobile data drops. Most hold an RTK fix for a short time and then fall back to float or standalone.</li>
</ul>
<h2>2. Your own base station</h2>
<p>A fixed GNSS receiver at the yard or on a mast sends corrections to your machines over UHF radio, or over the internet through your own NTRIP caster.</p>
<p><strong>It works well when:</strong></p>
<ul>
<li>coverage is patchy, or you farm far from the nearest network station;</li>
<li>you want no correction subscription;</li>
<li>you want full control over the coordinates your lines are stored in.</li>
</ul>
<p><strong>Get these right:</strong></p>
<ul>
<li><strong>Rigid mount and clear sky.</strong> A pole or concrete pillar, not a tripod, with a view of the sky down to about 10–15°, away from metal sheds and grain bins. A base with multipath passes the error to every machine.</li>
<li><strong>Proper base coordinates.</strong> "Survey-in" (averaging for a few minutes) only puts the base within about a metre. Your lines work today but shift the next time you set up. For repeatable lines, log several hours of raw data and post-process it (PPP or against a reference network), then enter those coordinates permanently.</li>
<li><strong>Range.</strong> Keep machines within about 10–20 km for consistent centimetre results; a UHF radio usually reaches a few km over open ground, more with a tall antenna or a repeater.</li>
<li><strong>Bandwidth.</strong> If you use a serial radio, check that its air data rate can carry your RTCM stream. MSM4 with two or three constellations is a safe start.</li>
</ul>
<h2>3. PPP and satellite correction services</h2>
<p>Precise Point Positioning uses precise orbit and clock corrections, delivered by satellite (L-band) or over the internet, instead of a nearby base.</p>
<p><strong>It works well when:</strong></p>
<ul>
<li>fields are large and remote, with no mobile coverage and no practical base site;</li>
<li>5–20 cm is enough for the job (tillage, broadacre spraying, mapping).</li>
</ul>
<p><strong>Limits:</strong> convergence takes minutes, longer after a long signal outage, and the best PPP-RTK services are only available in some regions. Check the convergence time and accuracy for your area, not the headline figure.</p>
<h2>Match the correction to the job</h2>
<table>
<thead>
<tr>
<th>Job</th>
<th>Accuracy needed</th>
<th>Usually fine</th>
</tr>
</thead>
<tbody><tr>
<td>Tillage, broadacre spraying, scouting maps</td>
<td>10–30 cm</td>
<td>PPP, or RTK</td>
</tr>
<tr>
<td>Seeding, planting, strip-till</td>
<td>2–5 cm, repeatable</td>
<td>RTK (network or own base)</td>
</tr>
<tr>
<td>Controlled-traffic farming, bed forming, row-crop cultivation</td>
<td>2–3 cm, repeatable every season</td>
<td>RTK with fixed, surveyed coordinates</td>
</tr>
<tr>
<td>Field robots and autonomous machines</td>
<td>2–3 cm + heading</td>
<td>RTK, often with dual-antenna heading</td>
</tr>
</tbody></table>
<p>Repeatability is the key word. If your seeding lines need to match your cultivation lines next spring, the coordinates behind the corrections must not change. That means either a network with a stable datum, or your own base on surveyed coordinates.</p>
<h2>Troubleshooting from the cab</h2>
<table>
<thead>
<tr>
<th>Symptom</th>
<th>Likely cause</th>
</tr>
</thead>
<tbody><tr>
<td>Stays in float near the base</td>
<td>Base antenna multipath or obstruction, or missing constellations in the message set</td>
</tr>
<tr>
<td>Fix drops in one corner of the field</td>
<td>Mobile dead zone (network RTK) or radio shadow (own base)</td>
</tr>
<tr>
<td>Lines shifted a few cm or a metre since last season</td>
<td>Base moved, or base coordinates re-averaged; or a datum change on the network</td>
</tr>
<tr>
<td>Fix comes and goes when driving</td>
<td>Correction latency or dropouts; check the radio air rate or modem signal</td>
</tr>
<tr>
<td>Slow to reach accuracy each morning</td>
<td>PPP convergence; consider RTK if the job needs it at the field edge</td>
</tr>
</tbody></table>
<h2>Summary</h2>
<ul>
<li><strong>Good mobile coverage, near a network station:</strong> network RTK is the simplest.</li>
<li><strong>Patchy coverage, or you want no subscription and full control:</strong> your own base, set up properly.</li>
<li><strong>Very large remote fields where 10 cm is enough:</strong> PPP.</li>
</ul>
<p>Many farms end up with a base station at the yard for the main fields and network RTK or PPP as a backup elsewhere.</p>
<p>If you're retrofitting an older tractor, I've written up the full kit (receiver and antenna, heading, corrections, display and steering) here: <a href="https://gnss-solutions.com/tractor-gps-rtk-retrofit-kit/">Tractor RTK retrofit kit guide</a>. Our own base option is the <a href="https://gnss-solutions.com/product/hb62-gnss-base-receiver/">HB62 GNSS base receiver</a>.</p>
]]></content:encoded></item></channel></rss>