Beiträge von Akriss

Zitat von Digiwill

ssh in: Jan 23 15:17:04 retropie hyperiond[452]: "rate" : 10000,

That differs from what you have in your previously posted configs. They have ""rate" : 115200,". Which is correct. As it matches the sketch's rate.

Hope it helps.

Hi,

Try appending:

spidev.bufsiz=32768

to /boot/cmdline.txt .

And add:

core_freq=250

to /boot/config.txt .

And reboot.

This is a fix for ws2812 leds running via SPI. However I'm thinking it may work for any SPI driven led.
It seems some distributions have settings that may not be optimal for SPI data transfer wile using SPI driven led's

I hope it helps.

Zitat von DiceBanga

ssh in: Jan 22 00:19:42 osmc hyperiond[2420]: Opening UART: /dev/ttyUSB0

That error is saying it can't find a arduino on ttyUSB0.

Maybe the arduino is on ttyUSB1 or /dev/ttyACM0?

Try this to find the port:
Boot the Rpi once with out the arduino attached and run this at the command prompt:

dmesg | grep "USB"

Copy or take note of the last 15-/+ or lines,
Now plug the arduino in the USB port and rerun the command:

dmesg | grep "USB"

And note the change in the output from before.
You should notice the port that the arduino is attached to.

Hope it helps.

Mmm.
I would not say problems. More limitations then anything.
When using SPI It seems the driver needs the cpu at a specific frequency,(as detailed Here ) So no overclocking the Rpi if driving leds from SPI. And you cant use any other SPI gadget at the same time.

Other then that it should work fine.

Zitat von JoeBee

Jan 19 16:15:47 jb-osmc systemd[1]: hyperion.service: Start request repeated too quickly.

Adding "RestartSec=15" to the [Service] section of the satartup file "hyperion.service" May help. I think.

Zitat von JoeBee

Can somebody give me a good link how to configure and what sketch the Arduino needed?

The sketch is (Here), It has good comments on how to configure within. If help is needed, just ask the forum.

Hope is of help.

Hi,
This page (Here) has very good info on the potential pitfalls of diving ws2812 leds from Rpi Gpio's.

Try black listing the "Broadcom audio kernel module" as detailed Here.

Or try driving the led's via SPI pin's.

Hope it's of help.

Zitat von SciLor

Whats the extra IC on the board is doing?

It's a SN74AHCT125N "Buffers & Line Drivers Tri-State Quad Bus "

I'm driving 240+ APA102a led's with that one, The wemos data lines are 3.3v. I thought it would be good to add a level shifter to the data and clock lines to bump up the voltages to 5v. to avoid problems.

I have made others that omit the level shifter that work well. However they ere less then 40 led in the string and ws2812 leds. I find level shifters work well when using lots of led's and driving the from 3.3v data lines.

Maybe something like this can work?
https://www.home-assistant.io/components/light.hyperion/

Hope it helps.

Looks like a voltage drop issue.

Split the power supply line feed to corners to spread the available volt's.

Hope it helps.

Not sure.
Try lowering:

#define serialRate 500000

And.

"rate"     : 500000,

Hope it helps.

Zitat von dani3

Code

// LED CONFIGURATION
    ...

That has been clipped, correct?

Zitat von Rob Neeson

every time i try to screenshot i get null device, is that correct

ssh out: sudo systemctl stop hyperion.service 2>/dev/null; sudo /etc/init.d/hyperion stop 2>/dev/null ; sudo /sbin/initctl stop hyperion 2>/dev/null
ssh disconnected
ssh connected
ssh out: sudo systemctl stop hyperion.service 2>/dev/null; sudo /etc/init.d/hyperion stop 2>/dev/null ; sudo /sbin/initctl stop hyperion 2>/dev/null

That just a stop script sending all possible types of stop commands .

Try to add a delay to the config:

"delayAfterConnect"  : 10,

I cant help any further until you are able to reliably start Hyperion with stable start up effect and able to reliably connect and control with the app.

You are jumping from step two, straight to step eleven.

Post your currant config file.

??

Zitat von Rob Neeson

still no lights

??

So you have the resistor in place now?

I think your grabber Is faulty.
just a guess.

How about from command line, with:

hyperion-v4l2 --screenshot

?

Hyperion needs to be shutdown prior the taking screenshot.

I sure that's detailed in the wiki.

Hmm. last post has 100000 in the log.

Ok then you need a resistor on the data line between the Uno and led's. A value between 330 to 470 ohm's usually works good.

That should calm the led's and show nice effects.

Change the rate in config from:

ssh in:     Jan 03 19:56:00 raspberrypi hyperiond[1583]:         "rate" : 100000,

To 500000, or match what is in the sketch for:

#define serialRate

Hmm. thought that command would show more.

Well, try both ttyACM0 and ttyUSB0. One is likely correct, one is not. process of elimination.

Restart Hyperion after making changes. One setting well make leds shine the startup. Hopefully =).

Good.

Make sure what usb port the Uno is on. You have "/dev/ttyACM0" its could be "/dev/ttyUSB0"

Make sure with :

dmesg | grep usb

once without the Uno attached and then with the Uno attached. you well notice the port its on.

Then use hypercon to craft and upload the config file.

If all go's well the leds should shine the startup effect upon Hyperion's startup.