Job not showing in position - 2.9.4 - v2.9-238.315

 

I'll try and get a video of this and upload it.

www.youtube.com/shorts/b2f-urW5Wb4

So, load file - no worries.
preview opens a long way from 0,0
cuts in location
frames where preview is shown.

Could it be the post processor?? 

youtube.com/shorts/b2f-urW5Wb4?si=VfSc_KL7Y7zgTUn_

I apologize, this fell off my radar. I’m not sure what I’m looking at exactly, but a few observations:

1. That’s not the file you posted above
2. Are you showing a cut run and then clicking on framing? Everything happens so fast in that video and it doesn’t show the whole screen so it’s hard for me to follow what exactly is going on

I’ll try to simulate your setup this evening if time allows.

sorry Snow.

1. no tried again with a different file.
2. yes, cut, then frame. its a time lapse.

I did some testing tonight and all is good until i zero off the laser pointer.
The code i'm using for this is
G92 x0 y0/ G0 x-2 y 104/G92 x0 y0

Is this code wrong?

Also, everything is fine, until I zero on the laser pointer. 

Yep, that's definitely the problem.  QtPlasmaC does not intend for G92 to be used.  In fact for the Master branch, we disabled it entirely:

Master Docs

I would recommend you use the peripheral offsets process to set up your laser pointer:

Peripheral Offsets

Then you can use the process described in the LASER section to set your origin.  The bonus is that you can use this to rotate the work coordinate system to account for a sheet of material that is not quite straight.  

LASER

Hopefully that helps get you straightened out.  Please let me know if you have any questions. 

Thanks Slow.

In all that reading I couldn't find how to do what I have been doing.

I have a user button that allows me to align the laser on the sheet where i want 0,0 to be. I press the button and the machine moves to this point and re-zero's the machine.

Could you guide me on an appropriate code that would work in place of "G92 x0 y0/ G0 x-2 y 104/G92 x0 y0" ?

Cheers

If you want to set X0Y0 via a user button (or MDI), you can use
I’m going to be honest, I don’t understand your workflow, or why setting up the laser offset and using the laser button won’t work for you.  

Either I’m doing a bad job of explaining or I need more info about your setup.  Perhaps a picture of your table would help?

Setting up the laser offset sets the relationship between the laser pointer and the torch, as this should never change.  Once that’s set, you will get a LASER button above the axis readouts.  You can then use
this button to set your offsets.  If you don’t want to use it to set a rotation and only X0 Y0 then you just click a few times until it says laser again.  It will then park the torch above where your laser pointer was, and set everything to 0.

What am I missing?  Help me help you
 

Thanks Snow,

You always do a great job, i'm just a bit different.

Using the laser button is 3 clicks and wait for lag. first to "laser" then "mark edge" then "set origin", then the machine moves.

With the user button, its a one click and the machine moves to where i need it, zero's, and i'm ready to start cutting. the code i'm using is the one I found worked many years ago and i have just kept it. i also have another button used for the air scribe offset (albeit still a work in progress). I have only had this issue since the update to 2.9.4.

My normal operation flow goes.
home machine
sheet on machine
import drawing
align x,y using laser
click laser offset to zero torch on where i lined up laser pointer
frame to check cut file will fit (done alot when cutting multiple parts from sheets that have already been cut)
then cut

I'll try the new code now and see how it all goes.
new code is G10 L20 P0 X0 Y0 \ G0 X-2.5 Y104.3 \ G10 L20 P0 X0 Y0
Works perfectly, thanks again Snow !!

Glad it got you going again!

The “lag” is due to the way internal MDI commands are dealt with, in conjunction with choosing a method that works well with the preview.

Always interesting to learn how people use the GUI. The feedback is good, helps drive feature updates, etc. (to the master branch, 2.9 is locked in from a QtPlasmaC standpoint).

IIRC, something was updated with G92 that made us completely disable it in the master branch. At any rate whatever the change was is eluding me, but it’s the reason G92 doesn’t behave as it used to for you. It isn’t anything we changed in QtPlasmaC.

The other way is the way to go anyhow.

Enjoy.