Issues after recent upgrade to v61

I just upgraded my Taz6
from Marlin_Oliveoil_TAZ6Archim_Tilapia_SingleExtruder_bugfix-2.1.x.1 v58
to Marlin_Oliveoil_TAZ6ArchimBLTouch_Tilapia_SingleExtruder_bugfix-2.1.x.1 v61

First, THANK YOU!! Having this firmware available and having the Wiring Diagram for the Archim is a marvelous thing.

However, in playing with the new system I’ve “discovered” a couple of issues:

  1. All the max-stops no longer work; X, Y, or Z. Z crashes are particularly annoying since they screw up the tramming.

  2. The printer is MUCH louder than it was on the older software. Am I missing a setting somewhere to re-enable “stealth mode”?

Thanks for any help you can provide!
GK

Yeah, Marlin upstream has removed support for max end-stops. They don’t seem to feel the functionality is a priority, so I recommend you voice your opinions here:

For the time being, you can continue to use Drunken Octopus version 59, which is the latest version which supports max endstops.

Can you also let me know whether 59 also sounds louder? That way we can narrow down which version introduced the change. Thank you.

Oh, it looks like this might have been merged. I’ll have to see if the functionality is enabled.

Hi gregket1, I have made a new release of Drunken Octopus which enables the new X_SAFETY_ENDSTOP, Y_SAFETY_ENDSTOP, and Z_SAFETY_ENDSTOP features in Marlin. Let me know if this solves the endstop issue.

I have not been able to investigate the noise issue, but if you could run a M122, TMC Debug on both the quiet and the noisy builds, then we can narrow down what might have changed.

I just updated my TAZ 6 (Single Extruder) to v62 and tried an M122:

Send: M122
Recv: echo:Unknown command: "M122"
Recv: ok P15 B4
Send: N1 M115*39
Recv: FIRMWARE_NAME:Marlin bugfix-2.1.x (Aug 19 2023 12:20:50) SOURCE_CODE_URL:https://github.com/marciot/drunken-octopus-marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:TAZ 6 EXTRUDER_COUNT:1 UUID:845f003c-aebd-4e53-a6b9-7d0984fde609

I’ll test the endstops next…

X, Y, Z Min and Max endstops work. But G29 V4 fails. I’ll open a separate issue for this one.

Sorry for the delay.

v61 output

Send: M122
Recv: 		X	Y	Z	E
Recv: Enabled		false	false	false	false
Recv: Set current	975	975	975	750
Recv: RMS current	974	974	974	738
Recv: MAX current	1373	1373	1373	1041
Recv: Run current	18/31	18/31	18/31	25/31
Recv: Hold current	9/31	9/31	9/31	12/31
Recv: CS actual	9/31	9/31	9/31	12/31
Recv: PWM scale	0	0	0	0
Recv: vsense		0=.325	0=.325	0=.325	1=.18
Recv: stealthChop	false	false	false	false
Recv: msteps		16	16	16	16
Recv: interp		true	true	true	true
Recv: tstep		max	max	max	max
Recv: PWM thresh.
Recv: [mm/s]
Recv: OT prewarn	false	false	false	false
Recv: triggered
Recv:  OTP		false	false	false	false
Recv: off time	3	3	3	3
Recv: blank time	24	24	24	24
Recv: hysteresis
Recv:  -end		-2	-2	-2	-2
Recv:  -start		6	6	6	6
Recv: Stallguard thrs	0	0	0	0
Recv: uStep count	8	8	8	8
Recv: DRVSTATUS	X	Y	Z	E
Recv: sg_result	0	0	0	0
Recv: stallguard
Recv: fsactive
Recv: stst
Recv: olb
Recv: ola
Recv: s2gb
Recv: s2ga
Recv: otpw
Recv: ot
Recv: Driver registers:
Recv: 		X	0x80:09:00:00
Recv: 		Y	0x80:09:00:00
Recv: 		Z	0x80:09:00:00
Recv: 		E	0x80:0C:00:00
Recv: 
Recv: 
Recv: Testing X connection... OK
Recv: Testing Y connection... OK
Recv: Testing Z connection... OK
Recv: Testing E connection... OK

After going through the various versions of DO and mapping the hashes to versions it turned out that the quiet version I was using was v53, not v58. Here is the data for v53.

v53

Send: M122
Recv: 		X	Y	Z	E
Recv: Enabled		false	false	false	false
Recv: Set current	975	975	975	750
Recv: RMS current	974	974	974	738
Recv: MAX current	1373	1373	1373	1041
Recv: Run current	18/31	18/31	18/31	25/31
Recv: Hold current	9/31	9/31	9/31	12/31
Recv: CS actual	9/31	9/31	9/31	12/31
Recv: PWM scale	0	0	0	0
Recv: vsense		0=.325	0=.325	0=.325	1=.18
Recv: stealthChop	false	false	false	false
Recv: msteps		16	16	16	16
Recv: interp		true	true	true	true
Recv: tstep		max	max	max	max
Recv: PWM thresh.
Recv: [mm/s]
Recv: OT prewarn	false	false	false	false
Recv: triggered
Recv:  OTP		false	false	false	false
Recv: off time	3	3	3	3
Recv: blank time	24	24	24	24
Recv: hysteresis
Recv:  -end		-2	-2	-2	-2
Recv:  -start		6	6	6	6
Recv: Stallguard thrs	0	0	0	0
Recv: uStep count	24	1016	1016	1016
Recv: DRVSTATUS	X	Y	Z	E
Recv: sg_result	0	0	0	0
Recv: stallguard
Recv: fsactive
Recv: stst
Recv: olb			*	*	*
Recv: ola
Recv: s2gb
Recv: s2ga
Recv: otpw
Recv: ot
Recv: Driver registers:
Recv: 		X	0x80:09:00:00
Recv: 		Y	0xC0:09:00:00
Recv: 		Z	0xC0:09:00:00
Recv: 		E	0xC0:0C:00:00
Recv: 
Recv: 
Recv: Testing X connection... OK
Recv: Testing Y connection... OK
Recv: Testing Z connection... OK
Recv: Testing E connection... OK

The only differences I can find are the microsteps and the OLB settings:

v53

Recv: uStep count	24	1016	1016	1016
Recv: olb			*	*	*
Recv: ola

v61

Recv: uStep count	8	8	8	8
Recv: olb
Recv: ola

The OLB is not relevant, but the uStep count may be. I’ll need to investigate why that changed. Thank you for the info.

@gregket1 @b-morgan and I have managed to successfully correct a other issue by doing a binary search for the problem. I think the same approach might work in this case. Since the output of M122 changed from v53, I think I can try narrowing it down myself, but I will let you know if I need your assistance.

@gregket1 I just loaded up v53, did a “Restore Defaults” followed by a M122 and it showed “Recv: uStep count 8 8 8 8”

Hence, if the uStep were anything else, it would have been in an earlier release. Please go back through the various previous releases, do a “Restore Defaults” and power cycle your printer. Once you find a firmware where the noise issue is resolved, let me know and I can try working forwards from that point.

I tried different firmware versions going back to r33, and the uStep count is inconsistent and varies quite widely. Even restarting the board changes the value. So I believe that might be a step counter, rather than a configuration parameter that would affect the noise.

@gregket1 You could also check Configuration → Main → Advanced Settings → TMC Drivers → Stepping Mode. It’s possible you had manually enabled Steathchop and then when you upgraded it cleared the ROMs and restored them to the off state.

I just got back from a trip. I’ll take a look in the next couple days.