Homing with "X" axis with "A" motor as the SLAVE
I have now added switches so I can HOME and SQUARE the X axis. I have a question about how this should work.
Here is what I get when I hit "REF ALL HOME"
The X axis moves in the - direction ?(AS EXPECTED) When the Home Switches are hit each motor ("X" and "A") back OFF the switches?(AS EXPECTED) Then the "A" axis motor moves back to the switch and triggers it a second time and again it backs OFF and stops. (NOT SURE THIS IS CORRECT OR NOT)
Is there something I am missing?
Thanks, Troy
?
|
Yeah. T5 is the same / functionally similar stuff.
Woah..Namibia used to live (grew up in) africa.
On 18/02/2015 16:35, 'Andre Schoonbee'
andresch@... [mach1mach2cnc] wrote:
Been
looking at the HTD pulleys – is the same I have
?
My
drive system is using 60T T5 Timing pulley for driving and the
15T T5 Timing pulley connected to my 15T pinion gear. The belt
is T5 420 Timing belt
?
Sorry,
was for a moment thinking you talk about specialized stuff –
LOL
?
BTW
I am in Namibia
--
-hanermo (cnc designs)
|
Been looking at the HTD pulleys – is the same I have ? My drive system is using 60T T5 Timing pulley for driving and the 15T T5 Timing pulley connected to my 15T pinion gear. The belt is T5 420 Timing belt ? Sorry, was for a moment thinking you talk about specialized stuff – LOL ? BTW I am in Namibia ? ?
toggle quoted message
Show quoted text
From: mach1mach2cnc@... [mailto:mach1mach2cnc@...]
Sent: 18 February 2015 01:07 PM
To: mach1mach2cnc@...
Subject: Re: [mach1mach2cnc] Support? ? Great !
So, with the lower acceleration, the error does not appear, yes ?
Now, to confirm, put it back up to 100 again, and see if it now appears.
If it does, with high confidence, you have encountered the problem.
To quickly localise the max practical acceleration, first make sure you can reliably repeat the problem.
Then split the difference-
3-4 tests should get you very very close to the optimum number.
Ie, if at 100 it fails, and at 10 it does not (diff 90);
Try 10+45 = 55.
Errors, try 10+45/2 = 32.
No error, try 55+45/2 = 77.
And so on..
If you want more acceleration and better results, use HTD pulleys, 5 mm profile, 15 mm wide, at 1:3.
16 teeth small pulley, 48 teeth big one (less than 16 does not have enough belt wrap).
This will likely work reliably at around 100 (or could be even more) as you now have 300% more torque available.
Best,
h- On 18/02/2015 11:41, 'Andre Schoonbee' andresch@... [mach1mach2cnc] wrote: I did the tests a few times and the z-axis comes back to the correct zero position. This is after I have reduced the acceleration.
-- -hanermo (cnc designs)
|
|
This email has been checked for viruses by Avast antivirus software.
|
|
Who supply the HTD pulleys? Will for sure source them – the better my system works the better I am. ? I noted another issue- when doing a test in the air with this code, I noticed the spindle does not retract with enough clearance from one part to the next. And this is still in the air? I then stopped, went back to Z-Zero and it is perfect. But according to the code it is suppose to clear the 16mm board by lifting 21mm ? % O0001 N10 (PROGRAM PRODUCED? - 18 FEB 15) N20 G21 G90 (UNITS METRIC) N30 G40 G91.1 N2140 T07 M06 H07 N2150 S18000 M03 N2160 G0 X161.35 Y1313.125 N2170 G1 G41 D17 X155. Y1273.125 Z8.5 F2000 N2180 Y1098.125 F10000 N2190 X5. N2200 Y1448.125 N2210 X155. N2220 Y1273.125 N2230 Y1260.425 N2240 G40 X161.35 Y1220.425 Z21. N2250 G0 X161.35 Y1313.125 N2260 G1 G41 D17 X155. Y1273.125 Z1. F2000 N2270 Y1098.125 F10000 N2280 X5. N2290 Y1448.125 N2300 X155. N2310 Y1273.125 N2320 Y1260.425 N2330 G40 X161.35 Y1220.425 Z13.5 N2340 G0 X220. Y929.075 N2350 G1 G41 D17 X180. Y935.425 Z8.5 F2000 N2360 X5. F10000 N2370 Y1085.425 N2380 X355. N2390 Y935.425 N2400 X180. N2410 X167.3 N2420 G40 X127.3 Y929.075 Z21. N2430 G0 X220. Y929.075 N2440 G1 G41 D17 X180. Y935.425 Z1. F2000 N2450 X5. F10000 N2460 Y1085.425 N2470 X355. N2480 Y935.425 N2490 X180. N2500 X167.3 N2510 G40 X127.3 Y929.075 Z13.5 N2520 G0 X691.7 Y929.075 N2530 G1 G41 D17 X651.7 Y935.425 Z8.5 F2000 N2540 X367.7 F10000 N2550 Y1034.631 N2560 X935.7 N2570 Y935.425 N2580 X651.7 N2590 X639. ?
toggle quoted message
Show quoted text
From: mach1mach2cnc@... [mailto:mach1mach2cnc@...]
Sent: 18 February 2015 01:07 PM
To: mach1mach2cnc@...
Subject: Re: [mach1mach2cnc] Support? ? Great !
So, with the lower acceleration, the error does not appear, yes ?
Now, to confirm, put it back up to 100 again, and see if it now appears.
If it does, with high confidence, you have encountered the problem.
To quickly localise the max practical acceleration, first make sure you can reliably repeat the problem.
Then split the difference-
3-4 tests should get you very very close to the optimum number.
Ie, if at 100 it fails, and at 10 it does not (diff 90);
Try 10+45 = 55.
Errors, try 10+45/2 = 32.
No error, try 55+45/2 = 77.
And so on..
If you want more acceleration and better results, use HTD pulleys, 5 mm profile, 15 mm wide, at 1:3.
16 teeth small pulley, 48 teeth big one (less than 16 does not have enough belt wrap).
This will likely work reliably at around 100 (or could be even more) as you now have 300% more torque available.
Best,
h- On 18/02/2015 11:41, 'Andre Schoonbee' andresch@... [mach1mach2cnc] wrote: I did the tests a few times and the z-axis comes back to the correct zero position. This is after I have reduced the acceleration.
-- -hanermo (cnc designs)
|
|
This email has been checked for viruses by Avast antivirus software.
|
|
Great !
So, with the lower acceleration, the error does not appear, yes ?
Now, to confirm, put it back up to 100 again, and see if it now
appears.
If it does, with high confidence, you have encountered the problem.
To quickly localise the max practical acceleration, first make sure
you can reliably repeat the problem.
Then split the difference-
3-4 tests should get you very very close to the optimum number.
Ie, if at 100 it fails, and at 10 it does not (diff 90);
Try 10+45 = 55.
Errors, try 10+45/2 = 32.
No error, try 55+45/2 = 77.
And so on..
If you want more acceleration and better results, use HTD pulleys, 5
mm profile, 15 mm wide, at 1:3.
16 teeth small pulley, 48 teeth big one (less than 16 does not have
enough belt wrap).
This will likely work reliably at around 100 (or could be even more)
as you now have 300% more torque available.
Best,
h-
On 18/02/2015 11:41, 'Andre Schoonbee'
andresch@... [mach1mach2cnc] wrote:
I
did the tests a few times and the z-axis comes back to the
correct zero position. This is after I have reduced the
acceleration.
--
-hanermo (cnc designs)
|
I did the tests a few times and the z-axis comes back to the correct zero position. This is after I have reduced the acceleration. ?
toggle quoted message
Show quoted text
From: mach1mach2cnc@... [mailto:mach1mach2cnc@...]
Sent: 17 February 2015 02:41 PM
To: mach1mach2cnc@...
Subject: Re: [mach1mach2cnc] Support? ? >>The same code I tested 2x and worked fine. Then on tool change it start to
>>hit the z-limit switch again
This is almost textbook for a system with Z axis trouble. When the axis
drives into the material, it struggles and steps get lost, this causes a
most
annoying and confounding type of problem, in the air all is fine, in
material you hit the Z upper limit switch over time.
The test for this is simple, run a program that drives the Z up and down
several times and moves in the X after each Z up and down. Run this in the
air 10 times, then see if Z has lost anything. Then run it in material 10
times, where the Z has to cut the material on each downward plunge. How
often out of 10 times is it out of position in the Z at end of program?
If the AIR run is clean, and the material run is not.. you have a problem
with your Z.. Sometimes its the speed is too high on the retract, meaning
your Z tuning is set too high. ( Personally, when seeing this type of
problem my first move is to lower the Z max tuning speed by 50% as a test.
If that doesnt fix
it I then turn down the Z plunge rate in the GCode by 50% to see if that
fixes it.. I rarely get further than those two tests before the issue shows
itself.
If GCode runs properly in the air... and doesnt in material, the problem
in 95% of cases is the machine, not the GCode or Mach3. Ive seen this
error literally thousands of times over the years, the problem....and its
ensuing frustration remains the same. :) , Mach3 still has many bugs, most
known, but it runs the same from run to run in 99.999% of cases.. so in your
case, Im betting on a mechanical / tuning issue...
Thanks,
Art
----- Original Message -----
From: charles Fellows cfellows49@... [mach1mach2cnc]
To: mach1mach2cnc@...
Sent: Tuesday, February 17, 2015 8:17 AM
Subject: Re: [mach1mach2cnc] Support
Andre,
I am sorry you are still having problems. It appears your issue is tied to
tool height compensation. I suggest you experiment with limited code until
it is worked out. When I was learning I used a cardboard box as my table
height so I could change tools and have time to hit E-stop before I struck
the bed if something was wrong.
I have observed in your discussions you include diameters. I suggest until
you work this out you forget diameters and only pay attention to lengths.
The easiest way to have the problem you are describing would be to be using
the offsets screen incorrectly. Are you using the offsets screen at any
time?
I have an hour or so if you are available now. Please describe how you have
determined tool length, how you have set your lengths into the tool table,
and how you have numbered your tools.
Charlie.
On Tue, Feb 17, 2015 at 6:59 AM, 'Andre Schoonbee' andresch@...
[mach1mach2cnc] <mach1mach2cnc@...> wrote:
I do not know if I am allowed to post a RFQ/RFP on this forum but, I am at
the end of the line – for some reason Mach is working on my nerves and seems
to get a kick out of it.
When using Vectric Aspire and generate code it works perfect.
But then with the help of the guys form Cabinet Vision, the code is acting
weird. This yesterday and this morning, O was doing a test run of g-code and
it worked fine, it sliced the air like butter – each line executed perfect.
I then restarted my machine again to make sure no memory or setting issue
can creep in to cause a problem and started the real cut of a MDF sheet -
cutting a 4 drawer floor cabinet. The same code I tested 2x and worked fine.
Then on tool change it start to hit the z-limit switch again.
I need someone that know mach well and also can detect why the g-code is
causing this. This person should preferably be willing to do remote support.
To make sure there is no setting error om my machine, give advice in the
steps I follow, maybe provide customized scripts if needed, and then most
important, help me to identify why the code on mach3 works and then all of a
sudden does not work without anything changed.
This is really urgent
This email has been checked for viruses by Avast antivirus software.
|
|
This email has been checked for viruses by Avast antivirus software.
|
|
Well let me explain what I do. ? Remember my machine is using a manual tool change, so every time I execute M6, it will go to the tool change position, I insert the new tool. Then I press OK. The cnc then measure the tool and then continue the cut. ? I noted an error occurred in in the tool change in that the Z-limit switch was triggered. I then stopped the code. I restarted the cnc and mach3? to make sure all memory is clear. I then load the same code, click on edit and change the tool nr. Follow the same steps for setting my work Coordinates and start the code. ? Hope this explain a bit more. But please – I am very, very green when it comes to CNC, Mach3 and g-code so at no point am I to be quoted as expert or knowledgeable. Is just an explanation of my steps of what I did. ?
toggle quoted message
Show quoted text
From: mach1mach2cnc@... [mailto:mach1mach2cnc@...]
Sent: 17 February 2015 09:01 PM
To: mach1mach2cnc@...
Subject: Re: [mach1mach2cnc] Support? ? I didn't know you could do that. I've learnt something.? If you change tool number (length dia etc) wouldn't you have to change the rest of the code or you'll be cutting over or under size.? I confess, I'm not sure what your doing. I'm off home so I hope you see some light tomorrow. Setting accel and velocity is specific to your machine, Just zip an axis back and forth until you get a feel for it then back off a little when you get them both at a max.? I'm just repeating what Art said.? You were asking what numbers should I use today.. not sure it's fully sunk in.? Good luck, you'll get it.
I am editing the code in Mach ? ? ? When you say 'manually change the code to use tool 2' What are you actually doing?? Are you re-writing the code in your CAM software or changing a Mach DRO? or...? Missing a step I understand. But what does the tool radius have to do with this. See, if I have the diameters for 2 tools defined in my tool table. And I execute the code using first tool and it fails, I then manually change the code to use tool 2, and then rerun the code. Then it works. This I cannot understand.
?
| This email has been checked for viruses by Avast antivirus software.
|
?
|
|
This email has been checked for viruses by Avast antivirus software.
|
|
I assume you mean Parallel Port? _ Yes I am. ?
toggle quoted message
Show quoted text
From: mach1mach2cnc@... [mailto:mach1mach2cnc@...]
Sent: 17 February 2015 09:15 PM
To: mach1mach2cnc@...
Subject: Re: [mach1mach2cnc] Support? ? This is, by far, the best method.
The most important thing in troubleshooting is to only change one thing at a time.
And, if you think you have discovered simething important, go back and verify it really was what you thought it was.
Otherwise, errors caused by something that is not steady, like inductive noise, intermittent or poor connections can lead you on a long, unnecessary dance.
Or plugins errors.
USB errors.
Poor plugins.(Sw problem).
Poor home switches.
Poor index switch re: threading (very common). Its hard to make good index switches.
Also, depending on motion control hw the machines work differently.
Sometimes its determinant and important.
Are you using the PP ? On 17/02/2015 19:11, 'Andre Schoonbee' andresch@... [mach1mach2cnc] wrote: Never the less, I need to make sure I am not missing any step in the first place. So lets’ eat this elephant one bite at a time then.
-- -hanermo (cnc designs)
|
|
This email has been checked for viruses by Avast antivirus software.
|
|
Re: Where do I find the extra 0.0003"
Adam wrote: """ What is the steps per inch in Mach3? If your less then 10k you could be at
the limit of one step.
""" yep, that's probably it... belt drive only requires 2224 steps per inch... I'm sure when I switch that to a ballscrew drive things will be much different. ?Thanks, I'll stop worrying about that pesky 0.0003.
|
Re: Where do I find the extra 0.0003"
I can buy (and live with) a rounding error. ?I'm not about to start diddling the screen at this point, I'm still a babe-in-the-woods with most of this stuff, so if it ain't broke bad enough to actually demand fixing it ain't getting fixed. ?Thanks for the heads up.
|
Re: Where do I find the extra 0.0003"
What is the steps per inch in Mach3? If your less then 10k you could be at
the limit of one step.
In MachScreen (
)
you can open the 1024 screenset file, select the Z DRO and change the
format to include more decimal places.
Hope this helps!
[image: Inline image 1]
*-Adam Brunette*_
|
Re: Where do I find the extra 0.0003"
Could maybe be roundoff. Its small enough.
What the DROs state is not exact .. they are a truncation (? or rounded ) from the internal representation, that was something very accurate.
32 digits maybe or 30 decimals ?
Brian ? Art ?
If it works correctly, and always repeats to the same number, its likely related to inch/metric/internal representation issues, ime.
You could maybe test by modifying the screen, and adding digits.
I remember its doable, not sure if its wortwhile.
I looked at this maybe 5 years back..
toggle quoted message
Show quoted text
On 17/02/2015 20:09, marv@... [mach1mach2cnc] wrote: Any ideas??
--
-hanermo (cnc designs)
|
This is, by far, the best method.
The most important thing in troubleshooting is to only change one
thing at a time.
And, if you think you have discovered simething important, go back
and verify it really was what you thought it was.
Otherwise, errors caused by something that is not steady, like
inductive noise, intermittent or poor connections can lead you on a
long, unnecessary dance.
Or plugins errors.
USB errors.
Poor plugins.(Sw problem).
Poor home switches.
Poor index switch re: threading (very common). Its hard to make good
index switches.
Also, depending on motion control hw the machines work differently.
Sometimes its determinant and important.
Are you using the PP ?
On 17/02/2015 19:11, 'Andre Schoonbee'
andresch@... [mach1mach2cnc] wrote:
Never
the less, I need to make sure I am not missing any step in the
first place. So lets’ eat this elephant one bite at a time then.
--
-hanermo (cnc designs)
|
Where do I find the extra 0.0003"
Here's one for you.... the following script is called with the "Auto Zero Tool" button:
""" CurrentFeed = GetOemDRO(818) 'Get the current feedrate to return to later CurrentAbsInc = GetOemLED(48) 'Get the current G90/G91 state CurrentGmode = GetOemDRO(819) 'Get the current G0/G1 state
If GetOemLed (825)=0 Then 'Check to see if the probe is already grounded or faulty DoOEMButton (1010) 'zero the Z axis so the probe move will start from here Code "G4 P3" ' this delay gives me time to get from computer to hold probe in place Code "G90 G31Z-3. F4" 'probing move, can set the feed rate here as well as how far to move While IsMoving() 'wait while it happens Wend ZProbePos = GetVar(2002) 'get the exact point the probe was hit Code "G0 Z" &ZProbePos 'go back to that point, always a very small amount of overrun While IsMoving () Wend Call SetDro (2, .090) ' change .060 to your plate thickness and then adjust for final accuracy Sleep 200 'Pause for Dro to update. Code "G1 Z1.000 F50" 'put the Z retract height you want here, must be greater than the touch plate thickness While IsMoving () Wend Code "(Z axis is now zeroed)" 'puts this message in the status bar Code "F" &CurrentFeed 'Returns to prior feed rate Else Code "(Z-Plate is grounded, check connection and try again)" 'this goes in the status bar if applicable End If If CurrentAbsInc = 0 Then 'if G91 was in effect before then return to it Code "G91" End If If CurrentGMode = 0 Then 'if G0 was in effect before then return to it Code "G0" End If ?? """
It runs exactly as expected... Z-axis sneaks down to my touch plate, signals zero and retracts to one inch above the touched surface. ?However, at the end of the process my Z-axis DRO always reads 1.0003, not 1.0000. ?I have no idea where that extra 3-tenths is coming from... not that it matters a whit for the kind of machining I'm doing, but it bugs me that it doesn't match what's called for in the script. ?The application is controlling steppers on a Zenbot with the standard breakout board that came with the unit. ?Any ideas??
|
I didn't know you could do that. I've learnt something.? If you change
tool number (length dia etc) wouldn't you have to change the rest of the code or
you'll be cutting over or under size.? I confess, I'm not sure what your
doing. I'm off home so I hope you see some light tomorrow.
?
Setting accel and velocity is specific to your machine, Just zip an axis
back and forth until you get a feel for it then back off a little when you get
them both at a max.? I'm just repeating what Art said.? You were
asking what numbers should I use today.. not sure it's fully sunk in.? Good
luck, you'll get it.
?
?
In a message dated 17/02/2015 18:37:47 GMT Standard Time,
mach1mach2cnc@... writes:
toggle quoted message
Show quoted text
I
am editing the code in Mach
?
From:
mach1mach2cnc@... [mailto:mach1mach2cnc@...]
Sent: 17 February 2015 08:31 PM
To:
mach1mach2cnc@...
Subject: Re: [mach1mach2cnc]
Support
?
?
When
you say 'manually change the code to use tool 2' What are you actually
doing?? Are you re-writing the code in your CAM software or changing a
Mach DRO? or...?
Missing a step I understand. But
what does the tool radius have to do with this. See, if I have the diameters
for 2 tools defined in my tool table. And I execute the code using first
tool and it fails, I then manually change the code to use tool 2, and then
rerun the code. Then it works. This I cannot understand.
|
This
email has been checked for viruses by Avast antivirus software.
|
|
I am editing the code in Mach ?
toggle quoted message
Show quoted text
From: mach1mach2cnc@... [mailto:mach1mach2cnc@...]
Sent: 17 February 2015 08:31 PM
To: mach1mach2cnc@...
Subject: Re: [mach1mach2cnc] Support? ? When you say 'manually change the code to use tool 2' What are you actually doing?? Are you re-writing the code in your CAM software or changing a Mach DRO? or...? Missing a step I understand. But what does the tool radius have to do with this. See, if I have the diameters for 2 tools defined in my tool table. And I execute the code using first tool and it fails, I then manually change the code to use tool 2, and then rerun the code. Then it works. This I cannot understand.
|
|
This email has been checked for viruses by Avast antivirus software.
|
|
When you say 'manually change the code to use tool 2' What are you actually
doing?? Are you re-writing the code in your CAM software or changing a Mach
DRO? or...?
?
In a message dated 17/02/2015 18:11:44 GMT Standard Time,
mach1mach2cnc@... writes:
toggle quoted message
Show quoted text
Missing
a step I understand. But what does the tool radius have to do with this. See,
if I have the diameters for 2 tools defined in my tool table. And I execute
the code using first tool and it fails, I then manually change the code to use
tool 2, and then rerun the code. Then it works. This I cannot
understand.
|
I will run the few tests tomorrow morning and then give feedback ? As I mentioned, I use the Calipso MachStdMill screenset and on the tooling page you can zero the axes from a button. ? What I do is: I use the MDI to go to the position on all 3 axes Then I press the zero for each axis The WC is then changed to 0.0000 ? I also did reduce the acceleration of the z-axes to 21 as that is the lowest it will go. ? I admit, there is a lot I do not know about CNC, Mach and g-code, but if I understand why an error occur, then it is easier to find a problem. Missing a step I understand. But what does the tool radius have to do with this. See, if I have the diameters for 2 tools defined in my tool table. And I execute the code using first tool and it fails, I then manually change the code to use tool 2, and then rerun the code. Then it works. This I cannot understand. ? Never the less, I need to make sure I am not missing any step in the first place. So lets’ eat this elephant one bite at a time then. ?
toggle quoted message
Show quoted text
From: mach1mach2cnc@... [mailto:mach1mach2cnc@...]
Sent: 17 February 2015 06:46 PM
To: mach1mach2cnc@...
Subject: Re: [mach1mach2cnc] Support? ? Your statement that you changed Z heights to above the work and ran the code with no problems and always have problems with the next tool when cutting makes the scenario Art was describing fit.? To check if you are loosing steps, confirm your tool zero,?run the code using your first tool and stop (feed hold, then reset) near the end. Check to see if your tool zero for that first tool is still correct. If it is not, you are loosing steps.? Once this is confirmed we can discuss why. Just to be sure this is not a operation issue.? Are you setting zero by writing 0.0 into the MDI or are you using the settings page? ? On Tue, Feb 17, 2015 at 7:59 AM, 'Andre Schoonbee' andresch@... [mach1mach2cnc] <mach1mach2cnc@...> wrote: ? HI Charlie / Guys ? Well let start by giving specifics of my setup and work process. Then I will show some of the code ? My CNC is using a new PC with 4GBRAM and windows XP – dedicated to Mach3 only. My bed size is x=3m long, Y=2m and Z have total travel of 170mm I use a manual tool change spindle. ? My limit switches in on all 3 axes. And also on the extreme to make sure I do not try to over run any axes. ? My Z-Axis I home on top so I move in negative values. ? I always start the machine firs by starting the PC and mach3, then start the CNC control board and reset. Then I Reff all and make sure all axis are then zero. ? I also made sure that my Tool table is blank. ? I lately tried to use the Calypso MachStdMill screen set because the tool change sequence is great. ? On my table I have a fixed location for tool change with a fixed plate. The fixed plate is on Z=-167.454 (Measured to the gauge line of my spindle) ? I have a specific start position for my work and use this position as my work coordinate offset X=80.4310 Y=0.0000 Z=-95.0716 ( This offset is measured using my Master tool) I have a master tool that I know the length and always inert this tool first, touch it off and make sure the length is know. This tool is tool nr 200. With the tool length then measured, I then go to the offset position, enter the offset values and make double sure the offset is perfect. Then I zero all the axes. ? I always zero on top of my spoilboard. ? Then I start loading my code. ? Now getting to the code: I did run this code 2x at the same x and y coordinates, the Z coordinate were higher to make sure I do not cut any material. And both times it worked fine. Then I reset my axes and start the code to cut. And it start hitting the z-limit ? This error I have now for 3 weeks Previously, I had the tool diameters in the tool table. But then when I executed the code, it keep on hitting the z-limit switch on top. This happened for example with tool 1. I then changed the code only to use tool 2 and not the tool table. So in the tool table the tool diameters were still there. Then rerun the code and it worked. The same happened with tool 2. When I start the program with tool 2, it gave the same problem and then when I edit the gocde and change the tool to tool 3 it worked again. Then I removed all the tool settings in the tool table and tried all the codes again and first time all of them worked. ? One thing that I did notice as that the rapid clearance of my machine when executing the code is always going to Z-Zero position. ? Here is a few lines of the code that is giving me the problem. ? % O0001 N10 (PROGRAM PRODUCED? - 13 FEB 15) N20 G21 G90 (UNITS METRIC) N30 G40 G91.1 N40 T05 M06 G43 H05 N50 S12000 M03 N60 G0 X1038.7 Y267.206 N70 G98 G81 X1038.7 Y267.206 Z4. R21. F2000 N80 X1038.7 Y171.206 N90 X1038.7 Y43.206 N100 X1216.45 Y43.206 N110 X1216.45 Y171.206 N120 X1216.45 Y267.206 N130 X1411.7 Y267.206 N140 X1411.7 Y171.206 N150 X1411.7 Y43.206 N160 X1606.95 Y43.206 N170 X1606.95 Y171.206 N180 X1606.95 Y267.206 N190 X714.25 Y234.8 N200 X714.25 Y138.8 N210 X519. Y138.8 N220 X519. Y234.8 N230 X519. Y362.8 N240 X714.25 Y362.8 N250 X323.75 Y362.8 N260 X323.75 Y234.8 N270 X323.75 Y138.8 N280 X146. Y138.8 N290 X146. Y234.8 N300 X146. Y362.8 N310 G80 N320 T02 M06 G43 H02 N330 S12000 M03 N340 G0 X2289.5 Y472. N350 G98 G81 X2289.5 Y472. Z-0.1 R21. F2000 N360 X2142.8 Y472. N370 X1996.1 Y472. N380 X1849.4 Y472. ? ? ? ? I am sorry you are still having problems.? It appears your issue is tied to tool height compensation.? I suggest you experiment with limited code until it is worked out.? When I was learning I used a cardboard box as my table height so I could change tools and have time to hit E-stop before I struck the bed if something was wrong. I have observed in your discussions you include diameters.? I suggest until you work this out you forget diameters and only pay attention to lengths.? The easiest way to have the problem you are describing would be to be using the offsets screen incorrectly.? Are you using the offsets screen at any time? I have an hour or so if you are available now.? Please describe how you have determined tool length, how you have set your lengths into the tool table, and how you have numbered your tools. ? On Tue, Feb 17, 2015 at 6:59 AM, 'Andre Schoonbee' andresch@... [mach1mach2cnc] <mach1mach2cnc@...> wrote: ? I do not know if I am allowed to post a RFQ/RFP on this forum but, ?I am at the end of the line – for some reason Mach is working on my nerves and seems to get a kick out of it. ? When using Vectric Aspire and generate code it works perfect. ? But then with the help of the guys form Cabinet Vision, the code is acting weird. This yesterday and this morning, O was doing a test run of g-code and it worked fine, it sliced the air like butter – each line executed perfect. I then restarted my machine again to make sure no memory or setting issue can creep in to? cause a problem and started the real cut of a MDF sheet? - cutting a 4 drawer floor cabinet. The same code I tested 2x and worked fine. Then on tool change it start to hit the z-limit switch again. ? I need someone that know mach well and also can detect why the g-code is causing this. This person should preferably be willing to do remote support. To make sure there is no setting error om my machine, give advice in the steps I follow, maybe provide customized scripts if needed, and then most important, help me to identify why the code on mach3 works and then all of a sudden does not work without anything changed. ? This is really urgent ? ?
| This email has been checked for viruses by Avast antivirus software.
|
?
? ?
| This email has been checked for viruses by Avast antivirus software.
|
?
?
|
|
This email has been checked for viruses by Avast antivirus software.
|
|
Andre,
Your statement that you changed Z heights to above the work and ran the code with no problems and always have problems with the next tool when cutting makes the scenario Art was describing fit.? To check if you are loosing steps, confirm your tool zero,?run the code using your first tool and stop (feed hold, then reset) near the end. Check to see if your tool zero for that first tool is still correct. If it is not, you are loosing steps.? Once this is confirmed we can discuss why.
Just to be sure this is not a operation issue.? Are you setting zero by writing 0.0 into the MDI or are you using the settings page?
Charlie
On Tue, Feb 17, 2015 at 7:59 AM, 'Andre Schoonbee' andresch@... [mach1mach2cnc] <mach1mach2cnc@...> wrote:
?
HI Charlie / Guys ? Well let start by giving specifics of my setup and work process. Then I will show some of the code ? My CNC is using a new PC with 4GBRAM and windows XP – dedicated to Mach3 only. My bed size is x=3m long, Y=2m and Z have total travel of 170mm I use a manual tool change spindle. ? My limit switches in on all 3 axes. And also on the extreme to make sure I do not try to over run any axes. ? My Z-Axis I home on top so I move in negative values. ? I always start the machine firs by starting the PC and mach3, then start the CNC control board and reset. Then I Reff all and make sure all axis are then zero. ? I also made sure that my Tool table is blank. ? I lately tried to use the Calypso MachStdMill screen set because the tool change sequence is great. ? On my table I have a fixed location for tool change with a fixed plate. The fixed plate is on Z=-167.454 (Measured to the gauge line of my spindle) ? I have a specific start position for my work and use this position as my work coordinate offset X=80.4310 Y=0.0000 Z=-95.0716 ( This offset is measured using my Master tool) I have a master tool that I know the length and always inert this tool first, touch it off and make sure the length is know. This tool is tool nr 200. With the tool length then measured, I then go to the offset position, enter the offset values and make double sure the offset is perfect. Then I zero all the axes. ? I always zero on top of my spoilboard. ? Then I start loading my code. ? Now getting to the code: I did run this code 2x at the same x and y coordinates, the Z coordinate were higher to make sure I do not cut any material. And both times it worked fine. Then I reset my axes and start the code to cut. And it start hitting the z-limit ? This error I have now for 3 weeks Previously, I had the tool diameters in the tool table. But then when I executed the code, it keep on hitting the z-limit switch on top. This happened for example with tool 1. I then changed the code only to use tool 2 and not the tool table. So in the tool table the tool diameters were still there. Then rerun the code and it worked. The same happened with tool 2. When I start the program with tool 2, it gave the same problem and then when I edit the gocde and change the tool to tool 3 it worked again. Then I removed all the tool settings in the tool table and tried all the codes again and first time all of them worked. ? One thing that I did notice as that the rapid clearance of my machine when executing the code is always going to Z-Zero position. ? Here is a few lines of the code that is giving me the problem. ? % O0001 N10 (PROGRAM PRODUCED? - 13 FEB 15) N20 G21 G90 (UNITS METRIC) N30 G40 G91.1 N40 T05 M06 G43 H05 N50 S12000 M03 N60 G0 X1038.7 Y267.206 N70 G98 G81 X1038.7 Y267.206 Z4. R21. F2000 N80 X1038.7 Y171.206 N90 X1038.7 Y43.206 N100 X1216.45 Y43.206 N110 X1216.45 Y171.206 N120 X1216.45 Y267.206 N130 X1411.7 Y267.206 N140 X1411.7 Y171.206 N150 X1411.7 Y43.206 N160 X1606.95 Y43.206 N170 X1606.95 Y171.206 N180 X1606.95 Y267.206 N190 X714.25 Y234.8 N200 X714.25 Y138.8 N210 X519. Y138.8 N220 X519. Y234.8 N230 X519. Y362.8 N240 X714.25 Y362.8 N250 X323.75 Y362.8 N260 X323.75 Y234.8 N270 X323.75 Y138.8 N280 X146. Y138.8 N290 X146. Y234.8 N300 X146. Y362.8 N310 G80 N320 T02 M06 G43 H02 N330 S12000 M03 N340 G0 X2289.5 Y472. N350 G98 G81 X2289.5 Y472. Z-0.1 R21. F2000 N360 X2142.8 Y472. N370 X1996.1 Y472. N380 X1849.4 Y472. ? ? ? ? I am sorry you are still having problems.? It appears your issue is tied to tool height compensation.? I suggest you experiment with limited code until it is worked out.? When I was learning I used a cardboard box as my table height so I could change tools and have time to hit E-stop before I struck the bed if something was wrong. I have observed in your discussions you include diameters.? I suggest until you work this out you forget diameters and only pay attention to lengths.? The easiest way to have the problem you are describing would be to be using the offsets screen incorrectly.? Are you using the offsets screen at any time? I have an hour or so if you are available now.? Please describe how you have determined tool length, how you have set your lengths into the tool table, and how you have numbered your tools. ? On Tue, Feb 17, 2015 at 6:59 AM, 'Andre Schoonbee' andresch@... [mach1mach2cnc] <mach1mach2cnc@...> wrote: ? I do not know if I am allowed to post a RFQ/RFP on this forum but, ?I am at the end of the line – for some reason Mach is working on my nerves and seems to get a kick out of it. ? When using Vectric Aspire and generate code it works perfect. ? But then with the help of the guys form Cabinet Vision, the code is acting weird. This yesterday and this morning, O was doing a test run of g-code and it worked fine, it sliced the air like butter – each line executed perfect. I then restarted my machine again to make sure no memory or setting issue can creep in to? cause a problem and started the real cut of a MDF sheet? - cutting a 4 drawer floor cabinet. The same code I tested 2x and worked fine. Then on tool change it start to hit the z-limit switch again. ? I need someone that know mach well and also can detect why the g-code is causing this. This person should preferably be willing to do remote support. To make sure there is no setting error om my machine, give advice in the steps I follow, maybe provide customized scripts if needed, and then most important, help me to identify why the code on mach3 works and then all of a sudden does not work without anything changed. ? This is really urgent ? ?
| This email has been checked for viruses by Avast antivirus software.
|
?
?
|
|
This email has been checked for viruses by Avast antivirus software.
|
|
Hi ? Yes. This way the zero position is always a fixed position and is just easier for me. I found that sometimes when zeroing on top of the material, the board tends to bend on the corners sometimes, resulting in me not having a clear cut all through the entire board. ?
toggle quoted message
Show quoted text
From: mach1mach2cnc@... [mailto:mach1mach2cnc@...]
Sent: 17 February 2015 06:19 PM
To: mach1mach2cnc@...
Subject: Re: [mach1mach2cnc] Support? ? I was reading your set up and one thing that caught my attention is you are zeroing your Z to the table, is Vectric material set up with Z- zero at the bottom of your material?
? ? ? Go back and see my post from earlier, and the one from Charles. I'm pretty sure the G43 is causing your issues.
From: "'Andre Schoonbee' andresch@... [mach1mach2cnc]" <mach1mach2cnc@...>
To: mach1mach2cnc@...
Sent: Tuesday, February 17, 2015 10:13:02 AM
Subject: RE: [mach1mach2cnc] Support ? Di I understand you correctly? If torque is 100 then acceleration is 300? This is a very good system. ( I would drive the z axis at 1:3, for more 300% torque = acceleration.)
Try Arts test at the lower acceleration, and let us know. It will likely make a difference, or lead to clues on where the problem is. On 17/02/2015 15:04, 'Andre Schoonbee' andresch@... [mach1mach2cnc] wrote: In the control box I have 4 x Gecko G203V Stepper drive units 34HSX-104D Stepper motor (2 x motors for X-Axis, 1 X motor on Y-Axis) 23HSX-102D Stepper motor (Z-Axis) 20mm Linear Guides and 20mm Linear Blocks 20 x10mm Ball Screw and 20 x10mm Ball Nut 15mm Linear Guides and 15mm Linear Blocks 12x4 Ball Screw with 12x4 Ball nut 15mm Linear Guides and 15mm Linear Blocks What motors are you using;
Ie what is your motion-control train ? Steppers ? Drivers ? Volts ? Belts or couplers ? Breakout board ? Do you only have 86.x steps / mm on x ? On 17/02/2015 14:31, 'Andre Schoonbee' andresch@... [mach1mach2cnc] wrote: My Motor Tuning settings for all my axes as the following – starting with the Z-Axis: Z-Axis:? Steps per = 494.0698539 ??????????????? Velocity mm’s per min = 5191.0 ??????????????? Acceleration = 100 X-Axis:? Steps per = 86.95652174 ??????????????? Velocity mm’s per min = 8328 ??????????????? Acceleration = 306.1875 Y-Axis:? Steps per = 200.3234631 ??????????????? Velocity mm’s per min = 6228 ??????????????? Acceleration = 157.15116
? -- -hanermo (cnc designs)
| This email has been checked for viruses by Avast antivirus software.
|
-- -hanermo (cnc designs) ?
| This email has been checked for viruses by Avast antivirus software.
|
?
|
|
This email has been checked for viruses by Avast antivirus software.
|
|
