Thanks Ewart
I did a replace M104 to M109 and run the file again, and had this result.
(It may be that not every M104 should have been changed)
I have uploaded both the gcode and a screen shot of Octoprint.
I do appreciate you and Sammy spending time on this.
In the meantime, I am going to try a file that I know works OK to ensure that there has be no sudden change in the Prusa or Ender3.
Do you have something like a SSR between the printer board and hotend heater?
The actual temp should go down when the target temperature goes down.
Also the target temp ramp in the end is quite unusual.
Ewart.
I don't know what an SSR is, however, I may have sent you two gentlemen on a wild goose chase.
When trying to print a previously 'good' file, I had a report back from the printer.
Tomorrow I will pull the print unit apart and makes sure all is well.
I have spare, so I might install that.
If I have wasted your time, i sincerely apologise.
Ewart
SR Solid State Relay . Nope ... bog standard hot end . . . but it looks interesting!
Please share the systeminfo bundle.
There are weird things going on:
@1: the target temp is 0 but @2 the heat is at 250°C
@3: the target is at 240°C and the actual temp is oscillating. This is a sign that a PID tune is needed.
I assume some issues with the serial connection too.
And I'm still wondering about the ramps with the target temps
Ewart,
Please don't waste too much time on this.
However, system bundle attached.
octoprint-systeminfo-20211206205710.zip (52.6 KB)
I did say that I would replace the hot end, but instead decided to run the 260-200 temp stack file in Octoprint on my Rpi's browser. The print is coming out fine, but the Octoprint data does not match what is happening on the printer.
The printer is stepping the temperatures, as required, according to the Ender3 display:-
See below please (The forum will notlet me embed images)
The Octoprint via the Rpi shows this:- See below
The Octprint on the PC shows this:-
Admittedly they are taken at different times, but the variation is obvious. See below
I suppose the important thing is the printer is working as I want, so I will continue to use Octoprint, but ignore what the data shows me.
Real shame, Octoprint and the Rpi was an 80th birthday present from my son, and I was really enjoying it.
I quite understand if you also want to give up on this issue. If so, let me know and I will close the thread off.
I am confused. None of the temperature graphs I see here reflect what I expect to see when printing a temperature tower. I decided to create a very simple test case (see below) and the resulting temperature graph (see below that). I left out the actual printing parts. You may want to change the position of the nozzle, the temperatures, and the delay between changes but the resulting temperature graph should look similar to mine.
G28
G0 X140 Y140 Z10
M109 S180
G4 S60
M109 S190
G4 S60
M109 S200
G4 S60
M109 S210
G4 S60
M109 S220
G4 S60
M109 S230
G4 S60
M109 S0
I am cycling through the tool heads on my LulzBot TAZ 6 doing PID tuning and this data was collected before I completed the process for this tool head. Pretty sure this graph would look better after I finish.
Here are the input and output files, Temp_Test.zip (71.3 KB)
since you stated you are using PrusaSlicer, in the custome gcode section of the printer tab insert the following in either the "before layer change gcode" or "after layer change gcode" section and reslice the file. You may need to change the specific layer values or temp values.
{if layer_z==1.6} M104 S225 ; T tower floor 1
{elsif layer_z==11.6} M104 S220 ; T tower floor 2
{elsif layer_z==21.6} M104 S215 ; T tower floor 3
{elsif layer_z==31.6} M104 S210 ; T tower floor 4
{elsif layer_z==41.6} M104 S205 ; T tower floor 5
{elsif layer_z==51.6} M104 S200 ; T tower floor 6
{elsif layer_z==61.6} M104 S195 ; T tower floor 7
{elsif layer_z==71.6} M104 S190 ; T tower floor 8
{elsif layer_z==81.6} M104 S185 ; T tower floor 9
{elsif layer_z==91.6} M104 S180 ; T tower floor 10
{endif}
Hi tsturgill
I did originally say that I used Prusa to slice a .stl file, but since then, I obtained from Thingiverse a gcode file expressly stated to be for the Ender.
It was gcode file that I ran today, the original code being changed to run at higher temperatures.
I do like the if statements you mention, and can see how that should work
Thank you for your response
Hi b-morgan
I like this.
It's worth a punt.
Thank you.
I will let you know how it goes.
Well! That didn't go quite like I expected!
These test results make it even stranger that I got an earlier perfect print when the data in Octoprint was less than accurate..
Am I chasing a false goal here?
"Broken implementation of the communication protocol" can also cause a whole bunch of trouble with temperature reporting. Take care of this, this message is not there for fun.
Additionally something indeed seems to be off with your heaters, or you wouldn't get heating failed messages from your firmware. This indicates something like loose wiring/intermittent connection errors or outright heater failure.
All in all everything in this thread looks like a beyond confused firmware and a strong need to make sure your wiring is sound, your printer electronics are sound and also your firmware itself is sound.
Very many thanks for your response foosel.
When I first saw the error report I spent a considerable amount of time, within the level of experience that I have, to resolve the error message situation. I am getting a new board as an Xmas present from my son, so I will repeat all of those efforts again. With a new all-metal extruder as well (What a good son!)
I am very much looking forward to getting this working.
Is there any link that you can suggest, please, to help working out how to get rid of the errors in my system.
There's a link right in the message shown to you in OctoPrint, just click on "Learn more" 
I must admit, that was the first port of call, but was unsuccessful. I will persevere, because I really want this to work for me as it obviously does for so many more people.
