Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: ssutton on March 11, 2011, 07:14:48 PM
-
I have a new install of Mach3 Demo to set up my machine. I have configured my travel limits to all come in on 1 port pin because of limited inputs from my breakout board. This works fine, for a few minutes. Here is the situation, when I first start Mach and begin to jog my machine if I hit a travel limit the machine stops and tell me in Mach that a travel limit has been tripped. I reset Mach and all is well. However, after jogging a few minutes the travel limits no longer stop Mach from operating. When I go into diagnostics I can see that the travel limits are in fact coming on when I press them but Mach continues to run. This happens every time I start Mach after about 5 minutes of machine motion.
Anybody know what could cause this?
Thanks,
Scott
-
So, if you're in the diagnostics screen, and your jogging and hit the switch, the LED will come on , but the machine won't stop?
-
Yes, I can be jogging and looking at the diagnostics and trip one of my limits and it will illuminate in Mach. I have all six limits wired to one pin input. In diagnostics, all six limits will come on when I trip a limit but Mach ignores it and just keep on jogging. I have re-started Mach and restarted my computer several times.
-
Hi Scott,
You might try reinstalling Mach.
The lockdown version.
Russ
-
If you attach your xml maybe the problem can be found.
Hood
-
I have additional information about my problem. When I first start up mach and my machine I can jog via the keyboard and trip a limit and the machine will stop instantly and require that I reset it. It will then reset as it should and continue to run and continue to stop when I trip a limit. BUT, if I click Ref All Home then mach will not stop when a limit is pressed. It will home normally, but after the home is complete it will not stop if I jog via the keyboard and trip a limit. I can open diagnostics and see that the limits are tripping but mach ignores them after a home routine. I am running the stable release of Mach demo. The only unusual setup that I have is that all my limits are wired normally open and all of them come into 1 pin on my G540 drive.
I have attached my XML file.
My computer specs;
Windows XP pro service pack 2
pentium processor 2.79 GHz
640 MB of ram
I am running no antivirus, this is a new clean install of windows and this machine is not connected to the web.
Thanks for any insight, I am really stuck here.
-Scott
-
Do you have 9 switches?
-
Sounds to me like your homing is not completing and Mach is still in the homing state, ie ignoring limits.
Will go see if I can find a prob in your xml.
Hood
-
I have 6 limits, 2 per axis all wired together normally open, any limit will produce an input on pin 10
-
I also have 3 home sensors that are NPN type all wired together that land on 1 input to the G540. These produce an input on pin 11. My machine homes all three axis and then stops, so I think that it homes successfully.
Thanks to you guys for taking time out for me.
-Scott
-
Hi Scott, you have A slaved to X and A set as Angular.
Is this intentional ?
My guess, it's hung up in the homing routine like Hood mentioned as A is never getting referenced.
Home slave with masrer is also checked.
Un-slaved A and it appears to work normally now in sim.
Russ
-
Sorry had someone come in. Yes I think that is the problem.
Hood
-
OK,
Sounds like you guys are on to something here. Please help me set up my machine correctly.
I have A slaved to X because I have 2 motors on my X axis. However, I currently have only 1 home sensor on my X axis. What I will do (I have ordered the parts) when I get the parts is have 2 home sensors on 2 separate inputs so that I can "square" my gantry with a homing routine.
But, currently I have only 1 home sensor for the X. I am confused about slaving, when I first set up my machine I slaved A to X and the machine would jog via the keyboard normally, BUT, when I clicked ref all home only 1 of the X motors would run and the gantry would try to twist until it stalled. I posted a question about this on another CNC forum and was told to check "Home slave with master axis", this seemed to fix my problem because now both motors run when I home. But it has caused this issue.
So what am I to configure to get it to run correctly with the 1 X axis sensor that I have now?
What am I to configure when I get the second home sensor and i want to square my gantry with it?
Thanks guys,
Scott
-
Yes because you have the A home switch enabled, disable it and all should be fine.
Hood
-
Uncheck A as Angular
disable the HOME swit for A in Ports and pins/input signals
check Home slave with master
when you get the second sensor, install and enable it in config
-
Wow! Thanks, I am a total newbie and just could not figure this out. That solved my issue and shed light about the way that Mach "thinks". That seems to be the largest problem of learning new software is getting your head wrapped around the logic.
Thanks again to all who shared your time with me.
-Scott
-
:)
The learning is never ending.
Glad we were able to help.
:)