Mesa modbus and pktUart

Seems to be related also to this
forum.linuxcnc.org/27-driver-boards/5432...v2d-firmware?start=0

If after startup set update-hz to 0.0001 or something non zero problem seem to stops..
Is this division by zero bug?

Yes, this is a long known bug, never set the update rate to 0.

This is the reason for crazy data readings on encoders ?
I make now a config that encoder.count and encoder.velocity goes crazy to see if it stops by setting update-hz to non zero

Yes problem of noise in encoders resolves by non zero value to update-hz
verified by different configs that produced random data to different encoders.
All random data stop to encoders if update-hz is non zero but stop and modbus device to work.
 

If i set non zero update-hz problem of crazy data reading on encoders stop
but also stops working modbus device so no solution here..

If you ever set the update rate to 0, you can never change it again or the driver will hang (this is a known bug)

I start with 0.1 in hal file setting and does not work
if change it to 0 from halshow starts working but encoder reads crazy data.
Also if change functions order in vhdl pin file changes affected encoder number and pins.
Seems to be bug in vhdl because the functions order affects the encoder that is affected
in one config affected encoder.00.input-a and b
and in other config encoder.04.velocity and count.
Also when modbus device working the encoder reads crazy data when not working
by removing power supply/unwiring or stop it by setting update-hz to non zero
the same time stops the problem to encoder.
Seems like electric noise problem internaly in fpga
The same module works ok with mb2hal so it is not the module