Topics created by FairladyZ

Just to be clear I am not endorsing yanking cables about with the system powered.

Do the drivers lock a fault flag or only hold it temporarily while it thinks the fault is present? The duet may keep a pop up warning active for longer than the fault exists to warn of pending failure. If the fault flag doesn't lock then a fault must exist for x seconds before pause may catch most false posatives.

Main use case for this is capturing failures in highly dynamic power cables such as direct extruders and serial manipulators such as cartesians where the x axis stepper is moved for a change in y.

@fairladyz said in Using rotary encoder for filament monitoring:

Has anyone tried using a rotary encoder for this? Any advice on how I could go about wiring and configuring a rotary encoder for filament monitoring?

99p filament monitor
99p filament monitor again

It's still in use on my cartesian (diy i3 clone) and working well, although I had to set the parameters looser than I expected due to the error that accumulates with retraction and not actually knowing which way the encoder is moving when a transition comes through. I think to make this work well one would need to develop a model of the encoder in the duet firmware and predict the transitions based on the instructed filament movement.

@dc42 I power my bed from the mains and I have lots of 12V PSUs that I got for free. I do have several 24V PSUs and 36V and 48V but they are much bigger. I am trying to make a compact machine.

I do use 24V on my machines that have ball screws but with belt drive my motors go as fast as I would want them to on 12V. I easily get 200mm/s out of a Melzi on 12V with Marlin.

Are you saying the Trinamic drivers won't work as well at 12V or just that they will go even faster on 24V?

When R is set to 2 should it stop as soon as it detects a crash or does it finish the current move? After more testing I believe that it detects the crash the same regardless of the R value but when R is 2 the printer keeps moving prompting me to shut off the printer to prevent damage. Since the gcode I have been using to test crash detection tells the printer to move far past the location of the crash, I need it to stop as soon as the crash is detected.

I was able to make crash detection work as I intended by using R3 to rehome and using M291 to inform the web interface of the crash and pause the printer until I am able to monitor the restart of the print.

That was the issue. I updated to 2.03 and my new numbers are around min 45% avg 83% max 123%. The sensor is now working very well. Thank you.