Hi @TCIII ,
Here is my test setup:
I have a Postcard + Shield running RTK Everywhere 2.2 (July 16th). The LG290P is running the v05 firmware.
I have re-flashed the LG290P using QGNSS so we have a known starting point.
I have set the RTK Firmware back to its Factory Defaults, so we have a known reproducible starting point. Options “s r y” from the serial menus.
I put the RTK Firmware into Base mode with “s B x x”. It performs its survey-in. This completes and it begins transmitting corrections. These are accessible via the white locking JST connector, which connects to LG290P UART3.
I am using a logic analyzer to study the data on the JST TX pin. It is 115200 baud and contains a mix of NMEA and RTCM. The RTCM messages are: 1005, 1033, 1124, 1074, 1084, 1094, 1114. I.e. is is outputting MSM4.
I have an LG290P Breakout which I am using as my Rover. It too is running v05 firmware. I have re-flashed it just to be sure.
Here is what I see using QGNSS on UART1 (via the USB connector and the CH342):
The white JST connector on the Breakout provides access to UART3 also.
I use JST cables to link the Postcard to the Breakout: GND to GND; Postcard UART3 TX to Breakout UART3 RX.
UART3 on the Breakout defaults to 460800 baud. The Postcard is outputting corrections at 115200 baud. I change the baud rate on the Breakout using QGNSS, and sending $PQTMCFGUART,W,3,115200*07.
The effect is immediate. I see:
The white LED on the Breakout is illuminated.
@TCIII : as a starting point, please try and replicate this. Please ensure you have a wire link from JST to JST. Please do NOT use Radio. Start with wire. Once you have this working, you can start to make changes: one at a time - and re-test.
It is 6:30PM here. Please send updates and I will read them in the morning.
I hope this helps,
Paul