Advanced Search

Turns out the GNU versions of chmod is inferior to the FreeBSD version I'm used to using on macOS.

Why don't the people at the GNU foundation just use the FreeBSD chmod?!!!

They could, but they insist on re-coding the wheel.

It's very annoying!

The FreeBSD has some issues, but has WAY more functionality than the GNU one.

The man page for chmod on macOS is WAY, WAY more detailed and informative than the lame, short GNU one.

 
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
 

You can set special file permissions.

Allow write but not deletion.

Set the sticky bit to true.

Writing is allowed, but not deletion.

sudo apt install lm-sensors

(Optional, but recommended): sudo sensors-detect

sensors

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. 

Hi all 
I need to order a 7i73 and shipping is $90 USD to get it to Qld Australia. This may be the unavoidable cost but I can't justify it for a $49usd board.
I'm happy to wait a couple of months if necessary and combine freight with others ordering from Mesa.
If your considering ordering and would like to combine our orders and split freight costs PM me. 
Cheers Brad.

Fixed the link formatting.

Not sure what has happened to that link? but it still works?

Hi Stenly, I bought these Signal converter . They cost a lot more than I wanted to spend but at the time I thought I was going to get it going quicker. Approx $130USD each. The Aikron ones might be worth the gamble. Or if you are more tech savvy than I am currently then the ones jochen has linked would be a option. Here is their reply to my email for the ones I bought.

"Your calculations are very helpful.  The HEIDENHAIN LS 486C has a 20µm resolution glass which, as you correctly calculated, will produce a 10Khz signal at 12m/min.  I have attached a data sheet showing the federate limits of each interpolation version for your reference.  You can choose any interpolation option from 0.5x to 5x.  The 5x interpolation model (SA 1872) will provide you with a 1µm TTL output signal. "

In all likelihood they just have the chip jochen has linked

Got it to build. The install script, as far as I can tell it doesn't bring in libclothoid3d and libscurve
When I did that manually (path here forum.linuxcnc.org/38-general-linuxcnc-q...orm?start=170#323932) and copied that to the empty directories the code builds.

Thank you! That did the trick!
I'm currently getting familiar with the HAL Scope.

After displaying the encoder position and the stepgen feedback position, I noticed that the stepgen was counting positive while moving in the positive direction.
I corrected this by adding a minus sign in front of the STEP_SCALE.

However, this caused the motor to spin in the positive direction during homing.
I fixed that by removing the negative signs from the homing and latching velocities.
There probably is a nice way to fix that, isn't there?

Edit: I've added working .hal and .ini files for future Reference. (only X has encoder feedback)