2.5 nur für den pi ?? Hätte ich nie vermutet. Ich probiere es aus , danke.
Beiträge von MikeOO
-
-
Was am Grabber ankommt weiß ich nicht, der hängt ja am Pi und hat keinen separaten Stromanschluss. Oder .... sollte da einer rangelötet werden....oder ganz anders?
Pi und HDMI=> AV haben ein 2A NT, Splitter 1,5A.
-
Every device got a seperate 5v usb adapter, 1.5 amp.
Is there any way to get some kind of a software log file to see where the problem is ?
-
Need help please.
Short history of my ambilight attempts.
Set up the whole system and got it to work 5 weeks ago. My grabber became "unstable" after 3 weeks, ultimatly dying in week 4. Maybe overheated. Bought another grabber, which had the empia 28xx chipset inside. Not supported, but it worked. The casing couldnt be opened, so i sold it after some days (cause i wanted to attach a heatsink).when i got a new utv007-grabber
My newst 007-grabber worked out of the box, but only for ONE evening. Now when i screenshot, i get green lines AGAIN (that was the case with my dead first grabber, too).My question: why did my grabber die again, after one evening?
-
Thanks, i already thought in this direction but didnt expect to achieve anything. Your experience encouraged me, thanks. Gonna try this.
-
Not a single idea? What means "Failed with result 'signal'"
Code
Alles anzeigenNov 05 22:39:00 raspberrypi systemd[1]: Started Hyperion Systemd service. Nov 05 22:39:00 raspberrypi hyperiond[418]: Hyperion Ambilight Deamon (418) Nov 05 22:39:00 raspberrypi hyperiond[418]: Version : V1.03.3 (brindosch-2fbbcff/2f01dfa-1495880388 Nov 05 22:39:00 raspberrypi hyperiond[418]: Build Time: Jun 3 2017 02:06:37 Nov 05 22:39:00 raspberrypi hyperiond[418]: INFO: Selected configuration file: /etc/hyperion/hyperion.config.json Nov 05 22:39:00 raspberrypi hyperiond[418]: HYPERION INFO: ColorTransform 'default' => [0; 4] Nov 05 22:39:00 raspberrypi hyperiond[418]: HYPERION INFO: ColorCorrection 'default' => [0; 4] Nov 05 22:39:00 raspberrypi hyperiond[418]: HYPERION INFO: ColorAdjustment 'default' => [0; 4] Nov 05 22:39:00 raspberrypi hyperiond[418]: LEDDEVICE INFO: configuration: Nov 05 22:39:00 raspberrypi hyperiond[418]: { Nov 05 22:39:00 raspberrypi hyperiond[418]: "colorOrder" : "rgb", Nov 05 22:39:00 raspberrypi hyperiond[418]: "delayAfterConnect" : 0, Nov 05 22:39:00 raspberrypi hyperiond[418]: "name" : "MyHyperionConfig", Nov 05 22:39:00 raspberrypi hyperiond[418]: "output" : "/dev/ttyUSB0", Nov 05 22:39:00 raspberrypi hyperiond[418]: "rate" : 38400, Nov 05 22:39:00 raspberrypi hyperiond[418]: "type" : "atmo" Nov 05 22:39:00 raspberrypi hyperiond[418]: } Nov 05 22:39:00 raspberrypi hyperiond[418]: Opening UART: /dev/ttyUSB0 Nov 05 22:39:01 raspberrypi hyperiond[418]: INFO: Creating linear smoothing Nov 05 22:39:01 raspberrypi hyperiond[418]: HYPERION (CS) INFO: Created linear-smoothing(interval_ms=33;settlingTime_ms=600;updateDelay=0 Nov 05 22:39:01 raspberrypi hyperiond[418]: EFFECTENGINE INFO: 27 effects loaded from directory /usr/share/hyperion/effects Nov 05 22:39:01 raspberrypi hyperiond[418]: EFFECTENGINE INFO: Initializing Python interpreter Nov 05 22:39:01 raspberrypi hyperiond[418]: INFO: Hyperion started and initialised Nov 05 22:39:01 raspberrypi hyperiond[418]: INFO: Boot sequence 'Rainbow swirl fast' EFFECTENGINE INFO: run effect Rainbow swirl fast on channel 0 Nov 05 22:39:01 raspberrypi hyperiond[418]: BLACKBORDER INFO: threshold set to 0 (0) Nov 05 22:39:01 raspberrypi hyperiond[418]: BLACKBORDER INFO: mode:default Nov 05 22:39:01 raspberrypi hyperiond[418]: started Nov 05 22:39:01 raspberrypi hyperiond[418]: INFO: Json server created and started on port 19444 Nov 05 22:39:01 raspberrypi hyperiond[418]: INFO: Proto server created and started on port 19445 Nov 05 22:39:01 raspberrypi hyperiond[418]: terminate called after throwing an instance of 'std::runtime_error' Nov 05 22:39:01 raspberrypi hyperiond[418]: what(): V4L2GRABBER ERROR: Cannot identify '/dev/video0' ERROR 2, No such file or directory Nov 05 22:39:01 raspberrypi systemd[1]: hyperion.service: Main process exited, code=killed, status=6/ABRT Nov 05 22:39:01 raspberrypi systemd[1]: hyperion.service: Unit entered failed state. Nov 05 22:39:01 raspberrypi systemd[1]: hyperion.service: Failed with result 'signal'. Nov 05 22:39:01 raspberrypi systemd[1]: hyperion.service: Service hold-off time over, scheduling restart. Nov 05 22:39:01 raspberrypi systemd[1]: Stopped Hyperion Systemd service. Nov 05 22:39:01 raspberrypi systemd[1]: Started Hyperion Systemd service. Nov 05 22:39:01 raspberrypi hyperiond[426]: Hyperion Ambilight Deamon (426) Nov 05 22:39:01 raspberrypi hyperiond[426]: Version : V1.03.3 (brindosch-2fbbcff/2f01dfa-1495880388
-
My Hyperion Setup stops working, about every 3 days. The leds are still on, but in "background lightning" mode. It seems like the grabbing stopped, but thats just my guess.
Hyperion-app at android still works. The rpi itself works, i can ssh into it.
Only solution so far: wait one night, without powering the rpi.
What i tested already:
killall hyperiond and restart
resetting usb device (the grabber or the atmo) with a scriptEDIT: when i take a screenshot of the grabber i just get a thin green line.
Any Help?
-
Any Help in this case? The problem still occures from time to time. After a night of shutdown its always gone. A reboot is not enough, a short shutdown too. It has to be some hours.
-
2 (wonderful...) days my setup was working perfect. Thanks Devs!
Now i got a strange problem: the brightness seems to be much to high. That results in only white light, but no more colors.
When i reduce the luminance in Hypercon to 1 (sat remains 2), the colors are normal again. With 2 / 2, only white light.
The same goes for the color SSH-wheel in Hypercon: if i reduce the brightness there (while keeping 2/2 in Page 1), there is color again. With the normal setting in the wheel, i get only white light, no more color.
Of course meanwhile i created a json with lum1/sat2. But that has no effect: i have to manually reduce lum to 1 again in Hypercon manually to get colors,How to fix this? Already updated Hyperion without success.
-
Ok, now grabbing works, too. :):). With logilink and the settings above.
But not automatically.At the moment only the following way: start Hypercon (Windows), click start Hyperion. I thought it should start automatically when the pi boots?
-
A little success :).
USB0 works with 38.400. THe problem seems to be that the rpi or atmo or hyperions seems to need a fairly long time to switch between the settings i tested. When i waited 1 Minute right now, it works (i mean send a color!).
What still doesnt work is grabbing. When i click "take pic frome grabber" always the same pic is displayed.EDIT:
The Wiki says
Mumbi video grabber
Dazzle DVR
Fushicai UTV007Nonworking grabbers are:
LogilinkI got the logilink, cause many tutorials said so. It uses the 007-chipset.
-
It's likely to be either /dev/ttyUSB0 or /dev/ANA0 - have a look to see which one exists.
Hypercon should have a section for the device name - probably near thee baud rate.
For me there is
Type - Atmo
Output - ACM0
Baud - 38.400
Delay - 0 -
Defined a fifth one.
Send a color for testing purpose. Nothing happend.In my other thread you wrote " USB serial port name as seen by linux " - where to add this?
-
The problems / errors described in this and the old thread here are solved - i get no (general) error messages anymore. Reason was the sd-card; i remembered that this one was faulty sometimes. With the new card i get no error messages. I can ssh into the pi, your command # ldd hyperiond ends in directory not found.
But for example i can grab a pic from the grabber, so i think hyperion works?
Main problem is unsolved - how to connect to the Atmolight? I tried Atmo and Adalight, several baud rates. The best success i got was in the SSH-Log:
Codessh in: Okt 09 22:44:49 raspberrypi hyperiond[10152]: AtmoLight: 4 channels configured. This should always be 5!
=> the only sign (in Hyperion) i ever got that the atmolight is there. Btw lsusb finds the atmo.
EDIT: Thanks for the link !!
The source of the error mentioned :). But how to define 5 LED when Atmo only supports 4 ??
-
Is there anyone out there who tried to use Hyperion with the "Atmo" LED Type?
I try to use an Atmolight (see https://ca.rstenpresser.de/index.php/atmo-main.html) as a "LED". In another thread i was told that this should work. Because of the meanwhile misleading title of the old thread i created this new thread.I dont know how to configure Hyperion to get this to work. The wiki doesnt have infos about his.
Btw, my ssh-log looks like there are additional problems, dont it?
Codessh in: Okt 09 20:03:28 raspberrypi systemd[1]: Stopped Hyperion Systemd service. ssh in: Okt 09 20:03:28 raspberrypi systemd[1]: hyperion.service: Start request repeated too quickly. ssh in: Okt 09 20:03:28 raspberrypi systemd[1]: Failed to start Hyperion Systemd service. ssh in: Okt 09 20:03:28 raspberrypi systemd[1]: hyperion.service: Unit entered failed state. ssh in: Okt 09 20:03:28 raspberrypi systemd[1]: hyperion.service: Failed with result 'exit-code'.
-
Okay, some hours later.
I installed Hyperion and my windows pc can communicate with the rpi using hypercon.But - darkness reigns. No lights.
Today i dont have the grabber/converter, i get it tomorow i hope. I thought i could experiment with the atmolight anyway?
My setup atm:
Rpi USB => AtmolightBaud: tested 100.000 and some other - no effect
LED horizontal and l / r: 1 in every zone
Grabber: internal grabberi get the following error in SSH log:
ssh out: ERROR: ld.so: object 'bMマ}`゙ᆳj,bᅡ ̄?r(トCD+vラ}ᅡ' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
-
It looks like hyperion supports that device using serial/USB as the "atmo" device (not to be confused with the atmoorb)
could you go into detail what you mean? Or show me the way to a thread ... thanks.
-
Yes, i have many meters of non andressable LED.
I dont want the room behind the tv illuminated, a) because i read that the brightness is low. But more important, b) i want to illuminate the complete room: 1 Stripe left wall, 1 at the right wall, 1 above tv, 1 under. I am using this right now, but only for PC, which is not enough (using https://ca.rstenpresser.de/index.php/atmo-main.html). -
Hi,
i want to create a ambilight alternative, but not using an andressable LED strip but a normal one. I dont need 100 seperate LED-Colors, 4 channels would be enough for me (left right up down).
There are several projects on the market to do this, but only for USB/Windows. I want to use it for HDMI sources, using the usual converter/grabber-combination.Is there a project like this available? I cant find one.