Further update:
The print above finished, and I was able to print another part of the same assembly from F360.
As far as I can tell, grounding the negative output of the PSU fixed the issue.
I will report back to this thread if the software reset occurs again, but if I never do- assume the problem is fixed.
Thanks again, Folks!
UPDATE:
Possible Solution-
After grounding the items you specified, the next print of the large saw adapter part has reached 78% and has been printing all night, 10 hours at this point.
Hate to speak too soon, but I see no reason that it would fail at this point, the mystery errors always happened relatively soon in the print.
I will keep printing and remove the grounds one by one until I find the one that matters, which I suspect is the grounding of the power supply itself.
The Meanwell LPV-150-12 PSU I'm using actually does not have a ground connector, it is double insulated and meant to be installed inline. It has been suggested to me that this is the source of the problem. It has no ground connector, but connecting the PSU negative output to the power cord ground conductor may have done the trick.
Thanks, DC42 for sticking with me through this troubleshooting. I'll report back when I track down exactly what was causing this, initial indications are that grounding was in fact the issue.
Thanks again!
@dc42 said in Duet Maestro Resetting and Stopping print, HELP! (Thanks!):
Thanks! For the future, it will help if you can save the M122 output in a way that preserves the line endings.
I saved it as CSV this time, hopefully that works as it is the only other option I can see:
This report will have several failures and successes. For example, I drew a 3" diameter 6" tall cylinder in Sketchup, and one in F360. and sliced both in vase mode with identical setttings. The SU one completed, the F360 has failed twice so far. I was advised to make a perfectly identical model, i.e. make a 24 sided figure in F360 to exactly match Sketchup's 24 side circles, so I did.
I printed that model, and it also failed. Always the same thing, spinning module something or other and reset.
These are all different. That suggests strongly that the problem is either a faulty microcontroller (rare), or the microcontroller is overheating (which I would have thought unlikely, and the readings in the M122 report are good), or a transient or static discharge is causing the problem. So I would like to explore the possibility of a transient or static discharge causing the problem. Here are some suggestions:
- Make sure that you don't have a USB cable connected to the Maestro (of if you do, see the wiki page on USB ground loops)
I disconnected the USB first thing, so all the subsequent prints (and failures) have been without it.
- Make sure that all of the following are grounded: bed plate (very important when using an AC mains bed heater), negative output of the PSU, all stepper motor bodies (possibly through the printer metalwork, but if you are relying on this, check using a multuimeter)
- Preferably, ground the hot end metalwork too
I made a harness just now and grounded all of these things, checked with my meter. The 24 side F360 cylinder is printing again now, we willl see if it succeeds fuinally.
Just in case it is related to MCU heating, please keep an eye on the MCU temperature reading during your next print.
I have watched it, I have never seen it go above about 32.4
I will keep making prints and collect more data.
I tried a new print, something made in Fusion 360 but not the same file, and in fact I've printed this file successfully before.
It still stopped about an our in.
Here is the M122 report:
I'm trying now with a file that was not made with F360 just to see if that somehow works.
Thanks for looking at this.
Hello,
The print quit less than an hour in- Here is the report text file:
I hope this helps "us" narrow it down! Thank you!
@dc42 said in Duet Maestro Resetting and Stopping print, HELP! (Thanks!):
Unfortunately the hard fault reported had the "imprecise" flag set, which means the stack data was not valid. This makes the fault hard to diagnose.
So please can you send me further M122 reports. If this type of fault repeats, then I will make a special firmware build that will make it easier to track down.
I will keep running this print and sending the M122
As you are the only user reporting this problem, it could be that you are using the Duet in an unusual way. Please tell me:
- Are you printing the GCode file from the built-in SD card? If not, are you printing via USB? or external SD card? or some other way?
From the built-in SD, in the normal way as far as I am aware
- What type of display (if any) is connected to the Duet? If it is a PanelDue, what M575 P1 line do you have in config.g?
I have the stock CR-10s lcd display plugged in and working, as it has been since I installed this Duet several months ago.
- What sort of printer is it?
It is a Creality CR-10s, with a Bondtech direct drive replacement, and the Duet Maestro running it. It has a 120v bed heater run with a SSR.
- What power supply does it have?
Meanwell LPV 150 12
This may be a red herring, but this is how this started:
-I drew a large part in Fusion 360
-I split the part into 2 parts for printing
-The first part was only 1.5 inches in height and printed fine.
-The second was nearly (397 of 400mm) too tall for the print volume, but it sliced.
When I tried printing this, it seemed to work, but there was an anomaly: On the print status page, where it normally shows "line x of 23334456" nothing was shown, there was no total or tally of layers. Aso, in the time-prediction windows below, some were blank since it had no layer information.
When the print repeatedly failed, I went back to F360 and split the large part into two parts. I tried slicing the smaller parts, and this time when loading the STL into DWC, all the layer and other info was shown correctly.
However, this print still failed in the same way, resetting for no apparent reason. Like I said, this could be totally unrelated, but ever since something loaded with no layer information, I've been having this problem.
I'm running the print again now, history indicates I will have a M122 for you in about an hour.
Thank you!
@dc42 said in Duet Maestro Resetting and Stopping print, HELP! (Thanks!):
Thanks for your reports.
The last M122 report cotains this:
Last software reset at 1970-01-01 00:00, reason: deliberate Hard fault
The "deliberate" means that RRF executed a special M122 command to test the crash handler. These commands have P parameters in the range P1001 to P1006. Have you any idea how that command could have got sent to the Duet?
Your earlier report was a not-deliberate hard fault. I will look into it now. Meanwhile, if you get any more instances, please capture and post the M122 report again.
I do not have any idea how that command was sent. Each time, the printer is printing normally, until about 1 hour in, when it just stops. I've restarted the print many times, five at least, and it always stops about an hour in but at a random place.
Thanks for helping! I really have no idea what to do to make this work again.
Hello,
I started a print, different item, different slice, and it worked once, but then I did a third print, new slice as before, and the printer reset overnight again.
I figured out how to download the text version of the console:
I really hope that someone can help me, I basically don't have a printer now and have no idea how to get the Duet Board to stop restting on every print.
Thank you for any help you may provide.
OK, I found it in the console, Here are the top few lines:
Here is the complete report, I hope:
it only appears for a second or two and it's hard to screen shot it.
2.05.1 (2020-02-09b1) is the firmware version.
I don't use the sensor, it is "shorted out" with a jumper now so the input thinks it has filament no matter what. Never been an issue before. I will try disconnecting the filament sensor entirely and running the print again.
. . .
Well, the print started just fine with nothing plugged in to the sensor connector. We'll see what happens.
I saw another post where a person was having this problem, and it turned out to have something to do witht he SD card, they "repaired the file structure" and that helped, but I don't know how to do what they are describing.
I'll see how this print goes.
Duet Maestro has worked fine for many months, completed a 14hr print last week- never an issue.
Now, three times in a row, I come back to find the print stopped at a random point around an hour into a 20 hour print. Printer is reset as if it had b een turned off and back on.
I looked over some posts, and one recommendation was to send M122 and see what the reason for rest was. I did so:
image url)
I don't know what "Hard fault, spinning module FilamentSensors" means.
I have the stock CR-10s filament sensor itself defeated with the included jumper for doing so.
Printer is essentially unusable at this point- Any ideas how to prevent this automatic print destruction feature?
Phaedrux,
Thanks for that insight. Based on your description, it seems to be functioning as normal. Thank you for explaining it.
Phaedrux, thank you for your reply. i have modified my homeall to look more like what you suggest.
I do still have one lingering issue- Z babystepping does not seem to function. I've got it so it starts low enough now, but even if I try to raise the Z height during printing, nothing happens.
For example, when it homes, Z positoin reports as 3.97 and then when the print starts, it reports as .25, as expected.
At that point, the print starts and the nozzle is basically touching the sheet- I use a very rough aftermarket PEI powedercoated sheet, so although the nozzle is just rubbing, the valleys give the plastic aplace to go. i would like to bump it up just a hair, so it's not actually touching, but when I use babystepping to try to raise the nozzle a bit, nothing happens. The head position still says .25
I do happen to have my "normal" jog control set to 0.1 z movement, and if I press that, it will change, say from .50 to .60.
But why won't z babystepping work?
Thanks for your helop and replies. . . I really appreciate it!
That worked, I was able to fix the z homing. I know you answer noob questions 1000s of times, but thanks for helping me anyway!
Hi folks,
People here have really helped me out with my last problem, so hopefully youall can sort this one out:
I've tried repeateadly to set the z offset. I have a Maestro with a BLTouch I just installed on a CR-10s.
No matter what, I cannot get it to lower the nozzle more than about 1mm from the bed. Moving the nozzle to touch the bed Resetting Z to zero may appear to work, but after that, when you start a print, it moves up and will not allow you to babystep any lower. Setting the z offset according to instructions does nothing- It always start about 1mm up after homing.
I'll post my config.g here:
; Configuration file for Duet Maestro (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Feb 23 2020 23:10:13 GMT-0600 (Central Standard Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"CR-10x" ; set printer name
M918 P1 E4 ; brian- enabling lcd
; Network
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E415.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z1000 E500 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X0 Y10 Z0 S1 ; set axis minima
M208 X305 Y315 Z350 S0 ; set axis maxima
; Endstops
;M574 X1 Y1 Z1 S1 ; set active high endstops (original setting)
M574 X1 Y1 S1 ; X home to min. Y home to min. NC limit switches
M574 Z1 S2 ; Define Z to use Probe. Home to min
; Z-Probe
;M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed (original setting)
;M557 X15:300 Y25:300 S20 ; define mesh grid (original setting)
M558 P9 H3 F100 T6000 ;Setting up BLTouch. F=speed of lift. T=speed of movement between points
G31 X36 Y-4 Z.87 P25 ;BLTouch offset
M557 X50:250 Y50:250 S50 ;Define mesh grid
; Heaters
M305 P0 T100000 B4138 R2200 ; set thermistor + ADC parameters for heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 R2200 ; set thermistor + ADC parameters for heater 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C
; Fans
M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H-1 ; set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off
; Tools
M563 P0 S"Main Extruder" D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
; Custom settings are not defined
I've changed the G31 line repeatedly, and it makes no difference. Z baby stepping used to work, but now it simply will not lower the nozzle during a print. I've made no changes that would affect that, that I can tell.
Many posts seem to mention a config-override.g file but I do not seem to have one.
I have messed with my home all and home z files, so I will post those as well:
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Feb 23 2020 23:10:13 GMT-0600 (Central Standard Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-310 Y-310 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-310 Y-310 F360 ; move slowly to X and Y axis endstops once more (second pass)
G1 X50 Y50 F4000 ; make z home on bed, not off edge
M280 P64 S10 ; drop pin
G1 H1 Z-355 F360 ; move Z down stopping at the endstop
G90 ; absolute positioning
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)
M280 P64 S90 ; lift pin
; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Feb 23 2020 23:10:14 GMT-0600 (Central Standard Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G90 ; Absolute for z homing position
G1 X50 Y50 ; make z home on bed, not off edge
M280 P64 S10 ; drop pin
G1 H1 Z-355 F1800 ; move Z down until the endstop is triggered
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)
M280 P64 S90 ;lift pin
; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning
I'm sure i've goofed something up, I'm just not sure what!
Many thanks for any help- I've spent hours and hours on this and the more i mess with it the worse it gets. . .
Hi,
I hope someone can help- I recently installed a Duet Maestro on my CR-10s and got it working. I'm not good with this type of thing but from the directions and posts here and on Reddit I made it happen.
My prints always start too high even after doing the paper under the nozzle thing. While I was trying to figure that out, I accidentally entered "g90 z0" instead of using g92 to rest Z position. I'm not sure that's what did it, but since then, or perhaps all along, I've had a weird problem:
The BLTouch bracket on the right, in blue, was printed with this printer, after installing the BondTech extruder on the CR-10s, but I think it was before Duet Maestro was installed. The left one is the same file.
In any case, I installed the board, and set it up. When I try to print the same bracket, I get the result you see on the left. I thought it might be because I accidentally set the printer to relative movements as described above, but I've tried sending g90 and I tried adding g90 to the starting script, and I've checked that g90 is in the start of my config file.
The only change that I have (knowingly) made is to add the command to enable the LCD and that seems to work fine.
Asking around, It's been suggested to me that if it isn't g90, then maybe my z e-steps are wrong.
The print starts ok (except I have to baby-step z down some to get it close to the bed despite leveling it) then the second layer will adhere, but by the third layer, the outlines don't stick, and each layer the z gets higher and higher above. I've done several other tests and they all exhibit this behavior.
I'm using Simplify 3d to slice, which has worked for me before on other printers.
Any ideas? I'm really stumped. . .
EDIT: I moved the z axis up "50mm" with the jog controls, and it moved right at 250mm, so it appears to be off by a fcator of 5. If it was a factor of 2 or 4 that would make more sense. . . Anyway I believe that I'm getting 1.25mm of z raise for every ".25mm" the slicer is telling it.
Hopefully this is a simple noob mistake and someone can set me straight. . .