Sparkfun F9R calibrate IMU and wheel tick?

Hello, I have some questions regarding the use of the SparkFun ZED-F9R in dead reckoning mode for indoor use.

I have the SparkFun ZED-F9R in dead reckoning mode as a rover station, connected to a RTK base station with RTK float and fix corrections. After calibration according to the manual, it is now in dead reckoning mode, and the status is 3D + DR/Fixed or Float in fusion mode. However, I do not have a wheel tick sensor.

1.	When using it indoors (stationary in a parking lot), the position is not accurate and does not stay fixed(Lat Lon is not stable). Should I install a wheel tick sensor? If so, can I just connect it to W+ and W-, and will the program automatically calibrate (single wheel tick)? Can you recommend a suitable model?
2.	Is it possible to use the SparkFun ZED-F9R in dead reckoning mode indoors with high accuracy, in combination with an RTK base station, the built-in IMU of the F9R, and a wheel tick sensor?

Which dynamic? Automotive?

I can confirm that without wheel tick on car, it is not very precise when driving indoor. It is not so bad inside tunnel at stabilized speed. It is worth in covered parking.

Yes, I am using it with a car in automotive mode.

When connecting a wheel tick encoder to the SparkFun F9R, does the algorithm automatically calculate the position based on the calibration? And in the UBX-ESF menu, will the single wheel tick sensor display as calibrated? Also, when the car stops indoors, will the position continue to shift? Thank you for your answer.

The wheel tick data is used in combination with the other sensor inputs, all of which have different prominant noise properties, ie dither, drift, etc
When the wheels stop ticking it’s probably NOT moving, unless say on a ferry or train.
You also don’t need physical pins, you can push in speed or ticks via software methods.
And, for example, ticks from both rear wheels.
Also setting up the relative geometries of the receiver, antenna, and turning center, etc.
For these things to work effectively you need to integrate them rather than slap-dash the implementation.

I am using the ESP32 and SparkFun F9R. The software method involves receiving the speed data from the SparkFun F9R, along with the wheel size, etc., to calculate the estimated ticks. I then send the calculated value back from the ESP32 to the SparkFun F9R to be used in combination with other sensor data (IMU, GNSS, and estimated ticks). Is that correct?

Thank you for the advice.

The Speed can be sent in SI units
The Ticks are more arbitary units, which you can either define, or the receiver can determine during the fusion process.
Ticks can come from encoders, or motor drive subsystem.