Posts made by goury

᠌᠌ ᠌᠌ ᠌᠌ ᠌᠌ ᠌᠌️️ ᠌᠌ ᠌᠌ ᠌᠌ ᠌᠌️️
️️️️️️
️️️️️️
᠌᠌ ᠌᠌ ᠌᠌ ᠌᠌️️️️️
᠌᠌ ᠌᠌ ᠌᠌ ᠌᠌ ᠌᠌ ᠌᠌ ᠌᠌ ᠌ ᠌᠌ ᠌᠌ ᠌᠌ ᠌️️️
᠌᠌ ᠌᠌ ᠌᠌ ᠌᠌ ᠌᠌ ᠌᠌ ᠌᠌ ᠌ ᠌᠌ ᠌᠌ ᠌᠌ ᠌ ᠌᠌ ᠌ ᠌᠌ ᠌᠌ ᠌᠌️

So we have pressure advance compensation to compensate for the delay in extruding plastic, what do we have for the same issue with extruding cooling air?

Problem: when a machine starts spinning a motor, the result comes with a measurable and predictable delay.
The problem with extruding plastic is addressed and it is called "pressure advance compensation" or something like that.
Another problem: actually, it's the same problem, when a machine gets a command to start a cooling fan, there's a very noticeable delay for the fan to ramp up and then for the air to actually come out and start cooling stuff.

Question: does a solution to this problem exist?
If so, what's its name and what am I supposed to do to turn a fan a second or two in advance of a bridge?
I am failing to find anything, search engines nowadays are not very helpful.
And I'm a bit tired of manually editing my gcode files.

@Phaedrux it was 300, I've set it to 500

Subj: Machine suddenly started moving first one Z axis during first homing move in reverse

At first I was to ask "what do I do".
But then I've tried a few more things and it's homing okay now.

Given:
Voron 2.4, was tuned and working perfectly for a year.
Updated RRF 3.3 → 3.4.5.
Worked for a day, now it fails to home.
For some some mysterious reason it started moving one Z axis down when probing first point.
This is consistent behaviour, happens every single time except first pass.
Obviously, deviation is so high it can never home itself.

Tried:
Reverting to 3.4.4, 3.3, didn't change a thing.
Making it go super slow, no difference.
Raising probe offset, no difference.
Adding S-1 to probe points, refuses to home.
Adding S4 to probe points, refuses to home.
What was I thinking.

What worked:
Increased Z current, decreased Z acceleration, tightened sloppy belt.

Morals of this story:
Software developers are smarter than they think.

Video evidence:
https://youtu.be/ThYAQc2Bo0c

@phaedrux

So now I know what to fix in the config when a new duet arrives
Thanks.

Email message is sent.

@phaedrux
says

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Invalid Z probe index
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 283C

Strange, Z probe does work just fine and heater 0 should be at 50%

14.12.2021, order #77200

config.g

; Configuration file for Duet3 Mini5+ with Mini2+ expansion (firmware version 3.3 or newer)
; executed by the firmware on start-up

; General preferences
M111 S0                     ; Debugging off
G21                         ; Work in millimetres
G90                         ; Send absolute coordinates...
M83                         ; ...but relative extruder moves

M669 K1                     ; Select CoreXY mode
M564 S1 H1                  ; Forbid axis movements when not homed
;M918 P2 R6 C30 E-4 F200000 ; Fysetc 12864 display

; Network
M550 PDaikarasu             ; Set machine name
M551 P"[REDACTED]"             ; set password
M552 P0.0.0.0 S1            ; enable network and acquire dynamic address via DHCP
M586 P0 S1                  ; Enable HTTP
M586 P1 S0                  ; Disable FTP
M586 P2 S0                  ; Disable Telnet

; --- Z Drive map ---
;     _______
;    | 1 | 2 |
;    | ----- |
;    | 0 | 3 |
;     -------
;      front
;
; (looking at the printer from the top)

; Drive directions
M569 P0 S1 ; A
M569 P1 S1 ; B
M569 P2 S1 ; E
M569 P4 S0 ; Z0
M569 P3 S1 ; Z1
M569 P6 S0 ; Z2
M569 P5 S1 ; Z3

; Motor mapping and steps per mm
M584 X1 Y0 E2 Z3:4:5:6
M350 X32 Y32 Z32 E16 I1         ; Use 1/16 microstepping with interpolation everywhere
M92 X160 Y160 Z800                ; Set XYZ steps per mm (1.8deg motors)
M92 E410                        ; Set Extruder steps per mm

; Drive currents
M906 X1000 Y1000 Z1000 E600     ; XYZ and E current
M906 I20                        ; Idle current percentage
M84 S120                        ; Idle timeout

; Accelerations and speed
M98 P"/macros/print_scripts/setup_printing.g"

; Axis travel limits
M208 X0 Y0 Z0 S1                ; Set axis minima
M208 X340 Y350 Z330 S0          ; Set axis maxima

; Endstops
M574 X2 S1 P"^!io0.in"          ; Xmax endstop on hall effect board
M574 Y2 S1 P"^!io1.in"          ; Ymax endstop on hall effect board
M574 Z1 S1 P"^io2.in"           ; Zmin endstop

; Z probes
M558 K0 P8 C"^io3.in" T18000 F120 H5 A5 S0.01 R0.2
G31 K0 P500 X0 Y25 Z1.70        ; Don't really care about inductive probe Z offset
;M558 K1 P8 C"^io6.in" T18000 F240:60 H2 A10 S0.005 R0.2
G31 K1 P500 X0 Y0 Z0.50         ; Z switch offset (if positive, greater value = lower nozzle. if negative, more negative = higher nozzle)

; Bed leveling
M671 X-60:-60:360:360 Y-10:370:370:-10 S20  ; Define Z belts locations (Front_Left, Back_Left, Back_Right, Front_Right)
M557 X25:325 Y25:320 S25                    ; Define bed mesh grid (inductive probe, positions include the Y offset!)

; Bed heater (dual thermistor setup)
M308 S0 P"temp1" Y"thermistor" T100000 B3950 A"Bed Heater"  ; configure sensor 0 as thermistor on pin temp0 (heater sensor)
;M308 S2 P"temp0" Y"thermistor" T100000 B3950 A"Bed Plate"  ; configure sensor 2 as thermistor on pin temp1 (mic6 sensor)
M950 H0 C"out0" T0 Q10                                      ; create bed heater output on out0 and map it to sensor 2 (mic6 sensor). Set PWM frequency to 10Hz
M140 P0 H0                                                  ; Mark heater H0 as bed heater (for DWC)
M143 H0 P0 T0 A2 S115 C0                                    ; Regulate (A2) bed heater (H0) to have pad sensor (T0) below 115°C. Use Heater monitor 0 for it
;M143 H0 P2 T0 A1 S125 C0                                   ; Shut off (A1) bed heater (H0) if pad sensor (T0) exceeds 125°C. Use Heater monitor 2 for it
M143 H0 S110                                                ; Set bed heater max temperature to 110°C, use implict monitor 0 which is implicitly configured for heater fault
M307 H0 B0 S0.5                                             ; disable bang-bang mode and set PWM to 60% to avoid warping

; Hotend heater
;M308 S1 A"Hotend" P"temp2" Y"pt1000"                       ; Hotend is 2-wire PT1000 on pin temp2
M308 S1 A"Extruder" P"temp2" Y"thermistor" T100000 B3950    ; Hotend is 2-wire PT1000 on pin temp2
M950 H1 C"out1" T1                                          ; Hotend heater is connected to out1
M307 H1 B0 S1.00                                            ; disable bang-bang mode for heater and set PWM limit
M143 H1 S350                                                ; Set temperature limit for heater 1 to 350C

; MCU sensors
M308 S3 Y"mcu-temp" A"MCU"
M308 S4 Y"drivers" A"Drivers"

;M308 S6 P"spi.cs2" Y"rtd-max31865" F60 A"Z Switch"

; Fans
M950 F0 C"out5" Q250                ; Create fan 0 (hotend) on pin out3 and set its frequency
M106 P0 S1 H1 T50 C"Hotend"         ; Configure fan 0: Thermostatic control is turned on, based on sensor #1
M950 F1 C"out6" Q250                ; Create fan 1 (cooling) on pin out4 and set its frequency
M106 P1 S0 H-1 C"Cooling"           ; Configure fan 1: Thermostatic control is turned off
;M950 F2 C"out5" Q30                ; Create fan 2 (electronics bay) on pin out5 and set its frequency
;M106 P2 S0.25 H1 T50 C"Bay"        ; Run the fans at 25% if the hotend is over 50C
;M106 P2 S0 H-1 C"Bay"              ; (temporary manual setup)
;M950 F3 C"out6" Q30                ; Create fan 3 (chamber) on pin out6 and set its frequency
;M106 P3 S1 H2 T65 C"Chamber"       ; Configure fan 3: Thermostatic control is turned on, based on sensor #2 (mic6 temp)
;M106 P3 S0 H-1 C"Chamber"          ; (temporary manual setup)

; LEDs
;M950 F4 C"out2"                     ; Create fan 4 (top leds) on pin out2
;M106 P4 S255 B0 H-1 C"Top Lights"

; Tools
M563 P0 D0 H1 F1                    ; Define tool 0 using fan 1 for M106
G10 P0 X0 Y0 Z0                     ; Set tool 0 axis offsets
G10 P0 R0 S0                        ; Set initial tool 0 active and standby temperatures to 0C

; Misc
;M572 D0 S0.075                      ; Pressure Advance
M572 D0 S0.01                       ; Pressure Advance
M592 D0 A0.015 B0.0012 L0.2         ; Non-linear extrusion
M376 H10                            ; Fade mesh out compensation over 10mm Z
M912 P0 S-8.5                       ; MCU temp calibration

; DAA tuning (you will need to change this for your slicer)
;M593 F26.6                          ; Cura 4.5 stock profile @ 40mm/s outer printing speed
M593 F42.5                          ; PrusaSlicer @ 40mm/s outer perimeter

M501                                ; load config-override.g
T0                                  ; select tool 0

config-override.g

; config-override.g file generated in response to M500 at 2022-01-18 13:14
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 R0.186 C1391.931:1391.931 D19.45 S0.60 V24.1 B0 I0
M307 H1 R2.762 C179.113:179.113 D4.64 S1.00 V24.1 B0 I0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00

macros/print_scripts/setup_printing.g

; called to set up current, speed & accel for printing moves

M566 X600 Y600 Z30 E8000        ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z3000 E15000 ; Set maximum speeds (mm/min)
M201 X1200 Y1200 Z250 E1800     ; Set maximum accelerations (mm/s^2) 
M204 P1500 T2000                ; Set printing acceleration and travel accelerations

M913 X100 Y100 Z100             ; restore current to 100%

then I move it a bit and it says

Driver 0: position -32000, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 12384, writes 2, timeouts 0, DMA errors 0
Driver 1: position 0, standstill, SG min/max 0/12, read errors 0, write errors 0, ifcnt 11, reads 12384, writes 2, timeouts 0, DMA errors 0

I am confident that it's driver 0 that doesn't move what's attached to it and driver1 works just fine

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: B0QUJ-9196U-D65J0-40KM4-ML03Z-ZPP5P
Used output buffers: 3 of 40 (11 max)
=== RTOS ===
Static ram: 102724
Dynamic ram: 100980 of which 0 recycled
Never used RAM 40000, free system stack 204 words
Tasks: NETWORK(ready,26.9%,245) ETHERNET(notifyWait,0.4%,554) HEAT(notifyWait,0.0%,348) Move(notifyWait,0.1%,338) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(delaying,1.1%,116) MAIN(running,70.0%,426) IDLE(ready,0.6%,29) AIN(delaying,0.8%,264), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:26 ago, cause: power up
Last software reset at 2022-01-19 12:38, reason: User, GCodes spinning, available RAM 40000, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 26735, completed 26734, timed out 0, errs 0
Step timer max interval 1469
MCU temperature: min 9.8, current 14.9, max 18.3
Supply voltage: min 24.1, current 24.1, max 24.2, 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
Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 2350, writes 9, timeouts 0, DMA errors 0
Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 2350, writes 9, timeouts 0, DMA errors 0
Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 2350, writes 9, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 2350, writes 9, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 2350, writes 9, timeouts 0, DMA errors 0
Driver 5: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 2350, writes 9, timeouts 0, DMA errors 0
Driver 6: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 2350, writes 9, timeouts 0, DMA errors 0
Date/time: 2022-01-19 12:54:50
Cache data hit count 44439563
Slowest loop: 5.01ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
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, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.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
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
Code queue is empty.
=== CAN ===
Messages queued 235, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 132/0/0
Tx timeouts 0,0,131,0,0,102 last cancelled message type 30 dest 127

=== Network ===
Slowest loop: 5.24ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 2 2 2 2 2 0 0 0

UPD: already ordered a new one from another store to have it faster.
Can I opt for return instead of repair/replacement?

Bought a 3 mini 5+ from filastruder.
It worked okay for a day, but this night driver0 stopped functioning during a print.
After power cycling the board it worked for about 15 minutes and then failed again.
Now it doesn't work regardless of power cycling.
I did try swapping motors, every motor connected to driver0 doesn't spin.
Motor is getting power, but just doesn't spin at all.

What should I do now?

@dc42 interpolation isn't real stepping.
It's better than not having it, but it's 0,0125 mm accuracy versus 0,00078125 mm accuracy.
I sure don't need 0,001 mm accuracy for my application because material itself can't be this much accurate, but 0,01 can some times be visible (this is why I switched to full 256 microsteps.
I've tried 1/64 before switching to 1/256, it did improved some surfaces but not as much as 1/256 did.

What's about Duet 3?
Does it have the same issue or should I start saving for an upgrade?

@Phaedrux
So I did M350 X16 Y16 Z16 E256 I1
And now I have Hiccups: 0, FreeDm: 156, MinFreeDm: 104, MaxWait: 405246ms

Though It is very sad that 256 microstepping isn't really usable =(

@Phaedrux
Right now M122 says Hiccups: 128302, FreeDm: 156, MinFreeDm: 116, MaxWait: 2417589ms
It this a lot or not enough to worry?

I don't think I can run it right after the stall as it doesn't respond to anything.

@JamesM it's 400mm/s in config and it works reliably.
Should I put m122 on every second line or is there a shortcut?

@bot upgraded to 2.05.1, same thing is happening during different prints.

@matt3o my top speed is set to 400mm/s and this machine can do this.
Not very precisely on XY plane, but its Z is driven by three beefy motors, so there is no problems.
Also, since it homes at top, it otherwise takes too much time for head to move all the way down to the bed.
Time that I don't like wasting.

@Danal config.g
I like it moving fast during retraction. Ringing won't happen in those phases, but any extra delay can cause thermoplastic to dip out of the nozzle.
Machine doesn't skip any steps at 400mm/s unless there's something in its way.
Whenever there's a possibility of something to be in its way it moves under 150mm/s.
If only I knew what parameters to change.
To me it looks like regular G1 moves.
My goal is not to take lines from gcode but to fix firmware so it won't freeze ever.
Having a freeze or two per every new design (yes, this is how often this is happening per 50 grams of material) is very frustrating and counterproductive.

Board: Duet Ethernet 1.02 or later
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.05 (2019-12-13b1)

Tried few times, rebooted few times.
It freezes at the same exact spot in this gcode file, around line 2413
Dice tray fast.gcode
I then cut its head and guess what — it freezes at the same spot, line 24 this time
Dice tray fast resume from 0.675.gcode

Motors stop (but are still powered), web intefrace disconnects, panel due seems to be able to read temperatures but machine doesn't react to anything but cutting off its power.
It doesn't seem to be overheating, thankfully.

What should I do?
How do I diagnose this deeper and further?
How do I avoid this in future?
Do you need any extra information from me?

PS: dice tray model of this gcode is under GNU GPL v3, sources are provided on request

@burtoogle Cura also does lot things badly, like nonexistent nozzle wipe or just forgetting/resetting some settings while lying about it in the interface.
It's just too buggy there's no way I can use it and not hate myself every moment I do.
You can't even change your nozzle width in default profile without duct tape in latest stable version.
And it is like this for a very long time (since 3.4 or 3.5 IIRC).

So we have this feature that compensates springiness of filament, called "pressure advance".
How's about we do something like this for cooling?

The problem: fans take time to spin up and air pressure takes time to advance.
The solution: look ahead for fan powering up command and power it up early.
I believe it's better to be done in firmware than hacked into GCODE, because it is machine-specific.

My case: I found that my fans take about 1.8 seconds to spin up, resulting in PLA bridges sagging in the beginning if I do nothing to my GCODE.
Yes, it's almost a second before it spins up from 40% to 80% and then some more before it reaches full power.
It is very much noticeable.

When requesting reprapfirmware.org it serves cert for www.reprapfirmware.org.
Fix this please.

I'd also love if you consider dropping this www subdomain, it's 2019 already.