It's out! RepRapFirmware 2.0 and 1.21.1 released

dc42

@timcurtis67 said in It's out! RepRapFirmware 2.0 and 1.21.1 released:

Thank you David. I will try that tonight after I try re-inserting the SD card. I'm hoping that I don't have a bad SD card detect pin (maybe it's been that way all along). The more I think about it the more it seems like that is the issue.

What would be the "work around" if that turns out to be the case?

Here is a photo showing the position of the CD pin.

alt text

Take a look at it, using magnification if possible, and see whether it looks properly soldered to the pad or is just resting on top of it.

If the CD pin does cause issues then in recent firmware versions you should see error messages telling you that the SD card has been removed with open files on it.

timcurtis67

@dc42 Thank you, I will check it out tonight and advise.

demonio669

dc42, what happens if you have a 0 bytes config.g ? should the firmware run config.g.bak ?

I have several times a 0 bytes config.g after power-off cycle

BMMal

To expand further on my issue of not getting responses, it seems that DWC is somehow getting out of sync but not disconnecting ie, a print was started and it did not automatically go to the Print Status screen. DWC still indicated that the machine was connected. I made a change to config.g, the file got updated (confirmed by looking after saving) and DWC asked if I wanted to reboot as if the machine was not printing even though it was. Manually going to the status page, it did not appear that the machine was printing. Refreshing the browser did however update properly.

Knaudler

Hello

little Problem with
Web Interface Version: 1.21.1
there is only 1 Fan slider
on 1.21 you have sliders for all 3 PWM Fans (if activated)

thanks

Ingo (Knaudler)

timcurtis67

@dc42 I got my install working perfect now. I tried taking the SD card out a few times but that made no difference so I copied the firmwares to my SD card and activated the installs with my PanelDue. It worked great that way. No need for USB interfacing.

On a side note I did notice when I was having my issues with the first install I saw that the blue LEDs were lit up in the Wifi module but not blinking and they were barely lit. If that means anything?

I must have gotten a bad install on one of the firmwares the first time but all is well now.

Thank you for the help!

Catalin_RO

Using it on WorkBee since released. No problems so far!

ChrisP

I have some Duest 06 that I'm still having the same issues with as was mentioend previously in 1.20 with regards to not using static IPs (https://forum.duet3d.com/topic/3508/firmware-1-20-released/75).

To confirm, if a static IP isn't provided using M552 then the Duet will work fine and can be controlled over USB and/or a PanelDue as long as the ethernet is disconnected. Before plugging in the ethernet, this is the output of M112:

=== Diagnostics ===
RepRapFirmware for Duet version 1.21.1 running on Duet 0.6
Used output buffers: 1 of 16 (2 max)
=== System ===
Static ram: 44628
Dynamic ram: 41348 of which 40 recycled
Stack ram used: 2920 current, 4400 maximum
Never used ram: 7888
=== Platform ===
Last reset 00:00:07 ago, cause: power up
Last software reset time unknown, reason: Stuck in spin loop, spinning module Network, available RAM 7080 bytes (slot 2)
Software reset code 0x2041 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0440f80f, BFAR 0xe000ed38, SP 0x20087cdc
Stack: 000c4127 00000001 fffffff9 20087b98 20087c41 80000000 00000001 2007a524 000ac0bd 000ac0bc 61000000 000000b5 00000004 000bdcd9 000afa53 0000003a 00000001 00000006 2007a900 20087d56 2007aa40 20087d90 20087d50 00000023
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 30.3, current 36.6, max 36.6
Date/time: 1970-01-01 00:00:00
Slowest loop: 1.16ms; fastest: 0.10ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 100, MinFreeDm 100, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Free connections: 16 of 16
Free transactions: 24 of 24
Locked: 0, state: 2, listening: 0, 0, 0
ok

Immediately after plugging in the ethernet, this is the output:

=== Diagnostics ===
RepRapFirmware for Duet version 1.21.1 running on Duet 0.6
Used output buffers: 1 of 16 (7 max)
=== System ===
Static ram: 44628
Dynamic ram: 41348 of which 40 recycled
Stack ram used: 2920 current, 5128 maximum
Never used ram: 7160
=== Platform ===
Last reset 00:00:48 ago, cause: power up
Last software reset time unknown, reason: Stuck in spin loop, spinning module Network, available RAM 7080 bytes (slot 2)
Software reset code 0x2041 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0440f80f, BFAR 0xe000ed38, SP 0x20087cdc
Stack: 000c4127 00000001 fffffff9 20087b98 20087c41 80000000 00000001 2007a524 000ac0bd 000ac0bc 61000000 000000b5 00000004 000bdcd9 000afa53 0000003a 00000001 00000006 2007a900 20087d56 2007aa40 20087d90 20087d50 00000023
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 36.6, current 39.5, max 39.6
Date/time: 1970-01-01 00:00:00
Slowest loop: 3.99ms; fastest: 0.10ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 100, MinFreeDm 100, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Free connections: 16 of 16
Free transactions: 24 of 24
Locked: 0, state: 3, listening: 0, 0, 0
ok

Shortly after, however, everything locks up and neither the serial over USB or PandelDue respond. After unplugging the ethernet, and waiting a short while (without power-cycling or resetting) I can issue an M122 again, and this is the response:

=== Diagnostics ===
RepRapFirmware for Duet version 1.21.1 running on Duet 0.6
Used output buffers: 1 of 16 (2 max)
=== System ===
Static ram: 44628
Dynamic ram: 41348 of which 40 recycled
Stack ram used: 2920 current, 4400 maximum
Never used ram: 7888
=== Platform ===
Last reset 00:00:12 ago, cause: software
Last software reset time unknown, reason: Stuck in spin loop, spinning module Network, available RAM 7884 bytes (slot 0)
Software reset code 0x2041 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0440f80f, BFAR 0xe000ed38, SP 0x20087e64
Stack: 000c4127 00000001 fffffff9 89cdcd64 20087ebc 20070ff4 00000001 20087ebc 000aac3d 000a9c2c a1000000 20073788 2007a868 0000012c 00000113 00000000 20073778 200737b4 0000011f 2007add8 000000f0 00000045 81cdcd89 20073778
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 39.3, current 39.9, max 40.3
Date/time: 1970-01-01 00:00:00
Slowest loop: 1.17ms; fastest: 0.10ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 100, MinFreeDm 100, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Free connections: 16 of 16
Free transactions: 24 of 24
Locked: 0, state: 2, listening: 0, 0, 0
ok

ChrisP

I have just tried the same on an 85 board and can confirm that it does the same. Dropping back down to 1.19 makes everything work again (minus the new features ofc).

dc42

@demonio669 said in It's out! RepRapFirmware 2.0 and 1.21.1 released:

dc42, what happens if you have a 0 bytes config.g ? should the firmware run config.g.bak ?

Only in the version 2.0 release firmware.

dc42

@knaudler said in It's out! RepRapFirmware 2.0 and 1.21.1 released:

Hello

little Problem with
Web Interface Version: 1.21.1
there is only 1 Fan slider
on 1.21 you have sliders for all 3 PWM Fans (if activated)

thanks

Ingo (Knaudler)

With DWC 1.21.1 and RRF 2.0/1.21.1 you are able to control all fans that are not set up as thermostatically controlled.

dc42

@chrisp said in It's out! RepRapFirmware 2.0 and 1.21.1 released:

I have some Duest 06 that I'm still having the same issues with as was mentioend previously in 1.20 with regards to not using static IPs (https://forum.duet3d.com/topic/3508/firmware-1-20-released/75).
To confirm, if a static IP isn't provided using M552 then the Duet will work fine and can be controlled over USB and/or a PanelDue as long as the ethernet is disconnected. Before plugging in the ethernet, this is the output of M112:

I have tried to reproduce this issue before several times, without success. But if you make your config.g file available, I'll try once again.

Knaudler

@dc42 said in It's out! RepRapFirmware 2.0 and 1.21.1 released:

@knaudler said in It's out! RepRapFirmware 2.0 and 1.21.1 released:

Hello

little Problem with
Web Interface Version: 1.21.1
there is only 1 Fan slider
on 1.21 you have sliders for all 3 PWM Fans (if activated)

thanks

Ingo (Knaudler)

With DWC 1.21.1 and RRF 2.0/1.21.1 you are able to control all fans that are not set up as thermostatically controlled.

could I change this behavior in reprap.htm ?
unhidden ?

thanks

ChrisP

@dc42

@dc42 said in It's out! RepRapFirmware 2.0 and 1.21.1 released:

@chrisp said in It's out! RepRapFirmware 2.0 and 1.21.1 released:

I have some Duest 06 that I'm still having the same issues with as was mentioend previously in 1.20 with regards to not using static IPs (https://forum.duet3d.com/topic/3508/firmware-1-20-released/75).
To confirm, if a static IP isn't provided using M552 then the Duet will work fine and can be controlled over USB and/or a PanelDue as long as the ethernet is disconnected. Before plugging in the ethernet, this is the output of M112:

I have tried to reproduce this issue before several times, without success. But if you make your config.g file available, I'll try once again.

Thanks, that would be great!
Below are two config file from two very different printers one uses an 06 board, the other uses an 85 board - the problem on both boards is the same. With any FW later than 1.19, the ethernet connectivity is broke. If a static IP isn't specified then the board constantly boot loops. If a staic IP is defined, the boards will boot but I still can't access the web interface either by printer name or IP.
The first is my own printer that I often take into work and use there. Its a pretty standard setup and uses the 06 board with a PanelDue:
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Communication and General
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M111 S0 ; Debug off
M555 P2 ; Set output to look like Marlin

M550 PStarttEx ; Machine name
M551 Preprap ; Machine password (used for FTP)
M540 P0x36:0x18:0x70:0x4E:0xDB:0x00 ; MAC Address

;M552 P<removed> ; IP address
M552 P0.0.0.0 ; IP address
M553 P255.255.255.0 ; Netmask

M586 P0 S1 R80 ; Enable HTTP/HTTPS
;M586 P1 S1 R21 ; Enable FTP/SFTP
;M586 P2 S1 R22 ; Enable Telnet/SSH

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Workmode
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Motor Configuration
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M569 P0 S0 ; Drive 0 (x) goes backwards
M569 P1 S1 ; Drive 1 (y) goes forwards
M569 P2 S0 ; Drive 2 (z) goes backwards
M569 P3 S0 ; Drive 3 (e) goes backwards
M906 X900 Y900 Z900 E900 ; Set motor currents (mA)

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Axis Configuration
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M574 X1 Y1 Z2 S1 ; X and Y endstop at min end, Z at max end, active high
M92 X80.0 Y80.0 Z1600.0 ; Set axis steps/mm (GT2)

M201 X2000 Y2000 Z100 E10000 ; set max accelerations (mm/s^2)
M203 X18000 Y18000 Z600 E3600 ; set max feedrates (mm/min)
M204 P10000 T10000 ; set max print and travel accelerations (mm/s^2)
M566 X600 Y600 Z30 E600 ; set max inst. speed change (jerk) (mm/min)

;M201 X2000 Y2000 Z100 E5000 ; set max accelerations (mm/s^2)
;M566 X600 Y600 Z30 E120 ; set max inst. speed change (jerk) (mm/min)

M208 X155 Y125 Z131.45 ; set axis maxima
M208 X-19.5 Y-1.5 Z0 S1 ; set axis minima (make X=0 and Y=0 the edge of the bed after homing)

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Temperature Sensor Parameters
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M305 P0 R4700 T100000 ; Bed
M305 P1 R4700 T100000 B4725 C7.06e-8 ; Hot end

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Tool Definitions
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M563 P0 D0 H1 ; Define tool 0
G10 P0 S200 R0 ; Set tool 0 operating and standby temperatures
; Gain (A) | Time constant (C) | Dead time (D)
M307 H1 A437.5 C48.6 D4.6 B0 ; Model based hotend temperature control from an autotune (over-ridden in config-override.g)

M92 E410 ; Set extruder steps per mm

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Z Probe
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M558 P0 ; Z probe is not present

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Axis Compensation
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M556 S78 X0 Y0 Z0 ; Axis compensation

;M581 E1 S1 T1 C1 ; Execute pause script when triggered and currently printing

M501 ; run config-override.g

The second has 5 axes and a past extruder and uses an 85 board:
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Configuration file for Paster
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Communication and General
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M111 S0 ; Debug off
M555 P2 ; Set output to look like Marlin

M550 PPasteEx ; Machine name
M551 PPreprap ; Machine password
M540 P0xBE:0xEF:0xDE:0x76:0xFE:0xED ; MAC Address

;M552 P<removed> ; IP address
M552 P0.0.0.0 ; IP address
M553 P255.255.255.0 ; Netmask

M586 P0 S1 R80 ; Enable HTTP/HTTPS
;M586 P1 S1 R21 ; Enable FTP/SFTP
;M586 P2 S1 R22 ; Enable Telnet/SSH

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Workmode
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Motor Configuration
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M569 P0 S1 ; X Drive 0 goes forwards
M569 P1 S1 ; Y Drive 1 goes forwards
M569 P2 S0 ; Z Drive 2 goes backwards
M569 P3 S1 ; U Drive 3 goes forwards
M569 P4 S1 ; V Drive 4 goes forwards
M569 P5 S1 ; E0 Drive 5 goes forwards
M906 X800 Y800 Z1600 U1000 V1200 E1000 ; Set motor currents (mA)
M906 I50 ; Set motor idle factor

M584 X0 Y1 Z2 U3 V4 E5

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Axis Configuration
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M574 M574 X1 Y1 Z2 S0 ; end stops
M574 V1 S1
M92 X80 Y80 Z400 U88.9 V32 ; Set axis steps/mm
M350 X16 Y16 Z16 U16 V16 E16

M201 X800 Y1800 Z500 U200 V200 E1000 ; Accelerations (mm/s^2)
M203 X2000 Y2000 Z1500 U1500 V1500 E3600 ; Maximum speeds (mm/min)
M566 X1200 Y1200 Z50 U1000 V1000 E500 ; Maximum instant speed changes (mm/min)

M208 X190 Y270 Z194.8 V190 ; set axis maxima

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Temperature Sensor Parameters
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M140 S-273.15 H-1

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Tool Definitions
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M563 P0 D0 S"Paste extruder"
G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures

M92 E913 ; Set extruder steps per mm

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Z Probe
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M558 P0 ; Z probe is not present

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Axis Compensation
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M556 S78 X0 Y0 Z0 ; Axis compensation

T3P3Tony

@knaudler you could edit DWC to change this, but by definition seeing the fans does not give you control of them because they are controlled by the temperature of the hotend....

wilriker

I had a strange issue today while printing. Somewhere in the middle of printing layer 1 I used baby-stepping to raise Z by 0.025mm. And about 40s into layer 2 I undid that again. And now this might be coincidence but at about the same time DWC reported a switch from layer 2 to layer 3 (layers 1 to 4 were supposed to take about 10-15 minutes each) and reported layer 2 with a total time of 40s.

Now my print does have a shifted layer (again might be coincidence with bad first layer adhesion as another rather probable reason). I cannot tell if that really is layer 2 to 3 (it rather looks like layer 2 was shifted to the left compared to layer 1 but I cannot tell for sure - and as I was controlling the printer from remote using webcam to only check sometimes I don't know for sure either).
I looked at the Gcode and layer 1, 2 and 3 have about the some amount of lines which means that part is OK.

I will have to print that part again and will see if this happens again. Definitely never had something like this before when using baby-stepping.

Knaudler

@t3p3tony

hi
using fan 1 for hotend cooling
starting at 50 degrees - at 80% (have 15v input)

sometimes - if I want higher temps - 250 degrees - I push the fan to 90-100%
or if I need only 190 degrees - in the night, for extra silence - go down to 70% fan, thats ok

the only sound of the cr10 now are the fans

would be nice for me to controll all fans

thanks

dc42

@knaudler said in It's out! RepRapFirmware 2.0 and 1.21.1 released:

@t3p3tony

hi
using fan 1 for hotend cooling
starting at 50 degrees - at 80% (have 15v input)

sometimes - if I want higher temps - 250 degrees - I push the fan to 90-100%
or if I need only 190 degrees - in the night, for extra silence - go down to 70% fan, thats ok

the only sound of the cr10 now are the fans

would be nice for me to controll all fans

thanks

One workaround would be to create a few macros to set different speeds for the hot end fan.

deckingman

@knaudler said in It's out! RepRapFirmware 2.0 and 1.21.1 released:

@t3p3tony

hi
using fan 1 for hotend cooling
starting at 50 degrees - at 80% (have 15v input)

sometimes - if I want higher temps - 250 degrees - I push the fan to 90-100%
or if I need only 190 degrees - in the night, for extra silence - go down to 70% fan, thats ok

the only sound of the cr10 now are the fans

would be nice for me to controll all fans

thanks

I don't know if you are aware of this but you can use thermostatic control to vary the fan speed over a range of temperatures which might achieve what you want automatically when you change the hot end temperature. This is what I do but in my case I just use zero speed below 60 deg C and full speed at 140 and above. In your case you could use for example M106 P1 S255 I0 F250 H1 T50:250 would give (if my maths is correct) zero speed at 50 degrees C and below, 70% speed at 190 deg C and 100% speed at 250 deg C. You might need to play around with those values and there is also an "L" parameter to set the minimum fan speed which you could use to give a non zero speed.

Knaudler

thats a good idea
I will test.

thanks