Solved Extruder stopped working
-
This new board won't hold the wifi connection either...keeps dropping out unless I've start the wifi module with YAT.
-
@Corexy said in Extruder stopped working:
won't extrude via extrusion menu or load filament option.
See my note above about cold extrusion. You either need to heat up the extruder or send the command to allow the extruder motor to move without being at temp.
I've start the wifi module with YAT.
Do you have a command in your config.g to enable networking?
Can you post your config.g file?
-
Thanks Phaedrus,
I do appreciate your continued and patient help.
The loss of connection is simply wifi range. I've moved the machine into the living area where signal is strong, and it's staying connected. On the previous motherboard I had a dongle in the garage (which costs and extra plan), and this time I was trying to connect to the house wifi which is unlimited. We have a range extender in the hall to the garage, but it's not helping unfortunately.
I was aware of the heat to extrude rule, but the machine broke down while hot and in the middle of a print, and before I stripped it down I heated the extruder to try and test it. Right now the extruder temp is reading 2000.0 by the way. If you want to add a command to ignore extruder temp for now, that's fine with me and will probably be helpful.
Here's my config.g file. I don't think I've changed anything since the configurator.
; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.2 on Mon Nov 18 2019 18:31:11 GMT+1100 (Australian Eastern Daylight Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Zortrax M200" ; set printer name; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I0 ; configure microstepping without interpolation
M92 X80.00 Y80.00 Z800.00 E420.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 Z300.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z250.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X195 Y195 Z175 S0 ; set axis maxima; Endstops
M574 X1 Y1 S1 ; set active high endstops
M574 Z1 S2 ; set endstops controlled by probe; Z-Probe
M558 P1 H5 F300 T6000 ; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:195 Y15:195 S20 ; define mesh grid; Heaters
M305 P0 T100000 B4000 R4700 ; set thermistor + ADC parameters for heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M305 P1 X201 ; configure PT100 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 H1 T45 ; set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on; Tools
M563 P0 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
-
@Corexy said in Extruder stopped working:
M305 P1 X201
If your PT100 is connected to the first port on the daughterboard this command should be
M305 P1 X200That might solve your -2000 temp problem, which may solve the no extruding problem.
-
That got it (thank you), but I'm not convinced we got the root cause. Temp is now correct. Obviously the json file doesn't upload exactly to the configurator, but I'll take what it's given me.
When I first fired it up, I got a "driver phase disconnected" message, something to that effect.
I plugged in my test motor/lead and it worked in reverse and too fast, so I dialled back my steps/mm and reversed it, all good. I plugged in the usual motor/wiring, and it worked this time. I wiggled the wiring around, but can't reproduce the fault (intermittent, the worst kind). If it goes out to lunch again in the middle of a print I know I have to rerun the long and difficult extruder wires. I recrimped the ends (but it didn't work for a while still), or maybe there was a dirty connection after all these years, but if it does it again it's a rewire for sure.
Are you staff Phaedrux? Do you mind taking me through some other things? I'd greatly appreciate it. Once I've got it up and running I'll be fine to adjust my bed height etc, and I'll go back to old posts to see what I did with probing etc.
I'll start with Z homing...won't do it. Homes X and Y correctly, but Z won't home or respond to commands. I'll post my homing files. I haven't set my IR sensor yet either.
-
Homeall:
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2.1.2 on Mon Nov 18 2019 18:31:12 GMT+1100 (Australian Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-200 Y-200 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-200 Y-200 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 H2 X97.5 Y97.5 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
G91 ; relative positioning
G1 S2 Z5 F100 ; lift Z relative to current position
G90 ; absolute positioningHomex:
; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v2.1.2 on Mon Nov 18 2019 18:31:12 GMT+1100 (Australian Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-200 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F6000 ; go back a few mm
G1 H1 X-200 F360 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioningHomey"
; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v2.1.2 on Mon Nov 18 2019 18:31:12 GMT+1100 (Australian Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Y-200 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y5 F6000 ; go back a few mm
G1 H1 Y-200 F360 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioningHomez:
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v2.1.2 on Mon Nov 18 2019 18:31:12 GMT+1100 (Australian Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 H2 X15 Y15 F6000 ; go to first probe point
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
G91 ; relative positioning
G1 H2 Z5 F100 ; lift Z relative to current position
G90 ; absolute positioning -
@Corexy said in Extruder stopped working:
driver phase disconnected
Yes that could indicate exactly what it says, a disconnected phase of the motor wiring, either a bad wire, corroded connector, or even possibly a bad driver. But the fact that this is a different board than the one you started with I would suspect that it's not the driver but actually the wiring. And from the salt air comments, I'd think corrosion. Unfortunately, disconnecting a motor while it's running like that is a good way to damage the driver chips, so best to get that sorted before doing too much heavy testing.
-
You may need to test your z motor movement by itself to see if it needs to be reversed or if the steps per mm are correct.
You can send G92 Z0 in the console to force the Z axis to act as homed and at Z0 position. Then you can use the jogging buttons to attempt to move it up and down. Start slowly. If possible, adjust the z axis manually to get it clear of the physical endstops first.
-
Yes...I'm with you on that. I'm thinking corrosion as there's no movement of the cables at the plug ends. There was certainly plenty of corrosion on the second/unused extruder driver pins. I've got plenty of slack there, so I might drag the cables through a bit and redo the crimps/plugs both ends.
You're talking about the Z sensor height setting procedure? Yes I can do that. I'd forgotten about G92 Z0 allowing it to move "unhomed".
Another issue is that I can't use the house wifi as it's too weak in the garage, and I want to cancel the contract on the dongle I've used in the past. My phone has a 5gb monthly quota that I never use, and when I tested it's signal as a hotspot it was much stronger than the dongle. I would like to use that, but I've already connected this board to the house wifi via YAT, and it doesn't seem to want to change by the same method.
Can I do it via the DWC?
-
The easiest way to add another wifi network is through the gcode console.
Use M587 to add the new SSID. At boot time, the Duet should choose the SSID with the strongest signal.
-
Belay this one, all good now
It's never ending...
Now when I try to open the DWC, I get this message:
Browsing via the MMS proxy is not allowed. Please use the browsing proxy 10.1.1.181
And that address won't open either. I was only on there a minute ago.
Any suggestions (and thanks again for all your help)?
-
@Phaedrux said in Extruder stopped working:
The easiest way to add another wifi network is through the gcode console.
Use M587 to add the new SSID. At boot time, the Duet should choose the SSID with the strongest signal.
Mate, you're an absolute champ! (don't mean to gush).
It's all working, and surprisingly my old Samsung Galaxy S6 with custom ROM absolutely pounds out a strong wifi signal.
Obviously I've got to re terminate these cables and setup all my homing files etc, but I'm seeing a light at the end of the tunnel.
I won't say "one last thing", because it's possible it won't be, but is there a way to revert the DWC back to the old format without losing any functionality? I'd really just prefer to see the old school screen, I was pretty familiar with that.
-
OK, so straight back into trouble.
I'm trying to calibrate the Z probe trigger height, and it's not playing the game at all. I've done this procedure plenty of times in the past.
I'm raising it until I grip the sheet of paper, then G92 Z0, down 10mm, then G30 S1 and that's where it plays up.
Instead of just staying in the center of the bed and lowering the nozzle to the bed (or raising the bed to the nozzle), it tries to home X, then Y, then moves to a random position and lowers the nozzle just a little.
Never seen it do all that from G30 S1 before...can anybody help?
-
should be G30 S-1
-
@jay_s_uk said in Extruder stopped working:
should be G30 S-1
Cheers mate. It actually did exactly the same thing with that command too.
Wondering what I'm missing here
-
I'd call the extruder issue resolved, and I'll start anew with my tuning issues in the tuning and tweaking section.
Thanks for the help Phaedrux, appreciated
