DuetWifi V1.02 DuetEthernet 1.0 Stops Printing Software Reset
-
I have a Fusion3 Printer F400 running a DuetWifi V1.02. During a print it will randomly do a software reset and stop the printer. There are no error messages on the screen. The heaters are turned off. Printer remains still exactly where it stopped. I doesn't always stop in the same spot. Sometimes it doesn't stop at all. Will do it on several different parts. I am using Simplfy3d V4.0.1. Below is the M115 Text as well as the M122 Text. Fusion3 tech support has been really helpful, but cannot seem to fix the issue. I think because it is a Duet Problem. Again the same exact file not re-sliced can either print ok, or stop in random spots at random times so I do not think it is the slicer program.
7:39:12 AMM115
FIRMWARE_NAME: RepRapFirmware for Duet Ethernet FIRMWARE_VERSION: Fusionware 1.18.1 RC1 ELECTRONICS: Duet Ethernet 1.0 FIRMWARE_DATE: 2017-05-156:08:39 AMM122
=== Diagnostics ===
Used output buffers: 2 of 32 (8 max)
=== Platform ===
Static ram used: 25020
Dynamic ram used: 89876
Recycled dynamic ram: 3888
Stack ram used: 1104 current, 3824 maximum
Never used ram: 8464
Last reset 23:53:02 ago, cause: software
Last software reset code 0x5003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0040080f, BFAR 0xe000ed38, SP 0xffffffff
Spinning module during software reset: GCodes, available RAM 4072 bytes (slot 2)
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 25.7, current 29.3, max 35.2
Supply voltage: min 23.6, current 23.7, max 23.9, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: stalled standstill
Driver 4: standstill
Date/time: 2019-01-14 06:08:38
Slowest main loop (seconds): 0.007812; fastest: 0.000000
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
Code queue is empty.
=== Network ===
State: 4
=== Webserver ===
HTTP sessions: 1 of 8
FTP connections: 0, state 0
Telnet connections: 0, state 0
6:08:28 AMConnection established!
6:08:22 AMPage Load complete! -
The firmware version you are running (1.18.1RC1) is nearly 2 years old and we no longer support it. The software reset code (0x5003) indicates that the secondary watchdog timed out, but that firmware version doesn't provide a stack trace, so we can't offer further diagnosis.
I know that Fusion 3 have their own firmware modifications, so I don't know whether our standard current firmware (version 2.02) will work with your machine. You could ask F3 whether any of the modifications they made are essential to the operation of the machine, and also whether they have a later firmware version.
-
DC42,
Thanks! I will pass this on. This has been an ongoing issue for about 10 months. My first printer had a Duet board that did not have the built in ethernet. They upgraded it to one like this. After about 7 months of experimenting, sending new boards, new screens, adding ground wiring, etc. We both decided it was time for a new printer. In November, I got a new printer and at first all worked great. Then about two weeks ago, I had a small print fail. Then over the weekend, I had two large prints fail. The original printer and board gave us a power up reset, even though it never went down. This one gives us a software reset. They are sending me another board with a different firmware, the problem is I don't think they know what is wrong and are just hoping this fixes it. I sent them your text to see what they say.
-
DC42,
Where can I get a copy of this new firmware. I am afraid that I am about to go down the same path that I have gone down with them for months. I don't think it is a hardware issue myself. I think it is firmware or some sort of software issue.
-
https://github.com/dc42/RepRapFirmware/releases/tag/2.02
Or... You can go to the "firmware and installation" where new releases and release candidates are discussed.
-
DC42,
I need to ask one more question. I have a DuetWifi V1.02 in another printer I have a Duet2 V1.03. Which is the latest version? I am trying to do research to assist in solving this issue. I would like to use the latest board I would think.
-
The Duet 1.03 is a later PCB revision than the 1.02. For the differences, see https://duet3d.dozuki.com/Wiki/Hardware_Overview#Section_PCB_revision_history. Both can run the same firmware.
-
Well, it happened again. They sent me a new board. This one is a Duet 2 V 1.04a. This was a different file than before and a much shorter print. Below is the M115 and M122 code info. Does this reveal anything different than before? Either being the same info on a different board or other. Any info or help is greatly appreciated.
7:16:53 AMM115
FIRMWARE_NAME: RepRapFirmware for Duet Ethernet FIRMWARE_VERSION: Fusionware 1.18.1 RC1 ELECTRONICS: Duet Ethernet 1.0 FIRMWARE_DATE: 2017-05-15
7:16:46 AMConnection established!
7:16:41 AMPage Load complete!6:08:50 AMM122
=== Diagnostics ===
Used output buffers: 2 of 32 (8 max)
=== Platform ===
Static ram used: 25020
Dynamic ram used: 89780
Recycled dynamic ram: 3984
Stack ram used: 1104 current, 3824 maximum
Never used ram: 8464
Last reset 08:36:44 ago, cause: software
Last software reset code 0x5003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0040080f, BFAR 0xe000ed38, SP 0xffffffff
Spinning module during software reset: GCodes, available RAM 4208 bytes (slot 0)
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 32.4, current 35.5, max 39.3
Supply voltage: min 23.5, current 23.6, max 23.7, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: stalled standstill
Driver 4: standstill
Date/time: 2019-01-23 06:08:50
Slowest main loop (seconds): 0.003906; fastest: 0.000000
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
Code queue is empty.
=== Network ===
State: 4
=== Webserver ===
HTTP sessions: 1 of 8
FTP connections: 0, state 0
Telnet connections: 0, state 0 -
I can't support that old firmware version, and updating to latest firmware will very likely fix it. See my earlier reply.
-
DC42....Thanks. I have told Fusion exactly what you have stated about the firmware and they state that they can't go to the latest firmware. They have given me some stupid reason for not doing it. So my question is this.......
If they send me their firmware, would it be possible for me to basically make the changes that they need to the latest firmware and then debug myself. I can't very well ignore what they have changed and just update the firmware as I am guessing it would't work.
Thanks again for your help.
-
There have been huge changes to the standard firmware since 1.18. So you would need to establish what changes they have made to the standard 1.18. Then try to make the same changes to the latest standard firmware.
-
DC42
I am still waiting on a reply from Fusion3. In the meantime I have tried to do another print. Again, I had the same software reset. Through all of this, the only thing that has not been replaced has been the Power Supply. Is it possible to get the error that I am getting "software reset" due to a power supply being undersized. Again, I am just throwing darts trying to see what I might hit.
They are looking into upgrading the firmware.
