Error status 8 July 14, 2016 05:40PM |
Registered: 9 years ago Posts: 517 |
SENDING:M122 Diagnostics Used output buffers: 1 of 32 (15 max) Platform Diagnostics: Memory usage: Program static ram used: 45208 Dynamic ram used: 40432 Recycled dynamic ram: 376 Current stack ram used: 2728 Maximum stack ram used: 5716 Never used ram: 6572 Last reset 09:01:01 ago, cause: software Error status: 8 [ERROR] Error status: 8 Bed probe heights: -0.017 0.762 -0.261 -0.097 -0.024 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Free file entries: 10 SD card interface speed: 21.0MBytes/sec SD card longest block write time: 0.0ms MCU temperature: min 35.8, current 41.0, max 53.5 Slowest main loop (seconds): 0.138367; fastest: 0.000000 Move Diagnostics: MaxReps: 5, StepErrors: 0. Underruns: 26 Heat Diagnostics: Bed heater = 0, chamber heater = -1 Heater 0 is on, I-accum = -54.0 GCodes Diagnostics: Move available? no Stack pointer: 0 of 5 macro is idle http is idle telnet is idle serial is ready with "M122" aux is idle file is idle Network Diagnostics: Free connections: 16 of 16 Free transactions: 24 of 24 Webserver Diagnostics: HTTP sessions: 1 of 8 FTP connections: 0, state 0 Telnet connections: 0, state 0
Re: Error status 8 July 15, 2016 06:43AM |
Registered: 10 years ago Posts: 14,684 |
Re: Error status 8 July 15, 2016 08:08AM |
Registered: 9 years ago Posts: 517 |
Quote
dc42
2. When the last reset code is "software", there is usually a "Last software reset reason" displayed as well. But there isn't in your M122 output. Which Duet do you have, and which firmware version on it? Is it possible that the software reset that occurred 9 hours before you ran M122 was because you upgraded the firmware at that time?
Quote
3. Can you tell from the "Last reset" time (9 hours before you ran the M122) whether the software reset occurred during the print, or was it before the print started?
Quote
4. Can you confirm that more than one heater was turned off, and the head stopped in the middle of the print?
Re: Error status 8 July 15, 2016 08:27AM |
Registered: 10 years ago Posts: 14,684 |
Quote
ElmoC
Quote
dc42
2. When the last reset code is "software", there is usually a "Last software reset reason" displayed as well. But there isn't in your M122 output. Which Duet do you have, and which firmware version on it? Is it possible that the software reset that occurred 9 hours before you ran M122 was because you upgraded the firmware at that time?
I have a 0.8.5 version. This has occurred on both 1.12a and 1.14. When it happened on the 1.14, it was the first print job after the update.
Quote
3. Can you tell from the "Last reset" time (9 hours before you ran the M122) whether the software reset occurred during the print, or was it before the print started?
This has always occurred during a print and at different points. Some time it occurred early in the print, other time it was close to the end.
Last reset 09:01:01 ago, cause: software
Re: Error status 8 July 15, 2016 08:41AM |
Registered: 9 years ago Posts: 517 |
Quote
dc42
Quote
ElmoC
Quote
dc42
2. When the last reset code is "software", there is usually a "Last software reset reason" displayed as well. But there isn't in your M122 output. Which Duet do you have, and which firmware version on it? Is it possible that the software reset that occurred 9 hours before you ran M122 was because you upgraded the firmware at that time?
I have a 0.8.5 version. This has occurred on both 1.12a and 1.14. When it happened on the 1.14, it was the first print job after the update.
Quote
3. Can you tell from the "Last reset" time (9 hours before you ran the M122) whether the software reset occurred during the print, or was it before the print started?
This has always occurred during a print and at different points. Some time it occurred early in the print, other time it was close to the end.
I think you misunderstood me. When I said the "Last reset", I meant the reset that M122 reported as having happened 9 hours before you ran M122:
Last reset 09:01:01 ago, cause: software
Does the time (9 hours and 1 minute before you ran M122) tie in with when you updated the firmware? Or does it tie in with when the machine stopped in the middle of a print?
Re: Error status 8 July 15, 2016 12:30PM |
Registered: 10 years ago Posts: 14,684 |
Re: Error status 8 July 15, 2016 12:33PM |
Registered: 9 years ago Posts: 517 |