Gandalf/OctoPrint-Enclosure
1
0
Fork 0
Code Issues 156 Pull Requests 6 Actions Packages Projects Releases 28 Wiki Activity

Multiple PWM doesn't work reliably #236

New Issue
Open
opened 2019-04-19 14:46:40 +01:00 by HaythamB · 3 comments
HaythamB commented 2019-04-19 14:46:40 +01:00 (Migrated from github.com)
Copy Link

Describe the bug
Setting up 3 separate PWM outputs for RGB 5050 LED strips doesn't change duty cycles reliably, ending up with this in the logs:

octoprint.plugins.enclosure - WARNING - An exception of type RuntimeError occurred on log_error. Arguments:
('A PWM object already exists for this GPIO channel',)

To Reproduce
Steps to reproduce the behavior:

  1. Create 3 PWM outputs, map to any default GPIO pin
  2. Try and change duty cycle normally, and then change another PWM duty cycle

Expected behavior
Duty cycle should trigger an output, nothing happens, and log outputs the above for debug.

**Describe the bug** Setting up 3 separate PWM outputs for RGB 5050 LED strips doesn't change duty cycles reliably, ending up with this in the logs: octoprint.plugins.enclosure - WARNING - An exception of type RuntimeError occurred on log_error. Arguments: ('A PWM object already exists for this GPIO channel',) **To Reproduce** Steps to reproduce the behavior: 1. Create 3 PWM outputs, map to any default GPIO pin 2. Try and change duty cycle normally, and then change another PWM duty cycle **Expected behavior** Duty cycle should trigger an output, nothing happens, and log outputs the above for debug.
HaythamB commented 2019-04-19 17:13:16 +01:00 (Migrated from github.com)
Copy Link

Tested this out further. Turns out it requires a restart of the OctoPrint service every time you change the PWM frequency. Working properly after restarting the service.

Tested this out further. Turns out it requires a restart of the OctoPrint service every time you change the PWM frequency. Working properly after restarting the service.
RoCkHeLuCk commented 2021-04-30 13:54:22 +01:00 (Migrated from github.com)
Copy Link

I have the same problem, if I change any PWM plugin configuration to, and in the log the message "A PWM object already exists for this GPIO channel", just restarting to get back to work.

I have the same problem, if I change any PWM plugin configuration to, and in the log the message "A PWM object already exists for this GPIO channel", just restarting to get back to work.
jacopotediosi commented 2025-05-01 17:50:47 +01:00 (Migrated from github.com)
Copy Link

Hi everyone, the recently merged PR #504 should have fixed this issue. Could you please reinstall the plugin and, if confirmed, close the issue?

Hi everyone, the recently merged PR #504 should have fixed this issue. Could you please reinstall the plugin and, if confirmed, close the issue?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
duplicate
enhancement
help wanted
invalid
Missing Data
Missing necessary data to troubleshoot
 question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Gandalf
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Gandalf/OctoPrint-Enclosure#236
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?