Hello Guest it is December 13, 2019, 10:36:11 PM

Author Topic: help  (Read 7387 times)

0 Members and 1 Guest are viewing this topic.

Re: help
« Reply #10 on: May 15, 2012, 05:41:18 AM »
If you are inputting a G01 move you must set a feed rate. At startup there is no prior feedrate for the machine to use. If you hit veryify I think that it will leave a feed rate = to the homing speed in the system. Try a G01 f20 x 5 or something similar and see if that works.

Mike
We never have the time or money to do it right the first time, but we somehow manage to do it twice and then spend the money to get it right.

Offline dude1

*
  •  1,253 1,253
    • View Profile
Re: help
« Reply #11 on: May 15, 2012, 09:40:47 PM »
tried all of that same problem, start up, hit reset same problem axis moving very slow. i can push stop or verify to clear problem once hit stop or verify z goes up 20 then down 20 then all good.
have put xml on to another computer same problem must be a ghost in the xml

Offline Hood

*
  •  25,856 25,856
  • Carnoustie, Scotland
    • View Profile
Re: help
« Reply #12 on: May 16, 2012, 03:22:29 AM »
It does not happen here with your xml so it is hard to see how it is an issue with the xml, assuming that is you attached the correct xml?
As I said earlier I loaded the standard screenset as I dont have that one you are using. So the only things I can think that would cause your issue are the screenset, a plugin or a brain.
There is no way the Z axis should move at all just by pressing the Stop button, that suggests there is VB in that button on the screenset you are using or you have a brain or macropump doing something when that is seen.
Hood

Offline dude1

*
  •  1,253 1,253
    • View Profile
Re: help
« Reply #13 on: May 18, 2012, 07:18:01 PM »
i have tried this xml on 3 different computers with same result when you start Mach hit reset then go to MDI screen and type in a move its still slow as, but you can jog with key board or fly out screen that run at correct speed and if you load a g code that will work ok its just when you type in a move in the MDI screen after you start up this problem exists, if you hit stop or verify before inputting move its gone.

Offline ger21

*
  • *
  •  6,291 6,291
    • View Profile
    • The CNC Woodworker
Re: help
« Reply #14 on: May 18, 2012, 08:26:42 PM »
In General Config, put F150 in your initialization string and see if it's faster.
Gerry

2010 Screenset
http://www.thecncwoodworker.com/2010.html

JointCAM Dovetail and Box Joint software
http://www.g-forcecnc.com/jointcam.html

Offline Hood

*
  •  25,856 25,856
  • Carnoustie, Scotland
    • View Profile
Re: help
« Reply #15 on: May 19, 2012, 04:24:29 AM »
What are you entering in MDI?
Hood

Offline dude1

*
  •  1,253 1,253
    • View Profile
Re: help
« Reply #16 on: May 19, 2012, 05:43:44 PM »
something like G0 X200

Offline Hood

*
  •  25,856 25,856
  • Carnoustie, Scotland
    • View Profile
Re: help
« Reply #17 on: May 20, 2012, 03:16:58 AM »
Well I have tried many times with your xml, even installed a couple of different versions of Mach and also downloaded that screenset and still it behaved.
Hood

Offline dude1

*
  •  1,253 1,253
    • View Profile
Re: help
« Reply #18 on: May 20, 2012, 05:12:36 PM »
the problem is to do with the initialization string if I type say G0 f300 x300 into the mdi screen its ok but if I type G0 X300 its not ok its some thing I can live with, thanks for all of your help.

Offline Hood

*
  •  25,856 25,856
  • Carnoustie, Scotland
    • View Profile
Re: help
« Reply #19 on: May 20, 2012, 05:23:34 PM »
A G0 is a rapid move and it should not matter what F word is in the initialisation string so I am perplexed why this would work. I could understand if you were commanding a G1 move but not a G0 as you are.
It would be good if someone else would try your xml and see if they have the problem, so hopefully someone will.
Hood