Posts made by dportero

@DocTrucker did you ever get a duet board working with the pro2? I have a pro2 that needs a board transplant, but haven't been able to find if anyone has successfully done it yet.

@droftarts

That might be exactly what I’m looking for. I’ll try it out. Thanks!

@phaedrux

Awesome! Thanks a bunch.

I do actually remember seeing that now, but it slipped my mind. Apologies for not googling it again

@phaedrux

There are 3 fan ports (0,1,2). I could use Fan2 and wire the current fan to an always on port, which would free it up for being used as the part cooling fan if that’s possible.

How would I program fan 2 to be used as fan0?

@phaedrux

They can support it. But at this moment I am doing this for a printer that is past of a fleet of printers running 2.0. To keep all the printers the same we are staying on 2.0.

Is this not possible to do with rrf2.0?

My part cooling fan control no longer works after a bad print failure and subsequent short that occurred. I have an open I/O port that I would like to substitute for Fan0 that is currently used to control a chamber fan. The I/O pin is P42. I have been unable to locate a way to map this to Fan0. Is this something that is possible?

Thanks!

Duet 2 clone (vivedino)
Running Firmware 2.05 (unable to upgrade to 3.XX for a variety of reasons)

@dc42

If I am not always at the computer it sleeps and DWC reconnects so all messages are lost. Is there a way to save them somewhere?

I am running version 2.03RC3 (can't update for a few reasons). I was wondering if there was a way to print the job duration using M117? I really miss the ability octoprint has to go back and see how long a job actually took and this seems like the only partial solution. I would love it if it could add it to the metadata of a job.

Thanks!

@engikeneer Unfortunately updating the firmware is not an option at the moment, as the printer I am using is the test machine for a larger print farm, so I have to keep it the same as the other printers. Is there nothing applicable for the firmware it is currently running?

I have run into an interesting issue. My PID tune is valid for regular printing speeds on my Mosquito Magnum+. But when I try and increase the speed above 400mm/s, the PID tune seems to not be able to keep up with the amount of filament being pushed through the system.

Is there a way to have different PID tunes, depending on the movement speed that will be performed?

Duet firmware 2.03 on Duet 2 Clone