You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Fireworks Launch Control using a Raspberry Pi and Android phones.
4
4
5
5
##RPi
6
6
7
-
Using node.js there is a small webserver (app.js) that currently displays which channels are ready to fire, along with some utility responses for the future Android app.
7
+
Using node.js there is a small webserver (app.js) that currently displays which channels are ready to fire, along with a super-simple API for the Android app.
8
8
This is simply triggering the correct GPIO pins for 200 ms at a time (see below).
9
9
10
10
##Electrical
@@ -16,5 +16,13 @@ As for the ignition of the fuses; I used some 34 AWG Nichrome wire looped twice
16
16
17
17
##Android
18
18
19
-
Pretty simple Android app using standard motion sensors and AsyncHTTP. The idea behind the app is that each user has to shake their phone in order to 'charge' the tnt plunger. By pressing fire afterwards the app will send a request to http://rpi/fire. Full source under /android. As mentioned; the only depedency is Async-HTTP (compile 'com.loopj.android:android-async-http:1.4.5'
20
-
) from loopj.
19
+
Pretty simple Android app using standard motion sensors and AsyncHTTP. The idea behind the app is that each user has to shake their phone in order to 'charge' the tnt plunger. Full source under /android. As mentioned; the only depedency is Async-HTTP (compile 'com.loopj.android:android-async-http:1.4.5'
20
+
) from loopj.
21
+
22
+
##API
23
+
24
+
The following commands are implemented:
25
+
26
+
* /api-status - returns wether or not any fireworks are ready
0 commit comments