Beaglebone Black palette doesn't appear in the GUI left pane - No GPIO access.

[Michel Gerin]

Hello,

I installed Debian Wheezy and later Jessie. They both install flawless (only some warning related to node version 0.10.38 and 0.10.40 . But with these distributions, I get faults related to GPIO access.

Welcome to Node-RED

===================

15 Jan 15:58:29 - [info] Node-RED version: v0.12.5

15 Jan 15:58:29 - [info] Node.js  version: v0.10.38

15 Jan 15:58:29 - [info] Loading palette nodes

15 Jan 15:58:41 - [warn] ------------------------------------------

15 Jan 15:58:41 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node

15 Jan 15:58:41 - [warn] ------------------------------------------

15 Jan 15:58:41 - [info] Settings file  : /root/.node-red/settings.js

15 Jan 15:58:41 - [info] User directory : /root/.node-red

15 Jan 15:58:41 - [info] Flows file : /root/.node-red/flows_beaglebone.json

15 Jan 15:58:41 - [info] Server now running at http://127.0.0.1:1880/

15 Jan 15:58:41 - [info] Starting flows

15 Jan 15:58:41 - [info] [inject:tick] repeat = 1000

15 Jan 15:58:41 - [info] Started flows

15 Jan 15:58:42 - [error] [function:Toggle USR3 LED on input] TypeError: Cannot read property 'LOW' of undefined

15 Jan 15:58:44 - [error] [function:Toggle USR3 LED on input] TypeError: Cannot read property 'LOW' of undefined

15 Jan 15:58:45 - [error] [function:Toggle USR3 LED on input] TypeError: Cannot read property 'LOW' of undefined

15 Jan 15:58:46 - [error] [function:Toggle USR3 LED on input] TypeError: Cannot 

I got rid of the Debian distribution and installed Ubuntu console version.

I compiled and installed Node.js version 0.10.25  trying to install node-red (this version is mentionned on Beaglebone.org website. Unhappily node-red doesn't seems to install correctly.

Is there a way (guidelines) on a Beaglebone Black to install node-red on Ubuntu. 

I prefer to use Ubuntu as I have better access to my BBB GPIO and specially with a customized overlay.

Kind regards

Michel.

[Michel Gerin]

Sorry, I also forgot to mention that the BBB palette doesn't appear in the browser left pane.

Michel.

[Dave C-J]

so ... where are you now... ? The errors above are from the Debian install ? or ubuntu install ? Did you follow the page here http://nodered.org/docs/hardware/beagleboneblack.html ? As I updated that page just over Xmas I know it was working then :-(....

It should install on node -.10.25 OK - as long as you upgrade npm to npm@2.x first  - and will give a load of warnings about wanting 10.40 etc - but they are just warnings not errors.

[Dave C-J]

Hi - just retried with out latest version (Node-RED 0.12.5)...  on Debian Jessie image

 I get warnings about hoek, boom, cryptiles, i18next-client - but it installs ok..  last lines are

├── cr...@1.1.0 (moment-...@0.3.1)

└── node-red-nod...@0.1.0 (seria...@2.0.6)

I then cd ~/.node-red and installed the beaglebone nodes

and they install ok..  ending up with...

node-red-nod...@0.1.1 node_modules/node-red-node-beaglebone

└── octalbo...@1.1.1 (de...@2.2.0, ver...@1.6.0, i...@0.1.8, ep...@0.1.16, seria...@1.7.4)

and then I run node-red-pi

and it all starts up OK...

[Michel Gerin]

Hello Dave,

Thank you for your help.

The errors you see come from the Wheezy version. As mentioned, i really followed exactly the node-red guidelines from the link you sent.

In attachment you will find the main last "debian" install process. You can see that the installation occurs flawless.

Two problems:

1) the palette doesn't show up in the browser left pane. I don't know why ?

2) When I copy and paste the beaglebone node-red flow, everything is correctly installed ---> Deploy --> Deploy confirmation  --> errors are appearing when I start USR3 LED on or off. (my previous message).

I suppose that the problems comes from the GPIO access. But I am not skilled enough to know why (permissions). 

Until now, I use a custom overlay with the Beaglebone black and get access to the GPIO via python script.

I discovered node-red a couple a weeks ago and decided to test it yesterday.

If you think that I can use BBB Ubuntu console distribution and install node-red on it, I would prefer this solution. 

But in this case I would like to know if there is some particular installation steps.

On your link, it appears clearly that the installation guidelines are only valid for Debian.

Kind regards

Michel. 

[Mark Setrem]

To access the GPIO nodes on the beaglebone you need to install the beagle bone specific nodes as described on 

http://nodered.org/docs/hardware/beagleboneblack.html

BBB specific nodes

There are some BBB specific nodes now available in our node-red-nodes project on Github.

These give you direct access to the I/O pins in the simplest possible manner. The easiest way to install them is direct from npm.

For Debian Jessie based builds with kernel 4.x run the following commands in the root directory of your Node-RED install. This is usually ~/.node-red

mkdir -p ~/.node-red
cd ~/.node-red
npm install node-red-node-beaglebone

For previous versions of Debian (eg Wheezy) - use the older version of this node.

mkdir -p ~/.node-red
cd ~/.node-red
npm install node-red-nod...@0.0.8

 

[Michel Gerin]

Hello Mark,

As previously mentioned, I really followed exactly all the guidelines described in your link and Dave's one
That's why I don't understand why the BBB palette doesn't appear in the browser left pane . All other palette appear. I am using either Chrome, Firefox or Chromium on another BBB.
I am busy re-installing again BBB Ubuntu console. I will compile nodejs 0.10.40 version  and  try to reinstall node-red again --> uncomment one line in settings.js and try the example again.

Thank you for your advice

Michel.

[Mark Setrem]

i downloaded your "Node-red_installation_step" attachment.

Perhaps next time you could include ALL the install steps you took as there is no mention of installing the additional nodes in the attachment you provided.

[Michel Gerin]

Hello Mark,

I'll do it. But Iam back on a Ubuntu distribution. At this time 21:38 CET, le BBB is compiling nodejs version 0.10.40. It takes time ...

[Dave C-J]

Once you have node.js installed - it should be the same as for normal linux install

sudo npm install -g --unsafe-perm node-red

then install the nodes as before 

    cd ~/.node-red

    npm i node-red-nodes-beaglebone

One thing to make sure is that you are running Node-RED as the same user you are installing these nodes as...

or the "other" user won't see these nodes...

[Michel Gerin]

I made a full new installation. The user is the same during the whole install procedure.
I probably skiped a step yesterday (npm upgrade?)
Even if I now see the BBB palette in the browser left pane, I still get errors.
In the attached pdf file I made a copy of the main installation steps (all node-red installation steps as requested by Mark).
In order to more easily read this long file, I highlighted the main CLI commands in bold characters. My  own comments are highlighted in blue characters. Errors are displayed in red colors.
At the end I tested with a python script if I could still put, for example, BBB P9.12 output HIGH and LOW. That is the case. Is it possible that the bonescript module is not found ?
As I just started with node red I don't really know how to solve this issue.

Michel

[Dave C-J]

Ok - so once you get to the stage - "SUCCESS" - you should stop... and not do the editing settings.js piece...

then try the first flow from the docs page... or this - it should alternatively flash all four usr leds.

I think the original missing trick is that for some reason we now need root to access the gpio... - hence working when run as sudo.

[{"id":"68820342.977dfc","type":"inject","z":"d66162f6.299ea","name":"","topic":"","payload":"","payloadType":"date","repeat":"1","crontab":"","once":false,"x":197,"y":122,"wires":[["932da7db.6cd258","e85fb0cd.17a05","c36c86c2.3c9378","25ecc221.da133e"]]},{"id":"e308ade5.1cf75","type":"debug","z":"d66162f6.299ea","name":"","active":true,"console":"false","complete":"false","x":731,"y":102,"wires":[]},{"id":"932da7db.6cd258","type":"bbb-discrete-out","z":"d66162f6.299ea","pin":"USR0","inverting":false,"toggle":true,"defaultState":"0","name":"","x":481,"y":165,"wires":[["e308ade5.1cf75"]]},{"id":"e85fb0cd.17a05","type":"bbb-discrete-out","z":"d66162f6.299ea","pin":"USR1","inverting":false,"toggle":true,"defaultState":"0","name":"","x":482,"y":214,"wires":[[]]},{"id":"c36c86c2.3c9378","type":"bbb-discrete-out","z":"d66162f6.299ea","pin":"USR2","inverting":false,"toggle":true,"defaultState":"1","name":"","x":482,"y":261,"wires":[[]]},{"id":"25ecc221.da133e","type":"bbb-discrete-out","z":"d66162f6.299ea","pin":"USR3","inverting":false,"toggle":true,"defaultState":"1","name":"","x":481,"y":305,"wires":[[]]}]

I think the problem with the settings / docs is that it points to bonescript... which has not been updated in a while... whereas the octalbonescript project has been updated - so I should point to that instead.

[Michel Gerin]

I did what you requested ( bonescript commented again in settings.js).

-  I rebooted the BBB.
 
-  Using "sudo node-red-pi -v" gives the same errors as on my pdf file.

By changing user from sudo to root ----> the BBB palette doesn't show up in browser left pane and no error on the standard output (seems logic). I made extensive tests but each time with the same result:
either the BBB palette doesn't show up and no error appears or the BBB palette appears together with the errors

You mention "octalbonescript" project ? I'll have a look.

Thank you for your help. I really appreciate.

Have a nice week-end

Michel

[Jeronimo Avelar Filho]

Hi,

I am facing the same problems with a beaglebone black running the sd image bone-debian-8.2-tester-2gb-armhf-2015-11-12-2gb.img.  I found this thread googling for a tip about the possible cause of the problem and it seems to me that is related to bonescript , as I am not able to execute the test:

 node -pe "require('bonescript').getPlatform().bonescript" 

I have tried installing it and node-red still refuses to load the BBB pallete. 

Does anyone have a hint of what is happening ?

Thanks in advance

[Dave C-J]

OK - so some digging later... It seems that all the docs indicate that the only way to get access to the required GPIO via sys/class/... is by running as root.. If anyone finds any docs on how to do it without please let us know...

Also it is best to be running npm version 2.x as that seems to work better with nodes that need recompiling code

To install run (as root  or using sudo )

    npm i -g npm@2.x

    hash -r

But in the meantime... I'll change the instructions to make that more clear. Also it then makes sense to install the extra BBB nodes globally as root so rather than

    cd ~/.node-red

    npm i node-red-nodes-beaglebone

do this instead (as root) so use sudo if you are not currently root.

    npm i -g --unsafe-perm node-red-nodes-beaglebone

you can also cleanup the previous mess a bit...

    cd ~/.node-red/node_modules

    rm -r node-red-nodes-beaglebone

then start Node-RED - again as root (using sudo if necessary)

    node-red-pi

Also as mentioned earlier - bonescript no longer seems to be part of the basic distributions for BBB and has not been maintained enough to still work on newer versions on node... so I would advise using octalbonescript instead. 

[Jeronimo Avelar Filho]

It's Alive !! 

Thanks Dave , I have followed the instructions and finally the beaglebone pallete appeared and it is functioning. I tested with First Flow Hello World of http://nodered.org/docs/hardware/beagleboneblack.html and had success.

I have executed the following : 

    cd ~/.node-red/node_modules

    rm -r node-red-node-beaglebone

    sudo npm i -g --unsafe-perm node-red-node-beaglebone  

    sudo node-red-pi

    

I created a initialization script for /etc/init.d  ,the gist  is at https://gist.github.com/jeroavf/7f2c0945c3206f06a4df

 Thanks a lot !!

[Michel Gerin]

Hello Dave,

Thank you for the new guidelines you mentioned on the website. I am happy that Jeronimo was successful with his Debian distribution:

Your new (second) "Hello World" flow was also tested successfully with the following Ubuntu image.

bone-ubuntu-14.04.3-console-armhf-2015-12-11-2gb.img.xz

********************************************
ubuntu@arm:~$ sudo node-red-pi -v
[sudo] password for ubuntu:


Welcome to Node-RED
===================

17 Jan 21:29:13 - [info] Node-RED version: v0.12.5
17 Jan 21:29:13 - [info] Node.js  version: v0.10.25
17 Jan 21:29:13 - [info] Loading palette nodes
17 Jan 21:29:31 - [warn] ------------------------------------------
17 Jan 21:29:31 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node
17 Jan 21:29:31 - [warn] ------------------------------------------
17 Jan 21:29:31 - [info] Settings file  : /home/ubuntu/.node-red/settings.js
17 Jan 21:29:31 - [info] User directory : /home/ubuntu/.node-red
17 Jan 21:29:31 - [info] Flows file : /home/ubuntu/.node-red/flows_arm.json
17 Jan 21:29:31 - [info] Server now running at http://127.0.0.1:1880/
17 Jan 21:29:31 - [info] Starting flows
17 Jan 21:29:31 - [info] Started flows

Thank you again

Michel

[Dave C-J]

Great, glad we got it sorted. But do shot if any tweaks needed, out of van be clearer.

[Michel Gerin]

Hello Dave,

BeagleBone Black outputs were correctly set with Node-red and Bonescript.

I encountered errors with BeagleBone Black inputs. So I decided to get rid of Bonescript as you mentionned that Octalbonescript was more stable

Unhappily I am facing exactly the same problems as previously. The BBB palette doesn't appear in the GUI left pane. I suppose that when installing Octalbonescript, I may skip the following step:

sudo npm install -g --unsafe-perm node-red-node-beaglebone

and replace it by:

sudo npm install -g --unsafe-perm octalbonescript

 
Or not ?

Michel.

[Mark Setrem]

The simple answer is no.

The node node-red-node-beaglebone is not replaceable by octalbonescript.

The node would need to be modified to use octalbonescript rather than Bonescript But this has not yet been done

[Dave C-J]

Errr yes it has... And v0.1.1 drags in the octalbonescript prereq also so you don't have to.

[Dave C-J]

Mark

Errr yes it has... And v0.1.1 drags in the octalbonescript prereq also so you don't have to.

Michel - I thought it was working (from your post on 17th) ??? - or is this a different setup ? - On the new debian install there is no bonescript installed so nothing to remove...  so which OS version is this now on ?

regards

Dave Conway-Jones

[Michel Gerin]

Thank you for your quick reply,

the situation up to now:

• Yes, on the 17th Beaglebone palette was correctly displayed and I could activate BBB outputs correctly.
• I am still using the same Ubuntu version (see attached file)
  
• A couple of days ago I  to tried to use BBB inputs --> I encountered errors
• I made clean new installs ( the latest in attachment ) and only loaded "octalbonescript"
  
• Result ---> the BBB palette doesn't display and "octalbonescript" module is not found.

In the file attached, can you tell me what I am doing wrong ?

 

Michel

[Michel Gerin]

@Mark

You are right, it seems that I still need to load "node -red-nosde-beaglebone" to display the BBB palette in the browser left pane.

@ Dave

I still cannot load "octalbonescript" --> same error message as in my attached file


Michel.

[Michel Gerin]

I made the same test as some days ago:

While using a BBB output, I can set it HIGH and LOW
When using an Input, as soon as deployment occurs, errors are appearing (see attached file).
So I suppose that the source of the problem comes from the octalboenscript that doesn't load.
When I uncomment the line "octalbonescript:require('octalbonescript')," in the following part of settings.js, the console displays "cannot find octalbonescript".

functionGlobalContext: {
        // os:require('os'),
        octalbonescript:require('octalbonescript'),
        // jfive:require("johnny-five"),
        // j5board:require("johnny-five").Board({repl:false})
    },

So why this module octalbonescript doesn't load ? This time I installed the differents software module as "root". I suppose that permissions allowed a correct installation ?

Have you some idea about this issue ?

Michel.

[Dave C-J]

as well as installing as root... (correct) -  did you run Node-RED as root ?

You need to do so in order to have access to the pins.

I will add a trap to catch that error - so it won't crash - but if you don't have access it still won't work.

[Michel Gerin]

Hello Dave

I am sure I made the installation as root.  I posted the whole installation console output this morning. The file is called :

node-red_octalbonescript_beaglebone_black_ubuntu_console_all_installation_steps.pdf

This file is a 103 k just a few posts older today.  You can see the whole console output from npm upgrade to octalbonescript module installation.
The only installation details you cannot see is the one related to this command:

root@arm:~# cd .node-red/
root@arm:~/.node-red# npm install -g --unsafe-perm node-red-node-beaglebone
 
I must admit that this step was done after the octalbonescript module installation.
I suppose that it has no influence on the way the whole installation behaves ?
You can also check this particular installation by looking at the attached file to this post.
After this later installation step I can get the BBB palette again but the octalbonescript module still doesn't load.


The only result I have is always the same when uncommenting:
 

// octalbonescript:require('octalbonescript'),

---> Error loading settings file: /root/.node-red/settings.js
---> Error: Cannot find module 'octalbonescript'
 
Does Ubuntu have a different behaviour than Debian ?
I am not sure.

Michel.

[Nicholas O'Leary]

By uncommenting that line, make sure it doesn't have a trailing comma if it is the last line in the enclosing { } block - that would cause the parse error you are seeing.

--
http://nodered.org
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michel Gerin]

I have also the same behaviour when launching "node-red-pi -v" as sudo
I uncommented settings.js in usr/local/lib/node_modules/node-red/

Look at the result in the picture in attachment

Michel.

[Michel Gerin]

Hello Nick,

It's not the last line

 functionGlobalContext: {
        // os:require('os'),
        octalbonescript:require('octalbonescript'),
        // jfive:require("johnny-five"),
        // j5board:require("johnny-five").Board({repl:false})
    },

Michel.

[Nicholas O'Leary]

Ok, yes and no.

It is not literally the last line... but it _is_ the last line that isn't commented out.

 functionGlobalContext: {
        octalbonescript:require('octalbonescript')
    },

[Dave C-J]

Yes it is... the following lines are commented out - so that ends on being the last one... however for basic GPIO you don't need to uncomment octalbonescript in settings.js - that is only for advanced use inside functions...

I'm travelling at the moment (without access to my BBB) - so can't get hands on to try to recreate until next week.

The node-red beaglbone node includes the required library...

ubuntu should behave just fine - we use on laptops all the time.

[Michel Gerin]

OK, you may beat me. Sorry

But with the new edited file (correctly saved...I re-opened the file to be sure to display the correct modification) it seems that I still have the problem:

 functionGlobalContext: {
        // os:require('os'),
        octalbonescript:require('octalbonescript')

        // jfive:require("johnny-five"),
        // j5board:require("johnny-five").Board({repl:false})
    },

....
..

New test:

root@arm:~# node-red-pi -v

Error loading settings file: /root/.node-red/settings.js

Error: Cannot find module 'octalbonescript'

root@arm:~#

[Nicholas O'Leary]

you should run "npm install octalbonescript" in the directory that your settings file is.

[Dave C-J]

AAArgg - YOU DON'T NEED TO INSTALL OCTALBONESCRIPT . AND DON'T NEED IT IN SETTINGS.JS - to get the Basic GPIO nodes to work... 

Let's get that working first before we head off into this advanced area...

[Dave C-J]

... but then yes - when that works you can uncomment, remove the comment.

then as root

cd  /root/.node-red/

npm i octalbonescript

[Michel Gerin]

OK, I'll do it tomorrow as I have to leave the office now.

Thank you Dave and Nick for your help.
I really appreciate

Michel.

[Michel Gerin]

Hello

Well I wasn't successful:

The following gives even infinite permissions errors

when as root

cd  /root/.node-red/
npm i octalbonescript

I struggled the whole day with a different PC and a different µSD card to be sure not to use corrupted datas.

I decided to also try the latest official debian image:  bone-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img
With this image, I couldn't even load the BBB palette. Nevertheless, I followed steps by steps the installation guidelines described on the nodered website.

The Ubuntu image enabled at least to put BBB output pin high and low (without octalbonescript loaded). But, with this image, the BBB inputs palette when deployed gives immediatly the errors described previously (see picture with overlay text in one of my previous posts).

@Dave, if you have time to test the ubuntu image on your BBB next week,  it would be interesting to compare our respective results.
Take care of your BBB inputs by doing the test (pullup or pulldown resistors !!!)

Have a nice week-end

Michel.

[Dave C-J]

Michel

two posts ago I said not to install octalbonescript - why do you persist in doing so ?

Can you send a link to the exact Ubuntu image you are using so I can be sure to sue the same ?

Thanks

[Michel Gerin]

Hello Dave

You wrote: two posts ago I said not to install octalbonescript - why do you persist in doing so ?

OK let's start at the beginning:

After one of your previous helps, I wrote on 17th: Your new (second) "Hello World" flow was also tested successfully with the following Ubuntu image

At that time I really thought that everything was solved as I could set high and low one BBB output. With your flow the UserLED could be set ON and OFF.

After a couple of days I tested the inputs and noticed the errors I mentioned with a lot of details in several files.

You requested yesterday the following:

... but then yes - when that works you can uncomment, remove the comment.

then as root

cd  /root/.node-red/

npm i octalbonescript

I made the test today without installing octabonescript and wrote the following:

The Ubuntu image enabled at least to put BBB output pin high and low (without octalbonescript loaded). But, with this image, the BBB inputs palette when deployed gives immediatly the errors described previously (see picture with overlay text in one of my previous posts).

I cannot be more precise !  Without octabonescript loaded. After that step, loading or not loading octalbonescript won't change anything !

When I saw that this step wasn't succesful, I decided to try the Debian ...so why not trying to still load "octalbonescript" before deleting partition and reformating the µSD card. It doesn't harm anybody :-)
If you mean that I have to stop at that step, because you want to freeze the situation in order to make further test . Then OK just tell me.

I used this Ubuntu image: bone-ubuntu-14.04.3-console-armhf-2015-12-11-2gb.img.xz
Unhappily I don't see it anymore on the following link:  http://elinux.org/BeagleBoardUbuntu

I use the Ubuntu "console" version

In the content table you can reach the new image at: http://elinux.org/BeagleBoardUbuntu

4.3 raw microSD img

• 4.3.1 BeagleBone White/Black/Green

Please try to test the following one if you don't find the other in archives

https://rcn-ee.com/rootfs/2016-01-14/microsd/bone-ubuntu-14.04.3-console-armhf-2016-01-14-2gb.img.xz

If you are successful, I'll test this one again as soon as I come back . But keep in mind that the inputs make problems. Not only the LEDS must be tested. I don't know if I²C and serial won't also cause the same errors. So let's make it step by step.

Last word: I used bonescript with the  Angström distribution. But this distribution is not anymore a Beaglebone.org official one.
So I think I 'll still have  to octalbonescript if you tell me that it is more stable than bonescript.
 It's anyway easier to build script within the node element than to build it in separate function elements.

Very last word: an Open Source event occurs as every year in Brussels  and I'll go there ( www.fosdem.org ).
I'll have limited access to my Emails even if I'll check them from time to time.

Have a nice week-end

Michel.

 

[Dave C-J]

Hi Michel,

apologies for getting the wrong end of the stick with this/these problems... I have now pushed a new version of the node-red-node-beaglebone node to npm (0.1.3) - that does now handle inputs correctly...

so this simple flow now works (when two pins are wired together)

[{"id":"2e009e83.a5d592","type":"debug","z":"d66162f6.299ea","name":"","active":true,"console":"false","complete":"false","x":710,"y":420,"wires":[]},{"id":"d718b630.a52ab8","type":"bbb-discrete-out","z":"d66162f6.299ea","pin":"P8_7","inverting":false,"toggle":true,"defaultState":"1","name":"","x":450,"y":360,"wires":[[]]},{"id":"6549ff12.f1214","type":"inject","z":"d66162f6.299ea","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"x":200,"y":360,"wires":[["d718b630.a52ab8"]]},{"id":"8689456b.9304f8","type":"bbb-discrete-in","z":"d66162f6.299ea","pin":"P8_8","activeLow":false,"debounce":false,"outputOn":"both","updateInterval":"1","topic":"","name":"","x":440,"y":420,"wires":[["2e009e83.a5d592"],["2e009e83.a5d592"]]}]

I have yet to try it on Ubuntu - but I suspect this is the main problem that was breaking everything... 

[Michel Gerin]

Hello Dave,

You are right, now both output and input are operating correctly on the BeagleBone Black running Unbuntu.

I used the input in real environnement. To test the input "reaction", I used a push button that needs "debounce" configuration.
When "debounce" is true, I have no screen output results in the debug tab as you can see in the picture attached.

Can you also check the way you use the input software routine? Right after deployment, when the input push button is depressed, I generaly get max 3 input states in the debug tab (mainly 2 states).

Depressing the same push button a couple of times after the first action displays each time a minimum of  4 input states. I didn't modify the way I depressed it betwen the different configurations.
I recreated this situation a couple of times to be sure to be able to replicate it
I can understand that node-red is not a PLC program (Programmable LogicController), but it is perhaps worth looking at the code ?

I think that the system must keep the same behaviour whenever it is starting or running after some times.
 
Last question: I suppose that the "debounce time"  is in a certain way "hard coded" and cannot be changed easely without recompiling the sources ?.
I suppose also that using octalbonescript could allow me to build my own "debounce routine".

So what to do now to load 'octalbonescript" ? Sorry if I insist :-)

Michel.

[Michel Gerin]

Oups, I forgot to describe the push button type: it is a NO (normaly open) push button

Michel.

[Dave C-J]

Michel

I have now made the debounce time configurable on the input node so you should be good.

If you do need to do things in functions then yes you need to install (as root)

     npm i -g octalbonescript

and uncomment the line in settings.js (and remove the ,    ;-)

but I'd prefer to enhance the node enough so you don't have to ....

[Michel Gerin]

Hello Dave,

Great !!

"Debounce" works fine now even with the default settings "true" (without typing the ms bounce time, even if I tested that too :-;)  )

I won't have time to test octalbonescript before end of the week. I 'll let you know anyway !

What do you exactly mean by writing "but I'd prefer to enhance the node enough so you don't have to ...." ?

I'll need i²C and serial access on the BBB...are you planning to implement these features ?

In any case, thank you again for your quick replies leading to successful results

Kind regards

Michel.

[Michel Gerin]

I just want to add that debounce configuration has nothing to do with True or False with this new debounce routine. I don't know why I mentionned that logic. 
Probably because without configuring anything, the first behaviour was better than with the previous tests.

Michel.

[Dave C-J]

ah right - yes 12c and internal serial are probably a step too far for now :-)

If debounce is set without time then it will at least call the routine which will take some (minimal) time anyway... :-)

[Michel Gerin]

Hello Dave,

I had time to install octalbonescript node. But I encouter errors. The console output is copied in the attached file.

Have you an idea ?

Michel.  

[Dave C-J]

Hi - once again... is this Jessie or Ubuntu ? :-)

I have been through the instructions as per our docs and they are now working for me on Jessie.

(I had to change the example flow slightly as there is now a pinModeSync command that could be used)

[Dave C-J]

PS - for i2c and serial support you may wish to look at @monteslu 's gpio nodes - https://github.com/monteslu/node-red-contrib-gpio

[Michel Gerin]

Hello Dave,

I am still using Ubuntu Trusty for that issue. So, if you do think that octalbonescript installation is not compatible with Ubuntu Trusty, just tell me.
I won't bother you if am the only guy trying to use it with node-red nodes :-)

Michel.

[Michel Gerin]

OK, I'll have a look.

[John Stelmack]

Hello,  I am having the same problem - Beaglebone Pallet not showing up.
Beaglebone Black rev C.
Debian Jessie new install
NTP update and current time updated
From Webpage http://nodered.org/docs/hardware/beagleboneblack.html

Logged in as root -
1st tried install form directory ~/.node-red/  --- That did not work -
I saw instructions in this thread to install in directory ~/.node-red/node_modules

In directory ~/.node-red/node_modules/
root@beaglebone:~/.node-red/node_modules# npm i -g --unsafe-perm node-red-node-beaglebone

As root I run

node-red-pi
get the following output:root@beaglebone:~/.node-red/node_modules# sudo node-red-pi
Welcome to Node-RED
===================
5 Mar 01:01:40 - [info] Node-RED version: v0.13.3
5 Mar 01:01:40 - [info] Node.js  version: v0.10.41
5 Mar 01:01:40 - [info] Linux 3.8.13-bone79 arm LE
5 Mar 01:01:40 - [info] Loading palette nodes
Error reading directory /sys/devices/platform/ocp
5 Mar 01:01:53 - [warn] ------------------------------------------
5 Mar 01:01:53 - [warn] Failed to register 2 node types
5 Mar 01:01:53 - [warn] Run with -v for details
5 Mar 01:01:53 - [warn] ------------------------------------------
5 Mar 01:01:53 - [info] Settings file  : /root/.node-red/settings.js
5 Mar 01:01:53 - [info] User directory : /root/.node-red
5 Mar 01:01:53 - [info] Flows file : /root/.node-red/flows_beaglebone.json
5 Mar 01:01:53 - [info] Server now running at http://127.0.0.1:1880/
5 Mar 01:01:53 - [info] Starting flows
5 Mar 01:01:53 - [info] Started flows

My flow to send a generic e-mail from inject node works well.

The beaglebone nodes do not show up in the panel.  I've been at this for two days and cannot figure out what is wrong.

I also tried installing node_red_contrib_gpio, same results: no beaglebone nodes in panel.

I've tried from user debian and sudo - same thing, no beaglebone nodes. 

any guidance would be greatly appreciated. Any further information will be provided with pleasure.

Best regards,
John

[John Stelmack]

UPDATED to add output with -v option

root@beaglebone:~/.node-red/node_modules# node-red-pi -v
Welcome to Node-RED
===================
5 Mar 01:34:23 - [info] Node-RED version: v0.13.3
5 Mar 01:34:23 - [info] Node.js  version: v0.10.41
5 Mar 01:34:23 - [info] Linux 3.8.13-bone79 arm LE
5 Mar 01:34:23 - [info] Loading palette nodes
Error reading directory /sys/devices/platform/ocp
5 Mar 01:34:36 - [warn] ------------------------------------------
5 Mar 01:34:36 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node
5 Mar 01:34:36 - [warn] [bbb] VError: Unable to read from CapeMgr slots: ENOENT, no such file or directory '/sys/devices/platform/bone_capemgr/slots'
5 Mar 01:34:36 - [warn] ------------------------------------------
5 Mar 01:34:36 - [info] Settings file  : /root/.node-red/settings.js
5 Mar 01:34:36 - [info] User directory : /root/.node-red
5 Mar 01:34:36 - [info] Flows file : /root/.node-red/flows_beaglebone.json
5 Mar 01:34:36 - [info] Server now running at http://127.0.0.1:1880/
5 Mar 01:34:36 - [info] Starting flows
5 Mar 01:34:36 - [info] Started flows

[John Stelmack]

Hello All: UPDATE SOLVED. It found that the image I flashed on the BBB EMMC was in fact Wheezy and not Jessie. I created a new MicroSD card with (the real) Jessie and kernel 4.(something) and flashed the eMMC. apt-get update and upgrade. Set NTP clock and installed the BBB specific node-red nodes and all is well. The BBB specific nodes now show up in the pallet as they should.

I apologize for wasting anyone's time for my mistake.

Best regards,
John

[Dave C-J]

Phew - I thought we had cracked that one - was hoping not to go back to it for a while !

[John Stelmack]

Yeah.... I feel like an idiot. Not sure how I put the wrong image on the MicroSD card...

[Max Hadley]

This one just keeps on coming back - I've hit it now!

I've just flashed a 2GB BBB with Debian Jessie, using BBB-eMMC-flasher-debian-8.3-console-armhf-2016-03-20-2gb.img (from https://rcn-ee.com/rootfs/bb.org/testing/2016-03-20/console/) then installed node.js 4.4.0 following the instructions at https://github.com/nodesource/distributions#debinstall

I then installed node-RED (0.13.4), and node-red-node-beaglebone (0.1.5) as described on the node-RED website, in both cases using the -g and --unsafe-perm switches. While the installer was compiling the i2c optional dependency of octalbonescript, I got page after page of C++ syntax errors. Here is just a short excerpt:

make: Entering directory '/usr/lib/node_modules/node-red-node-beaglebone/node_modules/octalbonescript/node_modules/i2c/build'

  CXX(target) Release/obj.target/i2c/src/i2c.o

../src/i2c.cc: In function 'void setAddress(int8_t)':

../src/i2c.cc:21:28: error: 'New' is not a member of 'v8::String'

       Exception::TypeError(String::New("Failed to set address"))

                            ^

../src/i2c.cc:22:5: error: 'ThrowException' was not declared in this scope

     );

     ^

../src/i2c.cc: At global scope:

../src/i2c.cc:26:32: error: 'Arguments' does not name a type

 Handle<Value> SetAddress(const Arguments& args) {

                                ^

In file included from /root/.node-gyp/4.4.0/include/node/node.h:42:0,

                 from ../src/i2c.cc:1:

/root/.node-gyp/4.4.0/include/node/v8.h: In function 'v8::Handle<v8::Value> SetAddress(const int&)':

/root/.node-gyp/4.4.0/include/node/v8.h:885:13: error: 'v8::HandleScope::HandleScope()' is protected

   V8_INLINE HandleScope() {}

             ^

../src/i2c.cc:27:15: error: within this context

   HandleScope scope;

               ^

../src/i2c.cc:29:16: error: invalid types 'const int[int]' for array subscript

   addr = args[0]->Int32Value();

                ^

../src/i2c.cc:32:16: error: 'class v8::HandleScope' has no member named 'Close'

   return scope.Close(Undefined());

                ^

../src/i2c.cc:32:32: error: too few arguments to function 'v8::Local<v8::Primitive> v8::Undefined(v8::Isolate*)'

   return scope.Close(Undefined());

                                ^

This almost looks like the i2c package has not been updated to work with 4.4.x. However, it's an optional dependency, so I pressed on.

However, I get no Beaglebone palette section, and no beaglebone nodes! Running as a normal user, I get:

Welcome to Node-RED

===================

28 Mar 21:23:26 - [info] Node-RED version: v0.13.4

28 Mar 21:23:26 - [info] Node.js  version: v4.4.0

28 Mar 21:23:26 - [info] Linux 4.1.18-ti-r53 arm LE

28 Mar 21:23:26 - [info] Loading palette nodes

Optional package 'i2c' not loaded

28 Mar 21:23:36 - [warn] ------------------------------------------

28 Mar 21:23:36 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node

28 Mar 21:23:36 - [warn] [bbb] VError: Write to CapeMgr slots failed: EACCES: permission denied, open '/sys/devices/platform/bone_capemgr/slots'

28 Mar 21:23:36 - [warn] ------------------------------------------

28 Mar 21:23:36 - [info] Settings file  : /home/max/.node-red/settings.js

28 Mar 21:23:36 - [info] User directory : /home/max/.node-red

28 Mar 21:23:36 - [info] Flows file : /home/max/.node-red/flows_redbox.json

28 Mar 21:23:36 - [info] Creating new flow file

28 Mar 21:23:36 - [info] Starting flows

28 Mar 21:23:36 - [info] Started flows

28 Mar 21:23:36 - [info] Server now running at http://127.0.0.1:1880/

while if I run as root, I get:

Welcome to Node-RED

===================

28 Mar 21:27:36 - [info] Node-RED version: v0.13.4

28 Mar 21:27:36 - [info] Node.js  version: v4.4.0

28 Mar 21:27:36 - [info] Linux 4.1.18-ti-r53 arm LE

28 Mar 21:27:36 - [info] Loading palette nodes

Optional package 'i2c' not loaded

28 Mar 21:27:45 - [warn] ------------------------------------------

28 Mar 21:27:45 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node

28 Mar 21:27:45 - [warn] [bbb] VError: Write to CapeMgr slots failed: ENOENT: no such file or directory, write

28 Mar 21:27:45 - [warn] ------------------------------------------

28 Mar 21:27:45 - [info] Settings file  : /root/.node-red/settings.js

28 Mar 21:27:45 - [info] User directory : /root/.node-red

28 Mar 21:27:45 - [info] Flows file : /root/.node-red/flows_redbox.json

28 Mar 21:27:45 - [info] Creating new flow file

28 Mar 21:27:45 - [info] Starting flows

28 Mar 21:27:45 - [info] Started flows

28 Mar 21:27:45 - [info] Server now running at http://127.0.0.1:1880/

The version number i2c is 0.1.8, that of octalbonescript is 1.1.2, and that of node-red-node-beaglebone is 0.1.5

But no nodes!

Any ideas?

Max

[Nicholas O'Leary]

What version of npm are you using?

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
For more options, visit https://groups.google.com/d/optout.

[Max Hadley]

NPM 2.14.20

It seems i2c only works with node <=0.12.* and although a patch has been submitted the maintainer won't accept the PR because it doesn't fix the "underlying issue" - which would require a complete rewrite. So it looks like the BBB is restricted to node 0.12.* for the foreseeable future

[Dave C-J]

Which version is built into that Debian 8.3 image ?

[Max Hadley]

The image does not include nodejs as it's the stripped down console version. The Jessie repository contains node 0.12.x

[Max Hadley]

I've reverted to nodejs v0.12.12 and tried again. There appear to be two problems:

1. octalbonescript 1.1.2 is pulling in version 0.1.8 of i2c explicitly. This version will not compile under nodejs 0.12.12. manually allowing a higher version number pulls in i2c version 0.2.1, which does compile OK, at least.
2. octalbonescript 1.1.2 is failing to load the default cape. It is reporting that it cannot write to the slots file, because it does not exists, but it does: probably what is happening is that it cannot read the file contains the default cape, because it has been moved in the very recent past (since January). Octalbonescript claims to compatible with kernels 4.1 since version 1.1.0

Problem 2 is what is stopping the palette nodes showing. For now the advice must be to stick with 3.8 kernels (Wheezy) and nodejs 0.10.x, but this really needs to be sorted out! I have reported the problems to the octalbonescript package author.

BTW it would be preferable if when a palette node fails to load, the failing nodes were always listed to the console. Currently you only see them if they are included in the flows file.

[Dave C-J]

Max,

The current advice is to use the 2016-01-24  Debian 8.3 image from http://beagleboard.org/latest-images .That is the one we used for the instructions http://nodered.org/docs/hardware/beagleboneblack so we know it does work for Jessie and 4.1 kernel at that level. I guess they must have broken it since then.

[Max Hadley]

Dave

Does that system have a /lib/firmware directory?
If so, what does it contain?

Thanks
Max

[Dave C-J]

yes it does ... has a load of dtbo files in...

ADAFRUIT-SPI0-00A0.dtbo     cape-univ-hdmi-00A0.dtbo   PyBBIO-gpio0_20-00A0.dtbo  PyBBIO-gpio2_12-00A0.dtbo

ADAFRUIT-SPI1-00A0.dtbo     carl9170-1.fw   PyBBIO-gpio0_2-00A0.dtbo   PyBBIO-gpio2_13-00A0.dtbo

ADAFRUIT-UART1-00A0.dtbo    dev-USB-PWR-CTL-00A1.dtbo   PyBBIO-gpio0_22-00A0.dtbo  PyBBIO-gpio2_14-00A0.dtbo

ADAFRUIT-UART2-00A0.dtbo    htc_9271.fw   PyBBIO-gpio0_23-00A0.dtbo  PyBBIO-gpio2_15-00A0.dtbo

ADAFRUIT-UART4-00A0.dtbo    LICENCE.atheros_firmware   PyBBIO-gpio0_26-00A0.dtbo  PyBBIO-gpio2_16-00A0.dtbo

ADAFRUIT-UART5-00A0.dtbo    LICENCE.broadcom_bcm43xx   PyBBIO-gpio0_27-00A0.dtbo  PyBBIO-gpio2_17-00A0.dtbo

BB-ADC-00A0.dtbo     LICENCE.rtlwifi_firmware.txt  PyBBIO-gpio0_30-00A0.dtbo  PyBBIO-gpio2_2-00A0.dtbo

BB-BBBMINI-00A0.dtbo     LICENCE.ti-connectivity   PyBBIO-gpio0_3-00A0.dtbo   PyBBIO-gpio2_22-00A0.dtbo

BB-BONE-AUDI-02-00A0.dtbo   mt7601u.bin   PyBBIO-gpio0_31-00A0.dtbo  PyBBIO-gpio2_23-00A0.dtbo

BB-BONE-BACONE-00A0.dtbo    OBS_UNIV-00A0.dtbo   PyBBIO-gpio0_4-00A0.dtbo   PyBBIO-gpio2_24-00A0.dtbo

BB-BONE-CRYPTO-00A0.dtbo    OBS_UNIV-00A0.dts   PyBBIO-gpio0_5-00A0.dtbo   PyBBIO-gpio2_25-00A0.dtbo

BB-BONE-DVID-01-00A3.dtbo   PyBBIO-ADC-00A0.dtbo   PyBBIO-gpio0_7-00A0.dtbo   PyBBIO-gpio2_3-00A0.dtbo

BB-BONE-LCD3-01-00A2.dtbo   PyBBIO-AIN0-00A0.dtbo   PyBBIO-gpio0_8-00A0.dtbo   PyBBIO-gpio2_4-00A0.dtbo

BB-BONE-LCD4-01-00A1.dtbo   PyBBIO-AIN1-00A0.dtbo   PyBBIO-gpio0_9-00A0.dtbo   PyBBIO-gpio2_5-00A0.dtbo

BB-BONE-LCD7-01-00A3.dtbo   PyBBIO-AIN2-00A0.dtbo   PyBBIO-gpio1_0-00A0.dtbo   PyBBIO-gpio2_6-00A0.dtbo

BB-BONE-REPLICAP-00B1.dtbo  PyBBIO-AIN3-00A0.dtbo   PyBBIO-gpio1_1-00A0.dtbo   PyBBIO-gpio2_7-00A0.dtbo

BB-BONE-SERL-03-00A1.dtbo   PyBBIO-AIN4-00A0.dtbo   PyBBIO-gpio1_12-00A0.dtbo  PyBBIO-gpio2_8-00A0.dtbo

BB-CAN1-00A0.dtbo     PyBBIO-AIN5-00A0.dtbo   PyBBIO-gpio1_13-00A0.dtbo  PyBBIO-gpio2_9-00A0.dtbo

BB-I2C1-00A0.dtbo     PyBBIO-AIN6-00A0.dtbo   PyBBIO-gpio1_14-00A0.dtbo  PyBBIO-gpio3_14-00A0.dtbo

BB-I2C1-PCA9685-00A0.dtbo   PyBBIO-AIN7-00A0.dtbo   PyBBIO-gpio1_15-00A0.dtbo  PyBBIO-gpio3_15-00A0.dtbo

BB-I2C2-0A00.dtbo     PyBBIO-ecap0-00A0.dtbo   PyBBIO-gpio1_16-00A0.dtbo  PyBBIO-gpio3_16-00A0.dtbo

BB-RELAY-4PORT-00A0.dtbo    PyBBIO-ecap1-00A0.dtbo   PyBBIO-gpio1_17-00A0.dtbo  PyBBIO-gpio3_17-00A0.dtbo

BB-RTC-01-00A0.dtbo     PyBBIO-ehrpwm1-00A0.dtbo   PyBBIO-gpio1_18-00A0.dtbo  PyBBIO-gpio3_19-00A0.dtbo

BB-SPI0-MCP3008-00A0.dtbo   PyBBIO-ehrpwm2-00A0.dtbo   PyBBIO-gpio1_19-00A0.dtbo  PyBBIO-gpio3_21-00A0.dtbo

BB-SPIDEV0-00A0.dtbo     PyBBIO-epwmss0-00A0.dtbo   PyBBIO-gpio1_2-00A0.dtbo   PyBBIO-usr0-00A0.dtbo

BB-SPIDEV1-00A0.dtbo     PyBBIO-epwmss1-00A0.dtbo   PyBBIO-gpio1_28-00A0.dtbo  PyBBIO-usr1-00A0.dtbo

BB-SPIDEV1A1-00A0.dtbo     PyBBIO-epwmss2-00A0.dtbo   PyBBIO-gpio1_29-00A0.dtbo  PyBBIO-usr2-00A0.dtbo

BB-UART1-00A0.dtbo     PyBBIO-eqep0-00A0.dtbo   PyBBIO-gpio1_30-00A0.dtbo  PyBBIO-usr3-00A0.dtbo

BB-UART2-00A0.dtbo     PyBBIO-eqep1-00A0.dtbo   PyBBIO-gpio1_3-00A0.dtbo   rtlwifi

BB-UART4-00A0.dtbo     PyBBIO-eqep2-00A0.dtbo   PyBBIO-gpio1_31-00A0.dtbo  ti-connectivity

BB-UART5-00A0.dtbo     PyBBIO-eqep2b-00A0.dtbo   PyBBIO-gpio1_4-00A0.dtbo   univ-all-00A0.dtbo

brcm     PyBBIO-gpio0_10-00A0.dtbo   PyBBIO-gpio1_5-00A0.dtbo   univ-emmc-00A0.dtbo

cape-CBB-Serial-r01.dtbo    PyBBIO-gpio0_11-00A0.dtbo   PyBBIO-gpio1_6-00A0.dtbo   univ-hdmi-00A0.dtbo

cape-univ-audio-00A0.dtbo   PyBBIO-gpio0_12-00A0.dtbo   PyBBIO-gpio1_7-00A0.dtbo   univ-nhdmi-00A0.dtbo

cape-univ-emmc-00A0.dtbo    PyBBIO-gpio0_13-00A0.dtbo   PyBBIO-gpio2_10-00A0.dtbo

cape-universal-00A0.dtbo    PyBBIO-gpio0_14-00A0.dtbo   PyBBIO-gpio2_1-00A0.dtbo

cape-universaln-00A0.dtbo   PyBBIO-gpio0_15-00A0.dtbo   PyBBIO-gpio2_11-00A0.dtbo

[Max Hadley]

Problem solved! (thanks, Dave)

It turns out the console images are very stripped down, and don't include the dtbo device tree overlay tools. These don't seem to be available as a debian package, but I followed the instructions at http://voidnoise.co.uk/blog/?p=734 and did:

    git clone https://github.com/beagleboard/bb.org-overlays.git
    cd bb.org-overlays
    ./install.sh

(as an ordinary user - it sudo's itself where needed)

This created the missing directory & filled it with lots of dtbo files. I rebooted, and now the BBB nodes are appearing properly in the palette.

The absolutely essential packages to install on top of the stock console image to get node-red to run appear to be:

    sudo apt-get install git build-essential python-dev device-tree-compiler nodes

Looks like I'm good to go now!

[Max Hadley]

Aargh - bloody auto-correct. That last package should of course be nodejs not nodes

[Alberto Caraveo]

 
Hi, I have a problem like you were talking about, I'm using a BBB, and I upgrated to wheezy, and the NODE-RED runs perfectly, but I have a problem. Node-red is ignoring the specific nodes. If you can help me, I will be so happy:

Welcome to Node-RED
===================

12 Nov 22:04:40 - [info] Node-RED version: v0.18.3
12 Nov 22:04:40 - [info] Node.js  version: v4.8.7
12 Nov 22:04:40 - [info] Linux 3.8.13-bone79 arm LE
12 Nov 22:04:43 - [info] Loading palette nodes
12 Nov 22:04:51 - [info] Dashboard version 2.8.1 started at /ui
12 Nov 22:04:57 - [warn] ------------------------------------------------------
12 Nov 22:04:57 - [warn] [node-red/rpi-gpio] Info : Ignoring Raspberry Pi specific node
12 Nov 22:04:57 - [warn] [node-red-node-beaglebone/bbb] Info : Ignoring Beaglebone specific node.
12 Nov 22:04:57 - [warn] ------------------------------------------------------
12 Nov 22:04:57 - [info] Settings file  : /root/.node-red/settings.js
12 Nov 22:04:57 - [info] User directory : /root/.node-red
12 Nov 22:04:57 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
12 Nov 22:04:57 - [info] Flows file     : /root/.node-red/flows_beaglebone.json
12 Nov 22:04:57 - [info] Creating new flow file
12 Nov 22:04:57 - [info] Starting flows
12 Nov 22:04:57 - [info] Started flows
12 Nov 22:04:57 - [info] Server now running at http://127.0.0.1:1880/

I'm waiting  for you answers.

[Michel Gerin]

Hello Alberto,

Unhappily, I don't use anymore the BBB for the GPIO palette as you can see below. As soon as the "Raspberry pi zero w" was available", I switched over to this device.

The BBB I owned was quite old and had no WiFi interface. The WiFi Dongle I was using on a Win machine didn't work on the BBB (driver problem).

 These posts are 2 years old...I must admit that I don't remember exactly how this problem was solved. When I look at the different messages, I think there was a problem with one of the library version.

Finally, reading what other users did to solve this problem helped me certainly.. As it seemed that some devices on the BBB were only working with nodejs version <= 0.12, I reverted probably to V0.10.25 as you can see below

The only thing I can tell you is that I wrote down the following last lines on a document when the GPIO palette did appear correctly and was really available to use:

Correct BeagleBone Black library versions :

npm: 2.14.17   

Node-red: V0.13.1

Node.js: V0.10.25

Ubuntu: 14.04.3 Trusty (console version)

Linux arm 4.1.13-ti-r36

As you can see these versions are quite old !!! 

Here are the console messages when starting the "pi zero w" today

Starting as a systemd service.
Started Node-RED graphical event wiring tool..
20 Feb 13:15:30 - [info]
Welcome to Node-RED
===================
20 Feb 13:15:30 - [info] Node-RED version: v0.17.4
20 Feb 13:15:30 - [info] Node.js  version: v4.8.2
20 Feb 13:15:30 - [info] Linux 4.9.59+ arm LE
20 Feb 13:15:30 - [info] Palette editor disabled : npm command not found
20 Feb 13:15:30 - [info] Loading palette nodes
20 Feb 13:15:59 - [info] Settings file  : /home/pi/.node-red/settings.js
20 Feb 13:15:59 - [info] User directory : /home/pi/.node-red
20 Feb 13:15:59 - [info] Flows file     : /home/pi/.node-red/flows_raspberrypi.json
20 Feb 13:15:59 - [info] Server now running at http://127.0.0.1:1880/
20 Feb 13:15:59 - [info] Starting flows
20 Feb 13:15:59 - [info] Started flows

Hope this help you a bit.

Have a nice day

Michel.

--

http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack

---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/t_mw1led9Eo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/96cb9985-5429-4a63-9520-079b81d504d1%40googlegroups.com.

[Dave C-J]

Alberto

as I mentioned in your other thread - the latest version of Debian from beaglebone (9.3) comes with some GPIO nodes pre-installed and working. Given that Wheezy went out of support over a year ago I would suggest upgrading to it anyway...

[Michel Gerin]

Hello Alberto,

I confirm Dave's message. I installed Debian 9.3 on my old BBB version A5C. GPIO works fine (at least that's what I tested). I have other issues with this Debian version on the BBB but probably not related to Node-red.

Which BBB version are you using ?

Michel.

2018-02-20 19:05 GMT+01:00 Dave C-J <dce...@gmail.com>:

Alberto

as I mentioned in your other thread - the latest version of Debian from beaglebone (9.3) comes with some GPIO nodes pre-installed and working. Given that Wheezy went out of support over a year ago I would suggest upgrading to it anyway...

--

http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/t_mw1led9Eo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CACXWFwLdMGu%3DvvgmLgbwEYVZP9h%3De-PeMoFuLwi-oAE2v%3DrN1Q%40mail.gmail.com.

[Alberto Caraveo]

Hi Michel

Thank you for your advice, but also I tried to install Debian 9.3, but really I don't know how to do it, because I follow the steps in BBB getting started, and when I am booting the SD, this one doesn't work correctly, When it finish the "boot" this one appears like a format incorrect, and my PC tells me that I have to format it. I'm using win32.

El jueves, 22 de febrero de 2018, 13:04:13 (UTC-6), Michel Gerin escribió:

Hello Alberto,

I confirm Dave's message. I installed Debian 9.3 on my old BBB version A5C. GPIO works fine (at least that's what I tested). I have other issues with this Debian version on the BBB but probably not related to Node-red.

Which BBB version are you using ?

Michel.

2018-02-20 19:05 GMT+01:00 Dave C-J <dce...@gmail.com>:

Alberto

as I mentioned in your other thread - the latest version of Debian from beaglebone (9.3) comes with some GPIO nodes pre-installed and working. Given that Wheezy went out of support over a year ago I would suggest upgrading to it anyway...

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/t_mw1led9Eo/unsubscribe.

To unsubscribe from this group and all its topics, send an email to node-red+u...@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

[Michel Gerin]

Hello Alberto,

Well, maybe it's not exactly the place to discuss about installation issue on a topic related to node-red

I don't think either that it may profitable for someone else because your problem is probably due to the procedure you use to install Debian 9.3 on your BBB via the SD card. Maybe it is better to discuss that in private.

But I am not sure to be able to help you if you exactly followed the procedure described on beaglebone.org without success.

Michel.

To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/ba268c57-2054-40eb-8402-399975291899%40googlegroups.com.