Advanced Search

Search Results (Searched for: )

  • unknown
  • unknown
03 Sep 2025 09:59
Replied by unknown on topic Mesa 7I76eu with linuxcnc 2.8.2

Mesa 7I76eu with linuxcnc 2.8.2

Category: Driver Boards

Note: Using POSIX realtime
./CNC.hal:10: parameter or pin 'hm2_7i76e.0.watchdog.timeout_ns' not found
834
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

Try hm2_7176.0.watchdog.timeout_ns
  • JiKr
  • JiKr
03 Sep 2025 09:45
Replied by JiKr on topic Mesa 7I76eu with linuxcnc 2.8.2

Mesa 7I76eu with linuxcnc 2.8.2

Category: Driver Boards

PCW, thank you for fast reply, attached is the on start error report, with mesa 7I76e, there is no problem.Any idea how to fix it, please?  

File Attachment:

File Name: linuxcnc_report.txt
File Size:8 KB
 

File Attachment:

File Name: linuxcnc_info.txt
File Size:4 KB
  • andypugh
  • andypugh's Avatar
03 Sep 2025 09:14
Replied by andypugh on topic halui.mdi-command-NN pins not showing up

halui.mdi-command-NN pins not showing up

Category: HAL

Thanks for the fix.
It's odd that this seems to not have been seen before.
(Or maybe has just been worked around with dummy axes?)
  • Kuzma30
  • Kuzma30
03 Sep 2025 09:12
Replied by Kuzma30 on topic AMSAMOTION IO module

AMSAMOTION IO module

Category: EtherCAT

[ 7042.964030] EtherCAT: Master module cleaned up.
[ 7044.047160] EtherCAT: Master driver 1.6.7 1.6.7.gc1e6b50-1+26.2
[ 7044.047314] EtherCAT: 1 master waiting for devices.
  • Hakan
  • Hakan
03 Sep 2025 09:08

Issue with OP Entry Delay and Failures in LinuxCNC + EtherCAT System

Category: EtherCAT

Lots of errors there.
Maybe you should try disconnect most devices and test with only EK1100 and EL1008, that's combination that should work.
First error is "Can not calculated topology" or something like that. Cabling ok?
  • wankoran
  • wankoran
03 Sep 2025 09:04

Issue with OP Entry Delay and Failures in LinuxCNC + EtherCAT System

Category: EtherCAT

 I'll correct the previous description.

When the machine is turned on, the drives are all in the preop state


Then I opened linuxcnc and found that the status of several drives had not changed from preop to op, Moreover, even when in the op state, the drives of these copley cannot be controlled.
 

After shutting down linuxcnc, the status of these copley drives still remained at op
 

debian12+ethercat1.6.7 dmesg
 

File Attachment:

File Name: debian12et...mesg.txt
File Size:30 KB


debian10+ethercat1.5.2 dmesg
 

File Attachment:

File Name: debian10et...mesg.txt
File Size:2 KB

Although the network cards of the two PCs tested this time are different, I have tested exactly the same network card, and these problems still exist.
 
  • wankoran
  • wankoran
03 Sep 2025 09:01

Issue with OP Entry Delay and Failures in LinuxCNC + EtherCAT System

Category: EtherCAT

 I'll correct the previous description.

When the machine is turned on, the drives are all in the preop state


Then I opened linuxcnc and found that the status of several drives had not changed from preop to op, Moreover, even when in the op state, the drives of these copley cannot be controlled.
 

After shutting down linuxcnc, the status of these copley drives still remained at op
 

debian12+ethercat1.6.7 dmesg
 

File Attachment:

File Name: debian12et...mesg.txt
File Size:30 KB


debian10+ethercat1.5.2 dmesg
 

File Attachment:

File Name: debian10et...mesg.txt
File Size:2 KB
  • Hakan
  • Hakan
03 Sep 2025 08:09 - 03 Sep 2025 08:14
Replied by Hakan on topic AMSAMOTION IO module

AMSAMOTION IO module

Category: EtherCAT

Check the output of "sudo dmesg" after you do  "sudo systemctl restart ethercat" for clues.
  • Hakan
  • Hakan
03 Sep 2025 08:07
Replied by Hakan on topic orient spindle with ethercat EL5101

orient spindle with ethercat EL5101

Category: EtherCAT

Could not fully follow it, but it looks like you give speed to the analog output in the spindle speed case as it should be.
But you give position to the analog output in the spindle orient case - which is wrong, should always be speed.
Worthwhile checking anyway.
  • Kuzma30
  • Kuzma30
03 Sep 2025 08:01
Replied by Kuzma30 on topic AMSAMOTION IO module

AMSAMOTION IO module

Category: EtherCAT

I have not UEFI and enp2s0 is UP
cnc@cnc:~$ sudo mokutil --sb-state
EFI variables are not supported on this system
cnc@cnc:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 78:45:c4:23:9f:86 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.100/24 brd 192.168.0.255 scope global noprefixroute enp2s0
       valid_lft forever preferred_lft forever
    inet6 fe80::7a45:c4ff:fe23:9f86/64 scope link 
       valid_lft forever preferred_lft forever
  • Kuzma30
  • Kuzma30
03 Sep 2025 07:57
Replied by Kuzma30 on topic AMSAMOTION IO module

AMSAMOTION IO module

Category: EtherCAT

cnc@cnc:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 78:45:c4:23:9f:86 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.100/24 brd 192.168.0.255 scope global noprefixroute enp2s0
       valid_lft forever preferred_lft forever
    inet6 fe80::7a45:c4ff:fe23:9f86/64 scope link 
       valid_lft forever preferred_lft forever
cnc@cnc:~$ lspci 
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port Desktop SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
cnc@cnc:~$ cat /etc/ethercat.conf
#------------------------------------------------------------------------------
#
#  EtherCAT master configuration file for use with ethercatctl.
#
#  vim: spelllang=en spell tw=78
#
#------------------------------------------------------------------------------

#
# Main Ethernet devices.
#
# The MASTER<X>_DEVICE variable specifies the Ethernet device for a master
# with index 'X'.
#
# Specify the MAC address (hexadecimal with colons) of the Ethernet device to
# use. Example: "00:00:08:44:ab:66"
#
# Alternatively, a network interface name can be specified. The interface
# name will be resolved to a MAC address using the 'ip' command.
# Example: "eth0"
#
# The broadcast address "ff:ff:ff:ff:ff:ff" has a special meaning: It tells
# the master to accept the first device offered by any Ethernet driver.
#
# The MASTER<X>_DEVICE variables also determine, how many masters will be
# created: A non-empty variable MASTER0_DEVICE will create one master, adding a
# non-empty variable MASTER1_DEVICE will create a second master, and so on.
#
# Examples:
# MASTER0_DEVICE="00:00:08:44:ab:66"
# MASTER0_DEVICE="eth0"
#
MASTER0_DEVICE="enp2s0"
#DEVICE_MODULES="generic"
#MASTER1_DEVICE=""

#
# Backup Ethernet devices
#
# The MASTER<X>_BACKUP variables specify the devices used for redundancy. They
# behaves nearly the same as the MASTER<X>_DEVICE variable, except that it
# does not interpret the ff:ff:ff:ff:ff:ff address.
#
#MASTER0_BACKUP=""

#
# Ethernet driver modules to use for EtherCAT operation.
#
# Specify a non-empty list of Ethernet drivers, that shall be used for
# EtherCAT operation.
#
# Except for the generic Ethernet driver module, the init script will try to
# unload the usual Ethernet driver modules in the list and replace them with
# the EtherCAT-capable ones. If a certain (EtherCAT-capable) driver is not
# found, a warning will appear.
#
# Possible values: 8139too, e100, e1000, e1000e, r8169, generic, ccat, igb, igc, genet, dwmac-intel, stmmac-pci.
# Separate multiple drivers with spaces.
# A list of all matching kernel versions can be found here:
# https://docs.etherlab.org/ethercat/1.6/doxygen/devicedrivers.html
#
# Note: The e100, e1000, e1000e, r8169, ccat, igb and igc drivers are not built by
# default. Enable them with the --enable-<driver> configure switches.
#
DEVICE_MODULES=""

# If you have any issues about network interfaces not being configured
# properly, systemd may need some additional infos about your setup.
# Have a look at the service file, you'll find some details there.
#

#
# List of interfaces to bring up and down automatically.
#
# Specify a space-separated list of interface names (such as eth0 or
# enp0s1) that shall be brought up on `ethercatctl start` and down on
# `ethercatctl stop`.
#
# When using the generic driver, the corresponding Ethernet device has to be
# activated before the master is started, otherwise all frames will time out.
# This the perfect use-case for `UPDOWN_INTERFACES`.
#
UPDOWN_INTERFACES=""

#
# Flags for loading kernel modules.
#
# This can usually be left empty. Adjust this variable, if you have problems
# with module loading.
#
#MODPROBE_FLAGS="-b"

#------------------------------------------------------------------------------
  • Hakan
  • Hakan
03 Sep 2025 07:46
Replied by Hakan on topic Fresh start with linuxCNC and Ethercat

Fresh start with linuxCNC and Ethercat

Category: General LinuxCNC Questions

Definitely an Intel network card for EtherCAT.
For one of the Qt interfaces I would not select the slowest computer around.
  • Hakan
  • Hakan
03 Sep 2025 07:42
Replied by Hakan on topic AMSAMOTION IO module

AMSAMOTION IO module

Category: EtherCAT

The Ethercat server appears to be working but cannot connect to the network interface.
You should see something like this
debian@plasma:~$ ethercat master
Master0
  Phase: Idle
  Active: no
  Slaves: 4
  Ethernet devices:
    Main: c4:62:37:06:66:54 (attached)
      Link: UP
Look out for "(attached)" and "Link: UP"

There are several possible reason
- wrong module name or mac address in /etc/ethercat.conf
- network interface is not "up"
- your system uses secure boot, UEFI, ethercat kernel modules can not be loaded. Check some 15 lines down in "sticky", the spoiler section.


 
  • alexscott
  • alexscott
03 Sep 2025 06:40
Replied by alexscott on topic Fresh start with linuxCNC and Ethercat

Fresh start with linuxCNC and Ethercat

Category: General LinuxCNC Questions

Hey !
I'm building a cnc mill with a german FS4GM epoxy granite gantry and a Spinogy X22 spindle. It's a small but rigid setup that I'd Iike to control with 400W servos, LinuxCNC and EtherCat.
Since I only ordered the mechanical parts+spindle, I still can avoid some problems (ie latency issues) by choosing the right slope game things on the electronic/control/computer side. Hence this newbie message : 
What servo/drivers/computer/other things-I-still-don't-know-about would you go if you had to get them again ?

Cheers,
Flo

The FS4GM gantry with the Spinogy spindle should give you a very rigid platform. Since you’re still in the planning stage, it’s smart to think about the control side early.
Displaying 286 - 300 out of 23546 results.
Time to create page: 1.139 seconds
Powered by Kunena Forum