Sure, it’s possible. You’ll need a USB-UART like CP2102 to get UART-stream from Reach.
Reach outputs solution to a UART which needs to be process by ArduPilot. It’s treated as a second GPS. To achieve this you just launch ArduPilot with an additional switch -E /dev/ttyUSB0. (-E is a switch for additional GPSs)
Other than that the instructions are applicable for Navio 2 as well as for Pixhawk.
so, just to clarify, the USB port on REACH receiver cannot send data to NAVIO2 without a seperate piece? This converts the REACH uart to raspi friendly usb com port?
Yes. You should connect Reach RS as a client, then choose Serial->USB-to-PC in position output options. That’s it. Make sure you update first, as some critical bugs related to USB-to-PC were fixed in the recent versions.
I have noticed that when it comes to the USB interface …there is a possibility that the usb port can get renamed to a different dev label.
In my case I noticed that during my tuning process mission planner began to report rtk float while in the emlid viewer it was reporting a fix. I also noticed during this time that my positioning was very unstable. This led me to belive that the rover was using the onboard navio2 gps instead of the the reach rs.
upon inspection of the /dev/ directory . I noticed that the usb device had changed to /dev/ttyACM1 instead of /dev/ttyACM0. This of course did not match what was in my /etc/default/ardurover. But the weird thing was that mission planner maintained the rtk float message rather than display 3D GPS.