Question: P value with MESA Setup without encoders

Thank you. Will look into it

Currently I can't get LinuxCNC to start yet, with the communication delayed by 1.5ms. If I set the delay when LinuxCNC already started, the machine runs and works (so far tested for 1h).

One brief question. The influential parameters after reading hm2_eth manual and hostmot2 manual are the following?

HAL:

• hm2_7i76e.0.packet-read-timeout  xx % or XXX.XXX ns (dependent on Servo Period)
• hm2_7i76e.0.watchdog.timeout_ns X.XXX.XXX ns

INI:

• SERVO_PERIOD = X.XXX.XXX ns

Or do other adjusting factors exist?

Thank you in advance, always appreciate your help!

 

It may be that there are timeouts in the card initialization section
of the driver that would need to be lengthened to solve this issue

Yes, should be a problem of the initialization.
Those are not adaptable by the hm2_eth or hostmot2, if I get it right.

So the first idea with the code adjustment of the firmware (probably hm2_eth.c) could be the way to go?

Yes, the timeouts would be in the driver code

Ok Thank you.

Are there instructions or a tutorial regarding the creation of flashable bit-files.
I could not find sth in the git.

My plan would be to adapt the C-Code (that causes the timeouts), create a new bit file with all information needed for the Mesa 7i76E and flash it
... And hopefully do not brick the Mesa card

Maybe I will create a new thread.
By now this thread is rather off-topic

The timeout code is in hm2_eth the driver (part of LinuxCNC)
there are no timeouts in the 7I76E firmware (other than the
settable watchdog timeout)

Ok.
Now I got it.
Had a understanding issue what is part of Mesa code and Driver code

Thanks