Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: dude1 on May 12, 2012, 07:54:49 PM
-
Mach3 going mad, when start up machine needs to change pin1 from active hi to active low then back to active hi for axis to move at set speed. other problem can get machine to jog move with commands in mdi screen but when file loaded only z axis moves x and y go now wear but DTI shows movement on x and y help me
-
Please attach your xml and if there is a specific bit of code that produces it also attach that.
Hood
-
found out what problem was had a conflict with pins it works now, but still have start up problem have to hit verify in mdi screen to get things to move properly any ideas will post xml soon as not at same place as machine
-
Will see what I can find in the xml when you attach it.
Hood
-
attached xml thanks
-
I have tried jogging here and it works fine right from the start.
If that is not what you were meaning by " to get things to move properly" then maybe if you could elaborate a bit I will test further.
If that is what you were meaning then load the standard screenset (1024.set) and see if it still happens, it could be something in the screenset you are using that is the issue.
Hood.
-
what i mean is that at start up if you go to jog machine it goes very slow as in actually 1mm in a minute. to stop this happening i go to mdi screen and hit verify and then it goes the speed i wont when i first put machine together it was not doing it but next day it was its not that much of problem if i can stop it happening it would be good
-
Ok its fine here, start Mach with your profile and jog and it moves at 450mm/min or so which is about right as you have a slow jog of 30% set and your rapids are 1500mm/min.
Try with the standard screen and see.
Hood
-
I tried that and it made no differences what its doing now is if you jog after start up that ok, but if you type a distances to move in the mdi screen its really slow then if you hit verify it come right its something i can live with
-
I have just tried that also, open Mach with your profile, press reset and go to MDI page then MDI a G0X move and it moves correctly as far as I can see.
The other thing that puzzles me is why Verify would be making a difference, what Verify does is move an axis to your home switch and check how far it moves against where the switch was on a previous home move then calculate whether there is a difference.
Only thing I can think of is maybe you have a Brain ior a plugin that is doing something so if you can disable all Brains and Plugins and see if that makes a difference.
Hood
-
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
-
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
-
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
-
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.
-
In General Config, put F150 in your initialization string and see if it's faster.
-
What are you entering in MDI?
Hood
-
something like G0 X200
-
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
-
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.
-
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
-
its a wearied problem
-
Hood,
I just tried Daniel's XML on my development machine running Ver. 062, and a G0 X300 command runs at the speed set by the FRO slider. It most assuredly is not running at the XML set velocity of 1500 (IIRC) units/min. With my standard XML and the 1024 screen, it does not respond to FRO speed. Something is wrong, IMO, with Daniel's XML.
Best to All,
John Champlain
www.picengrave.com
-
The FRO slider will act on this when FRO goes lower than 100% as Rapid is Locked to FRO on General Config.
It does seem that it is doing a G1 move when it should be a G0 though. I had only been looking to see if the initial MDI move was very slow as Daniel had stated and had not looked at motor tuning.
Why the G0 are being treated as G1 moves I am not sure, cant seem to find any reason for that, when I get some time I will make a duplicate xml and see if it happens with it.
Hood
-
i had a play with settings yesterday if I set the initialization string to say f400 g80 it move all axis at f400 if I use the MDI screen first before I load a gcode as I haven't mounted the home swithes yet. if I hit ref all home after setting home location the problem is gone. so what I will do is set initialization string to f400 g80 for now, when I have home swithes mounted I will just hit ref all home then if I type a move into the MDI screen there will be no problem. this was what I did with old machine that's way I only found this problem now.