Currently studying maths at Vienna University of Technology
Hey,
I recently updated to firmware version 3.1 and I really like that the simulated print times are now displayed in webcontrol.
It would be cool if, after printing a file not simulated before, the actual printtime could be displayed as „simulated time“ in webcontrol.
@shirnschall After trying to get this to work for weeks, I found the error right after posting.
I used the old RRF 2
M106 F25000
to set the pwm frequency when it has changed to
M950 Q25000
in RRF 3.
The fans now work down to around 40% as expected.
@oliof I think I was using .6 or .7 with a long Bowden tube (as recommended on the duet PA website). I have since switched to a direct drive extruder (lgx ace), so this is really no longer an issue for me.
@phaedrux Thank you. Yes, I have looked at the documentation beforehand. I was unsure if I have to use the external 5V input on the duex if I am using the external 5V input on the duet itself.
To avoid confusion/errors I am now just using the external 5V on both the duex and the duet. Everything is working great.
@shirnschall After trying to get this to work for weeks, I found the error right after posting.
I used the old RRF 2
M106 F25000
to set the pwm frequency when it has changed to
M950 Q25000
in RRF 3.
The fans now work down to around 40% as expected.
Hi, I am trying to get a 120mm noctua nf f12 industrial fan (12V, 4pin pwm) to work as apart cooling fan. I have connected it as described in the documentation and as shown in the image below.
The problem is that the pwm control is not working correctly. The fan turns off at any level below approx. 80 and only turns on at 90 and above.
I have tested two different nf-f12 fans with the same result.
My setup:
I am currently using the duet2 wifi with the duex5 running at 24V with an external 5V supply. I am using RRF 3.4.1 (2022-06-01) and in my config.g I configure the fan using
M950 F2 C"!fan2" ; fan 2 part cooling fans nf-f12. output is inverted for 4-wire fan
M106 P2 C"Adv-Part-Cooling" S0 F25000 ; set fan 1 name, value, PWM signal inversion and frequency. Thermostatic control is turned off
I have also tried adding a 10k Ohm pullup between the pwm input of the fan and +5V as mentioned here: https://forum.duet3d.com/topic/25179/wiring-configuration-of-standard-4-pin-pwm-fans-on-duet-3-mb6hc
Increasing the B-value as mentioned here https://forum.duet3d.com/topic/25127/configuring-a-pwm-4-wire-fan causes the fan to spinn up briefly before spinning back down again.
Hi,
has anyone tried printing the perimeter or even just the outer most perimeter with half the layer height of the other features?
If done in the following order it should work shouldn’t it?
Sorry if this is already a slicer feature. I was unable to find it.
@dc42 Thank you for the clarification 
I have already updated to the new version.
@phaedrux Hi,
yes I am using DWC 3.4.0 as well.
Please download the gcode from github as it was too large to upload here.
Here is the M122 output (just in case).
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-9T6BU-FG3SN-6JKDJ-3S86N-98ZHF
Used output buffers: 3 of 24 (24 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 76252 of which 24 recycled
Never used RAM 11792, free system stack 118 words
Tasks: NETWORK(ready,15.5%,232) HEAT(notifyWait,0.0%,332) Move(notifyWait,0.0%,305) DUEX(notifyWait,0.0%,24) MAIN(running,84.3%,466) IDLE(ready,0.2%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:10:23 ago, cause: software
Last software reset at 2022-07-24 00:59, reason: User, GCodes spinning, available RAM 8144, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Step timer max interval 0
MCU temperature: min 39.4, current 41.8, max 42.1
Supply voltage: min 1.0, current 24.4, 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 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min 0
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min n/a
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min 0
Driver 10:
Driver 11:
Date/time: 2022-07-24 01:10:14
Cache data hit count 4294967295
Slowest loop: 69.92ms; fastest: 0.11ms
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 1.9ms, write time 120.6ms, max retries 0
=== Move ===
DMs created 83, segments created 6, maxWait 81367ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 89, completed 89, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 59], CDDA state -1
=== AuxDDARing ===
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 2 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock 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
Code queue is empty
=== DueX ===
Read count 1, 0.10 reads/min
=== Network ===
Slowest loop: 233.93ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 of 8
- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address 84:f3:eb:41:aa:d2
WiFi Vcc 3.42, reset reason Power up
WiFi flash size 4194304, free heap 23920
WiFi IP address 192.168.0.111
WiFi signal strength -57dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
Hi,
I recently noticed that the print status percent is extremely off for some prints and I am unsure what this percentage is based on. I tend to run a simulation before starting the print to get an accurate print time estimate (Although the slicer estimation is very close for my printer). I have attached screenshots of two different prints, both with the issue described above. I guess this statistic it is based on "File Progress" as it is very wrong for all other stats available (layers, filament usage, slicer estimate, and simulation). I am not sure if there is a better way for doing this.
I am using a duet 2 wifi with firmware version 3.4.0.
@oliof I think I was using .6 or .7 with a long Bowden tube (as recommended on the duet PA website). I have since switched to a direct drive extruder (lgx ace), so this is really no longer an issue for me.
@sonderzug @oliof Thank you guys for your input . However, I guess I need to think a bit more about this topic to fully understand the relation between Arachne/ variable-extrusion-width and pressure advance.
I originally thought about possible issues (not so much in practice but more from a theoretical point of view) as I ran into print speed reductions when using large PA values with low extruder jerk settings in the past. I have also noticed clicking in the extruder (without Arachne) as the extruder constantly changes direction.