-
Notifications
You must be signed in to change notification settings - Fork 112
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
Non functional after installing 1.0.1 #189
Comments
https://community.octoprint.org/t/where-can-i-find-octoprints-and-octopis-log-files/299 Set debug |
I have same issue , after update PSU no longer works. |
@htrabbit Open a new ticket and provide all required info. Be sure to restart octoprint after debug logs are enabled. |
octoprint.log Doing the same changes did not work on my first printer and Octopi setup. It had been running a print until recently, and did try doing the same changes on it, but that did not fix the issue there. I will see about enabling debug logs on it tomorrow if I get a chance and upload it. |
Same issue for me after the Update. I will try to provice details later. |
Same issue, also if psucontrol plugin is enabled wired etherneteth0 dissapear from system. Works with "PSU Control - RPi.GPIO" plugin after this update. |
@Markeno76 |
After powering off the Pi for the night, the one I uploaded the log for, that I had gotten working is no longer working. No changes made that I am aware of. I had it do a shutdown from the web interface and went to bed, after powering it back on his morning it no longer works. It is also again not letting the Enclosure plugin access that GPIO pin. Last night both could access it, the lightning bolt was showing status correctly. |
@Markeno76 looks like you installed PSUControl-RPiGPIO. Remove that and check the settings that I mentioned or open a ticket on https://github.com/kantlivelong/OctoPrint-PSUControl-RPiGPIO. You shouldn't really need PSUControl-RPiGPIO anyway. |
I have removed PSUControl-RPiGPIO, switched it back and set the pin number from the BOARD 40 designation to 21 the BCM number for both Control and Sensing. The lightning bolt button can now turn on the printer. It does not go Green, and it does not turn the printer off when pressed again. I also use BCM Pin 21 for the Sense function, in floating. Sounds like #192? |
Ah did not see you were using the same pin for both. Not really supposed to do that as an output can't really be an input at the same time. |
I just wanted to follow up, I did get PSUControl back to fully working. Both Switching and Sensing. There were other complications, confusion on the new PSUControl-RPiGPIO addon plugin thinking it was needed when it wasn't apparently. A locked up and then crashed Octoprint, then a failed SD card on the original Octoprint. Then a small wiring change. I had to start a print on the Octopi install that I had been using PSUControl on, so I went on to add it to my second printer. I needed to do that as I had gotten the IOT Relay unit for it the other day. This unfortunately became troublesome in it locked up while changing settings in the PSUControl-RPiGPIO. I had to reimage the SD Card for some reason. I was mistakenly using the RPi.GPIO addon plugin, I did get that working, but after a shutdown and then powering it up it wasn't working again. It was then removed, and settings back to BCM numbering but the Sensing wasn't working due to not being able to use the same pin as the Switching function any longer. I am still temporarily using "Internal" Sensing on that Octoprint. I will go back to it and wire the Switching pin to another pin for Sensing later on for it. I then went back to my primary printer and trying to get it working on there as the print was over. I tried to run an update on Raspbian via SSH, it errored out saying about a Readonly filesystem part way through the update. This killed the system. I pulled the MicroSD Card and tried to reimage it but it would not format, again saying read only. It appears due to the card failure. I imaged a new MicroSD Card with the latest OctoPi image. While having it open I wired the Switching pin to another GPIO to use for Sensing (Per #182 ). The Sensing still would not work. This turned out to be that the OctoPi 18.0 image has kernel 5.4, and in order for it to work you need kernel 5.5 or higher (Per #193 ). I did a full-upgrade that took it to 5.10. I now have Switching and Sensing working on the GPIO with the two pins wired together (Per #182 ). Thank you for your help sorting it out. |
Thanks for the summary. So in the short term I'll see if I can reimplement the "bugged" sensing/switching on same pin thing into PSUControl-RPi.GPIO. That should help with #182. In general it sounds like older/outdated installs should stick to using the PSUControl-RPi.GPIO plugin. |
What were you doing?
What did you expect to happen?
It to work still after the update.
What happened instead?
It did not work after the update. Lightning bolt won't change on clicking. I tried installing PSU Control RPGPIO and no change. Sensing is set to sense GPIO Pin 40. Changing it from that, the bolt will toggle, but won't trigger then GPIO 40 like it is supposed to.
Version of OctoPrint-PSUControl
It is not listed in the lower left but it quit on installing 1.0.1 update
Operating System running OctoPrint
OctoPrint 1.5.3 Python 2.7.16 OctoPi 0.17.0
Printer model & used firmware incl. version
Not applicable as PSU Control does not connect to the printer.
Link to octoprint.log with octoprnt.plugins.psucontrol set to DEBUG
not sure how to get this
Wiring diagram
Pi4b GPIO21 (Pin 40) to IOT Relay unit.
The text was updated successfully, but these errors were encountered: