This gets stranger. Adding in an M117 somewhere in config.g, even one with no text, fixes the problem! The 'Starting up' message comes up for a flash, less than a second, before going to 'Idle'. Comment out that M117 and it goes back to taking 30 seconds.

I'm guessing that it's always finished booting, it's just that PanelDue doesn't know about it. The addition of the M117 forces a communication with PanelDue that corrects the missed message.

Anyway, with the blank M117 in there all works fine.

Done! Found it under the printer configuration. I've only been 3D printing for a couple months now, and still learning new things every day. I had no idea there was this start and end gcode configurator in Cura until I went looking for it after your previous post.

Thanks!

I have one more issue that I know of now, which is that my paneldue 7" lcd isn't working right, but I'll post that in a separate thread.

I appreciate the help. This upgrade to the DuetWifi from the Melzi board wasn't for the faint of heart, but it was totally doable, and I'm just about there, and blown away by how eery it is not to hear my printer other than the fans. I was just lying on the couch and had to peek my head around the corner just to make sure my print was still going, because I'm used to hearing it loudly, and now I just don't.

As stated in the fitting instructions, the G31 threshold should always be set to 500 when using the IR sensor.

The diagnostic led is not currently used as such by firmware. It shares an output pin with the Z probe modulation signal, so it will be on if you have a type 1 or 2 Z probe configured in your M558 command.

I put the 1.16 firmware as well as the latest web and server. when I went to run the M997 all went well at least one solved.

Thanks for the help

Thanks dc42 for pointing me in the right direction. Turned out to be faulty Z endstop switch. Luckily, I had another. Now let me see if I can reconnect. Yes! Good to go.

Thanks again to both of you .. I now have my beast working .. at least all the homing and I can 'dry' print a file.

I still need to tune my heaters - and work on the IR Z-probe distance and Z offset .. so I'll be doing some more research/reading before I come back and bug you guys for help again.

@dc42 thanks for the clarification David.

@DjDemonD given we're only seeing the need for 1mm or less retractions then what I said still stands I believe.

These are the settings I have in firmware at the moment:

[[language]] M201 X1000 Y1000 Z1000 E1000 ; Accelerations (mm/s^2) Set all E-motors the same M203 X10000 Y10000 Z10000 E3600 ; Maximum speeds (mm/min) Set all E-motors the same M566 X1200 Y1200 Z1200 E1200 ; Maximum instant speed changes mm/minute. Set all E-motors the same

@dc42:

@briangilbert:

I also spoke with David Crocker about extrusion and retraction speeds he suggested that more than 5mm/sec is largely pointless (which is confusing give the web interface defaults), though I have run at up to 10mm/sec as well.

I made that remark in the context of using 1 to 2mm retraction, because I thought that with such a small amount of retraction there isn't sufficient accelerate/decelerate distance to reach high speeds. However, I've now done the sums and if the extruder acceleration is 1000mm/sec^2 then it turns it that with 2mm retraction you can reach 45mm/sec. I don't know whether higher speeds help or not when using small amounts of retraction in a direct drive extruder, because I don't have one.

If you use a conventional extruder with a long Bowden tube and much longer retraction distances, then higher retraction speeds are certainly worthwhile.

@CaLviNx:

I like that, I too was once a Mechanic, sorry my bad Automotive Engineer.

Not that it matters, but actually over about 35 years everything from apprentice, through project engineer to operations manager and for the final 7 years of that particular career I ran my own consultancy business. So I tend to lump the whole lot together as "Automotive Engineer".

S or S0 means default, which in your case will be S5 i.e. use all 5 points.

Thanks for the update, good to know you got to the bottom of the issues and yes that makes sense.

If either/both of you get a chance to post the details of your upgrades into the " My Duet WiFi-controlled machine" examples forum that would be really appreciated:

Thanks!

Good stuff 🙂

Ah OK - that's pretty cool.

Went ahead and tried uploading the 1.16 files. Web control was successful, although it killed my connection. Firmware failed as did the wifi server. I'll keep working on it.

See this thread: https://www.duet3d.com/forum/thread.php?id=433

Oh well today it works… Strange...

Thanks for the swift response, the gcode file header I am currently using looks like this:

G90
M82
M106 S0
M140 S60
M190 S60
M104 S210 T0
M109 S210 T0
G28 ; home all axes

Not sure why it has both M140/190 and M104/109 as surely just using M190 and M109 would be good enough?

Been using this for a long time with a Marlin machine with no problems.

Just noticed that the config.g file has T0 at the bottom.

I have only used the web UI so far so it was in that I was thinking a Print Again button would be useful.

That's correct at present. There is work scheduled to allow commands from other input channels to be accepted when M109/M190/M116 are waiting for temperatures to be reached.

@T3P3Tony:

I have updated the Wiki to include a note on the folder naming, eca77 sorry you spent so much time on this!
https://duet3d.com/wiki/SD_card_folder_structure

Also added a note about browsers to here:
https://duet3d.com/wiki/Prerequisites_for_using_the_Duet_WiFi

And this as a trouble shooting page:
https://duet3d.com/wiki/File_uploads_or_other_DWC_features_not_working

When any more information or workarounds for other browsers becomes available we can update the troubleshooting page.

No problem, it was mostly me being so new to all this and assuming things, something that gets me in trouble quite a bit when I think about it… 😉
But actually glad that something came about from this and hopefully will help others.

Looking forward to it!