Posts made by Phaedrux

@stuartofmt I think what seems to happen sometimes with dual band networks is that the router erroneously steers the Duet to the 5ghz network even though the Duet can't use it. I'm not sure if that's ever been definitively confirmed though.

You may want to state your approximate location.

@Leeuw123 said in Squealing motor noise & choppy movement:

@dc42 12v in. Basically, I took an ender 3 s1 set-up (gantry/motors/hotend) and am running it off my new duet 3 mini

Aren't the creality printers running 24v supplies?

Thanks for the macro. I edited your post to put it in a code block so that it displays correctly.

Can you share your full config.g and homing files?

Also please send M122 and M98 P"config.g" and share the results here.

@bugpwr said in resume redundant extrusion:

There seems to be additional extrusion when resuming a job

Can you show a photo of what you mean?

https://docs.duet3d.com/User_manual/Machine_configuration/Networking#configuring-duet-in-wifi-access-point-mode

https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_firmware#duet-3-mini-5-wifiethernet

If the mini5 is the wifi model, you can actually have it startup it's own access point which you can then connect to. You'd have to configure that over USB terminal connection.

Updating the firmware can be done with a USB connection to a computer. It presents itself as an external storage drive that you copy the firmware file onto.

I would suggest starting without the Pi in the mix at all, and get the mini5 up and running in standalone mode first. Once that's all working you can tackle adding in the Pi.

Getting the firmware updated on the mini5 is pretty straight forward, and getting connected to it over the network should be as well.

Start here: https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet

@Arminas said in PT1000 thermistor configuration:

at a random point temperature jumps up and down. New thermistors installed.

Are the cables routed near other wiring? Sounds more like interference.

I believe you may be running into the minimum feed rate limit.

F5 is 5mm/min

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m203-set-maximum-feedrate

Innn Minimum overall movement speed (firmware 2.03 and later), default 30mm/min

RepRapFirmware has a default minimum movement speed of 0.5mm/sec, or 30mm/minute.
Gcode commands sent with a slower feedrate than this (e.g. drilling) will automatically run at this speed.
In firmware 2.03 and later this can be changed using the I ('i') parameter of the M203 command. For example, for a 10mm/minute minimum speed, send:
M203 I10 ; set minimum speed to 10mm/min

Firmware version? Which Duet board?

Ok, so it's a Maestro board?

Did you try going back to 3.2.2?

Based on the sound which is driver whine, I would say it's likely something to do with the drivers being in spreadcycle vs stealthchop.

This seems relevant from the 3.4 changelogs:

[Duet 3 Mini] [Duet Maestro] The stepper drivers no longer default to stealthchop mode, because of the risk of excessive motor current if the correct tuning move is not executed.

https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x#reprapfirmware-340

Take a look here: https://docs.duet3d.com/en/User_manual/Connecting_hardware/Motors_tuning

Which axis specifically? Perhaps it's just stalling due to friction. I know that with my own Z axis lead screws if I haven't used it in some time the grease dries out and needs to be redone otherwise it binds and stalls and makes an awful noise.

Don't change anything with your config, nothing has dramatically changed. You should go through the release notes for the intervening firmware though to see if anything applies to you. Better to roll back to your previous firmware and see if that actually makes a difference before randomly changing settings.

@R006 said in Duet2 wifi: Motor Driver & Connector heating issue:

RRF 3.5.2rc1.

Please update to 3.5.4 and see if the be behaviour continues.
Also please post your config.g and homing files.

@Polyneutron21 said in [SZP] Scanning Z probes as regular Z probes:

The SZP show up in the Duet Web control, and communication looks great, the problem is with M308 is says S10 is not a valid sensor pin.

I think you should start a new thread and provide some additional information about your setup.

@lazy_mosquito
Your issue sounds more like an issue with the SD card slot on your particular board. I suggest you create a new thread for your issue. Please include some pictures of your SD card slot soldering and when and where you purchased the 6XD.

It's taking the bed size from M208 from the object model.

https://docs.duet3d.com/en/User_manual/RepRapFirmware/Object_Model

Starting with the config tool and getting something as close to your setup as possible with that and then comparing it to what you had for the duet 2 would be my choice.

@CCS86 said in Issues with pressure advance since RRF 3.4:

@Argo

Man, I sure wish the Maestro didn't get kicked out of the party before this issue was resolved.

The issue is still present in 3.5.4?