Advanced Search

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:
 

He did use sudo, I expect this is a BIOS issue, and it appears that the
hm2_pci driver works around this with this:

    // NOTE: this enables the board's BARs -- this fixes the Arty bug
    if (rtapi_pci_enable_device(dev)) {
        LL_PRINT("skipping AnyIO board at %s, failed to enable PCI device\n", rtapi_pci_name(dev));
        return failed_errno = -ENODEV;

But I don't see any equivalent code in mesaflash (nor do I know the equivalent
of rtapi_pci_enable_device with the PCI library that mesaflash uses, but I can take a look.)

 

Works, thanks

At the error, remove the USB device and wait 5 seconds, insert again the USB and wait 15 seconds, click on YES and next.
Usually that works for this, well almost always.
In case it does not work for you:
Download and install Linux Mint Debian Edition, update and upgrade, then
sudo apt install linuxcnc-uspace
-
Warning, this might not be the best option for parallel port use as it might end up with quite high latency.

Hello, I'm building a small CNC milling machine. The iHSV57-30-18-36-EC driver caught my eye. Since I have no experience with Linux, I struggled to get the motor running. However, the motor jumps slightly and irregularly. If you happen to have a working ini, hal, and xml file for this motor, could you help me learn from it? 

Josh 

Hi, sorry for the late reply but I was travelling.
I havent run any updates since I installed PB (never change a running system). 

What exactly do you want me do double check?

This is my config..
github.com/SebastianMusser/LinuxCNC/

regards!

Looks like installing LinuxCNC isn't as easy as installing a casual linux.I remember I had to burn DVD when I first installed it and I borrower a DVD drive to install it properly.I flashed the image using Rufus 4.7 and booted from the USB flash drive - but  then the setup mentions "your installation media coultn't be mounted". Is this a known bug? What's the workaround?Also I was unable to set the BIOS to UEFI mode only. There's no option to disable the compatibility mode - so setup outputs warnings when using USB flash drive in EFI mode.

The link in the html manual does not work. Is this spreadsheet still available?

I see. So is there something like GRBL for output, but used for encoder-inputs?
Like an Arduino or Teensy based encoder-decoder?

I just started um this old computer. There's an old Grub 1.98 with Ubuntu 13 installes. Linux 2.6.32-122-rtai (I probably installed this about 10 years ago )
Also I have to change the bios battery, since it is empty.
It has an Intel D425 installed and 4GB memory.


//Edit: github.com/AlexmagToast/LinuxCNC_ArduinoConnector
That might to the trick. I'm sure there's at least one Arduino Mega2560 within the range of two meters around me. Also I can see at least 5 Arduino Uno in front of me

Thank for the help!

As to what caused the damage, disconnecting/reconnecting the DB25 cable from the
7I77 if there is an (even small) ground potential difference between the PC and the machine
can damage interface components so should only be done with all power off.

That's probably what happened, definitely my screw-up!

Tomorrow, I can look at the schematics and see what parts on the 7I77 are in the ENCMUX
signal path (I think just one Hex inverter)

Thank you!

/Peter

After not having a single bit of Linux, let alone LinuxCNC experience beyond knowing the name, I'm quite happy with what I accomplished within the space of a few weeks. Took a CNC converted lathe and turned it into a dual head urethane grinder with notching and grooving cutting. I'll take what wins I can get at the moment. I'm fairly certain as time progresses and my understanding expands, I'll look back on what I did and facepalm at my "work". For now, I have to stick with the old saying: If it's stupid and it works, it's still stupid and you're lucky.
Thanks for the resource, I will go through it as I have other homework sources I need to review to gain a better understanding of this system.