Heater Fault
-
@dave-parry try putting the Duet2_SDiap32_WiFiEth.bin (from the 3.3 release)
and the Duet2CombinedFirmware.bin
from the 3.4b5 release in the /firmware directory and then run M997.
-
@t3p3tony Still the same.
-
@dave-parry what is reported by M997?
Also what is showing in the /firmware directory in DWC? -
@t3p3tony Nothing gets reported and paneldue shows error. But nothing in status window.
seems to start update but stops pretty quickly. Status just says M997 and nothing else. -
@dave-parry In firmware folder just have 3 files.
Duet2_SDiap32_WiFiEth.bin
Duet2CombinedFirmware.bin
Duet2CombinedIAP.bin -
@dave-parry are you sending M997 from DWC or the PanelDue?
At this point i would suggest connecting over a USB cable and sending M997 via a terminal program like YAT.
-
@t3p3tony I was using DWC. will try using yat. I think I have that installed. but maybe have to be later on. Thanks for your help.
-
@dave-parry Get the same thing using YAT.
I get a error message cant find 0:/sys/duet2comb.... which seems to be the wrong location. However even putting a copy in the sys folder doesnt work, still get the same message -
@dave-parry as far I can remember I had the same problem, my solution was to upload an actual version from Duet2CombinedIAP.bin I was sure I had the newest version, but it wasn't so...
-
Idk if it will work but make a copy of the contents of your SD card, then flash a stable binary using Bossa, perferably 3.3. Then generate the config files according to the printer and place those folders in the sd card. Then replace the bin in firmware folder with the version you want to flash. Go to YAT and run M997.
Also are you pressing the reset button before you try to flash the firmware? I have noticed that even if your all files are in correct directories, YAT gives .bin file not found unless you reset the board
-
@jazbaatbadalgaye No did'nt press reset. Will try that next.
-
@jazbaatbadalgaye trying to flash using bossa, but although the Com3 is listed (and Device manager/port is listed as duet) says cant connect to device. Am I missing something?
-
@dave-parry Did you put the jumper on the erase pins? As the name suggests, it is going to erase the board so proceed with caution.
-
@jazbaatbadalgaye no I didn't and its buried underneath the heated bed...
-
@dave-parry Ok Got it done. Installed 3.3 using bossa. Then tried to install 3.4.0beta 5 and just got the same problem. So I erased again with bossa and used YAT to install 3.4.0 Beta 5 and it worked. However I would like to know why it won't work through DWC as normal. If I have to do it with Bossa it means I have to take the heated bed off do the update, re-install and then recalibrate. IfI have to do that each time I want to update I will have to extend the erase pins so they are acessible.
-
@dave-parry After all that it hasn't cured the original fault. Still getting hot end heater errors as soon as I start a print. Do a heater reset, reset temp, wait for it to get back to set temp, restart and it prints fine. Don't think its the problem but tomorrow I will change the sensor and heater cartridge and see if it helps.
-
Maybe a redundant question, but you say that you store the pid calibration with M500.
Then it's saved to the config-override.g.
Do you load that in the end of the config.g with M501?
-
@gixxerfast yes it's in the file.
-
@dave-parry It seems it was a problem with the V6 hotend.
Took it apart, cleaned and re-installed and its so far been OK.
I think the block may have loosened from the heatbreak a little bit.
But would still like to get to the bottom of the update problem. -
@dave-parry ok, thanks for the update about the heater fault. Will be interesting to see if it is now fixed over repeated uses.
We can test the upgrade again when the next beta comes out.
