-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"accepted connection" but no lights #14
Comments
Could this be a duplicate of my current issue? |
I have read through all the comments and cant really say if its the same because I,m a complete newbie at this |
would commenting out the slacktoken and twitter stuff below in config/index.js get me anywhere ? |
Hi @dallen98 commenting out those fields won't help but it will lead to a cleaner console output. We need to turn those off by default really. It sounds like you're definitely really close to getting your LED's working with rio! First things first, you don't need to manually run any python script to communicate with the wall. The python script is actually run from within the node process so all you need is It is therefore possible you configured the wrong python script? The one you need to configure to suit your own LED wall is |
Feel free to also link me/attach your python script and your |
Hi and yes I can confirm the "npm start" works for me, I can see in server/outputs/pi-output.js mention of lowlevel-server.py In my rio-server/firmware/rpi/lowlevel-server.py I guesssed at the number of pixels and wrote 50 on pin 18 and 50 on pin 19 because ive got them still in there original reels across my desk. |
No I do not believe its critical to get the LED count right for them to light up. Just to be sure have you definitely enabled Python output: Opening socket... The GUID on the last line will of course be different. |
Hello I did a fresh install on my pi3 with raspbian full version, I have npm and node now installed being... In another terminal root@raspberrypi:/home/pi/rio/rio-server# npm start
warn: SlackDataStore is deprecated and will be removed in the next major version. See project documentation for a migration guide. then the gif plays, what i,m not seeing is lights or your fourth line that begins with Sending XXXX.... I then reboot and retry with just the... I then try ls /tmp and can see app.main |
what follows below is the log of the rio installation... d rio && npm run install-server ../src/CanvasRenderingContext2d.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE Context2d::SetFontFace(Nan::NAN_METHOD_ARGS_TYPE)’:
Downloaded youtube-dl 2018.12.09 added 183 packages from 134 contributors and audited 486 packages in 112.104s |
Ah you have Also please paste your |
Blimey activity on my lights at last, I dont have the led,s formed into a matrix yet so cant tell if the output is gibberish but hey looking good thanks here is my current ammended index.js with "SendToConsole false... /**
here is my current lowlevel-server.py... -- coding: utf-8 --import socket LED strip configuration:LED_COUNT = 20 # Number of LED pixels. LED_2_COUNT = 20 # Number of LED pixels. if name == 'main':
|
Awesome yes i took at the code and we were prioritising sending to console instead of sending to LEDs. I have now changed that in master. By the way if your matrix is 15x4 then your LED counts in |
About the matrix, I plan on a 16:9 aspect ratio screen so I calculate for example 48 pixels wide by 27 pixel rows high (48x27=1296 pixels total) (1296 divided by two = 648 LED_COUNT on pin 18 and ditto 648 LED_COUNT on pin 19 |
Yep that all sounds right. In fact the wall we built for use with rio was 60x34 and 2m wide! I cannot recall what the maximum number of pixels you can drive through each GPIO pin is, I believe its just the more you have the more your update rate suffers. Assuming you are powering the strips with an external 5v power supply 1296 pixels will be a breeze. |
I see the simpsons video gif on your rio intro page there seems to be some dropout of pixels towards the bottom of the image, did you have any problems playing full motion video across the 60x34 pixels ? is there anywhere in the code to alter the framerate up or down ? |
Nope that would just be our primitive electrical skills! We found that the wall had to be evenly powered across all the strips and I think towards the bottom had less power running through it. I think the entire bottom strip might not have worked due to some issues during soldering :D. With regards to framerate, in the case of GIFs the delay between frames is pulled from the GIF itself. In order to effect it you'd have to manipulate the delay returned from |
Is the frame rate restricted by the distance the signal has to travel (in my case 2 meters x 1.1 meters using the 30 pixels per mt ws2812b) or is the raspberry pi cpu/gpu the bottleneck, I have on order the newest rspb 3+, will be giving it a try. |
First thing to say is great project, I am using raspberry pi 3 with ws2812b leds connected via SN74HCT125N logic buffer. The strandtest.py and singlestrandtest.py both work using... root@raspberrypi:/home/pi/rio/rio-server# python ./firmware/rpi/singlestrandtest.py
Press Ctrl-C to quit.
and...
root@raspberrypi:/home/pi/rio/rio-server# python ./firmware/rpi/strandtest.py
Press Ctrl-C to quit
after reboot I then run this first... root@raspberrypi:/home/pi/rio/rio-server# python ./firmware/rpi/server.py
and get...
Opening socket...
Listening...
In another terminal i then run... root@raspberrypi:/home/pi/rio# npm run server
and get the following output and then the rio gif playing in the terminal window only
warn: SlackDataStore is deprecated and will be removed in the next major version. See project documentation for a migration guide.
error: Response not OK: not_authed
error: Disconnecting because not_authed is not recoverable
error: message=not_authed, stack=Error: not_authed
at handleHttpResponse (/home/pi/rio/rio-server/node_modules/@slack/client/lib/clients/transports/call-transport.js:103:17)
at handleTransportResponse (/home/pi/rio/rio-server/node_modules/@slack/client/lib/clients/transports/call-transport.js:153:19)
at apply (/home/pi/rio/rio-server/node_modules/lodash/lodash.js:478:17)
at wrapper (/home/pi/rio/rio-server/node_modules/lodash/lodash.js:5323:16)
at Request.handleRequestTranportRes (/home/pi/rio/rio-server/node_modules/@slack/client/lib/clients/transports/request.js:21:5)
at apply (/home/pi/rio/rio-server/node_modules/lodash/lodash.js:478:17)
at Request.wrapper [as _callback] (/home/pi/rio/rio-server/node_modules/lodash/lodash.js:5323:16)
at Request.self.callback (/home/pi/rio/rio-server/node_modules/@slack/client/node_modules/request/request.js:186:22)
at Request.emit (events.js:180:13)
at Request. (/home/pi/rio/rio-server/node_modules/@slack/client/node_modules/request/request.js:1060:10)
at Request.emit (events.js:180:13)
at IncomingMessage. (/home/pi/rio/rio-server/node_modules/@slack/client/node_modules/request/request.js:980:12)
at Object.onceWrapper (events.js:272:13)
at IncomingMessage.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
...the rio gif now appears
I can see over in the other terminal that "accepted connection" now appears after the word "Listening"
In a third terminal window I enter this and get app.main...
pi@raspberrypi:~ $ ls /tmp
app.main
dhcpcd-pi
ssh-7ZeY9epPkKdF
ssh-dja66qrhWrUg
systemd-private-81a092c6c05543848163712ddf01092f-systemd-timesyncd.service-OKVx6R
But still no lit leds, perhaps you could steer me in the right direction thanks Dave
The text was updated successfully, but these errors were encountered: