What Engineers Really Do



Auto Login and Auto Start in Raspberry Pi

Auto Login:

sudo nano /etc/inittab

Find line

1:2345:respawn:/sbin/getty 115200 tty1

Comment it out

#1:2345:respawn:/sbin/getty 115200 tty1

Add the following line just below the commented line

1:2345:respawn:/bin/login -f pi tty1 /dev/tty1 2>&1

Auto start something:

sudo nano /etc/profile

Add the following line to the end of the file

. /home/pi/your_script_name.sh

Set Static IP for Raspberry Pi

sudo nano /etc/network/interfaces

Simply change the line that reads:

iface eth0 inet dhcp


iface eth0 inet static
Then directly below this line enter like the following
sudo ./etc/init.d/networking restart
sudo reboot

Log back in and run


Home Automation Standards

Automating your home used to mean spending big bucks to get a specialized control system installed inside your walls, but that’s all changing. Simple DIY smart home gadgets are quickly becoming commonplace, so if you’re thinking about dipping your toes into automation and smartening up your pad, it’s important that you know the difference between the various home automation protocols out there.
Just like other electronic systems, smart devices all run on a variety of different protocols. That is, sets of rules and standards for communication between electronic devices. Think of them like languages. If you’ve got one device that only speaks ZigBee and another that only speaks Z-Wave, they won’t be able to communicate with each other. Ideally you’ll want to outfit your home with devices that all speak the same language, but there are a few products out there that are multilingual, so if you’ve got the right gateway you can mix and match. In this article we’ll offer up a quick rundown of all the major consumer-level home automation protocols and their respective pros/cons. That way, you’ll be able to make more informed decisions if you decide to give your home a smart boost.
Continue reading Home Automation Standards

Build a Chrome & Opera Extension

Create a folder.
Create a file “manifest.json” inside the directory.

{  "name": "My Extension",  "version": "1.0",  "manifest_version": 2,  "description": "This is an example extension.",  "browser_action": {  "default_icon" : "icon.png",  "default_popup" : "window.html"}}

The file must be UTF-8 encoded.
It can work both on Google Chrome and Opera browsers.