RRF and Heaters – Duet 2 WIFI 3.1.1

MJCT

@jay_s_uk said in RRF and Heaters – Duet 2 WIFI 3.1.1:

That means you have issues with your thermistor.
What is showing in DWC?

Both my thermistors where working perfectly before the update and I didn’t touched the wirings so…..

By DWC you mean this? (Sorry I'm just an end user)

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 (20 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93884 of which 60 recycled
Exception stack ram used: 304
Never used ram: 8844
Tasks: NETWORK(ready,332) HEAT(blocked,504) MAIN(running,1848) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:21:01 ago, cause: power up
Last software reset at 2020-11-12 16:16, reason: User, spinning module GCodes, available RAM 8596 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04417000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 46.4, current 48.2, max 48.6
Supply voltage: min 23.9, current 24.1, max 24.2, 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 10:18:09
Cache data hit count 2059511898
Slowest loop: 7.28ms; 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.7ms, 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
=== 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: 42.97ms; 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 ec:fa:bc:01:d4:c6
WiFi Vcc 3.38, reset reason Unknown
WiFi flash size 4194304, free heap 21384
WiFi IP address 192.168.10.62
WiFi signal strength -52dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0

jay_s_uk

Can't see anything wrong with what you have in your config. (assuming you made the changes to the M308 we discussed earlier)
If you send

M98 P"config.g"

What comes up?

MJCT

@jay_s_uk said in RRF and Heaters – Duet 2 WIFI 3.1.1:

M98 P"config.g"

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

MJCT

Manually I did this

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 C570.5 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S110 ; set temperature limit for heater 0 to 110C
M308 S1 P"e0temp" Y"thermistor" T100000 B4092 C202.3 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M140 H1 ;
M143 H1 S290 ;

No luck

MJCT

Veti

@jay_s_uk said in RRF and Heaters – Duet 2 WIFI 3.1.1:

yes you can use those values

no you can not. they will lead to the result you are seeing.

@MJCT

delete C570.5 and C202.3

MJCT

@Veti What do I put in place?

Veti

@MJCT

nothing

MJCT

@Veti like this?

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S110 ; set temperature limit for heater 0 to 110C
M308 S1 P"e0temp" Y"thermistor" T100000 B4092 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M140 H1 ;
M143 H1 S290 ;

Veti

@MJCT
yes

MJCT

@Veti Yes!!!!

Now, two questions

Why didn’t the RRF created a M140 and M143 codes for the H1 (I did it manually)?
Can (should) I run a new M307 for each thermistors? If so, do I need to erase 0:/sys/config-override.g or should I just leave it alone?

jay_s_uk

@MJCT run M303 for each heater.
Once complete run M500 and it will over write the values in config-override

Veti

@MJCT said in RRF and Heaters – Duet 2 WIFI 3.1.1:

Why didn’t the RRF created a M140 and M143 codes for the H1 (I did it manually)?

i think there is a bug regarding this in the configurator

Can (should) I run a new M307 for each thermistors?

yes its required on rrf3 (at least for the bed)

If so, do I need to erase 0:/sys/config-override.g or should I just leave it alone?

currently its not used because there is not M501 in your config.g
this also means you can not save values with M500

MJCT

@Veti Sorry , I meant to say M303 not M307

Veti

@MJCT

yes you run M303 and put the values into the config with M307.
i understood what you meant.

MJCT

@Veti After both tests and M500's got this

; config-override.g file generated in response to M500 at 2020-11-13 11:54
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 A135.2 C635.5 D0.6 S1.00 V23.6 B0
M307 H1 A600.5 C163.9 D10.4 S1.00 V24.0 B0
; 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

do I need to add any M501 at config-override or at config.g?

Veti

@MJCT said in RRF and Heaters – Duet 2 WIFI 3.1.1:

do I need to add any M501 at config-override or at config.g?

at the end of config.g

MJCT

@Veti Just like this?

; config-override.g file generated in response to M500 at 2020-11-13 11:54
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 A135.2 C635.5 D0.6 S1.00 V23.6 B0
M307 H1 A600.5 C163.9 D10.4 S1.00 V24.0 B0
; 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
M501

Veti

@MJCT

thats you config-overwrite not your config

MJCT

@Veti Sorry

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S110 ; set temperature limit for heater 0 to 110C
M308 S1 P"e0temp" Y"thermistor" T100000 B4092 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M140 H1 ; map heated bed to heater 0
M143 H1 S290 ; set temperature limit for heater 0 to 110C

; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 S"Extr 1" D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue
T0 ; select first tool
M501