Planning Notes » History » Version 2
Hammel, 18 Jan 2016 14:27
1 | 1 | Hammel | h3. voice control interface to infrastructure |
---|---|---|---|
2 | |||
3 | * mobile |
||
4 | 2 | Hammel | * "Jarvis":https://gitlab.com/groups/xjarvis |
5 | 1 | Hammel | * home UIs - NEST-like |
6 | * Follow-Me architecture - voice control follows you around the home. |
||
7 | |||
8 | h3. futuristic media display system |
||
9 | |||
10 | * display on glass w/ |
||
11 | ** static opaqueness |
||
12 | ** variable opaqueness |
||
13 | * Heads up |
||
14 | * Motion capture |
||
15 | |||
16 | h3. system control |
||
17 | |||
18 | * thermostatic and vent |
||
19 | * windows/shades/blinds |
||
20 | * garden |
||
21 | |||
22 | h3. robotic assistance |
||
23 | |||
24 | h3. controlled access: doors, windows, garage |
||
25 | |||
26 | h3. security cameras |
||
27 | |||
28 | h3. controllable power: outlets, lights |
||
29 | |||
30 | h3. resource management: |
||
31 | |||
32 | * what do you need (toilet paper, eggs) |
||
33 | |||
34 | h3. Monitoring: utilities |
||
35 | |||
36 | * location: humans, pets, visitors |
||
37 | |||
38 | 2 | Hammel | h3. MediaDevices |
39 | 1 | Hammel | |
40 | 2 | Hammel | * "DLNA - Digital Living Network Alliance":http://www.dlna.org/ |
41 | ** "DLNA Open Source Projects":http://elinux.org/DLNA_Open_Source_Projects#UPnP_Media_Players @ Wikipedia |
||
42 | * Libraries |
||
43 | ** "libdlna":http://libdlna.geexbox.org/ - Reference DLNA open-source implementation for Linux, both servers and players |
||
44 | ** "pupnp":http://pupnp.sourceforge.net/ - aka libupnp, Portable C SDK for UPnP devices |
||
45 | ** "Platinum UPnP":http://www.plutinosoft.com/platinum - C++ SDK to make it easy to build DLNA compliant devices |
||
46 | ** "GUPnP":https://wiki.gnome.org/Projects/GUPnP - similar to libupnp but with more abstraction to hide internals |
||
47 | * Servers |
||
48 | ** "uShare":http://ushare.geexbox.org/ - A free UPnP A/V & DLNA Media Server for Linux |
||
49 | ** "ReadyMedia":http://sourceforge.net/projects/minidlna/ - aka minidlna |
||
50 | *** "ArchLinux guide":https://wiki.archlinux.org/index.php/ReadyMedia |
||
51 | |||
52 | 1 | Hammel | h3. home data center |
53 | |||
54 | 2 | Hammel | * See "Media Devices":#MediaDevices and DLNA |
55 | |||
56 | 1 | Hammel | h2. Device node |
57 | |||
58 | Concept of a module unit so each new application doesn't need a new device. |
||
59 | |||
60 | 2 | Hammel | * "esp8266":http://www.esp8266.com/ for IoT |
61 | ** "Nurdspace references":https://nurdspace.nl/ESP8266 |
||
62 | ** "WikiPedia":https://en.wikipedia.org/wiki/ESP8266 entry |
||
63 | * "CHiP":http://getchip.com/ / "RPi Zero":https://www.raspberrypi.org/products/pi-zero/ for subnodes |
||
64 | * "RPi 2 Model B":https://www.raspberrypi.org/products/pi-zero/ quad-core for master nodes |
||
65 | * No Intel - Only ARM or related |
||
66 | 1 | Hammel | * Want a reusable minimal component |
67 | |||
68 | h2. Products |
||
69 | |||
70 | * server box - master @ home, could have multiple, distributed in a single home |
||
71 | * subnode - manages a collection of devices, reports to master |
||
72 | * nodes - IoT, media servers - any "thing" that is an endpoint |
||
73 | |||
74 | h2. Problems |
||
75 | |||
76 | * Margins: 80-100% initially, %30 sustained |
||
77 | * Cost: $80 per outlet would not be reasonable |
||
78 | * wired network (wireline electrical)? |
||
79 | * wifi problems? |
||
80 | ** g - interference |
||
81 | ** n - faster, still interference? |
||
82 | ** ac - best? not in esp8266? |
||
83 | ** could we use non-wifi comm? |
||
84 | * Comm security |
||
85 | * power IoT - must last a long time |
||
86 | ** power harvesting |
||
87 | ** minimal power for comm - save most for control of device |
||
88 | * Mechanical experience |
||
89 | * Data band vs Control band |
||
90 | ** wifi for data |
||
91 | ** bluetooth or other RF for control |
||
92 | * No cloud - network comm is private, not to 3rd party |
||
93 | ** Add on: we manage a server |
||
94 | |||
95 | h2. What is the MVP? |
||
96 | |||
97 | * Proof of Concept: defined by Feb 20th |
||
98 | * 1st product: definition by end of April |
||
99 | 2 | Hammel | * Danny - Jasper project working code - integrate with "Jarvis":https://gitlab.com/groups/xjarvis? |
100 | * Mike - "PiBox":http://www.graphics-muse.org/wiki/pmwiki.php/RaspberryPi/RaspberryPi, builds and infrastructure, UI maybe |
||
101 | 1 | Hammel | |
102 | h2. How do we divvy the work? |
||
103 | |||
104 | * Electrical: Danny, Mike |
||
105 | * Software: Mike, Danny |
||
106 | |||
107 | h2. What's already out there? |
||
108 | |||
109 | * what niches are not being filled? |
||
110 | * what niches are we competing against? |
||
111 | |||
112 | h2. Things to look at? |
||
113 | |||
114 | * Wink - home automation/IoT company |
||
115 | ** app-celerator - write Javascript, compile into mobile-specific apps |
||
116 | * Blynk - home automation mobile dev tool |