Hello Guest it is March 28, 2024, 02:13:37 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Davek0974

2121
General Mach Discussion / Re: Probably simple but...(G-Code help)
« 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?

2122
General Mach Discussion / Re: Probably simple but...(G-Code help)
« 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?

2123
General Mach Discussion / Re: Probably simple but...(G-Code help)
« 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.

2124
General Mach Discussion / Re: Probably simple but...(G-Code help)
« 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;)

2125
General Mach Discussion / Re: Probably simple but...(G-Code help)
« 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

2126
Brains Development / Re: Logic failure, help please
« on: January 12, 2016, 02:30:45 PM »
Ok, thanks, got it.

2127
General Mach Discussion / Re: Probably simple but...(G-Code help)
« 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.

2128
Brains Development / Logic failure, help please
« on: January 12, 2016, 01:24:00 PM »
I have a #var being set to 1 or 0 via G-code.

I have a brain that switches an output IF two conditions are met -

The #var being = 1 AND the RUN(804) LED being on i.e. we are running code.

However the logic fails as the output is triggered when I load a g-code file OR when doing a path regeneration.


Any reason why this should fail and is there a way to make it work??

2129
General Mach Discussion / Re: Probably simple but...(G-Code help)
« on: January 12, 2016, 01:20:40 PM »
isloading will not go in a brain AFIK, I have no macros, just g-code triggering a #var and brain monitoring it and switching an output IF two values are met - the #var being=1 AND the RUN led being on.

Unfortunately it does not work for some unknown reason, it defies logic which makes it all a nonsense.

2130
General Mach Discussion / Re: Probably simple but...(G-Code help)
« on: January 12, 2016, 12:51:01 PM »
Yes, that would work, i'm not so old-school and tend to go with the software ;)

I have the code in the files now, is this all that goes in the Mach screen button -
Code"M98 P549"
End

Also, back with my control logic....

I tried ANDing the trigger variable from the subroutine with the RUN led - this works fine when you run code, BUT when you load a file or do a regen it STILL triggers the probe - this seems to indicate the logic does not work as the RUN led is most definitely off when loading code.

Any ideas how i can brain logic this into working????