- Posts: 10
- Thank you received: 0
"Scan" feature to move around maximum boundaries
I would like to implement a "scan" function to move the spindle along the XY-bounding box of the loaded G-Code file. I thought I would get the boundaries, add a MDI_COMMAND that I can link to a pyVCP button or a button on a XHC-pendant.
I found forum.linuxcnc.org/41-guis/29080-boundaries-pin-in-axis which allows me to get the boundaries into HAL pins. But how can I access these pins from G-Code?
On forum.linuxcnc.org/22-pyvcp/30976-readin...n-values-from-python someone used a command like "G0 X#<_hal[boundaries.xmin]>", but when I try this I get an error that the variable does not exist.
How can I access the pin values? Or can I write the boundaries to named or numbered parameters in .axisrc? Or is there another way to get values from the python code in .axisrc to a MDI_COMMAND?
Thank you for your help,
Lars
Please Log in to join the conversation.
linuxcnc.org/docs/2.7/html/remap/remap.h...i_file_configuration
(You can be forgiven for not finding that, it is documented in a very odd place)
Please Log in to join the conversation.
Please Log in to join the conversation.
- tommylight
-
- Away
- Administrator
-
- Posts: 22012
- Thank you received: 3
lars wrote: Thanks a lot. Works great.
Would you mind elaborating ?
Thank you.
Please Log in to join the conversation.
tommylight wrote: Would you mind elaborating ?
Sure. Sorry. I didn't think there was any interest.
This is to check if the coordinates and the fixtures are all setup correctly before starting the actual job. It moves to the bounding box (XY only) of the loaded program, goes around once and then returns to its old position.
It was a feature I liked in bCNC which I used with GRML before switching to LinuxCNC on my new machine.
This is my .axisrc
and this is goes in $SUBROUTINE_PATH/boundaries-scan.ngc
Then I created a new line under [HALUI]
Please Log in to join the conversation.
Too bad it's so akward to get boundary info to linuxcnc.
I wonder in boundaries shouldn't be standard variables?
Chris M
Please Log in to join the conversation.
Although it would be nice if the GUIs exported this in a more easily accessible way.
Please Log in to join the conversation.
It could get the file name from the linuxcnc.stat().file
linuxcnc.org/docs/2.7/html/config/python...ding_linuxcnc_status
The run through each of the lines of G-code noting the max and min X and Y values.
(this might be inaccurate for arcs)
Then it could send the moves by MDI.
Please Log in to join the conversation.
1. What happens if the file changes? The boundaries should only be updated when the GUI reloads the file. How would an external component detect that?
2. The coordinate system offsets may change. I think this would be possible to detect from the component but it would not be really trivial.
3. Just getting min/max X/Y values from the G-Code also neglect cutter compensation and maybe other things? I think the values should be precise when they are used to ensure that the program won`t go through your fixtures.
Please Log in to join the conversation.
lars wrote: 1. What happens if the file changes? The boundaries should only be updated when the GUI reloads the file. How would an external component detect that?
Nothing changes. When the component sees the "do your thing" trigger it then loads a copy of the current G-code fie into it's own parser and works out the extents.
The module can either work in the current coordinate system, or get all clever and have the parser consider the offsets (read from linuxcnc.stat() and calculate absolute sizes.2. The coordinate system offsets may change. I think this would be possible to detect from the component but it would not be really trivial.
Yes, including arcs. But I was imagining starting simple and then making the parser more sophisticated as required.3. Just getting min/max X/Y values from the G-Code also neglect cutter compensation and maybe other things?.
Please Log in to join the conversation.
