Strange bugs 3.3beta2

Phaedrux

@Dep said in Strange bugs 3.3beta2:

M98 P"/macros/Move/bed_level_points"

What's in that macro?

@Dep said in Strange bugs 3.3beta2:

M98 P"homex.g" M98 P"homey.g"

Can you share these as well?

Can you also share the results of sending M98 P"config.g" and share your slicer start gcode.

Dep

@Phaedrux оf course

bed_level_points :

G30 P0 X-473 Y500 Z-99999 ;P0 - Probe point 0 (not drive)
G30 P1 X473 Y500 Z-99999
G30 P2 X473 Y-500 Z-99999
G30 P3 X-473 Y-500 Z-99999 S4 ;set correction

homex.g

; homex.g
; called to home the X axis
;

while iterations < 2
  if iterations < #sensors.gpIn && sensors.gpIn[iterations] != null && sensors.gpIn[iterations].value = 0
    M291 S1 T5 P{"Please return tool "^iterations^" to dock before homing"} R"Cannot home"
    abort


G91              	; relative positioning
M400 				; make sure everything has stopped before we change the motor currents
;M913 Z80	 		; drop motor currents to 20%
G1 H2 Z5 F6000 		; lift Z relative to current position
;M913 Z100	 		; motor currents to 100%
G1 H1 X-1200 F6000 	; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F6000  	; go back a few mm
G1 H1 X-1200 F360  	; move slowly to X axis endstop once more (second pass)
G1 H2 X5 F6000 	; move away from end
G1 H2 Z-5 F6000  	; up Z again
G90              	; absolute positioning

homey.g

; homey.g
; called to home the Y axis
;

while iterations < 2
  if iterations < #sensors.gpIn && sensors.gpIn[iterations] != null && sensors.gpIn[iterations].value = 0
    M291 S1 T5 P{"Please return tool "^iterations^" to dock before homing"} R"Cannot home"
    abort

if !move.axes[0].homed 
      M98 P"homex.g"

G91                ; relative positioning
M400 				; make sure everything has stopped before we change the motor currents
;M913 Z80	 		; drop motor currents to 20%
G1 H2 Z5 F6000 		; lift Z relative to current position
;M913 Z100	 		; motor currents to 100%
G1 H1 Y1205 F6000  ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y-5 F6000      ; go back a few mm
G1 H1 Y1205 F360   ; move slowly to Y axis endstop once more (second pass)
G1 H2 Y-50 F6000  	; move away from end
G1 H2 Z-5 F6000     ; up Z again
G90                 ; absolute positioning

Slicer (S3D) start code:

; START code
M140 S[bed0_temperature]
M106 S0 ;fan off
G92 E0; reset extruder distance
G28
T0 ; Select tool 0
M116
G10 P0 S[extruder0_temperature] R160
M116
M98 P"/macros/Purge Filament"
;---  end start gcode ---

Dep

@Phaedrux said in Strange bugs 3.3beta2:

M98 P"config.g"

18.03.2021, 22:24:45	M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

Phaedrux

@Dep said in Strange bugs 3.3beta2:

M376 H20 ; bed compensation taper

With a taper set the amount moved to compensate is diminished over the duration of the print and for small amounts can make it very hard to see.

Can you post a screenshot showing your heightmap?

How often do you re-create the heightmap?

Dep

I've done it many times. The print shows that the compensation does not work. I also attach a long stick to the pulley to check if there is movement or not.

If necessary, I can shoot a video.

Dep

@Phaedrux said in Strange bugs 3.3beta2:

@Dep said in Strange bugs 3.3beta2:

M376 H20 ; bed compensation taper

With a taper set the amount moved to compensate is diminished over the duration of the print and for small amounts can make it very hard to see.

I've tried disabling taper. M376 H0
Nothing changes.

jay_s_uk

add G29 S1 after the G28 in your start script

Dep

@jay_s_uk It is added:

homeall.g (G29 S1 here)

; homeall.g
; called to home all axes
;
M98 P"homex.g"
M98 P"homey.g"
M98 P"bed.g"
G29 S1

jay_s_uk

@Dep ah, missed that

Phaedrux

All I can think is that the conditional gcode in your homing files is skipping something.

Can you try adding G29 S1 to your slicer start gcode after the purge filament macro?

Then check if mesh compensation is active in M122 during the print and see if the Z axis is moving.

OwenD

Could it be that you're not homing Z after you run bed.g ?

Phaedrux

@OwenD said in Strange bugs 3.3beta2:

Could it be that you're not homing Z after you run bed.g ?

Bed.g is getting called as part of homeall. bed.g calls homez.

Dep

The oddities continue. Now there is a problem with the filament monitor: min -5% and printing continues:

20.03.2021, 10:39:40	M591 d0
Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 131 agc 107, measured sensitivity 25.37mm/rev, min -5% max 105% over 153582.5mm
20.03.2021, 10:32:45	M591 d0
Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 131 agc 107, measured sensitivity 25.36mm/rev, min -5% max 105% over 151673.8mm
20.03.2021, 10:25:49	M591 d0
Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 131 agc 107, measured sensitivity 25.36mm/rev, min -5% max 105% over 149761.4mm
20.03.2021, 10:22:38	M591 d0
Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 131 agc 107, measured sensitivity 25.36mm/rev, min -5% max 105% over 148885.3mm
20.03.2021, 10:21:55	M591 d0
Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 131 agc 107, measured sensitivity 25.36mm/rev, min -5% max 105% over 148686.4mm
20.03.2021, 10:21:18	M591 d0
Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 131 agc 107, measured sensitivity 25.36mm/rev, min -5% max 105% over 148515.8mm

After the "reset":

20.03.2021, 10:52:50	M591 D0
Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 132 agc 107, measured sensitivity 25.51mm/rev, min 97% max 104% over 2092.2mm
20.03.2021, 10:50:15	M591 D0
Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 132 agc 107, measured sensitivity 25.51mm/rev, min 97% max 104% over 1380.5mm
20.03.2021, 10:48:02	M591 D0
Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 132 agc 107, measured sensitivity 25.53mm/rev, min 97% max 104% over 766.6mm
20.03.2021, 10:47:35	M591 D0
Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 132 agc 107, measured sensitivity 25.54mm/rev, min 97% max 104% over 644.5mm
20.03.2021, 10:45:52	M591 D0
Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 132 agc 107, measured sensitivity 25.57mm/rev, min 97% max 104% over 171.1mm
20.03.2021, 10:45:22	M591 D0
Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 132 agc 107, measured sensitivity 25.57mm/rev, min 97% max 101% over 26.5mm
20.03.2021, 10:45:02	M292
Printing paused at X-21.7 Y-33.3 Z2.5 C40.0
20.03.2021, 10:44:51	Resume state saved
20.03.2021, 10:44:24	M591 d0
Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
20.03.2021, 10:44:14	M591 d0
Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
20.03.2021, 10:43:53	M591 d0
Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
20.03.2021, 10:43:39	M591 d0
Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
20.03.2021, 10:43:19	M591 d0
Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
20.03.2021, 10:42:57	M591 d0
Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
20.03.2021, 10:42:43	M591 d0
Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
20.03.2021, 10:42:34	M591 d0
Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
20.03.2021, 10:42:31	M591 d0 s1
20.03.2021, 10:42:24	M591 d0
Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, disabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
20.03.2021, 10:42:21	M591 d0 s0

All settings are higher in this thread.

I ran 170 hours long print. I should have tried to install the old firmware, something is wrong here

And a couple of screenshots to tread:

Dep

And I already had it. But at that moment
I had one of the extruders disabled on the CAN bus and errors were pouring in. I thought it was because of this.

Last time min was -107% the extruder ended up stuck, but the printer kept printing in air all night.

In general, the filament monitor does not work on this firmware.

Dep

I installed 3.2.2 firmware - the errors disappeared, the mesh is working, the filament monitor is working.

The printer is printing 5 hours, the flight is normal. So pay attention to what I wrote above.

Phaedrux

So it's all working fine in 3.2.2 but has problems with 3.3beta2?

If so I will remove the Solved tag as it still needs to be investigated.

Dep

The errors that fell on the screen and the problem with the filament sensor disappeared immediately. So yes, this is a beta issue.

As for the mesh calibration, I still do not understand. Now it seems to be working. But it somehow still worked on beta. I recalibrated many times, so I got completely confused.

oliof

FWIW I see those errors too with a Paneldue, so I removed it for the time being. Machine is down for other reasons right now, so I forgot to report it.

dc42

Next time one of you get these "Bad command" messages on PanelDue, please run M122 from the DWC console or USB. I am especially interested in what value it reports for "Aux0 errors".

dc42

@Dep said in Strange bugs 3.3beta2:

Another dangerous bug!

M558 K0 H5 A5 F120
Works as it should

M558 K0 H5 A5 F120: 120
Also works as it should

M558 K0 H5 A5 F120: 60
Broke today probe.
The bed goes up and breaks the probe. And continue to rise.

I checked it several times.

What type of probe is it? Some types of probe (e.g. Smart Effector and piezo probes) don't work at low speeds.