Topics created by Krohm Koala

@chrishamm Here it is :

M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.3+pre (2023-03-27 16:33:18) running on Duet 3 Mini5plus WiFi (SBC mode) Board ID: RBLWU-5096U-D65J0-40KMQ-K513Z-HRUJH Used output buffers: 1 of 40 (17 max) === RTOS === Static ram: 102980 Dynamic ram: 105380 of which 0 recycled Never used RAM 30840, free system stack 206 words Tasks: SBC(ready,5.9%,464) HEAT(nWait,0.0%,359) Move(nWait,0.0%,360) CanReceiv(nWait,0.0%,941) CanSender(nWait,0.0%,335) CanClock(delaying,0.0%,342) TMC(nWait,0.6%,114) MAIN(running,78.0%,549) IDLE(ready,14.7%,30) AIN(delaying,0.8%,273), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:00:02 ago, cause: software Last software reset at 2023-04-02 09:29, reason: AssertionFailed, Gcodes spinning, available RAM 30456, slot 1 Software reset code 0x4923 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000087d BFAR 0xe000ed38 SP 0x2003fe74 Task MAIN Freestk 62331 ok Stack: 0000019f 000bf718 0009b5ed 00000002 0009c775 00000000 00000000 2003b728 2000302c 2002c2c0 200165fc 00000000 00000000 00000000 00000000 20032738 000993f3 20018758 2003fee0 200327c0 00000000 00000000 00083cd1 20018758 20032738 00000000 00086275 Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 2169, completed 2169, timed out 0, errs 0 MCU temperature: min 22.9, current 23.3, max 23.3 Supply voltage: min 24.5, current 24.5, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/19, heap memory allocated/used/recyclable 2048/224/8, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 27, reads 86, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 27, reads 86, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 25, reads 85, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 144, read errors 0, write errors 1, ifcnt 34, reads 84, writes 14, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 144, read errors 0, write errors 1, ifcnt 34, reads 85, writes 14, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-04-02 09:29:29 Cache data hit count 3995363 Slowest loop: 144.04ms; fastest: 0.00ms === Storage === Free file entries: 20 SD card 0 not detected, interface speed: 0.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, comp offset 0.000 no step interrupt scheduled === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === DDARing 1 === 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, null HTTP* is doing "M122" 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 doing "M81 C"PS_ON"" in state(s) 0 0, running macro Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000803 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === Filament sensors === Extruder 0 sensor: ok === CAN === Messages queued 12, received 0, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 11/0/0 Tx timeouts 0,0,10,0,0,0 last cancelled message type 30 dest 127 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 6579/779 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0dd14 Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server version 3.5.0-beta.2 (2023-02-08 11:47:09) Trigger: >> Finishing macro config.g, started by system Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 56.24, max time between full transfers: 42.1ms, max pin wait times: 868.7ms/2.6ms Codes per second: 3.23 Maximum length of RX/TX data transfers: 4656/912

@chrishamm Thanks, i managed to print screen the part of the logs when it happens, but i don't see anything weird on the logs...LOG.png

@phaedrux yes it goes away but I had some layershifts when the driver switched to spread cycle during prints, and keeping it spread cycle the entire time is louder, i should try since there was many update since I've tried having it switched, maybe also bad config, I don't know, switching was loud and sounded almost as what I experience now.

@chrishamm Thanks a lot, it's smooth now 😄 what's the work-around for prusa slicer please ? if it's an easy one 😄

@siam i think i've found the problem, i just tried stopping the daemon.g from running and it doesn't rebooted in an hour print... i think i'll have to shut it down during printing and reactivate it after.

@krohm-koala said in [3.3.0-rc2] M3-M5 gcode action:

hen you want to adjust your focus, it's a bit difficult duri

Does your laser have a Z-axis to adjust height? I'm planning for mine too - so eventually I'll do a test g-code that fine adjusts the laser height over multiple passes, and to than workout the offset from the top of the material being engraved/cut.

@krohm-koala - Thank you for your reply. I was just trying to point out that you should value your own time, even a day developing your own and you are basically valuing your time at very little per hour after material costs. Thats why we made them available for others. Take care.

Yes, i run a config_override, and i don't have any PID set in the config.g for my hotend, unfortunately, i'm not allowed to mention my hotend ^^

@dc42 Okay thanks 🙂 make sense

Hi @dc42, i've just installed 3.3.1Beta (it goes a lot better when you are doing it right 😂 ) and tested a thing, i've put an echo command at the end of my file, and it does not display it at all, even in the console, do you think it can be related to too much M291 or a certain type that made it crash ?

@Veti I have set the H and C but don't want to set the S in the config.g as when I calibrated my offset, it's not the same Everytime, that's why I want it stored with the M500 P31

Work is in progress to address this. The new PanelDue firmware will require RRF 3.1 or later, and it will be too large to run on the older version 1.x and some 2.x PanelDue boards.

@bearer that's maybe possible but to do that, i need to be able to adjust my Z value to have the right height, that's why i want to use babystepping ^^ but i'm trying to do it in a macro, and it doesn't work while in a macro

@dc42 Sorry for bothering you with this too (i know i'm a bit annoying sometimes 😂 ) what do you think about that ?

Oh ok, cool 🙂 thanks !

Yes i think it'll be easy to get around, i just search ease x) but with your suggestion, i think it'll will be easy to do a bit of meta to ask which type of filament you are loading one by one 🙂

@dc42 not under warranty and got it from a friend, so i don't cause much of a problem for the use i'm going to do, but if i cant try something, i wanted to know if there's something, thanks for your time ! 🙂

Nice find, and great that it is working now.

@beare i just seen that i haven't read far enough 😌 sorry for that 😄 wasn't clear, now it is, thanks.

@Krohm-Koala

thanks!