Posts made by dlmorgan999

@KenW I do have that macro, and earlier today I accidentally hit the button for that on the PanelDue when I meant to hit Filament Load. That explains it. I'll get rid of that file. Thanks again for the quick help, Ken!

@KenW Sure enough - that file was missing (although all the other files seem to be there). I had intended to check the config files into revision control (like I do for my other printers), but I forgot to do this one. Fortunately, I still had a copy of all the config files on my laptop. I think that copy of the file is slightly out of date, but at least the printer is booting now.

Any idea why that file would disappear? In any case - thanks for the help!

With the help of a friend, I recently built a new printer. It's been working great for several months, but today I was removing a print from the BuildTak plate when all of a sudden one of the fans went to 100% (hotend I think). Then I noticed that the PanelDue was in a "Connecting" state. I went through the troubleshooting steps listed on the website. The LEDs are all looking good (red and green are lit, and status is flashing). So I turned the printer off and connected using YAT via USB. At that point I was able to talk to the Duet, but if I power up the printer again, I get the same non-working state. I don't know where to look next. Any suggestions?

Here's the firmware info:

RepRapFirmware for Duet 3 Mini 5+ version 3.4.6 (2023-07-21 14:09:13) running on Duet 3 Mini5plus WiFi (standalone mode)

I just upgraded to 1.21 and the issue appears to be resolved now.

I have that on my list, but it will likely be a few days before I can get to it. I'll let you know what happens.

I'm also seeing this and have been struggling with it for quite a while. It would be nice to know if this is an acknowledged / reproduced issue. I'm running 1.20 versions of all firmware.

To add a data point to this thread, I'm a fairly new Duet user. I've seen layer issues myself several times. Right now, I'm about halfway through the first layer of a pretty large bed area print, and DWC is reporting I'm on layer 9 of 86. It should be layer 1 of 90.

Thanks for the suggestion. I looked, and found that there were two T commands right before my starting script (I'm using Simplify3D), and one immediately after, but no more (see below). This is very odd.

[[language]]
M104 S235 T0
M109 S235 T0
G28 ; home all axes
G1 X30 Y50 F3000 ; bring extruder to front
G92 E0 ; zero the extruded length
G1 Z10 ; lower
G1 E19 F200 ; purge nozzle quickly
G1 E26 F60 ; purge nozzle slowly
G92 E0 ; zero the extruded length again
G1 E-2.5 F400 ; retract
G1 Y320 Z0 F9000 ; pull away filament (move to back left)
G1 X40 F9000 ; wipe
G1 Y330 F9000 ; wipe
G1 E0 ; feed filament back
G92 E0
G1 E-0.7500 F2400
G1 Z0.135 F1002
; process Process1
; layer 1, Z = 0.135
T0

The firmware is version 1.19., and I'm using just an E3D Titan Aero. This is on a Hypercube Evolution that I just finished building. I've done a few prints successfully, so this definitely surprised me.

I was about 10.5 hours into a print. I came into to check on it and all looked good but on closer inspection I found that it was not extruding. Then I noticed that the hot end temperature was back to ambient (I forgot to look to see if it was showing as active). I was puzzled, so I looked at the G-Code Console, and found this (with the message at the top continuing until I cancelled the print). Any idea what happened?

[[language]]
7:35:18 AM
Attempting to extrude with no tool selected.
7:35:14 AM
Attempting to extrude with no tool selected.
7:35:10 AM
Attempting to extrude with no tool selected.
8:59:01 PM
M32 Headphone_Stand - take 2.gcode
File Headphone_Stand - take 2.gcode selected for printing
8:56:34 PM
Connection established!

That sounds correct to me. I just finished building my HEVO a few days ago. I'm using optical endstops, and I'm pretty sure the LED is on all the time except when they are homed. Have you tried doing a home yet, or are you not quite at that point?