-
Notifications
You must be signed in to change notification settings - Fork 26
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 install cncjs-pendant-ps3 #10
Comments
Hi, that looks like Python 2 syntax, and I bet you have Python 3 installed. What does |
Effectively it gives me : Python 3.9.2 |
Ok, i get python 2.7 but the error list is just incredible :/ |
Yes, you need both versions installed. Some libraries will use Python 2, others will use 3. Do you have aliases set? What does this print?
|
Twice gave me :
|
That looks good, thank you. The problem here is that a dependency (node-gyp) is not using the right Python version, I'm not sure why. Issues like this are often due to discrepancies in how Python is installed. It could also be caused by outdated versions in package.json. I don't have any ideas on how to fix this at the moment, but you might try searching for something like "node-gyp rebuild Error: Command failed: /usr/bin/python -c import sys". |
Thank you for driving me on it. I guess it is totally outdated last update on pendant was 5 years ago ... I have made a brand new cncjs install and i guess my hope i flying away that seems to complicated for me without any help ... |
Here is the result of the install :
|
The problem is in the "node-hid" module. Its purpose is to give the program direct access to USB "human input devices" - like keyboards - instead of letting the internal operating system driver handle them. That module has been outdated for years, and attempts to switch to a more recent version have been frustratingly difficult. Several years ago I tried to fix cncjs-pendant-keyboard which also uses node-hid in a similar manner. I eventually gave up because there were just too many tricky details. I knew that even if I "fixed" it, it would break the next time that someone else tried to use it, so I would waste a lot of time trying to help people who would require a lot of handholding and even then might not succeed. The super-tricky problem is that, by going directly to the USB layer and thus bypassing the operating system's input layer, the program has to content with a lot of low-level details that professional (paid) programmers spend months refining so they work just right. The interface at that level is not clean and simple, but rather has a lot of "knobs" that must be handled just right if the system is to work robustly. Working at that level, it is not so difficult to get the program to work once in one environment, but very difficult to make it work for everybody and to continue to work as software versions change. Quite a few of the cncjs pendants are in the category of "the author got them working once, "helpfully" posted their work, then disappeared, leaving other people to deal with the long-term fallout". Basically, any pendant that has not had recent commits should be considered suspect. |
Thanks for that feedback :) I just was dreaming about something cool with my cnc ... I will do it in an otherway :) |
Hi, don't want to give up so fast seems some fork would work better as @balthisar one But gave this error on my PI
My some lights on it ? Thanks for reading |
@AnTeBiOss, you might post a bug report over at its own repository, instead of this one. The fix should be, though, to |
OMG it seems to work well :) @balthisar could you tell me how to configure Button map as i would like to use it ? Thanks a lot !!! |
@AnTeBiOss, you can have a look at |
Thank you for answer @balthisar , i will try but i'm not that dev killer i want :) |
Hi,
I'm desperatly trying to install and make work cncjs-pendant-ps3 wich made me dream about driving my cnc with a PS3 controller.
I followed all the steps with sudo, if not i got some permissions err
everything seems to be good until :
sudo npm install -g cncjs-pendant-ps3 --unsafe-perm
the return is :
May I get some help for that ?
Thanks for reading
The text was updated successfully, but these errors were encountered: