HELP! Duet 2 WiFi Configuration and DWC Upload???

[PCNoobNeedsMajorHelp]

In need of major help! I've tried everything in the duet3D configuration tool and I honestly have no idea how to get my board to work with my printer/get everything set up to be able to print again. Upgrading from stock Marlin Board.

Here's what I've got and was wondering if I can pay someone to make me a .JSON file specific to my printer so I can basically Plug and Play this thing, because after 2 months of trying my best I've gotten almost nowhere with this and I'm losing hope fast.

-Printer: Ender 5 (400mm Lead Screw) Purchased Nov.2019
-Coordinate System: Cartesian
-Hotend/Drive System: Micro-Swiss All Metal Hotend Direct Drive (Tool Steel Nozzle)
*Replaced Micro-Swiss Heater Block with E3D Copper Block
-Power Supply: 24V 350w Mean Well
-Main Boards: (Old Board Creality3D Marlin V1.1.4) New Board Duet 2 WiFi Firmware v2.05
-Daughter Board: Type K Thermocouple Daughterboard
-Interface Panel: (Bought with the Duet 2 WiFi) 5i PanelDue Touchscreen
-Heater Cartridge: 24v 60w
-Thermistor/Thermocouple: Type K Thermocouple (I think MAX31856 on CS1 or CS2, not sure which)
-Build Surface: Garolite Sheet

• No BL Touch. (I bought one but want to get this figured out first before I complicate things further.) so for now just regular Z Motor and Endstop

PROGRESS MADE:
-Wiring complete to the best of my knowledge
-Connected to Network and DWC
-All fans work as they should
-Tried about 30 different Config files, Ender 3 pro config file and custom configs, configs i got off of GitHub and nothing is working (I'm not a programmer and have no idea what to do or how to fix this)
-when I messed with something on the PanelDue my Z axis motor went berserk and was running into its Endstops *I had to emergency stop it
-I've checked forums on Duet3D, Reddit, Videos on YouTube, GitHub and nothing I can find is helping me. Everything was always catered to Ender 3's or Ender 5+. I know the Ender 3 has the same board but it has different overall axis locations and design with different dimensions, so I didn't feel comfortable using those files, plus I'm not sure how the direct drive effects things.

I've tried to copy the files directly onto the SD card with no avail, so I guess it probably only reads STL files
The config files I did try to use were immediately followed by "successful upload" on the DWC and then when I went to test things, I have a bunch of error codes and faults:
*Check IR Probe & PanelDue then press x endstop (there is a red LED lit up next to my x endstop)

• There is a red LED lit up next to the word FAULT on my Daughterboard
  *Here is my board wired up
  *Here are the error codes I'm getting
  

My goal with this upgrade is to be able to print remotely as well as reach 300°c+ (I figured I just set the max to 350°c)
I'm printing with Nylon Kevlar for my company. So, for the last 2 months my production has been down and I really need to be able to start printing again. For real, I will pay someone to walk me through this over video chat or whatever, I am desperate!

-If you need any more pictures or info let me know and I'll get those to you guys

Thank You all, in advance for your time and effort with this message and my issue.

-Carson

[Phaedrux]

From your photo of the panel due it looks like you're trying to print the config.g file from the gcodes folder. That's wrong in a few ways.

The folder and file structure for the Duet is as follows. Maybe this will clear things up a bit.

On the SD card you should have a few folders. sys, gcodes, www, and macros.

The sys folder is where your firmware and configuration files go. config.g, homeall, homex, homey, homez, bed.g all the system files. If you're putting those files anywhere else it's not going to work.

gcodes is where the sliced gcode files from your slicer go to be printed. They will show up in the jobs page on DWC.

the WWW folder is where the web control files go. It's basically just web site files that get loaded by your browser when you connect to it.

You've made it pretty far already and you're close, but I think there's just some confusion keeping you from the finish line.

This page has some details on setting up the SD card and what the folder structure should look like.

https://duet3d.dozuki.com/Wiki/SD_Card

Are you connected to the web interface yet? Once the SD card files are in the right place and you're connected you can use the web interface to actually interact with the system more easily.

https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7

Can you upload the config files you're trying to use so we can see what you have right now?

Can you send M115 and report back with the firmware version installed?

[PCNoobNeedsMajorHelp]

@phaedrux
Command Outputs

When I try to upload the zip with sys, www, and menu to DWC it tells me i can only upload 1 file so I don't know how else to do it
Let me know if you need more info or pics

Current Folders on Duet SD

sys Folder items

www Folder items

gcodes Folder items

My Config Files from config tool

Jobs Tab on DWC

Macros Tab on DWC

System Tab on DWC 1of2

System Tab on DWC 2of2

Confi .JSON file from RRF Config Tool

Thanks,

-Carson

[Phaedrux]

Ok thanks that gives me a better idea of what's going on.

Your firmware is 2.05.1. That's fine.
Your sys folder looks ok.
Your www folder looks ok and you're able to access the web interface.

Delete the config.g file in the gcodes folder. Shouldn't be there.

Delete the 01 02 03 04 test macros in the macros folder. Those are factory tests and not appropriate with your hardware.

Delete the DuetDriverFiles and LetsTryThisConfig zip files from the SD card.

I can't read your .json file. It's for a machine. Please post the contents of the config.g file itself or upload the .g files here so I can see them. config.g homeall.g homez.g homex.g homey.g bed.g

Where did you get LetsTryThisConfig?

[PCNoobNeedsMajorHelp]

@phaedrux

The LetsTryThisConfig was just another feeble attempt on the RRF Configuration Tool that I made. It gave me a Zip file. I had tried so many files at this point that I started naming the files like this out of frustration lol.

bed.g

config.g

homeall.g

homex.g

homey.g

homez.g

config.json

If somehow I didn't upload them correctly, I can send screenshots of the files

Thanks.

-Carson

[Phaedrux]

@pcnoobneedsmajorhelp I'll check your files a bit later I can't view the g files on mobile.

[PCNoobNeedsMajorHelp]

@phaedrux

ok

Here are some word docs. Just going to add the .json file so you can read it. I whited out the IP address stuff on it. I wasn't sure if that was sensitive info or not.

Config.jsonWordDoc1.docx

bed.gWordDoc.docx

Config.gWordDoc.docx

homeall.gWordDoc.docx

homex.gWordDoc.docx

homey.gWordDoc.docx

homez.gWordDoc.docx

[Phaedrux]

Ok so the config looks mostly ok. The biggest problem I see is that there is no endstop for z or a Z probe defined, so there is no way to home the Z axis as it is now. You mentioned you have a Z probe. Are you wanting to install it or use the endstop for now?

What problems specifically are you encountering?

Can you go to the gcode console tab in DWC and send the command M98 P"config.g" please? and copy and paste the results here.

[PCNoobNeedsMajorHelp]

@phaedrux

I do have a BL Touch but I don't want to complicate things too much. so i'll just use endstops for now. The main goal with this new board is just to be able to get back to basic printing but with 300+ temperatures

The problems I'm encountering are that no matter what button I hit on the DWC or the PanelDue my printer doesn't react/do anything. I just get errors and faults.
-If I try to test the Hotend temp...nothing happens and I get a fault.
-If I try to test the PMW fans, they don't react.
-If I try to heat the bed, nothing happens
-If I try to move an axis motor nothing happens and I get a fault.
At one point I hit the home button I think, on the PanelDue and my Z motor was traveling at max speed and was running into endstops violently, never stopping. I ended up hitting the Emergency stop button.

Seriously, thank you thus far for your attention and help with my issue. It means a great deal.

-Carson

[Phaedrux]

Well to use the Z endstop you'll need to edit the line in config.g to add the Z endstop.

M574 X1 Y1 S1 ; set active high endstops
Add Z1 in there. That should take care of the Z axis problem providing the endstop is connected correctly and actually working. Do a careful test first time. Does the LED on the board change when you click the switch by hand? Click homeZ and then click the switch by hand before it hits. If it doesn't stop, E stop it.

When you say you get faults and errors. It would help to know exactly what you try to do and exactly what happens including the error message. As in, I send this command and it does this. Or I click on this and it does this.

If you were trying to use those test macros to check things, that might have been part of the problem.

Do the fans work when connected to the always on fan ports?

When you try to turn on the bed heater does the LED on the board turn on? What kind of bed is it? How is it wired?

Motors won't move until they are homed.

[PCNoobNeedsMajorHelp]

@phaedrux
Ok. So. There was a loose wire on my Z Endstop. That's fixed. I did add the Z1 in there after the S1 on the line in the config.g file, saved changes and reset the board. All the LEDs are lit and the Endstops are working when I clicked them with my hand. The bed is heating fine and is working as it should, but I didn't see a light come on when I made the bed active

-Fans are still non-reactive. whether I set them at 100% 0r 0% it seems they're always at 100%. My always on fans are on and working as they should.
-The fault and errors I get are with the Hotend, and I have a red LED light on my daughterboard and next to the LED it says the word "Fault" (so I assume it means when lit, there's a fault)
-It seems when I try to home any axis, they're going in the wrong direction, and then end up running into the opposite end of where the endstops are resulting in me E Stopping it. So I figure in my firmware somewhere it's either an issue of motors set in the wrong direction, the wiring is wrong, or the build plate parameters are wrong and it thinks the bed is longer than it is. Or I'm way off base...not sure

I'll include screenshots of everything

Lights working on duet board

Temp Fault

Temp Reading Error

Hotend Fault

Error codes

Endstops in config.g

Thanks,

-Carson

[Phaedrux]

For the fans always being at 100%.
What are the fans? What voltage?
What ports are they connected to?
What setting is the voltage selection jumper set to?
The photo of the board is too blurry I can't make out any detail.

Sensor short to other wiring is pretty self explanatory. It thinks you have a short in your wiring, so best to double check that carefully.

What daughterboard is it specifically? The config.g says it's configured as a thermocouple. Is it actually a thermocouple? Is the thermocouple wiring extended at all?

In your screen shot of DWC it showed what looked like room temperature being displayed for the hotend. So it seems to be working at first at least. What temp are you trying to heat to? How have you commanded it?

The warning about the M918 command is because you have an M918 command in your config.g to configure a rotary encoder display but that's not supported on duet wifi. So should delete that line.

The waring about config-override.g not found just means that you haven'd done a PID tuning and saved the results with M500 yet. That will go away once you do.

[PCNoobNeedsMajorHelp]

@phaedrux
I'll include a better picture of the board.

I'll include pictures of my fans. the first two pictures are my hardware cooling fans. the larger black one I repurposed from another PSU. and then the small clear one was an upgraded hardware cooling fan I swapped with the stock fan. the small one is plugged into the Always on ports and the larger one is wired directly into the board with power from the VIN. (two white wires with blue ferrules)

As for my part cooling fans, I have the 2 that came stock with the printer, and those are plugged into the PMW ports
-Yellow and blue into Fan 1 port

• Black and Red into Fan2 port
  

"What setting is the voltage selection jumper set to?"...not sure what that is or what you mean? I don't have a buck converter or booster on this board in case that's what you were referring to.
Here's the daughterboard

-Thermistor/Thermocouple: Type K Thermocouple (I think MAX31856 on CS1 or CS2, not sure which)
-The wire is not extended

As for the Hotend, I commanded it to max out at 350c, I'm trying to test for 210 just to see if everything was working

I'll delete that line when I get home from work

*What's PID tuning?

Thanks

-Carson

[Phaedrux]

For the fan you've got connected directly to VIN, why not connect it to the second always on fan port? Then you have the benefit of the fuse protection at least.

For the PWM fan ports, you have them connected to fan1 and fan2, but fan0 is empty. It's recommended to use fan0 as the part cooling fan, and fan1 as the hotend heatsink fan.

So move the yellow and blue wired blower to fan0 for the part cooling, and the red and black wire 40mm fan to fan1 for the hotend heatsink. That seems to be the way it's configured in your config.g anyway.

The fan voltage selection jumper is the little jumper block right in front of the fan ports. I can see in your new photo that it is set to use VIN, so 24v, which matches your fans. That's all good.

For the thermocouple it looks like it's configured correctly and seems to be reading room temp ok. We're you able to pull the wiring and re-check it?

[PCNoobNeedsMajorHelp]

@phaedrux

How do I PID Tune? So like set the temp to 350c wait until it gets there and then let it turn off and then back on again at its minimum temp., and then save that somehow??

I deleted the M918 line.

Ok. So.
-The fans are all connected and in the right ports. They work and are reacting to being adjusted
-The Fault LED went off on the daughterboard after I readjusted them
-I tested the bed and the Hotend and both are working and reaching the desired temps

*Now as for the Homing, how do I even do that from scratch? i just tried to home X and the motors were running in the wrong direction. What do I change in the code to make the motors go in the right direction. I had to E Stop it.

Here are the Errors I got when I tried to home X

Thanks,

-Carson

[Phaedrux]

https://duet3d.dozuki.com/Wiki/Tuning_the_heater_temperature_control

In short though, you send M303 T0 S250 for the hotend and wait while it works. For the bed, send M303 H0 S70 and wait. Where S is the temp you will be printing at. Then after it's done tuning send M500 to save the results.

Good to see we're making some progress.

For the motor directions I'll link you do a test sequence that ill help walk you through figuring out the correct motor directions etc.

Basically though, you manually move the print head and bed to their center positions and then send G92 X100 Y100 to tell the firmware it's homed and at that location so you can jog the axis around.

When looking at the printer from the front, the 0,0 position would be in the front left corner of the bed. +x should move to the right, -x should move to the left, +y should move back, -y should move to the front.

If the axis aren't moving in those directions the direction of rotation of that motor would need to be changed in M569.

With that in mind, where are your endstops located? X would be either left (-) or right (+), y would be front (-) or back (+).

Will need to know that detail to make sure the M574 command reflects the correct location of the endstops. Then in your homing files the homing moves would need to move towards the endstop, so either in the positive or negative direction.

https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+3:+Commissioning/39

[PCNoobNeedsMajorHelp]

@phaedrux

This is what happened when I ran M303 T0 S250
*Also should I use those exact parameters for the test?

So do I move the print head and bed literally to the center, or to 0,0 (front and to the left)? What if I want the homed location to be in the back right, is that possible? That's how it was before I got the duet board.

So it wont let me test the +/- directions until it's been homed, so how do I know if the are going in the right direction or not? When I move the printer head manually the DWC doesn't reflect the movements being made.

So I hit X Home and it goes left for example.
-X endstop is on the right
-Y endstop is on the back right

Thanks,

-Carson

[Phaedrux]

Sorry, I forgot you are still on RRF 2.05. You'll need to use M303 H1 S250 for the hotend. And M303 H0 S70 for the bed.

@pcnoobneedsmajorhelp said in HELP! Duet 2 WiFi Configuration and DWC Upload???:

So do I move the print head and bed literally to the center, or to 0,0 (front and to the left)? What if I want the homed location to be in the back right, is that possible? That's how it was before I got the duet board.

Move it there by hand and send the M92 command just to allow the test to see what directions they move. It's just for the test, nothing permanent.

[Phaedrux]

Once you have confirmed the movement direction you'll need to make these changes to get homing working correctly.

@pcnoobneedsmajorhelp said in HELP! Duet 2 WiFi Configuration and DWC Upload???:

So I hit X Home and it goes left for example.
-X endstop is on the right
-Y endstop is on the back right

You'll need to change a line in config.g to setup the endstops.

M574 X1 Y1 Z1 S1 would become M574 X2 Y2 Z1 S1

your homing files would change to become:

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat May 01 2021 17:31:12 GMT-0700 (Pacific Daylight Time)
G91                     ; relative positioning
G1 H2 Z5 F6000          ; lift Z relative to current position
G1 H1 X240 Y240 F3000 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X-5 Y-5 F6000       ; go back a few mm
G1 H1 X240 Y240 F240  ; move slowly to X and Y axis endstops once more (second pass)
G1 H1 Z-315 F240        ; move Z down stopping at the endstop
G90                     ; absolute positioning

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat May 01 2021 17:31:12 GMT-0700 (Pacific Daylight Time)
G91               ; relative positioning
G1 H2 Z5 F6000    ; lift Z relative to current position
G1 H1 X240 F3000 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X-5 F6000    ; go back a few mm
G1 H1 X240 F240  ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat May 01 2021 17:31:12 GMT-0700 (Pacific Daylight Time)
G91               ; relative positioning
G1 H2 Z5 F6000    ; lift Z relative to current position
G1 H1 Y240 F3000 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y-5 F6000    ; go back a few mm
G1 H1 Y240 F240  ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000   ; lower Z again
G90  

Basically just flipped the direction of the X and Y moves so that they go towards the endstops.

[PCNoobNeedsMajorHelp]

@phaedrux

Ok. So.

-M92 Command failed

-The Bed Tuning was a success so I type M500 and hit enter

-In theory the Hotend test worked but I didn't save it because of this warning I got. I thought I'd check with you before I saved it

-I haven't made any changes to config.g just yet

Thanks,

-Carson