Wiring or settings issue? Stepper Motors not moving



  • Hi all, I believe having an issue with duet wifi. I believe I plugged everything in correctly, and I'll post pictures up here (warning, lots of pictures) of the board. Everything lights up, but when I try to move the motors, nothing happens.
    I got my BLtouch in late August from Spool3d, so that should be the latest version and so I believe I don't need to cut the logic for this one to make it 3.3V? It is flashing red for the warning sign though.
    I don't have the heat bed or thermistors installed on the printer just yet and that shouldn't make a difference. Here is my config.g for the Duet Wifi currently, based off some settings I've seen so far for people with Duet Wifi and BLtouch
    Apologies for the asking for help, I've also checked the duet wiki and such but as this is my first time using Duet (been a Marlin person for the past year and a half), slowly learning and appreciate all the help. Pictures are after the config.g
    Here is my config.g:

    ; Configuration file for Duet WiFi (firmware version 1.17)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool on Fri Oct 20 2017 20:23:53 GMT-0700 (Pacific 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
    M667 S1 ; Select CoreXY mode
    M208 X0 Y0 Z0 S1 ; Set axis minima
    M208 X300 Y300 Z295 S0 ; Set axis maxima
    ; Endstops
    M574 Z0 S0 ; Define active low and unused microswitches
    M574 X1 Y1 S1 ; Define active high microswitches
    M558 P1 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
    G31 P600 X27.25 Y0 Z1.12 ; Set Z probe trigger value, offset and trigger height
    M557 X15:258 Y15:258 S20 ; Define mesh grid
    ; Drives
    M569 P0 S1 ; Drive 0 goes forwards
    M569 P1 S1 ; Drive 1 goes forwards
    M569 P2 S0 ; Drive 2 goes reverse
    M569 P3 S1 ; Drive 3 goes forwards
    M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
    M92 X80 Y80 Z400 E804 ; Set steps per mm
    M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
    M203 X18000 Y18000 Z180 E1200 ; Set maximum speeds (mm/min)
    M201 X500 Y20 Z250 E250 ; Set accelerations (mm/s^2)
    M906 X800 Y800 Z800 E1000 I30 ; Set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout
    ; Heaters
    M143 S280 ; Set maximum heater temperature to 280C
    M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
    M305 P0 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 PHEVO (Hypercube Evolution) ; Set machine name
    M551 PChief24433100 ; Set password
    M552 S1 ; Enable network
    M587 SShana P"16888888" ; Configure access point. You can delete this line once connected
    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
    M307 H3 A-1 C-1 D-1 ; This sets the H3 exp pin to be your probe deploy signal.
    ;Set Z probe type of P5, and X0 Y0 Z1 says this is only for Z
    ;H sets dive height or expected main difference between nozzle/probe of 3mm
    ;F200 sets feed rate, or rate of moving probe head down to contact with bed
    ;T5000 sets travel speed between points
    M558 P5 X0 Y0 Z1 H3 F200 T5000
    ; Set Z probe trigger value, offset and trigger height
    ; My probe is in front of and to the left of my nozzle by those distances
    ; my measured z offset was 1.89
    G31 P600 X-25.4 Y-38 Z1.89
    ;setting up mesh bed grid, note this needs to be customized to your build platform (mine is 288x300, but offset on one end as probe head can only go to 260 max, which is really 260 + 25 or 285 in x, and 260+38 or 298 in y
    M557 X0:260 Y0:260 S10 ;

    Retractprobe.g:
    M280 P3 S90 I1

    Deployprobe.g:
    M280 P3 S10 I1

    Homez.g
    T0 ; select first hot end
    G91 ; Relative coordinates
    G1 Z5 F200 ; Lower bed.
    G4 P500 ; Dwell for 500ms - to ensure bed is down
    G90 ; Absolute positioning
    G1 X144 Y150 F3000 ; Go to first bed probe point and home the Z axis
    M401 ; Lower Z probe (BLTouch)
    G30 ; Calibrate Z-axis
    M402 ; Retract Probe
    G1 Z1 F200 ; Raise bed to 1mm.

    Meshlevel.g
    T0 ; Select first hot end
    G91 ; Relative coordinates - for dropping Z no matter what its current height
    G1 Z4 F6000 ; Lower bed to avoid hotend dragging in bed.
    G28 Y ; Home Y axis first to avoid dock crash
    G28 X ; Home X
    G90 ; Absolute coordinates
    G1 X144 Y150 F3000 ; Go to first bed probe point and home the Z axis
    G28 Z ; Home Z given we are in a known safe on-bed position
    M557 X0:250 Y0:250 S50 ; Define mesh grid
    M401 ; Lower BLTouch probe
    G29 S2 ; Clears bed height map in RepRapFirmware
    G29 ; Kicks off the Z probing across the height map
    M402 ; Retract BLTouch probe
    M374 ; Save calibration data. Default is sys/heightmap.csv
    G1 X10 Y10 F3000 ; All done




  • administrators

    I haven't spotted anything wrong with your configuration files. Here are some suggestions:

    1. Please confirm that you have adjusted your endstop wiring to allow for the different pinout of the connectors on the Duet compared with RAMPS etc. (e.g. the 3.3V pin is the centre one).

    2. Please confirm that the web interface is staying connected and the green 3.3V LED is remaining on.

    3. Please confirm that you are supplying 12V or 24V power and the blue LED is on, and it stays on when you try to move the motors.

    4. Send M122. In the diagnostic report that it produces, check that the reported power voltage is what you expect.

    5. Run M906 with no parameters and check that it reports the correct motor currents, in case for some reason they haven't been set.

    6. Do the motors respond to raw motor moves? See https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_CoreXY_printer#Commissioning.

    7. After trying to move the motors, check the GCode Console page of the web interface for error messages.

    HTH David



  • Hi dc42! Thanks for the super fast response. I found part of the issue. The wiring to the board was correct, but not to the motors themselves facepalm. However, once I fixed them and tried again, still the same thing.

    1. Yep the endstop works, and I triple checked the wiring for them. When (they're optical endstop) I push the carriage to the end, the endstop red lights turn off on the Duet Wifi.

    2. Yes the web interace is connected and the LED 3.3V is on.

    3. I am using a 500W 24V 20 A power supply, the blue LED is on and stays on when I try to move the motors

    4. Here is my M122 report, interesting enough as I was doing this, a code came on stating that it did not G28 X homing failed, but i never ran that.

    M122
    === Diagnostics ===
    Used output buffers: 3 of 32 (8 max)
    === Platform ===
    RepRapFirmware for Duet WiFi version 1.19 running on Duet WiFi 1.0
    Board ID: 08DDM-9FAM2-LW4SD-6JKD4-3S46N-92XVW
    Static ram used: 21176
    Dynamic ram used: 96000
    Recycled dynamic ram: 1608
    Stack ram used: 1304 current, 4840 maximum
    Never used ram: 7448
    Last reset 00:05:22 ago, cause: power up
    Last software reset reason: User, spinning module GCodes, available RAM 7448 bytes (slot 4)
    Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 3.7ms
    MCU temperature: min 67.3, current 82.1, max 95.7
    Supply voltage: min 28.7, current 29.3, max 31.7, under voltage events: 0, over voltage events: 0
    Driver 0: ok
    Driver 1: ok
    Driver 2: ok
    Driver 3: ok
    Driver 4: ok
    Date/time: 2017-10-21 14:14:25
    Slowest main loop (seconds): 0.006355; fastest: 0.000031
    === Move ===
    MaxReps: 2, StepErrors: 0, FreeDm: 240, MinFreeDm 236, MaxWait: 36474ms, Underruns: 0, 0
    Scheduled moves: 29, completed moves: 29
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heater = 0, chamber heater = -1
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Segments left: 0
    Stack records: 2 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
    autopause is idle in state(s) 0
    Code queue is empty.
    Network state is running
    WiFi module is connected to access point
    WiFi firmware version 1.19
    WiFi MAC address 60:01:94:33:84:e4
    WiFi Vcc 2.60, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 39568
    WiFi IP address 10.138.42.132
    WiFi signal strength -64dBm
    HTTP sessions: 1 of 8
    Socket states: 2 0 0 0 0 0 0 0
    Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)

    5. Here is my M906 Motor current (mA) - X:800, Y:800, Z:800, E:1000:1000:1000:1000:1000:1000:1000:1000:1000, idle factor 30%

    6. Tried and no they don't. I had three extra motors, and I thought maybe somehow both motors were dead, so I switched to check and still nothing.

    7. No errors at all, like none, even the G28 X home failed didn't show up.

    I also added in the deployprobe.g and retractprobe.g
    Something interesting to note, when I turn off the Duet, I heard one of the motors disabling itself, which means power is going to it?

    My BLtouch is flashing red at the start due to me not cutting the logic to make it 3.3V (I was told didn't need to for the newest BLtouch, but I guess I do need to. However that shouldn't cause the motors not to be able to move right?



  • Here's a picture of my machine settings:


  • administrators

    The problem is your supply voltage reading. The motor drivers are rated at 30V, and the firmware disables them to protect them if the measured voltage exceeds 29V. The M122 report is reporting more than 31V as the maximum value read.

    The reading could be high either because the VIN voltage really is that high, or because the 3.3V rail is low, perhaps because it is overloaded.

    If you have a multimeter, please measure the VIN voltage at the terminal block, and the voltage between the +3.3V and ground pins on one of the endstop connectors or the Z probe connector.

    If VIN is correct (24V) but the 3.3V rail is low, try powering up with your endstops and bltouch disconnected, and see whether the 3.3V rail returns to normal and the M122 reported voltage agrees with your measurement.


  • administrators

    PS do you have a jumper across the 5V_EN pins to enable the on board 5V regulator? Or are you providing 5V some other way?



  • Hi dc42 just checked that, yeah this is weird, my Multimeter says my Power supply is supplying 24V only, I've double checked that, nothing else should be connected to the thing. Let me check the voltage between the +3.3V and ground pins.

    For the 5V_EN I only have the jumper (well i didn't do anyting to that, just what is shows me right ) on the Jumper INT 5v EN, and NOT the Jumper EXT 5V EN. Do I need one for that over there?



  • Here are the jumpers if it's what I think you are talking about:



  • Hi dc42, I decided to turn the PS voltage lower than it reads (20V) and it worked. the only problem now is that the motors just start right on startup and won't stop, and the BLtouch still flashes red and won't deploy. That's a start though. here's the new M122 === Diagnostics ===
    Used output buffers: 3 of 32 (8 max)
    === Platform ===
    RepRapFirmware for Duet WiFi version 1.19 running on Duet WiFi 1.0
    Board ID: 08DDM-9FAM2-LW4SD-6JKD4-3S46N-92XVW
    Static ram used: 21176
    Dynamic ram used: 96000
    Recycled dynamic ram: 1608
    Stack ram used: 1304 current, 4840 maximum
    Never used ram: 7448
    Last reset 00:03:09 ago, cause: power up
    Last software reset reason: User, spinning module GCodes, available RAM 7448 bytes (slot 0)
    Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 3.7ms
    MCU temperature: min 70.5, current 83.7, max 95.1
    Supply voltage: min 22.7, current 24.2, max 26.2, under voltage events: 0, over voltage events: 0
    Driver 0: stalled standstill
    Driver 1: stalled standstill
    Driver 2: stalled standstill
    Driver 3: standstill
    Driver 4: standstill
    Date/time: 2017-10-21 16:04:01
    Slowest main loop (seconds): 0.006607; fastest: 0.000031
    === Move ===
    MaxReps: 2, StepErrors: 0, FreeDm: 240, MinFreeDm 236, MaxWait: 18346ms, Underruns: 0, 0
    Scheduled moves: 13, completed moves: 13
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heater = 0, chamber heater = -1
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Segments left: 0
    Stack records: 2 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
    autopause is idle in state(s) 0
    Code queue is empty.
    Network state is running
    WiFi module is connected to access point
    WiFi firmware version 1.19
    WiFi MAC address 60:01:94:33:84:e4
    WiFi Vcc 2.61, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 39512
    WiFi IP address 10.138.42.132
    WiFi signal strength -65dBm
    HTTP sessions: 1 of 8
    Socket states: 2 0 0 0 0 0 0 0
    Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)



  • Hi all, just wanted to provide an update and need some more help. Apparently my BLtouch is defective, despite only using it a couple of times on my Delta. It had the magnetic loss issue, so wouldn't retract anymore. So I will have to switch to a mechanical stop for now unfortunately. Thanks for all the help again.


  • administrators

    A jumper across 5V INT EN only is correct.

    As your multimeter confirms that the PSU was supplying 24V, I think the 3.3V rail (which is used as the reference for measuring VIN) must be low. Are any components on the Duet getting hot?

    When you say that the motors start right on startup, do you mean as soon as you apply power, or when you press one of the Home buttons?



  • No none of them was getting hot, just a little warm.

    About the motors, it was a config I borrowed from a friend, he had auto home set up. It's been fixed now. Thanks, now I just need to either get a new BLtouch or stick with mechanical endstop.


  • administrators

    Please measure the 3.3V rail, I think you will find the voltage is low.



  • Unn which one is the 3.3V rail? xD


  • administrators

    Measure between the 3V3 pin and ground pin of any endstop connector, or between the 3V3 pin and ground pin of the Z probe connector.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.