Advanced Search

 
Hi all,

I’ve developed a custom Python package — and not just a loose .py file, but a real multi-module package, complete with pyproject.toml, unit tests, internal structure, and even a __str__ for logging prettiness. Yes, I know, it’s total overkill for something that just drives the lubrication pump… but hey, it’s fun

The code I wrote can be found here if anyone is interested: github.com/johanvergeer/maho-mh400e-conf...ree/main/lubrication

Now I want to use this package from a Python script that’s launched via loadusr in my machine config.

Some context:

• The script uses linuxcnc, hal, and qtvcp modules.
• LinuxCNC runs on the global system Python interpreter as far as I can see, which means my package has to be available outside of any virtual environment.
• Installing with pip install . into the global Python environment technically works, but it’s strongly discouraged on modern Debian-based systems due to PEP 668. I’ve already seen Poetry try to uninstall half of /usr/lib/python3 
  
• Virtualenvs don’t help much either, since they can’t see LinuxCNC’s compiled modules.
• Adding my repo folder to sys.path is possible, but feels like duct tape.

So… what’s the best practice here?

• Is it acceptable to install your own packages into something like /usr/lib/python3/dist-packages/?
• Is there an officially recommended way to include custom Python packages that need to be imported across multiple files or used in different HAL components?

Or am I simply in “here be dragons” territory and should stick to a bunch of flat .py files with global state? 

Any advice or patterns you use would be greatly appreciated!

Cheers,
Johan
 

Yep, that's definitely the problem.  QtPlasmaC does not intend for G92 to be used.  In fact for the Master branch, we disabled it entirely:

Master Docs

I would recommend you use the peripheral offsets process to set up your laser pointer:

Peripheral Offsets

Then you can use the process described in the LASER section to set your origin.  The bonus is that you can use this to rotate the work coordinate system to account for a sheet of material that is not quite straight.  

LASER

Hopefully that helps get you straightened out.  Please let me know if you have any questions. 

If its still of interest, the limit switches are normally closed, and go over a relay to the controls.

Setup:
LinuxCNC 2.9.0 using Axis, configured with Stepconf
Dell Precision Workstation T3500, 8g ram
Radeon HD 5700
Two identical Sunix PCIe parallel port cards
Mint Debian Edition 6
#1 SMP PREEMPT_RT Debian 6.1.128-1 (2025-02-07)
6.1.0-31-rt-amd64
Why do I have two parallel port cards? Some time ago, I damaged the MB parallel port.
This setup works great.

When I add a wifi card (TP-Link PCIe Wifi card AC600), the second parallel port card address changes (per dmesg). I updated the hal with Stepconf for the new address. Now in Axis, the Machine Power button is grayed out, like the estop circuit is open. Estop-in is on the second parallel port card, so I'm interpreting this as the wifi card is somehow blocking the second parallel port card.
I shutdown, removed the wifi card, updated the second parallel port card address, and it all works fine again.

Put the wifi card back in and ran ptest
forum.linuxcnc.org/18-computer/4743-parallel-port-tester   (thanks BigJohnT)
Both parallel port cards work with ptest, with the wifi card installed.

Advice will be greatly appreciated.
Steve

 

I was considering getting these drivers. Did you manage to get them to work, or should they be avoided?

sorry Snow.

1. no tried again with a different file.
2. yes, cut, then frame. its a time lapse.

I did some testing tonight and all is good until i zero off the laser pointer.
The code i'm using for this is
G92 x0 y0/ G0 x-2 y 104/G92 x0 y0

Is this code wrong?

Also, everything is fine, until I zero on the laser pointer.