Advanced Search

Have you tired this image ?
linuxcnc.org/iso/rpi-5-debian-bookworm-6...23-11-17-1520.img.xz

First time this has come up, I've tested this image multiple times on a 4GB RPi5, so far no issues. No reported issues with 16GB either, which I guess doesn't help your issue.
Is this preventing a full boot ?
If not is zram module loaded ?
Is there any dmesg entry for zram ?
What device are you booting from SDCARD, USB or NVME.
Is your download a good download, ie: matches the sha256 file ?

I found a couple posts earlier that were talking about using basically an or argument. Looking like this must be kind of what they were talking about.

My understanding being that this allows you to use one or the other which solves most issues.
It is weird because I was reading about using a touch probe and tool setter together as a way to do tool offsets and or just to zero the probe and I would have been sure I read that here or other linuxcnc group but maybe not.

So in a quick search it looks like XOR can be used to deal with one sensor being NO and the other being NC, but they are still only tying to the one probe function right?

I read a post where you Lcvett talked about setting offset on a cutter, facing a surface, then calibrating your probe off that surface. Which solves the one use case I can imagine for wanting to use both but it seems like a pretty janky solution.
I can see having two probes with two moving elements adds some complexity and probably some stack up. Is this just considered an unacceptable solution to calibrate Z on a probe? Or is it just that no one has bothered to implement a useful feature because it's not a priority?

A. Is there a way in HAL that only allows spindle on or probe on ? Please share HAL code if possible.
B.Used debounce value 10. Should i lower or increase this value? Hope it doesn’t affect the probe performance. Please share any inputs / experience for the same. Please can you share changes in custum.hal files.

Hi Friends,

Sorry i probably elaborate enough. My goal is to reduce the error in my C/A axis. Currently it jogs, but its shaky and based on what i've seen tuning the servo could help this.

I am reasonably confident in my step and encoder scale figures - 90 deg turn looks like a 90 deg turn. The main issue i am having is that i can't for the life of me find any of the encoder pins that i should be using to tune in HalScope. I know that the tutorial is for a different board but i imagine they would have similar names? i am using 7i96s, below is a screen shot of halwatch when i search for the work "analog". Most of the highlighted ones seem to be inputs, e.g. when i put them in the scope i can enter a value for them. the only ones that seemed to be outputs are in the photo and do no change when i jog the C axis

any advice is greatly appreciated

What should I do to not kill my board?