temporary work offsets. external offset or something else?

More
2 years 10 months ago #287301 by Aciera
How about using an MDI command:

G10 L2 P0 X<your value> Y<your value>

If you wanted you could also create a custom command like

M123 X<your value> Y<your value>

They can enter the distance to the workpiece from xyz0 in those boxes, and run a program

This can also be done but is a bit more involved.
The following user(s) said Thank You: lunada

Please Log in or Create an account to join the conversation.

More
2 years 10 months ago #287303 by lunada

How about using an MDI command:

G10 L2 P0 X<your value> Y<your value>

If you wanted you could also create a custom command like

M123 X<your value> Y<your value>

They can enter the distance to the workpiece from xyz0 in those boxes, and run a program
This can also be done but is a bit more involved.
 


 
i'd rather spend the time now to figure out how to add the boxes. The operator gets too flustered and makes mistakes when it gets complicated. He JUST got used to the old controller before it took a dump, so i'd really like to make it like it was. Also, i am pretty fond of the way it was as well. The machine has a vacuum table so the workpiece placement is rather arbitrary and it's nice to just plop a piece of wood on the table, measure from the corner of the spoilboard, and just enter the values on the screen into the 3 boxes. 
I can add the boxes via pyvcp, however i assume that somehow either needs to enter an mdi command or change the .var file? That's where i'm a bit lost. 

Please Log in or Create an account to join the conversation.

More
2 years 10 months ago - 2 years 10 months ago #287305 by Aciera
Your pyvcp boxes should set a halpin value, say 'value_x' and 'value_y' you could then have another pyvcp button that executes an MDI command like this:

G10 L2 P0 X#<_hal[pyvcp.value_x]> Y#<_hal[pyvcp.value_y]>

[edit]
For more information on reading hal pins from gcode see section 4 here:
linuxcnc.org/docs/2.9/html/gcode/overvie...:overview-parameters
Last edit: 2 years 10 months ago by Aciera.
The following user(s) said Thank You: tommylight, lunada

Please Log in or Create an account to join the conversation.

More
2 years 10 months ago - 2 years 10 months ago #287311 by rodw
Normal workflow would be to go where you want to start your job and just touch off each axis. 
With my plasma machine I had a laser pointer (offset from the torch) which I pointed to where I wanted to start and press one button that moved the cutting tool to the laser point and set the g54 offsets for X & Y. I also had another button called Zero XY which made the current tool position X0Y0. That sounds more like what you want rather than mucking about with entering coordinates.
Last edit: 2 years 10 months ago by rodw.

Please Log in or Create an account to join the conversation.

More
2 years 10 months ago - 2 years 10 months ago #287312 by lunada

Normal workflow would be to go where you want to start your job and just touch off each axis. 
With my plasma machine I had a laser pointer (offset from the torch) which I pointed to where I wanted to start and press one button that moved the cutting tool to the laser point and set the g54 offsets for X & Y. I also had another button called Zero XY which made the current tool position X0Y0. That sounds more like what you want rather than mucking about with entering coordinates.
while that does sound handy for some stuff, what i want is to enter coordinates, just like our old controller, mainly to prevent incidents. Our operator is very new. The less changes the better right now until he gets more comfortable. I may add your button as a secondary thing though. 
Last edit: 2 years 10 months ago by lunada.

Please Log in or Create an account to join the conversation.

More
2 years 10 months ago #287313 by lunada

Your pyvcp boxes should set a halpin value, say 'value_x' and 'value_y' you could then have another pyvcp button that executes an MDI command like this:

G10 L2 P0 X#<_hal[pyvcp.value_x]> Y#<_hal[pyvcp.value_y]>

[edit]
For more information on reading hal pins from gcode see section 4 here:
linuxcnc.org/docs/2.9/html/gcode/overvie...:overview-parameters
Thanks! That's helpful. i'll do some reading and give it a shot. Sounds like what i'm looking for. I may try to add a button like Rodw mentioned as well. 

Please Log in or Create an account to join the conversation.

Time to create page: 0.174 seconds
Powered by Kunena Forum