New compensation component for engraving and 3D Printing

Hi,
I have the feeling this thread was somehow hijacked.

Coming back to the original topic, I would like to thank @scotta for this module. It appears to be exactly what i am looking for.
However, I have to admit that the documentation is much too short for me.
After about half a day searching the net I found that the grid-file probe-results.txt can be generated with an example file
grid-probe.ngc that actually comes with LinuxCNC. That's a frustrating newby experience.

After another half day of research I decided that the remark:
"... external offsets must be enabled ..."
could mean to copy all files from ~/linuxcnc/configs/sim/axis/external_offsets/ to the new config directory.

But now I'm stuck with something where I get almost no search results at all from Big-G and others, the error message now is:
./Compensate.hal:103: Pin 'axis.x.pos-cmd' does not exist
Where Compensate is the name of the configuration and this hal file includes in line 103
net xpos-cmd <= axis.x.pos-cmd => compensation.x-pos
which throws the error.

I have no clue where or how the Pin axis.x.pos-cmd gets defined???

Can anyone help?

You need to be running V2.8 and above for the external offsets feature. The pins are documented here
linuxcnc.org/docs/2.8/html/man/man9/motion.9.html

Thanks, for pointing that out, it explains a lot!
I found the webpage with the explanation as one of the very few search results, but did not realize the version constraint.
I'm on 2.7.15 still.
But that will probably change within this week .

Hi
 I'm keen to get this going on my CNC to cut and mill Depron. Glass is .3mm up in a area. Its a standard 64bit linuxCNC DEB install. First it needed Scipy so I did a "sudo apt-get install python-scipy"  ?
Now this -
Debug file information:Note: Using POSIX realtime./custom.hal:4: python exited without becoming ready1306Stopping realtime threadsUnloading hal componentsNote: Using POSIX realtime

Any ideas?
srl 

 

My compensation.py file was formated wrong, I did a cut and paste instead of a download.
It now loads up fine.
I now need to work out the comands as my hal file uses joint's.

srl

I'm having a problem with the hal lines. I have a standard Stepconfig set-up.
With two "net xpos-cmd" lines it has a config error.
Commenting out the the first- "#net xpos-cmd joint.0.motor-pos-cmd => stepgen.0.position-cmd"
the program runs but I get a "joint 0 following error" when I move the tool.

Any ideas ?

Hello

I will try to use your compensation component, instalaton was fine and load correctly, thanks you for sharing that.

Some time ago you will speak about sharing your subroutines for map generation.

It is something possible possible ? ( i will like to add z grid creation button in my Axis panel screen)

Best regards

I have found this topic with interesting link for Autoleveler
forum.linuxcnc.org/38-general-linuxcnc-q...to-linuxcnc?start=10

Not tested for now but it seem to create a ngc file correctly, now is time to find a way for create equivalent file with my python code.

I think i will not be "very difficult" to calculate point but i need to find how to create file and make this working correctly is another things lool.

At this point the major problem i can see is how to take care for manage to probe a T solt table ? so any help are welcome for this mathematic problem.

The goal is to embed all the stuff inside "probe screen NG" i hope i can use other value from regular probe config but need to add (6 entry box needed for "XY start" "XY end" "XY row") or (5 entry box
r "XY start" "XY end" "XY spacing")

Br

   
 

Edit : i will think for Tslot table to add fixed value in ini file but unfortunatly i think that i'm not able to create the math stuff :
"XY first length" from machine 0 for first groove
"XY groove width" 
"XY plate width" 

Max size can be checked with ini file
[AXIS_X]
MIN_LIMIT = -0.11
MAX_LIMIT = 356.11

Edit 2 : this was perfect if we also can use tool setter position + dimension for prevent probing in this area

There is a sample ngc file named gridprobe.ngc.
You can use it as a starting point.

Hello

Is i'm the only one having a possible little issue with your compensation component ?

I have noticed if you activate/unactivate the "compensation.enable-in" i can see my machine cumulating the offset.

I think this is because after disable compensation the machine stay in place.

I appologize if this is not understandable.


Edit : it is a good idea to try to return to old position before stoping the component ???