Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: LexMotorsports on February 08, 2018, 04:03:34 PM
-
Hey all, I have a 4x8 cnc plasma running off Mach3 and a gecko g540. I don’t have any limit
Or home switches and I need at least 2 on the Z axis for the PROMA. I need help please.
http://openbuildspartstore.com/micro-limit-switch-kit-with-mounting-plate/
I have these 2 switches, and I kind of understand the wiring. Where should I move toward next?
I need to mount them still as well.
Also I have my PROMA wired and it is reading voltage, I just need to wire it up to the g540 after I get
The 2 Z axis limit switches working.
Any help would be appreciated
Thanks
-
Hi,
are you looking for home switches or limit switches?
I know a lot of people combine the two jobs but there are some good reasons why that is not the best. It used to be that because we all had only parallel ports we
had to economise on inputs. With external controllers offering many more inputs you don't, in fact probably shouldn't do that today.
My recommendation for home switches are Omron or Honeywell Roller Plunger microswitches. They offer good repeatability and accuracy and can be mounted within
the machine boundaries thereby freeing the very ends of travel for the limit switches.
http://www.machsupport.com/forum/index.php/topic,36285.msg248575.html#msg248575 (http://www.machsupport.com/forum/index.php/topic,36285.msg248575.html#msg248575)
Craig
-
I’m trying to put 2 limit switches on my Z axis only. I have 4 available inputs on my g540 so I’m not worried about space.
-
Hi,
OK, those switches I linked to can be used as limit switches as well but are fairly sizable. The ones you pictured will work OK.
Another possibility is inductive proximity sensors, they can make for a tidy and robust installation.
No matter what switches or sensors you use you should give some thought to what happens if the axis runs away. Trust me it DOES happen!
Any switches/sensors in the way are going to get crunched, may not be the end of the world but certain arrangements or mountings mean that even
a runaway axis won't break them.
Craig
-
i think you are talking about PROMA THC.
on the PROMA Homepage:
http://proma-elektronika.com/index.php/en/products/thc-torch-height-control/compact-thc-150
are wiring digramms and Videos avalaiable as well.
i would start with tis stuff.
-
Hi,
OK, those switches I linked to can be used as limit switches as well but are fairly sizable. The ones you pictured will work OK.
Another possibility is inductive proximity sensors, they can make for a tidy and robust installation.
No matter what switches or sensors you use you should give some thought to what happens if the axis runs away. Trust me it DOES happen!
Any switches/sensors in the way are going to get crunched, may not be the end of the world but certain arrangements or mountings mean that even
a runaway axis won't break them.
Craig
Thanks Craig, i appreciate the input. i will have a look at the switches you linked. also im not worried about the Z axis running, i have some physical stops that will not let it go further than i want it.
-
Hi,
OK, those switches I linked to can be used as limit switches as well but are fairly sizable. The ones you pictured will work OK.
Another possibility is inductive proximity sensors, they can make for a tidy and robust installatio
No matter what switches or sensors you use you should give some thought to what happens if the axis runs away. Trust me it DOES happen!
Any switches/sensors in the way are going to get crunched, may not be the end of the world but certain arrangements or mountings mean that even
a runaway axis won't break them.
Craig
Can you explain to me exactly how limit switches need to be wired in?
-
Hi,
its common practice to wire all the limit switches in series with normally closed contacts. When any one switch operates the continuity of the switch string is broken and
that is what Mach detects. There again its common, but not universal to have Mach Estop on a limit event.
Large and powerful machines are even more safety oriented and a limit event will cause the axis drives and spindle to de-power. When a machine de-powers in such a manner
it is a time consuming matter to restart the machine, assuming no damage is done, and pick up where the job currently in the machine is and start from there.
None the less safety requires such an arrangement, if the controller has 'brain fade' and the EStop doesn't work or is slow, it is essential that the machine be made safe.
Because of the inconvenience and lost time a great deal of effort is expended to prevent a machine from ever operating the limit switches.
Mach has soft limits. They are programmed usually to be just inside the physical limits and limit switches. The program will detect that you or your Gcode is attempting
to drive your machine out of bounds and stop you. They work really well, but they absolutely rely on the machine being referenced or homed. So when you turn your
machine on and you 'home' your machine it will drive to pick up its home switches in each axis. Mach knows thereafter where it is in relation to the boundaries of the
machine and soft limits become useful.
It is for this reason that I argue that good, reliable, repeatable home switches are more important than limit switches. For about a year or so I operated my mill
without home switches and suffered a few crashes because soft limits didn't work because the machine was not repeatably referenced. Once I got around to fitting
home switches the number of out of bounds moves dropped dramatically. Good home switches were the best addition/development I ever did on my mill not to mention
very cheaply too!
Craig
-
What do I need to buy and how do I wire in 2 limit switches to my Z axis only? I have a g540 board and my e-stop is bypassed. It is very simple. I have one single relay, and it is only used to fire my plasma.
-
Hi,
you need two microswitches which can be mounted at the ends of the Z axis. You could use proximity sensors if you wish, but simple and bang for your
buck microswitches are fine.
You need a powersupply, I've shown it as 5V+ in the diagram, but whatever it is on your G540, hooked through the two normally closed contacts to one of your spare
input pins on the G540. Probably a good idea to include a resistor so that you can be sure the input pin goes low when one of the switches opens. Hook a 10k (approx.)
resistor between your selected input pin and earth on the G540.
The input pin can now be assigned as your Z++ and Z-- inputs with Mach3 and they will be active low.
Craig
-
Hi,
I just downloaded a copy of the G540 manual and it can be done very much simpler again, disregard the previous diagram....
Craig
-
Thank you I will order some new switches and then I will see how it goes!
I appreciate it a ton
-
If this is stepper powered, I would not fit limits at all, even a runaway axis on a stepper drive is unlikely to damage a machine, servos on the other hand = serious damage.
I would simply fit a good home switch and set soft limits up to work well. The first action upon start-up should be to home or reference the machine anyway IMHO.
I have fitted limits to my stepper builds but i realise now they are a waste of effort and inputs etc, they just do nothing, as long as soft limits are working.
There are those that never home their machines, maybe then a limit might help, doubtful still.
-
Hi,
to be honest I go with Dave here, good home switches and proper softlimts beat limit switches hands down.
I got the impression that OP needed limit switches for the Proma device.
Craig
-
I had a PROMA and it knows nothing of limits, it just reads voltage, compares to a set-point and outputs up and down signals for the z axis. It also has an arc-ok output IIRC.
-
Hi Dave,
I've never had a chance to play with a Proma but my recollection of the documentation I read about them did not mention limits.
It is for this reason that I argue that good, reliable, repeatable home switches are more important than limit switches
I have already made the same point to OP....if he prefers limits over a home switch...that's his choice.
Craig
-
In the proma manual is says it “uses inputs of outermost connectors LIMIT OR HOME - THC relay contacts should be connected to the terminals the same way as limit switches connectors.”
What are your thought? This is out of the proma manual they sent me
-
Hi Dave,
I've never had a chance to play with a Proma but my recollection of the documentation I read about them did not mention limits.
It is for this reason that I argue that good, reliable, repeatable home switches are more important than limit switches
I have already made the same point to OP....if he prefers limits over a home switch...that's his choice.
Craig
I am open to anything any will wire it however you guys think is the best, most efficient way. I am just saying, I’ve been running my table for 5 years, no limits or anything so I’m not worried about any runaways or resetting to come back tomorrow to same part stuff. I just want to hook my PROMA up and have a working THC. Any help is greatly appreciated!
-
All of my parts on my table are custom parts every time so I make a new zero every time
-
In the proma manual is says it “uses inputs of outermost connectors LIMIT OR HOME - THC relay contacts should be connected to the terminals the same way as limit switches connectors.”
What are your thought? This is out of the proma manual they sent me
This is BAD writing on behalf or Proma - it has NOTHING to do with limits at all.
From the manual....
The relay outputs “Arc, Up, Down”, are controlling outputs via relays, and should not be utilized for anything other then it's intended use.
COM terminal is a common input terminal connected to the ARC, UP and DOWN relay contacts inside the device, according to the diagram located on the cover (above picture). Suggested route is to “GND” at driver/pc end. Do not jumper this connection to the “7-35V” negative.
ARC output (also known as “Arc Okay”) is activated when plasma ignition is detected. Route and configure for a software input. Not required to operate.
UP output is activated when the measured voltage is lower than the voltage setpoints, reduced by half the hysteresis voltage. Route and configure for a software input.
DOWN output is activated when the measured voltage is higher than the voltage setpoints, reduced by half the hysteresis voltage. Route and configure for a software input.
Note: No output relays are activated in case when only the pilot arc is detected and when the main arc is broken.
SO, you need to connect the ARC, UP, DOWN to suitable free inputs on your BOB, then connect the COM to whatever your BOB needs - +5 or 0v etc.
Next configure Mach3 inputs to recognise the input signals from the PROMA.
Now, put the PROMA into test mode - this just sends repeat UP & DOWN outputs to Mach - make sure your Z axis responds in the correct direction, if not, fix it in settings. You may need to set temporarily in Mill options, ports and pins - allow THC moves when not in THC mode to let the z move without an Arc OK signal.
Next connect your plasma - are your using HIGH voltage inputs or LOW voltage inputs??????
-
All of my parts on my table are custom parts every time so I make a new zero every time
This is all personal setup - all my stuff is original etc but i always home first, it has allowed me to save jobs after a problem or two ;)
-
Okay I will hook it up like that right now. My proma is already hooked up measuring voltage!
-
Great- you got the dangerous bit working OK :)
the rest is just simple inputs, nothing more. you can even debug by replacing the proma with simple push switches - all you need is to get proper up & down control of the Z axis.
-
Thanks a lot you’ve helped a ton. I’m gonna mess around with this thing for a few and I’ll let you know if I run into promblems! Thank you!
-
Great- you got the dangerous bit working OK :)
the rest is just simple inputs, nothing more. you can even debug by replacing the proma with simple push switches - all you need is to get proper up & down control of the Z axis.
For COM, I connect this to the ground on my power supply?
-
Not usually - it all depends on what signal your BOB is looking for - some go to 0v on the BOB, some goto +5v on the BOB etc
Is there no connection for "inputs common" on the BOB?
-
I have UP on input 1, DOWN on input 2, ARC on input 3, and COM on input 7?
-
It’s a gecko g540 board
-
Looks like you want pin12 NOT 7 as com.
-
I have it all wired up as said, what should my setting be in Mach?
-
In ports & pins, inputs, set UP, DOWN & ON respectively to the inputs you wired - ON is ARC OK signal.
-
Looks like you want pin12 NOT 7 as com.
Pin 12 has a wire coming from my power supply, should I just combine them in the single input?
-
Yes, thats what i saw on the web for G540 wiring examples - it should the 0V line IIRC
-
Hm. I have it all wired up like said. In my inputs and outputs I have THC ON , with port 1, input 3
THC UP is on, port 1, pin 1, THC DOWN is on, port 1, pin 2. Allow thc is on in mill options, no movement in test.
-
Hi,
those signals are inputs to Mach. Therefore you can only use the designated input pins of the parallel port, pins 10-13 and pin 15.
Craig
-
What Craig said ++++ ;)
-
i think you are talking about PROMA THC.
on the PROMA Homepage:
http://proma-elektronika.com/index.php/en/products/thc-torch-height-control/compact-thc-150
are wiring digramms and Videos avalaiable as well.
i would start with tis stuff.
sorry that i repeat me.
wirring and configuration is all shown, on that link i have posted on page 1 of this thread.
-
I have everything wired and settings put as said on PROMA website and nothing happens.. I’m stuck and idk where to go
-
Hi,
on the Machine Diagnostics page do your new limit switches light up when you activate them by hand?
Craig
-
These are not "limit' switches - they are just inputs to Mach via the BOB, they should show in diagnostics - do they??
With Proma in test mode, the Up/Down inputs in diagnostics should be flashing
-
ok just to confirm wiring:
power supply V+ -> G540 terminal 11
power supply GND -> G540 terminal 12
power supply GND -> Proma terminal COM
Proma terminal UP -> G540 terminal 1
Proma terminal DWN -> G540 terminal 2
Proma terminal ARC -> G540 terminal 3
Mach3 Config -> Ports & Pins -> Inputs
THC ON - Enabled checked - Port 1 Pin 12
THC UP - Enabled checked - Port 1 Pin 10
THC DOWN - Enabled checked - Port 1 Pin 11
Mach3 1024 Screen set -> diagostics -right hand side about middle
there are three LED's Torch ON , Torch UP , Torch Down
put just for test a wire from
power supply GND -> G540 terminal 1
now Torch Up LED should be on.
-
My g540 pin 12 goes to my power supply V-. It has always been wired like this.
-
That is correct, 0v, GND, -v are generally the same thing.
-
So my settings in Mach are correct, and I have active lows checked
-
Everything seems to be hooked up correctly and I’m using my proma right now just to test voltage from the arc and the proma is getting a bad arc reading or something it keeps cutting in and out
-
and what are the THC up and down LED show in diagnostic screen ?
-
When I put my proma in test mode it shows arc on and up on proma and in diagnostic it shows torch up, torch on, no movement from torch though. When I run a gcode, it starts, moves to position, fires the plasma and doesn’t move, just continues to blast.
-
what are your Settings in
Config -> Ports&Pins - Mill Options -> THC Options ?
-
Advanced compensation analysis is checked, allow THC UP/DOWN control is checked
-
if you go to Settings Screen, what does the Enable THC Tog. Led ?
-
When I put my proma in test mode it shows arc on and up on proma and in diagnostic it shows torch up, torch on, no movement from torch though. When I run a gcode, it starts, moves to position, fires the plasma and doesn’t move, just continues to blast.
Don't jump ahead to live testing UNTIL you get torch moving up and down under test - you will dive into a world of problems, trust me, been there ;)
Get torch bouncing up and down with Proma in test mode first - it must move or you on a hiding to nowhere.
-
Should it be toggled on flashing?
-
Everything seems to be aware of the PROMA and it’s getting the inputs in the diagnostic screen.. it’s just not moving. M1 Home And M3 home are also flashing on diagnostic screen
-
I don't think M1 & M3 should be flashing just the torch up, torch down should be alternately flashing and torch on should be on.
Is mach3 out of reset i.e. in run mode?
-
Yes
-
What could I be missing? I’m lost
-
I got Z axis running under test mode, making movement up / down and recognizing itself in mach3. What is M1 home m2 home and m3 home? My M3 Home is lit up with torch on, m1 Home is lit with torch up, m2 home is lit up with torch down.
-
When I run a gcode with THC on and trying to operate with it, the Gcode moves to the pierce point, pierces and then gets stuck. If I click stop, it will jump to the next line in code and begin to make its way to the next pierce point, where it does the same thing. Any ideas?
-
I’m using sheetcam, could my post processor have something to do with it?
-
I got Z axis running under test mode, making movement up / down and recognizing itself in mach3. What is M1 home m2 home and m3 home? My M3 Home is lit up with torch on, m1 Home is lit with torch up, m2 home is lit up with torch down.
M1 M2 M3 home are the home liit Switches from X Y and Z axis.
so it Looks like you have configured home Limits (Config -> Ports&Pins -> Inputs) to the same port and pin like the torch signals.
Should it be toggled on flashing?
i think it has to Flash.
i will try to Setup TNC this afternoon on my mill, to see what we arer missiing.
Thomas
-
Im using sheetcam, could my post processor have something to do with it?
can post the code, you are trying to run ?
-
If its not moving after pierce, check you are getting ARC OK signal into mach from Proma and also that Proma is seeing the Arc voltage as being more than pierce voltage - there is a setting in proma for this. If its not sending arc ok that will cause the torch to freeze.
-
here:
http://eagleplasma.com/How%20to%20setup%20Mach3.pdf
i found a Manual for THC Setup
-
If its not moving after pierce, check you are getting ARC OK signal into mach from Proma and also that Proma is seeing the Arc voltage as being more than pierce voltage - there is a setting in proma for this. If its not sending arc ok that will cause the torch to freeze.
When it pierces it hits like 220v really fast and then just goes all over the place, I figured it was doing this because there was no metal for the arc any longer.. but what should I try?
-
When testing, Mach is not going into reset or freezing is it - this can be a problem with noise from the plasma, if not, can you still jog it around AFTER trying a cut - is it still talking to the BOB/machine?
Just trying to rule out various possibilities for failure
-
ok made a test on my mill (cs-lab Motion Controller)
what i did:
1. loaded Plasma Screen
2. configured three Inputs Torch ON - Torch UP - Torch DWN
3. Turnen THC ON (Programm run Screen), also set Config -> Ports&pins -> Mill Option -> Allow THC up/down
4. Set THC Min and THC Max to -20 and +20 (mm i am working in metric, therefor i had to modify Screen dro's to see the sign)
5. then i was able to drive Z axis up and down within THC Max / Min range
hope it helps.
Thomas
BTW are you running Mach3 in Demo? remember that THC is not working in DEMO, but can't find this anymore.
-
When testing, Mach is not going into reset or freezing is it - this can be a problem with noise from the plasma, if not, can you still jog it around AFTER trying a cut - is it still talking to the BOB/machine?
Just trying to rule out various possibilities for failure
Yes I can after I hit stop on my gcode.
-
ok made a test on my mill (cs-lab Motion Controller)
what i did:
1. loaded Plasma Screen
2. configured three Inputs Torch ON - Torch UP - Torch DWN
3. Turnen THC ON (Programm run Screen), also set Config -> Ports&pins -> Mill Option -> Allow THC up/down
4. Set THC Min and THC Max to -20 and +20 (mm i am working in metric, therefor i had to modify Screen dro's to see the sign)
5. then i was able to drive Z axis up and down within THC Max / Min range
hope it helps.
Thomas
BTW are you running Mach3 in Demo? remember that THC is not working in DEMO, but can't find this anymore.
I have that all figured out, THC is running in perameters while in TEST mode. I can’t seem to get it to function in working mode while runnin g a gcode. The code seems to be freezing on any file.
-
Even if I leave my plasma off, the gcode freezes at the first M03 code
-
Everything is working but the GCODE files are freezing every time the torch is fired
-
If I go into config-> ports pins -> input, and disable all the THC ON THC UP THC DOWN inputs, then restart mach3, the SAME EXACT GCODE FILE will run no problems.
-
are you sure THC ON is comming when Plasma fires ?
Mach will wait for this signal until it starts X/Y
-
No, my output 1 lights up, that’s how it is when it runs normally thought.
-
you mave to make sure THC ON is comming ortherwise X/Y will wait for it.
can you post your M3 macro ?
-
How can I make sure of this? Any if that’s the case then why won’t Mach wait for it when’s THC ON isn’t enabled?
What is my M3 MACRO? Sorry.
-
here a part of Mach3Mill_Install_Config Manual Appendix A Torch Height Controls
in Mach3
Notes:
• Turning spindle ON sets the THC correction to zero. Min/Max step counts are then effective from
the current Z.
• Only licensed versions can enable THC mode.
• When in THC mode, motion will not begin until THCON (Torch OK) signal becomes active.
Motion may be delayed by Pierce Delay.
• Pierce Delays tells the system not to move until delay seconds have passed since spindle (torch)
was turned on.
• Config/spindle Torch AutoOff setting shortens delay in takeoff, and also turns off torch automatically
if motion stops.
-
How can I make sure of this? Any if thats the case then why wont Mach wait for it whens THC ON isnt enabled?
don't ask i haven' done the Software for that THC controll in Mach
What is my M3 MACRO? Sorry.
c:\Mach3\Macros\your Profile Name\M3.M1S
-
here a part of Mach3Mill_Install_Config Manual Appendix A Torch Height Controls
in Mach3
Notes:
• Turning spindle ON sets the THC correction to zero. Min/Max step counts are then effective from
the current Z.
• Only licensed versions can enable THC mode.
• When in THC mode, motion will not begin until THCON (Torch OK) signal becomes active.
Motion may be delayed by Pierce Delay.
• Pierce Delays tells the system not to move until delay seconds have passed since spindle (torch)
was turned on.
• Config/spindle Torch AutoOff setting shortens delay in takeoff, and also turns off torch automatically
if motion stops.
I’m not sure where to even go from this..
-
How can I make sure of this? Any if thats the case then why wont Mach wait for it whens THC ON isnt enabled?
don't ask i haven' done the Software for that THC controll in Mach
What is my M3 MACRO? Sorry.
c:\Mach3\Macros\your Profile Name\M3.M1S
I am getting my macros onto a zip right now I will post them asap
-
this is the only part witch is urgent for now:
Notes:
When in THC mode, motion will not begin until THCON (Torch OK) signal becomes active.
-
is this the correct file?
-
this is the only part witch is urgent for now:
Notes:
When in THC mode, motion will not begin until THCON (Torch OK) signal becomes active.
This being said, my TORCH ON is lit up anytime the THC is in test mode, the TORCH UP and TORCH DOWN were alternating but the TORCH ON was a solid led on.
-
ok your M3 macro is Standard, should be no Problem.
what are your Settings in
Config -> Ports&Pins -> Spindle Setup ->CW Delay Spin Up ?
-
This setting I have always adjusted based on material thickness, but I usually leave it on .5 seconds as a standard. My spin down is 1 second and the immediate relay off is checked
-
This is such a headache. I feel like I’m so close.. ???
-
i have tested this Little GCode:
F50
S0
G1 X0 Y0
M3
G1 X10 Y0
here:
i have two situations tested
1. run Programm without THC ON Signal -> machine waits after M3 until THC ON is high.
2. run Programm with THC ON allready high -> Machine start's M3 immediately (after CW Delay Spin Up time)
so i am a little bit out off ideas now.
BTW Config ->Ports&Pins -> Spindle Setup -> Special Option's are all disabled ?
-
Torch/code freezes after M03....
That is correct behaviour - the the torch is firing on the M03 signal BUT mach3 is NOT seeing an Arc-Ok signal so it will NOT move at all.
The Proma is either not sending or not seeing the arc-ok.
As a test, go ports&pins and disable Arc-Ok IIRC this should let it move without seeing the signal.
-
one more idea:
pls doublecheck that the port and pin you have configured is nowhere else used in Input configuration.
-
Torch/code freezes after M03....
That is correct behaviour - the the torch is firing on the M03 signal BUT mach3 is NOT seeing an Arc-Ok signal so it will NOT move at all.
The Proma is either not sending or not seeing the arc-ok.
As a test, go ports&pins and disable Arc-Ok IIRC this should let it move without seeing the signal.
he did this allready see one or two sides before
-
I got arc ok signal, torch is firing and moving. I had to disable my x home z home a home y home, but getting proper signal now. Now the issue is that the THC is diving the torch head into the material when it’s going for its 2nd pierce
-
I can fire plasma and manually jog, THC runs great. But when I run gcdoe, it dives into material
-
It’s only allowing the Z axis to move up half the distance it should, which then drives t down the full distance into the material. Any ideas?
-
Increase your voltage on the proma 2 or 3v and try again.
Did you do a test cut to establish the correct voltage?
-
Yes! 160 ish seems about right.
-
somewhere i found this:
-
I can fire plasma and manually jog, THC runs great. But when I run gcdoe, it dives into material
can you pls post your GCode , maybe something is wrong there.
-
Yes! 160 ish seems about right.
That was the voltage displayed while doing a straight cut with the THC turned off in Mach3 over a reasonable distance like 200-300mm??
-
It’s acting kind of weird. It’s working sometimes, other times not. Sometimes it dives, sometimes it doesn’t.
-
I can fire plasma and manually jog, THC runs great. But when I run gcdoe, it dives into material
can you pls post your GCode , maybe something is wrong there.
-
Yes! 160 ish seems about right.
That was the voltage displayed while doing a straight cut with the THC turned off in Mach3 over a reasonable distance like 200-300mm??
see its weird, even if i uncheck the THC boc on the plasma screen., the THC still functions the same as if the THC button was on.
-
GCode is ok
the box with ideas is empty now.
-
thats where im at........
-
may i ask you to post your Profile XML
C:\Mach3\your profilename.xml
maybe i can find something there, but i think it will be tomorrow,
it late here in Bavaria ;).
i think we are Close.
-
Yes at lunch right now will post when I return.
I think we are close too. I have full function during g code, it’s just seems like it’s forgetting where my zero is for that work piece in reference to the Z AXIS. It will work on the first cut perfect, sometimes the second cut perfect, but then it goes for the third cut and dives itself into the material. I have adjusted the thc min and max as well. It seems to work in those perameterss until it decides to dive itself.
-
Torch dive is usually a plasma thing not a Mach thing, you are close but this can be a pain.
Is the metal flat?
Is the return lead clamped to the metal not the table?
What plasma supply do you have?
-
Well it’s changing it’s Z by itself in Mach. Wherever I set the Z, in reference to home, and then Zero out, run gcode, it tries to dive but I stop it before it gets to metal, then when I press return to Z, it goes all the way back To x,y 0,0 then when the Z makes it descent it tries to go lower than where I set the Z.
-
It seems like it’s making the Z lower than what i set it to..
-
But yes metal is flat. 10 ga MS cold rolled, lead clamped to table but that’s how I’ve always run it for the last 4.5 years.. I have thermal dynamic cut master a60. Been running it for years with no issues of plasma dive until now
-
It’s setting my Z height at zero -.7 units from where I set it before running the Gcode.
-
Is your Z losing steps?
-
How can I check that? It never has before..
-
I put my THC min on 0. Max is 2. I got the THC running with GCODE great. I cut 2 things, but next problem. When running, if the THC measures voltage too far, and makes moves to lower Z, it will go below the 0 THC MIN setting I set. It will finish that cut perfect, regardless that it’s below my THC MIN setting. Next pierce it continues and then drives itself into material.
-
Then, I set my THC MIN lower, like at -.5. Go to run again, it cuts first pierce awesome, goes to do second and drives into material, I’m guessing it’s trying to get to that THC MIN setting?
-
here:
http://www.machsupport.com/forum/index.php/topic,35183.0.html
i found a thread, witch sounds like the same Problem.
i have read the proma Manual again, i am a Little bit stuck
at this:
"H - U" (High Voltage) - value of the off load voltage detection
in the plasma cutter - used to detect the main (cutting) arc: 50-
300V by default: 200V
Parameter.My question is what does Proma if cutting voltage is below this Parameter ?
for my understanding this Parameter should be below cutting voltage, but i don't really know.
on the Plasma Programm run Screen is a dro called Curr:
this should be zeroed after each M3 call (Torch ON) ?
what does the DOWN LED on Proma in the Situation when the torch goes into material ?
sorry that can't provide the real solution.
Thomas
-
To find the off-load voltage or open-circuit voltage, just fire the torch into air - this only works if not is a pilot-arc or blowback-arc torch though, and do not do it for too long as it will melt the torch tip.
-
I think my PROMA may be bad.. I’m only getting ARC OK signal on the PROMA itself every once in a while and it’s very inconsistent
-
have you tryed this
H - U" (High Voltage) Parameter ?
-
HI at do I change it to? Whenever I try a dry fire test in the air to get the correct voltage, it shoots 180-190 v
-
All you need to discover is the voltage when NOT cutting and the voltage ranges when it IS cutting - set the H-U setting to be higher than the voltages when cutting as it needs to see the change from piercing to cutting.
Sounds like your setting is on the border, it needs a bit more of gap.
-
I will continue to trouble shoot things once I get my table back up and running. My G540 board crashed and I’m working on getting that fixed. Thanks for all the help
-
My G540 board crashed and Im working on getting that fixed.
when i read this, an the other "strange" things witch are Happening,
have you thought about noise , grounding , shielding ?
just a thinking.
Thomas
-
i dont think im having a grounding problem, because before i installed the PROMA i never had any issues. but maybe noise? cause none of my PROMA wires are shielded, and they run into my G540's home.. i will change all the wires out to shielded wires and mess with the H-U setting as soon as i get the driver fixed on my G540! thanks for all the help!
-
is there some sort of setting to make MACH compensate for the Z axis movement? i believe thats what happeneing here, my MACH is not compensating for the distance that the PROMA has made the torch move.
ive adjusted my settings in the PROMA, so now it is properly reading the arc voltage and is telling MACH to ARC OK every time.
im just stuck on the Z axis driving itself into the metal AFTER the PROMA has made adjustments to the Z axis height during the previous cut.
really confused.. ??? >:(
-
Have you got a floating head?
This is a slide assembly and switch on the torch mount that is used for probing the height before every pierce or every few pierces.
-
Have you got a floating head?
This is a slide assembly and switch on the torch mount that is used for probing the height before every pierce or every few pierces.
no i dont.. do i NEED one? would that fix my issue?
-
Have you got a floating head?
This is a slide assembly and switch on the torch mount that is used for probing the height before every pierce or every few pierces.
i have a floating head but i do not have any type of probe or anything that senses the material before every pierce. i am very interested in getting that kind of set up going though. what would i need to add to my existing "floating head" to make it sense the material every pierce? can MACH3 support that?
-
Not sure, as i understand it, your z axis is not remembering where you set it before starting cutting i.e. you maybe set z zero with a gap of say 3mm between torch and work - it then cuts ok, moves up and down with THC but when finished, Z Zero is no longer 3mm form work??
Its hard to tell as my table has material height sense at the start of each cut so if it did lose position, it would reset it every time.
If you have a floating head, all you should need is a switch fitted in the right place, an input to the Probe input on Mach and some probing code, its pretty simple, oh and you need to alter your post processor IIRC to call the probe cycle before each pierce.
-
Not sure, as i understand it, your z axis is not remembering where you set it before starting cutting i.e. you maybe set z zero with a gap of say 3mm between torch and work - it then cuts ok, moves up and down with THC but when finished, Z Zero is no longer 3mm form work??
Its hard to tell as my table has material height sense at the start of each cut so if it did lose position, it would reset it every time.
If you have a floating head, all you should need is a switch fitted in the right place, an input to the Probe input on Mach and some probing code, its pretty simple, oh and you need to alter your post processor IIRC to call the probe cycle before each pierce.
this is exactly the setup i need. the problems im really having trouble understanding is the probing code, and how would i go at altering my post procc? also, IIRC? sorry.
-
IIRC - If i recall correctly :)
Its not too difficult, I've had a few different setups on mine but they use the G28.1 or G31 reference codes, you will also need to add your pierce height setting into the mixture so it will probe the surface, set Z zero, then move to your pierce height and set z zero again then start cutting.
-
IIRC - If i recall correctly :)
Its not too difficult, I've had a few different setups on mine but they use the G28.1 or G31 reference codes, you will also need to add your pierce height setting into the mixture so it will probe the surface, set Z zero, then move to your pierce height and set z zero again then start cutting.
my pierce height is already in the mixture, i run sheetcam so i have my pierce height set at .05" currently. Cutting height is 0.
so what type of switch do i need? and would i fix it to my Z axis MIN setting? i cut many different thicknesses of metal, would this affect any of this setup as well?
also, back to the probing code and post processor, where would i find something like this?
Sorry for so many questions. i just REALLY want to get this figured out.
-
https://www.youtube.com/watch?v=DqRpxjJVGQ4
is this what im going for? im really troubled at the coding...
-
http://proma-elektronika.com/index.php/en/tips/plasma-detekcja-materialu
ive also come across this as well.
-
that axcacly discribes a flowting head.
get a Switch monted and connected, the we will go throug the code.
should be no big deal.
Thomas
-
Yep, thats it,
the switch is nOT connected to z-min etc it is a separate switch connected direct to the "Probe" input on mach3.
-
that axcacly discribes a flowting head.
get a Switch monted and connected, the we will go throug the code.
should be no big deal.
Thomas
Yep, thats it,
the switch is nOT connected to z-min etc it is a separate switch connected direct to the "Probe" input on mach3.
awesome my switches will be here on saturday, im modifying my floating head to work and i will let you guys know when i get it all hooked up! thanks a lot!
-
that axcacly discribes a flowting head.
get a Switch monted and connected, the we will go throug the code.
should be no big deal.
Thomas
I’m in process of mounting my switch right now, what do I need for the coding?
-
just make sure that the Switch of the Floating head 'switches' the probe input
-
1st thing is to get the switch to show up in diagnostic screen on "probe" or "digitise" input.
Edit
beat me to it ;)
-
Will work on that first thing in AM :) I feel like I’m so close!
-
I have my switch lighting up the “digitize” led in the diagnostic screen when the limit switch is active!
-
Great, thats a step further.
Now you need to modify your code/post processor to add a probing routine before each pierce, sorry but i cant help here as my setup is mega-modified and won't be applicable to yours.
Someone will be along though :)
-
Great, thats a step further.
Now you need to modify your code/post processor to add a probing routine before each pierce, sorry but i cant help here as my setup is mega-modified and won't be applicable to yours.
Someone will be along though :)
okay, from the reasearch ive done, im going to be using either the g31 or g28.1 code i think. Im running SheetCam, and im using the MACH3PLASMA post processor.
-
Great, thats a step further.
Now you need to modify your code/post processor to add a probing routine before each pierce, sorry but i cant help here as my setup is mega-modified and won't be applicable to yours.
Someone will be along though :)
what do you mean your setup is mega-modified? what have you modified?
-
SheetCam is a good app.
My setup has a pneumatic actuated probing switch, custom probing macro, screenset, external THC and various other bits and bobs.
-
I tried using the MP1000THC PP and it seems the torch is jogging up to find the probe instead of down
-
SheetCam is a good app.
My setup has a pneumatic actuated probing switch, custom probing macro, screenset, external THC and various other bits and bobs.
I’ve never heard of a setup like that. Sounds complex! How does it work?
-
I tried using the MP1000THC PP and it seems the torch is jogging up to find the probe instead of down
I think there is a setting for that somewhere
-
SheetCam is a good app.
My setup has a pneumatic actuated probing switch, custom probing macro, screenset, external THC and various other bits and bobs.
I’ve never heard of a setup like that. Sounds complex! How does it work?
The probe switch is mounted on a small air cylinder, your one will use the nose of the torch to sense the material, my one uses a very delicate switch, in the macro the head is moved sideways a little to place the switch where the pierce will be, the switch lowers, the head then drops until the switch triggers, the Z position is set, the switch lifts up, the head lifts up, the head moves back to pierce position and away we go.
It sounds complex but its not and its pretty fast, the big benefit is that i can sense very thin material without the weight of the head/torch deflecting it downwards, IIRC I was the originator of the air cylinder probe and I'm glad to say others have used it as well now :)
Here's a video, it was early days then but functioning.
https://youtu.be/Z-N3LOs73tE (https://youtu.be/Z-N3LOs73tE)
-
I tried using the MP1000THC PP and it seems the torch is jogging up to find the probe instead of down
I think there is a setting for that somewhere
A setting in MACH3?
-
THats a really cool setup, kudos to you for designing it yourself
-
ok, back again,
i think we can use your M3.m1s macro for the Job:
copy this code to macro before the dospinCW()
pierceHeight = 0.5 'enter here a value for wanted pierceheiht
code "F30"
code "G31 Z-1"
While Ismoving()
Wend
code "G00 Z" & GetVar(2002) 'go back to the probepoint
While Ismoving()
Wend
code "G91 Z-" & pierceHeight
While Ismoving()
Wend
code "G92 Z0"
While Ismoving()
Wend
Code "G90"
-
i got a an error, it said syntax error, and wouldnt run and gcode files
-
Did you copy/paste or type it?
seems ok to me
-
I copy and pasted it
-
It worked!!!!!!!
-
I think I may have changed a setting in MACH that I shouldn’t have, I reset Mach and it worked!
-
Running test cysts right now, it’s working amazing. Now just to set my THC back up!
-
Hooked my PROMA back up, I’m back to where I was before I decided to add a floating head, the THC is working correctly, but seems to lose it Z after the first pierce.. it’s still diving itself into the material. (Just lost a limit switch.. RIP. good thing I ordered5)
-
My work offset Z is stuck at 1.7477. I can reset, ZERO, and it keeps jumping back to 1.7477
-
So, with my THC atttached, after it probes for z, it goes back up to where the probe started, then it dives down instead of going up to my pierce height..?
-
Pierce height should be in the g-code IIRC
-
MACH is applying random numbers to my Z offset. I don’t know what is going on
-
The probe isn’t operating correctly anymore, it’s not raising Z to go to pierce height after probing, it’s driving down into the material.
-
ok let's get back to the Basics,
open up vb scirper window
copy this code:
pierceHeight = 0.5 'enter here a value for wanted pierceheiht
code "F30"
code "G31 Z-1"
While Ismoving()
Wend
code "G00 Z" & GetVar(2002) 'go back to the probepoint
While Ismoving()
Wend
code "G91 Z-" & pierceHeight
While Ismoving()
Wend
code "G92 Z0"
While Ismoving()
Wend
Code "G90"
and use the ||> green buton to se what's goinng on
-
It probes good, then dives at g91. I changed 2002 to 0, then re ran, it got all the way passed g91 z- (at this point it was back at Z 0) then it dove .5” down instead of rising .5” up
-
sorry should be
code "G91 Z" & pierceHeight
-
That fixed the probing issue, still having the same issue with the THC.
-
is Torch DN in dignosic Screen defenitiv off?
-
Really interesting, on my second pierce, when it goes to probe it changed my cutting speed From 130 ipm to 30 ipm.?
-
is Torch DN in dignosic Screen defenitiv off?
I don’t understand.. sorry
-
Really interesting, on my second pierce, when it goes to probe it changed my cutting speed From 130 ipm to 30 ipm.?
ok my fault will give you new code soon
-
Thanks for all the help, I really appreciate it.
-
I removed the f30 line out and it fixed it. Now I just need to figure out why the THC is diving on 2nd pierce.
-
Really interesting, on my second pierce, when it goes to probe it changed my cutting speed From 130 ipm to 30 ipm.?
I have never seen this, as far as i know, the only things that can change the speed are :- Code, Feed Override, MDI
If yours is changing outside these commands then you have a problem I think.
-
It was the code, I got it fixed it’s good now. The problem I’m running into now is with my THC. The code will run great through the first pierce, but when it picks itself up to go to pierce #2, it only raises up “x” instead of raising up 1”. This throws the Z axis location off in MACH and then drives into material on next cut.
-
Could it be because I’m using a PP that is designed to run without a THC?
-
Could it be because I’m using a PP that is designed to run without a THC?
Doubtful, the port won't know a plasma cutter form a mill - its just a port.
After the cut, there should be an M05 which turns the torch off, then a G00 Znn where nn is your clearance height.
The clearance height is relative to the height by your probing routine, if the probing works, then the torch tip should return to clearance height after every cut.
Any chance you can show some code?
-
everything seems ffine to me,..,
-
When I run my code without the THC inputs active and with just probing, it (probing) works flawlessly. It’s when I activate my THC inputs in Mach then turn my THC on in the plasma sceeenset.
-
ok this code should work, and restore original feedrate
pierceHeight = 0.5 'enter here a value for wanted pierceheiht
orgspeed=GetDro(18)
code "F30"
code "G31 Z-1"
While Ismoving()
Wend
code "G00 Z" & GetVar(2002) 'go back to the probepoint
While Ismoving()
Wend
code "G91 Z" & pierceHeight
While Ismoving()
Wend
code "G92 Z0"
While Ismoving()
Wend
Code "G90"
Code "F" & orgspeed
-
everything seems ffine to me,..,
N0010 (Filename: 1.tap)
N0020 (Post processor: Mach3 plasma.scpost)
N0030 (Date: 28/02/2018)
N0040 G20 (Units: Inches)
N0050 G53 G90 G91.1 G40
N0060 F1
N0070 S500
N0080 (Part: 1)
N0090 (Operation: Outside Offset, LAYER_1, T1: Plasma, 0.0561 in kerf)
N0100 M06 T1 F80.0 (Plasma, 0.0561 in kerf)
N0110 G00 Z1.0000
N0120 X0.6134 Y0.6013
N0130 Z0.0000
N0140 M03
N0150 G03 X0.7726 Y0.6873 I0.0366 J0.1227 F80.0
N0160 X0.7726 Y0.6873 I-0.2726 J0.0813
N0170 X0.6865 Y0.8466 I-0.1227 J0.0366
N0180 M05
N0190 G00 Z1.0000
N0200 X1.1256 Y-0.1384
N0210 Z0.0000
N0220 M03
N0230 G03 X0.9976 Y-0.0104 I-0.1280 J0.0000
Hmm, N0100 & N0130 items seem odd to me
Tool change is not usually used in plasma, why is it going to Z0 before the pierce??
You should never, pierce at zero height, unless this is a scratch-start plasma??
-
ok this code should work, and restore original feedrate
pierceHeight = 0.5 'enter here a value for wanted pierceheiht
orgspeed=GetDro(18)
code "F30"
code "G31 Z-1"
While Ismoving()
Wend
code "G00 Z" & GetVar(2002) 'go back to the probepoint
While Ismoving()
Wend
code "G91 Z" & pierceHeight
While Ismoving()
Wend
code "G92 Z0"
While Ismoving()
Wend
Code "G90"
Code "F" & orgspeed
Is this necessary? I have my my plunge rate in sheetcam set at 20ipm.
-
everything seems ffine to me,..,
N0010 (Filename: 1.tap)
N0020 (Post processor: Mach3 plasma.scpost)
N0030 (Date: 28/02/2018)
N0040 G20 (Units: Inches)
N0050 G53 G90 G91.1 G40
N0060 F1
N0070 S500
N0080 (Part: 1)
N0090 (Operation: Outside Offset, LAYER_1, T1: Plasma, 0.0561 in kerf)
N0100 M06 T1 F80.0 (Plasma, 0.0561 in kerf)
N0110 G00 Z1.0000
N0120 X0.6134 Y0.6013
N0130 Z0.0000
N0140 M03
N0150 G03 X0.7726 Y0.6873 I0.0366 J0.1227 F80.0
N0160 X0.7726 Y0.6873 I-0.2726 J0.0813
N0170 X0.6865 Y0.8466 I-0.1227 J0.0366
N0180 M05
N0190 G00 Z1.0000
N0200 X1.1256 Y-0.1384
N0210 Z0.0000
N0220 M03
N0230 G03 X0.9976 Y-0.0104 I-0.1280 J0.0000
Hmm, N0100 & N0130 items seem odd to me
Tool change is not usually used in plasma, why is it going to Z0 before the pierce??
You should never, pierce at zero height, unless this is a scratch-start plasma??
My pierce height says 0” in sheetcam, because with the edited m3 macro, i was having to control the pierce height in there.
-
ok ihave run your code on my PP testmachine.
deleted N100 toolchange not necesary.
run it with THC on but no Inputs connected. everything was ok.
can you for a test disconnect the THC Up/dn Inputs , but physicaly disconnect them.
-
ok this code should work, and restore original feedrate
pierceHeight = 0.5 'enter here a value for wanted pierceheiht
orgspeed=GetDro(18)
code "F30"
code "G31 Z-1"
While Ismoving()
Wend
code "G00 Z" & GetVar(2002) 'go back to the probepoint
While Ismoving()
Wend
code "G91 Z" & pierceHeight
While Ismoving()
Wend
code "G92 Z0"
While Ismoving()
Wend
Code "G90"
Code "F" & orgspeed
Is this necessary? I have my my plunge rate in sheetcam set at 20ipm.
yes because you have a "variable" cuttin feedrate but probing feedrate should allways be the same.
-
ok ihave run your code on my PP testmachine.
deleted N100 toolchange not necesary.
run it with THC on but no Inputs connected. everything was ok.
can you for a test disconnect the THC Up/dn Inputs , but physicaly disconnect them.
So leave THC on, and inputs active, but physically remove the inputs into my g540?
-
ok ihave run your code on my PP testmachine.
deleted N100 toolchange not necesary.
run it with THC on but no Inputs connected. everything was ok.
can you for a test disconnect the THC Up/dn Inputs , but physicaly disconnect them.
So leave THC on, and inputs active, but physically remove the inputs into my g540?
exactly
-
deleted N100 toolchange not necesary.
sorry i modified N100 to N100 F80 to Keep the fedrate
-
So leave THC on, and inputs active, but physically remove the inputs into my g540?
but disconnect only THC UP/Down inputs
-
deleted N100 toolchange not necesary.
sorry i modified N100 to N100 F80 to Keep the fedrate
Does the tool change code matter? It’s being generated by itself, but in MACH, my “ignore tool change” setting is checked. It has never been an issue
-
deleted N100 toolchange not necesary.
sorry i modified N100 to N100 F80 to Keep the fedrate
Does the tool change code matter? Its being generated by itself, but in MACH, my ignore tool change setting is checked. It has never been an issue
who knows ?
-
So leave THC on, and inputs active, but physically remove the inputs into my g540?
but disconnect only THC UP/Down inputs
Did this, everytbing is running smooth other than the proma actually making the inputs
-
Did this, everytbing is running smooth other than the proma actually making the inputs
can you please explain did not get this, sorry thats my bad english
-
I did what you said and it runs smooth but it’s not actually controlling the Z height.
-
deleted N100 toolchange not necesary.
sorry i modified N100 to N100 F80 to Keep the fedrate
Does the tool change code matter? It’s being generated by itself, but in MACH, my “ignore tool change” setting is checked. It has never been an issue
It shouldn't but in light of odd things going on, any odd code should be pulled i think just until its all working at least.
-
ok that means we know now that proma is sending z-axis down.
-
So maybe it’s a setting in my PROMA. I can’t think of anything else..?
-
MACH is changing my Z zero on its own after the first m05 code.
-
ok that means we know now that proma is sending z-axis down.
It’s not this, i can watch the PROMA while the code is running, and there’s is no led indicator on the face of the PROMA. It is just simply MACH changing the Z zero before the cut is finished, or when the m05 line is hit.
-
MACH is changing my Z zero on its own after the first m05 code.
Pretty certain Mach will not be doing it, something else, but not Mach, if it were then nobody would be using it and there are thousands of users.
-
MACH is changing my Z zero on its own after the first m05 code.
Pretty certain Mach will not be doing it, something else, but not Mach, if it were then nobody would be using it and there are thousands of users.
I guess I’m just lost, I don’t know where to look next
-
Could it possibly be the work offsets? I can’t set them to 0.
-
It needs a careful, methodical approach, step by step.
I would try disconnecting or turning off Proma, fit two switches - Z-up & Z-down to the points where the proma was connected.
Now, with the plasma turned off and code loaded, try running the code and you should be able to jog the torch up/down manually as it goes.
At the end, after M05, issue G0 Z0.5 in MDI and the torch should be 0.5 above the metal.
Post the results
-
Could it possibly be the work offsets? I can’t set them to 0.
Don't worry about WO,they will give you a headache, they are rarely zero and only indicate the difference in position from machine home to where you set XYZ zero.
Concentrate on the odd behaviour ;)
-
It needs a careful, methodical approach, step by step.
I would try disconnecting or turning off Proma, fit two switches - Z-up & Z-down to the points where the proma was connected.
Now, with the plasma turned off and code loaded, try running the code and you should be able to jog the torch up/down manually as it goes.
At the end, after M05, issue G0 Z0.5 in MDI and the torch should be 0.5 above the metal.
Post the results
My codes all end with
G00 z1
M05 M30
Also what is MDI, sorry
-
I’ve messed with the setting on the PROMA a little bit, and I have noticed: if I leave the delay timer on proma for a period longer than the duration of the cut itself, the z will work fine. If I lower the delay time, for a period shorter than the duration of the cut (PROMA makes adjustments to Z in Mach) the Z then doesn’t compensate for the distance traveled by the PROMA.
-
It needs a careful, methodical approach, step by step.
I would try disconnecting or turning off Proma, fit two switches - Z-up & Z-down to the points where the proma was connected.
Now, with the plasma turned off and code loaded, try running the code and you should be able to jog the torch up/down manually as it goes.
At the end, after M05, issue G0 Z0.5 in MDI and the torch should be 0.5 above the metal.
Post the results
My codes all end with
G00 z1
M05 M30
Also what is MDI, sorry
Not what i asked, but ok, when your code has finished running(torch off) enter G0 Z0 into the MDI and press enter
MDI = Manual Data Input - its a line/box where you can type G code directly and it will run as soon as you press enter
-
I’ve messed with the setting on the PROMA a little bit, and I have noticed: if I leave the delay timer on proma for a period longer than the duration of the cut itself, the z will work fine. If I lower the delay time, for a period shorter than the duration of the cut (PROMA makes adjustments to Z in Mach) the Z then doesn’t compensate for the distance traveled by the PROMA.
That is correct = by setting a long delay you are effectively turning THC OFF
The delay is a Pierce delay - it must be set JUST long enough for the pierce to happen and the torch to start moving, no longer, no shorter.
-
So, I fitted 2 switches to manually jog Z, it did the same exact thing that the proma was doing, so I adjusted my Z axis motor tuning as maybe it was losing steps? It is working perfect manually, I am going to hook the PROMA back up and try it now.
-
I believe the Z axis is losing its steps. Or something in this nature. I have my Z axis tuning : velocity is 15 and accel is 1. It is working with the PROMA just kind of weird. Needs fine tuning I think
-
what is your thc Speed Setting?
don't be surprised about my Setting, i am in metric
-
Ok, thats possible - try making up some simple code to rapid (G0) the Z axis from Z0 to Z2 (or whatever travel you have, run it maybe 10 times starting from Z0 at a known position and at the end go to Z0 - is the axis in exactly the same position it was at the start???
If you are losing steps it could well be this, plus, when running THC you need to know that the normal acceleration curve is not used, THC moves on Z are more like BANG-BANG-BANG really fast moves are needed here or by the time the Z has moved the torch is elsewhere :)
I think there its a setting called THC-Rate - its a % of speed, try going low and working up, however i cant remember if this is a generic Mach3 setting or one specific to my screen set/THC system.
Test for lost steps first
EDIT
just saw TPS' reply - thats the box i mentioned.
-
what is your thc Speed Setting?
don't be surprised about my Setting, i am in metric
15
-
Ok, thats possible - try making up some simple code to rapid (G0) the Z axis from Z0 to Z2 (or whatever travel you have, run it maybe 10 times starting from Z0 at a known position and at the end go to Z0 - is the axis in exactly the same position it was at the start???
If you are losing steps it could well be this, plus, when running THC you need to know that the normal acceleration curve is not used, THC moves on Z are more like BANG-BANG-BANG really fast moves are needed here or by the time the Z has moved the torch is elsewhere :)
I think there its a setting called THC-Rate - its a % of speed, try going low and working up, however i cant remember if this is a generic Mach3 setting or one specific to my screen set/THC system.
Test for lost steps first
EDIT
just saw TPS' reply - thats the box i mentioned.
I ran a code
G0 z1
G0 z0
G0 z 1.5
G0 z0
G0 z 1.3
G0 z0
Ect.. maybe 25 times over and over. Z Axis landed in same position every time.
I will mess with my setting on Z axis tuning,
Thanks
-
if you have still your buttons connected to THC up/dn you can also Play a Little bit with the THC speed
-
Yes as TPS says above, set your Z zero at a known position, then using the buttons move the Z up and down really violently, sharp changes are what is needed, up-down-up-down then go back to Z0 and see if it returned to where you set it.
If not then lower the THC speed a bit and try again.
-
Okay, so I’m at This point trying to get my Z axis to travel at its maximum speed before it makes an error?
-
Well, really we are trying to find out if THC moves (which are different to normal moves) are causing your Z axis to lose steps.
Maximum speed is not relevant yet, just trying to fix your odd Z issues.
-
Ever since I adjusted my Z axis motor to run at 15:15, it’s running perfect. I’ve been cutting some 1/4” , 14GA, and 10GA mild steel and it’s awsosme
-
Sounds good, if it works, go with it :)
-
I’m going to keep fine tuning the setting to make it work better, but it’s working great.
Thanks again for all the help, I appreciate it.