Figured it out, 3.3 release notes listed this:
All extruders must be declared explicitly using M584. In previous firmware versions, one default extruder was assign to driver 3.
Once I input M584 E3 in my config.g, it now listed both heaters and my extruder... off to a test print
M122 only listing one heater, but I see nothing wrong with my heater section in Config.g:
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
; Heaters
M308 S0 P"bed_temp" Y"thermistor" R4700 T100000 B3950 ; define bed temperature sensor
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M308 S1 P"e0_temp" Y"thermistor" T100000 B4815 C7.06e-8 R4700 ; define E0 temperature sensor
M950 H0 C"bed_heat" T0 ; heater 0 uses the bed_heat pin, sensor 0
M950 H1 C"e0_heat" T1 ; heater 1 uses the e0_heat pin and sensor 1
M140 H0 ; the bed heater is heater 0
M143 H1 S280 ; Set temperature limit for heater 1 to 280C
M307 H1 R2.546 C123.4 D3.51 S1.00
Looks like i lost my extruder after the upgrades:
; Heaters
M308 S0 P"bed_temp" Y"thermistor" R4700 T100000 B3950 ; define bed temperature sensor
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M308 S1 P"e0_temp" Y"thermistor" T100000 B4815 C7.06e-8 R4700 ; define E0 temperature sensor
M950 H0 C"bed_heat" T0 ; heater 0 uses the bed_heat pin, sensor 0
M950 H1 C"e0_heat" T1 ; heater 1 uses the e0_heat pin and sensor 1
M140 H0 ; the bed heater is heater 0
M143 H1 S280 ; Set temperature limit for heater 1 to 280C
M307 H1 R2.546 C123.4 D3.51 S1.00
; Fans
M950 F0 C"fan0" Q125 ; 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
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H0 T30 ; set fan 2 value. Thermostatic control is turned on
; Tools
M563 P0 D0 H1 S"HotEnd" ; 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
Worked now on:
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.5 (2022-11-30)
Duet WiFi Server Version: 1.27
Thank you both !
Now to see if things still work... 
@jay_s_uk said in Upgrading after 1.5yrs:
3.3 zip file then try
Won't re-apply 3.3 now, same error, even though I'm already on 3.3:
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.3 (2021-06-15)
Duet WiFi Server Version: 1.25
I'm using the Duet2CombinedFirmware.bin file
Well I got to 3.3, but 3.44 or 3.45 just causes an error when trying to update:
Error M997: In-application programming binary "0:/firmware/Duet2_SDiap32_WiFiEth.bin" not found
@jay_s_uk - Thank you.
Can I go straight to 3.44, or do I need to take smaller upgrade steps to get to 3.44 ?
Hey guys,
Long story short, my printers sat in storage for 1.5 years, just go them back online and working.
I'm currently rocking the below versions:
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.2.2 (2021-02-11)
Duet WiFi Server Version: 1.25
I'd like to upgrade to the latest stable releases for all the nifty new bells and whistles, but the release notes are longer than a college essay - LOL
Anyone have any cliff notes as far as config changed needed to remain functional after the upgrade?
Thank you for the quick reply - since I'm using the HEVO to build the Voron at the minute, I guess I'll wait to implement this as I've read the move from 3.2 to higher can be a bit tricky.
Thanks again !
So long story short, I updated my DD Ender 3 to Klipper with input shaping, simply calculated the frequencies using the formula they have documented and I'm thoroughly impressed. I'm now able to print at 200mm/s with 5k accel and almost no ringing.
I wanna try with my HEVO and Duet board with firmware 3.2.2, is it possible or do I have to update firmware and am I required to use an accelerometer to use input shaping with RRF?
I won't pretend that I made this change the "right way", but changing the M308 line to the below resulted in my displayed hotend temp to match the Type-K probe I inserted into the heater block
M308 S1 P"e0_temp" Y"thermistor" T100000 B4815 C7.06e-8 R4700
yes, I am using a E3d themistor, not sure why i needed to make this change, but I have verified printing looks normal now.
So I picked up a good certified DVM and using a k-style thermocouple, I was able to measure 185c when the printer believes it's at 200c That's a fairly large delta.
Any way to compensate?
Hey guys, recently swapped to Phateus Dragon hotend and slice heater cartridge, but still using the same thermistor.
It "feels" like I'm about 20deg cooler at 200c than normal, but I have no solid way to confirm.
I want to add a 20deg offset and see what happens, what's the best way to do that on a Duet 2 WiFi running on 3.2.2 ?
Current thermistor config is:
M308 S1 P"e0_temp" Y"thermistor" T100000 B4725 C7.06e-8 R4700
Sorry, I was being lazy, I do understand printing speed is not the be-all end all, but rather volumetric flow is.. some are getting ridicules volumetric flow on these hotends, from HEVORT to NOVA guys.
I couldn't care less if the creator is a "nice" guy or is abrasive. I also have investments in E3d, but am not adverse to try something new and it seems the Nova is a much cheaper high end unit when compared to Slice Engineering.
So I take it no one here has put hands on this unit and can provide any feedback?
Guys, don't get caught up on the heater wattage, they offer 60/80/100...
I'm more interested in how this is working and if any of you are using it.. the few videos that are out there seem very promising, easily printing at 300mm speeds.
It just doesn't seem very popular at the moment.
Anyone using one with a 100w extruder heater and a PT1000 sensor?
@gloomyandy said in Y Axis homing in reverse direction if acceleration increased:
@tsitalon1 You might want to switch back to absolute positioning after you have homed. It can get very confusing otherwise.
I have it in my start gcode in my slicer, but I will make the change, thank you!