Large Format Dowell to Duet conversion
-
I undid the changes and unplugged the 3D touch and it still does not work. How can even wiring up one io wrong fry the whole board?
I noticed, before all this crashed, the print cooling fan was spinning but hardly getting going then stopping again.
-
@charles-fraser said in Large Format Dowell to Duet conversion:
I noticed, before all this crashed, the print cooling fan was spinning but hardly getting going then stopping again
unplug this as well - the power cycle the power to both the 6HC and the 3HC. Run M98 P"0:sys/config.g" to verify the changes are undone.
-
Nothing is happening when I do any commands anymore. It just spins around and around. All things added are disconnected now. The 3HC doesnt blink anymore
-
@charles-fraser can you still access the network interface? in that case send M122
-
m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.0beta5 (2021-10-12 13:53:56) running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-9P63L-DJ3S0-7J1D6-3SD6S-1UJV8 Used output buffers: 1 of 40 (12 max) === RTOS === Static ram: 151104 Dynamic ram: 65108 of which 0 recycled Never used RAM 134460, free system stack 219 words Tasks: SBC(ready,0.4%,518) HEAT(notifyWait,0.1%,361) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,333) TMC(notifyWait,7.1%,92) MAIN(running,41.2%,1241) IDLE(ready,51.2%,30), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:00:30 ago, cause: power up Last software reset details not available Error status: 0x00 Step timer max interval 132 MCU temperature: min 12.4, current 21.8, max 21.8 Supply voltage: min 24.1, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0 Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: pos 0, standstill, SG min/max 0/0, reads 41983, writes 14 timeouts 0 Driver 1: pos 0, standstill, SG min/max 0/0, reads 41983, writes 14 timeouts 0 Driver 2: pos 0, standstill, SG min/max 0/0, reads 41983, writes 14 timeouts 0 Driver 3: pos 0, standstill, SG min/max 0/0, reads 41983, writes 14 timeouts 0 Driver 4: pos 0, standstill, SG min/max 0/0, reads 41983, writes 14 timeouts 0 Driver 5: pos 0, standstill, SG min/max 0/0, reads 41983, writes 14 timeouts 0 Date/time: 2021-11-03 20:39:44 Slowest loop: 0.97ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP* is doing "M122" in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger* is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === CAN === Messages queued 168, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 48), ts 154/0/0 Tx timeouts 0,0,153,13,0,0 last cancelled message type 30 dest 127 === SBC interface === State: 4, failed transfers: 0, checksum errors: 649 Last transfer: 2ms ago RX/TX seq numbers: 16350/750 SPI underruns 2, overruns 2 Disconnects: 0, timeouts: 0, IAP RAM available 0x2b7dc Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.4-b5 Code buffer space: 4096 Configured SPI speed: 8000000Hz Full transfers per second: 37.18, max wait times: 2187.4ms/29.1ms Codes per second: 0.01 Maximum length of RX/TX data transfers: 2868/560 -
@charles-fraser and after doing the following:
Power cycle the 3HC
send M98 P"0:sys/config.g"
Send M122 B1 -
I’ve done that and nothing. When I send those commands the DWC gets stuck in the spinning wheel of death. There is no blinking light on the 3HC
-
@charles-fraser it sounds like that 3d touch has caused an issues (or resurfaced an issue from the previous heater problems) with the 3HC. I remember you had issues with it right at the beginning - is this a new 3d touch or your original one?
We previously reset and reflashed the firmware on the 3HC. I think that's the step to take again now:
To force a firmware reload on the 3HC set all the dip switched to 0, power cycle the 3HC, you should see the diag light flash a bit. when its showing steady flashing in sync with the mainboard, switch the dip switch back to 1 as it was then power cycle the 3HC.
-
I have done that and still no flashing light
Also this is the same 3D touch as before. Now I remove it but still the 3HC doesnt flash. Before when I removed it the 3HC started working again. There is nothing on the board and it’s not working
-
04/11/2021, 10:20:13 Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin) 04/11/2021, 10:20:09 Error: M308: Response timeout: CAN addr 1, req type 6031, RID=6 04/11/2021, 10:20:06 Error: M558: Response timeout: CAN addr 1, req type 6036, RID=5 04/11/2021, 10:20:06 Error: G31: Invalid Z probe index 04/11/2021, 10:20:06 Error: Invalid remote handle 04/11/2021, 10:20:05 Error: M906: Response timeout: CAN addr 1, req type 6043, RID=4 04/11/2021, 10:20:05 Error: M92: Response timeout: CAN addr 1, req type 6042, RID=3 04/11/2021, 10:20:04 Error: M350: Response timeout: CAN addr 1, req type 6042, RID=2 04/11/2021, 10:20:02 Error: M584: Response timeout: CAN addr 1, req type 6042, RID=1 04/11/2021, 10:20:00 Error: M569: Response timeout: CAN addr 1, req type 6018, RID=0 04/11/2021, 10:19:59 Connected to duet3 -
Any help? Is it fried? I can't believe it fries just because of a short that doesn't make sense to me
-
Is the 3.3v LED lit on the 3HC? (its with the other power LEDS in the top left og the board as you have it oriented.
-
@charles-fraser said in Large Format Dowell to Duet conversion:
Not sure what is going on here? why were there two sets of wires going into IO2?
-
@t3p3tony said in Large Format Dowell to Duet conversion:
Not sure what is going on here? why were there two sets of wires going into IO2?
None of this is plugged in any more. I explained this in my post with the description of the wiring of the 3D touch above. Please have a look.
-
-
@T3P3Tony this explains the wiring
@charles-fraser said in Large Format Dowell to Duet conversion:
I’m sorry it’s a bit of a fudge but I have only been able to get the 3D touch wired up (I hope correctly) with the 3HC, IO_2
Here is what the wiring from the touch is supposed to be:
But the 3D touch I have does not have a white wire, it has a blue wire though so I am guessing that’s the only difference.
I have to connect the BL touch to two different cables, each with four wires in them to reach the board at the other end of the printer. In one of the cables, two of the wires are already used by the NTC thermistor so it looks like this:
Then I can only reach IO_2 on the 3H with all that following this diagram:
Which looks like this:
I hope that’s correct! I’ll try to change the code and hope it works!
-
Hi please advise. Do I need to buy a new board or what to keep things moving forwards?
-
@charles-fraser It looks like the 3.3V regulator & possibly other ICs on the 3HC was blown by the 3d touch. I suspect given that it caused issues before that it is faulty, I don't know much about the 3d touches but if they are the same as the BL touch internally they should not blow the board by just mis wiring.
Yes you need to replace the 3HC
-
Okay I will as soon as I have some money. Is there a way to diagnose what caused this? Is a fan wired the wrong way or a 3D touch really able to blow a whole board?
-
@t3p3tony hi Tony, I have the replacement 3HC now and am awaiting a BL Touch to arrive next week.
I’ll try to reconnect the new 3HC and rewire it as it was before just leaving out the fan and 3D Touch.
