Skip navigation
1 2 3 4 5 Previous Next

Raspberry Pi

372 posts


At Embedded World 2017 I saw something that initially made me very confused. It was a rugged piece of hardware that clearly looked like it was related to the Raspberry Pi in some way but upon opening it up I couldn’t see how a Pi would fit inside. The internal connector looked interesting because it had pins instead of a socket, so how could a Pi 3 plug on top of it? And it had many Ethernet and USB ports already fitted. It took someone to explain it to me. This was actually a complete new custom design that had the Raspberry Pi 3 already inside it!


The company, Hilsher, has worked with the Raspberry Pi 3 manufacturers in order to create an entirely new variant of the Raspberry Pi 3. After seeing and learning about it I really want one. It is the best Pi variant yet, ruggedized, with a decent power connector, expandable, and capable of operating in all typical Raspberry Pi usage scenarios and more as will be described. It is not currently available, but will be available soon.



What do Hilscher do?

The key to understanding the netPI is to examine the motivation for the product. Hilscher is a 30-year old company (originally established in Germany but now they are a global business) deeply involved in Real-Time Ethernet (also known as Industrial Ethernet). This technology (actually, a range of technologies – there are several standards) has become the dominant way of building automation within factories. Every time you see a robotic assembly line building a car, there will be a controller somewhere talking to many sensor devices and output devices, and all the communication between controller and such node devices is occurring over the Real-Time Ethernet connections.



Real-Time Ethernet takes traditional Ethernet but transports some protocols over it that can be deterministic. This means that message loss is not tolerated like in a non-industrial network. In a normal non-industrial network there is no guarantee that a packet will not be lost. It is up to the higher-layer protocol to re-send the packet if needed. Transmission Control Protocol (TCP/IP) is used to relieve the application layer (user applications) from the burden of reassembling packets of data and requesting retransmissions but these would cause delays that would be unacceptable in an industrial assembly line. To take one example, known as PROFINET IO, Real-Time Ethernet solves this typically by defining a type of ‘upper-class railway carriage’ type of scheme where there is a regular train time and the upper-class carriage portion of the train is never allowed to fill up with non-priority packets. Only the deterministic packets are sent in that carriage.



There can be different levels of determinism such as strict (which requires packets to arrive within a certain time) or soft determinism which doesn’t mind if the packet takes a little longer sometimes to arrive (but it must arrive and must not be dropped) depending on the particular type of Real-Time Ethernet that is being used. There are also techniques to ensure that packets do not sit for very long in a buffer. A normal (non-industrial) Ethernet interface will collect up the packet before it is announced to the application. With Industrial Ethernet it is possible to start serving the packet to the application (the sensor or output node software) as it arrives on the wire. This type of functionality is only possible with special hardware. A normal Ethernet interface does not have this capability.


Hilscher is a company which has developed custom chips to perform Real-Time Ethernet capability and embedded them into different products such as:

  • Modules or Interface boards that can connect a computer (say using PCI-E) to the Real-Time Ethernet bus to perform controller or node operations depending on the specific use-case
  • Interface PCBs that can connect embedded hardware (say using dual-port memory) to the  Real-Time Ethernet bus
  • Gateways that can perform Real-Time Ethernet operations and interwork them to traditional Ethernet and TCP/IP for sending over the network for server based applications to monitor or control or manage using protocols that function well over IP networks or the Internet, such as MQTT
  • Test tools for diagnosing Real-Time Ethernet


In essence, the Hilscher products act like a bridge between the Industrial Ethernet world and any other hardware or software, either locally or over networks.


A while ago Hilscher launched a little PCB that could connect to the Raspberry Pi using the 40-pin connector on it. The PCB had Hilscher’s secret-sauce Real-Time Ethernet chip on it, a couple of Ethernet sockets (some Real-Time Ethernet technologies use both ports) and talked to the Pi using the serial peripheral interface (SPI) that allows applications running on top of Linux on the Pi to interwork with Real-Time Ethernet. This product allows for possibly the cheapest way for anyone to experience Real-Time Ethernet. It would even be possible to use several Pi’s and build up a controller and nodes and simulate a factory basically.



Having a high performance ARM chip opens up a lot of possibilities. Hilscher decided to take the leap and build a custom product that would use the heart of the Raspberry Pi but in a ruggedized industrial form-factor. For the software stack, Raspbian wouldn’t do; a hardened Linux kernel is needed for reliability and security. However to maintain ease-of-use Hilscher did a clever thing and provided Raspbian in a ‘software container’ so that software programmers still get the same Raspbian experience if this is desired, but in a protected container. This will be examined further below in a bit more detail.



The end result is a product that can be used and programmed the same as any normal Raspberry Pi in any preferred language of choice, and has applicability for a range of functions in industrial automation. The possibilities are immense. It could be used as a gateway, or a controller, or it could be used to attach additional custom sensors or actuators. It just depends on the software, and whatever users decide to attach to the netPI’s hardware interfaces.


Check out the discussion with Hilscher at Embedded World 2017 here:


Hardware Overview

The netPI has a single circuit board which contains Raspberry Pi 3 functionality including wireless and Bluetooth and video connections. It has the same 40-way connector inside so all the usual Pi accessory boards can be fitted inside the enclosure. The USB connectors are spread out, it has a total of 4.


It has the default Ethernet interface but also an extra two Ethernet interfaces built-in; these are intended for connecting to the industrial network. There is also a built-in real-time clock with power back-up.



What is very cool is that there is an expansion connector slot with blanking plate on the side and it allows for modules to be inserted and removed. These could be additional Ethernet interfaces or other future functionality.


The interface is based on a mini-PCIe connector but the connections carry general-purpose input/output (GPIO) and serial bus signals such as I2C and SPI. The details of the expansion interface will be opened up so it will be possible to design custom hardware to fit into the slot.


Industrial customers could benefit from the netPI even if they do not use it for real-time Ethernet, since it would be possible to design sensors or control circuitry to fit into the expansion module slot. A module that supports thermocouple probes could be a nice example.


Overall the hardware design is very nice. The radio antenna has been designed for good coverage by extending it beyond the metal chassis (a non-conductive shell to enclose the antenna is not shown in the photo). I also liked the easy-to-see LEDs, the space to install additional functions (even though the netPI is still very compact) and the wider-range power supply input with a more usable connector than micro USB.



Software Overview

The nice design extends beyond the hardware too. In order to provide something secure and reliable while remaining easy-to-use, Hilscher have taken the effort to produce a software image which uses a hardened Linux kernel (based on the Yocto project) at its core. On top of that a container technology is run (Docker). This is kind-of similar to virtualization but can be more efficient in terms of resource usage. Docker is one of the open-source success stories that is extremely valuable and worth experimenting with.



The end result is that it is possible to run Raspbian in a container, and upgrade it (and any applications) as required, remotely. The benefit of this is that software developers can make use of all the familiarity they already have with Raspbian (and can even develop apps on a traditional Pi 3 before deploying to the netPI). Furthermore there is reduced risk of software clashes; it is possible to add additional containers for all your new applications, each running on a separate Raspbian if desired. The container technology allows for safe upgrades because one can always fall back to an earlier container if a new one has any issues.


Hilscher supply a ready-made Raspbian container that already has technologies like Node-RED and all the drivers to support Real-Time Ethernet built-in. People can directly use that, or modify it by adding their own applications to create a new container and then deploy it remotely to as many netPI’s as desired.



I was impressed with the level of detailed attention paid to the product design and the software implementation to make it easy for developers and for deployment. I hope to see and experiment with more Hilsher technology in future, I like that they have found ways to make Real-Time Ethernet accessible for all.

Go Go Gadget Raspberry Pi Zero W


                    Happy Birthday from Raspberry Pi Foundation!!!

     March 7 was Raspberry Pi’s fifth birthday: it has been five years since we launched the original Raspberry Pi, selling a hundred thousand units in the first day, and setting us on the road to a lifetime total (so far) of over twelve million units. To celebrate, we’re announcing a new product: meet Raspberry Pi Zero W, a new variant of Raspberry Pi Zero with wireless LAN and Bluetooth, priced at only $10.



20170314_115745 Pi Zero W.jpg


     With this announcement, I was excited to see this as an important upgrade. Finally a way to use the Zero W with WiFi from Cypress using the CYW43438 wireless chip just like the older brother the Raspberry Pi 3. The only problem was how to get one when they sell like hotcakes.Then I got my chance when on Saturday Micro Center announced stock of Zero W as 923029. So bright and early Sunday morning I went down there to get me one. Talking to the sales rep, I found they dropped shipped 200 to this store which was not their normal shipment. And yes they were going fast. BTW, the second one cost 14.99 which is still not bad.

     In addition today is Pi day! Not Raspberry Pi but that other famous Pi 3.14 etc. What more reason to read this little(ish) tutorial. I am sorry for the many steps, but I wanted a complete setup for noobs and experienced users alike. So lets get on with it.


                                        457746_925313_01_front_thumbnail.jpg?1488940459712                457746_925313_02_front_thumbnail.jpg

    The Dilemma


So I get home and start looking at the new small board and ponder how to setup this wonder without a keyboard, mouse, and HDMI monitor. Yes, I could use them and be done, but that is not the way most people would try it. Even though wireless should work, how was the configuration of wireless to get started without keyboard and monitor.

After Googling the net, I came up with an idea! The good folks at Adafruit had this article This seemed the way to go thinking of the choices. But it was not without trials and tribulations. The serial USB seems to be the simplest until I found no logon till the TTY was setup first. A chicken and an egg problem to be sure. So without further ado, here we go.


     Ready Set ...


  1. Find the latest Jessie Rasbian Lite at and download it. I chose this because it can work on a small SD card of 4 GB and does not have a graphical interface to run. This means I load only what I need. For reference I used 3/2/2017 version

  2. Next I mounted the micro SD card on a USB interface on Windows computer. I chose a  need tool called Etcher at, It is smart and simple to use. Also you can flash more than one card at a time. It will verify the image as well.

  3. Even though the tool does an "Eject" on the card for you, remove and reinsert the same card since we have a few hings to do.

  4. Look for boot (E:) on Windows. For Linux or Mac, this would be the first partition FAT32. Later it is mounted at /boot in the tree. Edit config(.txt) file with either Notepad or Wordpad. If you use Wordpad, you must be careful to save as TXT and not anything else. Firstly, save a backup copy as config2.txt to be safe. Now add the following line as the last line in file:



    Now we can do a save as config.txt and reply Yes to overlay it.

  5. Next we edit cmdline.txt same as above. Again save a backup as cmdline2.txt. Now add the following after "rootwait" with just a space before and after. Do not hit the enter key since this file is very particular.


  6. One last edit, edit config.txt in Notepad. Do a save as and in the bottom the name is "ssh." include the period but not the quotes. Make sure all files are selected not just plain text. Then hit the save button. You should see this as a file not a text file. This will allow ssh the first time.

  7. Now properly Eject the card to use in the new Pi Zero W.

  8. Put micro SD card into Pi Zero W. Plug a micro USB into the inside called USB not PWR. I plugged this other end into a Pi 3. Why not Windows? Because of missing RDNIS driver for Windows 10 and Bonjour for Windows 10. For Windows, go to Directory: /static/beaglebone/latest/Drivers/. Select the correct version for Windows checking for 64 bit or not. Follow install procedures. Next go to, and select "Download Bonjour Print Services for Windows Vx.x.x'. Again follow install and now Windows can handle name resolution as well as RNDIS USB driver.

  9. On the Pi 3 they have both included in a full Jessie Rasbian desktop. Later I will locate and add when I find the drivers.

  10. Under the Pi 3, I opened a terminal window. Here I entered:



    Look for                    ID 0525:a4a2 Netchip Technology. Inc Linux-USB Ethernet/RNDIS Gadget

  11. Now we can SSH into the Zero W with: See note 1 below for more information.


    ssh pi@raspberrypi.local
  12. Reply Yes to next message to add ECDSA key and next the default password of "raspberry" (no quotes of course)

  13. Enter config file to change password and optionally host name. Also turn on SSH for future use.


    sudo raspi-config
    Interfacing Options
    P2 SSH
    <NO> to reboot now option
  14. Now to setup wireless settings with your SSID and PSK after any lines already there, paste and change the correct values:


    sudo nano /etc/wpa_supplicant/wpa_supplicant.conf
  15. Edit the interfaces file to fix up a static USB0 so logins can be done by IP address: Skip this as it did not work as intended/


    sudo nano /etc/network/interfaces
    allow-hotplug usb0
    iface usb0 inet static
  16. Now reboot the Zero W with:


    sudo reboot
  17. Wait a while and try to re-login. Note any changes to the host name will affect the xxx.local name or just use the static IP of



  18. Try a ping test like:


  19. After all this bask in the sunlight and enjoy a cup of Java. Oh that is another topic. Adios amigos.

Raspberry Pi have (today) launched the new Raspberry Pi Zero Wireless.



For more information on the Raspberry Pi Zero range, including where to buy the new Raspberry Pi Zero Wireless please visit the Raspberry Pi Foundation website at


Happy 5th Birthday Raspberry Pi!

Hello Again,

As i said in others post of mine i am working on a house automation system based on raspberry pi and arduino ... I ve moved a lot with this.. I also writing a program for this. I wrote the program in Visual basic has over 1000 lines of code cause it is also like JARVIS from ironman... It can execute a dissent amount of pre installed commands. I also added a feture when the doorbell ring a window pop up in my screen and it show me who is in the front door with face recognition.... I now want to move to the "next level" and make it work also on my there any way to make it synchronise in real time pc software and Android? For example if i dim the lights in one room to see the changed value on my phone and reverse or monitor the temperatures(data comes from arduino to pc software)

One idea that i had is to setup a local server. Or website on the arduino and share the data with pc and android. But i don't know if this is gonna be okay.

So... Any thoughts?

Thanks a lot nicolaoscon96

Almost everyone has heard of RetroPie.



The open source software which has enabled a bunch of Ikea tables with embedded Raspberry Pi.


Unfortunately, they've recently learnt a bitter lesson in trademarks, that unless you get there first, someone else can pull the rug out from under your feet, as the makers behind RetroPie call out for legal help.



Amazingly, someone from India has setup a website selling Raspberry Pi's with the software on the SDCards, something which is already against the license of RetroPie.



Furthermore, they're practically claiming RetroPie as their own, as they have filed a trademark in America (yes, even though they're from India) to lay claim to 'RetroPie' and 'Emulation Station'.



Allegedly the person behind this trademark registration has come out with his side of events and reasoning why they've done this:




So perhaps a word of warning, even if you're creating something open source, even if you're giving it out there and believe the GPL and licensing protect you, ultimately you cannot stop someone unless you've put measures in place to protect it first, and you're able to chase after them with the money necessary to hire lawyers/solicitors. A sour lesson, all the same.

A few months back, I enrolled for a design contest at . Needless to say its one of those contest where hundreds(500) of people join but every few complete. Anyway I did my part and here are a few tit-bits I gathered.


The implementation

I initially though about adding a massive array of features but then remembered that it was a contest sponsored by Cypress. Instead I worked on one part and ended up getting stuck in a loop. I started with the Texas Instruments MSP430 and finally settled on using a RPi 2 instead. The idea took me a month to finalize and 4 days to implement! That was so stupid I though BUT the fact it a lot of the times this happened. I spend an additional week trying to learn PSOC creator and made a small video.


I also did a lot of goofing around and have the footage to prove it. Its still needs a bit of editing but I will post it




when I am done Here are a few pictures




Im pretty OK with the result as everything is clean (thats a first!) and work.


Putting together the enclosure was a tough decision as I did not want to go with the boring box design but due to personal blunders, I had to cave.


Here is a time lapse that was the result of the Cel Robox.





Here is why I am actually writing this blog. I need feedback. Feedback on what is right and what is wrong. Why this is important is ...


(Content to be filled in after collection of feedback)


So what do I solicit feedback on? Here it is...


and this little video I mocked up considering advice from Workshopshed sir, jancumps sir fvan sir


So the question is... "what do you guys think?"

"what is the first thing that comes to you mind when you see this content?"

"Why am I hungry"... OK forget that one.


Thanks in advance.

Live long and prosper.

Not even a near record breaking heatwave can stop BitScope Blade hosted Raspberry Pi servers as we discovered by accident when our trusty old Dells came to an ignominious end but the 32 BitScope Blade Raspberry Pi in the same overheating room survived without skipping a beat!


We had an unexpected demonstration of just how robust Raspberry Pi is as a compute platform this week. If you live downunder where our R&D headquarters are, you will know it's been very hot for quite a while. It just seems like it will never end.


Recently the mercury topped 40℃ (or about 104℉ for our North American friends) here in Sydney. We know it's hard to imagine from the Northern hemisphere right now but if the airconditioning fails it's quite intolerable, and not just for humans.


Unfortunately, that's just what happened over the weekend just past in our lab and inside it got very hot.


File Server Meltdown


We run a range of computers and some them are servers that run 24x7. Or they're supposed to! Two of them are Dell PowerEdge Blade Servers which have been with us for quite a few years, as you can see.


One of them is our office file server and the other is our R&D file server. Both of them are quite important to us.


Unfortunately, the airconditioning failure was just a little bit too much and the R&D server overheated and failed, taking all the data with it, despite our efforts at recovery. The other one also died but (fortunately for us) we managed to relocate the hard disk to another computer and recover the data. Now before you laugh at us for not backing up, we do, and we were able to recover most of the data that would have been lost, but the stuff we'd been working on most recently was, unfortunately, lost.


Raspberry Pi Servers


Meanwhile, on the wall opposite, and in the same overheating conditions, was the pair of Raspberry Pi 2 we threw together up as our redundant office DNS/DHCP server. This little server had been running for 6 months when we wrote about them just after the Raspberry Pi 3 launch last year.


They have been running flawlessly since then with no more than a few reboots to upgrade them the entire time. At the time, we added the small hard disk drive with the intention of migrating our file server across to them too, but we never got around to it. Such a shame!


BitScope Blade Duo and Raspberry Pi.


We run about 32 Raspberry Pi in Blade Racks and wall mounted Blade Servers 24x7 in the same office.


Not one of them failed !


We should have moved our office and R&D file servers across already.


We're going to now!


As we wrote a few days ago, we reckon Blade DuoBlade Duo and pair of Raspberry Pi and WDLabs' PiDrive is perfect combination for replacing our old servers.


We'll write up what we've done when it's all up and running. There's nothing like a little dogfooding to prove a product idea. In fact, we have a quite a few applications in development together with the software to implement them. We'll post details soon and we'll add our new file server to the list. The fact that we've run our office DNS and DHCP and more recently a pair of WiFi AP from one Blade Duo and pair of Raspberry Pi 3 without a single hitch is testament to the reliability of Raspberry Pi when powered by BitScope Blade. They consume a fraction of the power of x86 based servers, are very low cost, and if last weekend proves anything, they don't need airconditioning or special cooling set ups to work reliably.


Post reprinted with permission from the BitScope Blog.

Following the recent launch of BitScope Blade and the case studies about the weather station in Nepal and the interactive Theremin exhibit at MAAS we received a lot of questions about which Blade is best for what purpose. Read on to learn why Blade comes in three editions and how you can best make use of them.


BitScope Blade Reloaded is our computing infrastructure platform for Raspberry Pi.


It is available in three editions; UnoUno, DuoDuo and QuattroQuattro which power and mount one, two or four Raspberry Pi and support the use of Raspberry Pi and BitScope accessories including HATs, displays, cameras and other devices. Blades may be used stand-alone or combined to build large computing platforms.


In this post we'll focus on some stand-alone examples.


GF10G blade uno hat example

So what does Blade do ?

BitScope Blade solves the “power and mounting problem” using Raspberry Pi.

A common problem when using single board computers like Raspberry Pi is how to power it reliably. The other common issue is how to mount it robustly.

These problems become more challenging when peripherals and expansion hardware such as HATs and USB are used and/or when using more than one Raspberry Pi at once.

BitScope Blade solves these problems making it easy to build small stand-alone servers, routers and workstations up to full sized compute clusters, private clouds, industrial IoT, edge and fog computing platforms, industrial data acquisition and control systems. HATs and almost any other peripheral compatible with Raspberry Pi may be used with BitScope Blade.

Blade Uno, the ideal "motherboard" for Raspberry Pi & HAT

The simplest Blade application is a motherboard for Raspberry Pi, a HAT and optionally one or more USB devices.

GF10G uno application example

For example, this BitScope Blade UnoBitScope Blade Uno is configured with Raspberry PiRaspberry Pi, Pimoroni Explorer HAT and BitScope MicroBitScope Micro to build a complete self-contained mixed signal test and measurement system.


Blade Uno provides power and mounts the Raspberry Pi, the HAT and BitScope. It accepts any source of power from 9V to 48V (so long as it’s 10W or more) with power connected via the 2.1mm socket or via the Blade tabs.


Additional accessories such as Raspberry Pi Display and one HUB Expansion Card or other SPI, I2C Serial or GPIO connected devices can also be used. The entire assembly can be mounted via the Blade's M3 mounting tabs or simply sat on a flat surface using the stand-offs.


The Raspberry Pi network port is available for network connections and/or a monitor (via HDMI), keyboard and mouse (via USB) and audio (via the 3.5mm). Full access to all the Raspberry Pi I/O is avaiable via the Explorer HAT. A "hat tip" to Pimoroni for the exceptionally handy Explorer HAT! We use this setup to help teach new users about logic protocols with BitScope Logic for BitScope Micro


Blade Duo, the ideal platform for tiny redundant "micro-servers".

For example, this Blade Duo mounts a pair of Raspberry Pi 3 and WDLabs’ PiDrive mounted on the back.

GF10G duo application example

The PiDrive is perfect for this (see our earlier post about building servers with Raspberry Pi). The PiDrive is powered via a Raspberry Pi and Blade Duo ensures there is plenty of power to drive it.


Blade Duo has the same HUB Expansion and I/O as Blade Uno and it offers auxiliary power connectors for external devices underneath each Raspberry Pi.


Using the Raspberry Pi 3 built-in WiFi the pair of Raspberry Pi can be networked to each other and/or a connected network switch or WiFi access point to configure them as a pair of servers or a router and server pair. The range of applications is huge, essentially anything you can think of using a pair of Raspberry Pi, e.g. UTM gateways, WiFi access points, VPN IPSec routers etc.


Blade Quattro, the industrial cluster platform for Raspberry Pi

A more sophisticated application for BitScope Blade, using Quattro, is a four node compute cluster.

GF10G quattro application example

Blade Quattro extends Blade Duo to power and mount up to four Raspberry Pi. Compute cluster applications such as a small private clouds, a build or render farms, web CMS any many other multi- node applications compatible with Raspberry Pi can be used.


Multiple Blades (of any edition) can be used to build very large compute clusters and a range of rack mount solutions are available to enable to physical construction, commissioning and deployment of large cluster computing systems of up to hundreds of nodes. For one excellent example of a small cluster built with Blade Quattro, check out Andy Clark's recent series about his Blender Render Farm.


In future posts we'll describe cluster computing examples ranging from 2 nodes to 200 that can be built with BitScope Blade Quattro, Duo and Uno. We'll also publish details of some software solutions such as Docker and explain some of our own tools designed to make Raspberry Pi programming and cluster management with Blade easy.


We designed BitScope Blade to unlock the huge potential of Raspberry Pi for use in industrial applications because nothing beats Raspberry Pi on price/performance, availability and viable software solutions.


We look forward to seeing what applications you decide to build with Blade!


There's more information across the element14 Community about Blade.


Post reprinted with permission from the BitScope Blog.



I want to introduce a new small project of me. It's a OLED display shield for Arduino and Raspberry Pi. The shield includes 3 buttons and leds to realize simple menues etc. The communication with the Arduino or RPi works via I2c. You will need only 4 wires to connect the shield.


Pls check this link for sample code and more information


The pcb fits perfect in our DIN rail enclosure sets for Raspberry Pi and Arduino.


Arduino OLED


Raspberry Pi

Shield front view



Interfacing 16x2 LCD by using  MCp23017 16 Bit input/output Port Expander IC with Raspberry Pi by using I2C Interface. To interact with the IC here we have used Pi4J and JAVA.



MCP23017 Features:

  16-bit input/output port expander with interrupt output

  Cascadable for up to 8 devices on one bus

  25mA sink/source capability per I/O

  Supports 100kHz, 400kHz and 1.7MHz I2C™Compatible compatible    modes


Intro visual Source:

MCP23017 Details :


Links :

I2C Communication on Pi :

16x2 LCD with Pi :

Java Application on Pi Playlist:

Schematic :

Pi4J GPIO Numbering :

Download Pi4J Library :

Code :



Subscribe YouTube :


Guys Subscribe to my channel for latest contents into your inbox.

Support me to keep going.


Website :


Connecting MCp23017 16 Bit input/output Port Expander IC with Raspberry Pi by using I2C Interface. To interact with the IC here we have used Pi4J and JAVA.


MCP23017 Features:

  16-bit input/output port expander with interrupt output

  Cascadable for up to 8 devices on one bus

  25mA sink/source capability per I/O

  Supports 100kHz, 400kHz and 1.7MHz I2C™Compatible compatible    modes


Intro visual Source:

MCP23017 Details :


Links :

Java Application on Pi Playlist:

Schematic :

Pi4J GPIO Numbering :

Download Pi4J Library :

Code :



Subscribe YouTube :


Guys Subscribe to my channel for latest contents into your inbox.

Support me to keep going.


Website :

Twitter :

YouTube :

Instagram :



Dear: Element 14 Community


I am letting you guys know I am building a raspberry pi cluster based off of a laser cut frame I designed and cut on a laser cutter and designed with librecad.


Let me just explain first of all my experiences as an engineer. Here are a list of accomplishments I have made within the past few years.


  • Built a video game for xbox 360 from XNA C#.
  • Built a 3D printer.
  • Built several robots with Arduino.
  • 3D printed a  ton of junk in my basement.
  • Working on a new 3D printer.
  • Did first robotics and learned netbeans ide.
  • and more...

I also have used a raspberry pi before. I recently got a raspberry working with an lcd display and raspbian. Here are a list of parts I need to continue the project.

  • 60 * m2.5 X 15mm bolts.
  • 15 * RPi3
  • A ton of Ethernet cables
  • A 15 usb port usb bus
  • A 15 Ethernet port Ethernet bus
  • usb micro cables.

I would also need to accomplish the following.


  • Powering 15 raspberry pis.
  • Getting 15 raspberry pi's in a  cluster.
  • Mounting and keeping things organized in the cluster.
  • Program a code breaking algorithm.


Wish me good luck!!! Thanks!!!

This's a pretty clever design, and I thought to myself "it wouldn't take much to make these into actual cartridges, if the Pi Compute was used as an edge connector".


Still, the images speak for themselves, and the creator used Berryboot to allow the OSs to be changed easily.


{gallery} Raspberry SUPER PI


Super Pi: Switch OS by switching cartridges


Super Pi: Looks almost like a SNES


Super Pi: Especially when next to a controller


Source: Imgur Gallery / blog




How would you design this differently? I think this makes it very accessible for people of all ages, and microSD cards are so small these days they're easy to lose...


Showing messages on 16X2 LCD display by interfacing with Raspberry Pi using JAVA and Pi4J library.

Intro visual Source:


Links :

Java Application on Pi Playlist:

Schematic :

Pi4J GPIO Numbering :

Download Pi4J Library :

Code :


Subscribe YouTube :



Guys Subscribe to my channel for latest contents into your inbox.

Support me to keep going.



Website :

Twitter :

YouTube :

Instagram :



This is just a High Level Diagram approximation of what the Pi 3 consists of.

It is based on various bits of information on the Internet, and could be incorrect in places.

If you have any corrections, or additional bits of information/suggested tweaks, please let me know and I'll get the diagram updated.




Diagram revision: 4

Filter Blog

By date: By tag: