Posts made by ozpete81

Looks great I might get one for Christmas

M81 sent then M122 shows

10:44:10 AMM122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS0-7J1DJ-3SJ6J-18BVR
Used output buffers: 3 of 24 (15 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93604 of which 0 recycled
Exception stack ram used: 200
Never used ram: 11556
Tasks: NETWORK(ready,764) HEAT(blocked,1208) MAIN(running,3824) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:02:02 ago, cause: software
Last software reset at 2020-07-02 10:42, reason: User, spinning module GCodes, available RAM 11556 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 27.1, current 27.5, max 27.7
Supply voltage: min 0.4, current 0.5, max 0.5, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 2020-07-02 10:44:09
Cache data hit count 460671883
Slowest loop: 5.02ms; fastest: 0.05ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 5 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 201.12ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 1
  WiFi firmware version 1.23
  WiFi MAC address bc:dd:c2:31:9d:90
  WiFi Vcc 3.40, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 24360
  WiFi IP address 192.168.1.10
  WiFi signal strength -45dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0

On power on, can confirm DWC thinks M80 activated as per config.g above

10:42:22 AMM122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS0-7J1DJ-3SJ6J-18BVR
Used output buffers: 3 of 24 (14 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93604 of which 0 recycled
Exception stack ram used: 164
Never used ram: 11592
Tasks: NETWORK(ready,764) HEAT(blocked,1256) MAIN(running,3824) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:00:15 ago, cause: software
Last software reset at 2020-07-02 10:42, reason: User, spinning module GCodes, available RAM 11556 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 26.8, current 27.4, max 27.5
Supply voltage: min 0.4, current 0.5, max 0.5, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 2020-07-02 10:42:22
Cache data hit count 40610092
Slowest loop: 1.42ms; fastest: 0.05ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 5 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.49ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.23
  WiFi MAC address bc:dd:c2:31:9d:90
  WiFi Vcc 3.40, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 24864
  WiFi IP address 192.168.1.10
  WiFi signal strength -45dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0

; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.1 on Thu May 28 2020 21:33:56 GMT+0800 (Australian Western Standard Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Flashforge Creator Pro" ; set printer name
M80 ; turn on 24V PSU

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes forwards
M569 P4 S1 ; physical drive 4 goes backwards
M584 X0 Y1 Z2 E3:4 ; set drive mapping
M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation
M92 X94.12 Y94.12 Z400.00 E144.5:144.5 ; set steps per mm
M566 X480.00 Y480.00 Z12.00 E1200.00:1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z1200.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00:250.00 ; set accelerations (mm/s^2)
M906 X810 Y810 Z300 E810:810 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-111 Y-75 Z0 S1 ; set axis minima
M208 X150 Y75 Z150 S0 ; set axis maxima

; Endstops
M574 X2 Y2 Z1 S0 ; set active low endstops

; Z-Probe
M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
M557 X-96:135 Y-60:60 S20 ; define mesh grid

; Heaters
M307 H0 B1 S0.80 ; bang-bang mode for the bed heater and set PWM limit 80%
M305 P0 T100000 B4066 R4700 ; set thermistor + ADC parameters for heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M305 P1 X150 ; set Thermocouple 1 (defult type K) for heater 1
M143 H1 S310 ; set temperature limit for heater 1 to 310C
M305 P2 X151 ; set Thermocouple 2 (defult type K) for heater 2
M143 H2 S310 ; set temperature limit for heater 2 to 310C

; Fans
M106 P0 S0 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 H2 T45 ; set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Tools
M563 P0 S"Left Extruder" D0 H1 F0 ; 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 S"Right Extruder" D1 H2 F0 ; define tool 1
G10 P1 X-38.500 Y0 Z0 ; set tool 1 axis offsets
G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C

; Custom settings
M671 X-52:0:48 Y62:-68:62 P0.5 ; level screw locations and screw pitch type

; Miscellaneous
M501 ; load saved parameters from non-volatile memory
M98 P"/sys/config.g" ; temp for diag purpose - no error reported 2/7/20

@droftarts said in PS_ON function using SSR and 5V and 24V PS:

Or wire a 5V fan or bulb in between 5V and PS_ON pin, and see if works when you send M80.

So I checked my SSR and a second SSR I know works, both light the LED at 3V, dimmly and 4.5V brightly, I hooked up a small motor I have and it didnt turn. im getting 0V voltage potential between the +ve terminal and -ve terminal, (I put the probe on the PS_ON pin on -ve terminal on SSR, I probed between the PS_ON wire and -ve terminal on my 5V PS and got +5V; both with M80 and M81 toggled, no change in condition, next I checked the Voltage potential across the +5V and PS_ON with a 10k resistor on PS_ON (as suggested elsewhere on forum, and I got about 1.1 to 1.4V both with M80 and M81, no change in condition?

I had returned the wiring back to above diagram when I checked these things.

I looked at the Mosfet TR7 it looks in good condition. As I mentioned earlier the Board is brand new, still stuck. (not sure I want to try to probe the TR7 Mosfet its very crowed there and I dont want to wreck my new board.) Same condition as where I started. On this installation there has not been any shorts funny noises or smells or smoke, is there a setting/persistant code that could be halting this.

Any ideas, I will post my config.g and M122 M80 and M81 state in next posts below.

I dont believe this is difficult I thought it was just M80 / M81 command, I can confirm the web interface confirms action.

I wonder if @dc42 has any input thanks david.

@droftarts said in PS_ON function using SSR and 5V and 24V PS:

What SSR is it?

says 50A Fotek but prob Chinese knock off,
I will take out and test the SSR triggers at 5V it states 3-36V input, might try another SSR I know works.

@droftarts said in PS_ON function using SSR and 5V and 24V PS:

You will read 5V on the PS_ON pin, because the MOSFET switches

I thought you might say that, some of the other posts I have seen implied that may be the case, (I dont have complete understanding of electronics, but I thought maybe something funny) , the Duet board is basically brand new so I dont think I would have blow the mosfet up yet. fingers crossed

@FelixH code should be as simple as M80 to turn on (when a heater or move commanded) and M81 to turn off at end of prints (its in the documentation)

@droftarts, yes I have moved the jumper; I am currently running printer with 5V external PS, and the 24V PS hooked up to VIN not through the SSR everything working perfectly while im writing my macros for commissioning my printer.

@FelixH, I am trying to get the power off 24V power supply function (AKA ATX power off) so I can turn off that power supply and have the 5V always on so I can quiet my machine when not in use, and send jobs wirelessly to start up and shutdown automatically.

I seem to be having an issue, I thought I had my wiring correct, this is what I have done pictured

my SSR is not starting up the 24V supply as it doesnt seem to be activated, not sure what the issue is as I seem to be getting +5V from the PS_ON all the time even when I set M80, my understanding was that the PS_ON pin is supposed to ground on M80, there doesnt seem to be any voltage potential between 5V direct from PS line and PS_ON pin.

My duet is a v1.04 FW2.05.1

I have tried to figure out if I had a setting incorrect in gcode but Im stuck.

Thanks

For posterity and possibly others interest; after hot air soldering on the U2 and U11 chips (without the wifi module installed I tried again and got no different result to before. Unrecognized device. rebooting and trying completely different computer didnt work. I now have extra parts for next time I screw up. Thanks David @dc42 and @bearer for your help.

@bearer wiring on my machine or wiring in my house 240V.

All was well when it was running on 24V and all was well when I had it plugged into USB, the short happened the instant when I had it plugged into USB and then turned on 24V, I know I had a solid connection to VIN, crimped bootlace ferrells tightened down well and crimped ring connector on the Meanwell. It could have been the cheap chinese usb cable or poor grounding, which I read as something wrong with my house, or power boards im using on PC/printer.

I guess there could be other possibilities but I wasn't heating anything, or moving axis and no end stops were triggered, and I had just tested the endstops were working correctly a couple minutes before and I dont have a Z probe. I was having issues connecting to wifi; it doesnt have external antenna (hence why I was connected via USB but I believed that was caused by mounting under the Flashforge all metal frame.

The screw I thought may have been the culprit was grounded to the metal frame, the power supply and the wall socket, maybe that was the route of the short, but again Im not sure the board contacted the screw, may have been close.

Now Im nervous about plugging in the newer duet I have in, I certainly wont be doing both the USB and VIN, but now I am paranoid, but cant think of anything else I can check, I have made absoluetly sure belt and braces that the board cant contact any metal; could it be a dodgy 24V power supply? Its the Mean Well NES-360-24. I have a Mean Well 450 coming to replace anyway.

@dc42 said in Duet Wifi Bricked probably a short 24V F_VIN to 5V:

Was that after using the Erase jumper? If it wasn't, try again after fitting the Erase jumper.

Hi David I have version 1.01 hardware I tried the Erase button, didnt seem to help, should I try to hold down while plugging into usb or turning on 3.3Vrail? its probably the only thing I havent tried.

I will probably fit the U2 and U11 later when the parts arrive, and try again but I dont expect it to work I just want to practice with the equipment I borrowed off a friend, not much use for the parts otherwise. Ill keep the board as I will probably order another duet by end of the year if the domestic CFO approves.

But was looking at new slice engineering Mk10 to improve the heat management on the Flashforge hotend as Im wanting to insulate and heat the chamber, plus no more thermocouples and uses e3d nozzles, I have the Bondtech Replicator extruders installed already. Ill pull the Duet board out of my other printer (Hypercube Evo) in mean time to get project moving.

Its really disappointing as I was just commissioning it and everything was working well when this USB goundloop hit. (which doesnt appear in the "How to destroy your Duet" post but is in the Warnings which I dont recall reading about when I was last using the forums couple years ago, I thought I knew everything)

I am pretty sure now that is what it was as I was thinking that the 24V to 5V short must have been it as the screw was sort of close and symptoms were similar but I didnt see how it did it spontaneously as it took significant pressure to get it to touch otherwise, and I didnt know about the ground loop issue earlier.

As they say "**it Happens"

Thanks very much Bearer for sticking with me on this unfortunately the fallback procedure didn't work, Time to call it. Full Points 10/10 on Duet destruction.

Well I think this might be the end of the road for this board.

I get 5V 3,3V USB and Diag all on but Windows reporting Unknown USB Device (Device descriptor Request Failed) Error code 43, tried different cables rebooting and different ports It wont recognise the device.

I think that that means the USB device is damaged which means the CPU gone and I think means its uneconomical to fix if all of that has failed. At least the SD cad is ok I guess.

Unless there are any other suggestions, I guess I better start saving my pennies for Christmas.

@bearer said in Duet Wifi Bricked probably a short 24V F_VIN to 5V:

both the cpu and wifi is rated for 3.6v max so 3.8v is probably worth waiting for the 3.3v regulator. Or maybe connect a diode or resisor in series to drop 0.5v at 200mA if waiting isn't an option.

I did this worked nicely, seems the wifi module got warm and the blue light was on very dimmly, cpu seemed cold, so maybe a wifi module blown by the look of it. $8 for a replacement seems reasonable so another component came off. (the 3.3 v and diag. LED came on so hopefully this is it fingers crossed, now waiting for more parts.

But I am concerned that the resistance is still a bit low on the pin u2 (on the processor side) I said was 7.8 has increased to 66 Ohm, which I think may indicate something else nasty, Bearer said: i'd expect to see a couple of kilo ohms or thereabouts" Although the cpu with the wifi module taken off is cool with the 3.3V applied.

I think I was reading elsewhere on the forum others suggesting connecting USB at this point, with the 3.3V connected is possible to look at the cpu, is that possible/wise?

Cheers Again Bearer

Can Confirm no short from 5V to gnd, and replaced usb connector I didnt need to run the bypass was able to get pin 5 to solder to the damaged tracing and also replaced the cable (that was burnt too).

PC USB port seems to be functioning fine BTW; but think its highly likely Im dealing with a USB ground loop issue. But not sure if the damaged U11 is nominally a symptom? and Im not trusting of U2 component. I know my connections to VIN negative were good, bootlace ferrels and ring connector at PS end tightened down good.

I connected the duet to computer and its no longer detecting anything but the 5V and USB LED turns on, I assume that this is a good thing as the usb device is driven off the cpu and that is unpowered, and there is a functioning ground pin.

I checked at pads U2 (removed) for 3.3V short to ground and my multi meter is reading 0.03 ohm on centre pin and 7.3 ohm on the outer pin (processor side) i dont know if this is expected but seems like it could be a short, though I checked on a mighty-board FF RevD I had spare at U14 (24V to 3.3V voltage reg.) and that was indicating short on second pin and the board is fine. Also was planning on using the Mighty-board as my 3.3V source but it out puts 3.8V even if I turn the PS to 19V, If I used that will I damage the duet further? (I think this particular voltage reg was changed in later revisions of mightyboard due to failures)

Also as more info that may diagnose the cause I noted that the 24v power supply I was using when the damage occurred (out of the FFCP im converting) was set at 25.1V I wonder if that may have precipitated the incident combined with the USB 3.0 Voltage? Might be barking up wrong tree?

If I cannot use the Mightyboard 3.8V output Ill have to wait for my digikey order to arrive I guess, and suck it and see when I put a new U2 and U11 on.

Cheers Bearer awesome help.

Just pulled the usb connector, the pin on the connector is gone, and the trace is lifted and slightly shortend (though possibly serviceable, I guess when you said the capacitor just next door you ment C13, which looks like goes to ground on the schematic) I guess it wont matter which side of cap (I'm a hobbiest with a smd rework station so dumb questions may come up, Im just checking).

Ill go into Jaycar in the morning, but still wondering if this is a pointless exercise, its not cost me to much so far Ive got the board cleaned up with U11, and U2 off. I took U2 off so I could check components like the CPU and wifi for overheating as mentioned in another post, with the 3.3v rail but I dont think I can do that till I get U11 back on but not sure.

If it has shorted to ground at the USB connector, I have to start doubting if I did actually short the 5V to fan_vin as I dont seem to have the same component damage as others with similar shorts.

Maybe it does have to do with something with having the USB connected to computer and turning on 24V, as I mentioned earlier everything was working fine till then (and yes everything was turning on and off perfectly before then with USB and 24V separately, so it wasn't a board wiring issue.) I had it plugged into USB 3.0 in the PC a decent usb type-b cable and into a "Chinese" USB B to micro (the micro end has scorch marks on pin 5 too I can see now.

I have to wonder if it was USB 3.0 current draw and sudden powering up from the 24V VIN that may have overloaded it or something? I think on the schematic the VBUS is protected by a diode so I guess its unlikely. Especially as I believe this is an operation mode the board is supposed to handle.

We will see mid month I guess, when the parts arrive from digikey, I might try plugging in the USB when I get it to see what happens when I get the connector fixed up, see if more magic smoke is still inside this thing.

@bearer said in Duet Wifi Bricked probably a short 24V F_VIN to 5V:

v output, and/or 3.3v input/output being shorted causing excessive load on the usb host. using a current limited supply is the easiest. 200mA is a reasonable limit for both 5v and 3.3v
it could also be U11 or any other consumer of 5v/3.3v causing excessive load. you'll just have to pull the hot c

Update, well I can now see under good magnification and light that the USB pin 5 is toasty, (my understanding is that its the ground pin, I was going to pull the connector off the board and take a closer look at the tracings. Im begining to think this is not a good sign as well.

Ahh thanks, I always find Github a bit difficult to navigate, found U2 for V1.01: TC2117-3.3VDBTR going to put in an order for digikey, its great paying 100 times the cost of parts for postage.

Do you suppose the USB current host limit is indicating USB is shot? Thanks

I have looked around a bit on my issues, I think that I have somehow shorted Fan VIN to 5V using an adaptor board with a metalic screwhead touching the back of the board, the thing is I am not sure because where this may have occurred I dont see any scorch marks and I had to push a fair amount to get the screw to touch when I powered things off. The other possibility is that changed the second it happened was I turned on the 24V power supply at the same time I had the duet plugged into the PC which as far as I can tell is not supposed to be an issue.

Anyway I can see visible damage to the U11 chip, I dont think that U2 is necessarily affected it looks OK. I am pretty handy (hobbist) with soldering iron and have SMD hot air rework available. I need part numbers for both, I have the V1.01 board, I think U2 is specific to each version. I think U11 is: SN74HC02PW‎

I was thinking about replacing either/both U11 and U2 (as U2 seems to often blow when these things happen) I think its worth trying as my SD card is reading fine in the PC, and nothing (processor, Wifi) seems to be heating up when plugged into usb or 24v. I may have been lucky. I really dont want to have to buy another one (currently own 2 Duet wifi). and at near $300AUD inc postage its an big investment for my hobby.

Is there any other tests I should do to check to see if it works, I can say that when I plug into PC the PC detects an unrecognisable device, I have rebooted Win10 and changed ports and I continue to get same message, Code 43 the device is in error. when first plugged in the usb indicator and the 5V light flash 4 times then all lights go out, on 24Vin just the 24V and 5V LED come on.

Why was I mucking around with my old board? I was wanting to install another (3rd Duet) on my FF Creator Pro.

Thanks
Pete