Mapping: Boundary Edges, Modules, No Go Zones

Support & Solutions Mapping Issues
1

Please provide the standard operating procedure for precision mapping the boundary lines and No Go Zones (NGZ).

  • List item
    https://bit.ly/OffRouteEnteringNoGoZones
    Initially created maps with the desired module (M1, S1, Hitch) connected to provide for clearance with the width of the module. The Core (with the same module attached) routinely overruns boundary lines with Med.+ GPS signal, resulting in collision and/or track slippage.

What is the “marker” when mapping? The Core left track edge, right track edge, center of core? Are the dimensions of the connected module taken into consideration when executing a work plan within mapped areas to prevent collisions? Are the patterns taken into consideration when executing a work plan? Is a dead end a true navigation and reverse (without veering or turning)?

Tech support has reviewed incident logs and photo/video of collisions causing RTK antenna damage & surrounding area damages.

Supports conclusions & the mapping tutorials (video & manuals) vary on how to accurately perform this critical setup step.

Thank you!

2

The center of the core between the two RTK antennas is the mapping reference point. It supposedly takes the module sizes into account, but not usually when turning or coming from an angle. If you are using templated no go zones, then I would recommend using the rover to map the NGZ’s. In areas where you have GPS issues, make the NGZ 30cm larger than it needs to be in order to have a safety buffer.

Use dead ends to mow for “precision” in these zones, but make sure that they start out in the open areas and go straight in. If the dead end is within a mapped area, when backing it will use the area to do turns. It assumes it is safe to use the area to do so. Dead ends will ignore NGZ’s, so this shouldn’t be an issue. Going straight will help if there is GPS issues. Going faster in weak or dead GPS areas can help too in some instances because it may recover GPS signal quick enough that dead reckoning doesn’t get too far out of sync (it loses precision over time and distance traveled).

3 Likes