@Arminas In other word, is there a jerk setting that is good for both slower and faster printing speed, and for both high and low resolution stl's?
Best posts made by Arminas
-
RE: Jerk settings at different speeds
-
RE: does not completely finish the last layer of the print 3.5.0-b4
@dc42 M122:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.4 (2023-06-08 23:40:14) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: U51SX-F396U-D65J0-40KMW-M603Z-ZFNKD
Used output buffers: 1 of 40 (18 max)
=== RTOS ===
Static ram: 102996
Dynamic ram: 122548 of which 0 recycled
Never used RAM 16512, free system stack 188 words
Tasks: NETWORK(1,ready,46.8%,240) HEAT(3,nWait,0.1%,327) Move(4,nWait,0.0%,358) CanReceiv(6,nWait,0.0%,939) CanSender(5,nWait,0.0%,337) CanClock(7,delaying,0.0%,342) TMC(4,nWait,3.7%,116) MAIN(1,running,46.6%,704) IDLE(0,ready,0.1%,29) AIN(4,delaying,2.6%,266), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 02:19:32 ago, cause: power up
Last software reset at 2023-07-25 21:46, reason: User, Gcodes spinning, available RAM 13112, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 8372702, completed 8372702, timed out 0, errs 0
MCU temperature: min 34.5, current 34.8, max 41.0
Supply voltage: min 23.9, current 24.0, max 24.0, 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 0, read errors 0, write errors 0, ifcnt 11, reads 40203, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 40203, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 40204, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 40203, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 40203, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 40203, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 40203, writes 10, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2023-08-21 22:03:31
Cache data hit count 4294967295
Slowest loop: 7.11ms; fastest: 0.16ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.6ms, 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, ebfmin 0.00, ebfmax 0.00
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 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
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
=== CAN ===
Messages queued 75351, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 41863/0/0
Tx timeouts 0,0,41862,0,0,33487 last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 15.28ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Interface state: active
Module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
Firmware version 1.26
MAC address f0:08:d1:03:81:a2
Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 24792
WiFi IP address 192.168.32.177
Signal strength -45dBm, channel 0, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0 -
RE: Extruder randomly starts spinning backwards
@jay_s_uk now that makes more sense, thank you!
Latest posts made by Arminas
-
RE: Toolboard 1LC troubles
@droftarts Is there a way I can check if the TB 1LC is actually permanently damaged or not?
-
RE: Toolboard 1LC troubles
@droftarts Okay, I might need some more explanation on this I have grounded the frame to the power socket's ground pin. As I was assembling the printer, there where an instructions to ground the bed to the PSU ground, and from PSU ground to power socket ground pin, so bed is grounded like per instructions.
-
RE: Toolboard 1LC troubles
@droftarts Okay. So as I understand, I had a short circuit due to static charge and it damaged the 1LC. I have grounded my hotend with simple wire to the printers frame. Frame is grounded. I checked the continuity between hotend and power sockets ground pin. But I still can see a spark after I touch the nozzle with tweezers. How can it be? Building's ground is not working?
-
RE: Toolboard 1LC troubles
@dc42 Hi. I have purchased a new TB 1LC to try to swap it and see if the problem is still there. And I noticed that one component on old and new board is different. Both boards are v1.3, both with 202305-xxx code. Could this be an issue?
image url)
-
RE: Toolboard 1LC troubles
@Phaedrux @dc42 @oliof Unfortunately, I think I have recreated the main issue with my other printer with exactly the same setup.... I have touched the nozzle with tweezers and I think something shorted due to static discharge. Blower fan immediately started to blow at 100% speed instead of 20%.. And now I have "hotend offline" in my DWC...
"On the v1.3 toolboard the mounting screw holes are all grounded via 100K resistors to provide a path to ground for any static build up in the extruders, assuming the toolboard is mounted to the extruder" - so if any of 1LC mounting bolts touches the extruder motor, I can simply wire a hotend with one of the mounting bolts?
Also, am I right that I can ground hotend to any duet GND pin? I would also ground the hotend of my Modix printers, but there is no toolboard. So I would connect the wire from hotend to Duet2 Wifi ground pin.
-
RE: Toolboard 1LC troubles
@Phaedrux one of IO is used for BLTouch, I can't start the print without it. Maybe it's not a big deal if I leave this one connected?
-
RE: Toolboard 1LC troubles
@Phaedrux Blue - cold, Red - hot (I don't feel comfortable touching it more than 3 seconds). And extruder motor is very very hot
-
RE: How to properly ground hotend?
@droftarts @EasyTarget so which option is better - hotend or extruder stepper?
Would it additionally help if I would print hotend parts in ABS ESD?
-
How to properly ground hotend?
Hello, I have 4 printers that makes a spark once I touch them by hand or if I touch the nozzle with tweezers. I guess it is not okay, so I am thinking where is the issue? All printers have grounded beds.