Mesa modbus and pktUart

I'll try setting the update rate to .1 in the hal file
(I've set it later to .1 without any issue)

Setting  the update rate to .1 in the hal file works fine here.

 ( Of course it only  updates the outputs every 10 seconds so you need to wait
from 0 to 10 seconds after you update an output for the physical output to get updated )

loadrt mb25ioc32 ports=hm2_[HOSTMOT2](BOARD).0.pktuart.0
addf mb25ioc32.00 servo-thread
setp mb25ioc32.00.baudrate 9600
#setp mb25ioc32.00.baudrate 115200
setp mb25ioc32.00.parity 0
setp mb25ioc32.00.address 1
setp mb25ioc32.00.update-hz 0.1
#setp mb25ioc32.00.setbaud 7 # 7 is 115200



 

A quick way to verify that you have fixed the divide by 0 issue
is to set the update rate to 0 in say halshow, and the set it back to say 1
If communication continues at 1 Hz, then the issue has been fixed.

(I say this because at least in a RIP installation the
mesa_modbus.c.tmpl file used is not the one in the
LinuxCNC sources)

Yes works but it is practically unusable with 10sec intervals
also the problem of random data to encoder input it is unknown if resolves
completely or just happens in these long intervals and it is difficult to detect..
With update-hz set to 0.05 does not work.

Yes, I would test at say a 100 Hz update rate.

I was just checking the 0.1 Hz update rate, as you said
it did not work, but it seems OK.

So if you can change the update rate from 0 to some positive number
while running and it keeps working, that indicates that at least one
divide by zero issue has been fixed.

The bad data error you have may be unrelated but the divide by zero fix
seems to have solved the very similar error finnengineering had with the stepgens


 

try this to mesa_modbus.c.tmpl i think works?

That does not set the rate though, what I did for testing was:

                if (inst->hal->rate > .001) {
                    timer = 1e9 / inst->hal->rate;
                }  else {
                    timer = 1e9 / 1000;  # 1 ms
                }      
 
 

My observation is the fastest ioc32 data rate led blicks(more speed)
the numbers of encoder read go more crazy.

Are you setup to build LinuxCNC from source?

I have a patch from a LinuxCNC developer that may fix this issue.

2.9.4 but can apply patch to 2.9.4 source.