search

crealitycloud / OctoPrint-CrealityCloud

26 stars 10 forks source link

Messing up temps with wrong added commands #50

Open splunkenizer opened 2 years ago

splunkenizer commented 2 years ago

This plugin is messing with the gcode commands in octopi. When I enable it and print from octopi, two temp setting commands are added after the bed has reached its temp and the hotend is then turned on. The target temps are mixed up with the other device. Why is this plugin even adding commands here?

Recv:  T:27.44 /0.00 B:59.99 /60.00 @:0 B@:47
Recv:  T:27.44 /0.00 B:60.00 /60.00 @:0 B@:59 W:0
Recv: ok
Send: N4 M104 S60*87
Recv: ok
Send: N5 M140 S200*98
Recv: ok
Send: N6 M113 S2*103
Recv: ok
Send: N7 M104 S200*96
Recv: ok
Send: N8 M105*47
Recv: ok T:27.47 /200.00 B:60.05 /110.00 @:0 B@:63
Send: N9 M109 S200*99
Recv:  T:27.47 /200.00 B:60.05 /110.00 @:0 B@:63 W:?
Recv:  T:27.47 /200.00 B:60.12 /110.00 @:127 B@:127

The two commands Send: N4 M104 S60*87 and Send: N5 M140 S200*98 are added and should not be there. They even have the wrong temps set. As you can see my bed is then going to 110, which seems to be the maximum. If I disable the plugin the two commands are not added anymore and everything works as expected.

thekameleon commented 1 year ago

I am experiencing the same issue. It set my bed to 110 Celsius and hotend to 80 Celsius. I am using a Creality CR-M4 printer.

Vaakefjell commented 9 months ago

I’m seeing a similar thing, but not when using the cloud printing. When starting prints from Cura on the LAN, the bed temp will be set to the same as the extruded temp after it reaches the correct temperature, and will instantly revert to 115 C. Not an issue when manually adding and starting files in Octoprint. Disabling this plugin removes the problem.