Extruder motor stops during print…

ofloveandhate

upping the temp by 25° to 210 still yielded a failure last night.

a big lingering question i have – if my browser disconnects from the printer while printing, is the gcode console still guaranteed to log correctly? that is, how do i know that i am not experiencing some other error, and simply not seeing it in the log the next time i connect?

dc42

A delta with 16-tooth pulleys, GT2 belts, 0.9deg motors and x16 microstepping (like mine usually is) has 200 steps/mm. So if you set x64 microstepping in M350 and use M92 after that, 800 steps/mm would be correct.

ofloveandhate

i have stock motors on my d300vs, so should be 0.9. let's double-check the extruder motor (PG35L Micro Extruder Motor)

ofloveandhate

see this d300vs forum post

http://forum.ultibots.com/viewtopic.php?f=49&t=358&p=2075&hilit=microstepping#p2075

for a brief discussion of the stepping modes.

whosrdaddy

@ofloveandhate, can you share the STL of the object you want to print, just want to try printing it (but I don't have a delta :))

ofloveandhate

link is already above (extracted the link from the folder just now). it's in 3mf format.

http://danibrake.org/gcode/failing

i use simplify3d for the manually-placed supports. my same slicer settings work fine for the same model, printing on my taz6 and rostock max v2. i only have problems with my duet-powered machine.

ofloveandhate

two outstanding questions:

in M350 X64 Y64 Z64 E16 I1, does this enable interpolation for all axes, or just the extruder?
if my browser disconnects from the printer while printing (this happens all the time), is the gcode console in the web interface still guaranteed to log correctly? that is, how do i know that i am not experiencing some logged error, and simply not seeing it in the log the next time i connect because it was missed due to not being connected?

whosrdaddy

as David pointed out above, only the extruder will have interpolation
I don't think so (but I could be wrong). If I were you, I would enable event logging
-> add M929 P"eventlog.txt" S1 to your config.g, this way everything will be logged onto the SD card (and maybe the problem you are having )

ofloveandhate

thanks

was that information in "The I1 parameter on the M350 command will work for the E drives because they are set to x16 microstepping."? because that's a compound statement, and i didn't want to assume. so, am i correct in understanding that interpolation applies to all extruders listed in the M350 command, but only if the stepping mode is 1/16? where is this documented? i am happy to refer to documentation.
i enabled logging to a file. is there a way to write the current date or time into the filename, to prevent overwriting the old ones, or can i make it append? does it append by default?

whosrdaddy

here is the documentation for M350:
https://duet3d.dozuki.com/Wiki/Gcode#Section_M350_Set_microstepping_mode

Excerpt from doc (emphasis mine) :

Parameters

Not all parameters need to be used, but at least ''one'' should be used. As with other commands, RepRapFirmware reports the current settings if no parameters are used.
Xnn Set stepping mode for the X axis
Ynn Set stepping mode for the Y axis
Znn Set stepping mode for the Z axis
Enn Set stepping mode for Extruder 0 (use Enn:nn:nn etc. for multiple extruders)
Inn Enable (nn=1) or disable (nn=0) microstep interpolation mode for the specified drivers, if they support it. The Duet WiFi and Duet Ethernet support interpolation (to x256 microstepping) only when configured for x16 microstepping.

whosrdaddy

Concerning the log file:

Date and time (if available) are logged and events are appended to this file.
I believe that the duet will get the correct time if you connect via a browser (I don't know about paneldue)
Its all explained in the documentation: https://duet3d.dozuki.com/Wiki/Gcode#Section_M929_Start_stop_event_logging_to_SD_card

ofloveandhate

thankyou

ofloveandhate

i re-ran my failing gcode (tobel60) with logging on. no information logged, despite a failure.

power up + 00:45:06 Event logging started
power up + 14:22:41 Finished printing file tobel_small_60_norobust.gcode, print time was 14h 20m
power up + 19:26:53 HTTP client 10.0.1.4 login succeeded
2018-02-28 08:34:28 Date and time set at power up + 19:26:53

this time, i printed with interpolation off, to see what would happen. no difference.

dc42

Which firmware version are you using? Logging was introduced in firmware 1.19 and extended in firmware 1.20.

ofloveandhate

1.20

ofloveandhate

what effect will changing this line have?

M111 S0                             	; Debug off

answer, kinda:

M111 S1 P15
Debugging enabled for modules:
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14)

ofloveandhate

the Aprinter firmware claims to work on a duet. see http://reprap.org/wiki/List_of_Firmware

know anyone running it? this would be a good way for me to rule out a firmware bug.

Dougal1957

@ofloveandhate:

the Aprinter firmware claims to work on a duet. see http://reprap.org/wiki/List_of_Firmware

know anyone running it? this would be a good way for me to rule out a firmware bug.

Looking at that link and the online configurator from it it looks like only the 0.6 board is selectable so the wifi/ethernet boards are unlikely to run with it.

dc42

I really don't think it is a firmware issue. Nobody else has reported a similar problem. So I think we are looking at one of the following:

1. Trying to extrude with no tool selected, or with the heater not up to temperature. If this is the case, there will be error messages on the GCode Console page of DWC.

2. Faulty stepper motor, or (more likely) a faulty cable or crimp connection at the end of the cable.

3. Stepper driver overheating, due to a faulty stepper driver or running it at maximum current (2.4A) with inadequate cooling. If you are running firmware 1.20 or later then there would be an error message on the GCode Console page again.

4. Faulty stepper driver chip, or faulty soldering of the stepper driver chip. To rule that out, try using the E1 motor output instead of the E0 output. But I think you already tried that.

5. A good old fashioned hot end jam. Are you able to extrude immediately after cancelling the print? If you run the print with no filament in the extruder, does the motor continue turning right up to the end of the print?

6. Bad GCode causing M906 or M913 being executed to reduce the motor current. Run M906 and M913 without parameters after the fault has occurred and check the reported values.

HTH David

ofloveandhate

thanks for the list.

1. no error messages, so not this

2. replaced stepper motor already. replaced cables from bottom of whip to board once. i could replace again, including the wires in the whip. it could be this

3. no error, same behaviour with two duet boards, same problems with a heat break and active cooling on the duet. not this.

4. same behaviour with two duet boards. same problem on E1. not this

5. no, i am not able to move it – the motor does not respond to requests to move. my gut tells me there might be something to explore here. i will also try generating a fail with an unloaded extruder.

6. seem likely? will do next fault, combined with #5.

7. firmware bug seem unlikely, but we are still unable to rule it out. lack of other reports points to not this, but something with my machine... let's continue to eliminate other causes.

thanks soooo much for your ongoing advice and help. i will solve this issue!!!