Messages

5461

General Mach Discussion / Re: G31 Probe problem

« on: August 02, 2011, 11:24:00 PM »

Set up the switch as the Z home in Config/ Ports_pins/inputs. Test it by tripping the switch and looking on the diag page to see IF the Zhome led comes on.

 You will need to set up Zhome in Config Homing to setup the correct Zhome direction AND speed. The speed is based on a % of rapid of the Z. MAKE sure there is no offset value for Z home and make sure that the AUTO Zero is checked on.

Check to make sure the function work testing them in the air first as you go. Making sure that the Zhome is going in the right direction(;-)That way there should NOT be any surprises when you start/test the routine.

The motion is as follows. The G28.1 will go to the midpoint as defined by the Call G28.1 Z.500 this is normally a safe position in plasma. Next it will start the home routine and move to the Zhome switch. When it trips it comes to a controlled stop then reverses UNTIL the switch resets(makes contact). Then the Z dro is reset to ZERO ( or the correction value). Next the Z rapids UP to the pierce height and fires the torch. Then the pierce dwell takes place and the torch lowers to cut height and away you go.

IF the switch stays tripped after the routine then then your else statement will take you to the end and post the message to the error bar


NOTE: I would test it first from the CB CODE editor stepping 1 line at a time (F7) to ensure it does what is needed and does work(;-)



This macro should be very close to the same function as your G31 setup. You will notice that the Z will FIRST go to Z.500 on its way to home that is a safety of sorts that we use. the idea is that the Z.500 should be a safe point to start the routine above the Material. IF the torch is below that point it raises first if above it lowers to that point first. You can use it OR not your choice.


PierceHeight = GetUserDRO(1000)
CutHeight = GetUserDRO(1001)
PierceTime = GetUserDRO(1002)

If GetOEMLed(836) = 0 Then    ' Checks the Home LED if active then goto else
Code "G28.1 Z.500"   ' Set up the Zhome for the correct direction and speed
While IsMoving()
Wend
Code"G92 Z0.000"   ' Set the Z value +/- to insure the pierce height comes out correct
                                 ' The correct value depends on the lost motion of the switch assy
Code"G0 Z" &PierceHeight
While IsMoving()
Wend

DoSpinCW()
While Not isActive(Input1)
Wend
Code "G4 P" &PierceTime 'Pierce Delay
Code "G0 Z" & GetUserDRO(1001)
While IsMoving()
Wend

Else
Code "(Torch is On Surface Hit STOP and Fix)"
End If


Hope that helps, (;-) TP

                                      

5462

General Mach Discussion / Re: G31 Probe problem

« on: August 02, 2011, 10:42:26 PM »

If you listen to the vid carefully you can HEAR the difference in the G31 and the G0(;-)

If you would like to try the G28.1 in the macro let us know and we can help you if you need it.

(;-) TP

5463

General Mach Discussion / Re: G31 Probe problem

« on: August 02, 2011, 10:26:19 PM »

OK what are the acell values for the X and Y (;-) just in case.

Try this as a test. lift the head up to the top. Reset Zero Then do a fast Down and stop with G1

G1 X-3 F150 (Do not let it hit the table)

See IF the slowdown at the end is quick

Next do the same with a G31 Z-3 F150 (do not trip the switch)

See if the slowdown at the end is the same as the G1.

Next do the G31 again only this time trip the switch on the way down and look at the deacell rate.

Next try it with G0 Z-3.

Somehwere inside the testing should be the answer hopefully.

(;-)TP

5464

Feature Requests / Re: conditional execution

« on: August 02, 2011, 08:58:21 PM »

(;-) Thankfully the NIST RS274 is not the STANDARD it is but a reference. There are many dialects of gcode and many good reasons for it.

Unfortunatly Mach3 is about the only one that does not support condition Gcode in one form or the other.

Mach3 does a very good job for what it is.  I believe its original design was for the hobby world where exoctic parametric conditional Gcode was a rarity not the norm.  Being that Mach3 is a buffered system it may have took a great hit in performance to have it do condition Gcode. Mach3 stacks the moves into the que buffer and then runs them as continous moves. Interrupting that stream to do condition correction would have been asking a lot from Mach3 under windows AND have a fast and accurate system.

Along with Mach3's push in the hobby market came more low cost Cam systems that petty much circumvented the basic need for condition Gcode in this market.

Just my opinion on this one, (;-) TP

5465

General Mach Discussion / Re: G31 Probe problem

« on: August 02, 2011, 07:42:01 PM »

On a side note(;-)   This brings up one of the reasons that many choose to use the G28.1 method to find the TOM (top of material). The G28.1 cycle stops on contact THEN backs up to reset the switch. This takes out the overun, loss motion, switch travel and material flex variables. When the cycle stops you are at the TOM all that is needed is to Set Z, move to pierce hieght and go.

The G28.1 speed is also presettable in config as a percentage of Rapid.

What you do loose with it is the ability to use the G68 to do coord rotation as the G28.1 will NOT run in coord space. AND it does NOT error out, it just hops over it and continues the Gcode  (that needs fixin to allow Z to home in G68)

Just a thought, (;-) TP

5466

General Mach Discussion / Re: G31 Probe problem

« on: August 02, 2011, 07:23:22 PM »

What are the motor settings accell/vel  and what is the turns per inch on your feedscrew for the Z?

  It looks and sounds like you are combatting inertial overrun and having to run slow accel rates to avoid loosing steps. Common with useing High speed stepper values to make axis speed.

As Stirling noted The Macro needs a few more checks / wait points in order to insure it stays in sync. NOTE:Some machines require it some get away with out it. It all depends.


AS a reference(;-)

In the Gcode side all that is replaced with

G31 Z-5 F20
G92 Z0
G0Z.080
G92 Z0
G0Z.100

M3
G4 P1

And is only run after the machine has moved a predeteremend amount of travel. Not at every piercing.

To do what you do it would look similar to this and there is NO CB involved in the motion code. The macropump will keep the #vars up to date with your DRO entries.


G31 Z-5 F20
G92 Z0
G0Z#500
G92 Z0
G0 Z#501

M3
G4 P#502

5467

General Mach Discussion / Re: Missed Features

« on: August 02, 2011, 09:47:50 AM »

Yep I agree with Tweaky. It is not always advantages to upgrade. I have one last machine on MACH3 and I am holding way back in versions as it is the most stable and predicatable.

But to the subject line, THAT is the price you pay when you use a custom screen set and the Author does NOT do the maintance to keep it up to data for the newer versions.

OR he is HOLDING at that version because he KNOWS it works and the newer version may not work as well.

Take your pick, (;-) TP

5468

General Mach Discussion / Re: can mach3 support brake at any time any position for A axis or B axis?

« on: August 02, 2011, 09:40:42 AM »

Along with what Hood said you could do it in the macropump as an automatic function. You monitor the A/B axis and if it is NOT ismoving then apply the brake.

But be aware there is a latency in doing it that way. It take times for the brake system to respond and it could effect the motor pulling against the brake for a fraction of a sec. It may be a problem or may not be a problem. Further testing would prove it out.

(;-) TP

5469

General Mach Discussion / Re: Spindle turning off during cycle

« on: August 01, 2011, 07:38:24 PM »

That sounds like a spindle control problem. Possibly a bad port pin, Bad BOB(opto), bad wire, connection or bad holding relay. To test to see IF it is mach3 doing it when it happens you need to check the port pin that control the spindle "on" and see IF it is still active. If it is then it is not mach3 or the PC. Check the spindle control downline of the PC.

Some BOBs have leds that show the port as active that would be an easy check. When it fails check the LEDs before you restart the spindle

Hope that helps, (;-) TP

5470

General Mach Discussion / Re: GCodes and editing files

« on: August 01, 2011, 06:01:27 PM »

(;-) Thank You

1.  Do you want to access the Mode message line OR do you want to see the reference of what the gcodes do?  I don' think you can access the Mode line and you can see the Gcode references ON SCREEN by pressing the Gcode button lower left hand side of the main page(program Run)

2.  You need to look at the download page and read the updates section to see what and when things were done to the versions. That way you get fresh info.

3. You cannot edit the Machine coord base the only thing you can do to it is Reset it to zero based on your current position(not recommended)

4. You edit the table and tool offsets in the Tool table and the Fixture offset tables in CONFIG  OR through Gcode calls. You can also modify the CURRENT Fixture offset from the offsets page.

Hope that helps, (;-)TP