TX2: (1) What is the maximum rate for RTCM3 MSM7 (1077/1087/1097/1127) output — can it sustain 10 or 20 Hz? (2) With “Output GNSS data to USB serial” enabled, what is the USB baud rate, and does it carry MSM7 at that rate without drops? (3) Does the TX2 have any onboard storage? (4) What USB-serial chip does it use?
Welcome @whesse99 ! Great questions.
- Generally yes, but it do you want NMEA as well or just MSM7?
Above is pygpsclient showing RTCM parsing from the TX2, MSM7, 1077/1087/1097/1127 at 20Hz.
-
115200bps. It appears to not be dropping any data but this is visual inspection only.
-
No, not really.
-
CH342 dual USB to serial IC capable of going up to 921600 or above. Currently the TX2 firmware doesn’t allow modification of the USB serial baud rate, but we could add that if needed.
Thanks — very helpful. For Q1: MSM7 only (1077/1087/1097/1127 + 1005 at 1 Hz); NMEA off or ≤1 Hz on the second port.
On Q2, my concern is bandwidth: in open sky with all four constellations, a multi-band MSM7 epoch is roughly 1.0–1.4 kB, which at 115200 (≈11.5 kB/s) caps us around 8–10 Hz before the UART saturates. 20 Hz would need ~25–30 kB/s.
Could you add a configurable USB serial baud rate (460800 or 921600)? That would be a deciding factor for us. And if possible, could you run a 10-minute open-sky test at 20 Hz and check for gaps in the MSM epoch times per constellation, rather than message counts?
Yup. Feature request here. Release candidate has the feature.
I’ve limited the baud rates to just 115200 and 921600 so that a user who has lost connectivity has just two bauds to try.
I don’t have a chance at the moment to run the 20 minute test. I encourage you to give it a try.
Welcome @whesse99,
I know there is a good chance you cant share the details, but there is likely a neat backstory to needing MSM7 at 20Hz. I’d love to hear it if you can share ![]()
We are creating point clouds from video and gnss and need 20Hz to get the resolution.
See https://4d-360.com/ for detail/demos.
Just purchased a TX2 in Oz.
Thanks for your help.
Walter
Wow, what a great reason for 20Hz MSM7 !
I’d love to chat about the registration across frames for the model… if you ever have time for an email.
with the old RTK torch I used IMU sync between its IMU and camera IMU to transfer GNSS time to video frames.
On the TX2 I will use GNSS Kinematic to sync (that is working now on the RTK torch as well with 3ms difference).
All good fun.

