Im fairly new to linux cnc, trying to do a clean install in a mini pc of the 2.9.8 iso but im encoutering these errors when trying to install ethercat the way this thread discribes, can someone help?


Failed command:
./configure --enable-sii-assign --disable-rt-syslog --disable-tool --disable-userlib --enable-generic --enable-ccat --disable-tty --with-linux-dir=/lib/modules/6.12.86+deb13-rt-amd64/build --enable-e1000 --enable-igb --disable-igbvf --disable-ixgbevf --enable-igc --enable-e1000e --enable-8139too --enable-e100 --enable-r8169 --disable-stmmac-pci --enable-dwmac-intel --disable-genet && make modules

Error! Bad return status for module build on kernel: 6.12.86+deb13-rt-amd64 (x86_64)
Consult /var/lib/dkms/ethercat-dkms/1.6.9/build/make.log for more information.
dpkg: error processing package ethercat-dkms (--configure):
 installed ethercat-dkms package post-installation script subprocess returned error exit status 10
Setting up libltdl-dev:amd64 (2.5.4-4) ...
dpkg: dependency problems prevent configuration of ethercat-master:
 ethercat-master depends on ethercat-dkms; however:
  Package ethercat-dkms is not configured yet.

dpkg: error processing package ethercat-master (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linuxcnc-ethercat:
 linuxcnc-ethercat depends on etherlabmaster | ethercat-master; however:
  Package etherlabmaster is not installed.
  Package ethercat-master is not configured yet.

dpkg: error processing package linuxcnc-ethercat (--configure):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for libc-bin (2.41-12+deb13u3) ...
Errors were encountered while processing:
 ethercat-dkms
 ethercat-master
 linuxcnc-ethercat
E: Sub-process /usr/bin/dpkg returned an error code (1)

This happens on my system rarely too, and i can solve it that way:

forum.linuxcnc.org/38-general-linuxcnc-q...-after-reboot#314789

You could try deleting the igH.sources (name might be a  bit wrong) from /etc/apt/sources.list.d

And follow this process which I have tested with 2.98 in the last week or so.
github.com/linuxcnc-ethercat/apt

This is going to become the official repository and Ethercat version to use for linuxcnc

I was clicking more or less randomly. Found an option (which I cannot find again) to choose in a session manager what saved session to start during login.

I deleted that session and now it works again.

I still would be interested to learn what I might have done wrong in the first place.

Hallo Tommy,

vielen Dank, werde ich heute ausprobieren..

karlhe

 
The menue bar in the upper screen is missing and the blue menue of the Axis GUI is missing. And I do not know why. 

The next screen shot is from the other machine and that is what the first machine looked like a few days back. 
 
 

Hello, 
I know the following will be somewhat unspecific, but maybe someone has a simple explanation based on my attempt. "Did you try to switch it offandonagain?" Yes already. The machine also seems to move normal, but the Linux desktop cannot be operated normal. 

I left the machine on and coming to the workshop today I could not see the Axis window anymore. 
The complete desktop behaves strange. 

After re-start and unplugging the screen I could start Axis Gui. I cannot move the axis window or re-size it. 
Something is odd it seems. 
Either something is really damaged on the installation or I have accidently changed some setting that I am not aware of. 

Also usually there was a bunch of software things visible and that seems to be missing. 

 

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
 

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!