directions wrong and no zero...
-
-
@fcwilt yes, board plugged into 24v feed as usual to run printer for testing.
-
@fcwilt laptop on mains and battery works fine.
-
@fusedeep said in directions wrong and no zero...:
@fcwilt yes, board plugged into 24v feed as usual to run printer for testing.
I cannot be sure since I don't know the details of your 24 volt power supply and your laptop but it is possible, under certain circumstances, when the Duet is getting power from both sources (the 24 power supply and the USB cable) that damage to the Duet can occur.
I'm not saying this is what has happened but it might have happened.
If your Duet is damaged and you proceed with getting it repaired or replaced you might want to consider using my approach to getting a Duet up and running. I don't use the USB connection, rather I pull the SD card and connect it to my computer via a SD card reader/writer device. Then I create a minimal config.g file on the SD card with just the commands need to get the WiFi up and running. When the config.g file is ready I return the SD card to the Duet and apply power. Once WiFi is up then I can do the rest of the configuration via the DWC editor.
Frederick
-
There is the possibility that it has been damaged by a ground loop through the USB connection.
Can you show a photo of the board when connected to just USB so that we can see the lights?
Same for when just connected to VIN.
Close up photos of the board may show if a component has failed as well, such as a regulator.
You can also check with your finger to see if any component gets very hot.For more detailed steps on how to check what is working or not please go through this guide and let us now what you find.
https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond -
Jesus. I won't be too impressed if this is the case. It's a 150 quid unit!
How is that even possible?
For some reason this set up has been a proper nightmare. Fusedeep was much simpler and that was my first go!
Will look at it and send images.
Rich
-
@fusedeep said in directions wrong and no zero...:
How is that even possible?
https://docs.duet3d.com/en/User_manual/Overview/USB_ground_loops
-
Well, all power supplied from the same socket block.
Unfortunately I needed to keep the usb plugged in because the wifi kept disappearing.
All cables well rated ref v-/ground.
It's been a really bad experience with duet, after the initial success with fusedeep.
It has also chewed up hours of my time.
Am extremely frustrated and disappointed in all honesty.
-
I understand your frustration and I'm sorry your experience hasn't been smooth.
USB ground loop is a possibility, but I'm not certain.
At any rate, the best we can do now is follow the guide here and see what the status of the board actually is. Either we can recover, or the board has failed and would need to be replaced under warranty.
https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond
-
-
As per instructions on that page;
disconnected power and usb.
removed all end stop connectors.
plugged in usb.
All lights came on fine and duet wifi appeared on laptop.
Also got usb bell noise.
However; laptop unable to open any com terminal with yat/putty (yat would not reinstall after i removed it to reinstall it in case yat was borked).
However, after unplugging usb, I reconnected the end stops and reconnected usb cable. back to 2 red led and no wifi .
Seems kaput to me. I think it has also fried my laptop com ports too.
I do remember being recommended a 75 gbp duet board for the makergear m2 rebrain a while back, but iirc it has no wifi option?
Is there a cheaper option than the duet 2 for me?
Good lord.
Rich
-
Did you verify the wiring of the endstops and that they were not shorting out the 3.3 volt power?
When you made the USB connection you heard the typical USB connection sound which suggests your USB port is still working.
Just FYI, COM ports over a USB connection are virtual - there is nothing to fry - other than the USB port itself.
The least expensive Duet I know of is the Maestro but I don't know if they are making that anymore.
The next would be the Duet 3 Mini 5+ which is a very nice board.
Frederick
-
@fusedeep sounds like the endstops may be wired incorrectly and if you connect them they are shorting the board. If you come from a RAMPS style board, please note this section: https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_endstops and this one from the old wiki which I can't find in the new docs yet: https://duet3d.dozuki.com/Wiki/Wiring_and_hardware_differences_from_RAMPS_etc#Section_Endstop_switch_connectors
-
@fcwilt the Duet Maestro is not in production anymore. The Duet 3 mini supercedes it and is only marginally more expensive.
-
Endstops have been working fine for 6 years and nothing changed.
They were working fine after I amended the duet config to correct my error.
They are simple microswitches.
Am honestly not sure how they could go wrong?
But obviously there is some issue somewhere.
I think the board is borked.
-
Ah!
Thank you so much!
I followed that and all 3 end stops happy now and board working on wifi!
Plus the z end stop had an led attached and this was obviously upsetting the system! Disconnected it.
Only thing is, z zero not bouncing back to do a slow zero return but will check the config.
Need to sort my wacky fans now!
-
Thanks
Led removed from z endstop and all rehashed. Board back to life!
Weird
Only thing is z home works but does not do slow 5mm return as per other axis.
Fans put to 0 for work piece and 1 for extruder seem to be happy.
Assigning extruder trickier. It is heating up fine by web control but not un greying on web control extrude buttons, even past 180 degrees...
Nearly there!
Sorry if I was painful. It's been a really crappy week and I thought this would be the simple bit...
-
To enable extrusion you have to have a tool selected.
Having a T0 command at the end of config.g will usually do it.
Or you can select a tool from the DWC.
Frederick
-
Last thing (except for no z home bounce check)
I just put T0 at the end, below wifi line and it now let's me extrude!
Is that correct?
-
@fusedeep said in directions wrong and no zero...:
Last thing (except for no z home bounce check)
I just put T0 at the end, below wifi line and it now let's me extrude!
Is that correct?
Well in most cases there is no one correct way to organize your code.
There are some commands which must proceed other commands but that is covered in the on-line docs.
Just FYI here is what my config.g file looks like for one of my printers. You can see that I put the communication stuff in the section labeled prologue.You will not find a T0 command because I handle that in my print start code. If I were to add it it would be in the section labeled tools.
; ---------------------------------------------------------------------------------------------------- ; start of file - printer MF1 - hardware Duet 2 WiFi/Duex 5 - firmware 3.3.0 ; ---------------------------------------------------------------------------------------------------- ; **************************************************************************************************** ; prologue ; **************************************************************************************************** M111 S0 ; debug off M550 P"MF1" ; machine name ;M551 P"?????" ; machine password M555 P2 ; set output to look like Marlin M575 P0 B57600 S2 ; communication parameters for USB serial M575 P1 B115200 S1 ; communication parameters for PanelDue M552 S1 ; enable (S1) networking (WiFi) M586 S1 P1 T0 ; enable (S1) FTP (P1) Disable TLS (T0) M586 S1 P2 R2323 T0 ; enable (S1) Telnet (P2) Disable TLS (T0) G21 ; dimensions in mm G90 ; for X,Y,Z use absolute coordinate values M83 ; for E0,E1,etc use relative coordinate values ; **************************************************************************************************** ; mode control variables ; **************************************************************************************************** global g_z_home = 5 ; can be used to always move Z to known height global g_z_datum_set = false ; can be used to prevent unneeded setting of Z=0 datum global g_map_mode = "300 point" ; determines which kind of height map is created/loaded global g_probe_mode = "two consecutive" ; determines if z proving used consecutive or averaging global g_level_mode = "3 point" ; determines if 3 or 4 points are used for leveling global g_print_beg_prime = 10 ; default - set desired in filament config.g global g_print_beg_retract = 0 ; default - set desired in filament config.g global g_print_end_retract = 0 ; default - set desired in filament config.g global g_print_end_mode = "heat off" ; determines if heaters are turned off when print is done global g_probe_z_trigger = 1.8 ; default - set as appropriate for the Z probe ; **************************************************************************************************** ; kinematics - K11 = MarkForged (x is -left/+right, y is -front/+back, z is bed -up/+down) ; **************************************************************************************************** M669 K11 X1:0:0 Y-1:-1:0 Z0:0:1 ; defaults X1:0:0 Y-1:1:0 Z0:0:1 ; **************************************************************************************************** ; motors ; **************************************************************************************************** ; motor direction - drive (P), direction (S1 = normal, S0 = reverse) M569 P0 S1 ; drive 0 - normal - X M569 P1 S1 ; drive 1 - normal - Y (R) M569 P2 S0 ; drive 2 - reverse - Y (L) M569 P3 S1 ; drive 3 - normal - E0 - for Nimble M569 P4 S1 ; drive 4 - normal - spare M569 P5 S0 ; drive 5 - reverse - Z (L) M569 P6 S0 ; drive 6 - reverse - Z (C) M569 P7 S1 ; drive 7 - normal - Z (R) M569 P8 S1 ; drive 8 - normal - spare M569 P9 S1 ; drive 9 - normal - spare ;M569 P10 S1 ; drive 10 - normal - spare external ;M569 P11 S1 ; drive 11 - normal - spare external ; motor assignment M584 X0 Y1:2 Z5:6:7 E3 ; set what motors do what ; other motor settings ; for X, Y, Z M92 X80 Y80 Z400 ; steps per mm (Z1600 for 2mm lead - Z400 for 8mm lead - Z400 for belt drive using stepper with gearbox of 5-to-1) M203 X12000 Y12000 Z1200 ; max speed (mm/min) (Z1200 for 2mm lead - Z300 for 8mm lead - Z1200 for belt drive) M566 X400 Y400 Z120 ; max instant speed change (jerk) (mm/min) (defaults 900 900 12) (Z values from phasdrux) M201 X500 Y500 Z240 ; acceleration (mm/s^2) (defaults 500 500 20) (Z values from phasdrux) M906 X1000 Y1000 Z1000 I30 ; motor current (mA) and idle current (30%) (Zmax 1400) ; external driver settings - tested but not in use ;M569 P5 S1 T2:2:10:10 ; drive 5 - normal - X external (T values as suggested by dc42) ;M569 P6 S1 T2:2:10:10 ; drive 6 - normal - Y external - reversed in controller (T values as suggested by dc42) ;M92 X204.75 Y204.75 Z1600 ; steps per mm (Z1600 for 2mm lead - Z400 for 8mm lead - Z400 for belt drive using stepper with gearbox of 5-to-1) ;M906 Z800 I30 ; motor current (mA) and idle current (30%) (for external drivers) ;M350 Z16 E16 I1 ; 16x microstepping with interpolation - not used for external drives ; Nimble extruder M92 E2750 ; steps per mm (suggested 2750) M203 E3600 ; max speed (mm/min) (suggested 3600) M566 E60 ; max instant speed change (jerk) (mm/min) (suggested 40) M201 E120 ; acceleration (mm/s^2) (suggested 120) M906 E500 ; motor current (mA) (suggested 500) ; BMG extruder ;M92 E830 ; steps per mm (suggested 415 for 1.8 stepper) ;M203 E10000 ; max speed (mm/min) (suggested ?) ;M566 E1000 ; max instant speed change (jerk) (mm/min) (suggested ?) ;M201 E3000 ; acceleration (mm/s^2) (suggested ?) ;M906 E1000 ; motor current (mA) (suggested ?) ; if M92 above is set for the default 16x microstepping then putting M350 here ; will result in the needed adjustments to the initial values set by M92 M350 X16 Y16 Z16 E16 I1 ; x16 microstepping with interpolation (I1) ; ============================================================ ; axis dimensions and coordinate value modes for 0,0 in center ; ============================================================ M208 X-150:150 Y-100:100 Z0:350 ; set axes min/max values for 0,0 in bed center M579 X1.0 Y1.0 Z1.0 ; scaling (values are determined by measuring test object) M564 H1 S1 ; H1 = dont allow moving non-homed axes, S1 = limit movement to axes min/max values ; **************************************************************************************************** ; end stops ; -- X,Y,Z,etc = location of endstop (0 = none, 1 = low end, 2 = high end) ; -- S = type (1 = switch, 2 = probe, 3 = motor stall (one), 4 = motor stall (multiple) ; -- ! = invert ^ = enable pull-up ; **************************************************************************************************** M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y M574 Z1 S1 P"!duex.e2stop + !duex.e3stop + !duex.e4stop" ; configure active-high endstop for low end on Z ; **************************************************************************************************** ; heaters ; **************************************************************************************************** M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 Q10 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 S1.00 A187.6 C189.8 D4.2 V12.0 ; values A, C, D, V determined by running heater tuning M140 H0 ; map heated bed to heater 0 M143 H0 S115 ; set temperature limit for heater 0 M308 S1 P"e0temp" Y"thermistor" T100000 B4267 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 Q250 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 A403.7 C171.6 D3.4 V11.9 ; values A, C, D, V determined by running heater tuning M143 H1 S250 ; set temperature limit for heater 1 ;T500000 B4723 C1.196220e-7 ; for Slice 500K thermistor ; other heater settings M570 P300 ; heater fault timeout - increase to allow extra heating time ; **************************************************************************************************** ; cooling fans ; -- P = fan #, S = speed (0 to 255 or 0.0 to 1.0) ; -- H# = thermostatic control (turn on fan F# when heater H# reaches temp T#) ; -- H-1 = no thermostatic control ; **************************************************************************************************** M950 F0 C"fan0" Q500 ; create fan (F), pin name (C), frequency (Q) M106 P0 C"Part" S0 H-1 ; set fan (P), name (C), speed (S), thermostatic control off (H) M950 F1 C"fan1" Q500 ; create fan (F), pin name (C), frequency (Q) M106 P1 C"Hotend" S1 H1 T45 ; set fan (P), name (C), speed (S), thermostatic control on (H & T) ; **************************************************************************************************** ; LED light strips ; -- P = fan #, S = speed (0 to 255 or 0.0 to 1.0) ; -- H# = thermostatic control (turn on fan F# when heater H# reaches temp T#) ; -- H-1 = no thermostatic control ; **************************************************************************************************** M950 F2 C"duex.fan3" Q500 ; create fan 2 (F), pin name (C), frequency (Q) M106 P2 C"Lights L" H-1 ; set fan 2 (P), name (C), thermostatic control off (H) M950 F3 C"duex.fan4" Q500 ; create fan 3 (F), pin name (C), frequency (Q) M106 P3 C"Lights R" H-1 ; set fan 3 (P), name (C), thermostatic control off (H) ; **************************************************************************************************** ; tools ; --- M563 --- ; P is tool number ; S is tool name (optional) ; D is extruder drive (0 or 1) ; H is associated heater number ; F is associated fan number ; --- G10 --- ; P is tool number ; X, Y, Z are axis offsets ; R, S are initial standby & active temperatures ; **************************************************************************************************** ; tool 0 M563 P0 S"T0" D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set axis offsets G10 P0 R0 S0 ; set active and standby temperatures ; **************************************************************************************************** ; external buttons (P = pin #, T = trigger #, R = when to trigger (0 = always, 1 = printing), S = what edge (I->A = 1, A->I = 0, -1 = ignored) ; --- T0 does emergency stop ; --- T1 does pause (see M25) ; --- T# runs macro trigger#.g ; **************************************************************************************************** M950 J2 C"!^duex.e6stop" M581 P2 T0 R0 S0 ; big button does emergency stop M950 J1 C"^e0stop" M581 P1 T2 R0 S0 ; little button runs trigger2 which does M999 (board reset) ; **************************************************************************************************** ; filament sensor ; Pnn = sensor type ; - 0 = none ; - 1 = simple sensor (high signal when filament present) ; - 2 = simple sensor (low signal when filament present) ; - 3 = Duet3D rotating magnet sensor ; - 4 = Duet3D rotating magnet sensor with microswitch ; - 5 = Duet3D laser sensor ; - 6 = Duet3D laser sensor with microswitch ; - 7 = pulse-generating sensor ; C"xx" = input pin name ; Dnn = extruder drive (0,1,2,...) ; Snn = enable/disable monitoring (0 = disable, 1 = enable) ; --- for types 3 to 7 --- ; Ann = when to check (0 = printing motion only, 1 = all motion) ; Enn = min extrusion to trigger check (mm, default 3) ; Lnn = movement per sensor wheel rotation (in mm, default 28.4) ; Raa:bb = extrusion error range (percent) ; **************************************************************************************************** M591 D0 P2 C"e1stop" S1 ; TriangleLabs ;M591 D0 P3 C"e1stop" S0 A0 E3.0 L25.72 R40:115 ; E3D magnetic ; **************************************************************************************************** ; epilogue ; **************************************************************************************************** ; ---------------------------------------------------------------------------------------------------- ; workplace coordinates ; Ln Mode (L1 L2 or L20 - see below) ; Pnnn tool number if L=1 or coordinate system number if L=2 or L=20 ; X,Y,Z,U,V... Offsets ; ; L= 1: this sets the tool offset, as if the L parameter was not present ; L= 2: this sets the origin of the coordinate system number specified by the P parameter (1 to 9) to the specified X, Y, X... values ; L=20: this is similar to L=2 except that the origin is specified relative to the current position of the tool ; ---------------------------------------------------------------------------------------------------- G10 L2 P1 X0.00 Y0.00 Z0.00 G10 L2 P2 X0.00 Y0.00 Z0.00 G10 L2 P3 X0.00 Y0.00 Z0.00 G10 L2 P4 X0.00 Y0.00 Z0.00 G10 L2 P5 X0.00 Y0.00 Z0.00 G10 L2 P6 X0.00 Y0.00 Z0.00 G10 L2 P7 X0.00 Y0.00 Z0.00 G10 L2 P8 X0.00 Y0.00 Z0.00 G10 L2 P9 X0.00 Y0.00 Z0.00 ; ---------------------------------------------------------------------------------------------------- ; Z probe configuration ; ---------------------------------------------------------------------------------------------------- M98 P"probe_config.g" ; ---------------------------------------------------------------------------------------------------- ; end of file ; ----------------------------------------------------------------------------------------------------