Hi @svetlana.nikolenko unfortunatelly I am experiencing the same behaviour with legacy RTCM3 messages. Check here