Advanced Search

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

In case this happens to anyone else, I reached out to Mesa and they replied back quickly. They offerred to fix the card for free if under warranty, for a small fee if not. Unfortunately shipping is more costly than card since I live in Turkey, therefore I decided to scrap the card.

I ordered 3 new 7i96S for 2 of my machines and 1 backup. I only need few inputs, thank you for taking the time.

I struggle to find an electric unloader valve
on all of them it states for oil less compressors. Does that mean the seals will deteriorate from compressor oil? Or is it nothing to worry about?

 

This is with int graphics

Done, thank you, i will delete this and the one above this after you get a chance to read it to keep this topic clean.

AMD still has driver support on Linux for the 500 series gpus. I'll try using my integrated graphics but it hasn't worked before. Which is why I have a card in the first place.

Amd readeon RX560

Non-existant user wrote:

Should we delete the two duplicate replies above without the quoted text?

Yes please, i tried it myself but i guess that is not possible. Thanks!

OpenGL issues, what graphic card does the PC use?
Can it be removed? If yes, remove it and test with the onboard video.

PCW wrote:

if estop-latch.N.ok-out goes false, one of these must have changed:

estop-latch.N.ok-in  goes false
estop-latch.N.fault-in goes true

So I would watch these in halshow or halscope to see whats happening.

I also don't understand why you have two estop latches. It seems that one
should be sufficient (adding some logic if you need to add fault inputs or OK inputs)

 

Hi, thank you for your quick reply. I have been looking at these halshow/scope bits but could not get it to click.

I have tried with two latches, with the idea that one will be for external estop (input 00) and the other for software internal estop (user enable out).
I also tried with one, linking the ok-in for user-enable out and fault-in to input00 external estop. No succes.

I will keep trying, thanks.

If you have any more sugestions i would be happy to hear them.

Unlogic wrote:

I documented my e-stop setup using an external safety relay in the post linked below:

forum.linuxcnc.org/12-milling/50559-opti...rsion?start=0#284533

Maybe it will help you get your setup up and running.

 

Hi, thank you for your reply. I have read your documents on your build, very impressive, thanks for the detailed sharing and documenting.
I saw you used the oneshot function, i have tried implementing it like you did but no succes. I will try again once i got the time.

Thanks, cheers

This solution worked, but when i try to start my cnc file, it gives me an error. error report in the attached file.