PCA9685 4-Channel 8W 12V FET Driver Proportional Valve Controller with IoT Interface
Highlights
- 12V PWM Power FET Controller Shield with IoT Interface
- Compatible with Particle Photon, Electron, or Bluz
- Adaptable to Arduino, PyCom, Raspberry Pi, Onion and more
- PCA9685 12-Bit 4-Channel 8W 12V Programmable Voltage Outputs
- Rated for Use with Inductive Loads
- Provides 12-Bit PWM Proportional Valve Control and Speed Control DC Motors
- Solid-State PWM Control of 12V Incandescent or High-Power LED Lighting
- 4 N-Channel BUK98150-55A 12V 5.5A Power Fets
- Designed for Resistive or Inductive Solid State DC PWM Control Applications
- I2C Expansion Port for Adding External Sensors or Controllers
- 4,096 Output Levels per Channel
This 4-Channel power FET driver allows 12-Bit variable control of high-current loads your favorite IoT communications technology via I2C communications. This device uses four BUK98150-55A power FETs, allowing PWM cloud control of 4 channels. Control DC Motor Speed, vary the opening of proportional valves, adjust brightness of LEDs or incandescent lighting from anywhere in the world. The BUK98150-55A is capable of controlling up to 12VDC and 5.5 Amps of current (8 Watts of Heat Dissipation), making it an ideal choice for inductive or proportional control of resistive loads. Compatible with 12VDC motors, pumps, valves, solenoids, high-power LEDs, incandescent lights, and many other types of devices. The PCA9685 chip is used as a driver for this controller, making communications easy and expandable to up to 62 devices on a single I2C port.
What is the NCD IoT Interface?
The NCD IoT Interface provides users with a means of changing or upgrading the IoT communications technology as new technologies emerge. The NCD IoT Interface is directly compatible with Particle Photon for WiFi communications, Electron for Cellular Communications, Bluz for Bluetooth. Optionally, adapters may be installed to provide a direct interface to Arduino Nano, Micro, USB, PyCom WyPy, Onion Omega, Raspberry Pi, and much more. The NCD IoT interface allows you to re-use your hardware so it never becomes obsolete! Based on I2C communications, the NCD IoT Interface uses only 2 GPIO lines of your microcontroller, freeing the rest of your CPU for other tasks.
nodeLynk™ IoT Device Expansion
This is a IoT Device which accepts a common processor and provides on-board sensing or control capabilities. This IoT device may be expanded to include additional hardware functionality using nodeLynk Expansion Devices. The NCD IoT socket found on IoT devices is capable of directly handling NCD ESP8266 and ESP32 series processors as well as Particle Photon and Particle Electron. We also manufacture many adapters for the NCD IoT socket for Arduino Nano, Micro, and Feather microprocessor modules. Between the socket is a nodeLynk connector, which is used for I2C Expansion.
What is nodeLynk?
Chain expansion devices using nodeLynk. Connect a wide variety of accessories to expand the capabilities of a nodeLynk compatible controller. Use nodeLynk to add Relay Controllers, Sensors, PWM Drivers, Displays, and a wide variety of 4-20mA, 0-10V ADCs and DACs, as well as a wide array of TTL & Isolated GPIO devices. All nodeLynk devices use I2C communications to chain devices together. nodeLynk is an easy way to expand functionality without soldering. nodeLynk allows expansion in seconds so you can focus on your software and firmware development.
Unlimited I2C Expansion
Based on our plug-and-play nodeLynk I2C interface standard, all NCD IoT devices are equipped with a nodeLynk I2C expansion port, making it easy to expand to a wide variety of sensors, current monitors, relay controllers, PWM controllers, and much more! We are always designing new nodeLynk expansions for our plug-and-play nodeLynk I2C framework. We are dedicated to building a product line of interconnected devices to simplify all forms of automation. Re-use or upgrade your hardware in seconds by selecting the modules that best fit your needs, and chaining them together using the included nodeLynk I2C expansion cables!
Mechanical Drawing
Wiring Diagrams
Documentation
Datasheets
Official Repository
Integration Notes
This controller is equipped with 4 12VDC outputs, which may be proportionally controlled with 4,096 levels of voltage output (12-Bit) using I2C communications. This device is suitable for proportional control of inductive or resistive loads, and may be used for pumps, valves, DC motor speed control, LED and incandescent light dimming, and much more. Integrated induction suppression capacitors and flyback diodes ensure a long life under heavy loading applications. See our wiring diagram for connection examples. Not for use with AC power applications. This device requires an external 12VDC Power Supply.
IoT Interface Compatibility
NCD IoT Interface devices are designed to plug in to many popular IoT computing platforms. This allows the “brains” from other manufacturers to directly plug into our devices for easy plug-and-play operation. IoT interface devices use I²C as the underlying communications technology. The notes below will guide you into plugging 3rd party IoT technologies into our devices, we will highlight any adapters that may be required in this section. Please note that all IoT Interface Devices act as a I²C Master Device, and may be expanded by connecting to any of our Cross-Platform nodeLynk I²C Slave Devices using the nodeLynk I²C Output.
NCD IoT Interface Direct Connection
The following devices directly plug into NCD IoT Interface controllers without a adapter.
- Particle Electron
- Particle Photon (Particle.io)
- Bluz Module (Bluz.io)
- ESP8266 Module
If using a Particle Photon or Particle Electron communications module, the PKFR Key Fob Receiver overlay shield may be used to add long-range wireless Key Fob remote control to the communications module.
NCD IoT Interface Adapters
Use the following adapters will adapt the IoT Interface for I2C communications with other popular computing platforms:
- Arduino Nano using the Arduino Nano Adapter
- Arduino Micro using the Arduino Micro Adapter
- Onion Omega 1&2 using the OC Adapter
- Pycom WiPy using the WiPy Adapter
- Pycom WiPy2 & LoPy using LoPy Adapter
- Adafruit Huzzah ESP8266 using the Adafruit Huzzah Adapter
- Windows using USB Interface and the USB IoT Interface Adapter
Convert IoT to I2C Interface Devices
- This device may be converted to an I²C slave device using the I2C to IoT Interface Adapter, ideal for use with Raspberry Pi, Beaglebone, Arduino Uno, and BridgeX5.
Arduino Interface
- Use the I2C to IoT Interface Adapter and a Arduino Uno Interface Adapter
- Use the I2C to IoT Interface Adapter and a Arduino Nano I²C Shield
- Use the I2C to IoT Interface Adapter and plug into any Arduino Nano Master Device
- Use the I2C to IoT Interface Adapter and plug into any Arduino Micro Master Device
- Use the I2C to IoT Interface Adapter and plug into any Arduino Due Master Device
BeagleBone Interface
- Use the I2C to IoT Interface Adapter and a BeagleBone I²C Interface Adapter
Banana Pi Interface
- Use the I2C to IoT Interface Adapter and a Banana Pi I²C Interface Adapter
C.H.I.P. Interface
- Use the I2C to IoT Interface Adapter and a C.H.I.P. I²C Interface Adapter
Raspberry Pi Interface
- Use the I2C to IoT Interface Adapter and a Raspberry Pi I²C Interface Adapter
- Use the I2C to IoT Interface Adapter and a Raspberry Pi 2/3 I²C Interface Adapter
- Use the I2C to IoT Interface Adapter and a Raspberry Pi Zero I²C Interface Adapter
Windows 8/10 PC Interface
- Use the I2C to IoT Interface Adapter and a USB to I2C Converter
- Use the I2C to IoT Interface Adapter and a BridgeX5 Series Controller
Key Fob Compatibility
NCD IoT Interface devices are also compatible with a 418MHz Key Fob receiver (Part Number: PKFR), allowing your Particle Electron, Photon, or Bluz to receive and process remote Key Fob commands up to 750 feet away. Up to 40 remote controls may be associated to the PKFR. Program your IoT communications module to receive wireless remote control commands using a Key Fob. Compatible with 1, 2, 3, 4, 5, and 8-Button MS Series Key Fobs from Linx Technologies.