Add TCP Connection to DGPS
Emlid Reach GPS can only publish the RTCM corrections using TCP or Serial connections. This adds the ability to select between UDP and TCP and allows configuration of the IP, PORT, CONNTYPE. It adds four commands (following the ntrip modules model): start stop status set
by default it is configure the same as it was before (UDP, 127.0.0.1, 13320)
I don't have a GPS that publishes corrections via UDP to test, but it should work. I did test the TCP connection
based on: https://github.com/antonvh/MAVProxy/tree/reach_inject by @antonvh
I have already added the status count for each packet, So that can be seen with the status command.
@tridge This seems to be working pretty good now, let me know if you want me to squash the three commits into one, but I think its ready to merge.
Squashed
please test with both py2 and py3
This needs a rebase and some more testing. Part of the functionality is a duplicate from #408. I will close #408 in favor of this one if this ones gets more testing
do you have a build that I could test/run? Really interested in this feature. we have a Emlid Reach M2 we would like to automate RTK corrections with via Rpi, but having troubles rebasing this branch on master and actually testing functionality