Races through first cycle upon first start up. Fine afterwards.

Just read your post prior to mine.

Your still to provide the information I ask for to diagnose your situation.

See sometimes as issue can arise that none have seen before, there was a recent one regarding MDI pins. Until one user had used a particular setup it had never occurred. Fortunately the user supplied the information particular to their usage and the code was quickly fixed and merged into the code base.
If that user had of reacted as you did nothing would have been resolved.
Now old Tommy has a great deal of experience deploying Linuxcnc based equipment as a commercial endeavour, so he is no Johnny come lately. PCW is the Mesa presence on the forum, very helpful, very knowledgeable and quick to respond to users requests for custom firmware. Very respected, will even endeavour to help when the mesa firmware is being deployed on non Mesa Spartan 6 platforms. Also has been generous enough to supply schematics to his products when asked.
So I would my two esteemed colleagues conduct themselves in a manner that has earned them the utmost of respect.
So I think it would be a good time for you the reassess your comments, look through the forum and read the replies they have given other users. Then it would be an idea to offer an apology cool down and supply the information requested so this issue can be resolved .

So what version of Linuxcnc are you using, what is the underlying OS, are you able to attach the config files ? Also what hardware is being used to control the machine, is it parallel port based, Mesa based or some other hardware based step direction system ?
Diagnosis requires the collection of information and that is the reason for request.

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".

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

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.

youtube.com/

Once again can you please offer up the version of Linuxcnc,the underlying OS and whether you are using a parallel port based system with software step generation or you are using a hardware based solution, once again any config files will be helpful.

Call me what you want I really don't mind, as you don't know me personally it hasn't affect .

In my dealings with PCW I have found him to be very generous with his time, knowledge and the schematics related to his products. Like I said read the forums and pay attention to the advice, help and response to custom FPGA bitfiles for his line of Mesa products, you will find everything I said to be truthful representation of the facts.
If you require help we're here to help, if you want to argue I gladly indulge that as well. If you bear false witness regarding members of this forum I will refute any statements that do not truthfully represent their character.

In saying all that I feel this thread would be better off deleted as it is proving to be a tit for tat affair.

Mayhaps then you could start a new thread and we can forget about the whole MEM thing which isn't a "Linuxcnc concept" as per the standard codebase. If this was a feature the various GUI would have that button, Hal pins would be exposed for that feature and it would be documented.
The closet feature would be the "reload button" but that rereads the file from the filesystem, but will also use the the original filename with any changes that may have been made. Which when combined from the "run from here" feature is a useful way to add extra code to a file without having a complete rerun.

Once again, the I formation requested regarding your system will be most helpful.

I would like to request if this information isn't supplied that either the thread is locked or deleted.

Ok thank you that is a bit more more informative, if somewhat weird. As I suspected the whole MEM debacle is someone's labeling, maybe to make the machine more familiar.

Somewhere along the way some one is going to ask for the gcode file, and once again the config files and the rest relating to your machine so they may have a chance of the simulating the issue.

If there is any proprietary IP involved you may have to make an agreement with one of the devs to sort this issue out. I'm just putting this out there as your particular site situation is unknown.

Just a word of warning, if the issue relates to some sort of issue with any Mesa hardware you'll be dealing with the company run by the person you referred to as conceited. But what you need to consider is that over the years there has been dealings with people that have landed at this forum requesting cnc help not related to the Linuxcnc ecosystem, also those that will argue that Linuxcnc should support this hardware or that, usually related to some form of USB based controller that for various reason does not work within realtime, I know unrelated to your issue.

Now time to let bygones be bygones and other such cliches and sort this out. I can understand if this is causing some frustration but sometimes it can go both ways. Like multiple requests for a user to give information regarding their system, ask your sales or engineering team how this can be with some customers. But like I said if there is any proprietary IP involved some agreement with one of the devs maybe the way to go, so as any discussion can take place within a non-public way.

Taking into consideration according to that person You consider an esteemed colleague and I called conceited, I'm too dumb to even know what operating system I'm working with... I've had enough of the elitist clique here... Thank each other all you like.
I think I'll take my chances and figure it out on my own. I didn't come here because I couldn't, I came here because (I thought) asking people who are more familiar with something than I am can save time.
My mistake.

In the end if I can't figure it out, I'll just deal with it until this job is done and I have time to gut this of Linux and install a complete FANUC oi-TB CNC unit I have. I'm also fairly certain I have everything I need to install this other Fagor unit I have access to.
Options are a plenty...