G32 ERROR

[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

[fcwilt]

@moe-adams9093 said in G32 ERROR:

@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

I don't understand what you mean when you say "M119 ALL at max" - I am only interested in the status of Z.

And you did just configure one at a time? The presence or absence of the ! should most assuredly make a difference.

Frederick

[fcwilt]

@moe-adams9093 said in G32 ERROR:

@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

Refresh my memory - what sort of end stop sensor hardware do you have on Z?

Thanks.

Frederick

[moe.adams9093]

they are normally close FYSETC and they are exactly the same as my X&Y EndStops they have 3 pins V G S

[Phaedrux]

@moe-adams9093 said in G32 ERROR:

@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

That's the point of S4. Stall detection for each motor independently. Check the wiki entry for m574

[moe.adams9093]

@dc42 could you please take a look at this problem I'm currently facing I will post the latest config files here to make it short as possible and not to have to go to the previous threads.

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Oct 13 2020 21:14:55 GMT-0500 (Central Daylight Time)
 
; General preferences
G90                                                     	; send absolute coordinates...
M83                                                     	; ...but relative extruder moves
M550 P"DIVINCI-3D (MP4560)"                             	; set printer name
M669 K1                                                 	; select CoreXY mode
 
; Network
M552 P0.0.0.0 S1                                        	; enable network and acquire dynamic address via DHCP
M586 P0 S1                                              	; enable HTTP
M586 P1 S0                                              	; disable FTP
M586 P2 S0                                              	; disable Telnet
 
; Drives
M569 P10  R1 T2:2:2:2  S1  									; physical drive 0 goes forwards
M569 P11  R1 T2:2:2:2  S1  									; physical drive 1 goes forwards
M569 P3 S1                                             		; physical drive 3 goes forwards
M569 P4 S1                                              	; physical drive 4 goes forwards
M569 P5 S1                                              	; physical drive 5 goes Backwards
M569 P6 S1 													; physical drive 6 goes Backwards
M569 P8 S0			          								; physical drive 7 goes Backwards 
M569 P9 S0                                              	; physical drive 9 goes backwards 
M584 X10 Y11 Z5:6:8:9 E3:4                              	; set drive mapping
M671 X5.0:455.0:455.0:5.0 Y25.0:25.0:455.0:455.0 S14    	; ZBelts Near Locations                    
M350 X32 Y32 Z16 E16:16 I1                              	; configure microstepping with interpolation
M92 X80.00 Y80.00 Z410.00 E415.00:415.00 					; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00:120.00              	; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z400 E1200.00:1200.00        		; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z40.00 E250.00:250.00           		; set accelerations (mm/s^2)
M906 X1800 Y1800 Z1000 E500:500 I30                     	; set motor currents (mA) and motor idle factor in per cent
M84 S30                                                 	; Set idle timeout
 
; Axis Limits
M208 X0 Y0 Z0 S1                                        	; set axis minima
M208 X460 Y460 Z460 S0                                  	; set axis maxima
 
M574 X1 S1 P"!xstop"                                    		; configure active-high endstop for low end on X via pin !xstop
M574 Y1 S1 P"!ystop"                                    		; configure active-high endstop for low end on Y via pin !ystop
M574 Z1 S2 														; configure Z-probe endstop for low end on Z  
M574 Z2 S1 P"!exp.e2stop+!exp.e3stop+!exp.e5Stop+!exp.e6stop"	; configure active-high endstop for High end on Z via pin !ystop
 
; Z-Probe
M558 P1 C"zprobe.in" H25 F600 T6000                      	; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z2.5                                     	; set Z probe trigger value, offset and trigger height
M557 X20:440 Y20:440 S20                                	; define mesh grid
 
 
; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4725 C7.06e-8 	; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                                   	; create bed heater output on bedheat and map it to sensor 0
M307 H0 A11 C99000 D2000 B1                  				; enable bang-bang mode for the bed heater and set PWM limit
M140 H0                                                 	; map heated bed to heater 0
M143 H0 S120                                            	; set temperature limit for heater 0 to 120C
M308 S1 P"spi.cs1" Y"thermocouple-max31856"             	; configure sensor 1 as thermocouple via CS pin spi.cs1
M950 H1 C"e0heat" T1                                    	; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                                        	; disable bang-bang mode for heater  and set PWM limit
M308 S2 P"spi.cs2" Y"thermocouple-max31856"             	; configure sensor 2 as thermocouple via CS pin spi.cs2
M950 H2 C"e1heat" T2                                    	; create nozzle heater output on e1heat and map it to sensor 2
M307 H2 B0 S1.00                                        	; disable bang-bang mode for heater  and set PWM limit
M308 S3 P"duex.e2temp" Y"thermistor" T10000 B3950       	; configure sensor 3 as thermistor on pin duex.e2temp
M950 H3 C"duex.e2heat" T3                               	; create chamber heater output on duex.e2heat and map it to sensor 3
M307 H3 A11 C99000 D2000 B1                             	; enable bang-bang mode for the chamber heater and set PWM limit
M141 H3                                                 	; map chamber to heater 3
 
; Fans
M950 F0 C"fan0" Q500                                    	; create fan 0 on pin fan0 and set its frequency
M106 P0 S1 H-1                                          	; set fan 0 value. Thermostatic control is turned on                           
M950 F1 C"fan1" Q500                                    	; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H2 T45                                       	; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q500                                    	; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H1:2 T45                                     	; set fan 2 value. Thermostatic control is turned on
 
; Tools
M563 P0 S"MAIN EXTRUDER" D0 H1 F0                       	; define tool 0
G10 P0 X0 Y0 Z0                                         	; set tool 0 axis offsets
G10 P0 R0 S0                                            	; set initial tool 0 active and standby temperatures to 0C
M563 P1 S"SECOND EXTRUDER" D1 H2 F0                     	; define tool 1
G10 P1 X0 Y0 Z0                                         	; set tool 1 axis offsets
G10 P1 R0 S0                                            	; set initial tool 1 active and standby temperatures to 0C
 
; Custom settings are not defined
 
; Miscellaneous
M575 P1 S1 B57600                                       	; enable support for PanelDue
M501                                                    	; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"      	; set voltage thresholds and actions to run on power loss
T0                                                      	; select first tool
 
 

The endstops I have are normally close Active low. when I run my M119 I get this message

2/1/2021, 10:27:05 PM: M119: Endstops - X: not stopped, Y: not stopped, Z: at max stop, Z probe: not stopped
 

even if I remove my( !) on M574 Z2 S1 code still the same M119 Message.

here's my homeall.g files

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Oct 13 2020 21:14:55 GMT-0500 (Central Daylight Time)
G91                     ; relative positioning
G1 H1 Z500 F6000          ; lift Z relative to current position
G1 H1 X-465 F8000 ; move quickly to X endstop and stop there (first pass)
G1 H1 Y-465 F8000 ; move quickly to Y endstop and stop there (first pass)
G1 H2 X5 Y5 F6000       ; go back a few mm
G1 H1 X-465 F360        ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-465 F360        ; then move slowly to Y axis endstop
G1 H2 Z-500 F6000;
G1 X235 Y235 F6000      ; Prob at Center 
M558 F600 A1 		    ; Dive fast once 
G30			            ; probe Z
M558 F300 A10 		    ; Slow second dive with more accuracy
G30			            ; probe z again
 

so the purpose here all I want when I press home all I want the bed to go to the max side and trigger all 4 endstops to stop all 4 Z axis individually, then to travel back to the Min side and prob using DC42 IR Sensor and home all at the min side.

[Veti]

@moe-adams9093 said in G32 ERROR:

M350 X32 Y32 Z16 E16:16 I1 ; configure microstepping with interpolation

the duet 2 only supports interpolation at x16. so this statement is incorrect

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

you have a mistake you wrote e5S and e6s

[moe.adams9093]

That's not the issue this I mistakenly uploaded a back up file if you look up on my previous thread I have the correct file even Phaedrux moderator checked it

[dc42]

@fcwilt said in G32 ERROR:

@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

The string buffer that holds the pin name in commands that require a pin name has a limited length. AFAIR it's 50 characters. Does that explain it?

As usual, running M98 P"config.g" should reveal if this is causing a problem.