Advanced Search

on the probe page, the the far right tab "Probe Help" gives an explanation and a graphical representation of the parameters so you can understand how to utilize them for probing. you can pretty much probe for any scenario if your parameters are correctly setup.

larger entries for step off and xy clearance can help with eyeballing probe starting point, it give you more cushion for error, but they will need to be more pecise when probing smaller features especially bores/holes valleys etc.

COFHAL wrote:

The c-axis component does not have, as orient does, a pin to indicate that it has reached the commanded position. I need to know when the spindle is in position in order to activate an output. Any idea how to do this?
 

Maybe a combination of the PID error being below a certain value and the PID output = 0?

Something like wcomp for the error comparison (+/- a little bit) and an and2 component could drive an output only when the C-axis has settled.

I'm having to give up on caxis.comp, at least for now.  I ran in to issues with spindle synchronization when using it.

when in doubt, it help to read the instructions which tell you to delete those comments

 

the xy clearance needs to be considered. that is how far it moves after making contact. also the step off width needs to be set to get the probe near the center of the hole.

for small holes i use the probe from center in the hole and use an xy clearance parameter that is the radius of the hole to be probed. that should get you what you need!

Same laptop exactly, but using PlasmaC on Linux Mint 19.3
www.youtube.com/shorts/ciVcxrlmMIA
Next video under it is Lenovo Yoga 370 with QtPlasmaC also with touchscreen
www.youtube.com/shorts/__zn74D7OyM

Images for RPI4 and RPI5 here
www.linuxcnc.org/iso/
Actually several for each, so it would be prudent to remove old versions.

Perhaps this is a key item

Thanks, I know how to load and connect to hal_manualtoolchange, I'm trying to figure out how hal_manualtoolchange.py works so I can roll my own using PyQt6.

This part is pretty straight forward to me making the pins
JT

Gents,
quick question - is laptop as below good for LinuxCNC + PlasmaC + Mesa 7i96 (or other Mesas)?
Lenovo ThinkPad T470s
Processor: Intel Core i7-6600U (2,6 GHz, turbo 3,4 GHz)
512GB SSD NVMe
RAM: 16GB DDR4
Grafika HD Graphics 520
Screen: 14", IPS, 1920x1080, matt, touchscreen

I can have it for 235 Euro.
I'm bit worried about screen size - is 14" comfy to operate in touch mode?

Thanks!

After removing # comments throwing errors PB still wouldn't switch the power on so I went and deleted all the # comments on lines after code and now it seems to be working properly.
I am used to code that accepts comments after code lines like that so I figured it would be best to keep it in there for reference but it didn't work till I deleted them all.
I suppose I could have tried putting them above or below if I cared enough. I assume that would work.

I just got in. Only note so far is the home all button being labeled HOMED is a little confusing.

Stuck in e-stop

tried using jumpers on diag0 and diag1 and monitored the pins:

halcmd show pin remora.input.00
halcmd show pin remora.input.01

nothing changed when pulling signal either high or low.

checked hal and ini files, still trying to get the hang of it, I checked if the current tool pos was out of bounds...

thanks for helping out,
Jairo
 

Ah progress. I commented out usertabs and relaunch it does the same for

raise IOError('The specified POSTGUI_HALFILE does not exist: %s' %
OSError: The specified POSTGUI_HALFILE does not exist: /home/shopbot/linuxcnc/configs/Shopbot/probe_basic_postgui.hal # ONLY 1 postgui hal file can be called at launch

Then between your comment being included in the error and then I noticed in Geany they were not red like other comments I tried deleting the # recommended/required comment after the lines that were throwing errors and the errors went away.

Hi Arciera,

I will make a repository for this. Then testing is easy.

Just found a exception. At page 5, where va1 & va2 are calculated.

This are arc related vectors, 90 degrees in between. And also need the arc normal.

However the proof function uses a example arc where the arc start, arc center, arc end are colinear.
The result is a arc normal vector [0,0,0] wich is not good.

So i think we have to ship the arc's containing the normal unit vector. Just as we do inside lcnc's
trajectory planner.

Edit : Now i shipped the arc normal into the funtions and things work for eq29, eq30.

Link to repository

Edit:
Now at the point :

eq29_proof(); -> interpolate arc
eq30_proof(); -> calculate derivates.
eq31_v1_proof(); -> calculate vector v1 & v2
eq31_v2_proof();
eq35_proof(); -> forward transformation 2 segments (did just one test, it does rotate the segments.).

And layoff the chatgtp it's not good for your health

That is fine, as long as there are entries under /dev everything is fine.