Is my brand new Duet Wifi dead??
-
I think my Duet Wifi is dead … unless someone can help.
Right now I can't get it to connect using a USB (computers don't even see a USB connection)
Only LEDs showing on are the LED VIN, LED+5V and the USB LED, Motor LEDs are not on anymore.Path to frustration:
Hooked up all leads to appropriate connections
Powered up duet Wifi
LEDs VIN, LED+5V,USB LED, and all Motor LEDs on
Connected by Wifi to board
All good so far...Edited config.g to use my new config for Cartisan/core X/Y
Forgot I left out the enable wifi, so opened Pronterface and connected.
Enabled Wifi using M552 S1
Connected to the browser interface on computer - but when it tried to connect to the board it was asking for a password. I never needed one before, so I looked at my config.g and saw the M551 Password ; Machine password (used for FTP connections).
Tried using 'Password' to connect, but got an Invalid Password error. Tried a bunch of others, nothing worked.Pressed the reset button hoping it would go back to factory default (I guess reset just restarts the board)
Used pronterface again to enable WiFi - still could not connect because of Invalid Password.
Decided to use progerface to test some axis controls ... did some x, y, z movements .. then got an error:
[ERROR] Can't write to printer (disconnected?) (SerialException):Now .. no USB connection at all … with power on with USB, or power off with USB, computers don't see the board at all.
I have an LED strip plugged into one of the Always On fan connections - and that comes on when I power up the board, but no USB/WiFi connection.
-
Check that your endstops are wired correctly. You may have GND shorted to +3.3V or the SIG shorted to +3.3V. If you're using switches you should have them connected to GND and SIG.
-
Thanks - I'll take a look at that … I have micro switchs - each as 3 wires and I thought I had them right .. will check again.
just on a fluke, with all wires disconnected I tried connecting with USB again.
So - there is something - either on the board, or in my wiring that is messing up the USB, board powering up.
-
Thanks - I'll take a look at that … I have micro switchs - each as 3 wires and I thought I had them right .. will check again.
That may be your problem. Do you mean to say you have all three pins from the endstop sockets on the Duet wired to all three connections on your microswitches? If so, depending on how you wired them you may have shorted the 3.3v rail directly to ground.
If you're using PCB mounted microswitches that have a status LED, etc than three wires would be ok (again assuming they are wired correctly), but if not you would typically only need to wire the signal and groind pins on the Duet to the outer two microswitch legs to use the default microswitch configuration.
-
If you have simple microswitches (not a fancy board thing) you should only have 2 wires connected to NC and C on the switches and GND and SIG on the duet.
-
the micro-switches I have - have 3 wires. A green, black, and red.
I assume they should be connected on the board to (as shown on the duet Wifi connectoins - Prototype V2 diagam:
green to zstop
red to +3.3v
blk to gndI'm not seeing any other labels on the switches
-
What microswitches do you have? could you take a picture/send a product page or data sheet?
-
Here is the micro-switch image:
https://goo.gl/photos/tb5cRqWAH62FmTrP8
https://goo.gl/photos/eyR3jX333xq7QnBG7I don't see a way to attach it here in the forum.
-
Best off to avoid confusion by calling that an endstop board, whilst it has a microswitch on it, some people use just a plain switch and don't bother with the pcb and LED's etc..
Anyway the middle two pins on that board are GND, the top pin as it is in your photo is signal and the bottom pin is vcc.
The standard endstop cables have +, -, sig but duetwifi needs -, +, sig so swap pins in the endstop cable and try again.
-
I recognise that microswitch board. There is a thread in the forums at reprap.org on how to connect it to a Duet, but I couldn't find it just now.
-
It might be worth checking the endstop board with your multimeter to determine which pin is definitely signal and vcc, I had a bunch of these Chinese ones recently that killed an arduino on my other printer, the micro switch was the other way around to most of the other designs, and I didn't pick up on it until after connecting it.
-
It might be worth checking the endstop board with your multimeter to determine which pin is definitely signal and vcc, I had a bunch of these Chinese ones recently that killed an arduino on my other printer, the micro switch was the other way around to most of the other designs, and I didn't pick up on it until after connecting it.
I second that suggestion. Any pin that has a low resistance to the ground pins when the microswitch is in one of its two positions is not the Vcc pin.
Returning to the original question, if the 3.3V LED does not illuminate when you power the board without the end stops connected, then either the 3.3V LED isn't working or the 3.3V regulator isn't working. Even if you did short +3.3V to ground by mis-wiring the end stop switches, I know that this has happened before without the regulator failing, so it surprises me that yours appears to have failed. I'm happy for you to be sent a replacement Duet WiFi under warranty - but please don't wire up your end stop switches to it without being sure of the right connections.
-
Thank you all for your quick input. It's so great to have such a helpful community.
I will check out all these suggestions. -
-
Cool, what's the website linked on the silkscreen, does that have a schematic/connection diagram or similar?
-
I had a look at the website last night and they don't have it on there anymore so no info to be had unfortunately.
Doug
-
Herr you go https://www.dropbox.com/s/7jttly92qz82duk/Photo%2021-09-2016%2C%2016%2039%2031.jpg?dl=0
Thank You!!!
-
So I have redone everything and the board comes back on, I can get access, and it seems that all the motors and sensors are working.
I may still have some issues in my config file for my CoreX/Y machine that sending gcode for moving both x & y axis seems to only move the y axis.
However - there are no LEDs on by the motor connections now. Are they 'supposed' to be on when the board powers up?
-
It depends on your configuration but those LEDs are indicators for the end-stops.
In my case, I used normally closed end-stops so because the micro-switches are closing the circuit between Signal and Ground the LEDs remain on until the end-stops are triggered, at which point the LEDs will go out because the switches open.
W3DRK
-
thanks for pointing that out … I tested, and I see now that when I trigger the x or y endstop the led does come on. They were probably on before because the enstops were shorted.
I have an IR mini Z-probe ... can I also use the z-endstop as a 'fail-safe', I don't see the z-motor led come on when the IR z-probe is triggerd.
Sorry for all the newbie questions .. moving from arduino/marlin to Duet has been more of a learning curve than I anticipated - but I'm sure with everyone's patience I'll make it...
