@Phaedrux Yeah, that was the problem. I'm not even going to tell you how many times I checked that and counted the pins....

I'm going to credit you with this one...as you pointed me at the proper pin. Thanks again. Cheers.

@fcwilt I believe that command is what I have been searching for! Thanks Frederick!

Bought a new card, was trying to move files from the old to the new and the old was acting odd. Would transfer the files in windows...but they didn't show up. It seems perhaps that card was the issue. Got the files moved in the end with copy paste though and connected to the board with YAT. Turned on wifi and connected, all of the config/macro files etc were there but config.g was blank. Perhaps when I clicked save config and reboot the card hiccuped and the config was wiped? Copied the .bak file into config.g and all seems to be well.

When is .bak updated and what triggers it? It appears to be fairly recent, but I haven't taken any backup steps in a while. Sure saved me a bunch of work. Thanks for your help as always Phaedrux!

So the .bak is always the most recent version. How great is that! This turned out to be significantly less of an ordeal than I thought it would be. Thanks Phaedrux for the help...again.

Bought a new card, was trying to move files from the old to the new and the old was acting odd. Would transfer the files in windows...but they didn't show up. It seems perhaps that card was the issue. Got the files moved in the end with copy paste though and connected to the board with YAT. Turned on wifi and connected, all of the config/macro files etc were there but config.g was blank. Perhaps when I clicked save config and reboot the card hiccuped and the config was wiped? Copied the .bak file into config.g and all seems to be well.

When is .bak updated and what triggers it? It appears to be fairly recent, but I haven't taken any backup steps in a while. Sure saved me a bunch of work. Thanks for your help as always Phaedrux!

Phaedrux, how you walk around with that much knowledge in your head without falling over is beyond me but I appreciate the help.

Following the path on that link. 5v, 3.3 and usb are lit, diag is not so it appears the board lives. Duet2wifi shows up on com3 so I can communicate. Have to run off to work for a bit and will continue down the path when I return. I suspect a firmware update/reload will be required? Reworking the configs might create a bit of brain damage. I believe the original is on my computer from the config tool....suspect I'm supposed to back this stuff up occasionally but didn't. Guess I'll learn a lesson here.

Have been printing for a few months. Working quite well. This morning I changed the nozzle, checked the Z-offset and changed it in the config.g. Clicked yes on the restart and....something has gone wrong. No longer connects to the web, Duet's three lights come on at power up, but Duex5 is dark, no lights, no fan. Hotend fan is on full time, which is not how it is setup in the config.

I get the impression the firmware got wrecked in the restart somehow. Problem is, how do I proceed from here? I've been looking through the dozuki and not having much luck. Any thoughts from those with bigger brains than mine would be appreciated.

@Phaedrux Thank you sir, I will do that.

I am on 3.2, but did the PID tune with fan off etc. The M570 appears to be doing the job at present. Prints 5 and 6 of 57 are on the two printers. Once those are done, I'll try PID under worst case and see how that goes without the M570 basically disabling protection for 3 minutes. Thanks all!

@Phaedrux

Its actually the nozzle and yes it was PID tuned. When I changed layers and ramped up speed and temp...the temp was increasing at a slower pace than firmware was looking for so it faulted. I think that's to be expected since it's extruding pretty quickly at that point. Here is the heater section as it sits now:

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 R0.628 C220.1 D5.85 S1.00 B0 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S110 ; set temperature limit for heater 0 to 110C
M308 S1 P"e0temp" Y"pt1000" ; wws configure sensor 1 as pt1000 on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 A893.3 C322.6 D5.3 S1.00 V24.0 B0 ; wws 64w BZAMD disable bang-bang mode for heater and set PWM limit
M143 H1 S450 ; set temperature limit for heater 1 to 450C
M570 H1 P200 ; set 180 seconds for anomaly before raising a heater fault

That appears to work at least on the current print. I have 57 more of these to do so we shall see. As always 1 of your thoughts are worth 10 of mine...so if you think I'm heading the wrong way or there is an easier way, I will be listening. Enjoy your weekend!

@fcwilt

I added M570 H1 P180 at the end of the heater section. I believe, if I'm reading the dozuki correctly that I'm giving the heater 3 minutes to make any changes called for before it starts looking for fault. That's likely a bit long, but it's a test. Worked fine on the first print. Will experiment a bit and drop the time limit. I appreciate the help.

@fcwilt I believe that command is what I have been searching for! Thanks Frederick!

@dc42 I thought it might be something like that! Thanks much for the clarification. It's all working very well!