Debugging sporadic read errors from Mesa 7i95

Take PCW's advice, edit the ini file in your config directory, locate the servo period and change it from 1000000 (1 million) to 2000000 (2 million), save and start LinuxCNC again.

tommylight wrote: Take PCW's advice, edit the ini file in your config directory, locate the servo period and change it from 1000000 (1 million) to 2000000 (2 million), save and start LinuxCNC again.

I think you will have to change the P 1000 to 500 as well

I increased servo thread period to 2 000 000. It this doesn't help, I'll experiment with power supplies. One change at a time.

Clive S wrote: I think you will have to change the P 1000 to 500 as well

What is P?

P value for each joint/axis in the same ini file further down.

piranha32 wrote:

Clive S wrote: I think you will have to change the P 1000 to 500 as well

What is P?

It is a parameter in the ini file.

tommylight wrote: P value for each joint/axis in the same ini file further down.

Ah, I see. I'm currently running sim environment (axis_mm) to play with simple I/O on the card, and it does not even specify PID parameters. Should I add it?
To be clear, I get the timeouts in the sim environment, and in configuration driving physical steppers.

What PC ?

The OP is using an Atomic Pi. It's a rebranded Atom based SBC that was destined for a household robot. It was marketed as an x86 challenger to the RPi. Bought by a lot of the "maker types". The sub reddit is kinda funny, so many bought them without reading the mass of data sheets and info the reseller has/had of their site. Biggest problem was people not being ale to read the instructions on how to power it. At the time it was USD $35 so kinda cheap for a x86 SBC. If you had a bit of common sense and were willing to read the docs it was easy to get to work. If you wanted a "turn key" x86 SBC it wasn't the thing you should have bought.
Mine is sitting in the corner ATM....work bench is kinda chocka block full, need to finish a few projects to make room.
www.digital-loggers.com/api_faqs.html