Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: CharliePatten on February 17, 2010, 10:28:38 AM
-
Has anyone had any experience using this? I have set up a perimeter guard with interlock on Input #1 and checked the "program safety" block under general config. Every time I open the interlock switch, the machine does not stop immediately and I also loose complete position from my workpiece coordinate, even though it shows that my work coordinates are correct. Would I be better off wiring this interlock switch in series with my E-Stop button?
-
The Programme safety lockout is meant so that code cant be run if a guard (or whatever you have connected) is open. It is not meant for stopping in a controlled manner if you open a guard whilst code is running, if you do that it will stop the code but as you have found it will lose your position and you will need to re-home.
One option as you say is to use the guard switch as an E-Stop, depends how you have the E-Stop string wired. Another option would be to have some form of lock (solenoid etc) so that when code is running you cant open the guard until the motion has stopped.
Hood
-
I don't know how it is supposed to function, but if you have code running, then activate output 1 Mach stops like you say but then when you deactivate 1, Mach resumes.
Probably not a good idea to have it this way ?
Should at least require a restart button press.
Also, If no code is running, and 1 is activated then hit Cycle Start nothing will happen....till you deactivate IN1 then it starts automatically.
I've never seen any lockout work this way. They ALWAYS require a reset and restart.
The function maybe should be:
If Mach is running, it functions as an EStop.
If not running, it inhibits RUN and doesn't allow RUN to latch the way it does and requires a restart once IN1 is not active.
Just seems safer.
If you Feed Hold, then activate IN1 to disable the running, then hit START it will come off of Feed Hold then resume when the guard is closed and IN1 deactivates. Stuff shouldnt start, or be able to with the closure of a door or gate.
Russ
-
Thanks for the input Russ. I agree with you completely. I think if I wire the gate interlock switch in series with the e-stop button that I will accomplish stopping all motion if the door interlock is opened. The operator will just have to do a homing operation before he starts up again if the door is inadvertently opened.
-
Russ, yes I agree as well, I dont use it on the mill but still do on the lathe. However what I use it for on the lathe is to alert Mach that a drive has faulted but I also have other outputs from my drives that will stop all others and also will E-Stop. So long and short I dont use it the way it is supposed to be used so have never seen the problems with it that you have mentioned.
Hood
-
Hood,
How do have the Lockout function configured to alert Mach of a drive fault ?
Is there an led associated with it ?
?
Russ
-
Now you are asking LOL, it was a few years ago now. I think it is just input like normal (input 1) which will stop the code if a drive faults, but also I have outputs from the drives that will drop out the other drives and if I remember they will also E-Stop Mach but will have to check as I never get a servo fault, will have to pull an encoder to see what happens ;D
Hood
-
Ah..OK.
So you have multiple funtions for IN 1 ?
Thought maybe if SAFETY was checked, it was dedicated to that alone and would be ignored elsewhere.
Russ
Dont go pulling nothin apart, you might not get it back right. :) just curious.
-
I will have a look tomorrow, if I remember ;)
Hood
-
I'm having a problem with the program safety lockout
when checked everything works great
the problem I am having it that if I shut down Mach3 its not persistent.
meaning every time I call up Mach3 I have to recheck the lockout
it was working but I'm not sure what I did to stop this from being persistent any Ideas?
-
Can you attach your xml and I will take a look and see if I can figure out whats wrong.
Hood
-
here it is
and tx in advance,
Sean M
-
Dont see anything wrong, only thing I see is m300 in init, what does that do?
Could your xml be set as read only?
Hood
-
I'll check M300 sets up my PLC basically only turns on an output to tell my PLC that Mach3 is running.
M300
'Enable plc
'Turn On Output 5
ActivateSignal(Output5)
-
xml is not set to read only I also manually saved the config and still ok as long as I don't shut down.
but as soon as I shut down and reload safety lockout is gone.
-
just a side note my sister lives in butterstone outside perth dunce just saw your flag lmao
-
Used to live and work in Perth and still go there every now and then to do work for the Harbour, in fact was there last Sunday fault finding on their tide gauge. Butterstone is a fair way out of Perth though, seem to remember it being near Blairgowrie.
I have started and shut down 20 or more times with your xml and always the box stays ticked so not sure what could be causing your problems. Can you try with the standard screenset and see if there is any change, also what version of Mach are you running and I will see if I can load that and test.
Hood
-
do you know where I can download the unedited final version of Mach# screen set only?
tx sean
tried looking for it still getting used to the forum
-
Have attached it but have renamed from 1024.set to Standard1024.set as 1024.set has more than likely been attached before and the forum will only accept a file name once..
You can either rename or keep it as it wont matter either way.
Hood
-
thanks Version R3.042.029 will try the new screen set
-
Ok if you have no joy I will try and see what happens with that version when I get home from the workshop tonight.
Hood
-
no that didn't fix the problem so its not the screen and not the xml and I'm not calling macropump.
I am using a licensed copy of Mach3 I deleted M300 from boot up just in case
-
what if i try just wiping Mach3 and reinstalling it?
how do I copy the license and reinstall it?
-
First I would try just installing Mach over the top of itself.
The files you want to save are your xml, any custom macros any custom screensets and associated bitmaps and of course you licence which is called Mach1Lic.dat and is in the main Mach3 folder. Also tooltable and offsets are stored in the macro folder of the profile you use so best just saving the whole macro folder.
Installing Mach over itself should not need replacing any files but always best to have them backed up just in case ;)
Hood
-
well its close when you consider I moved over to Cocoa beach, Florida from newport south wales about 10 years ago lol next time I come visit I'll have to make a point to come down your way and buy you a couple of pints lol
-
files backed up will try over writing thanks I'll downlod the final version of Mach3 and use that Mach3 R3.042.040
-
Ha ha as long as its not pints of water, had enough of that the last day, see pic of an idiot in his companies van ;D
-
lol that didn't end well
-
so what do You do Hood
appart from help out newbies
-
over ridden using Version R3.042.040 no effect even when using the stands Mill xml still wont save?
-
going to restart my computer incase
-
I mainly repair/refit fishing boats.
My workshop is a few hundred yards up the pier from that pic.
That is weird indeed, try making a new profile with default values and see if it still cant be enabled properly.
Hood
-
because of this issue which I thought was working I have destroyed 3 motors lol every time my aux motor hits a knote or a shake in the wood and gets stuck I tear the motor off of its mountings :-(
-
about ready to transmodify my computer into a paperweight via a 5lbs lump hammer
-
Have you tried the new profile to see if it still doesnt stick?
Also curious how you are using the lockout as cant figure out how it would save motors when hitting knots/shakes.
Hood
-
I have a 4 axis machine standard 3 axis wood router with and axillary to position a drill motor for end work I surface machine a profile then do end work with a forester bit .
The aux axis is used only to position the aux machine center and a PLC contols air cylinders to drill a set pattern
The the unit sometimes gets bunged up
The whole aux process takes about 7 secs during this process I have an input going to Input#1 which halts all motion from the controller and I put a dwell of 20 secs into the program if at the end of the 20 secs the drill isn't retracted the system should sit there and wait till it is.
unfortunately sometimes the forester bite can get snaged and can get stuck. and when this happens and the unit lockout isn't working bang there goes an other motor
-
I'll send you a link to my machine running
-
http://www.youtube.com/watch?v=eE5zOs7zCBg&feature=player_embedded#!
-
Ah right see where your coming from now, looks like a nice machine :)
Are you using Modbus for the PLC? If so can you as a test disable the Modbus and see if the Optional Stop will stick.
Hood
-
Thanks hood,
no I kept it simple and I'm using 5 discrete IO, (out1-EN/reset, out2-start, In1-Running, In2-Done & in3-Error)
never could tie the done bit in right still learning the Brains and macropump.
yep spent some time changing our motion systems over to Mach3 and was hoping i didn't make a mistake trying to cut costs lol
I think I have it fixed well working lol
after talking to you I did a fresh install on an other machine. inc profile xml bitmaps macros etc.etc....
Everything is now working think maybe Mach3 might have got corrupted?
any way if you ever need help with PLC, Vba, Java internet remote servicing , Screen design electrical mechanical systems just let me know.
whilst I was looking for a way to check the xml better came accross this thopught you might be interested.
http://www.machsupport.com/forum/index.php/topic,9561.msg58698/topicseen.html#msg58698
-
plus I owe you that pint ( not water) - wasn't thinking it could be the install
saved me some time
-
Ha ha yes have used Jasons reader since its beta days :)
Good to hear its working now, not sure if its a corrupt Mach as the install over the top should have done the trick. When you say another machine I presume you mean another computer? If so I suspect there is maybe something in the first one stopping the xml getting written correctly when shutting down Mach.
Afraid I dont drink so you will just have to have that pint yourself :)
Hood
-
well not sure its in the xml ok so I suspect your right just going to install an clean image an start again. I have a few Dll might be interfering so I remove the drivers
-
Let us know the outcome :)
Hood