GNSS tracking ability

[PTsen]

Hi,

I would like to know the maximum velocity that the TESEO LIV3F chip can still having a stable update rate. I'm currently doing localization using TESEO LIV3F, and it update the position very slow under 3m/s. Perhaps that's because there are some trees and buildings when I'm moving around , but even if I'm at open space (at least 20m away from the building), I am still not getting the position updated. Therefore, I would like to know the maximum velocity that can guarantee TESEO LIV3F to continuously update its position.

Thanks

[Francesco Virlinzi]

Ciao

> maximum velocity that the TESEO LIV3F chip

On the max Teseo-LIV3F has to be compliant with ITAR regulation which are:

• speed: 515 m/s
• altitude 18000 m

When both are true the Teseo-LIV3F will STOP providing the position.

In General Teseo-LIV3F has a global max limits which are:

• speed 600 m/s
• altitude 100000  m

> it update the position very slow under 3m/s

under a specific threshold Teseo-LIV3F decreases the Fix rate.

To avoid that you can enable the 'pedestrian mode':

De-assert bit-15 in CDB-ID-200

Hope this helps.

Regards

Francesco

[PTsen]

Hi, thanks for your reply, it turns out that there are some conflicts in pin usage with my own extension board and X-NUCLEO-GNSS1A1, so I think that is the reason why GNSS kept giving me invalid data ('V' in GPGLL) even in open space.

BTW, regarding the pedestrian mode, is this the correct syntax ?

$PSTMSETPAR,1200,32768,1*3d 

I'm not pretty sure about it, despite the response says set par ok, but I'm not sure if the syntax is correct, or I'm just ruin all the settings in CDB 200.

[Francesco Virlinzi]

Ciao

> some conflicts in pin

Which conflict do you have?

X-Nucleo-GNSS1A1 has several jumper to route the signals on different pins.

>  so I think that is the reason why GNSS kept giving me invalid data ('V' in GPGLL) even in open space.

No. this should not happen.

Between "Antenna->RP_path->LIV3F" there is No pin dependency.

Do you see satellites?

> $PSTMSETPAR,1200,32768,1*3d 

It's almost correct but you should disable the stop-mode, the correct command is:

$PSTMSETPAR,1200,32768,2*3d 

take into account that the change will take effect after a reboot thefore you have to save on flash and reset.

The complete script is:

$PSTMSETPAR,1200,32768,2	change the CDB
$PSTMSAVEPAR save on flash
$PSTMSRR reset