Posts made by Tinino

Resolved, when the print finished, retightened my wires in the mosfets, looks like something must've come loose…

I did a little searching on this, but I only found the solution for when someone is using a thermocoupler, which I'm not. I just have my heated bed wired up like normal to the mosfet on the board. What would cause this heater fault on the bed like that? I have a print going right now so it's actually working fine, it's like halfway through, but afterwards I'd like to know what steps to take to try and resolve this. My first thought is to play around with the thermistor and double check the bed wires. But I'd like some feedback on this as well. Thanks.

@dc42:

Why not connect the hot end directly to the Duet? Hot end heaters draw only a few amps, so the external mosfet serves no useful purpose.

To bypass the drain directly from the board and go straight to the PSU, using the H1 as the signal for the mosfet to indicate draw. It's not completely necessary, but it's something I'm used to doing. I've always had a preference for running the heating aspect of a printer directly from the supplies for the sake of complete energy efficiency.

So, I'd like to preface this post with a little background. Historically I'm more familiar with cheaper melzi boards, the Duet is higher end and is one of the nicer boards out there, so I'm not as familiar with it. If the wiring diagram below seems funky, just be aware this is almost exactly how it works with a lower end board. Perhaps there's an issue with the signal wires I'm using, maybe not.

I have a couple of cheap little 360 watt 12v Power Supplies, I'd like to use one to power the hotend and the board, and another to power the bed. Typically how the mosfets work is, when the board sends current to heater 1, the 18 gauge wire triggers the signal on the mosfet, which in turn pulls the voltage from the PSU to power the heating element. This gives a stronger and more stable current, allows for an additional PSU which helps to reduce loads, basically allowing for potentially faster heating, even if it's by fractions. The same thing goes for the bed.

However, here's the problem. When I signal for the hotend to heat, my signal wires don't seem to be triggering for heater 1, but when I wire the hotend directly to the board, it works fine. I'm thinking at this point perhaps it's just a defective mosfet, but I'd like some input on whether or not what I'm doing here is even supported by the board, and possibly if there's just some issues with it signaling. Let me know what you think.

Prepare your eyes for my terrible MSPaint skills

Thanks all

Hey thanks for the quick responses guys :), I do believe it's the gcode file that Cura is generating, I'll have to look into the settings a bit more and find out where it's stopping the heating. This is my first attempt at a multi-filament setup so there's certainly a learning curve here. Thank you both for the great info. And yes, I do have the cyclops style setup.

Just curious, I've noticed when I slice a multi-extruder gcode file, that when my duet runs the print and goes to switch tools, it stops heating. If I set my standby temp to 235 (Both filament lines/extruders share a single nozzle) will that resolve the issue of losing the heat when it switches tools? I'm testing that out now, but I'm also curious to see how any of you may have your setups done, just to compare it to what I have.

Currently I just have my 2 tools, both are assigned to heater 1, and then tool 1 is assigned extruder 0, tool 2 extruder 1. I've just now set my standby temps to 235 and my extrusion temps to 235. Looking forward to your replies. Thank you

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

@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.

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.

@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

@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.

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

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

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!

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

@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

@dc42:

I suggest you create new config and homing files using https://configurator.reprapfirmware.org/. Then you can upload the resulting zip file though the Settings/General page of the web interface.

I'll do that. Is my wiring on the steppers correct as far as you can tell?

https://ibb.co/gXhSOw
https://ibb.co/nvwyVb
https://ibb.co/fY4wGG

Please pardon my insanely messy wiring. I'm still getting the wiring and my build sorted, so right now I'm just trying to grasp everything that's going on, and then cleanup later.

Thanks for your quick reply and the help!

Edit: also I just noticed your mention of the delta printer. YES you are correct, when I move any axis in the web interface it mentions a delta printer, I was wondering why that is the case. Should I modify the config directly on the SD card or is there a faster way to go about doing this? (Also please still reference my other questions as I'd like to ensure my wiring is proper)

Endless thanks

@dc42:

The reason that the jog controls don't work may be because the config.g file has configured the firmware for a delta printer, in which case movement is not permitted until the towers have all been homed.

Please explain (preferably with a diagram) how you have wired your PSUs, hot end heater and bed heater to the Duet.

So, before reading your reply I removed the mosfet hearing from the equation, I have the PSU voltage running through a mosfet and into the duet. I DID previously have signal wires wired from the mosfet signal into the hotend heater. After removing that, the hotend still does not heat but the thermistor is working properly. I did the same with the mosfet I had hooked up for the bed, instead running the voltage to the board. The bed was only able to get up to 25c and it stopped from there.

I noticed my stepper wiring may be off so i looked over the nema17 steppers wiring diagram and wired the corresponding pins to the ones to match the board. My steppers are now able to jog, HOWEVER, any movement on the x or y axis jogs the other respectively, they also take one step forward and then the same step back, so they wiggle back and forth. I assume at this point my pins are not wired correctly and the diagram I am referencing may be outdated or it's just my ignorance.

Here's the diagram I am referencing for my wiring for the record:

https://duet3d.com/wiki/Duet_WiFi_and_Ethernet_wiring_diagrams

And also what I referenced for my stepper pinouts:

https://www.google.com/search?q=nema+17+stepper+motor+pins&client=ms-android-verizon&prmd=sivn&source=lnms&tbm=isch&sa=X&ved=0ahUKEwiwptOWxMzWAhWnqVQKHSs8DSMQ_AUIEigC&biw=412&bih=604#imgrc=rROHMtCUCzDwhM:

The stepper wiring is as follows

Stepper motors:

Blue = 2B
Green = 2A
Red = B1
Black = A1

The wiring as it appears on the board:

Blue ]
[ Green ]
[ Black ]
Red ]

And I'll post pictures momentarily for your reference as well.
Also I was able to get the web interface functioning, so things are looking up, but I am concerned with the lack of voltage my hotend and bed are getting and the heating errors, and of course my potentially (most likely) faulty wiring on the steppers.

Cheers.

To preface, or for context. I've only been 3d printing about 6 months. I've messed with firmware a bit, and I know a bit about hardware/wiring but generally not enough to understand pinouts. Most of my knowledge comes from wiring diagrams, which are what I referenced when wiring up my duet, and then I added a couple mosfets/signal wires and I'm running 2 12v PSU's, one going to the hotend and the other going to the bed.

Anyway, nothing is working. When I plug the printer in via USB, it connects via COM5, but I can't jog controls, and I can't heat my hotend or bed. I pulled out the SD and plugged it into my computer just to double check and make sure that I didn't need to install firmware, there's files in there it looks like, so I don't think that's it but correct me if I'm wrong.

Could anyone help me figure out the root of this issue? I know next to nothing about this board or the firmware, all I've basically done is wired it up, and I'm using matter control as my slicer. Anyway, any help is appreciated and if pictures are needed or any more info, let me know. Just to reiterate, the printer is connecting, the thermistors on the bed and hotend are reading ambient temps, but I can't do anything via USB. I don't have a display for it yet so this is how I've opted to print until I can get a display or figure out how to set up the wifi.

Thank you!