Advanced Search

Any idea of what may be suitable for a new image ?

2.9.7

-If it is a gantry machine with 2 motors on the same axis and 2 switches, it will not jog before homing
-check if the connectors are fully seated, parallel ports tend to seat crooked sometimes
-Does LinuxCNC get out of E-stop and can it be enabled
-do the drives have enable inputs wired
-check the power supply, might reset when drives get enabled and if yes, change the PS as it means the capacitors got dry and failed, do not use
-does the keyboard have arrow keys and are you using those to jog
-check the "Gremlin" the black preview where the parts are drawn, in front of DRO is there any sign
...

I've been away from LinuxCNC for a while. I've been working on other projects. Fired my CNC mill up this weekend but the jog doesn't work and I can't run a program. I thought maybe my parallel port break out board had gone bad but I can move each axis using the "test this axis" feature in the setup wizard. I have a very simple home made machine with only and Estop and no limit switches. Could someone please refresh my memory on some troubleshooting ideas? 

Thanks

Mike 

langdons wrote:

Also, a 10A PSU seems a bit tight for 4 motor drivers!

10A PSU is more than enough for 4 stepper drives/motors.
With some reserve, even at 5A set for each motor (makes 20A), a 5A/36V supply is enough.
@LangdonS, now go read how and why that is possible, instead of posting about stuff you have no experience with.
Then, check if same is true for servo drives, and report back.

Any idea of what may be suitable for a new image ?

I'd like an idea of what to use in the Raspios image I'm working on for Trixie.

Hmm...
That wiring seems correct.

I blame the enable pins.

Me sure the drives are not disabled.

I bought some drivers, wired them up, turned them on, only to realize they did not work and the fault LED came on.

I fixed them by disconnecting the enable inputs.

Powering the enable inputs often disables the drive for some reason!

Maybe shorting the enable inputs together is a good idea, just to make sure there is 0 voltage to disable the driver.

Though why the drives worked with Mach but not LinuxCNC, I can't explain.

So I'm not sure what you need to do for yours, but I had an issue with the pin out of the relay boards wiring. I fixed that and then needed to bypass the estop that was on my pendant as that will not be used anymore. Lastly I needed to press a button that enabled the drives and latched some of the relays on. I would need some .more info probably to help and more than that

Made a quick video of the shop today, while talking, so go have a laugh or two about the crappy accent!

Oh, and do not keep the thoughts in, comment as much as humanly possible as that is what youtube currently uses most as a yard stick.

so sorry for the mumbo-jumbo I created earlier attached is a pdf for the pin locations   

Typical issues with step/dir  not working are wiring or step pulse length being to short

I would make sure the initial step pulse length is at least 5 usec (5000 ns in LinuxCNC)

For the enable (since its active low) I would connect all enable pins to a say 1K pullup resistor
(so they default to being disabled) then connect OUT0+ to all enables and OUT0- to the drive
ground pin

 

2.9.6 is also broken.
And 2.9.5 and 2.9.6 only exist because 2.9.4 is broken.
As it 2.9.3, 2, 1, 0....

As far as I know at the moment 2.9.7 is, at least, broken in unknown ways.

It will be out on Sunday.

Mach was running Via Pokey57CNC. I think I just got tired of Mach, LOL!
the thing with Postep60-256 Enable (inverted, 0=enable, 1=disable).
I am using LINUXCNC 2.9.4 and I am using AXIS for now until I get it up & running, trying to test with 3 axis  with the goal of a total of 6 (gantry has X1 & X2).
using engmate power supply 36V 10A
wiring is as follows: AxisMesa connectorMesa pin (TB1)Mesa signalPoStep60 IDC pinPoStep signalX1 (master)7i96S TB1Pin 3STEP0+IDC Pin 5STEP  Pin 5DIR0+IDC Pin 3DIR  Pin 1 (TB1 GND)GNDIDC Pin 2 (or any GND pins: 2,4,6,8,10)GNDX2 (slave)7i96S TB1Pin 9STEP1+IDC Pin 5STEP  Pin 11DIR1+IDC Pin 3DIR  Pin 7 (TB1 GND)GNDIDC Pin 2GNDY7i96S TB1Pin 15STEP2+IDC Pin 5STEP  Pin 17DIR2+IDC Pin 3DIR  Pin 13 (GND)GNDIDC Pin 2GNDZ7i96S TB1Pin 21STEP3+IDC Pin 5STEP  Pin 23DIR3+IDC Pin 3DIR  Pin 19 (GND)GNDIDC Pin 2GND
for the enable I tried to use TB3 pins 13 (OUT-) connected to pin1 of all 4 drives (enable pin) and pin 14 (OUT+) connected to Mesa GND. 

2.8, 2.9, upcoming 2.10, have no major changes so everything works on all of them, but toolchangers, probes and routines, pendants, are not standard equipment and there is a huge variety of them, so might have issues sometimes.
Even configs from 2.5 and 2.7 work on new version as the included wizard does a good job of changing the required hal and ini entries, but this also fails sometimes as it is impossible to account for all the hardware that LinuxCNC can control.
-
While i am at it, the included wizards, be it changing from old to new versions, or StepConf or PncConf, are magnificent, and i am fully aware of how much work went into them, so whoever worked on them, thank you very much, i am very grateful, although i rarely use them as i am used to editing files manually, but when i do need them they work perfectly.

if -
##Negate Encoder Position
loadrt mult2 count=3
addf mult2.2 servo-thread
loadrt comp count=1
addf comp.0 servo-thread
loadrt and2 count=2
addf and2.1 servo-thread

setp mult2.2.in0 -1.0                    
setp comp.0.in0 0.005                   # Threshold value for encoder
net enable-probe    <=    motion.digital-out-03    =>    and2.1.in1
#
# Encoder position and comparator
net negated-encoder-out <= mult2.2.out
net negated-encoder-out comp.0.in1       # Connect to comparator input
net encoder-threshold-met    <=    comp.0.out   => and2.1.in0

then, when the command is executed -
M64 P3
G38.3 F15 Z0

the machine does not respond to the sensor.

And in the usual configuration -
        net probe-in        <= parport.0.pin-13-in-not
        net probe-in => motion.probe-input

the sensor is triggered, the machine understands this, but sometimes there is an error "non-probe mode"

What am I doing wrong?

Can you show a bit more about how the enables are wired?

What is OUT0+ (TB3 pin 14) connected to?