@Danal I got it! my white wire had a bad crimp.

That was definitely it. I swapped the wire around it works fine. What is interesting, is I have two duets. My other duet has a simple endstop inserted to E0 endstop. Also the wire is inserted at 180 degree rotation as compared to the board giving me issues. weird.

Thanks bearer

Good morning all!

I am having an interesting issue. My Duet wifi 1.02 is shorting when I plug a filament runout switch into it. I have tried two different wires and two different simple runout switches. Both short the board to where I cannot even command it through YAT or Pronterface.

There seems to be mentions of this happening here. https://duet3d.dozuki.com/Wiki/What_to_do_if_your_Duet_won't_respond#:~:text=If the red LEDs are,probe connectors from the Duet.&text=Then reconnect the USB cable and check the LEDs again.

In particular, when I plug in my filament switch, the 3.3v light shuts off as does the wifi led and a few others. The 5v and VIN led are the only ones that remain on.

I am really confused with this, as the filament runout switch was working fine until last night. I uploaded a .gcode file and everything went kaput.

Any advise on this subject will be greatly appreciated!

I am running RRF2.05.1 and DWC 3.1.1.

Thanks!

Jordan

Certainly, I will give it a try.

I deleted that particular gcode file and resaved it. No settings changes, and it worked fine.

I will go ahead and do the steps you advise.

Thanks!

Jordan

I checked the G Code console and there were no errors reported.

The temperatures were very stable and correct.

My config and the gcode file in question are attached.

RRF 2.05.1 for Duet Wifi 2 1.02 (2020-02-09b1), DWC 3.1.0.

I have a Duet laser sensor, but it is disabled currently.

config.g
config-override.g
https://1drv.ms/u/s!AmZ7ep7HflN2hIIOYB-I_AEdDtFNGA?e=4GRWye

Hello everyone! I am having an interesting problem regarding my Duet 2 Wifi.

For context, I am doing my first large volume print on this particular machine (a heavily modified Ender 5). For a slicer, I use Simplify3d, and it has never failed me (until maybe now?). I even ran a simulation on this gcode file before actually printing it so I could get an accurate print time. The simulation worked flawlessly, giving me a 35 hour estimate.

Next, I started the print, watched the first couple layers go down, and went to sleep. I woke up about 5 AM and discovered that it was paused. Puzzled, I opened up DWC and found it in fact to be paused. I next pressed resume print, and it went to its resume position on the print. However, before it extruded or moved, it paused again. This is where it gets weird.

A blank box, similar in size and style to the box that flashes on DWC when a filament sensor pauses the print, came up. The only thing in this box was the word "okay." I selected okay with my cursor, and it went away. At this point, the print tool had moved back to the home position. I pressed resume print again, and everything repeated.

Can anyone tell me what is going on here?

Be safe during this pandemic everyone!

Jordan Stephenson, JD

@Danal said in Genuine BLTouch 3.1 reading "1000" in Z probe on web control:

One last thing-- I tried the stock config home all and home z files, and they did not properly work. Yours did work for me. Thanks, as I still needed those changes.

@Danal I got it! my white wire had a bad crimp.

I swapped the wire, and still the same problem. Still reading "1000." It was the white wire that was bad.

I just discovered a faulty dupont jumper. I suspect this is the problem!

@Danal When I tried your files, I received this error: "G28 Z

Error: Z probe already triggered at start of probing move"

I did restart my machine once I changed the files.