Pixhawk V1 + SiK 915MHz Radio over UART

[Kmenezes (Keith M)]

Are you saying is that the Emlid Reach RTK doesn’t integrate completely with Pixhawk (Ardupilot) with long range radios and dual GPS?

Clarifications
-So is your communication over serial with the SiK radio actually working or are you using TCP?
-What did you alter in the code (ardupilot and/or reach)? How do I recompile reach code to the module? Is it a grueling task?
-Have you tried flying with reach as primary and only GPS? What were your results?

Came across your post in this topic which is related, can you comment on the parts I bolded/italicized.
Wondering if these four (4) main bugs have been fixed?:

@Amilcar_Lucas

Reach has at least four known bugs that mess up integration with ardupilot. I already corrected them, on my public github repository but Emlid has not merged the fixes yet, so reach does not integrate that well with ardupilot:

• hdop is messed up so dual GPS does not work (although recommended by Emlid)
• horizontal and vertical accuracy information is also messed up (again affects dual GPS)
• speed accuracy information is missing
• Ground course calculation is bogus wrong signal and 90deg offset, (EKF will get confused merging the information with a compass)
• GPS timestamps are messed up in versions prior to reach 2.5.2

@Amilcar_Lucas

One of the problems with Reach is that the reported ground course (heading) is wrong.

@Amilcar_Lucas

Missing speed accuracy information also makes it harder for the autopilot to blend the two GPSs. It would be nice to see it implemented. The ERB driver in the Ardupilot code already flags it as valid although it is not. But that will stop being a bug as soon as Emlid implements it on the reach side

When using reach as primary and single GPS source (against Emlid recommendation) should work