RRF and Heaters – Duet 2 WIFI 3.1.1
-
what firmware are you running on the paneldue?
-
@Veti 1.24
-
Under "Heat" is it every thing normal?
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L4MSJ-6J9F0-3S46Q-KT3YP
Used output buffers: 3 of 24 (13 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93884 of which 60 recycled
Exception stack ram used: 304
Never used ram: 8844
Tasks: NETWORK(ready,308) HEAT(blocked,1224) MAIN(running,1880) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:21:42 ago, cause: power up
Last software reset at 2020-11-13 12:09, reason: User, spinning module GCodes, available RAM 8836 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 43.0, current 49.1, max 49.4
Supply voltage: min 23.7, current 24.1, max 24.3, 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-11-13 13:30:55
Cache data hit count 2136812117
Slowest loop: 13.47ms; 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 4.1ms, write time 6.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 = 1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.2
=== 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: 26.07ms; fastest: 0.00ms
Responder states: HTTP(0) 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 ec:fa:bc:01:d4:c6
WiFi Vcc 3.38, reset reason Unknown
WiFi flash size 4194304, free heap 24528
WiFi IP address 192.168.10.62
WiFi signal strength -54dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
i dont see anything unusual. maybe someone else can have a look?
-
@Veti Funny
Just deleted the 2 lines that I added manually to the config (M140 and M143) and everything went back to normal
How can this be? -
Adding M143 H1 S290 and everything stays normal
Adding M140 H1and everything gets broken againThis M140 H1 command for the nozle makes all the difference
-
that makes sense.
M140 H1 ; map heated bed to heater 0
this means that the heater is designated to be a bed heater.
you dont want to do that for H1, as it is not a bed heater. -
@Veti that said, don't I need to map it anyway with some other M140?
I just leave it like that? -
yes
-
@Veti Ok, thank you very much for all this hours that you spent helping me
