@dc42 Thank you. I wasn't sure if the board identifier would be single digit or multi-digit as in "01" rather than 1" but you have clarified perfectly.

@hussainsail2002 I've used decimal without issue. ...but equally interested to see if there is anything more than circumstantial evidence showing otherwise.

but it does work if you probe before every print?

Does the BLTouch run its self test when you power on the Duet? If it doesn't then perhaps it's not getting 5V power.

A filament sensor (that detects movement as well as presence) would achieve the desired result. If its possible to use the warning directly or if its something that can be added to future versions is something the developers can address maybe.

@philipp-r Glad that's fixed.

Is the endstop a microswitch, or some other type? If it's a microswitch then the most likely cause of the problem is a bad crimp connection in the cable.

@caveman said in Bed and hotend not heating @ the same time: M82 ;Set extruder to absolute mode G28 ; home all axes ;Heating M104 S220 ; set extruder temp M140 S60 ; set bed temp M190 S60 ; wait for bed temp M109 S220 ; wait for extruder temp I think the problem is that no tool is selected at the start. You need a T0 command somewhere before the M104 command.

To get an accurate print time, run the file in simulation mode first. You can do this from DuetWebControl (right click on the file and select Simulate) or from PanelDue.

@curieos said in Programming a smart effector: I think I got the wrong model of ATiny44s, mine are too small to solder on the board reliably. What model of ATiny are you guys using? We use the smallest Attiny44a, that comes in a square leadless package. You have to reflow solder them. I soldered the prototypes myself, using a Mylar stencil to place the solder paste accurately, and a hotplate.

The blown chip is probably the A4403 buck regulator, the small square chip labelled U3. But as @Veti says, it's probably simpler to provide 5V power either via the Duet USB socket (using a phone charger or similar PSU that can provide more current than your PC or laptop can), or to the PanelDue USB socket, or to the external 5V input on the Duet.

PT100 v1.2 boards have already been shipping for several weeks. The first production batch did not have the capacitors fitted, because there wasn't time before assembly to verify that adding them had no bad side effects.

Don't get discouraged. You're almost there. Your M558 and G31 commands are missing a few parameters for starters. https://duet3d.dozuki.com/Wiki/Gcode#Section_M558_Set_Z_probe_type M558 needs at a minimum P for probe type, F for feed rate to probe at, T for travel speed between points, H for dive height to raise to between probe points. There are some additional parameters that can help tune for certain cases. https://duet3d.dozuki.com/Wiki/Gcode#Section_G31_Set_or_Report_Current_Probe_status G31 needs P for trigger value, X and Y values for the distance between the probe and the nozzle, and Z for the trigger height of the probe, which is how high the nozzle is from the bed surface when the probe triggers. https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe G32 calls bed.g. The old way of doing bed compensation was to probe 5 points and create a flat plane. That has been replaced with G29 which creates a mesh grid of as many points as you want. So if you choose 9, it will probe a 3x3 grid, which is close to the old way of doing it. Or you can use up to 441 points and get a detailed surface map. Plus that map can be saved and reloaded without having to reprobe before every print if you don't want to. It's just a more versatile way of doing things and it takes the actual shape of the bed into account rather than just a fitted plane. So there is the background. In your case, you can replace G32 with G29, and with the corrected M558 and G31 "it should just work". @en_passant said in Absolutely lost in G29, G32: M561 ; clear previous compensation (from memory??) M557 P0 X10 Y10 ; probe point 1 (front left) M557 P1 X10 Y345 ; probe point 2 (rear left) M557 P2 X345 Y345 ; probe point 3 (rear right) M557 P3 X345 Y10 ; probe point 4 (front right) This format has also been deprecated. https://duet3d.dozuki.com/Wiki/Gcode#Section_M557_Set_Z_probe_point_or_define_probing_grid Parameters to define G32 probe points (Cartesian/CoreXY printers only, deprecated and not supported in firmware 1.18 and later) Pnnn Probe point number Xnnn X coordinate Ynnn Y coordinate Example M557 P1 X30 Y40.5 I'm not actually sure what the goal is with G32 for you at this point. Based on my description above, does G29 now cover what you need? Technically, since G32 just calls bed.g, you could put whatever you want in there. You could even just put a few commands to prepare for and run G29. Or if you wanted the firmware to probe near your leveling screws and tell you how much to turn them to get the bed level, it can do that too. https://duet3d.dozuki.com/Wiki/Using_the_manual_bed_levelling_assistant

@deckingman That makes sense now. I just figured each endstop input would pair up with the corresponding motor output and I didn't look too much into it! Thanks for all of the help.

Welcome to the Duet and RepRapFirmware. You've only scratched the surface.

Do you have any of those commands in any other macros? Like bed.g or your homing files that may be over writing the ones from config.g? It would be unusual for those to exist in config-override.g unless you put them there yourself.

Yes it worked, but it was also dependent on temperature, so the trigger sensitivity when cold booted was different than after a long print. It led to false positive stalls and the risk of false negatives leading to head crashes was too much. BLTouch was far more reliable and it's shortcomings were less of an issue.

@phaedrux said in Duet maestro and weirdness on start gcode: @agniusm said in Duet maestro and weirdness on start gcode: G1 Y0.0 F5000 ; go outside print area G92 E0 ; reset extrusion distance G1 X70.0 E9 F1000 ; intro line G1 X140 E12.5 F1000 ; intro line I say again, it looks like you're missing G90 and G91 commands here. G1 Y0 makes no sense in the context of a relative move. But the next movements are to extrude a prime like, which would require a relative move. So the snippet above would become G90 ; absolute positioning G1 Y0 X0 F5000 ; go outside print area G92 E0 ; reset extrusion distance G91 ; relative positioning G1 X70.0 E9 F1000 ; intro line G1 X140 E12.5 F1000 ; intro line

It turns out they had some bad beds. Sending a new one.

@oliverracing said in Stepper motor lost torque: Just looking for a replacement chip, is it a TMC2660-PA-T or TMC2660-PA that I need to be a direct swap and is it just a case of removing the old chip and soldering the new one on? Yes that's the one. I think the -T suffix just means that it is supplied on a reel. But before you replace it, how old is your Duet? If the driver failure wasn't your fault, replacement is covered by the warranty.