Advanced Search

I've verified the vhdl and c code, and hostmot2 is indeed dealing with
the same protocol.

But at least now you know how to interpret the CRC, because that is not
done in hostmot2.

And I have learned where the batt_fail bit is (not that there is one on
the incremental encoder) They also don't seem to know what the purpose of
those 3 changing bits is. Maybe I'll figure that one out eventually.

Are you using master? If so you might have to update as a fix for such an issue was merged here:
github.com/LinuxCNC/linuxcnc/pull/3516

Yes, that was the problem. Thanks

Yes they also jog w/o probe screen. But then the axis stop when I release the button. Only in probe screen the axis don't stop.

Probably locale setting issues, so set the locale to en_US and UTF-8 and try again.

Hello,

Apparently I found the right place in the code, at least the image quality changes.
Enclosed the pictures I have reached, maybe you can use or expand it in the future.

Thanks to everyone and best regards, Frank

Thank you very much.
Attached are both filters for LinuxCNC, the normal 3 axis and the generated 4th axis noted in the file names inside the zip file, also require adding these two lines to the ini fileorAnd another try at explaining things, badly as usual, the attached 3D image has the blueish-green cut line that is the actual gcode, so the tool should be horizontally positioned to cut the line

No, maybe the wrong firmware? See attached file

This error occurs when we select the automatic G code file at the first startup from the gmoccopy settings.

It looks like it supports incremental jogging, which might be safer:
github.com/verser-git/probe_screen_v2/bl...probe_screen.py#L360

My guess would be that for some reason the button-release events are not calling the button-release routine.

Though it might be nothing to do with probe-screen directly at all. Do the keys you mention also jog in the UI you are using _without_ probe-screen?

It could very well be the same, but I'm not sure. This is for the beta and not the alpha series of Fanuc. Like I said, I could not find the details of the protocol anywhere, but that could also mean I did not look in the right place.

Resolver can have much, much higher resolution, depending on the card used for them and the ADC used.
Also, they never fail, at least i have never seen any failed ones.

Hello,
Is there a solution to this problem?

Got my mouth watering, thanks for sharing!

My existing install is using kernel 6.1.0-30-rt-amd64 (from the 2.9.4 ISO).

I'm going to grab Debian 13 and try to assemble from scratch.

Did you install ethercat from the repository or did you build from source?