{"action":"created","issue":{"url":"https://api.github.com/repos/sandeepmistry/node-chip-io/issues/11","repository_url":"https://api.github.com/repos/sandeepmistry/node-chip-io","labels_url":"https://api.github.com/repos/sandeepmistry/node-chip-io/issues/11/labels{/name}","comments_url":"https://api.github.com/repos/sandeepmistry/node-chip-io/issues/11/comments","events_url":"https://api.github.com/repos/sandeepmistry/node-chip-io/issues/11/events","html_url":"https://github.com/sandeepmistry/node-chip-io/issues/11","id":166670626,"number":11,"title":"I2C over hard-coded /dev/i2c-1 not working","user":{"login":"ugate","id":944948,"avatar_url":"https://avatars.githubusercontent.com/u/944948?v=3","gravatar_id":"","url":"https://api.github.com/users/ugate","html_url":"https://github.com/ugate","followers_url":"https://api.github.com/users/ugate/followers","following_url":"https://api.github.com/users/ugate/following{/other_user}","gists_url":"https://api.github.com/users/ugate/gists{/gist_id}","starred_url":"https://api.github.com/users/ugate/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ugate/subscriptions","organizations_url":"https://api.github.com/users/ugate/orgs","repos_url":"https://api.github.com/users/ugate/repos","events_url":"https://api.github.com/users/ugate/events{/privacy}","received_events_url":"https://api.github.com/users/ugate/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-07-20T20:10:41Z","updated_at":"2016-07-21T22:24:22Z","closed_at":null,"body":"I tested a PCA9685 with chip-io (master branch) and noticed that nothing was happening using the [johnny-five example](http://johnny-five.io/examples/servo-PCA9685/). It looks like [errors are just consumed in i2c.js](/sandeepmistry/node-chip-io/blob/master/lib/chip-io.js#L203) so there's no way of knowing unless debugging (headless chip, used `node --inspect` flag with devtools from remote PC). Maybe a better approach when encountering errors would be to emit an `error` event instead of throwing or ignoring? I noticed that `chip-io.js` uses a hard-coded **1** for the bus value in `/dev/i2c-1` [here](/sandeepmistry/node-chip-io/blob/master/lib/chip-io.js#L193) and [here](/sandeepmistry/node-chip-io/blob/master/lib/chip-io.js#L245), but a `ls /dev` only shows `i2c-0` and `i2c-2` (Linux 4.4.11-ntc). \r\n\r\n@rwaldron I'm trying to understand what the proper way to pass in the bus identifier when using the [johnny-five API](http://johnny-five.io/api/board/#i2cconfigmilliseconds)/`Board.i2c` functions for boards that support more than one I2C bus?"},"comment":{"url":"https://api.github.com/repos/sandeepmistry/node-chip-io/issues/comments/234402585","html_url":"https://github.com/sandeepmistry/node-chip-io/issues/11#issuecomment-234402585","issue_url":"https://api.github.com/repos/sandeepmistry/node-chip-io/issues/11","id":234402585,"user":{"login":"rwaldron","id":27985,"avatar_url":"https://avatars.githubusercontent.com/u/27985?v=3","gravatar_id":"","url":"https://api.github.com/users/rwaldron","html_url":"https://github.com/rwaldron","followers_url":"https://api.github.com/users/rwaldron/followers","following_url":"https://api.github.com/users/rwaldron/following{/other_user}","gists_url":"https://api.github.com/users/rwaldron/gists{/gist_id}","starred_url":"https://api.github.com/users/rwaldron/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rwaldron/subscriptions","organizations_url":"https://api.github.com/users/rwaldron/orgs","repos_url":"https://api.github.com/users/rwaldron/repos","events_url":"https://api.github.com/users/rwaldron/events{/privacy}","received_events_url":"https://api.github.com/users/rwaldron/received_events","type":"User","site_admin":false},"created_at":"2016-07-21T22:24:22Z","updated_at":"2016-07-21T22:24:22Z","body":"What version of Node.js is on the Chip?"}}
{"actor":{"display_login":"rwaldron"}}