There are not two components. RTCM3 is embedded in the MAVLink telemetry and updates at 5Hz when using recommended settings. Raw RTCM3 messages have a maximum packet size of 1023 bytes but are typically about half that size for F9P fixed base installations (varies with satellites visible and constellations enabled). MAVLink RTCM3 messages have a few extra bits of overhead for the MAVLink message type/format information.
I disagree.
RTCM3 may be embedded in the MAVLink telemetry - but it’s optional - it only happens if you’re doing RTK.
Just because there’s only one conga line, if there are two people in that conga line, there’s still two people.
And the Mission Planner Config screen doesn’t allow a way to throttle it’s RTCM3 bandwidth - as it does other telemetry.
It’s still only one telemetry stream.
This is an addendum to this thread to anyone finding it for help with this topic.
Some comments on this thread mention the use of RTS/CTS. This is an option on the RFD900 (and perhaps other SiK radio) configuration. This is flow control between the radios.
But there is also flow control available between the flight controller and SiK radio - and the ground control computer and SiK radio.
If the RTS/CTS pins on the Telem port are connected properly to the SiK radio, there is an ArduPilot parameter to enable it: BRD_SER#_RTSCTS - where “#” is the serial port. This is might be helpful if the flight controller’s serial port baud rate is faster than the SiK radio’s air rate.
On the ground control computer, I believe this is enabled (on Windows) by going to the COM port properties in the Device Manager, and turning on Hardware Flow Control in the Properties.