Your Ditch Assist Lite, start to finish
Do these in order. Open step 1, then keep tapping Next: each page takes you on to the next step of this list.
1Know your kit
2Get the tablet and app ready
- 3Install the appDownload from the website, allow the install, update over the top.
- 4Set up the tabletFile access, Location, Wi-Fi that stays put, screen, power, updates.
- 5First launchFile access, the manual reminder, the safety warning, Home, blade height.
- 6App tourHome, sidebar, Settings, Manual, and the Survey and Grade screens at a glance.
- 7Practise with the simulatorA guided practice session: survey, design and grade a pretend ditch, one tap at a time.
3Get the Reach working
- 8Choose Lite modeSwitch the app to Lite mode, and what changes when you do.
- 9Get the Reach readyCharge, mount, corrections and position output for the Reach.
- 10Power the receiverBattery for a day, charge overnight, power bank for long days.
- 11Connect to the ReachJoin the Reach hotspot, tap Emlid Reach, wait for RTK Fixed.
- 12Activate a receiverRequest code by email, 10-digit unlock code back, once per receiver.
4Your first day in the field
- 13Working in Ditch Assist LiteStart guidance, follow the Depth Guide, move the blade yourself.
- 14Pre-flight checksRead the Pre-Flight Checks panel row by row and test raise and lower.
- 15Blade heightCutting edge to ground, implement raised. Measure it, enter it, check it.
- 16Benchmarks and calibrationSame day, same base: just grade. Coming back: calibrate on the field's benchmark.
- 17Your first jobChecklist to finished pass: a whole Ditching job, in order.
Download this whole list as one PDF manual (PDF, 252 pages, 18.5 MB). Same steps, same pictures, for printing or for a tablet without signal.
Not your kit? Full Automation Kit · Guidance Only Kit · DIG™ Kit
Did this answer your question?
Thanks. That tells us which pages to improve.
Still stuck? Talk to a product specialist. 1-833-DITCH-AS · support@ditchassist.com · Monday to Friday, 8 a.m.–5 p.m. Central.
Calling about a problem? Send your app logs first so support can see what happened.