Advanced Search

This seems to be an issue that seems to happen with HP boxes, add in cards seem to be disabled. This is just not related to Linuxcnc cards. Users have had issues with PCIe LPT cards and a month or so ago when doing a google search related to this it pops up in HP forums with no resolution (not just the above mentioned add in cards). (sorry I didn't bookmark the threads I found)

The user, langdons, really needs moderating, he is a bane to the forum.

I will dig more into tonight and see if i can find something from the bios. The only thing i can think of is that linuxcnc was installed with secure boot.

Properply end up doing a fresh start with linuxcnc.

I will update on this, if i find something.

Thanks.
I tried 3mm thick steel and attached the clamp directly to the metal and it cut as it should.

When I do a torch-test with 3 seconds pulse then I read a voltage of 180V on the plasmac-screen. Is that a plausible value ? 

Is it possible to get a table with cutting-settings for different thicknesses from sb. who also uses a Stahlwerk-Plasmacutter or comparable so I don't neet to try and waste so much metal ?

The error log has identified an issue (noted above), you will need to address this.

Hello, I am running the master branch of LinuxCNC with QTLathe GUI. I have a Python component that reads the feed rate from linuxcnc.stat and further use that value in my C component. The machine seems to randomly hard crash and exit LinuxCNC fully. What could be the problem ar what could I change to solve this? Thank you in advance! I am attaching the Python and C components, .ini and .hal files and the error log.

Try the link in this earlier post:
forum.linuxcnc.org/16-stepconf-wizard/26...ulator?start=0#34752

Thanks!

do you also have an idea for my second issue?

Lichuan strange company i buy at aliexpress & receive a water damaged garbage and no one wants to be responsible for it. 

Ok that makes sense basically, I only really need it to use like a limit switch, so I only need the index signal to home it. Thanks

Did you follow the surface map read me instructions and copy over the subroutines? Those are what set the var file parameters for surface map page

I'm not super familiar with surface map, but I would guess it's because the bar doesn't have those parameters or the subroutines that updates the bar have those and needs to be updated.

I've got nothing, I've not seen that write and cannot produce it here to troubleshoot. I would update to the develop branch and update your config files. Start there so at least we know you're on a known working version.

You need to set the parameters in the UI only

The rack is is calculated automatically based on your pocket location settings in the ui

It's been a while, but please allow me to post a little update on my experience with N100 based systems. I noticed that sometimes my mini-pc completely freezes, while running my mini-PC with Windows 11 never caused any problems. So the fix that I implemented was simply to ditch Debian and run LinuxCNC on Windows 11. 
Okay, all jokes aside..... After struggling for quite a while and running all possible checks, I finally discovered that the mainstream Debian 12 and 13 (Trixie) kernels, drivers and firmware have some problems with Alder Lake processors, especially the iGPU part. This can easily be resolved by upgrading Debian with the latest RT kernel (6.12.33+ at this moment), drivers and firmware. Ever since, my system is rock solid. I am using isolcpus=2,3 and irqaffinity=0,1, which gives me a responsive system with with a servo thread latency of 26.3us and a base thread latency of 40.1us, which are both excellent. This was measured during several hours, while simultaneously running 10 instances of glxgears, playing Youtube videos and stress testing the system with:
$ sudo stress-ng --cpu 4 --vm 2 --hdd 2 --fork 4 --timeout 7200s

 

Here is a brief summary of the upgrade process, for those who may be interested: 1. Enable backports:
    Edit /etc/apt/sources.list and add:
    deb deb.debian.org/debian bookworm-backports main contrib non-free-firmware
    Then:
2. Install RT kernel:
   
3. Reboot and check Debian is running the latest RT kernel:
   
4. Update firmware:
   
5. Update Mesa drivers (iGPU):
   
6. Check setup:
    – RT kernel:(already done at step 3)
    – Mesa version:    – Firmware: