I think I have found the answer. I added these 2 lines in the start g-code and it seems that Z is adapting to the height map. I need to do testing / tuning in the coming days, but happy so far.
G29 S1 ;Load the height map from file and activate mesh bed compensation
M376 H5 ;Taper off bed compensation after Hx mm
I want to add a buzzer (a simple piezo) to make a noise for alarms and such when there is an event.
The M300 command sends messages to my phone/ computer but unless I've got the app open at the time I don't hear it. An actual buzzer would work better for me and I'm sure there is a way to attach it to an 3.3V output but I can't see any information on how.
Any suggestions on how to "export" an alarm to a specified io port? I'd like to be able to send a similar alarm for various events, such as filament error, crash detection, print completed.
I have a Duet 3 Mini 5+, firmware 3.4
@fcwilt
Great, thanks! I found some through the Duet macros documentation, so I should hopefully be able to work out something from these.
I'm still having problems but this title is now misleading since it is not necessary to set up sensorless homing first so I have started a new thread problems-setting-up-stall-detection
@droftarts Thanks! I checked and the config.g was indeed missing. I feel that is extremely weird but neverteless I was able to restore my saved backup and it's now woking. My releases are Firmware 3.4.1 and Server 1.26 Not that old, but they do need updating. I'll do that when I've cleared the backlog.
I have a Duet Mini Wifi that is not connecting. There is a green LED beside the wifi connection that normally flashes a few times at startup then is continuously on. Now it is not flashing at startup and there's no connection.
It has been okay previously and I haven't made any changes recently. The wifi in the area is good (-50, 3m), with other devices connectiong without any problem.
Is there a fix for this? Or a troubleshooting method? Or a workaround to get files onto the Duet. Otherwise my printer is effectively dead.
Thanks in advance
Here are the files:
Config.txt
HomeAll.txt
M122.txt
The motors are NEMA 17, 48mm. Specs:
The problem is not repeatable. The motor faults as described happen independently and infrequently. They have only happened during a homing routine. Once the fault occurs, I have to reset the machine and then everything is okay for a few more days. I have never had the faults during a print. I have checked the motor phases and cables but I can't see anything problemmatic.
I'm getting some odd behavoir with a couple of motors on my 3D printer. One displays this message with corresponding judder of the motor. The other doesnt give a message but the motor doesn't move or make make a noise.
I know there will be shouts of Check Your Wiring. But I've checked all phases on the motor, checked the cables and physical condition of connectors and nothing seems wrong, I understand that it could be a transient problem.
But here's the thing: these problems only happen occasionally and only during homing and other startup routines. If I switch off and restart, then (so far) everything is fine until maybe a few days later when I see it again. It has never happened during a print.
Surely if it was a wiring problem then the problem is more likely to occur during the hours of printing rather than restricted to the few minutes of startup?
I have a Rat-Rig core XY printer which has three Z motors The problem is occurs on one of the XY motosr and one of the Z motors. The error in the title is attributed only to the XY motor. The Z axis motor just doesnt move and so the bed levels unevenly with no warning message.
I have a Duet 3 Mini with latest firmware.
@OwenD @zapta @oliof @Norder @dc42
Wow, I'm amazed by the inventive range of ideas proposed by respondents to this post! Air raid sirens. Klaxons. MP3 tunes. Now, a buzzer sounds so yesterday. Thanks to all who responded.
I opted for the motor idea from @zapta with a few mods to the stl's so I can hang it at a jaunty angle on the back on my printer and have a flat on the shaft. I'm running some tests at the moment. Currently it sounds like a machine gun so I will make some adjustments to avoid anyone calling the police!
I want to add a buzzer (a simple piezo) to make a noise for alarms and such when there is an event.
The M300 command sends messages to my phone/ computer but unless I've got the app open at the time I don't hear it. An actual buzzer would work better for me and I'm sure there is a way to attach it to an 3.3V output but I can't see any information on how.
Any suggestions on how to "export" an alarm to a specified io port? I'd like to be able to send a similar alarm for various events, such as filament error, crash detection, print completed.
I have a Duet 3 Mini 5+, firmware 3.4
Following up:
The spare parts arrived yesterday and today I replaced just the hotend thermistor. That seems to have resolved the problem as I did about 6 hours of printing with no events. Yipee!
I remain unclear how a faulty hotend thermistor could have had consequential effects on the reported bed temperature as shown in the chart (from the original problem) so any celebrations might be premature, but no such problem today.
@infiniteloop said in Problems with Heaters:
@tomf said in Problems with Heaters:
The hotend heater measures 12.5 ohms, and the bed 25 ohms.
So I can assume your PSU has 24V, and your bed is not powered from mains?
Yes, 24V supply, but the bed is mains powered,120V, 600W, through SSR.
@infiniteloop Will do when I get back later.