5c57e614e9
added default consumer socket to interrupt process, named pipe by default added commands.interrupt to consumer namespace so pushed packets from interrupt process will be handled. interrupt process could still 'send' the packet if that is prefered but command would be prefaced with 'interrupt.' Fixed the interrupt:reset ready observer to it will get the interrupt ready state correctly. ready state after reset is sent in outgoing packet so action can be taken if something goes wrong. creates an iterrupt name for observers based on passed opts.interrupt.name or 'interrupt' by default. Improved switches example that uses options read from yaml file. Desgined to work with multi intererupt example and i2cbus example. |
||
|---|---|---|
| examples | ||
| src | ||
| test | ||
| .eslintrc.js | ||
| .gitignore | ||
| .npmignore | ||
| package.json | ||
| readme.md | ||
readme.md
uCOMmandIt MCP - An I2C Micro Chip NodeJS Class Library
What is it
This module contains ES6 Classes for the Micro Chip (MCP) I2C GPIO (general purpose input output) expander chips. The chips contain 8 GPIO pins organized in ports. The MCP23008 has a single port and the MCP23017 has two ports (A,B). Each port has a single interrupt pin which can be used to determine when any pin of a port has changed state. With this module after creating an instance of a chip class you'll be able to easily read and write to the chip's pins with simple methods such as .read(),.on()',.off(), and .toggle()
What's it good for
Lots of I2C devices make use of these chips. In particular many of Control Everything's boards use these chips including their relay boards and their general purpose DIO boards. To control and read them (and any other board using these chips) using nodejs all you need is this module!
Prerequisites
-
You'll need a computer with an I2C interface which is typically a set of reserved GPIO pins found on most ARM based single board computer (SBC) like the Raspberry Pi. You'll probably want a pin header shield (e.g. Control Everything's RPi shield) to make connecting your IC2 MCP device to your SBC easy.
-
You'll need to have an I2C bus interface library with NodeJS bindings and it will need to compile on your specific SBC. One such library, Fivdi's I2C-Bus, already exists for the Raspberry Pi and will likely compile on many other ARM7 SBCs (e.g. BeagleBone Black). This module makes use the Fivdi I2C library via the UCI-I2C module. It is possible that other I2C libraries with a nodeJS binding could be used but for now the Fivdi library is the only one.
Getting Started
-
Prepare an SBC (e.g. Raspberry Pi) with an appropriate OS (e.g. Raspbian).
-
Connect your MCP based I2C device and check that the SBC can talk to it using
i2cdetectwhich is part of thei2ctoolslinux package. Assuming your I2c linux device is number 1 that would besudo i2cdetect -y 1 -
Install the latest nodeJS. NOTE! You MUST be using at least node 7.6 for this module to work so just load and maintain the latest version for the best result. Node source has the easiest way to do that.
Using Ubuntu curl -sL https://deb.nodesource.com/setup_7.x | sudo -E bash - sudo apt-get install -y nodejs Using Debian, as root curl -sL https://deb.nodesource.com/setup_7.x | bash - apt-get install -y nodejs -
Start an npm project and install the uci mpc module
npm init
npm install @uci/mcp
- Now simply run the
sample.jscode in thedemo/directory by typing
npm run sample
if all went well the device should have been written to and read back and you can confirm the writes and reads were correct by looking at the console output. If you hook up a mcp based relay board you should see the relays being turned on and off.
Use the sample.js code as the basis for your mcp i2c project.