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
PWM output - Cound not connect to pigpiod #684
Comments
Thanks for the bug report. I'll look into this and see if I can replicate the issue. |
I was able to replicate the error and push a fix. It appears the location of pigpiod has changed from /usr/local/bin to /usr/bin/, which causes the systemd scripts to attempt to execute a non-existent file. This fix won't be available until the next release, but you can get your system working my manually making the changes found in commit 1e6d0dd, saving, then executing the following commands to enable the service file: sudo /bin/bash ~/Mycodo/mycodo/scripts/upgrade_commands.sh disable-pigpiod
sudo /bin/bash ~/Mycodo/mycodo/scripts/upgrade_commands.sh enable-pigpiod-low |
Since this is a pretty big bug, I've gone ahead and released v7.7.0. So, you can upgrade normally rather than editing those files manually. You may still need to run those commands after upgrading, though. |
Actually, found an issue. Fixing before making final release. |
Thank you very much for that fast reply! I already upgraded before getting your last comment and now will wait for that final release before testing it. |
I just released v7.7.1 which has bug fixes I found upon release of 7.7.0. Try an upgrade, then execute those two commands, above, and see if you can set a PWM. |
After upgrading to 7.7.1, executing the commands above and rebooting no error appears anymore: But unfortunately it seems like there is no PWM output. I have connected two servo motors and they remain still. This is the output when I executed the two commands:
After trying to set the PWM output there are no errors is die Daemon log referring to the PWM output. |
You might have to restart the daemon after executing those two commands. Does the output turn green with the duty cycle displayed after manually turning it on from the Outputs page? |
Disregard my previous comment about the output. It does appear to be working. Do you have a multimeter or oscilloscope to test? |
Make sure you're using the correct pin. The numbering is for BCM 12, so verify this is the pin you're using and not physical pin 12. |
I just testet with an oscilloscope - you're right, it looks like PWM is working fine. I also used the right pin numbering (physical 32 for BCM 12), so I guess something's wrong with my motors or I messed up something else. But it's not PWM anymore, so thank you very much for fixing that problem! |
Glad to help. Thanks for the bug report and helping get this fixed. I'll close this issue as it seems to now be working. Let me know if you have any other issues and good luck getting your servos spinning. |
Mycodo Issue Report:
ver. 7.6.3 on Raspberry Pi 3 B+, Raspian Buster Lite (Kernel version: 4.19)
Hello Kyle and everybody else!
Problem Description
My PWM outputs through hardware pins or any other pins do not work. After trying to set the duty cycle an error appears:
For trying to resolve the problem I made a clear install of Raspian Buster Lite (Version July 2019) and Mycodo (after expansion of the file system, setting up raspi-config like enabling SSH, reboot). The only change I made was adding a PWM (GPIO) output and installed the dependencies (pigpio) after I was prompted to do so, but the problem remains.
I also uninstalled pigpiod inside Mycodo (Configure --> Raspberry Pi --> Service options: Configure pigpiod --> Uninstall pigpiod) and reinstall it in that way after rebooting - still the same problem.
Errors
The corresponding Daemon (ERROR) log:
Steps to Reproduce the issue:
Making a clear installation of Raspian Buster Lite and Mycodo, adding a PWM Output.
Additional Notes
I also did read #617 but it didn't solve my problem - after prompted to install the dependency, reboot - then adding GPIO, set up PWM and turn PWM % did not help.
The text was updated successfully, but these errors were encountered: