• Firmware (pre-built) for Teensy LC/3.5/3.6/3.2
• Flash instructions
• UI/Qt application release (pre-built, signed?)

Related requirements:

• #1 (Advanced configuration)
• #3 (Documentation)
• #5 Circuit schematic (or wiring diagram)
• #5 PCB layout?

Improve Simple001:

• Correct board mount hole locations
• Add jumpers or solder bridges to support 6th fan PWM on Teensy LC, 3.2, 3.5, 3.6, and 4.0
• Remove AREF<>VCC jumper
• Remove AGND<>GND solder bridge?

Not sure if these are distro issues, or just issues in general. Trying to follow the istructions @ https://mstrthealias.gitbook.io/teensy-fan-controller/build-instructions/setup, can't really get anywhere.

git clone https://github.com/mstrthealias/TeensyFanController.git
git submodule init
git submodule update

looks like it needs to be

git clone https://github.com/mstrthealias/TeensyFanController.git
cd TeensyFanController
git submodule init
git submodule update

However, $ git submodule update throws all sorts of publickey errors. Assuming that command wasn't 100% necessary:

~$ cd TeensyFanController/
TeensyFanController$ ARDUINO_DIR=/opt/Arduino make
Makefile:12: *** Invalid ARDUINO_DIR.  Stop.

Thats as far as I got with that. Trying to build the compile the Arduino project right in Arduino IDE didn't work either. (Using "Teensyduino"). Here I tried it with a board setup for Teensy 4.0 which I would hope to be able to use, but it failed for 3.x as well.

Arduino: 1.8.13 (Linux), TD: 1.53, Board: "Teensy 4.0, Serial, 600 MHz, Faster, US English"

In file included from /tmp/arduino_build_491770/sketch/runtime_config.h:20:0,
                 from /home/justin/TeensyFanController/teensy_fan_controller/src/src.ino:3:
/tmp/arduino_build_491770/sketch/runtime_config_v1.pb.h:6:16: fatal error: pb.h: No such file or directory
compilation terminated.
Error compiling for board Teensy 4.0.

Complete an initial version of documentation:

• Usage/Getting Started
• Example data
• Detailed configuration
• PID tuning
• Hardware constraints (fe. no-save on Teensy LC, pin setup, etc.)

To support a possible RuntimeConfigV2, use a union message to wrap the RuntimeConfigV1 protobuf.

Fe.:
https://developers.google.com/protocol-buffers/docs/techniques#union
https://github.com/nanopb/nanopb/tree/master/examples/using_union_messages

Support advanced fan configuration(s), to provide a complete fan controller, with an ABI more similar to those controlled by liquidctl:

• Multiple PID support (1 PID per temperature sensor)
• Multiple temperature-fan % table support (table per fan/not-profile based)
• Fixed speed support

Technical details (in collaboration with Jonas @ liquidctl):

Notes:

• %-table is saved in each fan config
• PID config is saved in each sensor config

FanConfig->source (CONTROL_SOURCE):

• WATER_SUPPLY_TEMP
• WATER_RETURN_TEMP
• CASE_TEMP
• AUX1_TEMP
• AUX2_TEMP
• VIRTUAL_DELTA_TEMP

FanConfig->mode (CONTROL_MODE):

• TBL
• PID
• FULL

Hi Jack,
I have a project that I set aside, and am just getting back to. Amplifier controller, but it incorporates a fan control, and I was looking at your project for reference. I saw that on your schematic you show power and ground going into the fan through pins 3 and 4 respectively. Other documentation shows pins 2 and 1 for 12v and ground, including the original Intel pwm document, Since these are often implemented in headers that can be plugged in either way, it may not matter, but plugging the connector in the wrong way will probably fry it. Suggest you change the pin designations on your schematic.

• EAGLE library, schematic, and board files
• Documentation