Advanced Search

jimmyrig wrote:

Went to run a file generated from sheetcam and got "g92 offsets are not allowed" error. Documentation seems to want a g38 instead of a g92.

We probably should suppress that error when #<tube-cut>=1.

In the meantime you could hide it by creating a custom_filter.py file in your config directory with the following contents:

Hi
i have a machine that a friend of mine is doing and it seems as he has had a accident and is out off it for a bit .
linuxcnc is loaded 
switches are on mesa7184 board
the drives are on a mesa 7177 board 
that is connected to mesa 7194t
and ther is a extra meas7184 as well
My big problem is i have no clue on how to go on with this first time i have seen it ,
i need some help please 

Pncconf probably didn't get updated to set up unhomed joint jogging for the joystick.
So it must be homed before jogging works.
You don't need limit switches to home.

Looks great, love the control panel design.

I haven't added limit switches yet, that's further down the line.

It has an intel nic chipset. I didnt fully comrehend the workaround you had advised. By that I mean which version of debian and deskktop etc

is the machine homed?

Thank you Tommy,

I now get all four square corners as shown in the cutfile
much appreciated.

David

I've been having some issues in getting a wired Xbox360 controller working with LinuxCNC and could use some words of wisdom.
I've set up the controller in the Pncconf wizard:
 

I've ran the configuration in LinuxCNC but pressing the relevant controllers yields no result. However the meter does show the expected signals:
 

Any suggestions on what I am missing?

It's going to be helpful to mention the nic chipset. I've found it to be an issue with the 2.5GB realtek chips. From what I've seen it appears to be a firmware issue.

Tho I have advised on how to get around this issue.

What is the last thing?

Don't worry about it.

Everything will work fine when running a machine.

Have you tried htop when running gcode and actually running a machine ?

You can modify the isolcpu parameter, it's under the /boot folder in a subfolder, mind tho the boot folder has a different structure to the standard RPi one. It's been a while since I've used my RPi5 since helping Rod put the image together (due to the lack of a SPI driver for Mesa hardware).

Long story short latency will suffer without isolation. And depending how cache is shared between the cores there can be a performance hit by isolating the incorrect pair of CPUs (this was from a long forgotten paper). At the end of the day it's not outright performance this is vital with Linuxcnc but latency. Having a responsive interface and more importantly having latency within spec is all that matters. It's not as if you'll using the machine as a desktop whilst running a machine. Remember it's a single use computer, not a desktop.

Play around with isolating CPUs run some latency tests and see how you go. BTW what hardware are you using to control your machine.

Even on a multi core machine with no cpus isolated if the load doesn't require it you will have cores that are more or less idle.

You can use the weighted_sum component
to combine individual bits to create an integer
command

I am trying to install linuxcnc_2.9.1-amd64.hybrid.iso, on an intel nuc core i5 8gb Ram.  It has wlan and LAN.  Connected to LAN.  The live version works including networking! but if I try an install it goes to a stage where it asks for some intel network drivers.  when i cancel it just goes to a screen where it says setting up network and freezes.  I used Rufus to make the usb (Never had this problem with 2.8 versions,  have dowloaded twice and checked with two different usb's.  Totally stumped, can some seniors advise.  I am new to Linux.
Thanks in advance

Somehow with my mini pc with a N100 cpu I had a better result with turbo enabled, so that is something you could try. Sometimes a newer kernel version can help. This one works well with that mini pc:
drive.google.com/drive/folders/1L28lG0zD...2XQJx?usp=drive_link