![\"Cylon](\"https:\/\/elephantandchicken.co.uk\/stuffandnonsense\/wp-content\/uploads\/2018\/12\/CylonEyes.png\")
<\/a>Cylon Eyes<\/p><\/div>\n
So far, I’ve had versions of the program (re-written for required variations in available libraries) running on the Orange Pi (Armbian), ESP8266 (Arduino IDE) and the Raspberry Pi (twice, because I lost the original version). This post covers the latter, using the current libraries discussed on the Adafruit website, which unfortunately seem to only work with Python 3.<\/p>\n
Required Equipment & Setup<\/h6>\n
For this tutorial, you will require the following :<\/p>\n
- \n
- A Raspberry Pi, cables and an SD card<\/li>\n
- A string of WS2812B LEDs – 8 is a good number<\/li>\n
- Appropriate wires to connect the LEDs to the Raspberry Pi GPIO header<\/li>\n<\/ul>\n
I’ve used the linked LEDs as they are convenient for testing<\/a>. You will need to solder wires, or a header to these – I usually lay a standard male header (4 pins) on the pads and solder it down as it is handy for prototyping. The male header lets me use female->female dupont wires to connect to a Raspberry Pi. Also note that some variations have the red and green wired backwards – this can be easily be fixed in software (I have included a boolean near the start of the code in pictureLED.py to enable the switch).<\/p>\n
The LEDs should be wired into the Raspberry Pi while it is powered down to reduce the chance of fatal mistakes (always rewire with a computer powered down as they are very<\/em> sensitive to electrical shocks and the GPIO pins are wired directly into the inner gubbins of the main chip). Wiring is as follows, where the red wire goes to +5v, the blue wire to data and the black wire to ground (there are two on the suggested LED part which is useful when using separate power supplies for the Raspberry Pi and the LEDs).<\/p>\n
![\"Raspberry](\"https:\/\/elephantandchicken.co.uk\/stuffandnonsense\/wp-content\/uploads\/2018\/12\/RasPiRGBWiring.png\")
<\/a>Raspberry Pi LED Wiring<\/p><\/div>\n
The WS2812B LEDs are only borderline able to be driven from 3.3v to the data pin (the Raspberry Pi does this). While this is true, with short wires I have never had an issue. I will detail how to use a MOSFET to increase the data signal voltage to 5v later.<\/p>\n
I will assume you have a clean install of Raspbian on the SD card in the Raspberry Pi. Before doing anything else, ensure you run the following command in a terminal :<\/p>\n
sudo apt-get update<\/p><\/blockquote>\n
This updates the database of software on the Raspberry Pi and ensures that you’re requesting the latest versions of programs.<\/p>\n
Next run the following commands in a terminal :<\/p>\n
sudo pip3 install rpi_ws281x<\/p>\n
sudo pip3 install adafruit-circuitpython-neopixel<\/p><\/blockquote>\n
The first time I ran these commands, I had an error for an unknown reason. I ran them again and everything installed properly.<\/p>\n
First Test<\/h6>\n
To make sure everything is working, enter the following program into your favourite text editor on your Raspberry Pi and save it as test.py in a new folder (creating a new folder in the current directory : mkdir <foldername>, switch into the new folder : cd <foldername>, editor suggestion : nano test.py).<\/p>\n
#!\/usr\/bin\/env python3\r\n# The line above tells the Raspberry Pi that we want to run this\r\n# script in Python 3 - so we don't have to tell it later\r\n\r\nimport board\r\nimport neopixel\r\nfrom time import sleep\r\n\r\n# An example program that cycles through Red, Green Blue and then stops\r\n\r\nLEDcount = 8\r\n\r\npixels = neopixel.NeoPixel(board.D18, LEDcount)\r\n\r\n#red\r\npixels.fill((100,0,0))\r\nsleep(1)\r\n#green\r\npixels.fill((0,100,0))\r\nsleep(1)\r\n#blue\r\npixels.fill((0,0,100))\r\nsleep(1)\r\n\r\n# and off\r\npixels.fill((0,0,0))\r\n<\/pre>\n
If you’re powering the LEDs from the Raspberry Pi, do not turn on too many. 8 is likely to already be too many as they use up to 60mA each (480mA for 8!). To limit power in these examples, I’m not using full brightness (full brightness would be 255 in the first test program), limiting the number of lit LEDs or am only using single colours at a time. For white light and full brightness on all LEDs – use an external power supply if you have more than one or two LEDs! Thanks to PJRC for actually doing some measurements<\/a>.<\/p>\n
Once entered and saved, from a terminal in the saved file’s directory, enter the following command to give the file permission to execute as a script :<\/p>\n
chmod +x test.py<\/p><\/blockquote>\n
“chmod” is the permissions modification command and I think of “+x” as meaning “plus executable”.<\/p>\n
We’re ready to run our test – with everything connected, run the following command in the terminal :<\/p>\n
sudo .\/test.py<\/p><\/blockquote>\n
If everything goes to play, you should see the connected LEDs cycle through red, green and then blue before turning off. If you see any errors, google is your friend. Also check that you ran the command while in the correct directory, and have permission to use the sudo command.<\/p>\n
Make a “Clear” Script<\/h6>\n
A useful script to make at this stage is a “clear” script. This means if you interrupt another script, or create a script that leaves LEDs on and you want to get rid of them, you can run this script to tidy them up.<\/p>\n
#!\/usr\/bin\/env python3\r\nimport board\r\nimport neopixel\r\nimport sys\r\n\r\n# assume a default 200 LEDs\r\nLEDcount = 200\r\n\r\n# handle parameter\r\nif len(sys.argv) == 2:\r\n # we have been passed a parameter - this should be the number of LEDs\r\n LEDcount = int(sys.argv[1])\r\n\r\npixels = neopixel.NeoPixel(board.D18, LEDcount)\r\n\r\npixels.fill((0,0,0))<\/pre>\n
As before, enter the program, save it with a name (clear.py for example) and then make it executable with chmod. This script can be used in two ways – if you note the “handle parameter” if statement, by using a parameter when running the script you can define how many LEDs you would like to clear. If no parameter is passed, the script assumes you have 200. Note that overestimating is not an issue and so 200 will clear any number up to 200. If you have 201 LEDs, the final LED will remain lit!<\/p>\n
To use the script you’ve just entered, type the following at the command line :<\/p>\n
sudo .\/clear.py<\/p><\/blockquote>\n
This will clear the first 200 LEDs. To clear a specific number of LEDs (for example, the first 4 of 8 LEDs or if you have 450 LEDs) :<\/p>\n
sudo .\/clear.py 4<\/p>\n
sudo .\/clear.py 450<\/p><\/blockquote>\n
Preparing an Image<\/h6>\n
Creating the Image we’ll be using to control the LEDs is fairly trivial if you are familiar with any painting programs. The more basic the painting software, the easier the creation! The only complication is making sure that you save in the correct file format (24bit bitmap “.bmp”). Note that I previously tested JPEGs, but found that the compression made black not equal 0,0,0 and so LEDs would be visibly lit when I didn’t want them to be.<\/p>\n
For demonstration, I will use GIMP to create my image, because it is free.<\/p>\n
- \n
- Launch GIMP and create a new image. Make it as wide in pixels as the number of LEDs you have connected (8 for me) and as tall as the number of frames you’d like (16 for me).\n
![\"New](\"https:\/\/elephantandchicken.co.uk\/stuffandnonsense\/wp-content\/uploads\/2018\/12\/NewImage.png\")
<\/a>New Image<\/p><\/div><\/li>\n
- Fill the drawing area with black (RGB 0,0,0).<\/li>\n
- Zoom in lots until you can see individual pixels and start painting. The pencil (individual pixel drawing tool) is probably best for this. In GIMP you need to change the pencil “brush” size to 1px.<\/li>\n
- Draw your picture.<\/li>\n
- Once done, to save in GIMP, select “Export As…” from the File menu.\n
![\"Export](\"https:\/\/elephantandchicken.co.uk\/stuffandnonsense\/wp-content\/uploads\/2018\/12\/ExportImage01.png\")
<\/a>Export Image<\/p><\/div><\/li>\n
- Name your file, pick a location, select “Windows BMP image” and click Export.\n
![\"Export](\"https:\/\/elephantandchicken.co.uk\/stuffandnonsense\/wp-content\/uploads\/2018\/12\/ExportImage02.png\")
<\/a>Export Options<\/p><\/div><\/li>\n
- Select “24 bits” under “Advanced Options” in the Export Image as BMP dialog box which appears.<\/li>\n<\/ol>\n
I have created the following example.bmp. Note the red graduated tint in the lower half (only between 0 and 80 out of 255 intensity, which will be significantly more pronounced on the LEDs). I have uploaded the actual file (the following image has been enlarged to make it visible) and it can be downloaded from here<\/a> (right click and select “Save link as…”).<\/p>\n
![\"Example\"](\"https:\/\/elephantandchicken.co.uk\/stuffandnonsense\/wp-content\/uploads\/2018\/12\/exampleBig.png\")
<\/a>Example<\/p><\/div>\n
If you have drawn your image on a computer other than your Raspberry Pi, you will want to transfer it. There are many ways of doing this, from USB drive, to email. I will be using a built in tool command line tool available on Linux and MacOS called “scp”.<\/p>\n
In this example, we are assuming that the image file is saved in a folder called “To Transfer” in your home folder on your desktop \/ laptop computer (aka “the source”), is called “example.bmp”, that the network name of your Raspberry Pi (aka “the destination”) is still the default “raspberrypi”, the username is the default “pi” and that you want to move it to a folder in the Raspberry Pi home directory called “RGBLED”.<\/p>\n
If you haven’t consciously changed the network name from “raspberrypi”, it will still be this – if you have, use the new name instead. You can see the network name in the command prompt on the Raspberry Pi if I remember correctly, it is the bit after the “@” symbol).<\/em><\/p>\n
To move the file from the source to the destination, enter the following command on the source computer :<\/p>\n
scp ~\/To\\ Transfer\/example.bmp pi@raspberrypi.local:~\/RGBLED\/<\/p><\/blockquote>\n
You will be asked for your Raspberry Pi password (the destination, not the source) and you should almost instantly see the file as 100% sent and the source returns to the standard command prompt. If there is an error, make sure that the source and destination are on the same network, the file paths are correct at both ends, the password is correct and that you haven’t made any typos. If you still have issues, there are websites available that will take you through the process more carefully if you search for “transferring files to a Raspberry Pi using scp”.<\/p>\n
In later examples, I will assume that the file “example.bmp” is located in the ~\/RGBLED\/ (also known as \/home\/pi\/RGBLED\/) folder on the Raspberry Pi.<\/p>\n
The pictureLED.py Script<\/h6>\n
The main python script which converts an image into a sequence of LED based patterns is as follows, or can be downloaded directly from here<\/a> (right click and select “Save link as…”). I recommend placing it in the same “~\/RGBLED\/” folder on the Raspberry Pi.<\/p>\n
#!\/usr\/bin\/env python3\r\n\r\n#******************\r\n#* pictureLED.py - convert bmp image into LED sequence Code\r\n#* https:\/\/elephantandchicken.co.uk\/stuffandnonsense\r\n#* Circuit :\r\n#* Connect LED ground to both the Raspberry Pi ground and the LED power supply's ground\r\n#* Connect LED data to pin D18 (if not boosting with MOSFET)\r\n#* Connect LED +V to the LED power supply 5V\r\n#* Do not mix 5V and 3.3V!\r\n#* If in doubt, details of the circuit and software for controlling from linux\r\n#* are on my website\r\n#*******************\r\n\r\nimport sys\r\nimport board\r\nimport neopixel\r\nfrom PIL import Image\r\n\r\nfrom time import sleep\r\n\r\n# Edit the following line if red and green are backwards\r\nswitchColours = false\r\n\r\ndef fixColour(colour, scale):\r\n # correct the colour order for my ws2812 LEDs and scale the brightness\r\n # correct colour by switching [0], [1] and [2]\r\n theResult = (int(scale*colour[0]\/100),int(scale*colour[1]\/100),int(scale*colour[2]\/100))\r\n if switchColours:\r\n theResult = (int(scale*colour[1]\/100),int(scale*colour[0]\/100),int(scale*colour[2]\/100))\r\n return theResult\r\n\r\nif len(sys.argv) == 1:\r\n print(\"You've not provided any details! Command format is <required> [option] : sudo pictureLED.py <image.bmp> [fps] [loop? 1\/0] [loopdelay] [brightness percent] [pin]\")\r\n quit()\r\nif len(sys.argv) > 1:\r\n # identify image file - use defaults for all other parameters\r\n imgfile = sys.argv[1]\r\n fps = 15.0\r\n maxIntensity = 100\r\n pin = 18\r\n loopimg = True\r\n loopDelay = 0\r\nif len(sys.argv) > 2:\r\n # set the fps\r\n fps = float(sys.argv[2])\r\nif len(sys.argv) > 3:\r\n # loop?\r\n if sys.argv[3] == \"1\":\r\n loopimg = True\r\n else:\r\n loopimg = False\r\nif len(sys.argv) > 4:\r\n # loop delay (at the end of each cycle)\r\n loopDelay = float(sys.argv[4])\r\nif len(sys.argv) > 5:\r\n # set a maximum LED intensity and scale all values\r\n maxIntensity = int(sys.argv[5])\r\nif len(sys.argv) > 6:\r\n # parameter 5 - set pin for neopixel data\r\n pin = sys.argv[6]\r\nim = Image.open(imgfile)\r\npix = im.load()\r\npixw = im.size[0]\r\npixh = im.size[1]\r\nprint(\"Image size = \",im.size)\r\nPIXEL_NUM = pixw\r\n\r\nif pin==18:\r\n pinName = board.D18\r\n # add other options here\r\nelse:\r\n pinName = board.D18\r\n\r\npixels = neopixel.NeoPixel(pinName, PIXEL_NUM, auto_write=False) # pin, number of LEDs\r\n\r\nstat = True\r\n\r\nwhile(stat):\r\n for y in range(0, pixh):\r\n for x in range(0, pixw):\r\n pixels[x] = fixColor([pix[x,y][1],pix[x,y][0],pix[x,y][2]],maxIntensity)\r\n pixels.show()\r\n sleep(1\/(fps))\r\n sleep(loopDelay)\r\n stat = loopimg\r\npixels.fill((0,0,0))\r\npixels.show()<\/pre>\n
The program is not actually that large, with the majority of it being a clumsy decoding of the various parameters sent by the user when they execute the command. For a fixed application, much of this could be removed to produce something like the following (untested) code :<\/p>\n
#!\/usr\/bin\/env python3\r\n\r\n#******************\r\n#* fixedPictureLED.py - convert bmp image into LED sequence Code\r\n#* https:\/\/elephantandchicken.co.uk\/stuffandnonsense\r\n#* Circuit :\r\n#* Connect LED ground to both the Raspberry Pi ground and the LED power supply's ground\r\n#* Connect LED data to pin D18 (if not boosting with MOSFET)\r\n#* Connect LED +V to the LED power supply 5V\r\n#* Do not mix 5V and 3.3V!\r\n#* If in doubt, details of the circuit and software for controlling from linux\r\n#* are on my website\r\n#*******************\r\n\r\nimport sys\r\nimport board\r\nimport neopixel\r\nfrom PIL import Image\r\n\r\nfrom time import sleep\r\n\r\n#################\r\n# Define the image path here!\r\nimgfile = \"\/path\/to\/the\/image.bmp\"\r\n#################\r\n\r\n# Other parameters :\r\nfps = 15.0\r\nmaxIntensity = 100\r\npin = 18\r\nloopimg = True\r\nloopDelay = 0\r\nswitchColours = false\r\n\r\ndef fixColour(colour, scale):\r\n # correct the colour order for my ws2812 LEDs and scale the brightness\r\n # correct colour by switching [0], [1] and [2]\r\n theResult = (int(scale*colour[0]\/100),int(scale*colour[1]\/100),int(scale*colour[2]\/100)) \r\n if switchColours:\r\n theResult = (int(scale*colour[0]\/100),int(scale*colour[1]\/100),int(scale*colour[2]\/100)) \r\n return theResult\r\n\r\nim = Image.open(imgfile)\r\npix = im.load()\r\npixw = im.size[0]\r\npixh = im.size[1]\r\nprint(\"Image size = \",im.size)\r\nPIXEL_NUM = pixw\r\n\r\nif pin==18:\r\n pinName = board.D18\r\n # add other options here\r\nelse:\r\n pinName = board.D18\r\n\r\npixels = neopixel.NeoPixel(pinName, PIXEL_NUM, auto_write=False) # pin, number of LEDs\r\n\r\nstat = True\r\n\r\nwhile(stat):\r\n for y in range(0, pixh):\r\n for x in range(0, pixw):\r\n pixels[x] = fixColor([pix[x,y][1],pix[x,y][0],pix[x,y][2]],maxIntensity)\r\n pixels.show()\r\n sleep(1\/(fps))\r\n sleep(loopDelay)\r\n stat = loopimg\r\npixels.fill((0,0,0))\r\npixels.show()<\/pre>\n
Note the “auto_write=False” parameter passed when generating the “pixels” object. This changes the library’s behaviour so that it only sends updates to the LEDs once the function “pixels.show()” is called.<\/p>\n
As before, once you have pictureLED.py saved (pictureLED.py specifically as fixedPictureLED.py is just an example application) on the Raspberry Pi, run the chmod command to allow the file to be executed.<\/p>\n
Running the pictureLED.py Script<\/h6>\n
To run pictureLED.py, open a terminal with the current directory matching the location of both pictureLED.py and example.bmp. The command format is as follows :<\/p>\n
sudo .\/pictureLED.py <filename.bmp> [fps] [loop? 1\/0] [loopdelay] [brightness percent] [pin]<\/p><\/blockquote>\n
Parameters between “<>” are required and parameters between “[]” are optional, although all preceding optional parameters are required. These are two example commands :<\/p>\n
sudo .\/pictureLED.py example.bmp<\/p>\n
sudo .\/pictureLED.py example.bmp 2 0 0 50<\/p><\/blockquote>\n
The first example uses all default settings (15 fps, loop, zero second loop delay (time before the pattern repeats), 0% brightness reduction and the default pin) on the image “example.bmp”. The pattern will repeat indefinitely – to stop it, press Ctrl-c.<\/p>\n
The second example passes a number of parameters, more specifically describing how we want the program to run. In this example, we run at 2 fps, not looping, zero second loop delay, at 50% of full brightness. Note we do not specify the pin – this is because pin D18 is currently the only available pin in my code.<\/p>\n
Running at Boot<\/h6>\n
A simple way to make your LED sequence run when the Raspberry Pi powers on (note, powers on, not when you log in) is to edit the operating system file “\/etc\/rc.local”. Absolute care should be taken, as if you make a mistake, the Raspberry Pi will not finish booting. Assuming that the absolute path (from the root level of the disk, not from the Home (aka “~”) folder) for pictureLED.py is “\/home\/pi\/RGBLED\/pictureLED.py”, enter the following command in a terminal :<\/p>\n
sudo nano \/etc\/rc.local<\/p><\/blockquote>\n
A file will open in the text editor nano. Use the arrow keys to scroll to the bottom of the file. The last line should be “exit 0”. Above<\/strong> this <\/strong>enter the following new text :<\/p>\n
\/home\/pi\/RGBLED\/pictureLED.py \/home\/pi\/RGBLED\/example.bmp 2 &<\/p><\/blockquote>\n
There are a number of things to note here.<\/p>\n
- \n
- All paths have to be absolute as this means that they are always correct, no matter where the current directory is when the script executes.<\/li>\n
- “sudo” is not needed because the parent script is already executing with root permissions.<\/li>\n
- As shown it is best (don’t not do it<\/strong>) to include a ” &” (that is a space followed by an ampersand). This tells the computer to run the script as a background process and means that if your script throws and error, or stops to wait for user input, the computer does not hang but keeps booting. It also means that the computer doesn’t wait for your script to finish before continuing (imagine we used the default “loop” option).<\/li>\n<\/ul>\n
External Power Supply<\/h6>\n
To drive more LEDs at full brightness, connect the LEDs to an external 5v power supply, remembering to connect the ground between both the LED power supply and the Raspberry Pi (not doing so can damage the Raspberry Pi or LEDs as connecting the grounds holds both devices to the same reference point and avoids the voltages floating between the two supplies, potentially causing high voltages where there shouldn’t be). The following shows a suggested wiring :<\/p>\n
![\"External](\"https:\/\/elephantandchicken.co.uk\/stuffandnonsense\/wp-content\/uploads\/2018\/12\/RasPiRGBExternalWiring.png\")
<\/a>External Power LED Wiring<\/p><\/div>\n
Do not connect the 5V to the Raspberry Pi (unless you know what you are doing, and it is the only<\/strong> power supply to the Raspberry Pi (i.e. there is no micro USB connected)).<\/p>\n
Remember that each LED could draw up to 60mA and ensure that your selected LED power supply is able to provide sufficient current to power all of your LEDs. Given that the supply is at 5v, this means you are looking for 5×0.06 = 0.3 watts per LED. For example, if you had 100 LEDs, you would need a power supply rated to at least 30 watts at 5v.<\/p>\n
5v Data Signal<\/h6>\n
Another potential issue which has not impacted me, is due to the Raspberry Pi sending data to the LEDs at 3.3v. I believe that the minimum voltage required by the LEDs when running at 5v is 3v and 3.3v does not give much overhead. This is likely to result in issues when longer wires result in a further reduction in voltage, potentially causing intermittent issues or complete failure to operate.<\/p>\n
This can be solved by voltage shifting the Raspberry Pi output using a MOSFET. The following method is actually a way of getting bi-directional level shifting (very useful for I2C), but is simple enough that we might as well use it here. I’ve based the circuit on the one here : http:\/\/www.hobbytronics.co.uk\/mosfet-voltage-level-converter<\/a>, please double check that my implementation is correct! Note the strip board could be smaller in reality (you could manage a 4×3!), but I couldn’t get Fritzing to show stood up resistors.<\/p>\n
- Launch GIMP and create a new image. Make it as wide in pixels as the number of LEDs you have connected (8 for me) and as tall as the number of frames you’d like (16 for me).\n