Skip to content

Commit b0ba7ef

Browse files
committed
v1.0.1 - working binaries
now signed
1 parent 4e6f809 commit b0ba7ef

File tree

2 files changed

+11
-3
lines changed

2 files changed

+11
-3
lines changed

LaunchControl.apk

3.15 KB
Binary file not shown.

README.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Fireworks Launch Control using a Raspberry Pi and Android phones.
44

55
##RPi
66

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.
88
This is simply triggering the correct GPIO pins for 200 ms at a time (see below).
99

1010
##Electrical
@@ -16,5 +16,13 @@ As for the ignition of the fuses; I used some 34 AWG Nichrome wire looped twice
1616

1717
##Android
1818

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
27+
* /api-fire - fires one random firework
28+
* /api-fuckall - fires ALL firework

0 commit comments

Comments
 (0)