Does not run on Raspberry pi 3 B+

[natcl]

Tried the v1.0.0 version on Raspberry pi 3 B+ and it says it could not verify the raspberry version and to file a bug report.

Thanks !

[natcl]

I was able to make it work by updating rpi-version (submitted a pull request to the author) and also updating to the latest version of rpi-ws281x lib.
If you want to test:
https://github.com/natcl/node-rpi-ws281x-native/tree/v1.x

[tomvanoosterwyck]

Hi natcl, I would like to use your fork of this libary but I receive an build error while making it from source.

Could you activate the issues tab so I can post the error?

[natcl]

Should work now

…

-- lecaude.com studioimaginaire.com

Le 10 avr. 2018 à 17:53, Thyvo ***@***.***> a écrit : Hi natcl, I would like to use your fork of this libary but I receive an build error while making it from source. Could you activate the issues tab so I can post the error? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[tsuckow]

I also published [email protected] with your changes.

[riccardolardi]

Can we merge B+ support into v1.x?

[usefulthink]

thanks for bringing this up, I will have a look tonight!

[joakimunge]

@usefulthink Nice. I'm working on an IoT project using neopixels and RPi 3 B+ right now, so support would be great.

@natcl I tried to build your repo but I received an error, probably the same as @thyvo . Posted an issue in your fork.

[riccardolardi]

I got it to work by adding "a020d3" : "Model_B+_PI_3" to index.js of rpi-version and updating/cloning current master branch of https://github.com/jgarff/rpi_ws281x into ./src/rpi_ws281x and rerunning npm i. So is this coming with an outdated version of jgarff/rpi_ws281x?

[joakimunge]

@alberto2000 Was this using @natcl fork or the source v1.x?

[riccardolardi]

@joakimunge I'm using this repo's v1.x

[joakimunge]

@alberto2000 Thanks. Got it to work using your way as well.

[riccardolardi]

The things needed to to to make this work with B+ are

• update submodule at ./src/rpi_ws281x to use official/latest jgarff version
• use git version of rpi-version (npm package is out of date)

[joakimunge]

Can confirm. @alberto2000

[tjgionet]

Made a Dumb Dumb*
Didn't note the API change. : ) Thanks for all your work on this project.
Please ignore the question below.

@alberto2000 I'm still having trouble getting this to run even after both your updates listed above.
There is literally no response from either the neopixels or out the console.

Any other tips?
When you update the submodule rpi_ws281x and run 'npm i' is there anyting else that needs to be done.

Basically I do both updates above head to the root of the directory complete a final npm i then a node-gyp rebuild. Nothing fails I can init the leds fine and send a render to them but nothing...

I have been able to use the master branch of this repo which works sometimes.

Thanks!

[tsuckow]

Are you trying to drive the neopixels directly or do you have a 5v buffer between the pi and the pixels?

…

On Sun, Feb 24, 2019, 09:54 Trevor Gionet ***@***.***> wrote: @alberto2000 <https://github.com/alberto2000> I'm still having trouble getting this to run even after both your updates listed above. There is literally no response from either the neopixels or out the console. Any other tips? When you update the submodule rpi_ws281x and run 'npm i' is there anyting else that needs to be done. Basically I do both updates above head to the root of the directory complete a final npm i then a node-gyp rebuild. Nothing fails I can init the leds fine and send a render to them but nothing... I have been able to use the master branch of this repo which works sometimes. Thanks! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAQBJ6wdA7_EqudBkSyMdEntCfbaVdtxks5vQtHDgaJpZM4TAqOs> .

[tjgionet]

I believe we drive them directly. My issue was simply that I was using the old API. Once I updated that all went smoothly. Thanks!!

Are you trying to drive the neopixels directly or do you have a 5v buffer between the pi and the pixels?
…
On Sun, Feb 24, 2019, 09:54 Trevor Gionet @.***> wrote: @alberto2000 https://github.com/alberto2000 I'm still having trouble getting this to run even after both your updates listed above. There is literally no response from either the neopixels or out the console. Any other tips? When you update the submodule rpi_ws281x and run 'npm i' is there anyting else that needs to be done. Basically I do both updates above head to the root of the directory complete a final npm i then a node-gyp rebuild. Nothing fails I can init the leds fine and send a render to them but nothing... I have been able to use the master branch of this repo which works sometimes. Thanks! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAQBJ6wdA7_EqudBkSyMdEntCfbaVdtxks5vQtHDgaJpZM4TAqOs .

[riccardolardi]

Model a52082 is not present in rpi-version ivsgroup/rpi-version#8

[riccardolardi]

rpi-version updated with ivsgroup/rpi-version#9