error after upgrading firmware

oldironjunkie

I recently upgraded my firmware to 3.5.2 and after doing so I started to get a warning message "Error in start-up file macro line 2: Heater 1 not found" a start up. In the past I had issues with an extruder driver that was burned out by a faulty motor. I had to switch to extruder 1 and also heater 2 and was working for an extended period of time. Till the firmware upgrade. Not sure where to look for the start up file macro (unable to find). I am sure if I am pointed in the right direction I will fix it. Also tried uploading the config.g file but it is not working. Probably not doing it right. Printer is working ok but the message is annoying. Please help.

oldironjunkie

I just copied and pasted the config.g file. hope this helps.

;General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"OLDIRON PRINTER" ; set printer name

;Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

;Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S0 ; physical drive 3 goes backwards
;M569 P4 S0 ; physical drive 4 goes backwards TITAN AERO
M569 P4 S1 ; physical drive 4 goes forwards SLICE MOSQUITO
;M569 P3 S0 ; physical drive 3 goes backwards
;M569 P3 S0 ; physical drive 3 goes backwards
;M569 P3 S0 ; physical drive 3 goes backwards
;M569 P3 S0 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E4:4:4:4 ; set drive mapping
M350 X16 Y16 Z16 E16:16:16:16 I1 ; configure microstepping with interpolation
;M92 X80.70 Y79.95 Z399.74 E408 ;set steps per mm E3D titan aero extruder
M92 X80.70 Y79.95 Z399.74 E405 ; set steps per mm mosquito extruder (recheck)
;M92 X80.70 Y79.95 Z399.74 E454. ; set steps per mm biqu extruder
M566 X800.00 Y800.00 Z800.00 E650:800:800:800 ; set maximum instantaneous speed changes (mm/min)
M203 X7500.00 Y7500.00 Z6500.00 E900:900:900:900 ; set maximum speeds (mm/min)
M201 X800.00 Y800.00 Z500.00 E250:300:300:300 ; set accelerations (mm/s^2)
M906 X1400 Y1800 Z900 E1200:800:800:800 I50 ; set motor currents (mA) and motor idle factor in per cent
M84 S300 ; Set idle timeout

;Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X315 Y310 Z400 S0 ; set axis maxima3

;Endstops
M574 X1 S1 P"!xstop" ; configure active-(high) LOW endstop for low end on X via pin xstop
M574 Y1 S1 P"!ystop" ; configure active-(high) LOW endstop for low end on Y via pin ystop
M574 Z1 S1 P"!zstop" ; configure active-(high) LOW endstop for low end on Z via pin zstop

;Z-Probe
M950 S0 C"duex.pwm1" ; Duet 2 WiFi/Ethernet + DueX2/5
M558 P9 C"^zprobe.in" H3 F50 T9000 R0.5 ; Duet 2 WiFi/Ethernet, DueX2/55
G31 X-5 Y-25 Z3.66 ; z probe offset
M557 X0:300 Y10:300 S30 ; bed mesh size and spacing
M376 H9 ;bed mesh fading

;Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; 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.0 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H2 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H2 R2.584 C226.4 D8.23 S.5 V24.3 ;tool heat
M143 H2 S350 ; set temperature limit for heater 1 to 350C

;Fans
M950 F0 C"fan0" ; create fan 0 on pin fan0 and set its frequency
M106 P0 S.75 H-1 Q500 ; 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 S.75 H-1 Q500 ; set fan 1 value. Thermostatic control is turned on

;Tools
M563 P1 D1 H2 F0 ; define tool 1
M572 D1 S0.02 ;ADDED PRESSURE ADVANCE SETTING
G10 P1 R0 S0

; Miscellaneous
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T1 ; select first tool

jay_s_uk

@oldironjunkie what's in your config-override.g?

droftarts

@jay_s_uk said in error after upgrading firmware:

@oldironjunkie what's in your config-override.g?

That would make sense regarding the error message and line number, as heaters are the first thing that are written in config-override.g:

; config-override.g file generated in response to M500 at 2023-10-02 12:25
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 R0.326 K0.151:0.000 D5.80 E1.00 S1.00 B0
M307 H1 R1.967 K0.377:0.221 D8.17 E1.00 S1.00 B0 V12.1
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
...

I expect you have M307 H1 ... left in config-override.g, left over from when you had more hot ends, and the firmware is complaining that you haven't defined this heater before setting M307 for it.

config-override.g will also be overriding the M307 heater values set in config.g, so make sure they are the ones you want to use.

Ian

oldironjunkie

@droftarts Here is my config-override.g. looks like heater 2 is listed.

M307 H2 R2.584 C226.4 D8.23 S.7 V24.3 ;TOOL HEAT updtaed 6/28/2023
M572 D0 S.02 ;pressure advance
M307 H0 R0.890 C200.2 D3.32 S1.00 V24.0 ;bed heat
M106 P0 S.75 H-1 Q500

droftarts

@oldironjunkie It looks like you have manually edited that config-override.g. Usually it is generated by the firmware, sending M500 to save the current settings. If you want to manually add things, add them directly to config.g, to avoid confusion.

Perhaps comment out the M501 in config.g, then send M98 P"config.g" to see if there are any errors generated.

Ian

oldironjunkie

@droftarts I am in the middle of a print for the next 20 hours. Will try all when it is done.

oldironjunkie

@droftarts I forgot to sayt hat the config.g and config-override.g were changed when I had issues with the motor driver last year.

oldironjunkie

@droftarts Thanks for your help I did all you asked and kept having the same issue. I reloaded the firmware and it is now working ok. No messages. It must have been something in the install process that caused it.

droftarts

@oldironjunkie Did you go back to an older firmware, or are you still on v3.5.2?

Ian

oldironjunkie

@droftarts Still on 3.5.2. About to start some long prints . We will see if it works in a few days. Again I thanks you. John.