2025-06-13 1:23 PM
I received a Vespucci Dev Board from Future Electronics that has a Teseo LIV4F on it. I am currently trying to update it to output the RMC and VTG messages at a 10 Hz Output. I was able to set the 10 Hz rate with the following:
$PSTMSETPAR,1303,0.1
$PSTMSAVEPAR
$PSTMSRR (Reset Chip)
This worked to set it to update at 10 Hz.
I then used the following to limit the messages incoming to only VTG and RMC.
$PSTMSETPAR,1201,50
$PSTMSAVEPAR
$PSTMSRR (Reset Chip)
This worked to limit the messages to only those, but now there is not a new line between each VTG and RMC message. The new line only comes after both messages are received as shown by the following image of my terminal viewer.
Any help to get the new line to send between each message is appreciated!
2025-06-17 5:14 PM
Hi Matt,
I am guessing you are using a UART to USB cable to interface from Vespucci to PC.
Have you tried opening this output in Teseo Suite? This is just a sanity check on how the output is coming out.
Also, have you tried to add GGA and see if this makes a difference?
By the way instead of overwriting the complete register you can do bit SET or RESET by adding a bit mask. You can mask (SET or RESET) multiple bits instead of just one bit.
$PSTMSETPAR,1201,0x80, 1 //this will set CDB-201-bit[7]
$PSTMSETPAR,1201,0x80, 2 //this will reset CDB-201-bit[7]
I will try this on a LIV4F and will let you know in a couple of days.
2025-06-20 8:51 AM
Hi,
I checked with our app engineers and this is a bug in the module firmware for this message list combination. I was also able to reproduce this.
Is CR/LF used to check end of NMEA sentence ? Instead of CR LF to end of NMEA, can you use "$" to detect the start of next NMEA sentence?
2025-06-20 9:06 AM
I use the new line to check for the end of the incoming NMEA message. That could be an alternative route we could investigate. Thanks!
2025-06-25 5:10 AM
Hi,
Our app engineer suggested a workaround.
It looks like there is some issue with enabling UART and I2C together, therefore you can disable I2C
$PSTMSETPAR,1263,0x1,2
$PSTMSAVEPAR
$PSTMSRR
After setting this, I can see the NMEA output as
GNGBS is output because CDB-228 bit-mask 0x2000 is SET.
If you are fine with using this workaround you can use CR/LF and start of NMEA message.