M591 issue or not? IT IS AN ISSUE !!
-
@dc42 said in M591 issue or not?:
@tecno try sending M591 D0 with and without filament in the sensor, to see if it reports the correct state.
I get the answer as expected = working like a charm.
Been a bit busy so still no chance to play with ^
-
Did not do any good with ^ so now this function is deactivared in config.g.
Will have to investigate WHY this happends, I have a feeling that filament RETRACT can be the issue as the filament is probably due its movement triggering the switch momentarly. PETG is a bit more flexible so this behaviour might be the issue.
Report of my findings later....
Cheers
Bengt -
Still get this error even when M591 is DISABLED.
-
@tecno said in M591 issue or not?:
Still get this error even when M591 is DISABLED.
You mean using the S parameter setting for that?
Frederick
-
-
@tecno said in M591 issue or not?:
; Filament monitor
; M591 D0 P2 S1 C"^io4.in" ; filament sensorHmm... Commented out.
That would seem to rule out the M591.
Fixed problem here the other day when the OP had two of the same command and the second had the wrong settings.
Don't suppose you've got another M591 somewhere?
Frederick
-
@fcwilt
Only 1 commented out now in config.gWill do some prints tomorrow for my grandson pokémon cookie cutters and I will disable input shaping as that is the latest upgrade done on my setup.
Cheers
Bengt -
So I still get these annoying errors !! SO IT IS AN ISSUE !!
-
-
@tecno which firmware version are you using?
-
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.0beta3 (2021-08-24 14:08:24) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 0SBLN-A396U-D65J0-40KMQ-2R03Z-RQHV7
Used output buffers: 3 of 40 (20 max)