Topics created by handyandy

@handyandy I think you asked this previously https://forum.duet3d.com/topic/37922/duet-3-mini-5-vs-prusa-mk4

Perhaps start with the same settings as the Mk4, and tune extrusion (temperature, extrusion steps per mm) and see if you get similar results.

Ian

@handyandy I think the Teaching Tech calibration guide is pretty good: https://teachingtechyt.github.io/calibration.html
Also the 'Califlower' yields good results, though at a cost: https://vector3d.shop/products/califlower-calibration-tool-mk2

Ian

@handyandy I think that's dyscalculia!

Ian

@droftarts Thanks for that.

Thanks for that.

@handyandy said in Sensorless homing:

Error: Pin name needed for switch type end stop on X-axis

It's likely these lines in your X and Y homing files

M574 X1 ; use stallguard for endstop

It's missing the S3 for sensorless.

If it's still giving you the error, search your macros for other M574 commands and make sure they have the correct syntax.

@handyandy said in Sensorless homing:

I also can't get the PanelDue to display.

Your M575 command in your config.g is using S0 instead of S1.
It should be M575 P1 B57600 S1 to enable the PanelDue.

@chrishamm thanks I tried that but the printout does not show all the details in the original web page. I could not find the PDF option anywhere. Where is it?

@handyandy you can configure it directly, rather than tricking Duet into thinking it is a fan.

See my thread here, where I did exactly this to control some linear pull solenoids, and an LED ring light for a vision camera.

This way you'll be able to control your light using

M42 Pn S1 ; turn on your light M42 Pn S0 ; turn off

Where n is the number you assigned to your light, via the M codes in my thread linked above.

In my case, both the ring light and solenoid required 24V so I used OUT5 and OUT6, with the voltage select jumper set to VFUSED, as I too am supplying the board with 24V.

Alternatively you can configure the jumper to supply 12V on these pins, if you're within current limits.

Finally, I'd need to check the schematic to see if the outputs are just low side MOSFETS, in which case you likely can externally supply whatever voltage you need (within the drain-source breakdown limit of the FETs) and just use the ground side of the output pins, but take this last paragraph with a pinch of salt, as I've not done that check.

@handyandy Hi, I have just spotted the solution to this at the end of the 'Getting Started' document. I should RTFM more!

@tas said in Fan1 Stuck on!:

@handyandy said in Fan1 Stuck on!:

M106 P1 S1 H1 T45 ; Set fan 1 value. Thermostatic control is turned on at 45°C

Set S1 to S0.0?

From https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m106-fan-on

From RRF 3.4, when a fan is configured as thermostatic using M106, the S parameter is now ignored.

@handyandy What firmware version are you on? Send M122 and post response.

Ian

@handyandy What I meant was that you have that M204 line in your config.g. It overrides the setting in M201. Slicers have a habit of putting in M204 at low rates, overriding the acceleration rate you want, as machines generally print quieter with low acceleration.

The main reason to use M204 is to make all moves have the same acceleration. M201 defines the acceleration per axis, but on diagonal moves, the acceleration is faster as it moves at the limit of both X and Y. Eg if M201 X1000 Y1000 is set, a straight X move will use acceleration of 1000mm/s^2, but the acceleration of a 45° diagonal move will be 1414, with both motors accelerating at 1000mm/s^2. Setting M204 P1000 would set all moves to the same acceleration.

Ian

@handyandy What type of code are you referring to, G/M/T-codes, comments, or meta G-code like conditionals?

@cosmowave Thanks for that.

@dc42 Hi,
That's an easy one... I already have the Duet 2 Wi-Fi board!
I can't afford to just replace it with a Duet 3 as much as the more compact board etc interests me.

@ctilley79 you can't send parameters to start.g as it's executed before the gcode is

@handyandy I had the same issue and think I have resolved it.

The first thing I did is to put a very noticeable black marking on the top of the motor couplings so I could easily tell if they lost sync. If they ever do (has not happened lately) I can manually put them back in sync.

Another thing I did is a suggestion from @dc42 to slowly power up the motors in config.g as follows

;Sowly power up motors M913 X10 Y10 Z10 ;Set power to 10% M17 X Y Z ;Enable steppers G4 P100 ;Dwell 100ms M913 X20 Y20 Z20 ;Set power to 20% G4 P100 ;Dwell 100ms M913 X30 Y30 Z30 ;Set power to 30% G4 P100 ;Dwell 100ms M913 X40 Y40 Z40 ;Set power to 40% G4 P100 ;Dwell 100ms M913 X50 Y50 Z50 ;Set power to 50% G4 P100 ;Dwell 100ms M913 X60 Y60 Z60 ;Set power to 60% G4 P100 ;Dwell 100ms M913 X70 Y70 Z70 ;Set power to 70% G4 P100 ;Dwell 100ms M913 X80 Y80 Z80 ;Set power to 80% G4 P100 ;Dwell 100ms M913 X90 Y90 Z90 ;Set power to 90% G4 P100 ;Dwell 100ms M913 X100 Y100 Z100 ;Set power to 100% G4 P100 ;Dwell 100ms M18 X Y Z ;Disable steppers.

If that doesn't work try boosting the current to your Z motors a bit. One of them may need a bit more current than the other.

@chrishamm , Thanks that (of course) cured things. I'm not sure why I used M32 in this case! I have used M98 several times before!

@handyandy we don't advise using M18 or M84, except possibly at the end of a long print if the printer will likely be unattended. All Duets have software-settable motor current, and by default the motor currents will be reduced to the idle current (typically 30% of the normal current) 30 seconds after all movement has stopped.

Hi, I took on board your comments about my old text editors and looked at Notepad++... I didn't like it. The GUI seems very 'home made in my shed'.
I did however find the 'Atom' editor being recommended so have also tried this. I like it a lot.
It has a really nice and modern looking GUI. It allowed me to load my whole SD card into it as a project. I could then set up my Find/Replace criteria and quickly apply them throughout the project. Brilliant.
I can now also display degree symbols correctly!
Cheers all.