LIV4F RTCM input setup

[MHoll.2]

I'm new to the LIV4F (I have a Teseo-LIV4F evalution kit), coming from u-blox.

We have an NTRIP Client who delivers RTCMv3 data to the serial Port of the LIV4F, but the data seems to be ignored (the same data with a u-blox ZED-F9P is working fine).

Do I have to enable the receiving of RTCM data in the LIV4F?

[GalaxyQuest · Accepted solution]

LIV4F cannot use RTCM NTRIP RTK data and provide you a precise fix. LIV4F can output RTCM measurements for a host running RTK engine. This host can use NTRIP data and LIV4F measurements to provide precise position.

However, LIV4F can accept corrections RTCM MSM1 corrections data from NTRIP and provide a few decimeter level accuracy.

https://www.st.com/content/st_com/en/campaigns/multi-constellation-decimeter-level-positioning-stand-alone-gnss-module-teseo-liv4f-for-industrial-and-iot.html

To accept MSM1 corrections in RTCM, program LIV4F with firmware with MSM1 tag.

[MHoll.2]

Hi GalaxyQuest,

I got it working with the dedicated Firmware ( long time deviation standard as expected about 0.5m).

Can You confirm that the requested messages are:

RTCM1071 (MSM1 GPS)

RTCM1081 (MSM1 GLONASS)

RTCM1091 (MSM1 Galileo)

RTCM1121 (MSM1 BeiDou)

RTCM1006 ( Station description with Antenna Height) or RTCM1005 (Station description)

is there any possibility that in future the LIV4F will support MSM4 or MSM7 as stated in the data sheet (chaper 3.3 on page 7)?

Martin

[GalaxyQuest]

Hi,

Yes the above RTCM-MSM1 messages are supported.

If you update the LIV4F with DGNSS firmware and connect to SwiftNav network you can see the messages coming into LIV4F in Teseo Suite.

In Teseo Suite, during device connection, enable NMEA and RTCM. You should be able to see RTCM messages when you click the Monitor icon.

[hw-rx]

Hi,

In the Teseo-LIV4FSW Data Brief DB4875 - Rev 2 - June 2024, it is mentioned that the STA8041_LIV4F_PVT_STD firmware "can accept RTCM MSM7 message correction data from the host". I tried to test the functionality by sending MSM7 messages to the EVB-LIV4F, but the NMEA GGA quality indicator remains in state "1".

I then tested the STA8041_LIV4F_PVT_MSM1 firmware while sending MSM1 messages to the EVB-LIV4F, and in this case I can see the NMEA GGA quality indicator changing to state "2".

Also, the Teseo-LIV4F Datasheet DS13957 - Rev 6 says that MSM4 messages are even supported in Section 3.3 (Table 3).

Does the PVT_STD firmware support MSM7 message input?

Does the EVB-LIV4F support MSM4 message input?

[GalaxyQuest]

Hi,

LIV4F can only accept MSM1 messages.

The PVT_STD firmware only outputs PVT in NMEA format, no carrier phase output is present.

In the ME firmware, LIV4F outputs carrier and code phase measurements in MSM7. This can be used by a host running RTK.

[hw-rx]

Hi GalaxyQuest,

Understood, thank you for the response.

One more question, can the LIV4F accept either the 1005 or 1006 RTCM message along with MSM1 messages?

[GalaxyQuest]

Hi,

I was looking at the Teseo Suite input log for DGNSS and 1006 and 1008 messages are provided as input to the module. So to answer your question, yes, we support 1006 input to LIV4F.

[hw-rx]

Thanks for your reply. So what I understand is 1005 is not supported.

Can you confirm if 1008 is needed along with 1006?

Thanks!