Skip to content
English
Customer portal
Ask ASD GPT Here
  • There are no suggestions because the search field is empty.

Navigation Velocity error on the EAV J150  or J70. 

 This article outlines the steps to fix the Navigation Velocity error on the EAV J150, worked in order, before concluding the CPU needs to be replaced

Please follow the steps below to resolve this issue.

IF YOU RECEIVE THE FOLLOWING ERROR:

Navigation Velocity Error (33-008) 

This error most often appears after a crash or a rough landing. Before you start, note whether either happened — it points to physical damage rather than a software fault, and it matters for a warranty or parts conversation later. 

Complete the steps below to resolve the error and get your drone back in the air

Work the steps in order. Each one is cheaper and faster than the one after it, and the last several involve replacing parts. If a step clears the error, stop there and return the drone to service.

Key Steps

1. Hard Restart the Aircraft

  • Perform a full hard restart of the aircraft. Main battery off, then internal CPU battery off with the 40-second countdown 
  • Power the aircraft back on and check whether the error is still displayed.
  • If the error is gone, the drone can return to service. If it is still present, continue to step 2.

2. Run a Compass Calibration

  • Run a compass calibration on the aircraft. 
  • Check whether the error clears once the calibration completes.
  • If the error is still present, continue to step 3.

3. Clear the Historical Fault Log

  • Clear the historical faults stored on the aircraft. 
  • Check whether the error clears.
  • If the error is still present, continue to step 4.

4. Soft Restart the Domain Controller

  • Perform a soft restart of the domain controller. 
  • Check whether the error clears.
  • If the error is still present, continue to step 5.

5. Hard Restart the Aircraft a Second Time

  • Perform another full hard restart of the aircraft.
  • This second restart matters — the calibration, the cleared fault log, and the domain controller restart from the previous steps may not take hold until the aircraft has been power cycled again.
  • Check whether the error clears. If it is still present, continue to step 6.

6. Check Power to the CPU at the 485 Cable

  • Check the power supply to the CPU through the 485 cable. 
  • Inspect the cable and both connector ends for damage, corrosion, pinching, or pins that have been pushed back.
  • Replace the cable if it is damaged. 
  • If the error is still present, continue to step 7.

7. Swap in a Known-Good Main RTK Antenna

  • Replace the main RTK antenna with a known-good unit — new or one pulled from an aircraft that is currently flying without this error.
  • A second antenna of unknown condition proves nothing. If you do not have a known-good unit, stop here and call ASD tech support rather than guessing.
  • Check whether the error clears. If it is still present, continue to step 8.

8. Swap in a Known-Good Secondary (Sub) Antenna

  • Reinstall the original main antenna, then replace the sub (secondary) antenna with a known-good unit.
  • Check whether the error clears. If it is still present, continue to step 9.

9. Replace the CPU (Main Control Module)

  • If none of the steps above resolve the error, the CPU itself is the cause.
  • Contact ASD parts or tech support to order a replacement J150 CPU. 
  • Check whether the error clears once the replacement CPU is installed.

10. Contact ASD Tech Support

  • If replacing the CPU does not resolve the error either, contact ASD tech support at 573-306-2818.
  • Have the aircraft serial number, the date and description of any crash or rough landing, and a list of the steps you have already completed ready when you call.

 

Cautionary Notes

  • Work the steps in the order listed. Jumping straight to antenna or CPU replacement is the most common way to spend money on a part that was never the problem — this error frequently clears on a restart or a compass calibration.
  • Antenna swaps only tell you something if the replacement is known-good. Swapping in a spare of unknown history can leave you chasing the wrong component.
  • Note a crash or rough landing before you start troubleshooting. That history is the strongest indicator of what actually failed, and it is needed for any warranty conversation.
  • Do not conclude the CPU is bad until every step above has been completed. The CPU is the last item on this list because it is the last thing left, not because it is the likely cause.

Tips for Efficiency

  • Keep a known-good main and secondary antenna on the shelf so the swap tests in steps 7 and 8 can be done the same day instead of waiting on parts.
  • Write down which step cleared the error. If the same aircraft comes back with it again, that record turns a full ladder into a single check.
  • Re-check the error after every step rather than running several changes at once — otherwise you will not know which one fixed it.

Stay Informed: Subscribe to the Agri Spray Drones Newsletter

How to Subscribe

Subscribing is easy and takes less than a minute:

  1. Visit Our Website
    Go to www.agrispraydrones.com
  2. Scroll to the Bottom of the Homepage
    Look for the “Subscribe to Our Newsletter” section.
  3. Enter Your Email Address
    Type in the email address where you'd like to receive updates.
  4. Click “Subscribe”
    Once you submit, you'll be added to our mailing list and will start receiving valuable updates straight to your inbox.

Don't Miss Out

Join thousands of ag professionals who trust Agri Spray Drones for the latest in drone spraying and precision ag.
Subscribe today — and let us help you take your operation to the next level.