-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
PSU Control no longer works in 1.3.11rc2 #3112
Comments
Hi @burgedm, 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 - that can be found at discourse.octoprint.org. Go there for any kind of issues with network connectivity, webcam functionality, printer detection or any other kind of such support requests or general questions. 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 2019-04-21 21:40 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, 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. |
Please share your octoprint.log, from startup (plugin loading) through where you trigger the PSU control. You might need to increase your log level if you believe there's truly nothing in there. |
Sure, once I get home.
I had it at debug level yesterday and there is no sign the octopi attempts to execute the command to power off the power supply.
…--
David Burgess
Senior Systems Specialist
Flight Information Services Automation
(613) 248-6878
From: Ted Timmons [mailto:notifications@github.com]
Sent: Sunday, April 7, 2019 19:35
To: foosel/OctoPrint <OctoPrint@noreply.github.com>
Cc: Burgess, Dave <Dave.Burgess@navcanada.ca>; Mention <mention@noreply.github.com>
Subject: Re: [foosel/OctoPrint] PSU Control no longer works in 1.3.11rc2 (#3112)
Please share your octoprint.log, from startup (plugin loading) through where you trigger the PSU control. You might need to increase your log level if you believe there's truly nothing in there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#3112 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AtihbrNuIbeNXff02SYPIOEvnWbJMBh-ks5veoC9gaJpZM4cg8_s>.
________________________________
This electronic message, as well as any transmitted files included in the electronic message, may contain privileged or confidential information and is intended solely for the use of the individual(s) or entity to which it is addressed. If you have received this electronic message in error please notify the sender immediately and delete the electronic message. Any unauthorized copying, disclosure or distribution of the electronic message is strictly forbidden. NAV CANADA accepts no liability for any damage caused by any virus and/or other malicious code transmitted by this electronic communication.
Le présent message électronique et tout fichier qui peut y être joint peuvent contenir des renseignements privilégiés ou confidentiels destinés à l’usage exclusif des personnes ou des organismes à qui ils s’adressent. Si vous avez reçu ce message électronique par erreur, veuillez en informer l’expéditeur immédiatement et supprimez le. Toute reproduction, divulgation ou distribution du présent message électronique est strictement interdite. NAV CANADA n’assume aucune responsabilité en cas de dommage causé par tout virus ou autre programme malveillant transmis par ce message électronique.
|
I need all the data requested in the ticket template, otherwise I can't look into this. Also pinging @kantlivelong who's the author of the affected plugin. |
Here's the log file, at 2019-04-09 00:45:50,849 the PSU is commanded ON, it's currently configured to turn OFF after two minutes of inactivity. |
So PSU Control is turning it on properly. That works- as confirmed by the serial connection 5 seconds later. And after a few seconds we can see the polling:
I think it goes to the plugin author at this point. |
Hmm, will have a look. Trying to get my test env up but having issues. |
@kantlivelong I think it might be this sentry issue. What I don't understand is why that didn't happen earlier because the target could always be edit to add more details: Looks like the offending heater is |
Dug a bit deeper and you have the same issue with printers that do not report a bed temperature. A simple I'm a bit reluctant to modify OctoPrint here to default to |
actual and target may be None if the firmware doesn't know a heater. So far the plugin didn't honor these situations, leading to issue with automatic shutoff e.g. in case of a printer without a heated bed or in the future without a heated chamber report in the response to M105. This patch makes things a bit more resilient. See OctoPrint/OctoPrint#3112
actual and target may be None if the firmware doesn't know a heater. So far the plugin didn't honor these situations, leading to issue with automatic shutoff e.g. in case of a printer without a heated bed or in the future without a heated chamber report in the response to M105. This patch makes things a bit more resilient. See OctoPrint/OctoPrint#3112
actual and target may be None if the firmware doesn't know a heater. So far the plugin didn't honor these situations, leading to issue with automatic shutoff e.g. in case of a printer without a heated bed or in the future without a heated chamber report in the response to M105. This patch makes things a bit more resilient. See OctoPrint/OctoPrint#3112
Thanks @foosel ! Tested out good here. Merged and released 0.1.8. |
Perfect, closing this then. |
Uh guys ... The firmware is reporting the temperatures just fine. |
1.3.11 introduces parsing of chamber temperatures. The temperature data handed from OctoPrint to plugins thus contains an entry for a So unless you are telling me that you have a heated chamber configured in your firmware and thus data for Of course, if you had fully filled out a ticket template as instructed in several places and even provided with during creation of a ticket, you'd also have shared a Please update the plugin and test. If it's still broken we can reevaluate this. PS: I'm not a guy. |
Now you're just being an ass so ... I'm done. |
Perfect! If there's an issue be sure to open it up in the appropriate repo and fill out all required info. |
actual and target may be None if the firmware doesn't know a heater. So far the plugin didn't honor these situations, leading to issue with automatic shutoff e.g. in case of a printer without a heated bed or in the future without a heated chamber report in the response to M105. This patch makes things a bit more resilient. See OctoPrint/OctoPrint#3112
PSU Control was working perfectly fine with 1.3.10 but when I upgraded to 1.3.11rc1 and then rc2 it no longer automatically turns off my printer.
The log file has an entry "Idle timeout reached after 5 minute(s). Turning heaters off prior to shutting off PSU" but it does not actually turn off the printer.
Nothing else is logged in the octopi logs or in the OS logs.
I'll reiterate that things were working perfectly fine until the upgrade - that's all that has changed.
The text was updated successfully, but these errors were encountered: