Project

General

Profile

Users Guide » History » Version 13

Hammel, 20 Sep 2019 10:25

1 10 Hammel
h1. Ironman Users Guide
2 1 Hammel
3 7 Hammel
table{border-collapse;width:100%}.
4 8 Hammel
|={font-size:140%;margin-bottom:15px;background-color:#fdd}. This document is under development and is likely not accurate at this time. |
5 7 Hammel
6 2 Hammel
{{>toc}}
7
8 3 Hammel
In this document the term _host system_ refers to a Linux desktop or laptop that will be used to download and install software
9
onto an SD card.
10 1 Hammel
11 10 Hammel
h2. Overview
12
13 12 Hammel
Ironman is a home automation project based on the PiBox build system.  It supports a Nest-like monitor for controlling Arduino based sensors, cameras and remote voice control.
14 1 Hammel
15
|!http://redmine.graphics-muse.org/attachments/download/114!|
16
|={font-size:120%;margin-bottom:15px;background-color:#dff}. *Design Intent of the Ironman Project* |
17
|=. Mark I release is in progress.  Mark II and Mark III are future development plans.|
18
19 12 Hammel
Ironman consists of the following components.
20
21
| *Monitor* | The Nest-like control hub based on a Raspberry Pi 2/3 and the official 7" touchscreen display |
22
| *Sensors* | Arduino based devices, such as door alarms and cameras, running code based on a sensor and camera templates for pairing and secure communication with the Monitor |
23
| *Jarvis*  | A Java application that supports voice control of Monitor managed devices |
24
| *Controllers* | Network enabled control of Monitor managed devices |
25
26 1 Hammel
h3. Security
27
28
Ironman supports AES encrypted communication with IoT sensors and Jarvis interfaces.
29 12 Hammel
30
h3. What it is
31
32
Ironman is a do-it-yourself system, where you buy the parts and assemble them as described, modifying the provided code to suit your needs and handling flashing and maintenence.  Ironman is designed to allow you to build your own home automation system where you specify the devices you want to control and how you want to control them.
33
34
h3. What it is not
35
36
Ironman is not a product.  It is not intended for anyone other than Makers (aka DIY'ers) who like to tinker and see not just how to assemble things but why they actually work.
37
38 13 Hammel
While the Users Guide is intended to bring up a currently working version of Ironman with limited sensor and camera support, if you aren't prepared to deal with writing code or flashing devices and dealing with electrical circuits then Ironman is not for you.
39 10 Hammel
40 1 Hammel
h2. The Ironman Monitor
41 3 Hammel
42 10 Hammel
The Ironman Monitor runs on a Raspberry Pi 2 or 3 and provides a central hub for management of home automation devices.  It uses a 7" touch screen display and a mechanical switch to manage pairing with IoT devices and Jarvis interfaces.
43 3 Hammel
44
h3. Installation Prerequisites
45 1 Hammel
46 11 Hammel
* A "Raspberry Pi 2 or 3":https://www.adafruit.com/product/3055
47
* The official "Raspberry Pi 7inch touchscreen display":https://www.sparkfun.com/products/13733
48
* The Pi 2/3 requires a "V / 2A power supply":https://www.adafruit.com/product/1994.  For best results, use a power supply rated to at least 5.25V to avoid under voltage conditions.  For ease of use the power supply cable should include an "on/off switch":https://www.adafruit.com/product/2379.
49 3 Hammel
* The Pi 2/3 requires a microSD card that is at least 4GB.  A mechanism for using the SD card on your host system is needed, such as an SD card USB adapter or an SD port on your laptop.
50 10 Hammel
* A mechanical switch, such as a "SPDT":https://www.electronicshub.org/switches/#Single_Pole_Double_Throw_Switch_SPDT, should be connected to the Pi GPIOs to allow for pairing the Monitor with IoT Sensors and Jarvis interfaces.  The ASCII diagram below describes the setup. The LED is lit in normal mode and off in Pair Mode until something tries to pair with the Pi.
51 5 Hammel
52
<pre>
53
                    ___
54
           Normal  |---|  Pair Mode
55
                 --------- 
56
                |         |
57
                 --------- 
58
        pins -->  |  |  |  
59
60
       RPi GPIO   4  G  27
61 6 Hammel
        RPi pin   7  9  13     
62
                     |  |
63
                     |  +---LED---+
64
                     |            |
65
                     +---330 R----+
66 5 Hammel
</pre>
67
68 6 Hammel
* You will need to have sudo access for your Linux user id.
69 3 Hammel
70 1 Hammel
h3. Generating the SD Card for the Pi
71 3 Hammel
72 1 Hammel
* Download the RPi 2 Development Platform 
73 4 Hammel
** _wget <url>_
74
** Unpack the archive to a directory called *image*.
75 1 Hammel
* Download the Ironman Package Collection
76 4 Hammel
** _wget <url>_
77
** Unpack the archive to a directory called *package*.
78 3 Hammel
79 4 Hammel
In a terminal window run: _dmesg -w_
80 1 Hammel
Insert the microSD card and look for the device name for the newly added card.  It should be something like /dev/sdb or /dev/sde.
81 4 Hammel
Kill the _dmesg -w_ command with Ctrl-C.
82 3 Hammel
83 4 Hammel
From the *image* directory
84 1 Hammel
* Format the SD card
85 4 Hammel
** _sudo ./mksd.sh -d <device name>_
86 3 Hammel
** where <device name> is the name you noted from the output of dmesg -w.
87 1 Hammel
* Mount the boot partition from the sd card: 
88 4 Hammel
** _sudo mkdir -p /mnt/boot_
89
** _sudo mount <device name>1 /mnt/boot_
90 1 Hammel
** where <device name> is the name you noted from the output of dmesg -w.
91 4 Hammel
* Install the Development Platform to the SD card
92
** _sudo ./mkinstall.sh -b /mnt/boot -d <device name>2_ 
93 3 Hammel
** where <device name> is the name you noted from the output of dmesg -w.
94
95 4 Hammel
From the *package* directory
96 3 Hammel
* Mount the root partition from the sd card: 
97 4 Hammel
** _sudo mkdir -p /mnt/root_
98
** _sudo mount <device name>1 /mnt/root_
99 3 Hammel
* Copy the Ironman Package Collection files to /root of the root partition on the SD card
100 4 Hammel
** _sudo cp *.opk /mnt/root/root_
101 3 Hammel
102
Make sure all writes to the SD card have completed
103 4 Hammel
* _sync;sync;sync_
104 3 Hammel
105
Unmount the SD card partitions
106 4 Hammel
* _sudo umount /mnt/boot_
107
* _sudo umount /mnt/root_
108 3 Hammel
109 4 Hammel
Remove the SD card from the host system and insert it into the Raspberry Pi 2.
110 1 Hammel
111
h3. First time boot
112
113
h3. Network configuration
114
115 9 Hammel
wlan0
116
117
* This interface is used for configuration of the Monitor.
118
* Configured on the 192.168.36.0 subnet.
119
** See /etc/network/dhcpd.conf.aponly
120
121
uap0
122
123
* This interface is used as an access point for IoT devices.
124
* Configured on the 192.168.3.0 subnet.
125
** See /etc/network/dhcpd.conf.uap and dhcpd.conf.uap.tmpl
126
** The template is used to change the base subnet through the web interface.
127
** The SSID is _ironman_.
128
129
<pre>
130
Pair/Config button is GPIO 4 (RPi pin 7)
131
Pair/Config LED is GPIO 7 (RPi pin 13)
132
	LED should only be lit on boot if button is enabled (in Config mode).
133
		In this case, we're in Config Mode to configure the networks.
134
		The web server (imwww) is on SSID "ironman" at 192.168.36.1:1337.
135
	LED is off on boot if button is disabled (in Pair Mode).
136
	If in Pair Mode
137
		Start hostapd for aponly
138
		Start dhcpd for aponly on wlan0
139
		Start imrest web service on port 8165 for IoT devices and Jarvis interfaces.
140
	If in Config Mode
141
		Start wpa_supplicant on wlan0
142
		Create uap0 device as virtual device on wlan0
143
		Start dhcpd on uap0
144
		Start hostapd on uap0
145
		Start imwww for network configuration of the Monitor.
146
147
/etc/ironman/iot		Registration directory for IoT devices
148
/etc/ironman/jarvis		Registration directgory for Jarvis interfaces
149
</pre>
150
151
152 1 Hammel
h3. Pairing with IoT Sensors
153
154
h3. Pairing with Jarvis
155
156
h2. IoT Sensor
157
158
h3. Sensor Types
159
160
h4. Light Switch
161
162
h3. Flashing the firmware
163
164
h3. Power On
165
166
h3. Pairing with a Monitor
167
168
h2. Jarvis
169
170
h3. Prerequisites
171
172
h3. Pairing with a Monitor
173
174
h3. Supported Commands