Advanced Search

with the latest linuxcnc 2.9.8 ISO-install on a Lenovo M720Q I get compile errors. Any ideas?

more /var/lib/dkms/ethercat-dkms/1.6.9/build/make.log

  CC [M]  /var/lib/dkms/ethercat-dkms/1.6.9/build/devices/stmmac/dwmac-intel-6.12-ethercat.o
/var/lib/dkms/ethercat-dkms/1.6.9/build/devices/stmmac/dwmac-intel-6.12-ethercat.c: In function ‘intel_mgbe_common_data’:
/var/lib/dkms/ethercat-dkms/1.6.9/build/devices/stmmac/dwmac-intel-6.12-ethercat.c:615:15: error: ‘struct plat_stmmacenet_data’ has no member named ‘msi_lpi_vec’; did you mean ‘msi_mac_vec’?
  615 |         plat->msi_lpi_vec = 28;
      |               ^~~~~~~~~~~
      |               msi_mac_vec
/var/lib/dkms/ethercat-dkms/1.6.9/build/devices/stmmac/dwmac-intel-6.12-ethercat.c: In function ‘stmmac_config_multi_msi’:
/var/lib/dkms/ethercat-dkms/1.6.9/build/devices/stmmac/dwmac-intel-6.12-ethercat.c:1001:19: error: ‘struct plat_stmmacenet_data’ has no member named ‘msi_lpi_vec’; did you mean ‘msi_mac_vec’?
 1001 |         if (plat->msi_lpi_vec < STMMAC_MSI_VEC_MAX)
      |                   ^~~~~~~~~~~
      |                   msi_mac_vec
/var/lib/dkms/ethercat-dkms/1.6.9/build/devices/stmmac/dwmac-intel-6.12-ethercat.c:1002:59: error: ‘struct plat_stmmacenet_data’ has no member named ‘msi_lpi_vec’; did you mean ‘msi_mac_vec’?
 1002 |                 res->lpi_irq = pci_irq_vector(pdev, plat->msi_lpi_vec);
      |                                                           ^~~~~~~~~~~
      |                                                           msi_mac_vec
/var/lib/dkms/ethercat-dkms/1.6.9/build/devices/stmmac/dwmac-intel-6.12-ethercat.c: In function ‘intel_eth_pci_probe’:
/var/lib/dkms/ethercat-dkms/1.6.9/build/devices/stmmac/dwmac-intel-6.12-ethercat.c:1084:15: error: ‘struct plat_stmmacenet_data’ has no member named ‘msi_lpi_vec’; did you mean ‘msi_mac_vec’?
 1084 |         plat->msi_lpi_vec = STMMAC_MSI_VEC_MAX;
      |               ^~~~~~~~~~~
      |               msi_mac_vec
make[5]: *** [/usr/src/linux-headers-6.12.86+deb13-common-rt/scripts/Makefile.build:234: /var/lib/dkms/ethercat-dkms/1.6.9/build/devices/stmmac/dwmac-intel-6.12-ethercat.o] Error 1
make[4]: *** [/usr/src/linux-headers-6.12.86+deb13-common-rt/scripts/Makefile.build:471: /var/lib/dkms/ethercat-dkms/1.6.9/build/devices/stmmac] Error 2
make[3]: *** [/usr/src/linux-headers-6.12.86+deb13-common-rt/scripts/Makefile.build:471: /var/lib/dkms/ethercat-dkms/1.6.9/build/devices] Error 2
make[2]: *** [/usr/src/linux-headers-6.12.86+deb13-common-rt/Makefile:1981: /var/lib/dkms/ethercat-dkms/1.6.9/build] Error 2
make[1]: *** [/usr/src/linux-headers-6.12.86+deb13-common-rt/Makefile:236: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.12.86+deb13-rt-amd64'
make: *** [Makefile:963: modules] Error 2

# exit code: 2
# elapsed time: 00:03:42 

since the linuxCNC is not part of the process, its input pins cannot be part of it either, and just wanted to confirm that.

I'm inferring that the HAL file has the home switches connected to both LCNC and the drives' digital input:

net X-home-sw            <= lcec.0.10.din-4      #physical digital input on Beckhoff EL1018?
net X-home-sw            => joint.0.home-sw-in   #LCNC joint home switch pin (motion.comp)
net X-home-sw            => lcec.0.5.dout-0      #physical digital output on Beckhoff EL2008?

@Andrax has not mentioned any drive connections explicitly, but the only reason I can imagine sending the home switch signal to a physical output is to signal the drive.  Unless I'm mistaken, a drive's digital input is the only way a drive 'knows' when the home switch is triggered.

Which begs the question - why is the home switch also connected to LCNC joint.N.home-sw-in?

Maybe to do LCNC homing first, then move on to cia402 (internal) homing, and finally absolute encoder homing?

andrax wrote:

Hi,

It's important to always read the manufacturer's documentation.
Check page 27

I had seen that already, but that seemed more like "hey, you can use these pins and not have to buy separate inputs for homing" rather than "you NEED to use these for cia402 homing to work". What made it click was the readme on CIA402_home_comp explaining how you basically need to tell linuxCNC not to panic when it sees the drive moving without it asking and i figured since the linuxCNC is not part of the process, its input pins cannot be part of it either, and just wanted to confirm that. I ordered the db15 connections to solder and they should arrive tomorrow, my plan is to join the drive's internal supplies' grounds to my common ground and just wire the signal wire in there.

Noe I have working 5Axis Ini and hal with mesa card and would configure for sim.axis.vismach.5axis.table-rotary-tilting.....
.thank you
 

See mouse cursor.

Hallo,
ene neue Maschine mit stepconfig erstellt immer eine Simulationsmaschine.

Auf der ersten Seite der Stepconfig wird keine  Änderung angeboten.
Weis jemand, wo man das ändern kann?

Danke karlhe

 

The problem is finally solved! It wasn't an issue with the .ini file directly, but rather with the automatic configuration generated by PNCconf inside the ukryty `~/.axisrc` file.

For my 1366x768 screen resolution, PNCconf had automatically created a `~/.axisrc` file with a hardcoded window geometry of 1366x640:
root_window.tk.call("wm", "geometry", ".", "1366x640+0+0")

Because I am running a complex setup with a PyVCP side panel and 11 NGCGUI tabs, forcing a vertical size of only 640 pixels caused the Tkinter engine to run out of space. As a result, the bottom bars (tool info, positions) and the right side of the GUI were completely cut off.

To fix it, I edited `~/.axisrc` and updated the geometry to utilize the full height of my screen (leaving a small margin for the hidden OS panel):

root_window.tk.call("wm", "geometry", ".", "1366x740+0+0")
root_window.tk.call("wm", "resizable", ".", "1", "1")

I also set my Debian top desktop panel to "Always hide". Now, the AXIS interface starts in the correct size, scales beautifully, and absolutely nothing is cut off anymore. Thank you everyone for the guidance!
 

Hi,

It's important to always read the manufacturer's documentation.
Check page 27

Czy to jest podobne
forum.linuxcnc.org/21-axis/49685-2-9-axis-with-1366x768

Aktualizacja sytuacji: Okno GUI AXIS jest odcięte ZARÓWNO na dole, jak i po prawej stronie.

Rozdzielczość mojego ekranu to 1366x768 (LinuxCNC 2.9.8 na Debianie). Ponieważ 1366px powinno być wystarczająco szerokie dla standardowego AXIS, wydaje się, że zintegrowany panel boczny (jak PyVCP czy GladeVCP) wypycha główne okno poza widoczny obszar ekranu.

Czy mógłbyś mi powiedzieć, jak poprawnie przeskalować okno lub zmienić pozycję panelu, żeby wszystko zmieściło się na monitorze 1366x768? Czy powinienem szukać linii PYVCP lub GLADEVCP w moim pliku .ini?

I now have X and Y working on the actual machine and I want to give this another go. Can you clarify if to use cia402 homing I need to have the limit switches wired into the servodrive specific input pins, or if it works all the same with them wired to beckoff input pins?
Yesterday I had it sort of working (motor direction wrong + homing direction wrong yielded something sort of working) with them wired into beckoff but i'm wondering if by any chance it could be using regular homing because of something else in the config.

Mesa 7i97T would be nice if you can find it, or 7i92T with 7i77, or other Mesa options.
In the mean time, have a look at some of the retrofits i have done with such boards, and what it takes to endeavor in such undertaking:
forum.linuxcnc.org/30-cnc-machines/33529-hurco-bmc-20p-retrofit

forum.linuxcnc.org/30-cnc-machines/31792...-01-retrofit?start=0

And when you get to wiring and tuning, this is a must:
forum.linuxcnc.org/10-advanced-configura...ning-detailed-how-to

Anything and everything, the original post does not translate to anything useful.

Hi everyone! I'm not a programmer, I have a small lathe (LinuxCNC 2.9.8, Mesa 7I96S), and I'm slowly learning. I found a few real issues in the profiler — some of them can actually cause the tool to crash into the workpiece. All fixes were made together with Claude (AI), and tested on real hardware.What was fixed:

• English/Ukrainian language switcher at the very top of the window (English by default)
• D and I were swapped in G71/G72, plus incorrect scaling for G7 (diameter mode) — the actual depth of cut was twice the value entered
• unsafe G71→G70 transition — for certain Start X values the tool wouldn't retract and crashed into the part
• Start X / retract didn't account for arcs (G2/G3) "bulging" beyond their endpoints
• added a "Finish only" mode — re-run just the last pass without G71/G70
• added a safe approach move at program start, from any starting position
• improved preview (symmetric, centerline at X=0) and DXF import
  
  File and detailed changelog (CHANGES.txt) attached. If it's useful to anyone, feel free to grab it.
   
  

I have been looking to implement something like this on my machines. I downloaded the ngc files that you have posted and read your write up on it. Would it be possible for you to post the python files. I believe this would be a great option to be added to the main repo for makers like me. There are a lot of machines out there that have this feature in the controls already. Examples are Onfinity, Sienci Labs and others. It fills a huge void in semi automatic tool change area. I switch my machines to Linuxcnc do to replacement cost after controller failure and the options available with linuxcnc that other controllers don't have. Thanks for all your great work!