M105 reports wrong temperature for extruder 0

I am printing using extruder 2 via octoprint. I noticed that octoprint reports that the temperature for extruder 1 is 230. The printer control panel shows that extruder is at room temperature (confirmed by touching it). When I send a M105 command to the printer I get back
Recv: T0:230.00 /230.00 B:79.97 /80.00 T0:23.75 /0.00 T1:230.00 /230.00 @:64 B@:67 @0:0 @1:64
which shows that the SV04 reports the temperature for extruder 1 (T0) as 230.

Which firmware version are you using?

Version 1.1.0. The latest I can find

Host report generation is a mess in Sovol’s Marlin firmware versions: The temperature message implementation handles the target extruder & the redundant extruder which will lead to confusion depending on mode & toolhead selected…

I cleaned that up in my current firmware version. The host output format reads as follows:
left nozzle [T0:] current temperature [ / ] target temperature [ ]
right nozzle [T1:] current temperature [ / ] target temperature [ ]
print bed [B:] current temperature [ / ] target temperature [ ]
left heater [@0:] heater power [ ]
right heater [@1:] heater power [ ]
bed heater [@B:] heater power [ ]

Thanks for that. I note that in configuration.h there is a line

#define NUM_RUNOUT_SENSORS 2 // Number of sensors, up to one per extruder. Define a FIL_RUNOUT#_PIN for each.

but I could not find any definitions for FIL_RUNOUT2_PIN or FIL_RUNOUT2_PIN


Runout pin definition has nothing to do with the issue you started here.
Anyhow, pin definitions are related to the current motherboard type, in case of SV04 you will find that in file “Marlin/src/pins/stm32f1/pins_CREALITY_V4.h”:

// Filament Runout Sensor
  #define FIL_RUNOUT_PIN                  PE5
  #define FIL_RUNOUT2_PIN                PE6

Again Thanks for that. The reason I asked about the runout was that I had a filament runout that was not detected and you sound like you know what you ware talking about (certainly more than me).
I was looking at why it failed (I am using Octoprint and suspect that “Host Actions” are disabled) and was checking out all the parameters about runout. I am surprised though that the SV04 doesn’t seem to handle runouts itself. I would have though any printer would, on detecting runout, park the heads and wait for user action

Correct, Sovol’s Marlin firmware versions do not support HOST_ACTION_COMMANDS.
Runout sensor handling is imlemented in files “Marlin/src/feature/runout.h” and “Marlin/src/feature/runout.cpp”, however, there is much room for improvement left:

  • printing is paused when any sensor reports a runout, which makes no sense when printing in single mode
  • filament change and pause feature may or may not continue printing after resume

In addition, the runout sensors can hamper the supply of filament mechanically. Therefore I decided to skip the runout sensors on my SV04. If I have larger printouts, I usually weigh my filament spool and ensure that the remaining filament is sufficent for the calculated estimate of the sliced 3D-model.