Having troubles running the library with my Raspberry Pi 4. Getting this error:

Error: We dont recognize your revision (Revision        : b03112,b03112). Sorry! get in touch and let me know so I'll add it

Came across this closed issue which is similar to mine: #123. It looks like the library might just need to include this revision? Thanks!

My motor is getting hot while sitting idle (currently 50.7 C). Can a Hold Mode be implemented to reduce or turn-off the holding current when stationary?

I've read https://forums.adafruit.com/viewtopic.php?f=25&t=41048 and https://forums.adafruit.com/viewtopic.php?f=31&t=27322&p=140423 on the issue, which may be of use.

My application will require 24/7 run time and the majority of that no motion is needed and no holding force is required.

Thanks!

Version 3.4.0 of mocha just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

/home/pi/Documents/Node Projects/node_modules/motor-hat/dist/index.js:42
throw new Error(err);
^

Error: Error: default$
at errHdlr (/home/pi/Documents/Node Projects/node_modules/motor-hat/dist/index.js:42:11)
at wrapcb (/home/pi/Documents/Node Projects/node_modules/parambulator/parambulator.js:850:18)
at /home/pi/Documents/Node Projects/node_modules/parambulator/parambulator.js:968:11
at Object.fail (/home/pi/Documents/Node Projects/node_modules/parambulator/parambulator.js:592:12)
at validatedefaults (/home/pi/Documents/Node Projects/node_modules/parambulator/parambulator.js:939:29)
at Object.Parambulator.self.validate (/home/pi/Documents/Node Projects/node_modules/parambulator/parambulator.js:966:7)
at MotorHat (/home/pi/Documents/Node Projects/node_modules/motor-hat/dist/index.js:298:11)
at Object. (/home/pi/Documents/Node Projects/sheldon.js/example/cli/shell.js:9:36)
at Module._compile (module.js:662:30)
at Object.Module._extensions..js (module.js:673:10)

Hi. Getting the following exception when executing the module on my Pi Zero.

Error: We dont recognize your revision (Revision : 19000c1,19000c1). Sorry! get in touch and let me know so I'll add it

Version 12.1.0 of eslint-config-airbnb-base was just published.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-airbnb-base is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 15.9.15 of semantic-release was just published.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 11.1.2 of eslint-config-airbnb-base just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-config-airbnb-base is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 15.4.3 of semantic-release was just published.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 11.3.2 of eslint-config-airbnb-base just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-config-airbnb-base is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

I have seen that there is another ticket open for node 13.9.0, but I thought it was worth opening a new ticket for the stable version of node. It starts with the i2c-bus version. That does not work. I have tried forking ang changing the version to 5.1.0, but that opens a whole new can of worms. Is there any way to get this working? What version of node does it work on?

edit:
I have tried your suggestion from the other ticket and installed using:
npm install github:jcane86/motor-hat#greenkeeper/i2c-bus-2.0.0
and that command finishes successfully, but the node_modules/motor-hat directory only contains The license, readme.md and package.json at that point.

npm list:

[email protected] /home/pi/node-projects/motor
└─┬ [email protected] (github:jcane86/motor-hat#f64a863e6ad02a19f731df489c3b7bb15f54ba8e)
  ├── [email protected]
  ├─┬ [email protected]
  │ └── [email protected]
  ├─┬ [email protected]
  │ ├─┬ [email protected]
  │ │ └── [email protected]
  │ └── [email protected]
  ├─┬ [email protected]
  │ ├─┬ [email protected]
  │ │ └── [email protected]
  │ ├── [email protected]
  │ └── [email protected]
  ├── [email protected]
  └─┬ [email protected]
    └── [email protected] deduped

I also tried going into that directory and running npm install and after that npm run build. The error that showed up was this:

> [email protected] prebuild /home/pi/node-projects/motor/node_modules/motor-hat
> rimraf dist


> [email protected] build /home/pi/node-projects/motor/node_modules/motor-hat
> babel --copy-files --out-dir dist --ignore test/ lib

lib doesn't exist
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] build: `babel --copy-files --out-dir dist --ignore test/ lib`
npm ERR! Exit status 2
npm ERR! 
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2020-03-18T18_11_43_856Z-debug.log

The debug log contains this:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'build' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle [email protected]~prebuild: [email protected]
6 verbose lifecycle [email protected]~prebuild: unsafe-perm in lifecycle true
7 verbose lifecycle [email protected]~prebuild: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/node-projects/motor/node_modules/motor-hat/node_modules/.bin:/home/pi/node-projects/motor/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
8 verbose lifecycle [email protected]~prebuild: CWD: /home/pi/node-projects/motor/node_modules/motor-hat
9 silly lifecycle [email protected]~prebuild: Args: [ '-c', 'rimraf dist' ]
10 silly lifecycle [email protected]~prebuild: Returned: code: 0  signal: null
11 info lifecycle [email protected]~build: [email protected]
12 verbose lifecycle [email protected]~build: unsafe-perm in lifecycle true
13 verbose lifecycle [email protected]~build: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/node-projects/motor/node_modules/motor-hat/node_modules/.bin:/home/pi/node-projects/motor/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
14 verbose lifecycle [email protected]~build: CWD: /home/pi/node-projects/motor/node_modules/motor-hat
15 silly lifecycle [email protected]~build: Args: [ '-c', 'babel --copy-files --out-dir dist --ignore test/ lib' ]
16 silly lifecycle [email protected]~build: Returned: code: 2  signal: null
17 info lifecycle [email protected]~build: Failed to exec build script
18 verbose stack Error: [email protected] build: `babel --copy-files --out-dir dist --ignore test/ lib`
18 verbose stack Exit status 2
18 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
18 verbose stack     at EventEmitter.emit (events.js:311:20)
18 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
18 verbose stack     at ChildProcess.emit (events.js:311:20)
18 verbose stack     at maybeClose (internal/child_process.js:1021:16)
18 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
19 verbose pkgid [email protected]
20 verbose cwd /home/pi/node-projects/motor/node_modules/motor-hat
21 verbose Linux 4.19.97-v7l+
22 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
23 verbose node v12.16.1
24 verbose npm  v6.13.4
25 error code ELIFECYCLE
26 error errno 2
27 error [email protected] build: `babel --copy-files --out-dir dist --ignore test/ lib`
27 error Exit status 2
28 error Failed at the [email protected] build script.
28 error This is probably not a problem with npm. There is likely additional logging output above.
29 verbose exit [ 2, true ]

Any ideas?

Version 15.6.3 of semantic-release was just published.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Hi. Trying to made this library work for nanopi m4 with nanonat motor and found a bug that busnum variable is not in opts for pmwlib.
If it is possible, can you please add it into code to avoid extra patches for non-raspberry platforms?

diff --git a/lib/index.js b/lib/index.js
index 8187714..591a7cf 100644
--- a/lib/index.js
+++ b/lib/index.js
@@ -211,7 +211,7 @@ module.exports = function MotorHat(opts) {
    * or in second parameter to callback if callback provided, to enable chaining.
    */
   const init = function init(cb) {
-    const pwmopts = { i2c, address: options.address };
+    const pwmopts = { i2c, address: options.address, busnum: options.busnum };
     const self = this;
     pwm = pwmlib(pwmopts);
 

Thanks.

Hi, thanks for updating your module! It installs perfectly, but when I started using it, it told me to get back in touch with you :-)

Error: We dont recognize your revision (Revision	: c03112,c03112). Sorry! get in touch and let me know so I'll add it

Let me know if I can do anything to help.

The devDependency semantic-release was updated from 15.9.15 to 15.9.16.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency semantic-release was updated from 15.13.11 to 15.13.12.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hello,

I installed the module and tried to run the example code that was provided. But I keep getting this error:

`pi@raspi:~/RaspiStepperTests $ node StepperHatTest.js
/home/pi/RaspiStepperTests/node_modules/motor-hat/dist/index.js:90
pinAloc[pins[stepper.W1].PWM] = true;
^

TypeError: Cannot read property 'PWM' of undefined
at /home/pi/RaspiStepperTests/node_modules/motor-hat/dist/index.js:90:31
at Array.map ()
at checkPins (/home/pi/RaspiStepperTests/node_modules/motor-hat/dist/index.js:89:17)
at init (/home/pi/RaspiStepperTests/node_modules/motor-hat/dist/index.js:127:5)
at exports (/home/pi/RaspiStepperTests/node_modules/motor-hat/dist/index.js:143:3)
at Object. (/home/pi/RaspiStepperTests/StepperHatTest.js:12:36)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)
at tryModuleLoad (module.js:470:12)
`

What am I doing wrong? It seems it cannot even initiate the motor.

Moving the servo works (even though I think not over its whole angular range, but at least it moves).

I am really new to robotics and even the Pi itself, and hours and hours of googling did not get me anywhere, so I'm sorry to bother.

Kind regards,

Triadager

Version 4.1.4 of sinon was just published.

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 15.9.5 of semantic-release was just published.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency semantic-release was updated from 16.0.3 to 16.0.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The library should support asynchronous access to all motor functions.

Version 5.0.9 of sinon was just published.

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 15.5.3 of semantic-release was just published.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 4.1.0 of isparta was just published.

This version is covered by your current version range and after updating it in your project the build failed.

isparta is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 2.3.5 of sinon just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As sinon is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Version 12.0.1 of eslint-config-airbnb-base just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-config-airbnb-base is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 15.5.2 of semantic-release was just published.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 5.0.2 of mocha was just published.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hi, I'm getting the following error when attempting to initialize my application:

/home/pi/intervalometer/node_modules/i2c-bus/i2c-bus.js:257
  i2c.writeByteSync(peripheralSync(this, addr), cmd, byte);
      ^

Error: , Remote I/O error
    at Error (native)
    at Bus.writeByteSync (/home/pi/intervalometer/node_modules/i2c-bus/i2c-bus.js:257:7)
    at setAllPWM (/home/pi/intervalometer/node_modules/motor-hat/dist/pwm.js:148:9)
    at init (/home/pi/intervalometer/node_modules/motor-hat/dist/pwm.js:173:5)
    at exports (/home/pi/intervalometer/node_modules/motor-hat/dist/pwm.js:185:3)
    at init (/home/pi/intervalometer/node_modules/motor-hat/dist/index.js:124:11)
    at exports (/home/pi/intervalometer/node_modules/motor-hat/dist/index.js:142:3)
    at Object.<anonymous> (/home/pi/intervalometer/server/app.js:47:53)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)

Any ideas how to go about fixing this? Thanks in advance!

[email protected] install /home/pi/Public/agro/node_modules/motor-hat/node_modules/i2c-bus
node-gyp rebuild

gyp WARN EACCES current user ("pi") does not have permission to access the dev dir "/root/.cache/node-gyp/13.9.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/home/pi/Public/agro/node_modules/motor-hat/node_modules/i2c-bus/.node-gyp"
make: Entering directory '/home/pi/Public/agro/node_modules/motor-hat/node_modules/i2c-bus/build'
CXX(target) Release/obj.target/i2c/src/i2c.o
In file included from ../../nan/nan_converters.h:67,
from ../../nan/nan.h:202,
from ../src/i2c.cc:2:
../../nan/nan_converters_43_inl.h: In static member function ‘static Nan::imp::ToFactoryBasev8::Boolean::return_t Nan::imp::ToFactoryv8::Boolean::convert(v8::Localv8::Value)’:
../../nan/nan_converters_43_inl.h:18:69: error: no matching function for call to ‘v8::Value::ToBoolean(v8::Localv8::Context)’
val->To ## TYPE(v8::Isolate::GetCurrent()->GetCurrentContext())
^
../../nan/nan_converters_43_inl.h:22:1: note: in expansion of macro ‘X’
X(Boolean)
^

Log file attached.

Seems to be a problem with the i2c-bus module

pi@raspberrypi:/Public/agro $ uname -r
4.19.97-v7l+
pi@raspberrypi:/Public/agro $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
pi@raspberrypi:~/Public/agro $

motor1.log

The devDependency eslint was updated from 6.7.2 to 6.8.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 15.6.0 of semantic-release was just published.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴