Welcome! Log In Create A New Profile

Advanced

RepRapFirmware minor release 1.15e

Posted by dc42 
RepRapFirmware minor release 1.15e
October 02, 2016 06:23AM
I have just released this at [github.com]. Changes in this release:
  • Max temperature excursion and heater fault trigger time are now configurable via M570. See [reprap.org].
  • If a heater fault occurs then any SD card print in progress is abandoned. Currently sys/cancel.g is not run, so the head just stops wherever it is.
  • Improved M122 diagnostics headings.
  • Bug fix: some values of pressure advance caused too many extruder steps to be scheduled, resulting in extruder step errors; and another bug in the error handling then caused layer shifts.
The compatible version of DuetWebControl is still 1.12.



Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Re: RepRapFirmware minor release 1.15e
October 02, 2016 09:59AM
M570 looks just like what I need. Many thanks - I will install this as soon as the current print is finished.


DC42 Kossel 330mm x 2meters
My Thingiverse Creations
Re: RepRapFirmware minor release 1.15e
October 02, 2016 10:59AM
Upgrade installed and the following added to config.g. I'm starting with quite high values and will dial them down over time.

;Timeout for Heater Errors
;Pnnn Time in seconds for which a temperature anomaly
;Tnnn Permitted temperature excursion from the setpoint 
M570 H0 P15 T25
M570 H1 P15 T25


DC42 Kossel 330mm x 2meters
My Thingiverse Creations
Re: RepRapFirmware minor release 1.15e
October 02, 2016 02:35PM
This release doesn't appear to help. Shortly after turning on the bed heater I still see errors reading the temperature which causes a failure. Even with the command M570 H1 P25 T150 the short drop to -11c still causes a fault to occur.



Edited 1 time(s). Last edit at 10/02/2016 02:36PM by DADIY.


DC42 Kossel 330mm x 2meters
My Thingiverse Creations
Attachments:
open | download - drop out.PNG (26.6 KB)
Re: RepRapFirmware minor release 1.15e
October 02, 2016 03:37PM
Quote
DADIY
This release doesn't appear to help. Shortly after turning on the bed heater I still see errors reading the temperature which causes a failure. Even with the command M570 H1 P25 T150 the short drop to -11c still causes a fault to occur.


It looks that you have some wiring issues there. You should first try to fix them first. I have no issues with 15c so far.
Re: RepRapFirmware minor release 1.15e
October 02, 2016 05:49PM
DADIY, the error message in the web interface tells you exactly what went wrong.



Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Re: RepRapFirmware minor release 1.15e
October 03, 2016 04:00AM
Odd, this only happens randomly and only when warming the bed the first time. I will strip it down tonight and check the wiring.

But shouldn't M570 H1 P25 T150 ignore that -11c reading as long as it lasts less than 25 seconds?


DC42 Kossel 330mm x 2meters
My Thingiverse Creations
Re: RepRapFirmware minor release 1.15e
October 03, 2016 10:42AM
The disconnected thermistor detection predates the heater fault protection that I added in version 1.15, and it has always triggered a heater fault after just a few bad readings.



Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Re: RepRapFirmware minor release 1.15e
October 03, 2016 12:59PM
Well I think you might have been right about a physical fault. I stripped everything down and it appears that the thermistor might have been shorting out on the aluminium plate as the heat increased - I suspect with expansion it might have caused it. This has now be insulated with Kapton tape and the thermistor itself taped down to stop it being able to move. I have been able to heat the bed three times since this without fault, I'm now going through the bed calibration with M303 to get a value to add to config.g.

Thanks for your continuing support.

PS I seems like this fault detection is probably a good thing after all smiling smiley


DC42 Kossel 330mm x 2meters
My Thingiverse Creations
Re: RepRapFirmware minor release 1.15e
October 10, 2016 03:48AM
Out of interest...

Quote

If a heater fault occurs then any SD card print in progress is abandoned. Currently sys/cancel.g is not run, so the head just stops wherever it is.

Would this turn off all the heaters? Also would anything be logged to the console?

I have had two long running prints just stop after ~3 hours - the heaters turn off but nothing is logged to the console and as far as I can tell from the graph the temperature was OK.


DC42 Kossel 330mm x 2meters
My Thingiverse Creations
Re: RepRapFirmware minor release 1.15e
October 10, 2016 04:56AM
1.15e is a bug fix release, so the changes are minimal and only the heater with the heater fault is turned off at present.

If your print stops unexpectedly, I suggest you run M122 to see whether the print stopped because the board reset (look at how long ago the last reset occurred), and if so what the reset reason was.



Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Re: RepRapFirmware minor release 1.15e
October 10, 2016 02:45PM
So after a few hours of printing everything just stopped, and this is the output from m122. Doesn't look like the board restarted. The only thing that looks high is the MCU temperature.

Any thoughts?

19:40:53M122
=== Diagnostics ===
Used output buffers: 4 of 32 (28 max)
=== Platform ===
Memory usage:
Program static ram used: 45328
Dynamic ram used: 41776
Recycled dynamic ram: 3008
Current stack ram used: 2760
Maximum stack ram used: 5956
Never used ram: 2236
Last reset 02:59:38 ago, cause: power up
Last software reset code & available RAM: 0x0003, 2896
Spinning module during software reset: GCodes
Error status: 0
Bed probe heights: -0.561 -0.573 -0.435 -0.560 -0.504 -0.522 -0.471 -0.522 -0.494 -0.510 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 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 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 374.3ms
MCU temperature: min 7.1, current 53.6, max 57.9
Slowest main loop (seconds): 0.375732; fastest: 0.000000
=== Move ===
MaxReps: 6, StepErrors: 0, MaxWait: 2ms, Underruns: 0, 0
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 0 is on, I-accum = 0.1
=== GCodes ===
Move available? no
Stack pointer: 0 of 5
macro is idle
http is ready with "M122"
telnet is idle
serial is idle
aux is idle
file is idle
=== Network ===
Free connections: 15 of 16
Free transactions: 23 of 24
=== Webserver ===
HTTP sessions: 1 of 8
FTP connections: 0, state 0
Telnet connections: 0, state 0


DC42 Kossel 330mm x 2meters
My Thingiverse Creations
Re: RepRapFirmware minor release 1.15e
October 10, 2016 04:41PM
When the print stopped, were any heaters in the fault state, and was the status 'printing' or 'idle'?

Check that the file you were printing is complete on the SD card. With slic3r in particular, it is quite easy to upload a file via the web interface before slic3r has finished writing it.



Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Re: RepRapFirmware minor release 1.15e
October 12, 2016 04:45AM
I think I have found the cause of my issue, the stepper motor drivers were overheating, reducing the current to them seems to have resolved the issue. I had increased it a little to get some iygus bushing to work nicely some time ago and this is the first time that the print time had been more than an hour since.


DC42 Kossel 330mm x 2meters
My Thingiverse Creations
Re: RepRapFirmware minor release 1.15e
November 10, 2016 02:11PM
Quote
dc42
  • Max temperature excursion and heater fault trigger time are now configurable via M570. See [reprap.org].

What is considered the default M570 command? I've run into the temperature excursion exceeding 10C, and wanted to increase the time slightly but wasn't sure what the defaults being used are.
Re: RepRapFirmware minor release 1.15e
November 10, 2016 05:02PM
If you follow the link in my message that you quoted, you will find the default values. It's up to you how much you increase them.



Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Re: RepRapFirmware minor release 1.15e
November 11, 2016 11:18AM
Are you sure that M570 H1 P5 T10 is actually 10C and not 1.0C? I'm watching the machine that had an issue after 4+ hours and the heater does dip from 190 to 189.5 and then climbs back up to 190. I've got the machine running with M570 H1 P25 T15, but the fault it had the other day and what it does 4+ hours into a print almost make it feel like the default was 1.0C and not 10C.

I'll do some more testing with one of my other printers to see, but just my initial feeling with what I've physically seen from the PanelDue temperatures.


Watching one of the printers, I can see the wild temperature swings. Going to replace the older E3D blocks with the new cartridge thermistor ones as my newer machines don't have the wild temperature swing after 4-5 hours of printing.

Edited 1 time(s). Last edit at 11/11/2016 08:45PM by PDBeal.
Sorry, only registered users may post in this forum.

Click here to login