Framing set origen

phillc54 wrote:

You need to be out of estop, power on and torch enabled. It does work here on my table at this very moment.

Silly me of course you need to enable the torch!
I had dunked the torch while testing and the first pulse was all water and no sparks so it has a purpose!

phillc54 wrote:

We could probably look at this as a user button function.

[/quote]

Yeh, Thats what I had in mind. Would be a way cool feature!

For activate pulse button first activate torch on. 

Just thinking out loud.
Add to the load last button Load next button with an archive option
I'll have to think about it a bit more but say the machine has an operator on it and design sends a heap of jobs to it during the last shift. 
I'm thinking of some way to allow the operator to work through the list

Actually scratch all that and just add a run python option and let the user set it up how he likes.
That would be cool.....

So let a run-python button receive a parameter for the current file name and a method to load a new file into QTP

You'll be pleased to know I'm running out of ideas......

rodw wrote:

So let a run-python button receive a parameter for the current file name and a method to load a new file into QTP

 

Do you mean the operator needs to enter the file name?

Today I had to do a quick job and use the simple cut function and I wanted to use the laser to see where the sheet was cut and if it was straight but it seems to have the same problem that offsets, so I had to guide me by the torch

Can you post the gcode you’re having difficulty with ?

It is only when I use the simple cut button function, it is just a straight that cuts the shaft. Simple cut at x = 50 is just a cut line.

Was it off in X or Y?

I am sure I checked single cut with an offset applied for X in an X direction cut.  I’m not sure if I checked with an offset applied for X and Y with just an X cut.  

I’ll have to have a closer look tomorrow.

X=50
Y=0
Only x