Advanced Search

Was this with the version included in the 2.9.4 ISO?
Djakuju bardzo.

Same principle for the statusword. It is named statusword in ethercat-conf.xml not cia-statusword.
You can go over the names of all pins in ethercat-conf to see that they match the name in the hal file.
 

Pressed a little longer on the input field and a keypad showed up.
Unexpectedly helpful. But where is the "-" sign? And a "," or "." would be nice needed too.
As far as I can tell it is an integrated keyboard, not the external onboard.
 

thank you tommy. i will try adding home switches.

I need to reopen this topic. The installation went smoothly as described above. After reinstalling the system, I can no longer access the EK1100 (it worked before). I've spent hours searching for the error, but to no avail. What I noticed is that the EtherCAT master always has the status "Link DOWN."

Master0
  Phase: Waiting for device(s)...
  Active: no
  Slaves: 0
  Ethernet devices:
    Main: 80:ee:73:fd:0f:8b (waiting...)
      Link: DOWN
      Tx frames:   0
      Tx bytes:    0
      Rx frames:   0
      Rx bytes:    0
      Tx errors:   0
      Tx frame rate [1/s]:      0      0      0
      Tx rate [KByte/s]:      0.0    0.0    0.0
      Rx frame rate [1/s]:      0      0      0
      Rx rate [KByte/s]:      0.0    0.0    0.0
    Common:
      Tx frames:   0
      Tx bytes:    0
      Rx frames:   0
      Rx bytes:    0
      Lost frames: 0
      Tx frame rate [1/s]:      0      0      0
      Tx rate [KByte/s]:      0.0    0.0    0.0
      Rx frame rate [1/s]:      0      0      0
      Rx rate [KByte/s]:      0.0    0.0    0.0
      Loss rate [1/s]:          0      0      0
      Frame loss [%]:         0.0    0.0    0.0
  Distributed clocks:
    Reference clock:   None
    DC reference time: 0
    Application time:  0
                       2000-01-01 00:00:00.000000000

Could this also be the reason why no master is found when starting a test configuration?

The EK 1100 is powered and the network is connected. Is there something wrong with the network configuration?



 

Hi Aciera,

Thanks for your reply!

I’m planning to machine cast iron and steels like CK45 or SPK, mainly for mold making.

When it comes to speed, I'm still new to the CNC world — I'm coming from 3D printers world — so I don’t really know what’s considered fast or slow here. But I’m not looking for anything extreme. I thing Something like 45 or 30 mm/s feed rate with 0.3 to 0.5 mm depth per pass would be okay

About the machine setup:

For now, 3 axes will do, but I’d like to add a small 5th axis later — just enough to work on parts like cylinders up to 10 cm radius and 20 cm height.

I want to build the frame from epoxy granite for better rigidity and vibration damping.

Planning to use 25 mm ball screws with 5 mm pitch, and 30 mm linear rails.

The spindle will be a 2.2 kW single-phase induction motor, belt-driven with a VFD.


I’m not going for an automatic tool changer just yet, but it’s definitely on the list for future upgrades.

Oh, and by the way — I recently found a Beckhoff EK1100 for only €95, which I think is a good price

But Unfortunately, motors with ethercat are expensive.

Are the drives normally disabled and physically grounding pin 9 (to pin 10) enable the drives?
(this looks to be the case)

You can also verify operation of the enables when connected to the drive  by measure in the voltage
from ENA+ to ENA-. It should be a relatively high positive value when disabled and close to 1V when
enabled
 

That looks like its working since you are only getting interrupts on CPU 3
(CPU 2 interrupt count  is not changing)

ProblemAs a newbie to Mesa cards, I spent a whole night trying to connect to a 7I76EU card (IP 10.10.10.10, jumpers W2=OFF, W3=OFF). mesaflash kept throwing errors: „Unsupported ethernet device 7I76EU” or „No 7I76EU board found”, even though ping to 10.10.10.10 worked and LEDs CR4 (FIELD POWER) and CR14 (LOGIC POWER) were on. CR11 (FIELD I/O FAULT) was lit, and CR13 (FPGA /DONE) sometimes lit up, hinting at a firmware issue. I wasn’t sure whether to use 7I76EU or 7I76E in commands, as 7I76EU is less common.What I checked

• Power: Connected 24V DC to TB1 (VIN) and TB2 (FIELD POWER), following: YouTube: Mesa 7I76E Power . Jumper W1=ON. Did not use P4/P5 (5V) as the card has built-in regulators.
• Network: Used a standard Ethernet cable (non-crossover), connected directly to PC. Initially tried IP 192.168.1.121 (W2=ON, W3=OFF), but switched to 10.10.10.10 (W2=OFF, W3=OFF), setting up the network per: Forum: Mesa Ethernet Setup . PC IP was 10.10.10.11/24, firewall disabled (sudo ufw disable).
• mesaflash attempts: Commands like sudo mesaflash --device 7i76eu --addr 10.10.10.10 --readhmid failed. I noticed the error mentioned „7I76EU” even when I used ETHER or 7i76e, suggesting the card was detected but not supported by mesaflash.
• LinuxCNC: Using Pncconf, I configured for 7I76E (IP 10.10.10.10). Changing INI to BOARD=7I76EU caused LinuxCNC to fail, but BOARD=7I76E worked, and CR11 turned off. On TB2, a multimeter showed DIR+5V signals changing with axis movement, and shorting IN17 to +24V activated the input in HAL. The card was working!

SolutionThe issue was an outdated mesaflash version that didn’t support 7I76EU. Updating from GitHub fixed it. Steps:

1. Check version:
   bash
   Copy

   mesaflash --version

   My version was too old.
2. Install dependencies (Debian Bookworm):
   bash
   Copy

   sudo apt update sudo apt install libpci-dev libmd-dev pkg-config build-essential git

3. Download and compile mesaflash:
   bash
   Copy

   git clone https://github.com/LinuxCNC/mesaflash.git cd mesaflash make sudo make install

4. Verify version:
   bash
   Copy

   mesaflash --version

   Showed: 3.5.13.
5. Test communication:
   bash
   Copy

   mesaflash --addr 10.10.10.10 --device ETHER --readhmid

   After fixing a cable mix-up, it returned card details: BoardName: MESA7I76, HostMot2 firmware, 5 StepGen, 3 I/O ports.

Notes

• Ensure the PC is in the 10.10.10.x/24 subnet and firewall is disabled.
• Jumpers W2=OFF, W3=OFF set IP 10.10.10.10; W2=ON, W3=OFF sets 192.168.1.121.
• LinuxCNC with BOARD=7I76E works because 7I76EU is compatible with 7I76E in older versions.
• CR13 (FPGA /DONE) stopped lighting up after LinuxCNC started correctly, but updating mesaflash was key for proper diagnostics.

ThanksThanks to advice from LinuxCNC.org , YouTube videos, and Grok’s guidance, I solved the issue. Hope this helps other beginners!
Show in sidebar

Thanks for the quick reply.
Yes, it's 2.9.4. I don't know how to get to 3.4.6.
I'm still waiting for the timing belt that connects the spindle to the encoder.
So that could be the reason.

Thank you very much.

You don't have auto-tuning PID permanently in tuning mode by any chance?

LinuxCNC 3.4.6? I don't recognise that version number. 2.4.6 exists (but is very, very, old). The latest released version is 2.9.4

Anyway, the macros all work in feed-per-rev mode, so rely on a spindle encoder existing and being properly configured. Do you have a spindle encoder?
(It would be a simple case of editing the various .ngc files to operate in units/second mode, if not)

Do not set tandem axis, it does not work without home switches.
Set it as a normal XYZ machine and wire the two Y motors/drives to the same stepgen/output, be it physically or in hal.

If you want to execute a G-code file on pressing a PyVCP button, then I don't think that PyVCP supports this.
You can do it with G-code subroutines and action buttons in GladeVCP or QTVCP though. linuxcnc.org/docs/html/gui/gladevcp.html...an_o_word_subroutine

However, would just changing the default G-code file to be your G-code rather than the Axis splash screen do what is needed?

Existing code appears to expect either SIGINT or SIGTERM:

github.com/LinuxCNC/linuxcnc/blob/master..._intf/halui.cc#L2405

If halui quits on exit from Axis, then I would suspect a problem in your code, otherwise it would look like a wider question.