Advanced Search

Goto the forum section of Installing Linuxcnc.
Click on the sticky for the RPi images.
Read the whole thread. The answers are there.
That's what the purpose of that particular thread is for.

on the surface this appears like it should be correct , but I am not expert with ethercat, far far from it. it appears your checking for the home comparison and setting 0 or 1 based on that result, then issuing a home command if not homed. The next issue obviously will be having linuxcnc call the homing in the driver. Is this to be used as a C axis, if not just have it call the homing function in your postprocessor iirc

forum.linuxcnc.org/10-advanced-configura...7-homing-the-spindle

Ok all. Im stuck and going around and around in circles. So problem: Have two probes for input. Touch-off (pin0) and Probe (Pin2). But I cannot assign 2 pins to the one probe-input. In addition, want to allow for Probe (Pin2) to be rendered inactive when not connected.

Here is the error: probe2-in cannot be found. Comes up on load.

Here is the logic.
ini file has the inputs defined:
INPUT_0_0 = Probe Input
INPUT_INVERT_0_0 = True
INPUT_SLOW_0_0 = False
INPUT_0_1 = E Stop 0
INPUT_INVERT_0_1 = True
INPUT_SLOW_0_1 = False
INPUT_0_2 = Probe Input
INPUT_INVERT_0_2 = True
INPUT_SLOW_0_2 = False

The io.hal file has a set of logic to select the probe input and check the input for active low before it commences. It looks Ok to me. But I have something screwed up as it seems to be that the flipflop cant/wont work as a storage function. So not sure how to get this actioned. Any ideas?

# Inputs
#net probe-input motion.probe-input <= hm2_7i96s.0.inm.00.input-00-not
#net probe-input motion.probe-input <= hm2_7i96s.0.inm.00.input-02-not

# Define probe inputs (Pin 0 and Pin 2)
net probe1-in       hm2_7i96s.0.inm.00.input-00-not      # Tool Touch-off probe (Pin 0)
net probe2-in       hm2_7i96s.0.inm.00.input-02-not      # Edge Finder probe (Pin 2)

# Load logic components
loadrt and2 count=1
loadrt or2 count=1
loadrt flipflop count=1     # Stores Edge Finder connection status

addf and2.0 servo-thread
addf or2.0 servo-thread
addf flipflop.0 servo-thread

# Flip-flop to store the connected state of the Edge Finder (Pin 2)
net probe2-connected  flipflop.0.data <= probe2-in    # Memory for whether Edge Finder is connected
net probe2-connected-state flipflop.0.out             # Store connected state of Edge Finder

# Enable Edge Finder only when connected
net probe2-allowed and2.0.in0 <= probe2-connected-state
net probe2-final and2.0.out  # Final state of Edge Finder   # Allow probe2 (Edge Finder) if connected

# Send final signal to motion.probe-input
net motion-probe or2.0.out => motion.probe-input

Probably I will start with a new installation. Downloading Trixie now.
I think I will need help in "moving" the old configuration to the new one. I will post when help is required. Thank you

it is for EL6751 but it is basically the same ... check my reply maybe it will help U

Sorry for the double post, messed up the formatting of the original one with an edit.

Hello everyone,

I've been trying to set up a DELTA C2000 Plus control drive with LinuxCNC over EtherCAT for a spindle motor and I am having difficulties with the homing (what seems to be the bane of many LinuxCNC users)...

The hal-cia402 driver does not seem to work properly, as the controlword is not being passed correctly and the model does not support CSV mode, which seems to be something the cia402 driver relies on. There is a ready driver for a different, but very similar model, the DELTA MS300. The PDOs are the same, so getting it to run was as easy as changing the pid in the source and recompiling. However, this driver only supports Velocity Mode, even if it works well. Homing Mode is something I am trying to figure out how to implement myself, but sadly I am not well-versed enough to manage on my own.

Would it be a good idea to try to put the following section from the cia402 source into my driver, changing the variable names where appropriate and changing CSV Mode to Velocity Mode:
Do you think this approach is correct? Another thing I've tried is to set it to home over PLC, as the model supports that. But it does not look like it will suit our purposes, as the drive interrupts the EtherCAT connection when switching to PLC mode, which causes unexpected behavior.

I am using the CMC-EC01 extension card for the drive and the homing is intended to be handled by an Origin Switch as the encoder is incremental. I will attach the linuxcnc-ethercat driver for the MS300 for the sake convenience.

Using the EMC-PG01H card for the encoder too, but the encoder is not relevant for the homing. I think. I will tackle that once I get to the spindle orientation...

I appreciate any help and suggestions!

I assumed something was wrong . This is the model: intel 82579lm

The error I get when trying to update : forum.linuxcnc.org/9-installing-linuxcnc...kworm-update-problem

key missing : A94819A7CB97A204

The last command doesn't work. It says the key is missing from the server.
when trying to update only the kernel, it does not find a new version
 

Translations work with 2.10pre0
but i had 4 crashes of linuxcnc with master version so it is not an option..
I don't know if these crashes was hardware related or not.
Generally with master version can have crashes?

I am new to linuxcnc and I cannot get my Raspberry pi running linuxcnc to connect to wifi or to my mesa 7I92TM board. I tried ip a but the mesa board is not showing have looked everywhere online and read multiple forums but can't seem to find a proper solution to my problem. Please help.

Is z encoder output signal and encoded signal to ground needed?

Another thing to think of, what happens when X11 support is dropped in favour of Wayland ?
The GUIs that rely on X11 libs.

Tho it received no interest apart from 2 forum members I managed to build a Devuan ARM image, no systemd and their CoC is fair to all, basically just don't be a dick to anyone.

Sounds about right for Bookworm.

Trixie for ARM might be an issue as libgpiod version Trixie uses will require some effort with the hal_gpio driver, maybe a rewrite.
Andy is the expert on this, pretty sure he made a note of this some time ago.
Apart from that the ARM image is fine.

Not sure, but i think RT 6.8.n was installed last i used Debian 12, so ....

I ended up buying it because it was $103 and had a SSD as well.

7I97T     DRIVE CN1
AOUTN   AS+ (26)
GND       GNDA (11)
ENAN+  SON  DI1 (16)
ENAN-    24V Common
INN         RDY  DO1 (20)
INCOM    +24V  (Drive output common 24V common)   

QAN+       OA+  (13)
QAN-         OA-   (28)
QBN+       OB+  (14)
QBN-         OB-  (29)
QIDXN+    OZ+ (15)
QIDXN-      OZ-  (30)