G32 ERROR

moe.adams9093

M569 P5 S1
M569 P6 S1
M569 P8 S0
M569 P9 S0
Yes this is the correct format for all of my z axis motors 2 motors are mirror to the other 2 thats why I have p8 s0 and p9 s0

fcwilt

@moe-adams9093 said in G32 ERROR:

Yes I did and they all trigger as Z max endstop on m119

Great.

Can you easily remove the bed assembly so we can test each Z stepper one at a time?

Frederick

moe.adams9093

I already did to avoid crashes

moe.adams9093

As I explained driver number 6 on the duex5 works the way it supposed to but when add another endstop to my config.g it won't work like for example and click home Z it won't work only driver 6 even when I added them all

fcwilt

@moe-adams9093 said in G32 ERROR:

I already did to avoid crashes

Great.

Then I would try this.

In you config.g file make duplicate entries for the M584 M350 M92 M566 M203 M201 M906 commands.

Comment out the first set of commands so you can easily return to using them.

In the second set of commands

Change M584 X10 Y11 Z5:6:8:9 E3:4 to M584 X10 Y11 Z5 A6 B8 C9 E3:4
Change the other commands as needed to include the new axes A B and C

This will allow you to access each Z stepper individually (as Z A B or C) using the job buttons in the DWC.

Frederick

moe.adams9093

This post is deleted!

moe.adams9093

@fcwilt Ok what about when I use my Z-Probe and to run G32 how that going work

fcwilt

@moe-adams9093 said in G32 ERROR:

@fcwilt Ok what about when I use my Z-Probe and to run G32 how that going work

The changes I suggested were only for TESTING to verify that each Z stepper on it's own was working as expected with no possible interactions with the other Z steppers.

Once you were sure that they were working then you would restore the original stepper configuration commands.

Frederick

moe.adams9093

Ok make sense thank you

Phaedrux

M574 Z2 S1 P"!exp.e2stop+!exp.e3stop+!exp.e5stop+!exp.e6stop"

Instead of using exp.e#stop let's try using the pin names for the actual deux pins.

duex.e2stop
duex.e3stop
duex.e4stop
duex.e5stop
duex.e6stop

When using these names I think you can remove the !, but please test carefully.

moe.adams9093

@Phaedrux so I did move the ! And did exactly as
M574 Z2 S1 P" duex.e2stop+ duex.e3stop+duex.e5stop+ duex.e6stop"; when I click home Z axis are not moving they do get power but no signal

Phaedrux

And if you check M119 what does the endstop status say?
If it says the z endstop is triggered but the switch isn't pressed, then you would need to add the ! again to invert the signal.

moe.adams9093

@Phaedrux yes thats what I got

2/1/2021, 1:30:18 PM: M119: Endstops - X: not stopped, Y: not stopped, Z: at max stop, Z probe: not stopped

moe.adams9093

I'm going to put ! back and see what's going on

moe.adams9093

The only one is communicating probably is e6stop

moe.adams9093

Its not working. when I added this code
M574 Z2 S1 p"!duex.e6stop+!duex.e5stop+!duex.e3stop+!duex.e4stop";
and run M119

M119
Endstops - X: at min stop, Y: at min stop, Z: no endstop, Z probe: not stopped

but If I remove any one of any of the above endstops

example:
M574 Z2 S1 p"!duex.e6stop+!duex.e5stop+!duex.e3stop";

my M119 will show Z end stop is available I don't know what's causing this issue to not take all 4endstops. also when I press any of the endstops they all stop automatically not individually. I don't know whats happening maybe my duex 5 is bad or if you guys know any solution around please let me know. thank you

moe.adams9093

I believe somehow some of my end stop input on my duex 5 is not responding correctly. can I use stall detection to stop each motor at Zmax. please share your thoughts

alankilian

@dc42 I hate to jump in and be an idiot, but is it because MaxAxes is set to six in the firmware?

fcwilt

@moe-adams9093 said in G32 ERROR:

I believe somehow some of my end stop input on my duex 5 is not responding correctly. can I use stall detection to stop each motor at Zmax. please share your thoughts

I have the same board setup as you - Duet 2 WiFi + Duex5.

On my printer I only have 3 Z steppers so my end stop configuration command is:

M574 Z1 S1 P"!duex.e2stop + !duex.e3stop + !duex.e4stop"

As an experiment I entered this on the DWC Console

M574 Z1 S1 P"!duex.e2stop + !duex.e3stop + !duex.e4stop + !duex.e5stop"

and got this error message:

M574 Z1 S1 P"!duex.e2stop + !duex.e3stop + !duex.e4stop + !duex.e5stop"
Error: M574: Unknown pin name 'duex.e5sto'

Notice the last character, the p, is missing.

I then took that same text and created a gcode file with it in my sys directory.

I executed the file with the M98 command and got the same error.

I then used this text to create another gcode file with it in my sys directory:

M574 Z1 S1 P"!exp.4 + !exp.9 + !exp.14 + !exp.19"

which are alternate names for the pins.

I executed the file with the M98 command and got NO error.

Then I executed from the DWC console a M574 and got this:

Endstop configuration:
X: low end switch connected to pin xstop
Y: high end switch connected to pin ystop
Z: low end switches connected to pins !(exp.e2stop,exp.4) !(exp.e3stop,exp.9,spi.cs6,duex.cs6) !(exp.e4stop,exp.14,spi.cs7,duex.cs7) !(exp.e5stop,exp.19,spi.cs8,duex.cs8)

Notice for Z that all four pins are now present - albeit with all possible names for each pin.

It looks like there may be some sort of command length limitation causing the problem.

I tried this test with both 3.1.1 and 3.2.0.

Try the alternate names and see if they work for you.

Frederick

Phaedrux

@fcwilt Do you get the same error with the original pin names he had used?

M574 Z2 S1 P"!exp.e2stop+!exp.e3stop+!exp.e5stop+!exp.e6stop"