Probe basic absolute encoders reset position to zero

Hey guys,

I switched to probe basic due to the user friendly interface, previously using dragon GUI.
To avoid losing my actual config I performed a fresh installation on a new SD card ( using Raspi5 )

I'm heading to this weird behavior:

move the machine to X Y Z position -> restart  Probe basic (no servo power off) keeps the position info
move the machine to X Y Z position -> restart  Probe basic (servo power off) X Y Z are back to zero

I guess the cause could be:

1) Probe basic
2) The fresh install is missing something

Raspi5 flashed 2.9.2
Upgraded to LCNC 2.9.4
Installed Ethercat
Installed PB
Merged my actual config with PB

BONUS QUESTIONS : qtdragon allowed me to manual jog outside machine software limits (with home all in red) is this possible with PB? How can I force absolute encoders position to zero? I don't have limit switches on the machine

Thanks in advance for the help

is your new config correctly setup for absolute encoders? the dro's in probe basic are just displaying the axis data from linuxcnc so if it worked previously in dragon, it should also work the same in probe basic. it sounds like the absolute encoders are not correctly updating linuxcnc at startup. so i would start by double checking your ini settings for homing section maybe?

Thanks for the fast reply, you are right, I imported dragon on the new install to double check and indeed also resets the position to zero. Dragon config is copy/pasted.. so I guess is due to the new install or LCNC 2.9.4? How are stored the encoder positions?

Maybe didn't notice due to edit I had BONUS QUESTIONS : qtdragon allowed me to manual jog outside machine software limits (with home all in red) is this possible with PB? How can I force absolute encoders position to zero? I don't have limit switches on the machine

if using multiturn absolute servo encoders there isn't any homing, the encoders use batteries to maintain their position and on startup of linuxcnc those encoder positions are written to linuxcnc. this is all setup inside the config files, check the docs for using absolute encoders for the correct ini settings. they are unique and special. with this once started and the encoder positions update the dro's the machine is set in the homed state. linuxcnc does not store the previous positions on shut down as they could be useless on startup even for a non absolute encoder machine which may move slightly when powered off or could be moved while powered off giving an incorrect assumed position to actual machine position.

in the sidebar tab under the WCS tab is a button named limits override but its use is somewhat finicky from my experience. it is just commanding the same functionality available via linuxcnc so the docs will have all of the use case information for how/when to use it.

linuxcnc.org/docs/stable/html/config/ini...ome_absolute_encoder

Thank you, the issue was inside servo parameters, somehow all three have been swapped to incremental.

glad you got it resolved!