Posts made by pugzor

@kezat I went for gold and just switched around Pins 3 and 4 on the stepper side of things - it stopped the error and is extruding properly now. So ends up this error can come up if you've just wired a stepper incorrectly. All fixed!

@kezat said in Short-to-ground on driver 3:

Just to be clear, you still get the short to ground error message on driver 3 when you try and command a move of driver 3 without anything connected to that board connector correct? I'm trying to determine if the board has a fault or the issue is the extruder motor/wiring (driver3?) that is at fault.

Sorry, hadn't tried this. When I remove the connector completely from the board and send a command to the E0 stepper (at temperature), nothing happens and no error comes up. That would indicate a wiring error between plug and E0 stepper, wouldn't it?

@kezat said in Short-to-ground on driver 3:

Does unplugging the motor (power off board first) connector from the board clear the error? And make sure you don't have a bit of metal shorting out the underside of the board. If you cant clear the error by removing the connector a good visual inspection might be a good idea.

Hey @Kezat, I've tried that a few times without success. Have had a good visual inspection too and can't seem anything unusual on the board. My board is elevated above the mounting surface by a good 8-10mm too and I've run some air over it to try and clear it. Compared resistance between pins on the Duet side and they all seem to be around 11.4m Ohms between each other (another set of pins was around 10.9m Ohms so I'm guessing that's kind of normal).

At a bit of a loss!

Hi there,

I got my Duet Wifi late last year for my Hypercube Evolution and had a lot of success with it (seriously - very happy with the purchase). Anyway, I wanted to upgrade my hotend to a Titan Aero and unfortunately got caught in the bearinggate issue. Took a break while that was being sorted out, got an Ender-2, and have been mucking around with that until recently.

Recently I've come back to the Hypercube and tried to get it running again. Changed a few things (belt driven dual axis to standard dual Z motors) but also made my own bracket for the Aero since I couldn't find one anywhere that would accommodate for the 40mm stepper E3D recommended.

The problem now though is that everything seems to be working bar the extruder motor. It's a genuine E3D MT-1703HSM168RE. When I heat up the hotend to the required temperature and try to extrude 5mm at 1mm/s, I get the error that there's a short-to-ground on driver 3.

My main question is - does this error usually indicate there's an issue with the driver, assuming there's not a genuine short somewhere? Or can just wiring up the stepper indicate an issue?

The way I've currently got this motor wired is (pins are left to right on both the Duet and stepper):

• Pin 1 on the stepper to Pin 1 (2B) on the Duet
• Pin 2 on the stepper unused
• Pin 3 on the stepper to Pin 2 (2A) on the Duet
• Pin 4 on the stepper to Pin 4 (1B) on the Duet
• Pin 5 on the stepper unused
• Pin 6 on the stepper to Pin 3 (1A) on the Duet

Anyone able to give me a tip on this?

Thanks in advance.

David, you are a legend. I'd configured the homeall.g file but not the individual axis files.

I owe you a beer one day.

sigh I can't believe it, but it seems a grub screw had fallen out of one of the motor pulleys. I can't believe I asked a question on a forum before checking that.

Sorry guys. Appreciate the help.

Hi all,

Running a Hypercube Evolution (CoreXY) powered by a Duet WiFi and noticed that I've got some random movements in my X axis. It's not all the time, just maybe 1 in every 10 movements. Easiest way to describe is by YouTube hosted video:

https://goo.gl/dcF7kL
Just moving the X in 10mm increments.

Doesn't happen on the Y, just the X.

I doubt it's something to do with the hardware or firmware. Could one of my motors be dying?

Thanks!

Hey all,

Bit stumped on this one.

Installed my new Duet WiFi and mostly it went without a hitch (except for a Z probe which I ended up replacing with a mechanical endstop). I've got a Hypercube Evolution, a CoreXY design, which was previously running a MKS Sbase.

Anyway, did some basic tuning to make sure my steps were all happy first. When I went to do +10 on the X, it would move away from the front left corner (where it should be 0,0,0). When I hit -10 on the X it goes back. Excellent! When I hit +10 on the Y it goes away from me toward the back of the printer and vice versa. Excellent again! Z works the same way… moves down and away from the print head when I say +10 and up towards the hot end with -10. Firmware (config.g is here https://goo.gl/rbQM5o in txt form) is set to home to min on all axes.

Went to home and the X works fine. Went to home the Y and it starts heading to the max.

I know I could just set the Y to home to max, or reverse it, but that kind of confuses everything else.

Any ideas what the issue is? 99% sure it's a simple issue with my config.

@dc42:

If the black, brown and blue wires from the sensor are ground, positive supply, and output, then the wiring looks correct to me. Is it definitely an NPN output sensor? What voltage can you measure between the blue wire from the sensor and ground when the probe is and is not triggered?

Appreciate your help with this. Ended up just going for a modification to put a mechanical endstop for the Z. Already had one and since I had to open up the back anyway, seemed just as easy (and frankly more reliable - not a fan of the inductive sensor). Sometimes it's easier to reformat a PC than try and remove a virus!

Thanks gents!

Used a BAT43 as per the instructions in the wiki. Image in my original post shows how it was wired - is that correct?

@whosrdaddy:

The dive height is the height it will probe at.
Do you get 1000 readout for the z-probe in the webinterface when you put metal under the sensor?

Unfortunately not. Having said this though, earlier I did notice a number (maybe in the 400s) there when there was no metal under it before I started playing with config.g quite a while ago. What would be the next port of call?

@whosrdaddy:

Had a look at you config, seems fine to me.
The only thing I would change is the line:

M558 P4 X0 Y0 Z1 F600 T6000 I1 H0 ; Set Z probe type to mode 4, Z axis only

to

M558 P4 X0 Y0 Z1 F600 T6000 I1 H5 ; Set Z probe type to mode 4, Z axis only, 5mm dive height

Normally when you put metal under your sensor, the Z-probe value should show 1000 in DWC main screen.

Thanks mate! Out of interest, what does the dive height do exactly?

Didn't fix the issue, unfortunately, but thanks for the tip.

Hi there,

Upgraded my Hypercube Evolution from a MKS SBase to a Duet WiFi last week. So far I'm very, very happy with it, and I can't see myself using another board any time soon for future printers! I've got most things wired and working now. Case fans are working (love the additional outputs on the board, no need for an extra FET), all steppers are tuned, everything (bar one) is working as well as it can be prior to laying down plastic.

Currently using a V6 clone and inductive proximity sensor, but as soon as I get them working with the Duet I'll be printing out mounts for a genuine E3D Titan Aero and BLTouch combo. Just need to print well enough to do that! Unfortunately I was having issues with layer shifts which I ended up putting down to the SBase, so it was an early upgrade to the Duet.

The problem I'm currently facing is that my proximity sensor, a LJ12A3-4-Z/BX, seems to be powered up and detecting metal just fine, but I'm not able to get it to act as an endstop yet. I've followed the steps on the wiki (which is fantastic) but I've not had any joy. Figured I'd post in here to confirm I've done everything from wiring through to config.g modification. M119 doesn't see the endstop as being triggered when I place metal near it (or when there's no metal near it).

Here's a picture of my wiring, just to confirm it's correct. It's plugged into the E0 endstop, next to the the X endstop. If it is correct I'm very happy for it to be used on the wiki as an example. Please forgive my dodgy soldering skills, and of course, I have covered it with insulation tape.

https://goo.gl/uFtvuv (jpg hosted on Google Drive)

Here's a copy of my config.g file too (converted to txt to play nicely with Google Drive) which hopefully will shed some light. Maybe there's a dependency I'm missing?

https://goo.gl/Bi3Gmx (txt hosted on Google Drive)

Any help would be greatly appreciated!

• Andy