Advanced Search

Probably would need also changing the - sign for home_search_velocity and maybe home_latch_velocity for that axis/joint.

Helpful? I'm fairly certain you believe that too.
If there's confusion about something, then ask a question. No questions were asked. It's really easy too. "What do you mean by MEM? I'm not familiar with that term." I would have been happy to answer to clear up any confusion and learn whatever you folks call it.

What did I get in return? Some self-conceited person you consider an "esteemed colleague" that thought that I was too dumb to not know what operating system I was using...
Bad news, I match energy. If you don't like what you put out thrown back at you? Then don't be that way.

And here you are tossing out childish insults...

I'll figure it out myself.

Oh this old gem, the solution is to remove or purge the offending raspberry pi package. Its been mentioned many many times throughout the forum, the exact commands can be found with a quick search.

But the the theories above do not take into account it is fine afterwards, very intriguing.

It's quite possible it is a gcode issue, mayhaps the cam is in metric units and the machine is setup in imperial units and no g21 was given in the preamble.

Another possibility is whoever setup the machine gave the overrides quite a large postivie range and the feed override is set at max.

And just for clarity Linuxcnc loads the gcode from the filesystem, ie from disk, not from "Internal memory", for those that are familiar with computers there is a distinction between memory (being ram/rom) and disk. As many things getting terms incorrect can cause confusion.
Look for all we know you could be using a custom interface with a MEM button implemented to make the machine more familiar. If that is the case it would be no wonder there has been confusion. Reading through the documentation for the various interfaces supplied with Linuxcnc there is no mention of a MEM button. I mention this as the frustration of the OP seems to be the questioning of a MEM button being implemented in Linuxcnc to retrieve gcode from "internal memory".

I have just realised that my thingy requires you to type in the values. That's not as ergonomic as one might hope. Give me a few minutes.
Files updated
 

@scotta Following chatgpt it could work by only do ARR/CCR-updates via DMA-burst and the rest with timers. Does that make sense?

This captured my interest, so I made one.
Drop the two attached files into the same folder as your INI file.
Then, in the [DISPLAY] section of the INI file add:Be careful with the buttons, they are not tested on real hardware.Set Zero - should set the coordinate system zero to be the centre of the probed circle (considers G54 etc but not G92 at the moment)GotoZero does a Z-hop of (currently) 20mm then G0 X0 Y0.The diameter measured has 6mm subtracted from it to allow for probe diameter.The Z-hop and probe diameter are constants defined near the top of the python file. Feel free to edit to suit.This uses GladeVCP. As has been suggested elsewhere, there are other VCP frameworks, but Glade works well enough with Axis.