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 not always set correctly when "Shared nozzle" is selected #1907

Closed
tcm0116 opened this issue May 9, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@tcm0116
Copy link

commented May 9, 2017

What were you doing?

When the "Shared nozzle" extruder option is selected, OctoPrint will always send M104 commands using the T0 tool identifier. However, in the 1.1.0 version of Marlin (I'm not sure about older versions), the tool identifier in M104 needs to be either set to the current tool or no tool identifier provided.

What did you expect to happen and what happened instead?

If I select Tool 1 in the control tab of OctoPrint and then select a new nozzle temperature in the temperature tab, OctoPrint will send "M104 T0 SXXX.XXXXX", which will be ignored by Marlin.

Branch & Commit or Version of OctoPrint

OctoPrint 1.3.2 (master branch)

Operating System running OctoPrint

OctoPi

Printer model & used firmware incl. version

Custom HICTOP 3DP-11 with Marlin 1.1.0

Browser and Version of Browser, Operating System running Browser

Safari

Link to octoprint.log

https://pastebin.com/Dm9jMdcL

Link to contents of terminal tab or serial.log

N/A

Link to contents of Javascript console in the browser

N/A

Screenshot(s) or video(s) showing the problem:

N/A

I have read the FAQ.

@GitIssueBot

This comment has been minimized.

Copy link
Collaborator

commented May 9, 2017

Hi @tcm0116,

It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Read the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!).

If you did not intend to report a bug but wanted to request a feature or brain storm about some kind of development, please take special note of the title format to use as described in the Contribution Guidelines.

Please do not abuse the bug tracker as a support forum - if you have a question or otherwise need some kind of help or support refer to the Mailinglist or the G+ Community instead of here.

Also make sure you are at the right place - this is the bug tracker of the official version of OctoPrint, not the Raspberry Pi image OctoPi nor any unbundled third party OctoPrint plugins or unofficial versions. Make sure too that you have read through the Frequently Asked Questions and searched the existing tickets for your problem - try multiple search terms please.

I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2017-05-23 01:20 UTC) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you!

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them.

@foosel

This comment has been minimized.

Copy link
Owner

commented May 9, 2017

Thanks for reporting that, that was an oversight. While I think Marlin shouldn't just happily ignore temperature lines like that, OctoPrint indeed shouldn't be sending tool parameters with temperature commands when a shared nozzle is configured. Now fixed on maintenance, soon devel and will be part of the upcoming 1.3.3 release.

@foosel foosel added this to the 1.3.3 milestone May 9, 2017

@foosel foosel closed this in 2caa10f May 31, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.