GPIO FAN Controller

This is a lightweight plugin dedicated for controlling a fan via Raspberry Pi GPIO pin. This plugin has the following features:

Convenient sidebar control
Adjustable FAN speed
Pin selection via settings
M106 / M107 GCODE support
Independent GCODE control using optional fan index

IMPORTANT - FAN Compatibility

This plugin is only intended to drive an external brushless DC FAN via MOSFET driver circuit. A MOSFET must be used to drive the FAN since the PI is not capable of providing adequate current to the FAN.

It is a also a good idea to use a separate power supply to drive the FAN since the PI power supply might not have adequate current to drive the PI + FAN. See wiring digram below as an example of how to interface to a 12V DC FAN.

Pictures

Installation

URL:

https://github.com/z4gunn/OctoPrint-GpioFanController/archive/master.zip

Command line:

pip install "https://github.com/z4gunn/OctoPrint-GpioFanController/archive/master.zip"

Registration date: 04 Jul 2021

Active instances the past month: Installed on at least 136 instances

New installs the past week: At least 3 new installations

GitHub stats (Login)

Latest Release: 0.2.1
released on 18 Jul 2021
Releases: 4
Stars: 8
Issues: 10 open, 2 closed
Last push: 02 Aug 2021

Tags: fan gpio pwm

Compatibility Information

OctoPrint: all versions
Operating Systems: Linux, Windows, Mac OS X, FreeBSD
Python: >=3,<4

Author: Erik Gundersen

Homepage: https://github.com/z4gunn/OctoPrint-GpioFanController

Source: https://github.com/z4gunn/OctoPrint-GpioFanController

License: AGPLv3

Something wrong here?

If there is something wrong with this listing (broken links & images etc), please report it here.

If this plugin has been confirmed as abandoned by its maintainer, please report it here.

If this plugin is doing something suspicious (e.g. weird network activity, unannounced tracking, ...) and the maintainer is not cooperating in getting to the bottom of that, please report the plugin as suspicious here.

Report bugs or feature requests for the plugin to the plugin author (e.g. on the plugin's homepage) please, not here!