Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Temperature always be zero in preview for Creality K1 series #7582

Open
2 of 3 tasks
adoyle-h opened this issue Nov 26, 2024 · 1 comment
Open
2 of 3 tasks

Temperature always be zero in preview for Creality K1 series #7582

adoyle-h opened this issue Nov 26, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@adoyle-h
Copy link

Is there an existing issue for this problem?

  • I have searched the existing issues

OrcaSlicer Version

2.2.0

Operating System (OS)

Windows

OS Version

Windows 11

Additional system information

No response

Printer

Creality K1, K1C, K1Max, K1SE

How to reproduce

  1. Set up Printer
  2. Select any Creality K1, K1C, K1 Max Profile
  3. Put an stl file with or without changing Printer, Material, Process settings
  4. Slice
  5. Go to Preview Screen
  6. Select Temperature in dropdown menu

Actual results

In dropdown menu print(nozzle) Temperature shows 0.
Same steps with Creality Print not give this issue.

Expected results

The temperature dropdown menu in slicer preview screen must show the set temperature in the material profile.
Printer must use the slicer temperature values.

Project file & Debug log uploads

Cube.zip

Checklist of files to include

  • Log file
  • Project file

Anything else?

image

Related issue: #5491

@adoyle-h adoyle-h added the bug Something isn't working label Nov 26, 2024
@Sacrasang
Copy link

I am experiencing the same behavior in version 2.2.0 with a different printer (a modified Ender 5 S1 running Klipper and using the klipper gcode flavor).

I think the issue is related to this machine's start gcode not including any specific instructions for temperature and is only a graphical error in the gcode reader.

My machine start gcode is:

start_print BED_TEMP=[bed_temperature_initial_layer_single] EXTRUDER_TEMP=[nozzle_temperature_initial_layer]

The absence of any start gcode defining the first or subsequent layer temps appears to cause the gcode reader to ignore subsequent temperature commands - representing the extruder temperature with whatever is defined in the start gcode, or 0 if otherwise not defined. The called in bed and extruder temps I am using are not registered by the gcode reader. When I send this print to the machine it heads up to the appropriate temperature defined by the filament profile and successfully prints.

I tested adding M104 S150 before my start gcode and this caused the gcode preview to represent the entire print as 150C. This also had no adverse impact on printer execution of the print. Changing the gcode flavor had no impact on the gcode preview or machine behavior.

The temperatures reported in the gcode preview do not accurately reflect the temperature instructions present in the gcode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants