-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on "npm install johnny-five" with Windows 7 #48
Comments
The latest Serialport supports Windows com ports however Johnny-Five has never been tested on Windows (that I know of). At this point I can say confidently that even if it had installed, it still wouldn't work because Johnny-Five's serial port detection only looks in I dont have a Windows machine at my disposal to do the work required to support the OS. Sorry :( |
Ok, i think it is time for the Virtual Mashine now. |
I know it's a pain in the ass, but I'd like to encourage you to try and contribute the support for windows :) |
I will have a look into it. 2012/8/8 Rick Waldron [email protected]
|
CC Myself FWIW I was able to get this installed with a simple npm install and have this working to a point, but firmata seems to hang on trying to connect, spitting back data endlessly. Added onto the Win7 support issue at firmata/firmata.js#7 |
Really appreciate all the windows platform contributions (even if they're bug reports!) :) |
Try newest node (0.8) and newest npm But it seems like you don't have python in your path: "Can't find Python executable "python", you can set Try this: |
I had Python 3.x installed. I needed Python 2.7. Set my env.-variable: PATH=%PATH%;C:\Python27 npm install johnny-five was no problem than ... everything installed correctly. Well... and then we need to work on hat "/dev/..." in the johnny-five code. |
@ThomasDeutsch It's not too bad actually, the changes are pretty small. Rather than using the current grep comment, my approach so far has been either
Powershell right now is my preferred approach I think as it's simple, doesn't seem to require admin privs, and spits out the exact output that's needed. Once firmata is working on Windows properly, I'll be able to do some more testing. |
Are the windows port names always one of "COMn" where "n" is a number? |
I think this is node-serialport specific. I think serialport got that feature from serial-port2. |
Yes, @voodootikigod and @joeferner combined Serialport and Serialport2. We're thinking the same way—I asked about COMn b/c I saw the same reference as you... I think we're onto something :) Can we try to guess the COMm? |
you can use Windows Device Manager to identify the COMn values. |
I am confused about what the final issue is here, i feel like there are 8 different ones interleaved, what is still an issue ATM? Happy to help. |
@voodootikigod it's all good :) Johnny-Five does port detection for you, so we're brainstorming how to make it work on windows. @ThomasDeutsch @Jellyfrog @dcherman are working out implementation details :) |
Good luck on that, my response would be "Just use device manager". On Monday, August 13, 2012 at 11:34 AM, Rick Waldron wrote:
|
If you need a list of open ports you can use the serialport.list function. I updated the readme over on serialport with an example. On windows it will give you COM1, COM2, etc. On linux/osx it'll give you /dev/ttyUSB0 or whatever. |
Super helpful, thanks! |
You can find this in the serialport code: var serialport = require('../'); serialport.list(function (err, results) { for (var i = 0; i < results.length; i++) { but i always got an error from serialport.list ?! ... anyone got this working with windows? |
Yep, just tried serialport.list and it works beautifully. I'll try replacing the detection logic with serialport.list later tonight or tomorrow and see what happens. |
Thank you! I would like to help People to get the npm install working. Here are the steps it took. Install:
Configuration:
run "npm install johnny-five" from the project folder - DONE i am not sure about the 32-64-bit part. can anyone confirm that? |
Firmata should work now, too. There was also a problem with node-gyp today..... this was fixed too. |
Got it working with :
Going to look further to see what might be the problem with the newer versions of Nodejs. |
Hi, I have problems installing it on Win 8.1 with VS Express 2015. I get a lot of build errors during installation. Any idea what this could be? |
@Alexaas what version on Node.js is being used? If it's Node.js 4.x, the build errors are likely to be related to serialport which is in the process of being upgraded to support Node.js 4. If this is the case, see serialport/node-serialport#578 for further details.
Not sure, but would guess that it meant that a checkbox needed to be checked during the VS2010 install process. |
Same situation with windows 10 and VS Express 2015, NodeJS 4.1.1. |
@AlexDmr Node.js 4.x support is in progress. |
@rwaldron Could you please give an update here once it should work with Node.js 4.x? |
@rwaldron I propose creating an issue for node 4.x support that details the state of things that we can just point everyone to. Much like @jacobrosenthal did over on the serialport repo. I'm traveling all day, but will write one up tonight. |
@rwaldron , @ThomasDeutsch , @voodootikigod , I think ask people to install visual studio just for installing johnny-five is too heavy. VS is around 10GB. Can you think about light solution like gcc(mingw) on windows? |
That hasn't been necessary for almost two years—serialport auto builds pre-compiled binaries for every release |
We need to update the wiki |
@playteka @rwaldron |
Hi everyone.
I tried to install johnny-five on my Windows system - anyone tried this??
The text was updated successfully, but these errors were encountered: