Hello Guest it is March 28, 2024, 12:46:55 PM

Author Topic: Probably simple but...(G-Code help)  (Read 24695 times)

0 Members and 1 Guest are viewing this topic.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Probably simple but...(G-Code help)
« Reply #40 on: January 12, 2016, 01:48:27 PM »
Brain attached :)

As for the logic, I'm even more confused :) Would be great if there was a way of seeing the actual values.

Offline BR549

*
  •  6,965 6,965
    • View Profile
Re: Probably simple but...(G-Code help)
« Reply #41 on: January 12, 2016, 02:22:32 PM »
Try this brain

(;-)

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Probably simple but...(G-Code help)
« Reply #42 on: January 12, 2016, 03:15:11 PM »
Still studying this ;)

Here is a lump of my code, pretty similar to yours...

N0360 M01 (Paused: Hit RUN to continue)
N0370 X70.475 Y33.450
N0380 M08 (Turn on extract fan)
N0390 M98 (HeightSense.tap)
N0400 G00 Z3.8000
N0410 M03
o549
N0420 X70.4750 Y33.4496
N0430 G01 Z1.500 F1300.0
N0440 S20 (DTHC is ON)
N0450 G01 X66.475 F4100.0

So we jump in at o549 but does theG01 Z... line following not cause issues if a TOM setting has not been done - the Z could be anywhere and will try and reach 1.5

Offline BR549

*
  •  6,965 6,965
    • View Profile
Re: Probably simple but...(G-Code help)
« Reply #43 on: January 12, 2016, 04:43:49 PM »
OK now it is up to you. First you would have set the Prgram origin X0Y0 like you would for any cut. Then simply set teh Z0 to above the work I set it for about 1 inch above the surface.  That way you are well clear of the material and the Z will only raise to 1.5 above that.

(;-) TP

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Probably simple but...(G-Code help)
« Reply #44 on: January 12, 2016, 04:56:24 PM »
Fair enough, hopefully the modded brain will work and that will be it sorted :)

I always tend to try and program machinery and software at work with the proviso that if it can happen it will - like pressing dry run without setting the Z to a safe height first, that was my reasoning for asking, I am slowly learning that Mach and the intricacies of g-code does not play as well as a PLC or software :)

Never hurts to try though;)

Offline BR549

*
  •  6,965 6,965
    • View Profile
Re: Probably simple but...(G-Code help)
« Reply #45 on: January 12, 2016, 05:11:07 PM »
Now there is nothing stopping you from coding in what you want it to do (;-)  BUT for the most part you are just replicating processes that you have already done. I alway set teh point of origin for teh program and z about 1 inch hight to start a program run  . It then rapids down to teh reference point of .5 ( G28.1 Z.5) then runs the ref home routine.   So really there is no lost time or motion and safety is built in.

For the most part Gcode is a very simple motion language. It is like talking to a 3 years old. For the most part there is NO logic involved for normal cutting. Simply motion commands.

(;-) TP

(;-) TP

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Probably simple but...(G-Code help)
« Reply #46 on: January 13, 2016, 02:19:26 AM »
So do you set your Z at 1" and zero it or does the DRO show 1"

My Z is generally parked at 15mm at the end of every code run as that is more thickness than any metal i would likely ever run so no chance of dumping a thick plate on and running the torch into it ;)

My probe is G28.1 Z5.00 but I never get any slowdown or thats what it seems like, not sure why.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Probably simple but...(G-Code help)
« Reply #47 on: January 13, 2016, 04:27:22 AM »
Also....

If you have a sheet cam job where you have duplicated and nested the parts, you get multiple o549 entries, I gather this will fail when loaded into Mach3??

Obviously on a nested job like this you would not really want to do a dry run, BUT will Mach load the file with repeated subroutine headers with the same name??

Seems like there really is no easy option when it comes to dry-runs?

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Probably simple but...(G-Code help)
« Reply #48 on: January 13, 2016, 04:48:41 AM »
Try this brain

(;-)

Sorry, didn't work.

I have installed the front-end of Mach3 on my laptop (no lpt driver) so i can mess about with it, I can load a code file and you can clearly see the Output3 LED flashing on and off as the code loads/triggers the output.

Some sort of brain logic failure here?

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Probably simple but...(G-Code help)
« Reply #49 on: January 13, 2016, 04:52:04 AM »
Also....

If you have a sheet cam job where you have duplicated and nested the parts, you get multiple o549 entries, I gather this will fail when loaded into Mach3??

Obviously on a nested job like this you would not really want to do a dry run, BUT will Mach load the file with repeated subroutine headers with the same name??

Seems like there really is no easy option when it comes to dry-runs?

Reply edit time-out is too short!

Not only does Mach accept the multiple sub headers but when you call it, it only runs the last block - pretty smart. :)