Advanced Search

I have deleted the debs from the server (as much as I could do while at work) and will work on getting an update out this evening (GMT+1)

That version was the one that introduced the bug so you would need to update to a later version as this issue was fixed in 2.9.6.

Note the current version in debian (2.9.9) has an issue affecting tool offset parameters:
forum.linuxcnc.org/38-general-linuxcnc-q...38-2-weird-behaviour

So you could get the appropriate deb package for version 2.9.8 from here:
github.com/LinuxCNC/linuxcnc/releases

Or wait for version 2.9.10 to be available in the debian repositories to be able to update through the update manager.

Looks fine but for mesa its better to run: latency-histogram --nobase --sbins 1000 --show to get rid of the base thread window which gets in the road. and can suppress results. Run that and reshare.

I've just finished installing the system, disabled all power-saving features (C-states, SpeedStep, etc.) in the BIOS, and isolated a CPU core using isolcpus.

Here are my latency test results while stressing the system with 4 instances of glxgears and a YouTube video playing in the background

Note: I am currently running this test using an old VGA monitor. I suspect the analog output/Xorg driver might be causing some minor latency spikes compared to using a pure digital connection, but I'm not entirely sure.

What do you think of these numbers? Are they good enough to move forward with my Mesa setup, and what should my next steps be?

Thanks in advance for your feedback!

LinuxCNC 2.9.5

The old behavior did not respect the old docs, the old docs also specified that the parameter are set with G43

Tool Offsets for X, Y, Z, A, B, C, U, V & W. Set by G43. Volatile.

I guess there maybe many subroutine codes that relied on the old faulty behavior, even when the docs state you should set them with G43...

But the reasoning to use a different set of parameters is strong, we have had it wrong for so long time, wrong is the new correct...

Edit:
github.com/LinuxCNC/linuxcnc/pull/4219
follow progress here, you should get 2.9.10 with this reverted change soon.
The new behavior is in #5081-#5089

You don't need a gateway, and you certainly don't need DNS. You also don't need such a large mask. Just enter the IP address, for example, 10.10.10.20, and the mask. Depending on the format, either 24 or 255.255.255.0.

For testing, you can enter the IP address manually in the console.
#check the interface name (probably enp0s31f6)
sudo ip link show
#add address
sudo ip addr add 10.10.10.20/255.255.255.0 dev enp0s31f6
#test local address
ping -c 3 10.10.10.20
#test mesa card
ping -c 3 10.10.10.10

remove "require IPV4 addressing......."

I would leave the gateway and DNS server entries empty
as they are meaningless here.

I have made the changes that you suggested. Still the same message appears when I hover over the save button. That button never gets highlighted.

 

raul wrote:

Hi.

Did You have any luck fixing the card. I have the same exact problem.
s

Hi

Sorry for the very late reply... Yes, the cards got fixed. i bought the ethernet chips from mouser.de (about 6eur each) and a friend at work solderd them to the boards
 

I feel this is adequate but not sure if this is the right place, feel free to correct me.
-
As i read almost everything here, i keep noticing the same issue happening over and over, namely where users of LinuxCNC update/upgrade version for no particular reason and end up with broken machines.
This stems from the windows "update mentality" being forced upon us for the last 20 odd years... never mind.
-
[bold]In short, never update/upgrade a working machine, unless you explicitly need new features.[/bold]
-
It is Linux, and no matter how much money microsoft invests on youtubers to convince you that Linux is not secure, IT absolutely IS secure, the whole world uses Linux, all WORLD servers are running Linux (even microsoft's servers run Linux since 2000 with Red Hat), are on public IP so the whole world has access to them, yet very rarely anything happens to them.
STOP TYPING!
Even when something happens, almost always it is some running service/software that failed/got hacked, not LINUX, or some old server that was last updated 15 years ago.
And for those watching youtube about this, notice they never ever mention the comparison is being done for the web browser, NOT for the operating system.

OK, thank you Aciera.

IP 11 at the end, not 1
Gateway 1 at the end.

What version of LinuxCNC are you running?