Project

General

Profile

Planning Notes » History » Version 4

Hammel, 18 Jan 2016 16:30

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 3 Hammel
* Motor control tutorials
22
** " How-To: Motors":http://www.instructables.com/id/How-To-Motors/?ALLSTEPS @ Instructables
23
** "Control a DC Motor with an Arduino":http://www.allaboutcircuits.com/projects/control-a-motor-with-an-arduino/ @ All About Circuits
24
** "DC Motors":https://learn.adafruit.com/adafruit-arduino-lesson-13-dc-motors/overview @ Adafruit
25
** "Stepper Motors":https://learn.adafruit.com/adafruit-arduino-lesson-16-stepper-motors/overview @ Adafruit
26
** " Stepper Motor Quickstart Guide":https://www.sparkfun.com/tutorials/400
27 4 Hammel
* Stepper Motors
28
** "5v 28YBJ-48 Stepper Motor with Gear Reduction":http://arduino-info.wikispaces.com/SmallSteppers?responseToken=775f5a4b2f50b66a5603d762b13c435e
29
*** "from Adafruit":https://www.adafruit.com/products/858
30
*** "Sparkfun stepper motor driver":https://www.sparkfun.com/products/12779 alternative driver board
31
*** This means: 5v Arduino Pro Mini or Nano with driver board and 28YBJ-48 Stepper Motor driven by 5-12v power
32
*** Would require additional esp8266 or other comm board
33 1 Hammel
34
h3. robotic assistance
35
36
h3. controlled access: doors, windows, garage
37
38
h3. security cameras
39
40
h3. controllable power: outlets, lights
41
42
h3. resource management:
43
44
* what do you need (toilet paper, eggs)
45
46
h3. Monitoring: utilities
47
48
* location: humans, pets, visitors
49
50 2 Hammel
h3. MediaDevices
51 1 Hammel
52 2 Hammel
* "DLNA - Digital Living Network Alliance":http://www.dlna.org/ 
53
** "DLNA Open Source Projects":http://elinux.org/DLNA_Open_Source_Projects#UPnP_Media_Players @ Wikipedia
54
* Libraries
55
** "libdlna":http://libdlna.geexbox.org/ -  Reference DLNA open-source implementation for Linux, both servers and players
56
** "pupnp":http://pupnp.sourceforge.net/ - aka libupnp, Portable C SDK for UPnP devices
57
** "Platinum UPnP":http://www.plutinosoft.com/platinum - C++ SDK to make it easy to build DLNA compliant devices
58
** "GUPnP":https://wiki.gnome.org/Projects/GUPnP - similar to libupnp but with more abstraction to hide internals
59
* Servers
60
** "uShare":http://ushare.geexbox.org/ - A free UPnP A/V & DLNA Media Server for Linux
61
** "ReadyMedia":http://sourceforge.net/projects/minidlna/ - aka minidlna
62
*** "ArchLinux guide":https://wiki.archlinux.org/index.php/ReadyMedia 
63
64 1 Hammel
h3. home data center
65
66 2 Hammel
* See "Media Devices":#MediaDevices and DLNA
67
68 1 Hammel
h2. Device node
69
70
Concept of a module unit so each new application doesn't need a new device.
71
72 2 Hammel
* "esp8266":http://www.esp8266.com/ for IoT
73
** "Nurdspace references":https://nurdspace.nl/ESP8266
74
** "WikiPedia":https://en.wikipedia.org/wiki/ESP8266 entry
75
* "CHiP":http://getchip.com/ / "RPi Zero":https://www.raspberrypi.org/products/pi-zero/ for subnodes
76
* "RPi 2 Model B":https://www.raspberrypi.org/products/pi-zero/ quad-core for master nodes
77
* No Intel - Only ARM or related
78 1 Hammel
* Want a reusable minimal component
79
80
h2. Products
81
82
* server box - master @ home, could have multiple, distributed in a single home
83
* subnode - manages a collection of devices, reports to master
84
* nodes - IoT, media servers - any "thing" that is an endpoint
85
86
h2. Problems
87
88
* Margins: 80-100% initially, %30 sustained
89
* Cost: $80 per outlet would not be reasonable
90
* wired network (wireline electrical)?
91
* wifi problems?
92
** g - interference
93
** n - faster, still interference?
94
** ac - best?  not in esp8266?
95
** could we use non-wifi comm?
96
* Comm security
97
* power IoT - must last a long time
98
** power harvesting
99
** minimal power for comm - save most for control of device
100
* Mechanical experience
101
* Data band vs Control band
102
** wifi for data
103
** bluetooth or other RF for control
104
* No cloud - network comm is private, not to 3rd party
105
** Add on: we manage a server
106
107
h2. What is the MVP?
108
109
* Proof of Concept:  defined by Feb 20th
110
* 1st product:  definition by end of April
111 2 Hammel
* Danny - Jasper project working code - integrate with "Jarvis":https://gitlab.com/groups/xjarvis?
112
* Mike - "PiBox":http://www.graphics-muse.org/wiki/pmwiki.php/RaspberryPi/RaspberryPi, builds and infrastructure, UI maybe
113 1 Hammel
114
h2. How do we divvy the work?
115
116
* Electrical: Danny, Mike
117
* Software: Mike, Danny
118
119
h2. What's already out  there?
120
121
* what niches are not being filled?
122
* what niches are we competing against?
123
124
h2. Things to look at?
125
126
* Wink - home automation/IoT company
127
** app-celerator - write Javascript, compile into mobile-specific apps
128
* Blynk - home automation mobile dev tool