Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    First time using duet wifi, nothing working

    Scheduled Pinned Locked Moved
    General Discussion
    4
    22
    2.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • TimVukmanundefined
      TimVukman
      last edited by

      Hi Tinino

      In the configurator, you may find it helpful to make use of one of the stored configurations listed above the spot where you use existing or create new.
      That will get you starting out from a cartesian perspective and not the delta configuration.
      You will need to remove the macros that are intended for delta printers, but you can get to that when you're ready.
      Tim

      1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators
        last edited by

        Regarding stepper motor wiring, typically, red-blue is one phase, and green-black is another phase. So the wiring order I normally use is red-blue-green-black.

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        1 Reply Last reply Reply Quote 0
        • Tininoundefined
          Tinino
          last edited by

          @dc42:

          Regarding stepper motor wiring, typically, red-blue is one phase, and green-black is another phase. So the wiring order I normally use is red-blue-green-black.

          Thank you sir. I'll rewire in that order and mess with the config when I get home today. I appreciate your help

          1 Reply Last reply Reply Quote 0
          • Tininoundefined
            Tinino
            last edited by

            I'm kinda at a loss here. The motors are still doing the same thing, just kinda stepping forward then back. My z axises move however they don't move in parallel, they move one after the other, so it jerks up like 30 degrees on one side, and then jerks up like 30 on another. When uploading the configuration I set it to Cartesian, I calculated the steps with my t8 rod with 2mm pitch, 1mm of movement is like 10. The steppers were originally wired as you described and so I moved them back, my endstops are wired NO and not NC I believe my signal wire is in the right place as well, but maybe I'm wrong? I definitely don't understand what's causing the unparralel z movement, I'm using 2 z steppers which are running off of the same stepper driver it looks like, so they shouldn't be moving separately. My hotend still refuses to heat, but the bed is heating now. I've tried wiring the hotend wires to both options for the heater, neither is working. I used a multimeter and checked the voltage on the hotend heater and it's around 12.24 bolts, but for whatever reason it's not getting a signal, the thermistor is still giving readings however. I even tried plugging in another hotend just to make sure it's not a faulty heater, and the hotend I know works still didn't heat. I'm not sure what to do at this point, and the config setup isn't too hard to use, I'm just not understanding why anything is stepping. Maybe my endstops aren't wired right, maybe I'll try flipping the wires and see how that goes. Any advice on how to address the hotend issue and any more insight on the z steppers? Thanks again for your patience and willingness to help.

            Edit:

            So I looked into NO sensor wiring for the duet and corrected the wiring for my switches. The black wire goes to the NO/signal on the switch and I'm running the red wire to the GND, leaving the middle voltage pin empty. The stepper motors are still doing the same thing.

            I completely removed the mosfet altogether thinking perhaps there's some form of a current issue wiring the board directly to a single 12v psu. All motors still acting the same way no matter what is done with the wiring. Removing the endstops altogether doesn't even correct the issue.

            I triggered the z endstops manually to check the LED's on the board, and to ensure that the end stops were all wired correctly and in the right places. Even though my z axis is super messed up, the motor direction is correct, to test I homed my z axis and the switch worked as it should, so the z stop at least is functioning correctly. X and y axis I am still unable to jog. I modified the configuration to strictly x16 stepping from x16 interpolated to x256, still the exact same issues. Both z axis motors still not moving in unison just an FYI, I reread my paragraph above and it seems to imply that. The stops work, all the motors not so much

            1 Reply Last reply Reply Quote 0
            • Tininoundefined
              Tinino
              last edited by

              Okay. So I ran the z motors in line versus using the 2 separate connections, and now they are working great. However the esteps are definitely off. 1mm of movement is more like 10, but it's progress! Progress at last! My x and y axis are still giving me a hell of a time though, I need some insight on that one. Hotend still not heating. Thanks!

              1 Reply Last reply Reply Quote 0
              • Tininoundefined
                Tinino
                last edited by

                Z axis is calibrated, got the esteps going and it's running flawlessly on the z. However my x and y motors are still jerking back and forth, I can't figure out why this is happening on those two axis. They are no different as far as wiring goes than the z axis. I still can't get my hotend to heat whatsoever. I've repeatedly tried switching between the E0 and E1 heater connectors to no avail, I can only get a thermistor reading. This is a new out of the box E3Dv6 Chimera, so it's not an old janky hotend I'm trying to use. I can't figure out why it won't heat when I select a temp on the web ui. (Or any other place for that matter)

                Edit:

                I hooked my hotend wires into the bed wires and sent a command to heat my bed, the hotend is now heating up along with the bed. Yet the hotend will not heat when plugged into the E0 or E1 heater connectors.

                I've had the board a couple weeks but have only tried to use it with in the last couple days. I don't know an amazing amount about the board but I am questioning exactly what's going wrong with the E0 and E1 heaters.

                I guess this workaround will work for now, but I still have this issue with my x and y I cannot figure out.

                Nevermind, the workaround probably won't work on second thought because the hotend current will be specifically controlled with the bed. I'll keep messing with the firmware I suppose.

                FINALLY got the fricken hotend to heat. That fricken was not directed towards you lol, as you can see it has just been like 8 hours. I'm glad that's finally going. Now to tackle the issue of my x and y axis, then I'm gonna take a look at my extruder motors and see if those are working ok

                1 Reply Last reply Reply Quote 0
                • number40fanundefined
                  number40fan
                  last edited by

                  Want to post your config.g file?

                  If your motor wires are removable, you might want to swap some around to make sure you don't have a bad crimp/connection on the ones that are not working correctly.

                  1 Reply Last reply Reply Quote 0
                  • Tininoundefined
                    Tinino
                    last edited by

                    Just checking back on the thread. I actually was just looking into that. I just took pictures of the crimps I have and was just getting ready to post them. So, coincidentally, here's my amateur crimping job:

                    https://ibb.co/gz8fbG
                    https://ibb.co/fbofbG
                    https://ibb.co/kxrYwG
                    https://ibb.co/k8pxOw
                    https://ibb.co/dsrYwG
                    https://ibb.co/mVOfbG
                    https://ibb.co/do5hqb
                    https://ibb.co/gwM0bG
                    https://ibb.co/ds5RGG
                    https://ibb.co/gbRYwG

                    Just to make sure it WASN'T my steppers, one of my extruder motors was twisting fine, no prob at all, so I swapped the working and the non working, and the issue persisted on the non working (the one that was stuttering) so at this point it's likely my terrible wiring. I'm not great when it comes to crimping but I thought this would work, but not sure. Could you give me an example of a proper crimp or tell me if mine look messed up?

                    Edit: config.g on its way, keep in mind I'm still calibrating esteps and acceleration on the stepper motors, this is the latest version (#17) of my configs. Just trying to get the hardware going so I can calibrate. I'm thinking it's my wiring that's the issue, but obviously I can't be 100% on that.

                    ; Configuration file for Duet WiFi (firmware version 1.17)
                    ; executed by the firmware on start-up
                    ;
                    ; generated by RepRapFirmware Configuration Tool on Sat Sep 30 2017 23:17:50 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 P0 ; Set firmware compatibility to look like native output
                    M208 X0 Y0 Z0 S1 ; Set axis minima
                    M208 X220 Y220 Z240 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 P0 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height
                    M557 X15:205 Y15:205 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 backwards
                    M569 P3 S0 ; Drive 3 goes backwards
                    M569 P4 S0 ; Drive 4 goes backwards
                    M350 X16 Y16 Z16 E16:16 I1 ; Configure microstepping with interpolation
                    M92 X100 Y425 Z425 E723:723 ; Set steps per mm
                    M566 X600 Y600 Z12 E120:120 ; Set maximum instantaneous speed changes (mm/min)
                    M203 X900 Y900 Z180 E1500:1500 ; Set maximum speeds (mm/min)
                    M201 X100 Y100 Z100 E10000:10000 ; Set accelerations (mm/s^2)
                    M906 X800 Y800 Z800 E800:800 I30 ; Set motor currents (mA) and motor idle factor in per cent
                    M84 S30 ; Set idle timeout
                    
                    ; Heaters
                    M143 S260 ; Set maximum heater temperature to 260C
                    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
                    M563 P1 D1 H1 ; Define tool 1
                    G10 P1 X0 Y0 Z0 ; Set tool 1 axis offsets
                    G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C
                    M563 P2 D0:1 H1 ; Define tool 2
                    G10 P2 X0 Y0 Z0 ; Set tool 2 axis offsets
                    G10 P2 R0 S0 ; Set initial tool 2 active and standby temperatures to 0C
                    M568 P2 S1 ; Enable mixing for tool 2
                    M567 P2 E0.5:0.5 ; Set mixing ratios for tool 2
                    
                    ; Network
                    M550 PDuet ; Set machine name
                    M551 P9718321490 ; Set password
                    M552 S1 ; Enable network
                    M587 SFBIVAN-2 P"9718321490" ; Configure access point. You can delete this line once connected
                    M586 P0 S1 ; Enable HTTP
                    M586 P1 S1 ; Enable 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
                    
                    ; Miscellaneous
                    T0 ; Select first tool
                    
                    
                    1 Reply Last reply Reply Quote 0
                    • number40fanundefined
                      number40fan
                      last edited by

                      Easy way to check the connections is to hold two of the wires together and try moving the motor. So, hold the Red and Black together and try moving the motor, Do the same with Blue and Green. If the motor is a little harder to move, then you know the connection is good. If easy like it is without any wires touching, then you know you have a bad crimp.

                      1 Reply Last reply Reply Quote 0
                      • Tininoundefined
                        Tinino
                        last edited by

                        @number40fan:

                        Easy way to check the connections is to hold two of the wires together and try moving the motor. So, hold the Red and Black together and try moving the motor, Do the same with Blue and Green. If the motor is a little harder to move, then you know the connection is good. If easy like it is without any wires touching, then you know you have a bad crimp.

                        And I can do this without the printer being on I take it? I'll test it out tomorrow. It's getting late but I think that's a good start to testing my crimps. Cheers.

                        1 Reply Last reply Reply Quote 0
                        • dc42undefined
                          dc42 administrators
                          last edited by

                          To do this test, unplug the motor from the Duet. Push a short piece of solid core wire into 2 of the connections in the socket to short them.

                          Duet WiFi hardware designer and firmware engineer
                          Please do not ask me for Duet support via PM or email, use the forum
                          http://www.escher3d.com, https://miscsolutions.wordpress.com

                          1 Reply Last reply Reply Quote 0
                          • Tininoundefined
                            Tinino
                            last edited by

                            @dc42:

                            To do this test, unplug the motor from the Duet. Push a short piece of solid core wire into 2 of the connections in the socket to short them.

                            I think I must have a bad stepper driver on my x axis. I fixed my y, my z works as well, but my x refuses to function, it's doing the same thing as before. I checked my crimps, I even tried a new wire, and another new stepper I had lying around, it's just not functioning. My endstops seem to be wired correctly, as they all work. My wires work, my motors work, my crimps are fixed, my cables are good, so the only thing I feel it's rooted to at this point is maybe somehow my x endstop is triggering, or it's a bad stepper driver. Any other ideas for troubleshooting my x axis? I feel like I've tried it all at this point.

                            Thank you both for taking your time with this 🙂

                            1 Reply Last reply Reply Quote 0
                            • Tininoundefined
                              Tinino
                              last edited by

                              I did another test. When swapping a motor that was just previously working (y axis) over to my x axis, the y stepper motor produced the same issue, while the x axis worked fine. Both stepper motors work, both cables work (didn't change the cables I used just swapped the connections on the board). Y axis now jiggling, x axis works fine. What could be causing this? I really hope it's not a bad driver. I have no clue what the issue is.

                              Edit: changing the ma values in the config didn't work either. Increased it slightly but at that point the motor didn't even move. Put it back down to 800ma, it's just back to jiggling again.

                              I uploaded a config where I changed the endstops to NC from NO, unplugged all the end stops and turned it on, tried jogging the motor, same results, just jiggling rapidly back and forth.

                              1 Reply Last reply Reply Quote 0
                              • dc42undefined
                                dc42 administrators
                                last edited by

                                If your E1 motor output is free, try putting this command in config.g:

                                M584 X4 Y1 Z2 E3

                                Make sure it is earlier in the file than the M906 command. Then connect your X motor to the E1 motor output.

                                If that gets your X axis working, then I'm sorry you do have a bad X driver, and you should ask for your Duet to be replaced or repaired under warranty.

                                Are you using 12V or 24V power?

                                Duet WiFi hardware designer and firmware engineer
                                Please do not ask me for Duet support via PM or email, use the forum
                                http://www.escher3d.com, https://miscsolutions.wordpress.com

                                1 Reply Last reply Reply Quote 0
                                • Tininoundefined
                                  Tinino
                                  last edited by

                                  @dc42:

                                  If your E1 motor output is free, try putting this command in config.g:

                                  M584 X4 Y1 Z2 E3

                                  Make sure it is earlier in the file than the M906 command. Then connect your X motor to the E1 motor output.

                                  If that gets your X axis working, then I'm sorry you do have a bad X driver, and you should ask for your Duet to be replaced or repaired under warranty.

                                  Are you using 12V or 24V power?

                                  12v. I've gotta get to bed so I'll give this a shot tomorrow. Thanks for the help.

                                  1 Reply Last reply Reply Quote 0
                                  • Tininoundefined
                                    Tinino
                                    last edited by

                                    Just a friendly update. Replacement board got here, Runs great now 🙂 absolutely in love.

                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post
                                    Unless otherwise noted, all forum content is licensed under CC-BY-SA