Posts made by cbusillo

@dc42 The problems seems to have gone away with the new RC3. Thank you for whatever was fixed

@dc42 Testing new version now. Sorry for not doing this sooner, I had too much going on.

ESD doesn't make much sense to me since it only happened on RC3+. I'll check the ground anyway. Grounds can cause so many flakey issues, right? :). Thank you for all you do.

@droftarts I will after this 1-2 hour print finishes. I flashed it twice and both times it restarted within 30 minutes (I was out of the room so it might have restarted multiple times. Just to be clear, I'm not asking for troubleshooting help as I am fine with downgrading to RC2, I just want DC to be aware of the problem. I'll follow up shortly with M122 logs again. It reboots while doing nothing, just sitting there idle. I only noticed because the fan turn on like they do at power up

@droftarts Hi!

With rc3+ I had reboots. Is there more than one rc3+?

@gloomyandy anything more you want me to provide? I need to flash it back in a bit for a couple of prints, but I can collect whatever info you need.

To be clear, RC3 printed fine, but it only loaded the css file once in maybe 100 tries. RC3+ reboots while idle. I know at least once in 30 minutes, probably more since I wasn't in the room.

@gloomyandy

M122 output

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.3+ (2024-02-13 13:33:37) running on Duet Ethernet 1.02 or later
Board ID: 08DAM-9K9K2-NGNSN-6J9DL-3S46Q-9RSBJ
Used output buffers: 1 of 26 (14 max)
=== RTOS ===
Static ram: 23256
Dynamic ram: 68232 of which 0 recycled
Never used RAM 21656, free system stack 204 words
Tasks: NETWORK(1,ready,23.1%,220) HEAT(3,nWait 5,0.1%,326) Move(4,nWait 5,0.0%,359) MAIN(1,running,73.6%,743) IDLE(0,ready,3.2%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:27 ago, cause: software
Last software reset at 2024-02-16 13:20, reason: HardFault undefInstr, none spinning, available RAM 21192, slot 0
Software reset code 0x4073 HFSR 0x40000000 CFSR 0x00010000 ICSR 0x00400003 BFAR 0xe000ed38 SP 0x2001ff98 Task NETW Freestk 29864 ok
Stack: 200036c0 00000004 00004000 400e1400 ffffffff 0041bd09 00459000 010f001f 21000000 ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
Error status: 0x00
MCU temperature: min 28.4, current 29.6, max 30.1
Supply voltage: min 24.4, current 24.5, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
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: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 2024-02-16 13:21:23
Cache data hit count 1076937391
Slowest loop: 1.68ms; fastest: 0.18ms
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.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 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.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 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Filament sensors ===
check 0 clear 101141
Extruder 0 sensor: ok
=== Network ===
Slowest loop: 6.08ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex
Socket states: 5 2 2 2 2 2

Hi! I had issues with 3.5.0-RC3 where the css was consistently not served on My Duet 2 Ethernet. I found the updated RC3 on the forum that fixed the issue. This version restarted twice while idle. I went back to RC2 and that seems to have fixed the issues.

I just wanted to raise this incase it's an issue that needs to be addressed before release. I didn't copy the entire M122 (I should have) but this was from after the restart. If there is anything I can do to help, just let me know. I do not need help fixing it, since I am fine on RC2.

Last software reset at 2024-02-16 09:31, reason: HardFault undefInstr, none spinning, available RAM 21656, slot 1
Software reset code 0x4073 HFSR 0x40000000 CFSR 0x00010000 ICSR 0x00400003 BFAR 0xe000ed38 SP 0x2001ff98 Task NETW Freestk 29864 ok
Stack: 200036c0 00000004 00020000 400e1200 ffffffff 0041bd09 00459000 010f001f 21000000 ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
Error status: 0x00```

Thank you both! It turned out to be the change in the M593, input shaping. The discord helped me figure that one out. I didn't realize the old algorithm was not in the new firmware. I have an accelerometer coming so I can really tune it now. thank you both for the great hardware/software.

Hi all. Is there an archive of release candidates anywhere? It looks like they have been removed from GitHub. I am specifically looking for 3.2-RC2. That seems to be the last version of the firmware that worked for me without layer shifting. I am trying to load that firmware again to compare to 3.2 and newer to see if the shifting goes away. I have two boards and both have this issue. Before I updated the second one from 3.2-RC2 to the latest, it worked perfectly. Thanks all! Hopefully I can figure out what I am doing wrong and get this fixed.

Thank you so much for the link. Kicad source is awesome. It goes through a 10k to the MCU. Its showing a much lower static resistance on one direction. I think that usually means a bad internal diode in the package. Oh well. I'll likely just live with it on this board.

After the mishap I added a Schottky diode and its working on the Z stop. Thanks again.

Hi 24V power supply and a 10-30 volt probe. It put 22V directly into the Z probe port.

And of course this is the 1.03 that was not tolerant of higher voltages.

@fcwilt said in Connected inductive probe directly to Z probe:

We need more information.
Are you using a 12 or 24 volt power supply?
Was the inductive probe a 5 volt model or a 10-30 volt model.
I use 10-30 volt inductive sensors and they often output a signal that is just a bit less then the power feeding them.
This might damage a Duet input - depending on board model, board version, board input.
Duet 2 Wiring Diagram
Duet 2 Wiring Guide+Wiring+your+Duet+2+WiFi-Ethernet/9)
Frederick

Hi, I finally managed to hurt my Duet Ethernet 1.03. I wasn't paying attention and sent the output of an inductive probe directly into the z probe port. It still reads but not very well. I switched to the Z end stop and that seems to be working for now. Is there a benefit to the z_probe vs z_stop pin?

Also is there a schematic around? I'm thinking I either blew a cap or caused direct damage to the micro controller. I can fix either problem, but before I go trying to figure out the board layout, I wanted to ask.

Everything is working now. Thank you so much for the quick help

It seems to be working. The beta 4.1 wasn't on the releases page so I didn't know it existed. I'll do a real print with a pause in it after this current print. Thank you for the quick help.

Hi, my Duet Ethernet is stuck on pausing. It is currently not printing, but has the heaters on correctly.

I am trying to get the pause command to run, but every time I used M600, M226, or the pause button, the Duet appears to freeze. Nothing I can do or send seems to get it out of "pausing" except for resetting the board.

I am on the newest beta firmware. I cannot find anything related to this experience on the forum. M122 is included below. I welcome any suggestions before I hit the power button and restart this print again.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta3.2 running on Duet Ethernet 1.02 or later
Board ID: 08DAM-9K9K2-NGNSN-6J9DL-3S46Q-9RSBJ
Used output buffers: 3 of 24 (24 max)
=== RTOS ===
Static ram: 24108
Dynamic ram: 96412 of which 60 recycled
Never used RAM 9468, free system stack 116 words
Tasks: NETWORK(ready,164) HEAT(blocked,308) MAIN(running,422) IDLE(ready,20)
Owned mutexes:
=== Platform ===
Last reset 34:48:29 ago, cause: software
Last software reset at 2020-12-08 21:58, reason: User, GCodes spinning, available RAM 9468, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0x00
MCU temperature: min 15.6, current 26.4, max 27.4
Supply voltage: min 24.2, current 24.5, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 52933, standstill, SG min/max 144/965
Driver 1: position 63618, standstill, SG min/max 141/1010
Driver 2: position 2149, standstill, SG min/max 105/1023
Driver 3: position 0, standstill, SG min/max 0/1023
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2020-12-10 08:47:16
Cache data hit count 4294967295
Slowest loop: 116.95ms; fastest: 0.20ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.0ms, write time 80.9ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 103, MaxWait: 67361790ms
Bed compensation in use: mesh, comp offset -0.070
=== MainDDARing ===
Scheduled moves 91403, completed moves 91403, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 1.0
Heater 1 is on, I-accum = 0.6
=== GCodes ===
Segments left: 0
Movement lock held by File
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0 21, running macro
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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 92.94ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 of 8
Interface state active, link 100Mbps full duplex
=== Filament sensors ===
Extruder 0 sensor: ok

Robert if Qdeathstar falls through let me know.

Did you get the gloss or matte?

Material : Printing Temperature Initial Layer on 3.2

It works!