Advanced Search

Very cool! If you wanted another plasma challenge, how about an ethercat plasma board powered by 24v PoE so you can mount a board that does the ArcOK input, Torch on relay and the torch voltage right at the plasma cutter itself. Add a PoE injector in your control panel amd its all self contained.

the 7I75 works and I wouldn't have problems making a mistake?

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?

www.sainsmart.com/products/cnc-5-axis-br...stepper-motor-driver
 Is the common breakout I recommend.

You can connect directly to the parallel expansion connector but one wiring mistake
and you may kill the 7I97T

You can check the (DB25) pinout with mesaflash's --readhmid command if you have loaded the
desired firmware into the 7I97T.  You can also check the .pin files in the 7I97t.zip support image.
These are just the result of running mesaflash with the --readhmid option on a 7I97T with the
corresponding firmware loaded.

If you download the latest mesaflash, it has the option of showing the HDR26 pinout (the normal default
is to show the DB25 pinout)

What also helps if you give an overview of your complete project, rather than just a little bit at a time.
If you just want to run a single stepper Linuxcnc may be overkill, operating the parallel port via a simple C program may be easier, but that will mean obtaining permissions from the kernel to do these, and running in user space may not give consistent timings for the stepper.
The other option would be to have a hardware base approach and use python or what ever to control when the stepper runs & stops.
Even a simple Arduino sketch controlled by via a serial connection would be easy. Depending on the library used you could have control over decel & accel.

Hardware RPi 5 8gb
IMAGE rpi-5-debian-bookworm-6.12.11-arm64-ext4-2025-01-27-0140 (1).img.xz

On a fresh image install i get failure to start service in the boot.log below is from the journalctl

i formatted and tried again same problem any ideas?Feb 20 14:49:54 raspberrypi systemd[1]: Starting zramswap.service - Linux zramswap setup...
░░ Subject: A start job for unit zramswap.service has begun execution
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit zramswap.service has begun execution.
░░
░░ The job identifier is 119.
Feb 20 14:49:54 raspberrypi root[738]: Starting Zram
Feb 20 14:49:54 raspberrypi zramswap[738]: <13>Feb 20 14:49:54 root: Starting Zram
Feb 20 14:49:54 raspberrypi zramswap[734]: /usr/sbin/zramswap: line 53: echo: write error: Invalid argument
Feb 20 14:49:54 raspberrypi systemd[1]: zramswap.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ An ExecStart= process belonging to unit zramswap.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Feb 20 14:49:54 raspberrypi systemd[1]: zramswap.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ The unit zramswap.service has entered the 'failed' state with result 'exit-code'.
Feb 20 14:49:54 raspberrypi systemd[1]: Failed to start zramswap.service - Linux zramswap setup.
░░ Subject: A start job for unit zramswap.service has failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit zramswap.service has finished with a failure.
░░
░░ The job identifier is 119 and the job result is failed.

Most likely a loose connection or bounce. maybe use debounce?

There is a way to do it in Hal, run a search on the forum for an example. I don't have one handy to share,. But it was xor component used I think from memory. Or maybe someone has something setup they can share.

That instruction is in the docs.

kcjengr.github.io/probe_basic/machine_config.html

the pinout or configuration to connect the step and dir where could I find it?