DIY Ambilight – part 2

A while back I started with an Ambilight project based on a Raspberry PI and Hyperion. All the parts were delivered so I could finish the installation. The last part was to cut the LED strip into 5 pieces and solder them back together so they could be mounted on the TV.

The moment of truth… Failure! The last part of the strip (the last 7 LEDs) were all white so I thought something was wrong with the soldering. I removed the last part and tried again. Nothing! Now not one LED lit up…

So back to the shed… After a while and trying shorter pieces of LED strip I still didn’t have a working solution. The logging of the software (Hyperion) however looked ok. I saw the software start and also changes in the color of the LEDs was visible in the log. So I started to suspect the PI.

I installed Raspbian instead of Openelec to be able to use some troubleshooting tools. I used gpiotest (based on this article) and things didn’t look good:

It looked like I fried the gpio pins 🙁

One possible reason for this is that I accidentally put 5V on one of the used pins.  These are 3.3 volt logic pins. A voltage near 3.3 V is interpreted as a logic one while a voltage near zero volts is a logic zero. A GPIO pin should never be connected to a voltage source greater than 3.3V or less than 0V, as prompt damage to the chip may occur as the input pin substrate diodes conduct.

So I ordered a new PI and did the test again. This looked a lot better:

So I got a working PI again. Now I have to wait for a new LED strip 🙂

To be continued…

vRO – Import configuration – Exception occured. Could not extract ResultSet

While trying to import a vRealize Orchestrator configuration from one vRO appliance to another I received an error:

Not much information so I looked at some log files. There I got a bit more info on whats going on.

So it looked like the appliance ran out of memory. The first step I took was to increase the memory of the appliance itself. However I still bumped into a limit…

The flat line showed me that some process used al of the available memory. The next step was to increase the memory heap size inside the appliance. For this I followed this article: How to adjust the memory heap size for VMware vRealize Orchestrator (2138939)

Unfortunately it still didn’t work. The reason for this was that the import process doesn’t use the vco-server service but the vco-configurator service… So instead of editing the setenv.sh file for the server service I had to edit the same file for the configurator service. Edit the file setenv.sh  (/usr/lib/vco/configuration/bin) and search for this line:

Then increase the -Xmx value until the import is succesfull.