What You're Seeing
One or both of these messages are being displayed on the iPad:
- "The tracker may be tilted"
- "Recorded elevations do not match the file data"
Printing may still be attempted, but accuracy will be affected.
Why This Happens
Before printing begins, the FieldPrinter scans control points to determine its exact position and orientation. Each control point in the layout file is stored at a specific elevation. In most standard setups, all control points are recorded at the same height (elevation = 0).
If a control point is scanned at a physical elevation that is much higher or lower than what the file expects, the FieldPrinter interprets this as being tilted. When the tilt exceeds the acceptable threshold, this error is triggered.
Common causes:
- A control point was scanned from an elevated surface (a ramp, platform, raised slab, etc.) while the file records it at ground level
- Stationing was performed from a location significantly higher or lower than where the control points are placed
- The Elevation Setup toggle was left on when it should be off, or vice versa
How to Fix It
1. Check where stationing is being performed. The FieldPrinter should be stationed from a flat, ground-level surface. If an elevated structure or raised platform was used, the FieldPrinter should be moved to a level area before stationing is attempted again.
2. Confirm the Elevation Setup toggle is off. Unless the job was specifically set up with elevation differences between control points, this toggle should be switched off in the app settings.
3. Re-record control points from the correct location. After the FieldPrinter has been moved to a level surface, control points should be re-scanned and stationing attempted again. The same points defined in the layout file should be used, scanned from approximately the same height at which those points are recorded.
4. Avoid scanning control points at a different elevation than what is in the file. If control points are set to elevation 0 in the layout, they must be scanned at ground level. Scanning from a significantly higher or lower position will consistently produce this error.
What to Avoid
- Stationing from an elevated structure when control points in the file are at ground level
- Scanning control points at a height that doesn't match what is recorded in the layout file
- Assuming elevation differences will be compensated for automatically