Suggested Category: Setup → Control & Stationing
Audience: VDC Coordinators, Surveyors, Field Operators
Tags: control points, CSV, surveyed control, file prep, portal upload, unit errors, coordinate systems, duplicate CPs

Overview

Control Points (CPs) define how your design aligns to the physical jobsite. When surveyors provide coordinates, Dusty imports them through a simple CSV file. This article explains how to prepare, upload, and manage CP CSV files so your FieldPrinter can station accurately and your layout aligns correctly.

1. Required CSV Format

For all CSV files, for both control points and printable points, the CSV must include the correct column headers and structure. The Dusty Portal accepts:

• Name,x,y,z,description
• Name,e,n,z,description

Rules:

• Name, x, y, z columns are required; description is optional
• Column names must match exactly (lowercase, no extra spaces).
• No additional columns, hidden fields, or trailing commas.
• Coordinates must be numeric (no text, units, or formatting).
• Use the same coordinate system as your surveyor.

Dusty will print the name of the point, then a colon ":", and then the description on your jobsite.

Common Upload Failure:
Customers often see an upload error when extra or no columns exist in the CSV. Removing the additional fields resolves the issue.
 

2. Units and Coordinate System Requirements

To avoid scaling or alignment issues:

• Avoid “unitless” DWGs—these frequently cause Portal errors or invisible CP shifts.
• Ensure survey and model coordinates use the same orientation and baseline.
• Avoid mixing coordinate systems for different trades.

If you’re unsure what units your surveyor used, ask them to confirm before exporting the CSV.

3. How to Upload a CSV Control File

Follow these steps in the Dusty Portal:

1. Navigate to your project.
2. Open the specific layout file.
3. Click Upload Files.
4. Choose your prepared CSV file.
5. Publish the updated layout file.

Important: Updating a CSV requires publishing the file again for the changes to push to the iPad.

4. Updating or Replacing Control Points

To update CPs

1. Delete or deselect the old CSV in the Portal.
2. Upload and select the new CSV.
3. Publish the file.
4. Ensure the FieldPrinter operator downloads the new version to the Dusty App.

Why this matters

If you only upload a new CSV without deleting the old one, the robot may retain outdated CPs in its cached control layer. This can result in operators seeing duplicate or outdated control points on the tablet.

Republishing removes this mismatch.

5. Confirming CPs in the Dusty App

After publishing:

1. The operator goes to Files and taps the Update button.
2. The operator opens the Project on the tablet.
3. Navigate to Station → Control Points.
4. Verify that only the expected CPs appear.

If you still see old CPs:

• The operator may be viewing a cached file.
• Have them refresh or delete/re-download the layout file.

6. Troubleshooting CSV Control Issues

CSV Fails to Upload

Check for:

• Missing and extra columns in the CSV
• Incorrect header names
• Blank rows or non-numeric values

Control Points Don’t Appear in the App

Causes include:

• Layout file not republished (file in Edit Mode).
• Old CSV remnants stored on the robot
• Operator opened a cached version of the file

Publish the file again and re-download on the iPad.

Duplicate CPs Appear

Occurs when:

• Operators previously downloaded a file containing an older CSV
• A new CSV was uploaded but the old one was not cleared

Fix by:

1. Deleting the control layer on the robot.
2. Republishing the file.
3. Re-downloading on the Dusty App.

CPs Show Incorrect Locations

Likely causes:

• Wrong coordinate system
• Y/X swapped during export
• Scaling issues from Revit or CAD
• Mixed DWG units

Best Practices for Reliable Control CSVs

• Always verify the coordinate system with your surveyor before export.
• Keep your CSV clean—no extra fields or embedded formatting.
• Name CPs clearly (e.g., CP01, CP02).
• Re-upload and republish whenever any CP changes.
• Maintain consistent units across DWG and CSV workflows.
• Validate CP locations in the Portal before sending to operators.