Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: soarkraut on January 22, 2011, 10:16:16 AM
-
hey gang
Need some help.........
I have this program, an airfoil outline with some spar cut-outs.
It runs very smooth along the arc until I use the "run from here" option.
After that.........the arc is cut in jerky small steps. Nothing I can do changes this. Even ending out of Mach3 and reloading the G code , nothing helps. Its jerky steps from then on.
Someone help me here!!!
Pete in Lower/Slower Delaware
-
Can you attach your xml please.
Hood
-
ok............I new, I suppose you mean my G code file.
here ya go......
-
Why are you using run from here? Are you having to stop the program for some reason and restart it in the middle of a run?
-
Sometimes I get a similar problem.
Mach drops out of CV (G64) and into exact stop.
Make sure you have G64 at the start of your gcode to tell mach you want to run in Constant Velocity.
Might be totally unrelated but maybe worth a go ?
ATB
Derek
-
ok.........
Some of the "pros" now tell me to NOT run from the USB stick.
Random ********* will happen............so they say.
All good advise................thanks for answering
-
The problem is the drill cycles SOME drop OUT of CV to do the cycle and does not reinstate it when done, Especially when using the RFH. I notice that you dont have a preamble to set all the gobal values (;-) such as G64,etc.
Also a good idea to set them after any canned cycle.
(;-) TP
-
Ah OK running from network or USB is not a good idea, if you had said that it would have been the first response from most here ;) It is always best to have the file you are running on the hard drive of the computer you are using.
Regards the xml, it is the configuration settings you have done in Mach and there will be one for each profile on the computer and they will have the name of these profiles.
Hood
-
I know that G83 for sure changes to G61.
-
ok........pretty scary stuff for a Newbie.
I am retired now........used to have a young "whipper snapper" doing all these details for me :P
Its a lonely world now............have to look at the end of my own arm for a hand.
Thanks to all who answered my SOS ::)
Pete in Lower/Slower Delaware
-
IF you need to isolate some of your code like you do for drilling the holes then consider using block delete. That way if you don't require it turn on block delete and mach will bypass that code.
As to the USB (;-) it depends on the computer. I have one that runs the code from the usb STICK everyday without problems. MACH is memory mapped . that means it loads the entire Gcode program into SYS memory so it NEVER has to reread anything from the drive. SO it should not matter to mach where it came from originally.
Just a thought, (;-) TP
-
When the guy that wrote Mach said
I do read some reports of people using usb sticks for their program.. very
bad idea as Ive said many times. A disk works much less intrusively and requires
far fewer interrupts to be processed than a usb stick. ( USB drivers can vary
alot too between systems as well.).
I took it on board. I used to run on the network or USB and never had an issue but after I saw Art say that the first time, maybe 5yrs ago, I have always run from the HDD ever since.
Hood
-
I don't disagree with the HD as the BEST approach. But I dought the usb had anything to do with his original problem with RFH (;-)
MAYBE one of the VB gurus can come up with a Button utility to load a program from the USB stcik into the Gcode directory and then autoload it into mach from the HD. All with the push of a button
Just a thought, (;-) TP
(;-) TP