Duet not extruding on x axis and panel due has no screen
-
I've tested a little more and the x axis will move now dont know why its the same motor wire from the y i was testing it with i have the motor out just sitting on the machine same with the e didn't but nothing on e still at all no matter what can't even feel the motor engage to hold it in place
-
It's very difficult to diagnose from a distance. I'm wondering if it's a power supply issue. Maybe it's only just able to supply a small amount of power so that when you try to drive one or more motors, the voltage drops. Are you able to measure the voltage at the input terminals of the Duet? Preferably when you try to drive a motor. Also, after you've tried to move the extruder and X axis motor, could you run M122 and post the results of the diagnostics. I, or more likely David, might be able to spot something in that.
-
Ok will will measure the terminal voltages and run the M122 command and post the findings to you I will have to do it in just a little bit as I have to finish up an animation so I don't get behind on it but I will do it as soon as possible again thank you
-
ok i finished my work and started back looking at the printer i found the problem with the x motor is the cheap cable wire that was supplied with the printer i made a new one with some better wire like i did for the e motor and its working fine again so i ordered quality wire for all the motors (it kinks if you look at it worng) as that too is going to get replaced immediately so that issue is solved wire will be here monday. as for the e motor even with a new cable i get nothing i also remapped to the e1 driver and still got nothing tested with 2 different cables and 2 different motors on both drives same results with both test. i checked the voltage at the duet terminals and it was at 11.99v so the voltage looks good and this was what i got when i ran the M122 command
8:00:34 PMM122
=== Diagnostics ===
Used output buffers: 1 of 32 (4 max)
=== Platform ===
Static ram used: 20320
Dynamic ram used: 72784
Recycled dynamic ram: 1104
Stack ram used: 968 current, 2940 maximum
Never used ram: 33924
Last reset 00:01:22 ago, cause: power up
Last software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Spinning module during software reset: GCodes, available RAM 33576 bytes (slot 0)
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 32.8, current 37.1, max 40.0
Supply voltage: min 11.9, current 11.9, max 12.3, under voltage events: 0, over voltage events: 0
Driver 0: standstill
Driver 1: standstill
Driver 2: standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 2017-05-20 20:00:34
Slowest main loop (seconds): 0.002307; fastest: 0.000035
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
Code queue is empty.
=== Network ===
WiFiServer is running
SPI underruns 0, overruns 0
=== Webserver ===
HTTP sessions: 1 of 8 -
Ok I did get e1 to work for some reason it didn't assign the number in the config g file when I gave the command so I went back and tested both e0 and e1 and e1 works as should e0 nothing but it's still strange because from my understanding of the m122 command it didn't show any fault at least that I read in it
-
It looks like you are making progress. Also, I couldn't see anything amiss with the result of M122 (but David might spot something that I haven't - no doubt he will step in if he does see anything amiss). So it's looking like all your issues are down to poor cables or connections. As for the E motor, maybe it's a bad motor? Try swapping it with one that you know works consistently. That will prove it one way or another.
-
Yeah I worked out all the other issues mainly cheap Chinese wire but that's going to be fixed and I tried getting the e0 to work but no dice it's printing at the moment on the e1 port I could never get the e0 going
-
And I never got the panel due up either but filastuder said they would replace the panel due and the LCD I checked the wires on that one and they are fine (I'm using the premade wire lead that was optional ) so that will be fixed as well so everything seems good just that e0 but I only use one extruder
-
As I said, try swapping the E motors around. That will prove if it's a bad motor.
-
I did on two different motors when I started having the extrusion issue I purchased two new motors one as a replacement and one just for a spare I've tried all 3 motors and it will not move any of them and they all work on the e1 port I removed the board from the printer and checked to see if there were any wire strands resting on it but it's clean it's mounted to a melamine board with small deriln plastic standoffs I inspected the board for any noticeable marks scratches or burn spots and it appears to be clean I rechecked all motors after I mounted up the board again and replugged everything back up to the duet and again all three motors operate on e1 and not on e0
-
Please share your config.g file and tell us how you are trying to move a motor attached to the E0 motor output.
-
sorry for the delay in response Dc as i was at work but the way i tested the motors is as follows : i placed the motor on the base of the printer then ran a motor wire straight to the duet board loaded up the duet web page and sent an M302 P1 command to let me cold extrude then tried to extruded on the motor . i tried two small cables i have made then i received the premade motor cables i ordered when i got home and retried the test with new cable and both motors and still nothing i uploaded 2 photos to my google drive to show how i have the motors the pics are labeled motor test 1 and motor test 2 just to give you a better visual . i also tried the motor i have currently mounted and the new able i re ran thru the cable chain and still nothing this is the link to the photos and a copy of my config_g it seems correct to me but would definitely make me happy for you to look at it as i am no professional at this and i know i say it a lot but thank you and i am really sorry for all the trouble i know this has been a bit of a pain so thank you .
https://drive.google.com/file/d/0B6CzmHFanmGbV1VBWF9Yb180YXc/view?usp=sharing
; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Sat May 20 2017 22:48:07 GMT-0500 (Central Daylight Time); General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X300 Y300 Z400 S0 ; Set axis maxima; Endstops
M574 X1 Y1 Z1 S0 ; Define active low and unused microswitches
M558 P0 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to switch, the axes for which it is used and the probe + travel speeds
G31 P600 X0 Y0 Z0.05 ; Set Z probe trigger value, offset and trigger height
M557 X15:285 Y15:285 S20 ; Define mesh grid; Drives
M569 P0 S0 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z400 E448 ; Set steps per mm
M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z180 E1200 ; Set maximum speeds (mm/min)
M201 X500 Y20 Z250 E250 ; 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; Heaters
M143 S350 ; Set maximum heater temperature to 350C
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1; Tools
M563 P0 D0 H1 ; 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; Network
M550 PLoKi ; Set machine name
M551 Preprap ; Set password
M552 S1 ; Enable network
; Access point is configured manually via M587 by the user
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Fans
M106 P0 S0.3 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; Custom settings are not configured
-
Did you send T0 to select tool 0 before you tried to extrude?
Have you run M906 to check what the motor current is set to?
Does the motor shaft feel locked after you try to extrude, indicating that there is current passing through it?
-
No I did not send the to command before as I was using the web sever and switching my config_g between t0 and t1 but I will send it thru the gcode console and see if it moves and no I have not run the m906 either as I will try that but I did not feel any stiffness in the motor shaft that indicates current flow I get a faint twitch on the shaft but it can spin easily with my finger tips but I will test now thru the console and with the t0 and the m906 and see if it changes things
-
Ok i did the test you asked and did the commands thru the gcode console and with tool 0 on drive 0 selected when i give the G1 E20 F5 command i get a slight twitch on the motor shaft but the shaft spins freely with little to no resistance on the shaft i switched the motor cable to the drive 1 and set my config_g to use tool 0 drive one and with tool 0 drive one selected given the G1 E20 F5 command the motor moves as it should 5mm per sec and extrude 20mm of filament i issued a M302 P1 command before each test of the motor i ran the M906 command on with the tool 0 drive 0 selected and this is what i got
6:00:27 PMM906
Motor current (mA) - X:800, Y:800, Z:800, E:800:800:800:800:800:800:800, idle factor 30% -
It sounds to me that you have a faulty E0 motor driver. Ask your supplier to replace the Duet under warranty.
