AllPixel abd BiblioPixel on Raspberry Pi

Not sure what has happened here …

I develop on a Windows 10 platform and had been playing my app on a Pi.

Since all was working well I had not tried using the Pi in the last two weeks. Just continued my development on Windows 10.

We are nearing deployment so I thought I better make sure the Pi is up to date.

Now the Pi, in fact multiple Pi’s, will not turn on the led’s at all.

To switch between the two platforms I simply unplug the USB cable attached to the AllPixel and plug it in to the other platform.

Therefore it is the same AllPixel, same led strip and same connections.

The Pi recognizes that the AllPixel is there by showing the port and not crashing if you try to define a driver without the board connected,

It recognizes all of the BiblioPixel structures, such that no python crashes occur.

Yet nothing turns on. I hook the All Pixel to the Windows platform and it works just fine.

I have updated BiblioPixel.

I am at a loss as to what changed since Nov 23.

I attached my simple test app. But here is what the code is:

testAllPixel.py (229 Bytes)

···

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

from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

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

I have tried removing the c_order. No joy!

I have tried running without ledtype, but that fails during driver initialization.

When it runs on the Pi it seems to run normal except no leds turn on.

When it runs on Windows 10 all the leds turn red for 5 seconds and than turn off.

Any idea what has gone wrong?

(Full disclosure, I am pretty sure that when we finally resolve this it is going to be operator error on my part)

Harold

First, can you please run bibliopixel --version and send the output?
Also run pip freeze in whatever python environment you are using and send the output of that.
Also, please add this to your script right after the current imports:

from bibliopixel import log
log.setLogLevel("debug")

Then run again and send me the output. Nothing pops out at me right now. But those should give me a better idea of what’s going on.

···

On Tue, Dec 5, 2017 at 6:57 PM, Harold Breeden hdb4720@gmail.com wrote:

Not sure what has happened here …

I develop on a Windows 10 platform and had been playing my app on a Pi.

Since all was working well I had not tried using the Pi in the last two weeks. Just continued my development on Windows 10.

We are nearing deployment so I thought I better make sure the Pi is up to date.

Now the Pi, in fact multiple Pi’s, will not turn on the led’s at all.

To switch between the two platforms I simply unplug the USB cable attached to the AllPixel and plug it in to the other platform.

Therefore it is the same AllPixel, same led strip and same connections.

The Pi recognizes that the AllPixel is there by showing the port and not crashing if you try to define a driver without the board connected,

It recognizes all of the BiblioPixel structures, such that no python crashes occur.

Yet nothing turns on. I hook the All Pixel to the Windows platform and it works just fine.

I have updated BiblioPixel.

I am at a loss as to what changed since Nov 23.

I attached my simple test app. But here is what the code is:

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

from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

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

I have tried removing the c_order. No joy!

I have tried running without ledtype, but that fails during driver initialization.

When it runs on the Pi it seems to run normal except no leds turn on.

When it runs on Windows 10 all the leds turn red for 5 seconds and than turn off.

Any idea what has gone wrong?

(Full disclosure, I am pretty sure that when we finally resolve this it is going to be operator error on my part)

Harold

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/7a39e3c1-4b12-464e-a096-296dc872b28e%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

pi@raspberrypi:/opt/pianoBar $ bibliopixel --version
BiblioPixel version 3.3.3
ERROR: No command entered
Valid: alias, all_pixel, clear_cache, color, devices, demo, run, update

pi@raspberrypi:/opt/pianoBar $ pip freeze
Babel==2.5.1
BiblioPixel==3.3.3
BiblioPixelAnimations==3.20170913.013846
BiblioPixelTriggers==1.0.1
Flask==0.12.2
GitPython==2.1.7
Jinja2==2.9.6
MarkupSafe==1.0
Pillow==2.6.1
PyCmdMessenger==0.2.4
Pygments==2.2.0
RPIO==2.0.0-beta1
RPi.GPIO==0.6.3
RTIMULib==7.2.1
Sphinx==1.6.5
Werkzeug==0.12.2
alabaster==0.7.10
apipkg==1.4
appdirs==1.4.3
beautifulsoup4==4.6.0
chardet==2.3.0
click==6.7
colorama==0.3.2
croniter==0.3.20
docutils==0.14
execnet==1.5.0
gitdb2==2.0.3
gpiozero==1.3.1
html5lib==0.999
imagesize==0.7.1
itsdangerous==0.24
loady==1.7.4
mcpi==0.1.1
numpy==1.8.2
pgzero==1.1
picamera==1.12
pifacecommon==4.2.1
pifacedigitalio==3.1.0
pigpio==1.30
pkginfo==1.4.1
py==1.4.34
pyFirmata==1.0.3
pygame==1.9.2a0
pyserial==3.4
pytest==3.2.3
pytest-forked==0.2
pytest-timeout==1.2.0
pytest-xdist==1.20.1
python-apt==0.9.3.12
python-dateutil==2.6.1
python-debian==0.1.27
pytz==2017.2
requests==2.4.3
requests-toolbelt==0.8.0
rpi-ws281x==1.0.0
sense-hat==2.2.0
six==1.8.0
smmap2==2.0.3
snowballstemmer==1.2.1
sphinxcontrib-websupport==1.0.1
spidev==3.0
tqdm==4.19.4
twine==1.9.1
typing==3.6.2
urllib3==1.9.1
wheel==0.24.0

···

============================================================
from bibliopixel import log
from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

log.setLogLevel(“debug”)

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

pi@raspberrypi:/opt/pianoBar $ python testAllPixel.py
INFO - devices - Using COM Port: /dev/ttyACM0, Device ID: 0, Device Ver: 0
INFO - driver - Reconfigure and reboot needed, waiting for controller to restart…
INFO - devices - Using COM Port: /dev/ttyACM0, Device ID: 0, Device Ver: 0
INFO - driver - Reconfigure success!

On Tuesday, December 5, 2017 at 5:57:22 PM UTC-6, Harold Breeden wrote:

Not sure what has happened here …

I develop on a Windows 10 platform and had been playing my app on a Pi.

Since all was working well I had not tried using the Pi in the last two weeks. Just continued my development on Windows 10.

We are nearing deployment so I thought I better make sure the Pi is up to date.

Now the Pi, in fact multiple Pi’s, will not turn on the led’s at all.

To switch between the two platforms I simply unplug the USB cable attached to the AllPixel and plug it in to the other platform.

Therefore it is the same AllPixel, same led strip and same connections.

The Pi recognizes that the AllPixel is there by showing the port and not crashing if you try to define a driver without the board connected,

It recognizes all of the BiblioPixel structures, such that no python crashes occur.

Yet nothing turns on. I hook the All Pixel to the Windows platform and it works just fine.

I have updated BiblioPixel.

I am at a loss as to what changed since Nov 23.

I attached my simple test app. But here is what the code is:

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

from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

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

I have tried removing the c_order. No joy!

I have tried running without ledtype, but that fails during driver initialization.

When it runs on the Pi it seems to run normal except no leds turn on.

When it runs on Windows 10 all the leds turn red for 5 seconds and than turn off.

Any idea what has gone wrong?

(Full disclosure, I am pretty sure that when we finally resolve this it is going to be operator error on my part)

Harold

Oh…hmm…
First: pip install --upgrade bibliopixel as you are still on the old version that was broken for you.

Second. Can you put print('step 1') lines between each step. Feels to me like it’s just not running anything after the driver line. No idea why. Just checking.

···

On Tue, Dec 5, 2017 at 9:02 PM, Harold Breeden hdb4720@gmail.com wrote:

On Tuesday, December 5, 2017 at 5:57:22 PM UTC-6, Harold Breeden wrote:

Not sure what has happened here …

I develop on a Windows 10 platform and had been playing my app on a Pi.

Since all was working well I had not tried using the Pi in the last two weeks. Just continued my development on Windows 10.

We are nearing deployment so I thought I better make sure the Pi is up to date.

Now the Pi, in fact multiple Pi’s, will not turn on the led’s at all.

To switch between the two platforms I simply unplug the USB cable attached to the AllPixel and plug it in to the other platform.

Therefore it is the same AllPixel, same led strip and same connections.

The Pi recognizes that the AllPixel is there by showing the port and not crashing if you try to define a driver without the board connected,

It recognizes all of the BiblioPixel structures, such that no python crashes occur.

Yet nothing turns on. I hook the All Pixel to the Windows platform and it works just fine.

I have updated BiblioPixel.

I am at a loss as to what changed since Nov 23.

I attached my simple test app. But here is what the code is:

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

from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

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

I have tried removing the c_order. No joy!

I have tried running without ledtype, but that fails during driver initialization.

When it runs on the Pi it seems to run normal except no leds turn on.

When it runs on Windows 10 all the leds turn red for 5 seconds and than turn off.

Any idea what has gone wrong?

(Full disclosure, I am pretty sure that when we finally resolve this it is going to be operator error on my part)

Harold

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

pi@raspberrypi:/opt/pianoBar $ bibliopixel --version
BiblioPixel version 3.3.3
ERROR: No command entered
Valid: alias, all_pixel, clear_cache, color, devices, demo, run, update

pi@raspberrypi:/opt/pianoBar $ pip freeze
Babel==2.5.1
BiblioPixel==3.3.3
BiblioPixelAnimations==3.20170913.013846
BiblioPixelTriggers==1.0.1
Flask==0.12.2
GitPython==2.1.7
Jinja2==2.9.6
MarkupSafe==1.0
Pillow==2.6.1
PyCmdMessenger==0.2.4
Pygments==2.2.0
RPIO==2.0.0-beta1
RPi.GPIO==0.6.3
RTIMULib==7.2.1
Sphinx==1.6.5
Werkzeug==0.12.2
alabaster==0.7.10
apipkg==1.4
appdirs==1.4.3
beautifulsoup4==4.6.0
chardet==2.3.0
click==6.7
colorama==0.3.2
croniter==0.3.20
docutils==0.14
execnet==1.5.0
gitdb2==2.0.3
gpiozero==1.3.1
html5lib==0.999
imagesize==0.7.1
itsdangerous==0.24
loady==1.7.4
mcpi==0.1.1
numpy==1.8.2
pgzero==1.1
picamera==1.12
pifacecommon==4.2.1
pifacedigitalio==3.1.0
pigpio==1.30
pkginfo==1.4.1
py==1.4.34
pyFirmata==1.0.3
pygame==1.9.2a0
pyserial==3.4
pytest==3.2.3
pytest-forked==0.2
pytest-timeout==1.2.0
pytest-xdist==1.20.1
python-apt==0.9.3.12
python-dateutil==2.6.1
python-debian==0.1.27
pytz==2017.2
requests==2.4.3
requests-toolbelt==0.8.0
rpi-ws281x==1.0.0
sense-hat==2.2.0
six==1.8.0
smmap2==2.0.3
snowballstemmer==1.2.1
sphinxcontrib-websupport==1.0.1
spidev==3.0
tqdm==4.19.4
twine==1.9.1
typing==3.6.2
urllib3==1.9.1
wheel==0.24.0

============================================================
from bibliopixel import log
from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

log.setLogLevel(“debug”)

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

pi@raspberrypi:/opt/pianoBar $ python testAllPixel.py
INFO - devices - Using COM Port: /dev/ttyACM0, Device ID: 0, Device Ver: 0
INFO - driver - Reconfigure and reboot needed, waiting for controller to restart…
INFO - devices - Using COM Port: /dev/ttyACM0, Device ID: 0, Device Ver: 0
INFO - driver - Reconfigure success!To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/dcfc8226-13a8-417d-93b1-f049ce60a990%40googlegroups.com.

Also… It shouldn’t show that reconfigure every time. The AllPixel should be setup already from running on Windows and just continue on.
Does it do that every time?

···

On Tue, Dec 5, 2017 at 9:04 PM, Adam Haile adammhaile@gmail.com wrote:

Oh…hmm…
First: pip install --upgrade bibliopixel as you are still on the old version that was broken for you.

Second. Can you put print('step 1') lines between each step. Feels to me like it’s just not running anything after the driver line. No idea why. Just checking.

On Tue, Dec 5, 2017 at 9:02 PM, Harold Breeden hdb4720@gmail.com wrote:

On Tuesday, December 5, 2017 at 5:57:22 PM UTC-6, Harold Breeden wrote:

Not sure what has happened here …

I develop on a Windows 10 platform and had been playing my app on a Pi.

Since all was working well I had not tried using the Pi in the last two weeks. Just continued my development on Windows 10.

We are nearing deployment so I thought I better make sure the Pi is up to date.

Now the Pi, in fact multiple Pi’s, will not turn on the led’s at all.

To switch between the two platforms I simply unplug the USB cable attached to the AllPixel and plug it in to the other platform.

Therefore it is the same AllPixel, same led strip and same connections.

The Pi recognizes that the AllPixel is there by showing the port and not crashing if you try to define a driver without the board connected,

It recognizes all of the BiblioPixel structures, such that no python crashes occur.

Yet nothing turns on. I hook the All Pixel to the Windows platform and it works just fine.

I have updated BiblioPixel.

I am at a loss as to what changed since Nov 23.

I attached my simple test app. But here is what the code is:

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

from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

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

I have tried removing the c_order. No joy!

I have tried running without ledtype, but that fails during driver initialization.

When it runs on the Pi it seems to run normal except no leds turn on.

When it runs on Windows 10 all the leds turn red for 5 seconds and than turn off.

Any idea what has gone wrong?

(Full disclosure, I am pretty sure that when we finally resolve this it is going to be operator error on my part)

Harold

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

pi@raspberrypi:/opt/pianoBar $ bibliopixel --version
BiblioPixel version 3.3.3
ERROR: No command entered
Valid: alias, all_pixel, clear_cache, color, devices, demo, run, update

pi@raspberrypi:/opt/pianoBar $ pip freeze
Babel==2.5.1
BiblioPixel==3.3.3
BiblioPixelAnimations==3.20170913.013846
BiblioPixelTriggers==1.0.1
Flask==0.12.2
GitPython==2.1.7
Jinja2==2.9.6
MarkupSafe==1.0
Pillow==2.6.1
PyCmdMessenger==0.2.4
Pygments==2.2.0
RPIO==2.0.0-beta1
RPi.GPIO==0.6.3
RTIMULib==7.2.1
Sphinx==1.6.5
Werkzeug==0.12.2
alabaster==0.7.10
apipkg==1.4
appdirs==1.4.3
beautifulsoup4==4.6.0
chardet==2.3.0
click==6.7
colorama==0.3.2
croniter==0.3.20
docutils==0.14
execnet==1.5.0
gitdb2==2.0.3
gpiozero==1.3.1
html5lib==0.999
imagesize==0.7.1
itsdangerous==0.24
loady==1.7.4
mcpi==0.1.1
numpy==1.8.2
pgzero==1.1
picamera==1.12
pifacecommon==4.2.1
pifacedigitalio==3.1.0
pigpio==1.30
pkginfo==1.4.1
py==1.4.34
pyFirmata==1.0.3
pygame==1.9.2a0
pyserial==3.4
pytest==3.2.3
pytest-forked==0.2
pytest-timeout==1.2.0
pytest-xdist==1.20.1
python-apt==0.9.3.12
python-dateutil==2.6.1
python-debian==0.1.27
pytz==2017.2
requests==2.4.3
requests-toolbelt==0.8.0
rpi-ws281x==1.0.0
sense-hat==2.2.0
six==1.8.0
smmap2==2.0.3
snowballstemmer==1.2.1
sphinxcontrib-websupport==1.0.1
spidev==3.0
tqdm==4.19.4
twine==1.9.1
typing==3.6.2
urllib3==1.9.1
wheel==0.24.0

============================================================
from bibliopixel import log
from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

log.setLogLevel(“debug”)

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

pi@raspberrypi:/opt/pianoBar $ python testAllPixel.py
INFO - devices - Using COM Port: /dev/ttyACM0, Device ID: 0, Device Ver: 0
INFO - driver - Reconfigure and reboot needed, waiting for controller to restart…
INFO - devices - Using COM Port: /dev/ttyACM0, Device ID: 0, Device Ver: 0
INFO - driver - Reconfigure success!To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/dcfc8226-13a8-417d-93b1-f049ce60a990%40googlegroups.com.

Alright here is the results after doing the pip install and adding line numbers. Still no leds.

Also the extra verbiage on the previous post when initializing the driver was due to me monkeying with NUMLEDS to see if that had any effect. It only does the extra verbiage when it is not the same configuration as the last time.

Here is the output:
pi@esquirepi:/opt/pianobar $ bibliopixel --version
BiblioPixel version 3.3.6
ERROR: No command entered
Valid: alias, all_pixel, clear_cache, color, devices, demo, run, update
pi@esquirepi:/opt/pianobar $ pip freeze
automationhat==0.0.4
beautifulsoup4==4.6.0
BiblioPixel==3.3.6
BiblioPixelAnimations==3.20171123.54201
BiblioPixelTriggers==1.0.1
blinker==1.3
blinkt==0.1.0
Cap1xxx==0.1.3
certifi==2017.11.5
chardet==3.0.4
click==6.7
colorama==0.3.7
croniter==0.3.20
cryptography==1.7.1
Django==1.11.7
drumhat==0.0.5
envirophat==0.0.6
ExplorerHAT==0.4.2
Flask==0.12.2
fourletterphat==0.0.2
gitdb2==2.0.3
GitPython==2.1.7
gpiozero==1.4.0
idna==2.6
itsdangerous==0.24
jedi==0.10.2
Jinja2==2.10
keyring==10.1
keyrings.alt==1.3
loady==1.7.4
MarkupSafe==1.0
mcpi==0.1.1
microdotphat==0.1.3
mote==0.0.3
motephat==0.0.2
numpy==1.12.1
oauthlib==2.0.1
pgzero==1.1
phatbeat==0.0.2
pianohat==0.0.5
picamera==1.13
picraft==1.0
piglow==1.2.4
pigpio==1.38
Pillow==4.0.0
PixelWeb==1.1.5
pyasn1==0.1.9
pycrypto==2.6.1
pygame==1.9.3
pygobject==3.22.0
pyinotify==0.9.6
PyJWT==1.4.2
pyOpenSSL==16.2.0
pyserial==3.4
python-apt==1.1.0b5
python-dateutil==2.6.1
pytz==2017.3
pyxdg==0.25
rainbowhat==0.0.2
requests==2.18.4
requests-oauthlib==0.7.0
RPi.GPIO==0.6.3
RTIMULib==7.2.1
scrollphat==0.0.7
scrollphathd==1.0.1
SecretStorage==2.3.1
sense-emu==1.0
sense-hat==2.2.0
simplejson==3.10.0
six==1.11.0
skywriter==0.0.7
smmap2==2.0.3
sn3218==1.2.7
spidev==3.0
thonny==2.1.10
touchphat==0.0.1
twython==3.4.0
urllib3==1.22
Werkzeug==0.12.2
pi@esquirepi:/opt/pianobar $ python testAllPixel.py
1
2
INFO - devices - Using COM Port: /dev/ttyACM0, Device ID: 0, Device Ver: 0
3
4
5
6
7
8
9
pi@esquirepi:/opt/pianobar $ cat testAllPixel.py
from bibliopixel import log
from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

print(“1”)
log.setLogLevel(“debug”)

print(“2”)
driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
print(“3”)
led=Strip(driver)
print(“4”)
led.fill([255,0,0])
print(“5”)
led.update()
print(“6”)
time.sleep(5)
print(“7”)
led.all_off()
print(“8”)
led.update()
print(“9”)

···

On Tuesday, December 5, 2017 at 5:57:22 PM UTC-6, Harold Breeden wrote:

Not sure what has happened here …

I develop on a Windows 10 platform and had been playing my app on a Pi.

Since all was working well I had not tried using the Pi in the last two weeks. Just continued my development on Windows 10.

We are nearing deployment so I thought I better make sure the Pi is up to date.

Now the Pi, in fact multiple Pi’s, will not turn on the led’s at all.

To switch between the two platforms I simply unplug the USB cable attached to the AllPixel and plug it in to the other platform.

Therefore it is the same AllPixel, same led strip and same connections.

The Pi recognizes that the AllPixel is there by showing the port and not crashing if you try to define a driver without the board connected,

It recognizes all of the BiblioPixel structures, such that no python crashes occur.

Yet nothing turns on. I hook the All Pixel to the Windows platform and it works just fine.

I have updated BiblioPixel.

I am at a loss as to what changed since Nov 23.

I attached my simple test app. But here is what the code is:

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

from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

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

I have tried removing the c_order. No joy!

I have tried running without ledtype, but that fails during driver initialization.

When it runs on the Pi it seems to run normal except no leds turn on.

When it runs on Windows 10 all the leds turn red for 5 seconds and than turn off.

Any idea what has gone wrong?

(Full disclosure, I am pretty sure that when we finally resolve this it is going to be operator error on my part)

Harold

Harold,

These are the same exact LEDs on both Windows and the Pi? Just making sure you aren’t switching strips or something…

Try changing led.fill([255,0,0]) to led.fill([255,255,0]) - Just curious.
Also… how are you powering the LEDs?? If only via USB it’s likely the Pi doesn’t have enough power.

···

On Wed, Dec 6, 2017 at 7:02 AM, Tom Swirly tom@swirly.com wrote:

(I’ll have time tonight to look at this if Adam doesn’t get to resolve it today…)

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAOuQWfVuvLKiV8FzU-kw52PwYQ%2BMErorQHS3CnSZ%2BY4sk1bQmg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

On Wed, Dec 6, 2017 at 6:00 AM, Harold Breeden hdb4720@gmail.com wrote:

Not sure what has happened here …

I develop on a Windows 10 platform and had been playing my app on a Pi.

Since all was working well I had not tried using the Pi in the last two weeks. Just continued my development on Windows 10.

We are nearing deployment so I thought I better make sure the Pi is up to date.

Now the Pi, in fact multiple Pi’s, will not turn on the led’s at all.

To switch between the two platforms I simply unplug the USB cable attached to the AllPixel and plug it in to the other platform.

Therefore it is the same AllPixel, same led strip and same connections.

The Pi recognizes that the AllPixel is there by showing the port and not crashing if you try to define a driver without the board connected,

It recognizes all of the BiblioPixel structures, such that no python crashes occur.

Yet nothing turns on. I hook the All Pixel to the Windows platform and it works just fine.

I have updated BiblioPixel.

I am at a loss as to what changed since Nov 23.

I attached my simple test app. But here is what the code is:

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

from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

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

I have tried removing the c_order. No joy!

I have tried running without ledtype, but that fails during driver initialization.

When it runs on the Pi it seems to run normal except no leds turn on.

When it runs on Windows 10 all the leds turn red for 5 seconds and than turn off.

Any idea what has gone wrong?

(Full disclosure, I am pretty sure that when we finally resolve this it is going to be operator error on my part)

Harold

Alright here is the results after doing the pip install and adding line numbers. Still no leds.

Also the extra verbiage on the previous post when initializing the driver was due to me monkeying with NUMLEDS to see if that had any effect. It only does the extra verbiage when it is not the same configuration as the last time.

Here is the output:
pi@esquirepi:/opt/pianobar $ bibliopixel --version
BiblioPixel version 3.3.6
ERROR: No command entered
Valid: alias, all_pixel, clear_cache, color, devices, demo, run, update
pi@esquirepi:/opt/pianobar $ pip freeze
automationhat==0.0.4
beautifulsoup4==4.6.0
BiblioPixel==3.3.6
BiblioPixelAnimations==3.20171123.54201
BiblioPixelTriggers==1.0.1
blinker==1.3
blinkt==0.1.0
Cap1xxx==0.1.3
certifi==2017.11.5
chardet==3.0.4
click==6.7
colorama==0.3.7
croniter==0.3.20
cryptography==1.7.1
Django==1.11.7
drumhat==0.0.5
envirophat==0.0.6
ExplorerHAT==0.4.2
Flask==0.12.2
fourletterphat==0.0.2
gitdb2==2.0.3
GitPython==2.1.7
gpiozero==1.4.0
idna==2.6
itsdangerous==0.24
jedi==0.10.2
Jinja2==2.10
keyring==10.1
keyrings.alt==1.3
loady==1.7.4
MarkupSafe==1.0
mcpi==0.1.1
microdotphat==0.1.3
mote==0.0.3
motephat==0.0.2
numpy==1.12.1
oauthlib==2.0.1
pgzero==1.1
phatbeat==0.0.2
pianohat==0.0.5
picamera==1.13
picraft==1.0
piglow==1.2.4
pigpio==1.38
Pillow==4.0.0
PixelWeb==1.1.5
pyasn1==0.1.9
pycrypto==2.6.1
pygame==1.9.3
pygobject==3.22.0
pyinotify==0.9.6
PyJWT==1.4.2
pyOpenSSL==16.2.0
pyserial==3.4
python-apt==1.1.0b5
python-dateutil==2.6.1
pytz==2017.3
pyxdg==0.25
rainbowhat==0.0.2
requests==2.18.4
requests-oauthlib==0.7.0
RPi.GPIO==0.6.3
RTIMULib==7.2.1
scrollphat==0.0.7
scrollphathd==1.0.1
SecretStorage==2.3.1
sense-emu==1.0
sense-hat==2.2.0
simplejson==3.10.0
six==1.11.0
skywriter==0.0.7
smmap2==2.0.3
sn3218==1.2.7
spidev==3.0
thonny==2.1.10
touchphat==0.0.1
twython==3.4.0
urllib3==1.22
Werkzeug==0.12.2
pi@esquirepi:/opt/pianobar $ python testAllPixel.py
1
2
INFO - devices - Using COM Port: /dev/ttyACM0, Device ID: 0, Device Ver: 0
3
4
5
6
7
8
9
pi@esquirepi:/opt/pianobar $ cat testAllPixel.py
from bibliopixel import log
from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

print(“1”)
log.setLogLevel(“debug”)

print(“2”)
driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
print(“3”)
led=Strip(driver)
print(“4”)
led.fill([255,0,0])
print(“5”)
led.update()
print(“6”)
time.sleep(5)
print(“7”)
led.all_off()
print(“8”)
led.update()
print(“9”)

On Tuesday, December 5, 2017 at 5:57:22 PM UTC-6, Harold Breeden wrote:

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/a9a5eb62-c875-4a4f-9a51-8b674f1f6f07%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

Arg… It seems that there’s this thing called PiWheels (https://www.piwheels.hostedpi.com/) and it’s screwing with our python packages as the Pi looks there instead of the real PyPi.
Your BPA version is WAY wrong and I’m suspect of your BP version.

Will have to investigate… sadly later today. At work right now.

···

On Wed, Dec 6, 2017 at 8:10 AM, Adam Haile adammhaile@gmail.com wrote:

Harold,

These are the same exact LEDs on both Windows and the Pi? Just making sure you aren’t switching strips or something…

Try changing led.fill([255,0,0]) to led.fill([255,255,0]) - Just curious.
Also… how are you powering the LEDs?? If only via USB it’s likely the Pi doesn’t have enough power.

On Wed, Dec 6, 2017 at 7:02 AM, Tom Swirly tom@swirly.com wrote:

(I’ll have time tonight to look at this if Adam doesn’t get to resolve it today…)

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAOuQWfVuvLKiV8FzU-kw52PwYQ%2BMErorQHS3CnSZ%2BY4sk1bQmg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

On Wed, Dec 6, 2017 at 6:00 AM, Harold Breeden hdb4720@gmail.com wrote:

Not sure what has happened here …

I develop on a Windows 10 platform and had been playing my app on a Pi.

Since all was working well I had not tried using the Pi in the last two weeks. Just continued my development on Windows 10.

We are nearing deployment so I thought I better make sure the Pi is up to date.

Now the Pi, in fact multiple Pi’s, will not turn on the led’s at all.

To switch between the two platforms I simply unplug the USB cable attached to the AllPixel and plug it in to the other platform.

Therefore it is the same AllPixel, same led strip and same connections.

The Pi recognizes that the AllPixel is there by showing the port and not crashing if you try to define a driver without the board connected,

It recognizes all of the BiblioPixel structures, such that no python crashes occur.

Yet nothing turns on. I hook the All Pixel to the Windows platform and it works just fine.

I have updated BiblioPixel.

I am at a loss as to what changed since Nov 23.

I attached my simple test app. But here is what the code is:

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

from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

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

I have tried removing the c_order. No joy!

I have tried running without ledtype, but that fails during driver initialization.

When it runs on the Pi it seems to run normal except no leds turn on.

When it runs on Windows 10 all the leds turn red for 5 seconds and than turn off.

Any idea what has gone wrong?

(Full disclosure, I am pretty sure that when we finally resolve this it is going to be operator error on my part)

Harold

Alright here is the results after doing the pip install and adding line numbers. Still no leds.

Also the extra verbiage on the previous post when initializing the driver was due to me monkeying with NUMLEDS to see if that had any effect. It only does the extra verbiage when it is not the same configuration as the last time.

Here is the output:
pi@esquirepi:/opt/pianobar $ bibliopixel --version
BiblioPixel version 3.3.6
ERROR: No command entered
Valid: alias, all_pixel, clear_cache, color, devices, demo, run, update
pi@esquirepi:/opt/pianobar $ pip freeze
automationhat==0.0.4
beautifulsoup4==4.6.0
BiblioPixel==3.3.6
BiblioPixelAnimations==3.20171123.54201
BiblioPixelTriggers==1.0.1
blinker==1.3
blinkt==0.1.0
Cap1xxx==0.1.3
certifi==2017.11.5
chardet==3.0.4
click==6.7
colorama==0.3.7
croniter==0.3.20
cryptography==1.7.1
Django==1.11.7
drumhat==0.0.5
envirophat==0.0.6
ExplorerHAT==0.4.2
Flask==0.12.2
fourletterphat==0.0.2
gitdb2==2.0.3
GitPython==2.1.7
gpiozero==1.4.0
idna==2.6
itsdangerous==0.24
jedi==0.10.2
Jinja2==2.10
keyring==10.1
keyrings.alt==1.3
loady==1.7.4
MarkupSafe==1.0
mcpi==0.1.1
microdotphat==0.1.3
mote==0.0.3
motephat==0.0.2
numpy==1.12.1
oauthlib==2.0.1
pgzero==1.1
phatbeat==0.0.2
pianohat==0.0.5
picamera==1.13
picraft==1.0
piglow==1.2.4
pigpio==1.38
Pillow==4.0.0
PixelWeb==1.1.5
pyasn1==0.1.9
pycrypto==2.6.1
pygame==1.9.3
pygobject==3.22.0
pyinotify==0.9.6
PyJWT==1.4.2
pyOpenSSL==16.2.0
pyserial==3.4
python-apt==1.1.0b5
python-dateutil==2.6.1
pytz==2017.3
pyxdg==0.25
rainbowhat==0.0.2
requests==2.18.4
requests-oauthlib==0.7.0
RPi.GPIO==0.6.3
RTIMULib==7.2.1
scrollphat==0.0.7
scrollphathd==1.0.1
SecretStorage==2.3.1
sense-emu==1.0
sense-hat==2.2.0
simplejson==3.10.0
six==1.11.0
skywriter==0.0.7
smmap2==2.0.3
sn3218==1.2.7
spidev==3.0
thonny==2.1.10
touchphat==0.0.1
twython==3.4.0
urllib3==1.22
Werkzeug==0.12.2
pi@esquirepi:/opt/pianobar $ python testAllPixel.py
1
2
INFO - devices - Using COM Port: /dev/ttyACM0, Device ID: 0, Device Ver: 0
3
4
5
6
7
8
9
pi@esquirepi:/opt/pianobar $ cat testAllPixel.py
from bibliopixel import log
from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

print(“1”)
log.setLogLevel(“debug”)

print(“2”)
driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
print(“3”)
led=Strip(driver)
print(“4”)
led.fill([255,0,0])
print(“5”)
led.update()
print(“6”)
time.sleep(5)
print(“7”)
led.all_off()
print(“8”)
led.update()
print(“9”)

On Tuesday, December 5, 2017 at 5:57:22 PM UTC-6, Harold Breeden wrote:

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/a9a5eb62-c875-4a4f-9a51-8b674f1f6f07%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

What do you get from cat /etc/pip.conf?
also, clean everything up and then add --verbose to your pip install

···

On Wed, Dec 6, 2017 at 8:55 AM, Tom Swirly tom@swirly.com wrote:

I had a few spare minutes and I just tried to do a clean install of BP on a Raspberry Pi - I seemed to get the right versions!

Successfully installed BiblioPixelAnimations-3.20170913.13846 BiblioPixelTriggers-1.0.1 GitPython-2.1.7 Jinja2-2.10 MarkupSafe-1.0 Werkzeug-0.12.2 beautifulsoup4-4.6.0 bibliopixel-3.3.6 certifi-2017.11.5 chardet-3.0.4 click-6.7 croniter-0.3.20 flask-0.12.2 gitdb2-2.0.3 idna-2.6 itsdangerous-0.24 loady-1.7.4 python-dateutil-2.6.1 requests-2.18.4 six-1.11.0 smmap2-2.0.3 urllib3-1.22

But yes, PiWheels does seem to exist. I wasn’t able to tell if my clean install hit them or not, any idea on how to do that?

On Wed, Dec 6, 2017 at 2:24 PM, Adam Haile adammhaile@gmail.com wrote:

Arg… It seems that there’s this thing called PiWheels (https://www.piwheels.hostedpi.com/) and it’s screwing with our python packages as the Pi looks there instead of the real PyPi.
Your BPA version is WAY wrong and I’m suspect of your BP version.

Will have to investigate… sadly later today. At work right now.

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAG8g-TYSYz6DUAwuwcc-Ys7VGHbOoe0x5Wo_fh51dH%2BXSZ1PNg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

On Wed, Dec 6, 2017 at 8:10 AM, Adam Haile adammhaile@gmail.com wrote:

Harold,

These are the same exact LEDs on both Windows and the Pi? Just making sure you aren’t switching strips or something…

Try changing led.fill([255,0,0]) to led.fill([255,255,0]) - Just curious.
Also… how are you powering the LEDs?? If only via USB it’s likely the Pi doesn’t have enough power.

On Wed, Dec 6, 2017 at 7:02 AM, Tom Swirly tom@swirly.com wrote:

(I’ll have time tonight to look at this if Adam doesn’t get to resolve it today…)

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAOuQWfVuvLKiV8FzU-kw52PwYQ%2BMErorQHS3CnSZ%2BY4sk1bQmg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

On Wed, Dec 6, 2017 at 6:00 AM, Harold Breeden hdb4720@gmail.com wrote:

Not sure what has happened here …

I develop on a Windows 10 platform and had been playing my app on a Pi.

Since all was working well I had not tried using the Pi in the last two weeks. Just continued my development on Windows 10.

We are nearing deployment so I thought I better make sure the Pi is up to date.

Now the Pi, in fact multiple Pi’s, will not turn on the led’s at all.

To switch between the two platforms I simply unplug the USB cable attached to the AllPixel and plug it in to the other platform.

Therefore it is the same AllPixel, same led strip and same connections.

The Pi recognizes that the AllPixel is there by showing the port and not crashing if you try to define a driver without the board connected,

It recognizes all of the BiblioPixel structures, such that no python crashes occur.

Yet nothing turns on. I hook the All Pixel to the Windows platform and it works just fine.

I have updated BiblioPixel.

I am at a loss as to what changed since Nov 23.

I attached my simple test app. But here is what the code is:

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

from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

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

I have tried removing the c_order. No joy!

I have tried running without ledtype, but that fails during driver initialization.

When it runs on the Pi it seems to run normal except no leds turn on.

When it runs on Windows 10 all the leds turn red for 5 seconds and than turn off.

Any idea what has gone wrong?

(Full disclosure, I am pretty sure that when we finally resolve this it is going to be operator error on my part)

Harold

Alright here is the results after doing the pip install and adding line numbers. Still no leds.

Also the extra verbiage on the previous post when initializing the driver was due to me monkeying with NUMLEDS to see if that had any effect. It only does the extra verbiage when it is not the same configuration as the last time.

Here is the output:
pi@esquirepi:/opt/pianobar $ bibliopixel --version
BiblioPixel version 3.3.6
ERROR: No command entered
Valid: alias, all_pixel, clear_cache, color, devices, demo, run, update
pi@esquirepi:/opt/pianobar $ pip freeze
automationhat==0.0.4
beautifulsoup4==4.6.0
BiblioPixel==3.3.6
BiblioPixelAnimations==3.20171123.54201
BiblioPixelTriggers==1.0.1
blinker==1.3
blinkt==0.1.0
Cap1xxx==0.1.3
certifi==2017.11.5
chardet==3.0.4
click==6.7
colorama==0.3.7
croniter==0.3.20
cryptography==1.7.1
Django==1.11.7
drumhat==0.0.5
envirophat==0.0.6
ExplorerHAT==0.4.2
Flask==0.12.2
fourletterphat==0.0.2
gitdb2==2.0.3
GitPython==2.1.7
gpiozero==1.4.0
idna==2.6
itsdangerous==0.24
jedi==0.10.2
Jinja2==2.10
keyring==10.1
keyrings.alt==1.3
loady==1.7.4
MarkupSafe==1.0
mcpi==0.1.1
microdotphat==0.1.3
mote==0.0.3
motephat==0.0.2
numpy==1.12.1
oauthlib==2.0.1
pgzero==1.1
phatbeat==0.0.2
pianohat==0.0.5
picamera==1.13
picraft==1.0
piglow==1.2.4
pigpio==1.38
Pillow==4.0.0
PixelWeb==1.1.5
pyasn1==0.1.9
pycrypto==2.6.1
pygame==1.9.3
pygobject==3.22.0
pyinotify==0.9.6
PyJWT==1.4.2
pyOpenSSL==16.2.0
pyserial==3.4
python-apt==1.1.0b5
python-dateutil==2.6.1
pytz==2017.3
pyxdg==0.25
rainbowhat==0.0.2
requests==2.18.4
requests-oauthlib==0.7.0
RPi.GPIO==0.6.3
RTIMULib==7.2.1
scrollphat==0.0.7
scrollphathd==1.0.1
SecretStorage==2.3.1
sense-emu==1.0
sense-hat==2.2.0
simplejson==3.10.0
six==1.11.0
skywriter==0.0.7
smmap2==2.0.3
sn3218==1.2.7
spidev==3.0
thonny==2.1.10
touchphat==0.0.1
twython==3.4.0
urllib3==1.22
Werkzeug==0.12.2
pi@esquirepi:/opt/pianobar $ python testAllPixel.py
1
2
INFO - devices - Using COM Port: /dev/ttyACM0, Device ID: 0, Device Ver: 0
3
4
5
6
7
8
9
pi@esquirepi:/opt/pianobar $ cat testAllPixel.py
from bibliopixel import log
from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

print(“1”)
log.setLogLevel(“debug”)

print(“2”)
driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
print(“3”)
led=Strip(driver)
print(“4”)
led.fill([255,0,0])
print(“5”)
led.update()
print(“6”)
time.sleep(5)
print(“7”)
led.all_off()
print(“8”)
led.update()
print(“9”)

On Tuesday, December 5, 2017 at 5:57:22 PM UTC-6, Harold Breeden wrote:

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/a9a5eb62-c875-4a4f-9a51-8b674f1f6f07%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

Weird… mine does.
What are the outputs of cat /etc/os-release and uname -a

···

On Wed, Dec 6, 2017 at 9:41 AM, Tom Swirly tom@swirly.com wrote:

I at least have no /etc/pip.conf…

On Wed, Dec 6, 2017 at 3:00 PM, Adam Haile adammhaile@gmail.com wrote:

What do you get from cat /etc/pip.conf?
also, clean everything up and then add --verbose to your pip install


/t

https://tom.ritchford.com

https://tom.swirly.com

On Wed, Dec 6, 2017 at 8:55 AM, Tom Swirly tom@swirly.com wrote:

I had a few spare minutes and I just tried to do a clean install of BP on a Raspberry Pi - I seemed to get the right versions!

Successfully installed BiblioPixelAnimations-3.20170913.13846 BiblioPixelTriggers-1.0.1 GitPython-2.1.7 Jinja2-2.10 MarkupSafe-1.0 Werkzeug-0.12.2 beautifulsoup4-4.6.0 bibliopixel-3.3.6 certifi-2017.11.5 chardet-3.0.4 click-6.7 croniter-0.3.20 flask-0.12.2 gitdb2-2.0.3 idna-2.6 itsdangerous-0.24 loady-1.7.4 python-dateutil-2.6.1 requests-2.18.4 six-1.11.0 smmap2-2.0.3 urllib3-1.22

But yes, PiWheels does seem to exist. I wasn’t able to tell if my clean install hit them or not, any idea on how to do that?

On Wed, Dec 6, 2017 at 2:24 PM, Adam Haile adammhaile@gmail.com wrote:

Arg… It seems that there’s this thing called PiWheels (https://www.piwheels.hostedpi.com/) and it’s screwing with our python packages as the Pi looks there instead of the real PyPi.
Your BPA version is WAY wrong and I’m suspect of your BP version.

Will have to investigate… sadly later today. At work right now.

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAG8g-TYSYz6DUAwuwcc-Ys7VGHbOoe0x5Wo_fh51dH%2BXSZ1PNg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

On Wed, Dec 6, 2017 at 8:10 AM, Adam Haile adammhaile@gmail.com wrote:

Harold,

These are the same exact LEDs on both Windows and the Pi? Just making sure you aren’t switching strips or something…

Try changing led.fill([255,0,0]) to led.fill([255,255,0]) - Just curious.
Also… how are you powering the LEDs?? If only via USB it’s likely the Pi doesn’t have enough power.

On Wed, Dec 6, 2017 at 7:02 AM, Tom Swirly tom@swirly.com wrote:

(I’ll have time tonight to look at this if Adam doesn’t get to resolve it today…)

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAOuQWfVuvLKiV8FzU-kw52PwYQ%2BMErorQHS3CnSZ%2BY4sk1bQmg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

On Wed, Dec 6, 2017 at 6:00 AM, Harold Breeden hdb4720@gmail.com wrote:

Not sure what has happened here …

I develop on a Windows 10 platform and had been playing my app on a Pi.

Since all was working well I had not tried using the Pi in the last two weeks. Just continued my development on Windows 10.

We are nearing deployment so I thought I better make sure the Pi is up to date.

Now the Pi, in fact multiple Pi’s, will not turn on the led’s at all.

To switch between the two platforms I simply unplug the USB cable attached to the AllPixel and plug it in to the other platform.

Therefore it is the same AllPixel, same led strip and same connections.

The Pi recognizes that the AllPixel is there by showing the port and not crashing if you try to define a driver without the board connected,

It recognizes all of the BiblioPixel structures, such that no python crashes occur.

Yet nothing turns on. I hook the All Pixel to the Windows platform and it works just fine.

I have updated BiblioPixel.

I am at a loss as to what changed since Nov 23.

I attached my simple test app. But here is what the code is:

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

from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

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

I have tried removing the c_order. No joy!

I have tried running without ledtype, but that fails during driver initialization.

When it runs on the Pi it seems to run normal except no leds turn on.

When it runs on Windows 10 all the leds turn red for 5 seconds and than turn off.

Any idea what has gone wrong?

(Full disclosure, I am pretty sure that when we finally resolve this it is going to be operator error on my part)

Harold

Alright here is the results after doing the pip install and adding line numbers. Still no leds.

Also the extra verbiage on the previous post when initializing the driver was due to me monkeying with NUMLEDS to see if that had any effect. It only does the extra verbiage when it is not the same configuration as the last time.

Here is the output:
pi@esquirepi:/opt/pianobar $ bibliopixel --version
BiblioPixel version 3.3.6
ERROR: No command entered
Valid: alias, all_pixel, clear_cache, color, devices, demo, run, update
pi@esquirepi:/opt/pianobar $ pip freeze
automationhat==0.0.4
beautifulsoup4==4.6.0
BiblioPixel==3.3.6
BiblioPixelAnimations==3.20171123.54201
BiblioPixelTriggers==1.0.1
blinker==1.3
blinkt==0.1.0
Cap1xxx==0.1.3
certifi==2017.11.5
chardet==3.0.4
click==6.7
colorama==0.3.7
croniter==0.3.20
cryptography==1.7.1
Django==1.11.7
drumhat==0.0.5
envirophat==0.0.6
ExplorerHAT==0.4.2
Flask==0.12.2
fourletterphat==0.0.2
gitdb2==2.0.3
GitPython==2.1.7
gpiozero==1.4.0
idna==2.6
itsdangerous==0.24
jedi==0.10.2
Jinja2==2.10
keyring==10.1
keyrings.alt==1.3
loady==1.7.4
MarkupSafe==1.0
mcpi==0.1.1
microdotphat==0.1.3
mote==0.0.3
motephat==0.0.2
numpy==1.12.1
oauthlib==2.0.1
pgzero==1.1
phatbeat==0.0.2
pianohat==0.0.5
picamera==1.13
picraft==1.0
piglow==1.2.4
pigpio==1.38
Pillow==4.0.0
PixelWeb==1.1.5
pyasn1==0.1.9
pycrypto==2.6.1
pygame==1.9.3
pygobject==3.22.0
pyinotify==0.9.6
PyJWT==1.4.2
pyOpenSSL==16.2.0
pyserial==3.4
python-apt==1.1.0b5
python-dateutil==2.6.1
pytz==2017.3
pyxdg==0.25
rainbowhat==0.0.2
requests==2.18.4
requests-oauthlib==0.7.0
RPi.GPIO==0.6.3
RTIMULib==7.2.1
scrollphat==0.0.7
scrollphathd==1.0.1
SecretStorage==2.3.1
sense-emu==1.0
sense-hat==2.2.0
simplejson==3.10.0
six==1.11.0
skywriter==0.0.7
smmap2==2.0.3
sn3218==1.2.7
spidev==3.0
thonny==2.1.10
touchphat==0.0.1
twython==3.4.0
urllib3==1.22
Werkzeug==0.12.2
pi@esquirepi:/opt/pianobar $ python testAllPixel.py
1
2
INFO - devices - Using COM Port: /dev/ttyACM0, Device ID: 0, Device Ver: 0
3
4
5
6
7
8
9
pi@esquirepi:/opt/pianobar $ cat testAllPixel.py
from bibliopixel import log
from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

print(“1”)
log.setLogLevel(“debug”)

print(“2”)
driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
print(“3”)
led=Strip(driver)
print(“4”)
led.fill([255,0,0])
print(“5”)
led.update()
print(“6”)
time.sleep(5)
print(“7”)
led.all_off()
print(“8”)
led.update()
print(“9”)

On Tuesday, December 5, 2017 at 5:57:22 PM UTC-6, Harold Breeden wrote:

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/a9a5eb62-c875-4a4f-9a51-8b674f1f6f07%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

That’s why… this is only starting with Stretch (Debian 9 based).
I’ve reached out to the piwheels people to get our stuff removed. There is some stuff I could do to BPA to make the version numbers not wrong, but either way they are picking up really old stuff, so for now I’d rather get them to just remove it. It’s pure python, so there’s absolutely no point in being there.

···

On Wed, Dec 6, 2017 at 9:54 AM, Tom Swirly tom@swirly.com wrote:

$ cat /etc/os-release

PRETTY_NAME=“Raspbian GNU/Linux 8 (jessie)”

NAME=“Raspbian GNU/Linux”

VERSION_ID=“8”

VERSION=“8 (jessie)”

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

$ uname -a

Linux chopin 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux

On Wed, Dec 6, 2017 at 3:44 PM, Adam Haile adammhaile@gmail.com wrote:

Weird… mine does.
What are the outputs of cat /etc/os-release and uname -a

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAG8g-TbnKC0u1teJPJGKHZpjnp1%3DMqkgBKFsWyDT6XgiVu6Pvw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

On Wed, Dec 6, 2017 at 9:41 AM, Tom Swirly tom@swirly.com wrote:

I at least have no /etc/pip.conf…

On Wed, Dec 6, 2017 at 3:00 PM, Adam Haile adammhaile@gmail.com wrote:

What do you get from cat /etc/pip.conf?
also, clean everything up and then add --verbose to your pip install


/t

https://tom.ritchford.com

https://tom.swirly.com

On Wed, Dec 6, 2017 at 8:55 AM, Tom Swirly tom@swirly.com wrote:

I had a few spare minutes and I just tried to do a clean install of BP on a Raspberry Pi - I seemed to get the right versions!

Successfully installed BiblioPixelAnimations-3.20170913.13846 BiblioPixelTriggers-1.0.1 GitPython-2.1.7 Jinja2-2.10 MarkupSafe-1.0 Werkzeug-0.12.2 beautifulsoup4-4.6.0 bibliopixel-3.3.6 certifi-2017.11.5 chardet-3.0.4 click-6.7 croniter-0.3.20 flask-0.12.2 gitdb2-2.0.3 idna-2.6 itsdangerous-0.24 loady-1.7.4 python-dateutil-2.6.1 requests-2.18.4 six-1.11.0 smmap2-2.0.3 urllib3-1.22

But yes, PiWheels does seem to exist. I wasn’t able to tell if my clean install hit them or not, any idea on how to do that?

On Wed, Dec 6, 2017 at 2:24 PM, Adam Haile adammhaile@gmail.com wrote:

Arg… It seems that there’s this thing called PiWheels (https://www.piwheels.hostedpi.com/) and it’s screwing with our python packages as the Pi looks there instead of the real PyPi.
Your BPA version is WAY wrong and I’m suspect of your BP version.

Will have to investigate… sadly later today. At work right now.

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAG8g-TYSYz6DUAwuwcc-Ys7VGHbOoe0x5Wo_fh51dH%2BXSZ1PNg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

On Wed, Dec 6, 2017 at 8:10 AM, Adam Haile adammhaile@gmail.com wrote:

Harold,

These are the same exact LEDs on both Windows and the Pi? Just making sure you aren’t switching strips or something…

Try changing led.fill([255,0,0]) to led.fill([255,255,0]) - Just curious.
Also… how are you powering the LEDs?? If only via USB it’s likely the Pi doesn’t have enough power.

On Wed, Dec 6, 2017 at 7:02 AM, Tom Swirly tom@swirly.com wrote:

(I’ll have time tonight to look at this if Adam doesn’t get to resolve it today…)

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAOuQWfVuvLKiV8FzU-kw52PwYQ%2BMErorQHS3CnSZ%2BY4sk1bQmg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

On Wed, Dec 6, 2017 at 6:00 AM, Harold Breeden hdb4720@gmail.com wrote:

Not sure what has happened here …

I develop on a Windows 10 platform and had been playing my app on a Pi.

Since all was working well I had not tried using the Pi in the last two weeks. Just continued my development on Windows 10.

We are nearing deployment so I thought I better make sure the Pi is up to date.

Now the Pi, in fact multiple Pi’s, will not turn on the led’s at all.

To switch between the two platforms I simply unplug the USB cable attached to the AllPixel and plug it in to the other platform.

Therefore it is the same AllPixel, same led strip and same connections.

The Pi recognizes that the AllPixel is there by showing the port and not crashing if you try to define a driver without the board connected,

It recognizes all of the BiblioPixel structures, such that no python crashes occur.

Yet nothing turns on. I hook the All Pixel to the Windows platform and it works just fine.

I have updated BiblioPixel.

I am at a loss as to what changed since Nov 23.

I attached my simple test app. But here is what the code is:

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

from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

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

I have tried removing the c_order. No joy!

I have tried running without ledtype, but that fails during driver initialization.

When it runs on the Pi it seems to run normal except no leds turn on.

When it runs on Windows 10 all the leds turn red for 5 seconds and than turn off.

Any idea what has gone wrong?

(Full disclosure, I am pretty sure that when we finally resolve this it is going to be operator error on my part)

Harold

Alright here is the results after doing the pip install and adding line numbers. Still no leds.

Also the extra verbiage on the previous post when initializing the driver was due to me monkeying with NUMLEDS to see if that had any effect. It only does the extra verbiage when it is not the same configuration as the last time.

Here is the output:
pi@esquirepi:/opt/pianobar $ bibliopixel --version
BiblioPixel version 3.3.6
ERROR: No command entered
Valid: alias, all_pixel, clear_cache, color, devices, demo, run, update
pi@esquirepi:/opt/pianobar $ pip freeze
automationhat==0.0.4
beautifulsoup4==4.6.0
BiblioPixel==3.3.6
BiblioPixelAnimations==3.20171123.54201
BiblioPixelTriggers==1.0.1
blinker==1.3
blinkt==0.1.0
Cap1xxx==0.1.3
certifi==2017.11.5
chardet==3.0.4
click==6.7
colorama==0.3.7
croniter==0.3.20
cryptography==1.7.1
Django==1.11.7
drumhat==0.0.5
envirophat==0.0.6
ExplorerHAT==0.4.2
Flask==0.12.2
fourletterphat==0.0.2
gitdb2==2.0.3
GitPython==2.1.7
gpiozero==1.4.0
idna==2.6
itsdangerous==0.24
jedi==0.10.2
Jinja2==2.10
keyring==10.1
keyrings.alt==1.3
loady==1.7.4
MarkupSafe==1.0
mcpi==0.1.1
microdotphat==0.1.3
mote==0.0.3
motephat==0.0.2
numpy==1.12.1
oauthlib==2.0.1
pgzero==1.1
phatbeat==0.0.2
pianohat==0.0.5
picamera==1.13
picraft==1.0
piglow==1.2.4
pigpio==1.38
Pillow==4.0.0
PixelWeb==1.1.5
pyasn1==0.1.9
pycrypto==2.6.1
pygame==1.9.3
pygobject==3.22.0
pyinotify==0.9.6
PyJWT==1.4.2
pyOpenSSL==16.2.0
pyserial==3.4
python-apt==1.1.0b5
python-dateutil==2.6.1
pytz==2017.3
pyxdg==0.25
rainbowhat==0.0.2
requests==2.18.4
requests-oauthlib==0.7.0
RPi.GPIO==0.6.3
RTIMULib==7.2.1
scrollphat==0.0.7
scrollphathd==1.0.1
SecretStorage==2.3.1
sense-emu==1.0
sense-hat==2.2.0
simplejson==3.10.0
six==1.11.0
skywriter==0.0.7
smmap2==2.0.3
sn3218==1.2.7
spidev==3.0
thonny==2.1.10
touchphat==0.0.1
twython==3.4.0
urllib3==1.22
Werkzeug==0.12.2
pi@esquirepi:/opt/pianobar $ python testAllPixel.py
1
2
INFO - devices - Using COM Port: /dev/ttyACM0, Device ID: 0, Device Ver: 0
3
4
5
6
7
8
9
pi@esquirepi:/opt/pianobar $ cat testAllPixel.py
from bibliopixel import log
from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

print(“1”)
log.setLogLevel(“debug”)

print(“2”)
driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
print(“3”)
led=Strip(driver)
print(“4”)
led.fill([255,0,0])
print(“5”)
led.update()
print(“6”)
time.sleep(5)
print(“7”)
led.all_off()
print(“8”)
led.update()
print(“9”)

On Tuesday, December 5, 2017 at 5:57:22 PM UTC-6, Harold Breeden wrote:

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/a9a5eb62-c875-4a4f-9a51-8b674f1f6f07%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

Well, … Never mind!

As I had stated earlier it was probably going to be a classic operator error issue.

I had a disconnected ground wire from the 5V power supply to the breadboard. (I am moving to a soldered-breadboard later today).

Now why it worked on Windows, or not necessarily Windows as much as a laptop, and not on the Raspberry Pi is still a curiosity.

There has to have been a secondary means that the laptop was providing power ground to the led strips.

I will go ahead and answer the open questions just to fully clarify this whole situation.

Adam asked whether or not I was using the same led strips. I am.

Adam also asked about power. From the beginning I had used a 5v power supply to provide power to the led strips not willing to assume the USB port, either laptop or Pi, could effectively drive the leds.

My hardware setup is as follows:

  1. USB cable to AllPixel Mini Universal
  2. Connected AllPixel Data to Row E of a breadboard
  3. Connected AllPixel Ground to Ground on breadboard (-)
  4. Connected 5v power supply Ground to breadboard Ground (-)
  5. Connected 5v power supply Power to breadboard Power (+)
  6. Connected breadboard Row E to led strip Data
  7. Connected breadboard Ground to led strip Ground
  8. Connected breadboard Power (+) to led strip 5V

So as you see that the AllPixel, the led strip and the power supply share a common ground.

In moving from the Windows laptop to the Pi I simply moved the USB cable between the two platforms leaving all of the breadboard, power supply and led connections in place.

One thing I did do that is a little unconventional (?) is that I actually run two led strips off of the same Data row. This provides two parallel lines that are part of the piece we are working on. My only concern about this setup was whether or not my 5v 10a power supply could drive both lines, but so far seems to work very nicely.

So as I ate breakfast this morning and reviewing in my mind your comments concerning BiblioPixel and such it occurred to me that it had to be a power or ground issue. All of the AllPixel, BiblioPixel and Python seemed to be functioning properly as indicated in the testAllPixel.py running through all the line numbers without error. And the fact that just two weeks ago it worked fine on the Pi. And multiple Pi had the same issue. This had to be either a power or a ground issue.

When I pulled the breadboard out a little to look at it I saw that the ground from the 5v power supply was disconnected from the breadboard. (Pretty sure it was that darn cat wandering around on my desk when I am not in here)

After reviewing and verifying all the other connections I plugged the 5v ground back in and the led strip fired back up.

Now how the laptop connected to exactly the same setup (not just logically, but physically) functioned whereas the Pi did not I cannot explain. I have worked in IT hardware and software for over 40 years now and this set of circumstances just does not compute. Missing ground from the power connection should have shut down power regardless of which platform was connected at the time. The laptop had to be providing some means through the USB to provide common ground, but still the power supply ground was disconnected. How can that possibly work? Yet it worked on the laptop, but not on the Pi.

This is the second ground issue I have resolved while working on this project. Earlier, back when the Pi was still working and I was running the project on the Pi and the laptop I had a color issue. Some colors, not all, would have a very distinctive change in color the further down the line you got on the strip. One in particular, Blanched Almond, would be the right color for about 100 led’s, than start assuming more Red until at the end of 300 led’s it was almost Blood Orange (not sure that is actually a color name, but that was the impression I got of the color). Anyway what I found was that the ground from the power input on one of the two led strips was loose. Not disconnected, but loose. I tightened up the connection and suddenly I get the same color all the way down both strips for all of the 300 leds. Now why a “loose” ground on power to one strip would result in a change in color in both strips I cannot explain. I cannot explain why a “loose” ground would change color based on distance. Nor can I explain why a “loose” ground on one strip affected the parallel strip.

Moral of this story, if something is just weird and/or makes no sense, check your ground!

I cannot express enough how grateful I am to your attention to this issue.

I will continue working with AllPixel and BiblioPixel and let you know how my blinky things adventure progresses.

Hope to share this project with you soon after installation and debut.

Harold

···

On Tuesday, December 5, 2017 at 5:57:22 PM UTC-6, Harold Breeden wrote:

Not sure what has happened here …

I develop on a Windows 10 platform and had been playing my app on a Pi.

Since all was working well I had not tried using the Pi in the last two weeks. Just continued my development on Windows 10.

We are nearing deployment so I thought I better make sure the Pi is up to date.

Now the Pi, in fact multiple Pi’s, will not turn on the led’s at all.

To switch between the two platforms I simply unplug the USB cable attached to the AllPixel and plug it in to the other platform.

Therefore it is the same AllPixel, same led strip and same connections.

The Pi recognizes that the AllPixel is there by showing the port and not crashing if you try to define a driver without the board connected,

It recognizes all of the BiblioPixel structures, such that no python crashes occur.

Yet nothing turns on. I hook the All Pixel to the Windows platform and it works just fine.

I have updated BiblioPixel.

I am at a loss as to what changed since Nov 23.

I attached my simple test app. But here is what the code is:

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

from bibliopixel import *
from bibliopixel.drivers.serial import *

import time

driver=Serial(num=300,ledtype=“WS2812B”,c_order=“GRB”)
led=Strip(driver)
led.fill([255,0,0])
led.update()
time.sleep(5)
led.all_off()
led.update()

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

I have tried removing the c_order. No joy!

I have tried running without ledtype, but that fails during driver initialization.

When it runs on the Pi it seems to run normal except no leds turn on.

When it runs on Windows 10 all the leds turn red for 5 seconds and than turn off.

Any idea what has gone wrong?

(Full disclosure, I am pretty sure that when we finally resolve this it is going to be operator error on my part)

Harold