@droftarts I think that's just a weird reflection.
@dc42 Yes, it does seem like that one is darker. I would have thought that would have reported bad when plugged in to USB, but I suppose it must not.
I suppose. I mean worst case, that got reversed in the wiring. The old stepper motors aren't marked well.
Bummer. I guess that's the end for this.
@droftarts Interesting. The 7.5a fuse seems to be the one. Meaning that it seems there's a short either somewhere along the steppers or the extruder or extruder heaters? Everything looks fine...
Just to provide some additional context, the power supply is the old MW LRS-200-24 from the DI3+ as well. It ran everything fine before the frame rebuild (though the bed was different). It also was working fine prior to connecting the additional wires. I left it on and running for a couple of days just to see that the DWC stayed connected after my network issues.
I found some other folks in the Voron space who use this power supply and said it's a built in safety feature. If it detects something is shorted out, it won't supply voltage. Given the behavior I'm seeing when the leads are connected to the board vs not, I suspect this is what's happening. What I'm not sure about is how/where there would be a short on the board. No obvious signs of one.
If anything was connected I was immediately suspect my wiring.
Combing through the forums I found one other post with something similar. The user tried a new power supply and that seemed to solve the issue. I ordered a new LRS-350-24 last night. Should be here today so I'll try it out.
What confuses me here is that the board seems fine when connected to the PC via USB. So I don't think the board is dead.
I guess my hope/thought right now is that the power supply short protection feature is faulty and that's the cause, but I'm also a bit skeptical because it was working prior to connecting all the motors, fans, etc, so it could be a short somehow?
Here are a few pics. The first is the switch wiring. Old pic before I pulled it out of the old frame, but wired the same.
@Phaedrux Correct. No LED lights at all on the Duet board with only 24v supplied.
FWIW, the green light on the power supply flashes 1 time every few seconds. If I remove the wires from the Duet board, the light on the power supply is bright green and steady.
Not sure it was a good idea, but I connected it to both USB and 24v in. It just kept saying WiFi module started, flicking on an off. I did sneak in an m122, but I'm not sure it's trustworthy.
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.4 (2024-11-24 10:43:42) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F2MS4-7JTDJ-3SD6M-KDT8F
Used output buffers: 1 of 26 (11 max)
=== RTOS ===
Static ram: 23488
Dynamic ram: 71076 of which 0 recycled
Never used RAM 18912, free system stack 186 words
Tasks: NETWORK(1,ready,60.8%,462) HEAT(3,nWait 5,0.0%,385) Move(4,nWait 5,0.0%,361) MAIN(1,running,39.2%,792) IDLE(0,ready,0.0%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:02 ago, cause: power up
Last software reset details not available
Error status: 0x00
MCU temperature: min 27.7, current 27.8, max 27.8
Supply voltage: min 0.1, current 0.2, max 0.2, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 1970-01-01 00:00:00
Cache data hit count 116591638
Slowest loop: 0.22ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with "m122" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 0.02ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
=== WiFi ===
Interface state: changingMode
Module is idle
Failed messages: pending 0, notrdy 0, noresp 1
Failed to get WiFi status
Socket states: 0 0 0 0 0 0 0 0
ok
WiFi module started
WiFi module started
WiFi module started
WiFi module started
WiFi module started
I finally wired everything up on my printer and connected everything to the board.
Sadly, the PSU light doesn't go green and nothing lights up on the Duet Wifi board.
I removed every connection from the board and it didn't take long.
I verified that coming out of the PSU I have 24v.
Powered off, connected to the board, and nothing.
I have my fan jumper set to 24v since that's what my fans are.
I have the 5v jumper on internal
I checked the three fuses and they all look fine.
I disconnected the 24v and plugged the board into USB and things seem fine.
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.4 (2024-11-24 10:43:42) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F2MS4-7JTDJ-3SD6M-KDT8F
Used output buffers: 1 of 26 (14 max)
=== RTOS ===
Static ram: 23488
Dynamic ram: 71100 of which 0 recycled
Never used RAM 18888, free system stack 186 words
Tasks: NETWORK(1,ready,13.2%,217) HEAT(3,nWait 5,0.0%,378) Move(4,nWait 5,0.0%,361) MAIN(1,running,84.4%,946) IDLE(0,ready,2.4%,29), total 100.0%
Owned mutexes: WiFi(NETWORK) USB(MAIN)
=== Platform ===
Last reset 00:00:40 ago, cause: power up
Last software reset details not available
Error status: 0x00
MCU temperature: min 24.8, current 27.2, max 27.7
Supply voltage: min 1.4, current 1.7, max 1.8, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2025-02-19 17:55:06
Cache data hit count 1641897346
Slowest loop: 5.69ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with "m122" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 6.14ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.1
MAC address 60:01:94:2e:9a:74
Module reset reason: Turned on by main processor, Vcc 3.43, flash size 4194304, free heap 42772
WiFi IP address 192.168.50.88
Signal strength -54dBm, channel 1, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok
@dc42
It is the internal antenna model.
I wound up factory resetting my router (Asus) and making sure firmware was up to date.
I reconfigured my wireless networks and picked quiet channels. It's been up for 48 hours with no disconnects. So I think I'm alright moving forward.
That said, it still might be interesting for anyone in the future. I would imagine the first suggestion would be going for an external antenna?
Thank you to all who responded here.
For what it's worth, I might be closer to figuring this out?
We have some Govee string lights up around the room. I shut them off and I seem to be able to hold a connection for hours now. So it would appear interference is to blame!!
We also have some Amazon Firestick remotes, which I believe operate off of their own wifi network. We noticed using that remote messes with some twinkle lights in the windows as well.
So if anyone has any advice on handling interference and keeping that to a minimum, I'm all ears. I don't really want disconnects mid-print. I'll try to scan wifi channels and adjust accordingly, but I'm a bit skeptical.
I did see someone replaced their wifi module with a little solder work. I'm no stranger to that. https://clevercreations.org/fix-duet-wifi-esp8266-connection-problems/ But if I'm going that route, I'd want to replace it with something better. Not sure there's a drop in replacement that's better.
@droftarts It would appear I spoke too soon. At some point during the afternoon, it lost connection again. I had used the config generator to just generate some configs and dropped them in.
I then unplugged the board from my usb and plugged it back in and I only got maybe 20 seconds. When I plug it back in, I have to turn on the wifi module again (though that probably makes sense with no config.g)
I tried clearing out the configs and I'm still back to 20ish seconds before I get disconnected.
EDIT: Tried a new card and a new cable. Still the same thing.
It's weird. The wifi module doesn't appear to disconnect or drop in YAT.
Made sure the other network services are off...
Only one browser session connected.
Bumped the number of AJAX retries to 4
No PanelDue
And did the firmware upgrade.
From the browser side I can see it works, then just doesn't. It's almost like the server just crashes? Assuming reprap must be a default password?
It also seems to become available briefly if I reset the wifi module.... It briefly connects after each m552 s1 and after DWC disconnects, M552 shows it's still connected.
@droftarts Thank you for the upvotes!
And thank you for the response. I moved the files accordingly and downloaded the new WiFi firmware and updated it and it currently holding a connection.
First headache over.
Now, I'm left wondering if I should update to 3.6 Beta straight away or get it all running on 3.5.4. I'm leaning towards the latter.
I am seeing some errors in the DWC console, but those may disappear as I work my way through as I imagine I'll need a new config, etc.
FWIW, I pulled the SD card out and checked it again, popped it in and it connected back to my GoPackGo network. I was able to navigate to the DWC with the provided IP, however it quickly disconnected me again.
So I did an M588 S"GoPackGo" to force it to switch to GoPackGoGuest.
And it did.
So I switched to GoPackGoGuest on my PC and navigated to the displayed IP and.... nothing. It just times out.
So here's my m122 now. I'm going to bed and I'll see if sleep helps.
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.4 (2024-11-24 10:43:42) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F2MS4-7JTDJ-3SD6M-KDT8F
Used output buffers: 1 of 26 (14 max)
=== RTOS ===
Static ram: 23488
Dynamic ram: 70940 of which 0 recycled
Never used RAM 19048, free system stack 186 words
Tasks: NETWORK(1,ready,26.8%,239) HEAT(3,nWait 5,0.0%,378) Move(4,nWait 5,0.0%,361) MAIN(1,running,73.2%,501) IDLE(0,ready,0.0%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:09:18 ago, cause: power up
Last software reset details not available
Error status: 0x00
MCU temperature: min 26.9, current 29.7, max 30.2
Supply voltage: min 1.6, current 1.7, max 1.8, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2025-02-06 22:21:18
Cache data hit count 4294967295
Slowest loop: 99.26ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.8ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with "m122" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 17.02ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.0
MAC address 60:01:94:2e:9a:74
Module reset reason: Turned on by main processor, Vcc 3.43, flash size 4194304, free heap 46064
WiFi IP address 192.168.101.88
Signal strength -48dBm, channel 5, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok
I started by trying to go through the upgrade steps for firmware as recommended.
I continued to have an issue where I couldn't stay connected to DWC.
I eventually found myself down to fallback #2.
I was able to flash 3.5.4 successfully via that method.
M115 spits out
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.5.4 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2024-11-24 10:43:42
I ran M122 and saw the wifi module is disabled. Fine.
M552 S0.
ok
WiFi module is started
I noticed my blue light never came on and it never connects to anything.
I ran a M587 and can see my networks.
Remembered networks:
TNCAP2FCC19 IP=192.168.1.14 GW=0.0.0.0 NM=0.0.0.0
GoPackGo IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
GoPackGoGuest IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
Ok...
So I thought maybe I should look at fallback #1.
I've got the SD card set up with a firmware folder containing only Duet2CombinedFirmware.bin and DuetWiFiServer.bin. Then in the sys folder I only have Duet2_SDiap32_WiFiEth.bin. The other folders exist and I put the contents of DWC.zip into the www folder. Looks similar to my backup card, but with less stuff in sys.
I ran m997 s1
Trying to connect at 230400 baud: success, found ESP8266
Erasing 8192 bytes...
Erasing 690688 bytes...
Uploading file...
5% complete
10% complete
15% complete
20% complete
25% complete
30% complete
35% complete
40% complete
45% complete
50% complete
55% complete
60% complete
65% complete
70% complete
75% complete
80% complete
85% complete
90% complete
95% complete
Upload successful
ok
The blue light had a faint flicker so I figured ok that must have worked.
M552 S0 and no light, just ok wifi module started.
So I found a command to enable debugging. M111 S1 P14.
I did an M552 S-1
WiFi module stopped
ok
Followed by another M552 S0.
m552 s0
WiFi:
WiFi: ets Jan 8 2013,rst cause:2, boot mode:(3,6)
WiFi:
WiFi: load 0x40100000, len 5548, room 16
WiFi: tail 12
WiFi: chksum 0xf7
WiFi: ho 0 tail 12 room 4
WiFi: load 0x3ffe8008, len 24, room 12
WiFi: tail 12
WiFi: chksum 0x1e
ok
WiFi: ho 0 tail 12 room 4
WiFi: load 0x3ffe8020, len 2412, room 12
WiFi: tail 0
WiFi: chksum 0x2a
WiFi: csum 0x2a
WiFi: phy_version: 1163.0, 665d56c, Jun 24 2020, 10:00:08, RTOS new
WiFi module started
ESP reported status change
ESP reported status change
Wondering where I've gone wrong. I noticed that in the SD Card docs (can't post link due to rep) it says the Duet2_SDiap32_WiFiEth.bin should be in the firmware folder and says nothing about the DuetWiFiServer.bin file.
Hoping I'm closer after that infuriating DWC disconnect mess. I understand that the issue may be related to my network. GoPackGo is 5Ghz/2.4Ghz with a different router than I had previously. I was hoping I could maybe try to connect to GoPackGoGuest which is strictly 2.4Ghz and used for other IoT devices in my house.
Hi folks,
It's been quite a while since I've had my printer running. I put a Duet Wifi in my Wanhao Duplicator i3+ in either 2019 or 2020. Late 2020, I decided to rip it all apart and do some upgrading. Can't post links but following someone else's footsteps called a ReDuplicator.
I had already done the Hemera hot end and the BLTouch before taking it apart. The big goal was the removable build plate and some better parts.
I got it all taken apart and built the new frame. Then my kids came, I started a new business, and put my printing on hold.
I'm finally trying to get back into it. I just built a new enclosure that houses the board and power supply instead of just leaving them on the table. I'll reconnect all the wires over the next day or two but I have a few questions....
Given the new bed size and taller z axis, I know I can't just plug it in and start printing. So should I start completely fresh? Or try to see where I'm at and modify/upgrade?
Is RRF still the way to go? Or is Klipper the new standard? I'm not afraid to switch if it makes sense.
I should be able to grab some of the files and settings from the card, right? I did everything through the web interface previously. No PanelDue.
Anything else I should know before I jump back in?
My motors are still whatever came on my wanhao duplicator i3+. Probably should have got new ones.
It sounds like my best bet is just to try it and see how it goes. Thanks folks!
I just rebuilt the frame on my 3D printer. It's looking great and I'm excited to get it running again.
The design I followed seems to have forgotten about end stop placement with the upgrades I have. Given that my printer is down, I was going to cut some small blocks of wood to hold the end stops until I can print something so that things match. But as I was browsing the docs, it seems like sensorless homing is a possibility with this board. I run a BLTouch 3 so I'm not worried about the Z-axis, but it sounds kind of nice for the X and Y.
So I'm just curious if other folks have run their printers sensorless and what the experience has been? I doubt I'd ever need 100% of the build plate in either direction so if it's very slightly off occasionally, I don't think that'd be a huge deal... But yeah. Just looking for a little feedback before I commit one way or another.
Just wanted to come back here to post the results and close the loop. Overall, I was able to tune things and get things looking good. Here are the after pics https://imgur.com/gallery/Ogqr8lM
I did switch the order of the walls.
I printed the pressure advance test here https://forum.duet3d.com/topic/6698/pressure-advance-calibration/18 and adjusted accordingly. This made a nice improvement.
I lowered my print temp to 230. Might play around a little with this just to see.
I turned off combing. I did this more so because retraction on this extruder is tiny.
I also lowered my flow to 98%, lowered the speed of the walls to 60%, and turned on my cooling fan 30% after layer 3. For bridging I jumped the fan to 100%.
I've still got some slight ringing, but I'm going to tighten the belts a little and see how that plays out. They seem like maybe they are just a touch loose.
Just want to say thanks to @jens55 and @Phaedrux . Your tips definitely helped.
I recently gave my Wanhao Duplicator i3 Plus an overhaul. I upgraded the board to a Duet Wifi, rewired everything, and changed to a Hemera extruder. Many would say it wasn't worth it, but I learned a lot along the way which I love. My goal is to eventually go full ReDuplicator.
I was able to dial in PLA pretty quick and easy. Even pushed the speeds up to 100mm/s with decent results. A little ringing/ghosting that high. But I am stuck on PETG. I got some pretty iffy prints with the settings I used on my previous Micro Swiss all metal hot end. The cube dimensionally is good in both PLA and PETG so I imagine my axis steppers and esteps are calibrated ok.
I know I have to tune my bridging. The fan was completely off the whole time which I think lead to the mess when the ceiling went on the Benchy although it did surprisingly almost make a full recovery.
The main issue I'm not sure how to fix are the gaps along the X axis. It happens on the bottom and top layers on the cube but seems a bit more random in the Benchy. It's like it's retracting too early on layer changes maybe? I'm keeping the retraction lower as I've heard is best on the dual gear extruders like the Hemera. I had pressure advance off for these prints, and after poking around the forums, I feel like maybe that's where I've got issues. That and maybe still acceleration and jerk issues as I'm seeing the banding on the Y side even at 45mm/s for PETG.
Cura Print Settings
Layer Height: .2mm
Wall/Top/Bottom Thickness: .8mm
Top/Bottom Layers: 8
Infill: 20%
Infill Pattern: Concentric
Print Temp: 240
Build Plate: 75
Speed: 45 mm/s
Retraction Distance: .5mm
Retraction Speed: 30 mm/s
and my config.g
; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Mar 05 2020 15:48:10 GMT-0600 (Central Standard Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"wanhao-di3" ; set printer name
; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S0 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X128 Y128 Z128 E16 I0 ; configure microstepping without interpolation
M92 X632.71 Y633.66 Z3229.06 E397.09 ; set steps per mm
M566 X540.00 Y540.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z1200.00 E3000.00 ; set maximum speeds (mm/min)
M201 X800.00 Y800.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X855 Y855 Z855 E855 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
;M572 D3 S0.025 ; enable pressure advance
; Axis Limits
M208 X-3 Y10 Z0 S1 ; set axis minima
M208 X200 Y200 Z180 S0 ; set axis maxima
; Endstops
M574 X1 Y1 Z1 S0 ; set active low and disabled endstops
; Z-Probe
M307 H3 A-1 C-1 D-1 ; disable heater on PWM channel for BLTouch
M558 P9 H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P25 X13 Y54 Z1.659 ; set Z probe trigger value, offset and trigger height
M557 X10:200 Y10:200 S40 ; define mesh grid
; Heaters
M305 P0 T100000 B3988 R4700 ; set thermistor + ADC parameters for heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M305 P1 T100000 B4725 C7.060000e-8 ; set thermistor + ADC parameters for heater 1
M143 H1 S285 ; set temperature limit for heater 1 to 285C
; Fans
M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S0 I0 F500 H-1 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P2 S0 I0 F500 H-1 ; set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off
; Tools
M563 P0 S"E3D Hemera V6 .4" D0 H1 F0:1 ; 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
; Miscellaneous
T0 ; select first tool
M501 ; for saving
I'm going to run through the post stickied here today with the tuning macros, but if anyone has any thoughts/insight/experience, I'd love to hear it. I feel like I'm capable of tweaking and adjusting to many of the more common issues, but this one is feeling slightly more advanced.
@droftarts said in Upgraded extruder, nozzle offset clarification.:
https://duet3d.dozuki.com/Wiki/Centering_the_bed_or_setting_the_bed_origin
Thanks for the link. So when would M206 be used?
I recently upgraded my extruder to an E3D Hemera. The extruder and nozzle are positioned differently from the previous setup. When I home the X axis now, the nozzle is now off the build plate by ~3mm (or -3mm X direction). And when I home the Y axis, the nozzle is about ~10mm into the build area (or +10mm Y direction).
I saw when defining the tool you can set an offset with the G10 command. I also watched a video of someone doing their extruder upgrade and using the M206 command to set the axis offset from the nozzle.
So my question is G10 or M206? And do I pass the offsets like they are (-3, 10) or do I reverse them? Maybe that's different depending on which of these two commands I use.
@chas2706 I know it's been a while, but if you didn't mind sharing your load and unload macros, that'd be great. The filament management, in my opinion, is a weak point of the interface.
I get what they were going for but it's a step too far. Simpler is better here.
I recently upgraded my Wanhao Duplicator i3 Plus to the Duet Wifi. I'm loving most of the options available to me and I feel like I've got my PLA dialed in.
One place I'm struggling is the filament system. I initially had to call the API to create the directory for filaments. That's fine. But then I can't seem to name filaments appropriately? I managed to get one in called PLA but if I try anything longer like InlandBluePETG it fails.
Operation failed (reason: err 1)
I have multiple PLA filaments I'd love to define, but also, they will all use pretty much the same load/unload macros. I'm not sure if I'm missing something obvious? I'm guessing I must be?
And speaking of those macros, I initially grabbed the ones off of the site, but running the extruder at 3000mm/min to load and unload seemed real fast. Does anyone have a better macro set up they'd like to share? For now I toned it down and it's working, but I don't love it. I liked the default Wanhao behavior of waiting for the end to get up to temp, then running the extruder slowly until I pushed the button to stop it.