G32 ERROR

alankilian

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

fcwilt

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"

fcwilt

@Phaedrux said in G32 ERROR:

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

Hold on and I will try.

Frederick

Phaedrux

@alankilian said in G32 ERROR:

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

It shouldn't because in RRF3 you can use multiple endstops on a single axis. No need to create additional axis anymore.

fcwilt

@Phaedrux said in G32 ERROR:

@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"

That works.

Frederick

Phaedrux

@fcwilt Hmm, wonder why it didnt work for him the first time?

fcwilt

@Phaedrux said in G32 ERROR:

@fcwilt Hmm, wonder why it didnt work for him the first time?

I have no idea - this topic has gotten rather long and it's hard to remember it all.

Those names you suggested are shorter by one character each which tends to reinforce the idea of a command length limitation.

Perhaps you could speed verification of this possibility with direct communication with dc42?

Frederick

Phaedrux

@moe-adams9093 said in G32 ERROR:

can I use stall detection to stop each motor at Zmax. please share your thoughts

Yes. M574 Z2 S4. But you'll have to do the usual stall detection tuning.

Phaedrux

@fcwilt said in G32 ERROR:

Perhaps you could speed verification of this possibility with direct communication with dc42?

He's aware. But also asleep at the moment I'd wager.

fcwilt

@Phaedrux said in G32 ERROR:

He's aware. But also asleep at the moment I'd wager.

I have little idea of who lives where.

My hours are so erratic I'm not sure what time zone I'm supposed to be in.

Frederick

moe.adams9093

Sorry It's US central Time Here maybe we are 8 hours difference.

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

it's not working at all.

Phaedrux

Can you try testing on 3.1.1?

It's easy to switch between. Upload this zip file to the system tab. No need to change the config file.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip

moe.adams9093

so you dont thing the duex 5 is bad

M574 Z2 S1 P"!exp.e2stop+!exp.e3stop+!exp.e5stop+!exp.e6stop"
and run m119 it will show the endstop is triggered at max

moe.adams9093

@Phaedrux curently Im on 3.1.1

moe.adams9093

@Phaedrux said in G32 ERROR:

Yes. M574 Z2 S4

so if I can use M574 Z2 S4 how can split the axis and make one at a time when they hit max location. if you have documentation on that please share it

fcwilt

@moe-adams9093 said in G32 ERROR:

M574 Z2 S1 P"!exp.e2stop+!exp.e3stop+!exp.e5stop+!exp.e6stop"
and run m119 it will show the endstop is triggered at max

That result indicates that one or more of the end stop sensors is triggered.

If you could do the following we can find out if one of the end stop sensors is perhaps not working correctly.

From the DWC console if you issue the M574 to configure just a single end stop the M119 will report it's state independent of any others.

M574 Z2 S1 P"!exp.e2stop"
M119

M574 Z2 S1 P"!exp.e3stop"
M119

M574 Z2 S1 P"!exp.e5stop"
M119

M574 Z2 S1 P"!exp.e6stop"
M119

If would be very helpful to verify that each end stop sensor is working.

Thanks.

Frederick

moe.adams9093

@fcwilt ok I Will try that now thanks for keeping up with me I truly appreciated

moe.adams9093

@fcwilt I just tried that still same when I do that it will say M119 All at max and they are not even triggered it the same even if I keep ! or I remove. I know for a fact all my endstops function probably because I did install them on the X and Y and they all worked correctly

fcwilt

@moe-adams9093 said in G32 ERROR:

@fcwilt ok I Will try that now thanks for keeping up with me I truly appreciated

Sometimes the only way to track down a problem is to approach it one little bit at a time.

We have seemingly discovered an interesting issue with the firmware having difficulty in processing long commands. I've been using 3.1.1 for months and I have never encountered the issue simply because nothing I did needed a long command like that. And now finally we are aware of the issue.

As you may recall one of my printers has three Z steppers with end stop sensors. Homing worked just fine under 3.1.1.

I recently upgraded the printer to 3.2.0 and almost immediately began having homing problems where one of the steppers would keep moving even though the end stop sensor had been triggered (they have LEDs).

I've only begun testing and need to do much more but out of 5 homing attempts 3 failed as described above.

As part of my testing I reverted to 3.1.1 and 5 out of 5 homing attempts worked.

I'm confident I will get it sorted and I am equally confident we will get your problem sorted.

Frederick