Topics created by kordris

Definitely check your wires as it appears the bed isn't heating at all as far as the thermistor is concerned.

I got it fixed so the M997 worked great. Not sure what it actually did so if you can tell me so I know for next time. But when I was trying to figure out the heightmap issue I tried putting a mesh.g file in the files. So that was causing the mesh from from working. So deleted the file and works fine now. Thank you for the help. Seems to working fine now.

@kordris said in Tach output and tool board help.:

Also is the only way to use a runout sensor is on the toolboard that using the extruder. Is there going to be a update to allow you to run the runout sensor to the duet 3 board.

I have added this to the firmware wish list.

@phaedrux Thank you for the help you gave me.. Really would love to look into some Hall effect sensors. They are now just coming onto the market for the Voron. Like the idea of not having to use any contact. Might also look at replacing my bed micro sensor to a 3 pin one also. As of right now its been fine its working good. Guess because its not getting any interference. Anyways are there any newer plug ins or addons I should look at? or anything I should look at with the new duet 3 that the duet 2 wifi didn't do.

Except that "100%" reported by the DWC might just mean that the javascript is just reporting it's "done". 🙂
In any case I think @kordris just needs to give us more info.

@omni @kordris I got mine working with the following settings:

M591 D0 P7 C"ystop" L7 R80:115 E8 S1

What caused problems with my setup was that I've used an endstop pin from an axis where sensorless homing was enabled. Switching to an endstop without sensorless homing solved it for me.

I am using a third party controller board with a STM32 chip structure. I don't know if that has any impact on the error that I had but this might also help you if you are using an original Duet board.