Advanced Search

for your parport input you could use eg 'motion.digital-in-00'
linuxcnc.org/docs/html/man/man9/motion.9.html

in your hal you would connect the two pins like this:

in your ngc remap you would then use M66 P0 .. to interact with your input:
linuxcnc.org/docs/html/gcode/m-code.html#mcode:m66

Why are the spindle control buttons not visible in AXIS?

loadrt or2
addf or2.0 servo-thread
net probe-touchprobe or2.0.in0 <= hm2_7i76e.0.7i76.0.0.input-08
net probe-toolsetter or2.0.in1 <= hm2_7i76e.0.7i76.0.0.input-09-not
net probe-input motion.probe-input <= or2.0.out

this is about the simplest or2 use for two inputs to motion.probe-input, in this method you would want to use a 3pin touch probe connection jack so that when you unplug the touch probe the jack closes the circuit which takes the input out of triggered state.

something like this maybe and jumper when plug is removed the jack closes.

www.amazon.com/MEETOOT-5-5mm-Female-Sock...trical/dp/B09JP19XKP

Hello, I'm new here too, but I've had to deal with the topic intensively recently.
You can create the ethercat_conf.xml very roughly if you run "ethercat xml" and then copy what is displayed into the XML.

You can then load the XML for testing purposes with "halcmd loadusr -W lcec_conf ethercat_conf.xmf". Now run "halcmd lcec" and then you can use "halcmd show" to see whether it is displaying the variables.

As long as the ethercat master is still idle, you will unfortunately not see any content.

To do this, you have to put together a small dummy machine somehow. Then

addf lcec.read-all servo-thread

addf lcec.write-all servo-thread

must appear in the .hal file so that the values ​​are queried. then look for a machine ini from the demos (which also contains your hal file) and

then start linuxcnc **.ini

if that works, "ethercat master" will show you Phase: operation at the top and you can also look at the values ​​with halcmd show.

I hope that helps a little.

Hallo cmorley, große Klasse! Dein Script funktioniert auf Anhieb und ich bin glücklich über diese Vereinfachung! Danke danke!

Thanks for the reply, now I'm trying to do something via remap but I'm not sure I'm doing it right. I can't figure out how to interact with pin 17 on port 0.So far there is this outline of the remap, I would appreciate it if you could point out any errors.Thanks for the links, I'll have a look.

thank you for the guide. i am looking into it and so far it seems promising. i might have some questions down the line when i start building my g-code around the suggested solution.

Hi,

Which version of LinuxCNC is recommended for the MESA 7i96s (for a beginner user) in late 2024 / '25?

Debian 10 (Buster) + 2.8.4 has a few very good youtube beginner tutorials.  Is Buster + 2.8.4 still a reliable and recommended install?

A forum search on 7i96s + 2.9 seems mainly to be posts of people with issues getting 2.9 working reliably ...

I'd just like whichever solution is easiest to get up and running reliably!

Thanks

     

Have a look at the halui.program.* halpins:
linuxcnc.org/docs/html/man/man1/halui.1.html

Depending on the gui you are using it may provide its own hal pins to steer program execution.

You need only to lower the voltage a little bit for the Level-Shifter with a Diode or two Resistors,
the FPGA can handle up to 3.3V input and the Level-Shifter need to detect 1.8V as high.

but after applying G54 on X, it becomes a mess:

This issue is a known limitation of the feature. Please read paragraph 11 the documentation I posted above.

I hope this video will make more clear what is happening, I have no issue with g-code from CAM, machined parts are ok, only display section is a bit off in my case:

Hello, i am new to the linuxCNC systems.

I wish to build a simple rotating axis controlled by linuxcnc gcode. And i have a external robot which would perform some machining operations on the rotating part.

Now i want to sync both the machines. such that when i start the robot, the linuxcnc should also start executing the gcode.

Is it possible to execute the gcode when an input is provided through one of the parallel port input pins?
does the M66 code work here?
how to then pause the program if i pause the action of the robot (incase i have to e-stop the robot) and how to make sure then that the gcode is resumed from the paused location once the robot restarts and sends execution trigger to the linux cnc.

tommylight wrote:

A shot from the hip, but usually those drive/steppers will have wrong encoder wiring, would be prudent to double check.
 

Hi tommylight,

It just so turned out you were right: one of my encoder wire were loose, I tightened it on the CL57T-V41 driver and it behaves now.

This is the wiring diagram:




My References for the Wiring Diagram:

1.

From 34:14 CL57T Driver Overview.

2. help.stepperonline.com/en/article/wiring...tepper-motor-4cddqy/

The first CL57T diagram.

3. pypi.org/project/cl57t-raspberry-pi-stepper-drive/

See the table for signal pins to the Raspberry Pi 4B.

And I have learned to work the ENA+ pin: setting it to low to enable, to high to disable.

The Python code below turns the motor 1 revolution, pauses for a little then keeps on turning till Control C to stop.

If I changed [ gpio.output( ena_pin, gpio.LOW ) ] to [ gpio.output( ena_pin, gpio.HIGH ) ] the motor won't turn.

Now I am trying to figure out why I need 1600 to do one revolution, it is about how the DIP switches are set, I have to understand the table in the manual

Thank you and best regards,

...behai.

[
# 08/11/2024
#
# Enable by setting ENA+ pin to low. Expected: motor will run.
#
# /usr/bin/python3 nema23_04_ena_enabled.py
#
from time import sleep
import RPi.GPIO as gpio

direction_pin   = 13
pulse_pin       = 6
ena_pin         = 19
cw_direction    = 0
ccw_direction   = 1

gpio.setmode( gpio.BCM )
gpio.setup( direction_pin, gpio.OUT )
gpio.setup( pulse_pin, gpio.OUT )
gpio.setup( ena_pin, gpio.OUT )
gpio.output( direction_pin, cw_direction )

# Enable.
gpio.output( ena_pin, gpio.LOW )
# ENA pin must be ahead of DIR by at least 200ms.
sleep( 0.5 )

try:
    while True:
        print( 'Direction CW' )
        sleep( .5 )
        gpio.output( direction_pin,cw_direction )
        for x in range( 1600 ):
            gpio.output( pulse_pin, gpio.HIGH )
            sleep( 0.0001 )
            gpio.output( pulse_pin, gpio.LOW )
            sleep( 0.0001 )

except KeyboardInterrupt:
    # Disable.
    gpio.output( ena_pin, gpio.HIGH )
    gpio.cleanup()
]

 

This may be of interest:

github.com/LinuxCNC/linuxcnc/issues/2716
github.com/LinuxCNC/linuxcnc/pull/2722/files