How control works

The whole reason Level COMMAND exists is to help you implement earthmoving designs. It seems fairly simple, but the closer you look, the more is involved. Here are some of the considerations.

How GPS data is handled

When we read a GPS position, we convert this to a blade position using the offsets stored in GPS Offsets. Then we perform various calculations (see below) to determine the target elevation. Then when we send the target elevation to COMMAND, we reverse the GPS offsets.

Why Look Ahead exists

When the implement is over the design and COMMAND is engaged, we send target elevation (and cross slope if enabled) information to COMMAND. Since it takes a little bit of time between reading the GPS elevations and getting the blade to the desired height, we look ahead of the current position by a little. The exact distance changes depending on your speed, so it is determined using the current speed and a small time delay, called "Look Ahead". To edit it, go to Diagnostics/Advanced.

Blade shift and cut/fill limits

You can't often move all the dirt in one pass. So blade shifting and The elevation or slope we send is further modified by any blade shift specified and potentially by any limits set.

Off-map behavior

Designs may not extend to cover the full working area. We provide a gentle disengage when you have to work off the map:

1. When you are off the map, but within 33ft (10m) of the design, the nearest value is used, giving you a bit of leeway.
2. When you go further out, up to 66ft (20m), the we continue sending height commands, but they are raised by 4 inches (10cm).
3. When the implement is even further away, a "no move" message is sent to COMMAND, making it easier when off the map hauling dirt to/from stockpiles.