Can't get part cooling fans running :(
-
Yes 2 cooling fans (original Predator) in parallel connected to the FAN-0 connector, fans and the PSU are 24V.
Don't know about PWM frequency of Q24000, I copied the setup from someone on this forum (honestly doesn't know who anymore), maybe he didn't use the original fans.
Deleted M106
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 538CM122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-6J9F4-3S46T-1UVVN
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93212 of which 60 recycled
Exception stack ram used: 264
Never used ram: 9556
Tasks: NETWORK(ready,404) HEAT(blocked,1224) MAIN(running,1824) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:24 ago, cause: power up
Last software reset at 2020-10-12 21:12, reason: User, spinning module GCodes, available RAM 9316 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 29.4, current 34.6, max 34.7
Supply voltage: min 24.7, current 24.9, max 25.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2020-10-13 00:29:14
Cache data hit count 137051482
Slowest loop: 6.77ms; fastest: 0.14ms
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 3.9ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.91ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 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.23
WiFi MAC address f4:cf:a2:6e:87:5c
WiFi Vcc 3.36, reset reason Unknown
WiFi flash size 4194304, free heap 25192
WiFi IP address 192.168.1.20
WiFi signal strength -71dBm, reconnections 0, sleep mode modem
Socket states: 4 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
Anycubic Predator - Duet-2 wifi PanelDue - Smart effector
- WiFi -
-
I changed M950 to Q500, fans still not spinning.
M950 F0 C"fan0" Q500
-
@holco62 said in Can't get part cooling fans running
:I changed M950 to Q500, fans still not spinning.
M950 F0 C"fan0" Q500
Hi,
How did you test the fans? What command did you issue?
Frederick
-
@holco62 said in Can't get part cooling fans running
:Yes 2 cooling fans (original Predator) in parallel connected to the FAN-0 connector, fans and the PSU are 24V.
Don't know about PWM frequency of Q24000, I copied the setup from someone on this forum (honestly doesn't know who anymore), maybe he didn't use the original fans.
Deleted M106Don't delete the whole M106, just the F65535 part.
Try this:
; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 C"PartCoolingFan" P0 S0 H-1 B1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ;HOTEND FAN create fan 1 on pin fan1 and set its frequency M106 C"HotendFAN" P1 H1 T45 ; set fan 1 value. Thermostatic control is turned on -
@Phaedrux Thanks, I will try it this evening.
Btw, all the lines 1>5
-
@Phaedrux said in Can't get part cooling fans running
:@holco62 said in Can't get part cooling fans running
:Yes 2 cooling fans (original Predator) in parallel connected to the FAN-0 connector, fans and the PSU are 24V.
Don't know about PWM frequency of Q24000, I copied the setup from someone on this forum (honestly doesn't know who anymore), maybe he didn't use the original fans.
Deleted M106Don't delete the whole M106, just the F65535 part.
Try this:
; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 C"PartCoolingFan" P0 S0 H-1 B1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ;HOTEND FAN create fan 1 on pin fan1 and set its frequency M106 C"HotendFAN" P1 H1 T45 ; set fan 1 value. Thermostatic control is turned onIt's working now, many thanks for your help
Is it also possible to start the cold-end fan at a nozzle temp of 50 degrees on the fan01 connector?
-
I see it now
line 4 and 5 is for the hotend fan that triggers on 45 degree, I only have to put the connector on the FAN1 output which is now connected on a always on output 
Have a lot to learn about G-code
-
Still needed some tuning, but a week ago I did not expect to have a working printer already
-
With a Z axis calibration I sometimes see the number 1000 in red in the status box at sensors Z-probe, but usually it stays at 0 (not in red).
What does that mean? -
It's showing that the probe is triggered. What it shows and how long it shows it will depend on the type of probe.
-
@PhaedruxOk, but why don't I see the number 1000 in red every time the probe triggers during a calibration?
-
What probe do you have?
-
The stock Predator probe with a micro switch
-
-
I changed M558 H30 to H35 in the config.g, but that hasn't changed anything, but the calibration is going damn slow now
-
Well the switch is only going to show triggered when it's depressed, so in normal use it would be very brief.
M558 H is the dive height.
You should consider posting a new thread with your probing issues as it's not related to your initial problem which was solved.
-
Ok thanks, I will create a new topic.
