Error in published instruction. It should actually be -

vi sources.list.d/linuxcnc-uspace.list

deb [arch=amd64,arm64 signed-by=/etc/apt/trusted.gpg.d/linuxcnc.gpg.key.binary.gpg] www.linuxcnc.org/ bookworm base 2.9-uspace 2.9-rt
 

Bonjour à toutes et tous,
Quand j'ouvre une image en .png, il apparaît ce message :

Traceback (most recent call last):
  File "/usr/bin/image-to-gcode", line 34, in <module>
    plus_inf = numpy.core.Inf
               ^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/numpy/core/__init__.py", line 30, in __getattr__
    attr = getattr(_core, attr_name)
  File "/usr/lib/python3/dist-packages/numpy/_core/__init__.py", line 167, in __getattr__
    raise AttributeError(f"Module {__name__!r} has no attribute {name!r}")
AttributeError: Module 'numpy._core' has no attribute 'Inf'. Did you mean: 'inf'?

D'où vient mon problème ?
Quelles perspectives pour corriger ?
Merci !
 

That seems like a fair trade haha, currently watching videos on the 7i73 to modify the hal for all the buttons. also just designed a rough draft pendant

Unfortunately, this does not work on the actual machine. It worked on the sim on a VM but does not behave the same on the physical machine. I can't figure out why. I also can't figure out why just disabling with 'self.probe_spindle_nose_subcallbutton.setEnabled(False)' doesn't work either. Any pointers? I am out of things to look at that I can vaguely understand.

In any case, it seems like the Z axis homing is unreliable

If the latch velocity is low than this seem more like a switch/mechanical  or debounce issue

I've started reading and thinking about a solution.

Right now, unfortunately, I don't have the time to make the progress I'd like.

I've come a long way, but I'm not giving up...
Thank you for your work, it's a great help.

Thanks Unlogic! we are wrestling with the builder at the moment but once that is squared away we will be able to update the current main branch with the updates!

having that knowledge is essential for your cnc builds and troubleshooting as well as giving you the tools to customize macros and really simplify your day to day operations. we strive to give you a good starting point with the gui but it is very difficult to cover every need for the various machine and user circumstances that arise. hopefully you have some fun with learning it. when i started probe basic i was new to everything myself. I found the doc i linked above and after a couple days of reading, testing, adjusting, i was able to write all of the macros for the probing routines. as i went along i found new tricks and ways to write the code to improve upon things and still to this day i find new methods to utilize in how things function in the subroutines. it is a very rewarding endeavor to be sure! I wish you good luck with your journey and please do pop back in to share your journey or ask specific questions if the need arises!

ok, i have a clean install of everything and have ran a test with a new tool and everything seems to be working as expected on the main branch.

I set my parameters as follows and ran the test with the below results:
spindle zero = 10.0000
load new tool = 221
click touch off current tool
manually trigger probe tip button on probe page at Z-8.0015
spindle retracts home position
tool length offset is stored in tool table as 1.9985
z axis dro shows -1.9985

all of this seems to track correctly. can you try running things in your sim to see if it behaves differently from your machine? it may show something or maybe not.

also can you post your tool_touch_off.ngc subroutine code so i can compare to what the sim has? everything in the code appears to be correct and here it is tracking correct.

my earlier findings seem to be related to the experimental branch i was working on and the issues are not present on the clean install.

I downloaded the image of disk 2.9 and allowed network connection during installation. After installation, it was loaded normally, everything is working, linuxcnc-uspace.
We follow the instructions - 
apt-get update
apt-get install linuxcnc

linuxcnc.org/docs/2.9/html/getting-start...#cha:Installing-RTAI
He swears, there is no such package! The list of sources indicates -
deb linuxcnc.org bookworm base



I run synaptic, the kernel is 5.4.258-rtai
I order it to be installed and heads - 

Hi,
At first thanks a lot to the community for your effort to improve LinuxCNC.
I am using LinuxCNC 2.10 and it runs without problems on Debian Bookworm.
This morning pre0-5285 should be available. However on the buildbot only 4852 is downloadable and hasn't been updated since 2025-08-22.
Is there a new buildbot on which we get the newest version ? Or is it simply forgotten ?
Thanks again and have a nice day.
Philippe

Hola, buenos días, no creo que ese sea el problema, ya que el interruptor de inicio home solo se utiliza una sola vez cuando enciendo la máquina luego ya no lo utilizo para nada más.
la velocidad de home es muy baja, la máxima velocidad a la que la máquina puede funcionar es de 1700 y la velocidad del primer contacto con el interruptor de home lo tengo a 100 y el segundo contacto que es para el ajuste fino la tengo configurada a 3.

Digo que no creo que sea ese el problema por que para empezar a fresar la PCB tengo que subir y bajar el eje Z muchas veces antes de empezar, ya sea haciendo home de pieza (que no es el home de la máquina) o subiendo y bajando el eje manualmente y una vez empieza a cortar a la medida correcta y ya no se desvía en todo el trabajo que puede tardar una hora, y en el transcurso del trabajo el eje Z sube y baja muchas veces por que tienen que moverse de zona y para eso sube se desplaza y vuelve a bajar para seguir cortando y lo hace perfecto, el problema es al empezar que no sé por qué le pasa eso

My mistake, "sdos upload" should be just "upload".

And what? You now have an "Invalid input configuration"
By any chance, will there be another result if you repeat the same thing?

Can you then do the same thing with "ethercat -p 0 upload 0x1a00 0" to see if the input pdo got configured?
And the same for 0x1c12 and 0x1c13?

Or maybe one should start with what PDOs the drive has. "ethercat pdos".
I have a drive where I pick PDOs from several RxPDOs and TxPDOs,
maybe that's how you need to do it.
The drive doesn't seem to download the PDO mapping, like is needed for configurable PDO mapping.

Note that that is the default (as shipped) firmware, not the 5ABOB firmware

Ran into an issue with IRQ balance after updating to trixie

Nov 16 19:34:22 hazelnut irqbalance[597]: IRQ 9 affinity is now unmanaged
Nov 16 19:34:22 hazelnut irqbalance[597]: Cannot change IRQ 14 affinity: Read-only file system
Nov 16 19:34:22 hazelnut irqbalance[597]: IRQ 14 affinity is now unmanaged
Nov 16 19:34:42 hazelnut irqbalance[597]: IRQ 123: Override ban to true
Nov 16 19:34:42 hazelnut irqbalance[1572]: /etc/linuxcnc/lcnc_irqbalancepolicy.sh: line 17: /proc/irq/123/smp_affinity: Read-only file system
Nov 16 19:37:52 hazelnut irqbalance[597]: Cannot change IRQ 135 affinity: Read-only file system
Nov 16 19:37:52 hazelnut irqbalance[597]: IRQ 135 affinity is now unmanaged



Turns out there was a bug version of irqbalance that is fixed with

github.com/Irqbalance/irqbalance/issues/308#issue-2217868587

after adding

/etc/systemd/system/irqbalance.service.d/override.conf

➜  ~ sudo cat /etc/systemd/system/irqbalance.service.d/override.conf
[Service]
ProtectKernelTunables=no

It fixed the ethernet mesa issue that was causing latency spikes