I have a pair of Reach units that I am attempting to set-up as an RTK system to use on a rover. After some difficulty I have been able to connect to each device via wifi and to configure them (following the documentation). As they should, both devices connected to the server and downloaded the latest version of ReachView (2.5.2 I believe). I want to use a pair of 3DR radios (connected to the UART) to send corrections form the base to the rover. I used MissionPlanner to assign a unique NetID to the radios and to set the baud rate (57 which I assume to mean 57600).
I also checked the baud rate of the associated COM port for each radio - it too was set to 57600. When I power up the base and the rover I can see that each is seeing satellites and calculating a position (though not corrected). The bar chart on the status page shows satellites (w/ varying SNRs) but there is no evidence of grey bars on the rover’s display indicating base corrections are not being received. The LEDs on the radios are solid green and flickering red (at a fairly high rate but not apparently at a fixed rate). If I look at the logging tab, the base correction log (on the base Reach) is increasing suggesting that correction messages are being generated. This all suggests to me that the problem lies in the radio link. I believe the radios are working when I used MissionPlanner to change the NetID, the radios’ green LEDs flickered and then went solid green. I interpret this (based upon Sik radio documentation) to indicate they were looking for another radio when they were powered up (green flashing LED) and when they found each other the LED switched to solid green.
I would appreciate any constructive suggestions. By the way, to honor the wiring information in the Reach documentation, I had to switch the RX/TX wires on the DF13 cable supplied with the Reach units. Is there a reason why they are delivered with the incorrect wiring connection?
Thanks in advance!