Advanced Search

The following results:
- ip a returns the result that the adapter is running without errors:
enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP

- the permissions are also correct:
crwxrwxrwx 1 root root 238, 0  3. Mai 16:22 /dev/EtherCAT0

nevertheless the link is DOWN and I cannot start a test configuration
Debug file information:
Note: Using POSIX realtime
Failed to reserve master: No such device
LCEC: requesting master 0 (index 0) failed
LCEC: failure, clearing config
LCEC: exiting
LCEC: returning -EINVAL
lcec: rtapi_app_main: Invalid argument (-22)
./axis_mm.hal:3: waitpid failed /usr/bin/rtapi_app lcec
./axis_mm.hal:3: /usr/bin/rtapi_app exited without becoming ready
./axis_mm.hal:3: insmod for lcec failed, returned -1
2306
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime
 

OK, that's opposite of what the 7I77 enables do (they are on when enabled)

Probably easiest is to add a external relay, driven by a field I/O output
and wire the NC relay contacts to all drive enables.
 

hey i am having some trouble wiring switches to the board here is what I tried:
I am using pnc conf
I read that the inputs are opticallyisolated so I can put a lot of voltage on the input pins (haven't tried yet only 5v)

the mechanical switchers have NC NO and C

I tried connecting NC to 5V and V to pin1 doesn't stop during homing
inverting just began the turn on with an error about the switch limit


I tried connecting NC to GND and V to pin1 doesn't stop during homing
inverting just began the turn on with an error about the switch limit

I tried connecting NO to 5V and V to pin1 doesn't stop during homing
inverting just began the turn on with an error about the switch limit

I tried connecting NO to GNFand V to pin1 doesn't stop during homing
inverting just began the turn on with an error about the switch limit

FInally i tried attaching NC to 5V, NO to GND and C to pin one and it worked but then the mesa card would get restarted ( apparently its shorting something when i hold the button too long


i saw some other people connecting NC to 24V and then to pin 1, but it should work with 5V as well and it doesn't. i tried pin 0 as well in case the pin was not working. 

i am getting the 5V and gnd from the STEP 3 pins. 

I am very interested what exactly is it that I am doing wrong. 

THanks
 

I created a diagram so that the offset value can be visually confirmed.

Yes, the machine is on, it jogs and the icon for homing is grayed out, when I get to my shop next week I will upload pictures. Absolutely appreciate you guys are really awesome. Super helpful and responsive! Much appreciated! If there’s anyone in this forum that is for hire, let’s talk.

Got it to home but had to change the end stops to just home not home/min, I'll post up my files once I drag the pc upstairs to give it internet, I'm sure there is lots to still fix and do

I'd like to share a structured and slightly modified version of `qt_auto_probe_tool.ngc` I'm using on my self-built 3-axis CNC with LinuxCNC 2.9.3 and the QtDragon GUI.  

---

### ? My Goals:
- Separate tool length offset from work coordinate systems (WCS)
- Make the tool table intuitive and readable
- Ensure safe and efficient probing using machine coordinates

---

#### 1. Set the Probe Top:
I defined the probe top using the tip of the spindle body (with no tool/collet) as a consistent mechanical reference.

- For example, if the empty spindle is lowered to Z = -120 (machine coordinates), I input `-120` as PROBE HT in the QtDragon Probe tab.(I know this is not the intended use.)
- I do not use BLOCK HT at all.

#### 2. Define Work Coordinates:
Once a tool is mounted (e.g., Tool #1 with 30mm protrusion), I:
- Add `T1 Z30` into the tool table
- Set up the G54 (or other WCS) normally

This way, the tool length stored in the table is actual physical protrusion and independent from any WCS — much more intuitive for manual tool changers.

Use G43 to apply the offset.

---

- Tool table values are stable and logical (they represent actual tool lengths).
- Easy to estimate and input values for new tools before probing.
- Tool probing uses machine coordinates, so:
  - Probe start position can be calculated from tool length
  - No dependency on current WCS
  - Safer: if tool table Z is negative by mistake, start offset is clamped to zero
- Multi-WCS workflows (G54, G55...) work seamlessly — no need to re-probe per WCS
- Tool probing is simpler and can be single-pass since start is close

---

Thanks,  

SanzuiWorks

G10 L20 A0

linuxcnc.org/docs/stable/html/gcode/g-code.html#gcode:g10-l20

I did some manual G-code to use a 4th axis rotary basically like a lathe.  The A axis doesn't have a homing switch.  It advances a specified number of turns as the X and Y does its thing.  

Part gets changed out, repeat.  

What's the correct G-code to reset the A axis?  Numerically, it's spooled up like 1000 turns in one direction.  Moves aren't relative and I don't need the thing to unspool 1000 turns to get back to the absolute A-axis value the next G-code run will start at.

 

So, does it not respond to the home button? Is the home button greyed out?
Does it jog? Are the motors locked or free?

I don't think that counts mode _can_ work with a Boxford style of toolchanger as the number of steps lost when the motor stalls against the endstop is unknown.

It could be modified to work, but it might be easier to start from scratch as a single-sensor position-mode stepgen changer wasn't really considered when the component was written.

You could even consider doing all the control in the G-code subroutine:

1) Scale the stepgen so that a position shift of 1 is one pocket.
2) Connect motion.analog-in-00 to the stepgen.2.position-fb
3) Connect motion.analog-out-01 to the stepgen.2.posiiton-cmd
4) Connect the home sensor to motion.digital-in-02
(Actually, you can use any numberered analog/digital IO, you would probably use in, out and digital 00 in practice, but I made them different for clarity)

toolchange.ngc:

I have also overpowered the 5v side of a 7i76 board for a second or so. I saw smoke at S1 and driver chips etc.
Freight is too expensive to post back and forth to USA for repairs. ( In Australia)
Can you make up a component set that would normally be damaged? I'll buy another board and the component set...... to try to recover this board for my next project.

Looks like your network adapter is not upped correctly. The master can't access ethernet.
Check "ip a", it should say UP for the adapter but I guess it won't.
Follow one of the standard debian guides to bring it up, will involve the /etc/network/interfaces file.
Can be a permission problem, check "ls  -l /dev/EtherCAT0" should say crwxrwxrwx
Try with "sudo service ethercat restart"
Also check "sudo dmesg" the last say 50 lines for anything that can help.

Good to hear, wouldn't surprise me if you change D1 and D2 to X and Z.
That config should be enough to move the axis. Try it.
Then you need to add limit switches and other switches if you have that, spindle control, pendant or gamepad and so on.
Now when linuxcnc is up and running you can easily inspect pins' values using halshow.
The drive and motors are closed-loop I guess, then you will see actual-position change when you rotate the motor shaft, even by just a little if the motors are active.

I think the installation is fine. The system reports POSIX realtime, and the pins for testing are accessible:

Owner Type Dir Value Name
4 u32 OUT 0x00000001 lcec.conf.master-count
4 u32 OUT 0x00000004 lcec.conf.slave-count

When I now call EtherCAT Master, the system reports:

Master0
Phase: Waiting for device(s)...
Active: no
Slaves: 0
Ethernet devices:
Main: 80:ee:73:fd:0f:8b (waiting...)
Link: DOWN

The network adapter is correctly entered in Ethercat.conf:

MASTER0_DEVICE="80:ee:73:fd:0f:8b"
DEVICE_MODULES="generic"

The permissions are also correct:
'KERNEL=="EtherCAT[0-9]", MODE="0777"'

However, I can no longer access the EK1100. The EK is connected to the network and shows no errors. As mentioned, everything worked fine with the same components before the reinstallation.