Advanced Search

jjdege wrote:

Hi guys

I couldn't resist and bought a new board, this time I opted for a 3-axis EC500,
it has LEDs that indicate the I/O status, I think it's more complete.

I tested it with Mach3 to make sure it was working well, given the previous ones,
and it worked on all three axes.

When loading the firmware, it got to 29% and timed out and everything froze,
the DAP wasn't receiving signals.
I reread page 115 of the thread that talks about how to unlock and after having
bridged BOOT_MO and 3V3 I managed to delete and write the new firmware!!

Now all 6 axes work.

Thanks again to Scott and to whoever made all this possible.

Hi
I connected to a small laser gantry structure the EC500 with Remora
and a small demo video .
I have to say it works great!!!
Thanks!

THANKS!!! WORKS!

Now i understand, because they are isolated you need to connect the common pin to a GND reference point to the voltage that will be applied to the input 1-11 pins. I connected everything as you said and it works flawlessly. !!!!

This feels like a bigger achievement than getting my Master's degree haha.

The isolated inputs will not work as expected unless you connect the
input common (TB3 pin 12)

For sinking inputs (pullup to a positive voltage to activate), input common should be
connected to  GND/power common. If you are using 5V from the 7I96S, this is the
stepgen connector GND.

And yes if you use a 24V supply and sinking inputs, the 7I96S input common would
connect to the 24V supply common (negative)
 

Thank you very much.

I don't understand how this is different from what I am trying. here is the setup:

Switch NC to 5V from one of the pins (would it be okay to plug it in the stepper motor DC 24 power supply?)

Switch C to PIN 1 TB3.

IN this case I am missing the TB3 common pin - will it work if I connect it to the GND from the MESA where I am getting the 5V will it work? It is not working as it is right now.

Eitherway if you say it is safe I will connect the DC power supply 24V to the limit switch NC then C switch to TB3 pin and I can connect the Common TB12 pin to the Power supply DC GND.

If you use NC limit switch contacts and sinking inputs, wiring would be:

7I96S input common (TB3 pin 12) = GND (24V common)

+24V --> Limit-Switch C --> Limit-Switch NC --> 7I96S Input (TB3 pin 1 through 11)

In hal, the input must be inverted.

You can use 5V instead of 24V but it's not as reliable long term with mechanical switches

 

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?