Posts made by KennethR

Thank you both. Based on the recommendation from Oliof I decided to have a go at replacing the driver myself. I have been doing some electronics myself over the years, but I have never worked with SMD components before.

Well, Youtube is your friend and I found a video showing how to use special solder with a low melting point (Chip-quick) that you add to the solder already present on the old component. That way it’s easy to keep all the solder in a fluid State and the component can easily be removed.

Then it’s ‘just’ about learning the right technique to solder(and to use LOTS of flux).

It worked at my first try

It did bring some expenses of course. I didnt have the flux nor the special solder and I of course had to buy a driver as well. All in all I guess my cost was €40-50,- but I have flux and special solder to last me a lifetime and learned how to fix this if it happens again.

BR Kenneth

Hi,
I have a dead driver on my Duet3D 2 Wifi. Instead of trashing the whole board I’m considering using the Duet expansion breakout board, buy a TCM2209 and connect to one of the additional driver interfaces. Would that work after remapping the motor in the config file?

BR Kenneth

Hi,

I have a Panelduo running on a V2.03 Duet2 Wifi. I would like to remove the stop button from the screen as I have a physical emergency stop button(it's a huge 500X500X800mm clay printer). My reason for the change is that if the button by accident is hit, then a week long print job may be lost. It happened to us once, but luckily "only" 1,5 days of work was lost.

I understand that I would need to compile a new firmware, which would be V1.25 if I did my homework correctly, but can anyone point me to a guide on what I would have to change in the source files?

BR Kenneth

@Phaedrux @dc42

Hi again,

I just tested using relative extrusion, and it worked perfectly. The ‘blob’ issue is now gone!

Again, thanks a lot for the help

@Phaedrux @dc42

Thanks a lot to both of you I’ll try that in a few says when I’m back in the workshop.

BR Kenneth

@dc42

Thanks dc42. The volume extruded/retracted is very small compared to the 'blob'. I would say the blob is at least 10 times the volume of the extrude/retract.

I can also just try removing that command.

I'm not around my printer the next few days, so I cannot test at this moment.

BR Kenneth

@Phaedrux

Of course - it's attached.

Note that I only have the 'blob' issue when running the resurrect.g after having the power shut down. It does not happen in any other cases.

Shape-Cylinder_ø30.gcode

@Phaedrux

Yes, it extrudes a bit of filament, but that is while it is at 0,0. The 'blob' is much bigger than that and takes much longer to do, as well as being made at the position where it resumes printing after finishing the blob.

I have no idea what the logic of extruding that amount of material could be.

@Phaedrux

Thanks for a very quick reply

I got the printer with that FW and my reluctance to upgrade it right before REALLY needing the printer is the only reason I haven't done it yet.

Maybe I misunderstood the resurrect procedure because I don't use M916, I simply run the resurrect.g as a macro. It works fine apart from the 'blob'.

I have attached the files.

BR Kenneth
stop.g resurrect-prologue (3).g resurrect (2).g resume (1).g pause.g cancel.g
config (5).g

@KennethR

NOTE: I found an easy fix for the issue and have created another post on my remaining problem. Please ignore the above post(I cannot edit it anymore)

BR Kenneth

Hi,

I’m currently working on setting up resume after power loss on my Duet2 WIFI clay printer. The way I need to use it is to pause the print, turn off the printer, and then continue the print the next day.

I do not home Z and after a lot of fiddeling this now works, but I have a related issue: When I pause and resume it works fine, but when I pause, power off, power on, and the use resume(ressurect) then the printer moves to the correct place but then extrudes a blob of clay for around 5-10 secs and then starts printing perfectly. I have looked “everywhere” in the config files and cannot find what does this. Can anyone help?

Please note that I’m using an OLD firmware (2.03c beta). I am in the middle of producing some artworks for a soon to come exhibition so for fear of having the printer out of duty for some time if I do something wrong I really want to wait upgrading it until after the exhibition.

I hope someone can help

Thanks in advance,
Kenneth

@T3P3Tony

I know this is an old topic but I think it makes sense asking in here anyway.

I am on an old firmware(2.03C beta, dated before this thread was started). Was the issues of using resurrect without homing Z-axis solved in later versions, or is the best shot still to use the code provided in this thread?

The reason I'm not just simply updating the FW is that I purchased a pre-built printer and never did a FW upgrade on a Duet controller, and I am currently in a situation where any downtime because of me doing something wrong in the FW upgrade process would be really bad.

Best regards
Kenneth

@Phaedrux

I know it’s an old firmware, but the printer came with it and when asking the vendor regarding upgrading the message was that it should work, but he didn’t guarantee it.

So yes, I will definetely upgrade, but only if it is fixed. I read another post regarding resurrect issues and the conclusion was that that there were errors in the a t least a 2021 version of the firmware, and it had to be looked upon. I think I’ll ask the admin that answered that post whether it was ever fixed.

But thanks for your advice

@Trideo Sorry to reply to an old thread, but there aren’t many to ind with this issue.

Was this ever solved?

I’m using a corexy printer at also cannot home Z because of the way the printer is built, and therefore also have the problem that even after restart of the printer the babystep will be reapplied because it’s saved in resurrect.g

Im using Duet 2 wifi with firmware 2.03c