prusa3d / PrusaSlicer

G-code generator for 3D printers (RepRap, Makerbot, Ultimaker etc.)
https://www.prusa3d.com/prusaslicer/
GNU Affero General Public License v3.0
7.79k stars 1.94k forks source link

Gcode Preview showing wrong first layer temperature #7548

Closed wmmc88 closed 1 year ago

wmmc88 commented 2 years ago

Version

PrusaSlicer-2.4.0-rc2+win64 (but also seems to affect earlier 2.4 betas)

Operating system type + version

What OS are you using, and state any version #s Windows 11 Pro Insider Preview Build 22523.rs_prerelease.211210-1418

3D printer brand / version + firmware version (if known)

FlashForge Creator 3 V2

Behavior

Prusaslicer is showing the wrong temperature for the first layer of a print. In the "other_layer_temp.3mf" file, it shows first layer as 245C, which corresponds to the "Other Layer" temperature instead of the "First Layer" Temperature. This file has the layer height and first layer height to be the same.

In "first layer height different.3mf", it shows the first layer temp as 0C which corresponds with the temperature of the 2nd (unused) extruder. In this file, the first layer height is different from the layer height.

In both scenarios, it shows the wrong layer temp. It should be 240C. It looks like the generated gcode still has the right temperatures set, just not showing up properly in the gcode preview.

Is this a new feature request? No.

Project File (.3MF) where problem occurs

first layer wrong temp.zip

wmmc88 commented 2 years ago

cylinder on prism_0.6n_0.2mm_L-PVA_R-PETG_36m_FFC3V2.zip

Another temperature issue. It looks like its rendering tools 2's temperatures for tool 1's move. then Tool 2's temperature is just showing as 0C. Once again, the actual gcode seems fine and has M104 commands for the correct temperatures in the correct places.

dartrax commented 2 years ago

Prusaslicer is showing the wrong temperature for the first layer of a print. In the "other_layer_temp.3mf" file, it shows first layer as 245C

I see 0C here in first layer, the same as in the other 3mf. However, it seems to be wrong anyway.

bubnikv commented 2 years ago

Is it possible that you have the same issue as #7458?

bubnikv commented 2 years ago

7458 is indeed the same issue, see the following comment

IDEX temperature problem second extruder doesn't head up · Issue #7458 · prusa3d/PrusaSlicer · GitHub https://github.com/prusa3d/PrusaSlicer/issues/7458#issuecomment-991491246

https://reprap.org/wiki/G-code#M104:_Set_Extruder_Temperature

M104 in RepRapFirmware and Klipper

RepRapFirmware and some other firmwares support the optional T parameter (as generated by slic3r) to specify which tool the command applies to.

However Marlin 2 documentation states, that the T parameter is supported as well.

Set Hotend Temperature | Marlin Firmware (marlinfw.org) https://marlinfw.org/docs/gcode/M104.html

Your block

M104 S{first_layer_temperature[0]} T0 ; set right extruder temp
M104 S{first_layer_temperature[1]} T1 ; set left extruder temp

is not processed correctly by our G-code analyser. We likely need to improve that.

For now, you can just emit M104 S without the T parameter and switch the tools before setting the temperature.

st 22. 12. 2021 v 10:52 odesílatel dartrax @.***> napsal:

Prusaslicer is showing the wrong temperature for the first layer of a print. In the "other_layer_temp.3mf" file, it shows first layer as 245C

I see 0C here in first layer, the same as in the other 3mf. However, it seems to be wrong anyway.

— Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaSlicer/issues/7548#issuecomment-999438502, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMPSI4N4X74UC7GDSSXUHDUSGNUNANCNFSM5KQTD3QA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you are subscribed to this thread.Message ID: @.***>

wmmc88 commented 2 years ago

So the issue is just that prusaslicers gcoder viewer doesnt parse the M104 commands with the T parameter correctly?

bubnikv commented 2 years ago

yes

st 22. 12. 2021 v 15:23 odesílatel Melvin Wang @.***> napsal:

So the issue is just that prusaslicers gcoder viewer doesnt parse the M104 commands with the T parameter correctly?

— Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaSlicer/issues/7548#issuecomment-999613641, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMPSI2S4RVBAJFPJBEQIMTUSHNM3ANCNFSM5KQTD3QA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

boinappi commented 2 years ago

Similar issue like https://github.com/prusa3d/PrusaSlicer/issues/7548#issuecomment-998965309 slicer

GCode seems fine and just a visualization issue. PrusaSlicer 2.4.0

Garr-Garr commented 2 years ago

Bump :)

The GCode preview doesn't recognize the temperature of multiple extruders, only for Tool_0. The GCode is generated correctly! It just doesn't represent the temperature in the preview.

kubispe1 commented 1 year ago

In 2.6.0 G-Code preview is fixed and parsing G-Code M104 so:

DVSVIDEO commented 3 months ago

The bug is back in version 2.8.0+Win64 I have one extruder, no sync, no nothing. Simple printing. The legend shows the temperature at the first layer (where higher temperature is set) as 0 degrees Celsius Legend issue