NEO V2 Pro GPS

NEO V2 pro is DroneCAN standard GPS developed by CUAV. It integrates industrial-grade compass, barometer, autopilot status light, buzzer, and safety switch all in one package. It has the characteristics of high safety and strong interference resistance.

../_images/neo-v2-pro.png

Key Features

  • Processor

    • STM32F412

  • Sensors

    • Compass:RM3100

    • Barometer:MS5611

  • RTK Receiver

    • Ublox M8N

  • GNSS Bands

    • GPS/QZSS L1 C/A,GLONASS L10F ,BeiDou B1I,Galileo E1B/C,SBAS L1 C/A: WAAS, EGNOS, MSAS, GAGAN

  • Nav. update rate

    • RTK Up to 10HZ

  • Position accuracy

    • 2M

  • Acquisition

    • Cold starts 26 s

    • Aided starts 1 s

    • Reacquisition 2 s

  • Sensitivity

    • Tracking & Nav -167 dBm

    • Cold starts -148 dBm

    • Reacquisition -160 dBm

  • Protocol

    • support

  • Interface Type

    • GHR-04V-S

  • Input voltage

    • 5V

  • Operating temperature

    • -10~70℃

  • Size

    • 60x60x16mm

  • Weight

    • 33g

Purchase

You can buy it from CUAV store.

Connect to CUAV v5+

../_images/connection-to-v5%2B.jpg

Note

The connection to other autopilots is similar.

Enable CAN port, DroneCAN, and Configure for NEO-V2 Pro

See CAN Bus Setup and DroneCAN Setup for more information.

Set the following parameters in all parameter tables of Mission planner and restart after writing

../_images/fc-set.png

NEO-V2 is now ready for operation

SLCAN Interface

If you need to set up NEO V2 PRO or upgrade its firmware, you need to enable SLCAN

  • Please connect NEO V2 pro to the autopilot’s CAN1 interface.

  • Open mission planner and connect autopilot.

Modify the following parameters in the Full Parameter tab of Mission Planner.

for CUAV V5+/nano:

Note

CUAVV5 / NANO / FMUV5 autopilot running ArduPilot4.0 or later firmware will have two USB interfaces, one is autopilot’s console port (SERIAL0) running MAVLINK and one is an SLCAN interface port; if there are not two ports showing in the Mission Planner Comm Port drop-down box, please uninstall the driver and reinstall. If you continue to have problems, see Troubleshooting Composite Connections

For Pixhawk series / FMUv2 / FMU V3 / FMU V4

Note

STM32F4 does not support dual virtual USB ports, so autopilots using STM32F4 processor can only be used for SLCAN after the MAVLink connection on USB is closed; after writing the above settings, the USB interface becomes an SCLAN port; MAVLink connections can be made again after a reboot. Until then the USB connection can be used for SLCAN operations.

NEO-V2 Internal Configuration

ArduPilot supports setting DroneCAN device internal settings through SLCAN, such as modifying node ID; enabling / disabling barometer, etc.

../_images/slcan3.png
  1. Select the COMM port corresponding to SLCAN.

  2. Select the DroneCAN section under Initial Setup>Optional Hardware tab.

  3. Click “SLCAN NODE CAN1” and

  4. Click “Inspector”

  5. Change configuration parameters for DroneCAN device

Enable barometer

  • Baro_enabled=1, 0=disabled

  • Reboot

Modify device ID

  • Modify the CAN_NODE parameter

Upgrade Firmware

Method One: Firmware upgrade using Mission planner

../_images/slcan.png
  1. Select the COMM port corresponding to SLCAN.

  2. Click “SLCAN NODE CAN1” on the DroneCAN section under Initial Setup>Optional Hardware tab.

  3. Click “Update”

  4. Select “NO” in the pop-up prompt box (Tes is to select online firmware; No selects local firmware).

  5. Select firmware file.

../_images/slcan2.png
  • Wait for the flash process to complete.

Method Two:

Upgrade with DroneCAN GUI TOOL software

DroneCAN GUI TOOL.

  • Select the device port corresponding to SLCAN and click “ok”

../_images/uavcan.png
  • Click “√”; then double-click on the device information (marked in Figure 2 below).

../_images/uavcan2.png
  • Click “update firmware”, the message box will pop up “yes”.

../_images/uavcan3.png
  • The mode/heakth/uptime entry becomes “SOftware_update”

../_images/uavcan4.png
  • Waiting for firmware write to complete.

../_images/uavcan5.png

More information

CUAV docs.