Advanced Search

your script might be able to look for linuxcnc's rtapi thread (ie the servo thread) and exit if its not found.
AI seems to think it's possible.

I look forward to testing that, but my tiny script does what I need right now - except exit.  I had hoped to find something in the docs about detecting shutdown, but did not.  It seems a strange oversight, unless you assume linuxcnc never exits until the machine shuts off...
 

I too have started a journey through EtherCAT.  I am using an EK1100, EL1008, & EL2008.  Along with a LiChaun CL57E-4A closed loop driver.  I struggled for some time with getting the driver to go into OP mode.  If you are at all familiar with VS Code it can be an invaluable tool when used with Copilot.  I was able to use AI to build my entire configuration.  The problem I had turned out to be how my ethernet card was configured.  The key was to disable DNS on the ethernet card.  DNS does not play well with EtherCAT.  Once I did that everything just worked.  All the configuration file built by using Copilot.  If you find that your driver is getting an error when it tries to change to OP mode.  Try disabling DNS on your network card.

Hope this helps.

 

I have had really good luck with compac/hp 8300 sff (3rd gen i5 4 core)

sam

PS - my plasma is running a rpi 5...

www.youtube.com/shorts/9-y316bJrGk

Since I am a linuxcnc newb I hope that the below pic is what you are asking for.
I have CL57Y drivers , currently they are wired to: PU+ PU- DR+ DR- . The MF+ (enabled +) and MF- (enabled -) are not connected. 
If they do need to be connected do I connect them from MF+ to  the +5v and from MF- to GND on the TB2 terminal?
Thanks

This is not good. I need working LinuxCNC EtherCAT master very soon. How can I compile this? Maybe install older version of LinuxCNC?

See: linuxcnc.org/2026/07/03/2.9.9-Withdrawn/

Another error after trying to "sudo apt upgrade".

Error: Failed to fetch www.linuxcnc.org/dists/trixie/2.9-uspace...pace_2.9.9_amd64.deb  404  Not Found [IP: 69.163.143.134 443]
Error: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Why is that happening?

The good thing is that I managed to install the ethercat. But I used another computer with UEFI for the purpose.

Thank you very much in advance!

 

Sascha wrote:

Check the encoder resolution in the software. Mine were advertised as 24-bit and there are 23-bit. I have the L8EC drive and ACM2 motors.

Thanks, this is indeed true, they are 23 bit optical. 

Sounds like a great little project, keep up the good work and keep us posted.

Sure thing, take a look here:

forum.linuxcnc.org/plasma-laser/58942-fa...ing-scanning-project

Thanks!
Jeff

I have been working on a small LinuxCNC companion project called **FabScan**. The basic idea is to create a LinuxCNC-friendly camera tracing utility that can help capture outlines, edges, holes, and reference points from real-world parts, then export usable DXF geometry for cleanup/CAM.

The project was inspired by the general workflow of SheetCam Scanything, to be clear it is not based on Scanything code, reverse engineering, or proprietary information. It is a from-scratch MIT open-source project aimed at LinuxCNC users.
The project can be found here: github.com/FabLabRacing/FabScan
The documentation is lacking at this point, it is mostly build notes.

The intended workflow is:

1. Mount a USB camera on the Z-Axis.
2. Use LinuxCNC for the actual machine position reference.
3. Use FabScan to view the camera, detect edges/lines, capture points, and build geometry.
4. Export DXF.
5. Use SheetCam or another CAM program for cleanup, tooling, and cutting.

## Current Status

The current working milestone is around **v0.5.10**.

At this point, FabScan can:

* Load an image and detect contours.
* Adjust threshold, blur, minimum area, and simplify settings.
* Select/classify/sort detected contours.
* Export DXF geometry.
* Capture from a USB camera.
* Rotate/flip camera view as needed.
* Calibrate camera scale.
* Capture manual points from LinuxCNC position.
* Continue native DXF geometry using lines, arcs, and circles.
* Perform controlled X/Y motion through LinuxCNC.
* Jog X/Y from inside the app when enabled.
* Use camera center-dot calibration.
* Preview line/edge detection from the live camera.
* Take single-step and multi-step line/edge following moves.
* Export traced/captured geometry to DXF.

The newest work has been focused on camera robustness and line/edge following.

The line-following proof of concept is working well enough to be useful in testing. One important recent improvement was latching the follow direction during multi-step tracing. Before that, the detected edge tangent could occasionally flip direction and cause the machine to step backward. The current logic uses the selected Forward/Reverse direction for the first move, then chooses the next tangent direction closest to the previous successful move. In testing, this fixed the forward/backward flip.

A recent test captured 50 points along a Sharpie line without the direction flipping. The average step was about 0.050", with the largest observed deviation roughly in the .006"-.009" range. That was with the line slightly out of square with machine travel, so I was pretty happy with the result for an early proof of concept.

## Safety Philosophy

FabScan is intentionally limited.

It only moves X and Y.

It does not control:

* Z axis
* Torch firing
* Plasma start
* Cycle start
* Spindle
* Cutting output
* THC
* Any actual machining/cutting process

LinuxCNC still owns the machine. FabScan only talks to LinuxCNC for position/status and controlled X/Y motion. Motion functions require LinuxCNC to be in a safe state, such as machine on, homed, idle, and in manual mode.

The idea is that FabScan should behave more like a camera-assisted measuring/tracing pendant than a machine controller.

## Hardware / Test Setup

My current known-good test setup is:

* Dell OptiPlex 7060
* LinuxCNC / QtPlasmaC
* Mesa Ethernet hardware
* USB microscope/camera
* Camera resolution currently set to 800x600
* LinuxCNC servo period set to 2,000,000 ns

One important lesson from testing: my microscope camera does not support 1280x720. Asking for that resolution caused OpenCV/V4L2 timeouts and made the GUI sluggish. The current version defaults to 800x600 and is being improved to handle unsupported camera modes more gracefully.

## Recent v0.5.10 Camera Work

The latest camera robustness work includes:

* Default camera resolution changed to 800x600.
* Resolution presets added.
* Requested vs actual camera resolution display.
* Explicit V4L2 camera opening on Linux.
* MJPG request where supported.
* Camera frame reads moved off the Tkinter UI thread.
* Better handling of bad camera devices or unsupported modes.
* Safer preview window close handling.


## Current Line / Edge Follow Settings

The current settings that seem reasonable for testing are approximately:

* Mode: line center
* Step: 0.050"
* Max correction: 0.010" to 0.015"
* Minimum confidence: 55-60
* Count: 10-50
* Camera: 800x600

For tight curves or 180-degree bends, the plan is to reduce step size and search area, while keeping correction conservative.

A future safety improvement I am considering is stopping multi-step follow automatically if the heading changes too much in one step, maybe somewhere around 60-75 degrees. That would help prevent the trace from trying to chase a wrong edge or doubling back unexpectedly.

## What It Is Useful For

The project is aimed at things like:

* Tracing a physical part or cardboard template on the table.
* Picking up edges or holes from an existing part.
* Capturing a rough outline for SheetCam cleanup.
* Following a drawn Sharpie/scribe line.
* Getting usable geometry from shop-floor parts without turning the project into a full CAD system.

## Project Direction

The near-term direction is:

1. Keep improving camera reliability.
2. Make camera selection/resolution handling more user friendly.
3. Improve line/edge following confidence and stop conditions.
4. Continue improving DXF export quality.
5. Keep the project focused and safe.

Long term, I would like FabScan to become a practical open-source tracing/scanning helper for LinuxCNC users, especially for plasma/router-style machines where a camera-assisted part tracing workflow can save time.

It is still experimental, but it has reached the point where the core idea is working and the project feels worth continuing.

Thanks for the update! We'd love to see how things are looking now. Maybe you could share a short video or a screen recording someday.

all the best

tom
 

Hi all,

another short update on LatheEasyStep:

I continued working on the embedded QtVCP startup behavior and focused on the panel initialization path.

On my machine, the startup time with the panel embedded in LinuxCNC was reduced from about 49 seconds down to about 11 seconds.

The main work was cleaning up the widget lookup/initialization path, removing expensive startup overhead, and limiting panel-related searches strictly to the panel itself instead of doing broader lookups.

The panel is now usable again immediately after startup on my system, which is a big improvement compared to the previous state.

I will continue cleaning up the code step by step, but this was an important milestone because the panel is now much more practical to use in everyday work.

Regards

Anybody need ?