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

Nozzle temperature in status of completed job incorrect #9

Open
dojohnso opened this issue Nov 29, 2023 · 1 comment
Open

Nozzle temperature in status of completed job incorrect #9

dojohnso opened this issue Nov 29, 2023 · 1 comment
Assignees
Labels
bug Something isn't working todo Something that is being looked into or planned for a future release

Comments

@dojohnso
Copy link
Owner

per @morris2009 OllisGit#222

Hi,
In my setup, somehow in the status of completed jobs, it always says 160 degrees for nozzle temperature.
This is probably resulting from the start Gcode where the nozzle is heating up to a fixed temperature of 160, and the bed to printtemp, to do the bedlevel.
After bedleveleling has finished it will heat-up to print temp and start printing.

Is there a way to have printjobhistory ignore the first temperature setting, and display the correct nozzle temp with which the object was printed?

@dojohnso dojohnso self-assigned this Nov 29, 2023
@dojohnso dojohnso added bug Something isn't working todo Something that is being looked into or planned for a future release labels Nov 29, 2023
@dojohnso dojohnso moved this from Todo to In Progress in Octoprint PrintJobHistory plugin Dec 14, 2023
@pnt103
Copy link

pnt103 commented Dec 18, 2024

Just a "me too" comment to say that I also find this a real pain. I believe that the plugin is reading the first temperature commands it sees, which for many people is a pre-heat to a standby temperature. It should instead look for the first layer temperature, which would be the last M109 before the priming line. Given that different people/ using different slicers might have completely different priming lines or even none at all (using a blob or relying on a skirt/brim/raft), perhaps the best thing to do is to keep updating the value found in M109 commands until the plugin script sees the start of the first layer (ie a LAYER comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working todo Something that is being looked into or planned for a future release
Projects
Development

No branches or pull requests

2 participants