the coordinates (latitude and longitude) of the Teseo-LIV3F

[Iyaku]

Hi! Why are the coordinates (latitude and longitude) of the Teseo-LIV3F changing abruptly and not smoothly like the u-blox M8 and NV08? Smooth change of coordinates is very important to me, since the direction angle is calculated in our program precisely

[Francesco Virlinzi]

Hi

More probably the Stop Detection algorithm is reducing the fix evaluation frequency.

You can try disabling it in the CDB-200 bit[15].

Hope this helps

Regards

Francesco

[Iyaku]

Hi

Thanks for the help!

I will try to check your advice.

What does the walking detection algorithm do?

[Iyaku]

Hi

Turned off the Stop Detection algorithm in the CDB-200 bit [15] - the end result has not changed, jumps in the track angle are observed. What else can be done?

[Iyaku]

[Francesco Virlinzi]

Just a question looking the image...

Are you comparing devices with the same frequency FIX rate?

Are both the device running at 1 Hz FIX?

Thanks

Regards

Francesco

[Iyaku]

Hi

I compare devices with the same FIX frequency.

Both devices operate at 4 Hz FIX. Devices work on GPS, Galileo, Beidou.

UART 9600, NMEA RMC, and GGA output rates.

[Francesco Virlinzi]

> Both devices operate at 4 Hz FIX. Devices work on GPS, Galileo, Beidou.

I did an experiment with your setting and I can see the CPU is 100% of it's time....

In our default CPU runs @ 48Mhz it seems not enough in your setting...

You can increase the CPU speed @ 196MHz with this commands:

> $PSTMSETPAR,1130,00,0

> $PSTMSAVEPAR

Regards

Francesco

[Iyaku]

I forgot to say, the frequency has already been set to 196 MHz.

[Francesco Virlinzi]

> I forgot to say, the frequency has already been set to 196 MHz.

ok.

Could you try enabling the walking mode? It 's an optimization in case of low-speed.

Regards

Francesco