An RTCM output request is complete over the receiver's whole RTCM output: message types not named are turned off, including receiver-specific output outside the modeled group (MSM4, MSM7, ARP). The Allystar configurator now turns the broadcast-ephemeris targets off on every request, which the TAU1302 ships enabled, and there is no CLI vocabulary to leave them as found (and none to re-enable them until #282).
gpsprot.RTCMMsgOther already carries the leave-as-found semantics: a request with it set is restricted to the modeled group and leaves out-of-group messages alone. The Allystar backend honors it; the flag just is not reachable from the CLI.
- Accept
other in --rtcm-out (e.g. --rtcm-out MSM7,other, --rtcm-out other to turn off only the modeled group) and emit it from the flag's String().
- u-blox: an other-only request currently disables the RTCM3 port protocol and errors on models without RTCM support; with
RTCMMsgOther set it should leave the protocol mask alone, zero the known message rates, and not error when there is nothing to turn off.
RTCMMsgAuto/RTCMMsgAutoMSM7 must not include RTCMMsgOther.- Update the man page and the wire-format paragraph of
gpshwtest/SEMANTICS.md (completeness is over the whole protocol unless other restricts it to the group).
This is also what gpshwtest needs to restore the TAU1302 as found: its RTCM probes and restore can then say ...,other and the shipped ephemeris output survives the run instead of being reported as an unrestorable vocabulary gap.
An RTCM output request is complete over the receiver's whole RTCM output: message types not named are turned off, including receiver-specific output outside the modeled group (MSM4, MSM7, ARP). The Allystar configurator now turns the broadcast-ephemeris targets off on every request, which the TAU1302 ships enabled, and there is no CLI vocabulary to leave them as found (and none to re-enable them until #282).
gpsprot.RTCMMsgOtheralready carries the leave-as-found semantics: a request with it set is restricted to the modeled group and leaves out-of-group messages alone. The Allystar backend honors it; the flag just is not reachable from the CLI.otherin--rtcm-out(e.g.--rtcm-out MSM7,other,--rtcm-out otherto turn off only the modeled group) and emit it from the flag'sString().RTCMMsgOtherset it should leave the protocol mask alone, zero the known message rates, and not error when there is nothing to turn off.RTCMMsgAuto/RTCMMsgAutoMSM7must not includeRTCMMsgOther.gpshwtest/SEMANTICS.md(completeness is over the whole protocol unlessotherrestricts it to the group).This is also what gpshwtest needs to restore the TAU1302 as found: its RTCM probes and restore can then say
...,otherand the shipped ephemeris output survives the run instead of being reported as an unrestorable vocabulary gap.