Another realtime delay question - Mesa card

That's quite low acceleration (if in mm/s^2) = ~0.08g

That makes sense. I set up the speed by feel with the machine. It's plenty fast enough, like much faster than when it used to be a manual machine. But it's a dovetail mill, so the work envelop is rather small, say compared to a plasma cutter with long distances or a wood router which would need to be faster.

@rodw: Thank you for the link, I will try it later because I have a couple of time critical jobs to finish right now and don't want to risk to have the machine down for a while. I'll keep you updated!

I haven't had any more realtime errors since raising the servo thread to 1800000.

Should I still seek to upgrade my HW or install rodw's kernel?


Thanks a lot everyone, your help is very precious.

 

Unless you have an issue with motion, you should be fine.
The lower thread rate has no effect on maximum speed.

If you have very high acceleration the acceleration/
decceleration ramps will have fewer velocity steps at a
longer servo thread period, eventually a potential cause
of stalling.
 

I think I have experienced this a couple of time while jogging two mpgs at the same time. They go through a HAL filter, so I guess that would give too many instructions at once if spun fast?

That is totally none critical, though. can just not jog so fast.

Its unlikely that a filter component would take significant time
Its probably still communication delays on the PC.

To check, if you get an error run this halcmd in a terminal window:

halcmd show param *.tmax

This will show the maximum times used by all hal functions (in CPU clocks on x86 and ns on ARM)