Add ntrip client [v4.0] [CPP-944]

[adrian-kong]

• adds additional ntrip subtab to advanced tab
• adds--enable-ntrip flag, safe to merge since this feature is off by default
• static option (manual input) and dynamic (auto lat lon alt values)
• output options, RTCM or SBP out
• bundles rtcm3tosbp binary under /binaries/{OS}/rtcm3tosbp(.exe)
• adds additional hidden until running status bar to capture amount of bytes

[adrian-kong]

with regards to the options that we want to parse, is it something like...

general textfields that we must have:
URL, USERNAME, PASSWORD

• radio button, [GGA/CRA]

if GGA:
  add LAT, LON, ALT textfields
elif CRA:
  add REQ_COUNTER, AREA_ID, CORR_MASK, SOLN_ID text fields

i.e. main fields we want / capnproto struct is:

struct NtripConfig {
    url, username, password,
    (if gga then fill in...) lat, lon, alt
    (if cra then fill in...) req_counter, area_id, corr_mask, soln_id
}

add connect and disconnect button

on connect basically run main function from https://github.com/swift-nav/ntripping/blob/master/src/main.rs#L277 (maybe we should turn this into lib to reuse?)
on disconnect basically kills the thread ran in main.

• add some additional capnproto packets to send byte info, error log, ntrip config etc...

also havent touched ntrip before... didnt really understand what we wanted to do with the emitting output from ntripping.

@silverjam

[silverjam]

• radio button, [GGA/CRA]

Information for build GGA should come from two sources:

• Static, entered by the user
• Dynamic, from the lat/lon position emitted by the device

We don't need CRA for this feature.

[silverjam]

on connect basically run main function from https://github.com/swift-nav/ntripping/blob/master/src/main.rs#L277 (maybe we should turn this into lib to reuse?)

Could be useful eventually but I don't think we should pursue right now, let's see what's common between the two implementations before we make a decision to create a common library.

[silverjam]

also havent touched ntrip before... didnt really understand what we wanted to do with the emitting output from ntripping.

Ntrip is a protocol Skylark uses for delivering corrections to the device, the location of the device is sent to the server so that it can either: (1) fetch region specific error correction information; (2) model a virtual base station in order to provide error correction. Data from Ntrip needs to be routed to the device in order for it to correct it's position.

[swiftnav-travis]

Frontend and Release Workflow Started here

[swiftnav-travis]

Frontend and Release Workflow Started here

[pcrumley]

LGTM... however do you need to port the unrelated bugfixes in resources/SettingsTabComponents/SettingsPane.qml file in the other PR to this one? or were those bugs introduced after v4.0

[silverjam]

Agree with @pcrumley -- let's make sure we don't miss anything from https://github.com/swift-nav/swift-toolbox/pull/1088/files#diff-426f1e106c29afd7217275dd47a806603df0770a48d007397e430ee887fc1949 (if these changes are needed on this branch).

[adrian-kong]

the changes for parents -> parent seem to be a typo causing ReferenceError (introduced later)
the changes for height seems to be an issue on both branches - settings pane cutting off or scroll bar doesn't adjust to the amount of content on page (will revert this unrelated changes (doesn't seem to fix the issue) for both branches and logged a ticket: https://swift-nav.atlassian.net/browse/CPP-953 if this ever becomes an issue again)

[swiftnav-travis]

Frontend and Release Workflow Started here

[adrian-kong]

moved to SCD board https://swift-nav.atlassian.net/browse/SCD-3