Advanced Search

One interesting point I noticed, if, after booting LCNC, I run pinirq script first time and 2nd time, results are different and as follows:
==============================================================
raycnc1@debian:~/Downloads$ sudo ./pinirq_2024-09-26.txt enp4s0
[sudo] password for raycnc1:
Cores: 2
Old CPU Mask: 3
Set device enp4s0 IRQ 32 CPU mask to 2
raycnc1@debian:~/Downloads$ sudo ./pinirq_2024-09-26.txt enp4s0
Cores: 2
Old CPU Mask: 2
Set device enp4s0 IRQ 32 CPU mask to 2
raycnc1@debian:~/Downloads$
==============================================================

the "Old CPU Mask:" is different.
if I run LCNC after pinirq script is run once, interrupts goes to CPU1 as desired.

So what should I do? How to run this script on start-up?
 

Try this new pause_pin.py file

exactly which items do you intend to set? 
 
[img]data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAQAAAAngNWGAAABDUlEQVR4AYXRgUZDYRjH4TegFTKgpEqiFJgoWAoMEQGBgBboChaaAKxLKAhAhQqAdAmpBIQolkCFqp2nITvNKXuA7+/Hhzey5OWjE4Nq3rzY1f9/NGHPB549492+8Ww060iCS2XdctZdI3GsECmb+HJoIX6x6EgDm+lURTH+YB7V9nAqE5WNme4YKuOiY6iMe6PaQxUUIuTbswgFVNJwA8sO3Bn6yR6bWZMSNtJwDtuWfHpQxaPx9C9zadil7jrCigbq6UXceNIVKTWUIqypm2ytJdTiNyNeXclF6GttOVfeDEc7qzjR23r3OMFqZKng1kw0mXGLrfibHTScOZWgGv9TdC6ROFeMTgwYiIxvJzMRWQbeGZUAAAAASUVORK5CYII=[/img]

Both scripts runs and results as follows:
===========================================================
raycnc1@debian:~/Downloads$ sudo ./pinirq_2024-09-26.txt enp4s0
Cores: 2
Old CPU Mask: 2
Set device enp4s0 IRQ 32 CPU mask to 2
raycnc1@debian:~/Downloads$ sudo ./checkmask_2024-09-26.txt enp4s0
Cores: 2
Actual CPU Mask: 2
Desired CPU Mask: 2
IRQ: 32
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-18-rt-amd64 root=UUID=bc617657-6a6c-4afa-9a67-ef553e3b2439 ro initrd=/install/gtk/initrd.gz quiet isolcpus=1
raycnc1@debian:~/Downloads$
==========================================================

I did not understand the result though. Is it ok?













 

As a test, you can try running this utility to pin the IRQ

 

First download  then

chmod +x pinirq.txt

 then

sudo ./pinirq.txt enp4s0


This utility can check the mask:

 
 

So sorry about that Todd.

At the risk of getting banned:
FUCK!
-
Sorry Todd.

But with isolcpu=1, I understand that servothread runs in CPU1 and by irq balance setting, we are aiming the ethernet interrupts in CPU1, not in CPU0.

Am I correct?

Yes, looks like only CPU 0 get interrupts from enp4s0.

Ok, understood.

But please confirm whether Interrupt in CPU0 is correct or not. 

I'm not sure it can be done - but I'm no expert.

My initial thought is that the on_abort subroutine is run while LCNC is in auto mode... so there's no way for a program to switch to manual (or MDI) mode.

I'll dig around a little and open a new thread - the issue (or solution) may not be specific to PB.

Ismacr63 wrote:

I don't know why those modes aren't shown in my version. I just downloaded it, followed the installation instructions and it looked like this. 


How can I add them?
 

Sounds like something got messed up in your PB installation.

What Linux distribution are you using, and what version of LCNC?  This might have a bearing - I've had problems in the past with certain combinations/versions of Debian/LCNC/qtpyvcp/PB.  Seems like frequently some dependency or other invisible 'backstage' issue led to weird problems with PB.

I know it'll be a bit painful, but my suggestion is to make a copy of your config and then uninstall and reinstall PB using the instructions here:
forum.linuxcnc.org/qtpyvcp/53871-probe-b...on-start-here#310377

Yes, your Ethernet interface is named enp4s0

Look like ethtool is not included in your linuxcnc distribution

Note that if you have Realtek hardware you will need to load the DKMS driver
(and ethtool in not needed, ethtool is only needed for Intel Ethernet hardware)

So the existing setup/hold times are marginal
I would set them both to 20000 (20 usec) as I
mentioned before.

This is what indicate the manual for the servomotors jmc