Advanced Search

Yes, the RS-422 is their smart serial connection between the 7i97T FPGA main board and 7i73 and 7i84 daughter boards. Since there is only one RS-422 configured standard on the 7i97T (on TB4), you can only connect one of those two cards, until you reflash the 7i97T to reconfigure some of the pins of the P2 expansion port to provide a second RS-422.

Glad you are enjoying my videos. It is fun to dick around with this stuff
Cheers,
Mark

 
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.