(Solved) Races through first cycle upon first start up. Fine afterwards.

More
1 year 1 month ago #334452 by unknown
But the the theories above do not take into account it is fine afterwards, very intriguing.

Please Log in or Create an account to join the conversation.

More
1 year 1 month ago - 1 year 1 month ago #334454 by TheTinkeringMechanic1
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.
Last edit: 1 year 1 month ago by TheTinkeringMechanic1.

Please Log in or Create an account to join the conversation.

More
1 year 1 month ago #334456 by tommylight
What GUI? Assuming you are not using Axis as it is by default in Auto mode.
Does the machine use a tool changer?
Does it use any custom components?
Does it have any added hal wizardry?
-
I recall a while back in certain states/conditions it would run through all the tools in the gcode, but it was probably fixed since for a long time it was not mentioned here.

Please Log in or Create an account to join the conversation.

More
1 year 1 month ago - 1 year 1 month ago #334462 by TheTinkeringMechanic1
Last edit: 1 year 1 month ago by TheTinkeringMechanic1.
The following user(s) said Thank You: unknown

Please Log in or Create an account to join the conversation.

More
1 year 1 month ago #334463 by unknown
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.

Please Log in or Create an account to join the conversation.

More
1 year 1 month ago #334465 by unknown
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.

Please Log in or Create an account to join the conversation.

Time to create page: 0.211 seconds
Powered by Kunena Forum