https://wiki.emfcamp.org/2014/w/api.php?action=feedcontributions&feedformat=atom&user=Ms7821Electromagnetic Field - User contributions [en]2026-06-04T12:18:10ZUser contributionsMediaWiki 1.39.6https://wiki.emfcamp.org/2014/w/index.php?title=TiLDA_MKe&diff=3819TiLDA MKe2014-12-09T15:01:43Z<p>Ms7821: /* Debugging and Gotchas */</p>
<hr />
<div>[[File:IMG_0474.jpg|500px|right|thumb|Front]]<br />
[[File:Badge_Front.png|right|thumb|Front]]<br />
<br />
[http://en.wikipedia.org/wiki/E_(mathematical_constant) Why MKe?]<br />
<br />
=EMF 2014 Badge= <br />
The main aim of the 2014 badge is to give camp attendees an interesting bit of hardware to play with during the camp and experiment with afterwards. We designed an Arduino compatible platform to allow easy reuse and access, and have published all code and design files.<br />
<br />
==Battery Warning==<br />
A very last minute battery (and connector) change on the badge due to a supplier problem meant two issues arose with the badge during EMF:<br />
<br />
* '''Always make sure to plug your battery in the right way round!''' The new battery connector allows you to connect it backwards. We did our best to mitigate this, but connecting it incorrectly will destroy the power management controller and prevent the badge from charging or running from the battery. It will still function perfectly using USB power. "Red" and "Black" are written next to the connector - please make sure to plug it in correctly.<br />
<br />
* '''Be careful not to short the battery connector wires!''' The new battery connector slightly exposes the wires when the battery is plugged in. If a metal object shorts the two wires, it can result in extreme battery damage. If we'd known this was such an issue before the event we would have applied protective material to it - we suggest covering the exposed connector in tape, sugru, blu-tack, or some other insulating material. Alternatively, simply unplug the battery when your badge is not in use!<br />
<br />
==My badge is broken!==<br />
Due to the aforementioned supplier issues it is possible that you may have received a faulty badge, or it may have been damaged by connecting the battery backwards. If you badge will not turn on when it has been plugged in with a MicroUSB cable (and the power switch on the back is set to "USB"), or something else seems wrong with it, please email [mailto:badge@emfcamp.org badge@emfcamp.org] and we'll try to fix or replace your badge.<br />
<br />
==Basic post-event features==<br />
We made sure that the badge has a few features to play with once the event is over. More will be added over time as attendees submit changes to us.<br />
<br />
[[File:Badge_Back.png|right|thumb|Back]]<br />
* Torch mode - Press the light button next to the screen. It will only light up fully if it's hung upside down to avoid blinding<br />
* Snake<br />
* Tetris<br />
<br />
But of course the point of the badge is to modify it and use it for other interesting things! The following sections describe how to update the firmware on the badge, how to use it as a simple arduino, and how to write your own code for the main badge firmware.<br />
<br />
==Getting help==<br />
The EMF 2014 badge is a complex piece of hardware and software, however remember that you can just treat it as an Arduino if you find it all too daunting.<br />
<br />
If you get stuck and need advice, there's an [http://webchat.freenode.net/?channels=tilda active IRC chatroom] you can join to ask for advice, or if you're really stuck you can email us on [mailto:badge@emfcamp.org badge@emfcamp.org].<br />
<br />
=How to update the badge software & program the badge=<br />
The badge software has been substantially updated since EMF, fixing bugs and removing features that will no longer work now you're away from our radio network. You should update your badge before starting to play with it any further. If you've never used an Arduino before this might be tricky - ask an Arduino-literate friend to help you, or drop by your nearest [http://hackspace.org.uk hackspace] and ask for advice.<br />
<br />
The badge is Arudino Due compatible, so [http://arduino.cc/en/Guide/ArduinoDue some of their instructions may help you if you have problems].<br />
<br />
==Set up your environment==<br />
* Plug your badge into your computer via a MicroUSB cable. Make sure the power switch on the back is set to "USB".<br />
* Download Arduino IDE 1.5.7 from http://arduino.cc/en/main/software#toc3<br />
* Download the TiLDA firmware code from https://github.com/emfcamp/Mk2-Firmware<br />
* Start the Arduino IDE.<br />
* Now you have to change the sketchbook-folder to be the folder you just cloned or downloaded. To do this use File -> Preferences -> “Set Sketchbook location”. On MacOS, this is Arduino -> Preferences. <br />
* Restart the Arduino IDE.<br />
* Open sketch “EMF2014”.<br />
* Set Tools -> Board to MKe v0.333 (RTOS Core).<br />
* Set Tools -> Port to correct port for the Arduino<br />
** On MacOS this is will start /dev/tty.usbmodem with 4 digits, and change for each port<br />
** On Linux this is usually /dev/ttyACM0 but may be a higher number if you have other USB Serial devices<br />
* Hit the upload button<br />
* Wait<br />
* Your badge should now be running the latest TiLDA firmware!<br />
<br />
==Programming the badge as an Arduino==<br />
The badge is completely Arduino Due compatible, simply set the board type to "MKe v0.333(Arduino Core)" upload normal Arduino code and the badge will function. However if you want to use any of the more complex hardware on the badge (such as the screen and radio) we recommend programming it using our FreeRTOS framework documented below.<br />
<br />
Below is a version of the standard blink sketch that will flash the RX and TX LEDs<br />
<br />
<code><br />
void setup() {<br />
pinMode(PIN_LED_TX, OUTPUT);<br />
pinMode(PIN_LED_RX, OUTPUT);<br />
}<br />
<br />
void loop() {<br />
digitalWrite(PIN_LED_TX, HIGH);<br />
digitalWrite(PIN_LED_RX, LOW);<br />
delay(1000);<br />
digitalWrite(PIN_LED_TX, LOW);<br />
digitalWrite(PIN_LED_RX, HIGH);<br />
delay(1000);<br />
}<br />
</code><br />
<br />
If you do program the badge with simple Arduino code but wish to switch back to our official firmware, simply change the sketch to "EMF2014" (and if needed set the board type back to "MKe v0.333 (RTOS Core)") and upload again.<br />
<br />
To make the badge Arduino shield compatible, follow [https://wiki.emfcamp.org/wiki/TiLDA_MKe#Making_the_badge_Arduino_shield_compatible these instructions].<br />
<br />
==Programming the badge in FreeRTOS==<br />
===Your first “Hello world” app===<br />
There’s a “HelloWorldApp.cpp” file in which you can play around. In order for it to show up on the Homescreen you have to uncomment line 51 in AppManager.cpp and flash the changed code to the badge. Great app pull requests are appreciated!<br />
<br />
If you are still using the Arduino IDE at this point, note that it will not let you edit the .cpp and .h files that are needed to create Apps for the badge. To force the IDE to re-compile/re-read any files you've edited using an external editor, make sure to go to the File -> Preferences dialog box, and check the "Use external editor" checkbox.<br />
<br />
===Why are things so different from standard Arduino code?===<br />
We’re using a library called FreeRTOS that allows us to multitask - something that’s normally not possible with standard Arduino code. This allows us to run multiple tasks at the same time. FreeRTOS uses preemptive scheduling to switch between the task. Due to this we have to be very careful about how we do some things. For example we can’t just define interrupts for buttons in every task (imagine the mess!) or write to the serial port directly (your task might stop in the middle of the message). <br />
<br />
We’ve also spent quite a lot of time to make the built-in components as easy to use as possible without having every task to write lots of boilerplate code. If you feel like using the build-in components on the badge, chances are we already wrote a wrapper for them that is already used by one of the other tasks. <br />
<br />
Have a look at the “Documentation” section in this document for a full list of API functions. You will avoid a lot of headaches if you stick to those.<br />
<br />
=== Code structure ===<br />
* FreeRTOS has the concept of “Tasks” which work like threads. We’ve wrappered them in a class called “Task” (for background stuff) and “Apps” (for foreground, one-at-a-time things)<br />
* Everything needs to be in the main EMF2014 folder. Subfolders are not allowed. This is an Arduino IDE restriction :(<br />
<br />
==Debugging and Gotchas==<br />
* The USB serial is set up to 115200 baud. There are lots of terminals that can connect to them. See below for how to enable the debug logging.<br />
* If you can’t revive a badge, or only get the two red programming LEDs when you plug it, in, do a full erase (see below)<br />
* Avoid busy waiting, use FreeRTOS queues and Tilda::delay() instead<br />
* Don’t use low level functions like interrupts or serial ports directly unless you really, really know how FreeRTOS will handle them. For general logging you can use Tilda::log()<br />
* If sending code to the badge using the Arduino IDE "Upload" button fails, even though the /dev/ttyACM0 (linux com port) is there, just retry, twice if neccessary.<br />
<br />
==Full erase==<br />
This is the failsafe process if your badge won't show up over USB.<br />
<br />
# Unplug the badge<br />
# Connect the Erase pins on the back together (two holes down the left hand side next to the battery and under the blue wireless module). You can use a jumper, jump wire, or the leg of a resistor for this.<br />
# Turn the badge back on with the switch or plug it back in<br />
# Press the Reset button on the front (bottom centre) and release<br />
# Wait 15 seconds<br />
# Unplug the badge or turn it off<br />
<br />
When you plug the badge back into a computer it will come back up in programming mode, with a different serial port to the usual one. Open the EMF 2014 sketch in the Arduino IDE, select the Tilda v0.333 (RTOS) programmer, and find the new serial port. The IDE console should show something like this:<br />
<br />
Sketch uses 118,748 bytes (22%) of program storage space. Maximum is 524,288 bytes.<br />
Erase flash<br />
Write 127668 bytes to flash<br />
<br />
[ ] 0% (0/499 pages)<br />
[ ] 2% (10/499 pages)<br />
[= ] 4% (20/499 pages)<br />
[= ] 6% (30/499 pages)<br />
...<br />
[============================= ] 98% (490/499 pages)<br />
[==============================] 100% (499/499 pages)<br />
Verify 127668 bytes of flash<br />
<br />
[ ] 0% (0/499 pages)<br />
[ ] 2% (10/499 pages)<br />
[= ] 4% (20/499 pages)<br />
[= ] 6% (30/499 pages)<br />
...<br />
[============================= ] 98% (490/499 pages)<br />
[==============================] 100% (499/499 pages)<br />
Verify successful<br />
Set boot flash true<br />
CPU reset.<br />
<br />
==Your own wireless badge network==<br />
[[DIY TiLDA Badge Network]] has instructions on how to setup your own private badge network using a RaspberryPi and two Ciseco radios.<br />
<br />
==Contribute==<br />
Send us a pull request via [https://github.com/emfcamp/Mk2-Firmware GitHub] - We’ll do our best to review and merge the good ones during EMF so others can use them.<br />
<br />
=Using the badge hardware=<br />
The badge has a plethora of hardware built in for you to play with, everything from accelerometers and gyroscopes to hidden ethernet headers! Breaking it all down is too much detail for this document, however we'll call out some things we built in that you might want to play with.<br />
<br />
Remember the badge is Arduino Due compatible, and we broke out nearly all the features of the ARM chip so you can access them. [http://arduino.cc/en/Main/ArduinoBoardDue Anything the Due can do], the TiLDA can do!<br />
<br />
==Making the badge Arduino shield compatible==<br />
[[File:Sheild_Headers.JPG|500px|right|thumb|Sheild Headers]]<br />
To make the badge Arduino shield compatible you'll need to solder simple strips of header pins onto the back of the badge. <br />
You need the following headers<br />
{| class="wikitable"<br />
|-<br />
! Qty !! Type !! Use !! Rapid part<br />
|-<br />
| 1 || 2x03 Male || SPI ||<br />
|-<br />
| 2 || 1x08 Female || Power, Analog pins ||<br />
|-<br />
| 2 || 1x10 Female || Digital pins ||<br />
|-<br />
| 1 || 2x08 Male || Ethernet ||<br />
|}<br />
The picture to the right shows the placement.<br />
<br />
==Interesting things to play with==<br />
Most of the interesting things are on the back of the badge. They're clearly marked in white. [https://wiki.emfcamp.org/w/images/b/bd/Badge_Back.png This diagram of the back] should allow you to locate them. Some of the following require extra parts to be added to your badge.<br />
<br />
* Full Arduino R3 shield compatible pins (Requires soldering the headers on the back of the badge)<br />
* Pins either side of the lanyard holes for conductive thread (D19, D18, GND, 3V3)<br />
* Infrared transmitter on the front (Pin shortcut IR_TX_PWM)<br />
* Infrared receiver on the front (Pin shortcut IR_RX, Part Vishay TSOP75238TT available from digikey and Farnell )<br />
* Piezo buzzer (Pin shortcut PIEZO or PIEZO_PWM)<br />
* On-board ethernet (not available on the Due) - requires breakout module (eBay: Elechouse Taijiuino Ethernet PHY DM9161 Module)<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro (IMUTask.cpp and the MPU6050 library)<br />
* 128x64 pixel backlit LCD display (JHD12864, see [https://github.com/emfcamp/Mk2-Documentation/tree/master/LCD%20JHD12864 here for docs])<br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
* [http://shop.ciseco.co.uk/powerpod-ncp1402-5v0/ PowerPOD NCP1402] interface, used to generate 5V from 3V3 battery supply power (needed for some shields)<br />
* MicroSD adapter breakout (Molex 1050270001 available from digikey)<br />
* Compass (magnetometer) breakout (HMC HMC5883L-TR available from digikey and Farnell)<br />
* Reprogramming headers for the 868Mhz [http://www.ti.com/product/cc1110f32 CC1110 radio module]<br />
* 1 megabit flash module (Part S25FL216K0PMFI011)<br />
* SPI breakout<br />
* 2x RGB LEDs on the front <br />
* FTDI header (shared with SRF Radio)<br />
* JTAG header (Part M50-3500542 available form Farnell<br />
<br />
==Included hardware==<br />
<br />
The following hardware has been included on the badge.<br />
<br />
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]<br />
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge<br />
** 32bit ARM Cortex M3 * 84MHz<br />
** 512KBytes Flash RAM<br />
** 96KBytes of SRAM<br />
* A 128x64 pixel monochrome LCD display<br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
** 868Mhz RF Transceiver<br />
** Simple UART interface<br />
** Low power sleep mode<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro<br />
** I2C interface<br />
** Tri-Axis angular rate sensor (gyro) with a sensitivity up to 131 LSBs/dps and a full-scale range of ±250, ±500, ±1000, and ±2000dps<br />
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g<br />
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronisation and gesture detection<br />
* PMIC & LiPo<br />
* Joystick, 4 way with click<br />
* Buttons<br />
* RGB LEDs<br />
* IR Transmitter<br />
* Arduino Headers<br />
* Pads for wearable tech<br />
<br />
=Useful Hacks!=<br />
==3d printable & laser-cuttable badge case==<br />
Draft 3d print-able and laser-able case files [http://www.thingiverse.com/thing:436815 here]<br />
==Convert images to TiLDA bitmap format==<br />
* A Python script (via [https://twitter.com/trotmaster99 @trotmaster99]) that converts a monochrome bitmap image into a format suitable for the Tilda can be found [http://pastebin.com/8XeazQjT here].<br />
* A similar script in Perl to create TiLDA MKe fullscreen bitmaps from XBM: -<br />
<div style ="height:200px;overflow-x:hidden;overflow-y:auto;border: 4px solid orange;"><br />
'''xbm2mke.pl by [[User:Msemtd]]'''<br />
<nowiki><br />
#!perl -w<br />
use strict;<br />
# Little script to convert a regular XBM to TiLDA MKe bitmap<br />
# only tested with fullscreen bitmaps!<br />
# Hot file handle magic...<br />
select((select(STDERR), $| = 1)[0]);<br />
select((select(STDOUT), $| = 1)[0]);<br />
sub t(@);<br />
sub d($);<br />
sub chug($);<br />
my $f = shift;<br />
#~ $f = 'blankish.xbm' if not $f;<br />
if(not defined $f or not $f =~ /^(.*)\.xbm$/i){<br />
die "Usage: gimme an XBM file dude!\n";<br />
}<br />
my $name = $1;<br />
t "Reading file '$f'...";<br />
my $data = chug($f);<br />
t "OK";<br />
my @lines = split /^/, $data;<br />
@lines = grep{chomp; s/^\s+//; s/\s+$//; length;} @lines;<br />
#~ t d \@lines;<br />
my($width, $height) = (0,0);<br />
my @head = @lines[0..5];<br />
foreach(@head){<br />
if(/_width\s+(\d+)/){$width = $1;}<br />
if(/_height\s+(\d+)/){$height = $1;}<br />
}<br />
t "width x height = $width x $height";<br />
my @k;<br />
foreach(@lines){ push @k, split /,/; }<br />
@k = grep { s/^.*(0x[0-9A-Fa-f]{1,2}).*$/$1/o; /(0x[0-9A-Fa-f]{1,2})/o } @k;<br />
#~ t d \@k;<br />
my $bc = scalar(@k);<br />
t "Pulled out $bc hex bytes";<br />
if($bc != $width * $height / 8) {<br />
die "byte count $bc does not match that expected for w x h";<br />
}<br />
t "OK - reorder bytes for MKe bitmap";<br />
my $wb = int($width/8) + (($width & 0x07) ? 1: 0);<br />
t "width in whole bytes for $width pixels = $wb";<br />
my @mke;<br />
for(my $col = 0; $col < $wb; $col++){<br />
for(my $row = $height - 1; $row >= 0; $row--){<br />
my $idx = ($row * $wb) + $col;<br />
my $val = $k[$idx];<br />
#~ t "Column $col + Row $row = idx $idx = $val";<br />
push @mke, $val;<br />
}<br />
}<br />
my $out = "static const uint8_t ".uc($name)."_BM[] = {\n"<br />
." $width, // width\n"<br />
." $height , // height\n";<br />
#~ $out .= join(", ", @mke);<br />
while(scalar @mke){<br />
$out .= join(", ", splice(@mke, 0, 16)).",\n";<br />
}<br />
$out .= "};\n";<br />
# meh, just print it out<br />
t $out;<br />
<br />
sub t(@) {<br />
foreach (@_) {<br />
print STDOUT "$_\n";<br />
}<br />
}<br />
sub d($) {<br />
require Data::Dumper;<br />
my $s = $_[0];<br />
my $d = Data::Dumper::Dumper($s);<br />
$d =~ s/^\$VAR1 =\s*//;<br />
$d =~ s/;$//;<br />
chomp $d;<br />
return $d;<br />
}<br />
sub chug($) {<br />
my $filename = shift;<br />
local *F;<br />
open F, "< $filename" or die "Couldn't open `$filename': $!";<br />
local $/ = undef;<br />
return <F>;<br />
} # F automatically closed<br />
<br />
</nowiki><br />
</div><br />
<br />
<span id=github></span><br />
<br />
= Source =<br />
<br />
All the source code and designs are on openly available on Github:<br />
<br />
* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design<br />
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant parts datasheets<br />
* [https://github.com/emfcamp/Mk2-Firmware Firmware] - source code for the badge software<br />
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network<br />
<br />
If you want to help, point your IRC client to #tilda on Freenode.<br />
<br />
= Firmware Documentation =<br />
== Debugging ==<br />
===Enabling the USB serial debug log messages===<br />
To enable the debug logging you must uncomment the following line in [https://github.com/emfcamp/Mk2-Firmware/blob/master/hardware/emfcamp/sam/libraries/debug/debug.h#L42 hardware/emfcamp/sam/libraries/debug/debug.h]<br />
<br />
// Enable debug task and output<br />
// #define DEBUG 1<br />
<br />
===Tilda::log(String text)===<br />
<br />
This logs “text” to the serial console. To read it connect to it via the Arduino IDE Serial Monitor. Don’t use “SerialUSB.println” or similar -- it’s not thread-safe and you might end up with utter nonsense.<br />
<br />
===Debugging using the JTAG interface===<br />
The JTAG interface on the board provides powerful debugging facilities like breakpoints, backtraces, dumping memory, inspecting variables, checking task states, catching exeptions etc. To make this to work requires additional hardware and software, see [[TiLDA Debugging using JTAG]].<br />
<br />
== Buttons ==<br />
The badge has 8 buttons: Up, Down, Left, Right, Center (on the joystick), A, B and Light. You can use arduino-style “digitalRead(BUTTON_RIGHT)” to read the current status of any button, but you can’t define your own interrupt (because we already did that). This doesn’t mean you can’t wait for a certain button to be pressed, it just means you have to approach it slightly differently:<br />
<br />
Example: A simple app displaying the button code<br />
void ButtonApp::task() {<br />
ButtonSubscription allButtons = Tilda::createButtonSubscription(LIGHT | A | B | UP | DOWN | LEFT | RIGHT | CENTER);<br />
<br />
while(true) {<br />
Button button = allButtons.waitForPress(1000);<br />
if (button == A) {<br />
debug::log(“You pressed button A”);<br />
} else if (button == LEFT) {<br />
debug::log(“You pressed LEFT”);<br />
} else if (button == NONE) {<br />
debug::log(“No button has been pressed in 1000ms”); <br />
}<br />
}<br />
}<br />
<br />
<br />
===ButtonSubscription Tilda::createButtonSubscription(<buttons>)===<br />
<br />
Registers a subscriptions for a defined set of buttons and returns a ButtonSubscription. Multiple Buttons can be combined via “|” (see example above). One button can not be subscribed by more than 10 subscriptions (which shouldn’t really happen, but keep it in mind). <br />
<br />
Don’t use this function in a constructor, it requires FreeRTOS to be running. Using it inside the task() function is the only safe place for it.<br />
<br />
===Button ButtonSubscription::waitForPress(TimeInTicks timeout)===<br />
<br />
This is normally called in a loop. It causes the task to block until one of the buttons has been pressed. If the timeout occurs before any button has been pressed “NONE” will be returned. <br />
<br />
===ButtonSubscription::waitForPress()===<br />
<br />
The same as above, but without the timeout.<br />
<br />
===ButtonSubscription::clear()===<br />
<br />
This should be called after an App has been suspended, just before it’s going to be resumed. It causes the Queue to be cleared which could otherwise lead to buttons being reported that have been pressed while other apps were in the foreground. Have a look at the FlashLightApp for an example.<br />
<br />
==LEDs==<br />
===Tilda::setLedColor(Led led, Color color);===<br />
===Tilde::setLedColor(Color color);===<br />
<br />
Sets the color of all or one led. Color is an object that takes red, green and blue as a value between 0 and 255 each. If no led is defined both leds will be set to the same color.<br />
<br />
Example: A simple color-changing task<br />
void ColorfulTask::task() {<br />
while(true) {<br />
Tilda::setLedColor(LED1, {255, 0, 0}); // Red<br />
Tilda::setLedColor(LED2, {0, 255, 0}); // Green<br />
Tilda::delay(300);<br />
Tilda::setLedColor(LED1, {0, 255, 0}); // Green<br />
Tilda::setLedColor(LED2, {0, 0, 255}); // Blue<br />
Tilda::delay(300);<br />
Tilda::setLedColor(LED1, {0, 0, 255}); // Blue<br />
Tilda::setLedColor(LED2, {255, 0, 0}); // Red<br />
Tilda::delay(300);<br />
}<br />
}<br />
<br />
==Display==<br />
<br />
The Display Library is based on GLCDv3 (http://playground.arduino.cc/Code/GLCDks0108), docs (http://code.google.com/p/glcd-arduino/source/browse/trunk/glcd/doc/GLCD_Documentation.pdf) but adapted to support our screen. The Init routine is called in the setup, and the LCDTask takes care of ensuring the screen is updated every 40ms if required (Unlike the original GLCD library, screen updates are decoupled from the graphics routines.)<br />
<br />
Also available is M2tklib (https://code.google.com/p/m2tklib/) which is a nice toolkit library. Further details on using this will come later, but expect the main loop to be handled for you, and just passing the menu structure you require for your app.<br />
<br />
Right now, you can call the GLCD functions directly with GLCD.DrawBitmap() for example. This is going to change to be accessed through the GUITask class in the near future, to ensure only one task at a time writes to the screen. Expect this to be simply GUITask in place of GLCD, along with a registering a redraw call back to GUITask. The bitmap format, by the way, is rather unconventional but there are a couple of utility scripts to convert popular formats down in the hacking section below - you can grab the SponsorsApp.h as an example and swap out the bitmap array with one of your choosing.<br />
<br />
Extra features that are included, GLCD.SetRotation() will handle rotation of the screen for you, and GLCD.CurrentWidth() and GLCD.CurrentHeight will give you the correct Width and Height for the current orientation. GLCD.Width and GLCD.Height constants are not available, and the GLCD predefined Text areas will not be rotated for you, if you require this define your own text areas.<br />
<br />
Note that one function was not ported to the badge version of GLCD, "Printf", you'll have to cope without it.<br />
<br />
== Sound == <br />
There's a fully working Piezo on board!<br />
<br />
== IMU ==<br />
=== Tilda::getOrientation ===<br />
returns " ORIENTATION_HELD", "ORIENTATION_RIGHT" (joystick to the right of the screen), "ORIENTATION_HUNG" or "ORIENTATION_LEFT"<br />
<br />
== Flash Storage ==<br />
We have 2mb of flash storage, but we're not using it in the main firmware - Please get this working!<br />
== Data: Schedule ==<br />
===Tilda::getDataStore().getSchedule(day, location) ===<br />
== Date: Weather Forecast ==<br />
===Tilda::getDataStore().getWeatherForecast()===<br />
== Radio ==<br />
There's no way of sending messages in the current version of the firmware, sorry :(<br />
<br />
== Time ==<br />
<br />
=== Tilda::delay(uint16_t delayInMs) === <br />
<br />
Works like Arduino’s delay(), but is FreeRTOS-safe. It’s safe to use this function before FreeRTOS has started.<br />
<br />
=== tilda::getClock() ===<br />
<br />
Returns an instance of https://github.com/MarkusLange/Arduino-Due-RTC-Library/blob/master/rtc_clock.h<br />
<br />
==Settings==<br />
===uint16_t tilda::getBadgeId()===<br />
<br />
<br />
==Battery==<br />
===float TiLDA::getBatteryVoltage()===<br />
Returns the current voltage as a float<br />
<br />
===uint8_t TiLDA::getBatteryPercent()===<br />
Returns the current voltage as a percentage<br />
<br />
===uint8_t TiLDA::getChargeState()===<br />
Returns the charge state<br />
<br />
0 Charging<br />
1 Not Charging<br />
<br />
[[Category: Badges]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=TiLDA_MKe&diff=3818TiLDA MKe2014-12-09T15:01:13Z<p>Ms7821: /* Debugging and Gotchas */</p>
<hr />
<div>[[File:IMG_0474.jpg|500px|right|thumb|Front]]<br />
[[File:Badge_Front.png|right|thumb|Front]]<br />
<br />
[http://en.wikipedia.org/wiki/E_(mathematical_constant) Why MKe?]<br />
<br />
=EMF 2014 Badge= <br />
The main aim of the 2014 badge is to give camp attendees an interesting bit of hardware to play with during the camp and experiment with afterwards. We designed an Arduino compatible platform to allow easy reuse and access, and have published all code and design files.<br />
<br />
==Battery Warning==<br />
A very last minute battery (and connector) change on the badge due to a supplier problem meant two issues arose with the badge during EMF:<br />
<br />
* '''Always make sure to plug your battery in the right way round!''' The new battery connector allows you to connect it backwards. We did our best to mitigate this, but connecting it incorrectly will destroy the power management controller and prevent the badge from charging or running from the battery. It will still function perfectly using USB power. "Red" and "Black" are written next to the connector - please make sure to plug it in correctly.<br />
<br />
* '''Be careful not to short the battery connector wires!''' The new battery connector slightly exposes the wires when the battery is plugged in. If a metal object shorts the two wires, it can result in extreme battery damage. If we'd known this was such an issue before the event we would have applied protective material to it - we suggest covering the exposed connector in tape, sugru, blu-tack, or some other insulating material. Alternatively, simply unplug the battery when your badge is not in use!<br />
<br />
==My badge is broken!==<br />
Due to the aforementioned supplier issues it is possible that you may have received a faulty badge, or it may have been damaged by connecting the battery backwards. If you badge will not turn on when it has been plugged in with a MicroUSB cable (and the power switch on the back is set to "USB"), or something else seems wrong with it, please email [mailto:badge@emfcamp.org badge@emfcamp.org] and we'll try to fix or replace your badge.<br />
<br />
==Basic post-event features==<br />
We made sure that the badge has a few features to play with once the event is over. More will be added over time as attendees submit changes to us.<br />
<br />
[[File:Badge_Back.png|right|thumb|Back]]<br />
* Torch mode - Press the light button next to the screen. It will only light up fully if it's hung upside down to avoid blinding<br />
* Snake<br />
* Tetris<br />
<br />
But of course the point of the badge is to modify it and use it for other interesting things! The following sections describe how to update the firmware on the badge, how to use it as a simple arduino, and how to write your own code for the main badge firmware.<br />
<br />
==Getting help==<br />
The EMF 2014 badge is a complex piece of hardware and software, however remember that you can just treat it as an Arduino if you find it all too daunting.<br />
<br />
If you get stuck and need advice, there's an [http://webchat.freenode.net/?channels=tilda active IRC chatroom] you can join to ask for advice, or if you're really stuck you can email us on [mailto:badge@emfcamp.org badge@emfcamp.org].<br />
<br />
=How to update the badge software & program the badge=<br />
The badge software has been substantially updated since EMF, fixing bugs and removing features that will no longer work now you're away from our radio network. You should update your badge before starting to play with it any further. If you've never used an Arduino before this might be tricky - ask an Arduino-literate friend to help you, or drop by your nearest [http://hackspace.org.uk hackspace] and ask for advice.<br />
<br />
The badge is Arudino Due compatible, so [http://arduino.cc/en/Guide/ArduinoDue some of their instructions may help you if you have problems].<br />
<br />
==Set up your environment==<br />
* Plug your badge into your computer via a MicroUSB cable. Make sure the power switch on the back is set to "USB".<br />
* Download Arduino IDE 1.5.7 from http://arduino.cc/en/main/software#toc3<br />
* Download the TiLDA firmware code from https://github.com/emfcamp/Mk2-Firmware<br />
* Start the Arduino IDE.<br />
* Now you have to change the sketchbook-folder to be the folder you just cloned or downloaded. To do this use File -> Preferences -> “Set Sketchbook location”. On MacOS, this is Arduino -> Preferences. <br />
* Restart the Arduino IDE.<br />
* Open sketch “EMF2014”.<br />
* Set Tools -> Board to MKe v0.333 (RTOS Core).<br />
* Set Tools -> Port to correct port for the Arduino<br />
** On MacOS this is will start /dev/tty.usbmodem with 4 digits, and change for each port<br />
** On Linux this is usually /dev/ttyACM0 but may be a higher number if you have other USB Serial devices<br />
* Hit the upload button<br />
* Wait<br />
* Your badge should now be running the latest TiLDA firmware!<br />
<br />
==Programming the badge as an Arduino==<br />
The badge is completely Arduino Due compatible, simply set the board type to "MKe v0.333(Arduino Core)" upload normal Arduino code and the badge will function. However if you want to use any of the more complex hardware on the badge (such as the screen and radio) we recommend programming it using our FreeRTOS framework documented below.<br />
<br />
Below is a version of the standard blink sketch that will flash the RX and TX LEDs<br />
<br />
<code><br />
void setup() {<br />
pinMode(PIN_LED_TX, OUTPUT);<br />
pinMode(PIN_LED_RX, OUTPUT);<br />
}<br />
<br />
void loop() {<br />
digitalWrite(PIN_LED_TX, HIGH);<br />
digitalWrite(PIN_LED_RX, LOW);<br />
delay(1000);<br />
digitalWrite(PIN_LED_TX, LOW);<br />
digitalWrite(PIN_LED_RX, HIGH);<br />
delay(1000);<br />
}<br />
</code><br />
<br />
If you do program the badge with simple Arduino code but wish to switch back to our official firmware, simply change the sketch to "EMF2014" (and if needed set the board type back to "MKe v0.333 (RTOS Core)") and upload again.<br />
<br />
To make the badge Arduino shield compatible, follow [https://wiki.emfcamp.org/wiki/TiLDA_MKe#Making_the_badge_Arduino_shield_compatible these instructions].<br />
<br />
==Programming the badge in FreeRTOS==<br />
===Your first “Hello world” app===<br />
There’s a “HelloWorldApp.cpp” file in which you can play around. In order for it to show up on the Homescreen you have to uncomment line 51 in AppManager.cpp and flash the changed code to the badge. Great app pull requests are appreciated!<br />
<br />
If you are still using the Arduino IDE at this point, note that it will not let you edit the .cpp and .h files that are needed to create Apps for the badge. To force the IDE to re-compile/re-read any files you've edited using an external editor, make sure to go to the File -> Preferences dialog box, and check the "Use external editor" checkbox.<br />
<br />
===Why are things so different from standard Arduino code?===<br />
We’re using a library called FreeRTOS that allows us to multitask - something that’s normally not possible with standard Arduino code. This allows us to run multiple tasks at the same time. FreeRTOS uses preemptive scheduling to switch between the task. Due to this we have to be very careful about how we do some things. For example we can’t just define interrupts for buttons in every task (imagine the mess!) or write to the serial port directly (your task might stop in the middle of the message). <br />
<br />
We’ve also spent quite a lot of time to make the built-in components as easy to use as possible without having every task to write lots of boilerplate code. If you feel like using the build-in components on the badge, chances are we already wrote a wrapper for them that is already used by one of the other tasks. <br />
<br />
Have a look at the “Documentation” section in this document for a full list of API functions. You will avoid a lot of headaches if you stick to those.<br />
<br />
=== Code structure ===<br />
* FreeRTOS has the concept of “Tasks” which work like threads. We’ve wrappered them in a class called “Task” (for background stuff) and “Apps” (for foreground, one-at-a-time things)<br />
* Everything needs to be in the main EMF2014 folder. Subfolders are not allowed. This is an Arduino IDE restriction :(<br />
<br />
==Debugging and Gotchas==<br />
* The USB serial is set up to 115200 baud. There are lots of terminals that can connect to them. See below for how to enable the debug logging.<br />
* If you can’t revive a badge, or only get the two RED programming LEDs when you plug it, in, do a full erase (see below)<br />
* Avoid busy waiting, use FreeRTOS queues and Tilda::delay() instead<br />
* Don’t use low level functions like interrupts or serial ports directly unless you really, really know how FreeRTOS will handle them. For general logging you can use Tilda::log()<br />
* If sending code to the badge using the Arduino IDE "Upload" button fails, even though the /dev/ttyACM0 (linux com port) is there, just retry, twice if neccessary.<br />
<br />
<br />
==Full erase==<br />
This is the failsafe process if your badge won't show up over USB.<br />
<br />
# Unplug the badge<br />
# Connect the Erase pins on the back together (two holes down the left hand side next to the battery and under the blue wireless module). You can use a jumper, jump wire, or the leg of a resistor for this.<br />
# Turn the badge back on with the switch or plug it back in<br />
# Press the Reset button on the front (bottom centre) and release<br />
# Wait 15 seconds<br />
# Unplug the badge or turn it off<br />
<br />
When you plug the badge back into a computer it will come back up in programming mode, with a different serial port to the usual one. Open the EMF 2014 sketch in the Arduino IDE, select the Tilda v0.333 (RTOS) programmer, and find the new serial port. The IDE console should show something like this:<br />
<br />
Sketch uses 118,748 bytes (22%) of program storage space. Maximum is 524,288 bytes.<br />
Erase flash<br />
Write 127668 bytes to flash<br />
<br />
[ ] 0% (0/499 pages)<br />
[ ] 2% (10/499 pages)<br />
[= ] 4% (20/499 pages)<br />
[= ] 6% (30/499 pages)<br />
...<br />
[============================= ] 98% (490/499 pages)<br />
[==============================] 100% (499/499 pages)<br />
Verify 127668 bytes of flash<br />
<br />
[ ] 0% (0/499 pages)<br />
[ ] 2% (10/499 pages)<br />
[= ] 4% (20/499 pages)<br />
[= ] 6% (30/499 pages)<br />
...<br />
[============================= ] 98% (490/499 pages)<br />
[==============================] 100% (499/499 pages)<br />
Verify successful<br />
Set boot flash true<br />
CPU reset.<br />
<br />
==Your own wireless badge network==<br />
[[DIY TiLDA Badge Network]] has instructions on how to setup your own private badge network using a RaspberryPi and two Ciseco radios.<br />
<br />
==Contribute==<br />
Send us a pull request via [https://github.com/emfcamp/Mk2-Firmware GitHub] - We’ll do our best to review and merge the good ones during EMF so others can use them.<br />
<br />
=Using the badge hardware=<br />
The badge has a plethora of hardware built in for you to play with, everything from accelerometers and gyroscopes to hidden ethernet headers! Breaking it all down is too much detail for this document, however we'll call out some things we built in that you might want to play with.<br />
<br />
Remember the badge is Arduino Due compatible, and we broke out nearly all the features of the ARM chip so you can access them. [http://arduino.cc/en/Main/ArduinoBoardDue Anything the Due can do], the TiLDA can do!<br />
<br />
==Making the badge Arduino shield compatible==<br />
[[File:Sheild_Headers.JPG|500px|right|thumb|Sheild Headers]]<br />
To make the badge Arduino shield compatible you'll need to solder simple strips of header pins onto the back of the badge. <br />
You need the following headers<br />
{| class="wikitable"<br />
|-<br />
! Qty !! Type !! Use !! Rapid part<br />
|-<br />
| 1 || 2x03 Male || SPI ||<br />
|-<br />
| 2 || 1x08 Female || Power, Analog pins ||<br />
|-<br />
| 2 || 1x10 Female || Digital pins ||<br />
|-<br />
| 1 || 2x08 Male || Ethernet ||<br />
|}<br />
The picture to the right shows the placement.<br />
<br />
==Interesting things to play with==<br />
Most of the interesting things are on the back of the badge. They're clearly marked in white. [https://wiki.emfcamp.org/w/images/b/bd/Badge_Back.png This diagram of the back] should allow you to locate them. Some of the following require extra parts to be added to your badge.<br />
<br />
* Full Arduino R3 shield compatible pins (Requires soldering the headers on the back of the badge)<br />
* Pins either side of the lanyard holes for conductive thread (D19, D18, GND, 3V3)<br />
* Infrared transmitter on the front (Pin shortcut IR_TX_PWM)<br />
* Infrared receiver on the front (Pin shortcut IR_RX, Part Vishay TSOP75238TT available from digikey and Farnell )<br />
* Piezo buzzer (Pin shortcut PIEZO or PIEZO_PWM)<br />
* On-board ethernet (not available on the Due) - requires breakout module (eBay: Elechouse Taijiuino Ethernet PHY DM9161 Module)<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro (IMUTask.cpp and the MPU6050 library)<br />
* 128x64 pixel backlit LCD display (JHD12864, see [https://github.com/emfcamp/Mk2-Documentation/tree/master/LCD%20JHD12864 here for docs])<br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
* [http://shop.ciseco.co.uk/powerpod-ncp1402-5v0/ PowerPOD NCP1402] interface, used to generate 5V from 3V3 battery supply power (needed for some shields)<br />
* MicroSD adapter breakout (Molex 1050270001 available from digikey)<br />
* Compass (magnetometer) breakout (HMC HMC5883L-TR available from digikey and Farnell)<br />
* Reprogramming headers for the 868Mhz [http://www.ti.com/product/cc1110f32 CC1110 radio module]<br />
* 1 megabit flash module (Part S25FL216K0PMFI011)<br />
* SPI breakout<br />
* 2x RGB LEDs on the front <br />
* FTDI header (shared with SRF Radio)<br />
* JTAG header (Part M50-3500542 available form Farnell<br />
<br />
==Included hardware==<br />
<br />
The following hardware has been included on the badge.<br />
<br />
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]<br />
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge<br />
** 32bit ARM Cortex M3 * 84MHz<br />
** 512KBytes Flash RAM<br />
** 96KBytes of SRAM<br />
* A 128x64 pixel monochrome LCD display<br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
** 868Mhz RF Transceiver<br />
** Simple UART interface<br />
** Low power sleep mode<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro<br />
** I2C interface<br />
** Tri-Axis angular rate sensor (gyro) with a sensitivity up to 131 LSBs/dps and a full-scale range of ±250, ±500, ±1000, and ±2000dps<br />
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g<br />
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronisation and gesture detection<br />
* PMIC & LiPo<br />
* Joystick, 4 way with click<br />
* Buttons<br />
* RGB LEDs<br />
* IR Transmitter<br />
* Arduino Headers<br />
* Pads for wearable tech<br />
<br />
=Useful Hacks!=<br />
==3d printable & laser-cuttable badge case==<br />
Draft 3d print-able and laser-able case files [http://www.thingiverse.com/thing:436815 here]<br />
==Convert images to TiLDA bitmap format==<br />
* A Python script (via [https://twitter.com/trotmaster99 @trotmaster99]) that converts a monochrome bitmap image into a format suitable for the Tilda can be found [http://pastebin.com/8XeazQjT here].<br />
* A similar script in Perl to create TiLDA MKe fullscreen bitmaps from XBM: -<br />
<div style ="height:200px;overflow-x:hidden;overflow-y:auto;border: 4px solid orange;"><br />
'''xbm2mke.pl by [[User:Msemtd]]'''<br />
<nowiki><br />
#!perl -w<br />
use strict;<br />
# Little script to convert a regular XBM to TiLDA MKe bitmap<br />
# only tested with fullscreen bitmaps!<br />
# Hot file handle magic...<br />
select((select(STDERR), $| = 1)[0]);<br />
select((select(STDOUT), $| = 1)[0]);<br />
sub t(@);<br />
sub d($);<br />
sub chug($);<br />
my $f = shift;<br />
#~ $f = 'blankish.xbm' if not $f;<br />
if(not defined $f or not $f =~ /^(.*)\.xbm$/i){<br />
die "Usage: gimme an XBM file dude!\n";<br />
}<br />
my $name = $1;<br />
t "Reading file '$f'...";<br />
my $data = chug($f);<br />
t "OK";<br />
my @lines = split /^/, $data;<br />
@lines = grep{chomp; s/^\s+//; s/\s+$//; length;} @lines;<br />
#~ t d \@lines;<br />
my($width, $height) = (0,0);<br />
my @head = @lines[0..5];<br />
foreach(@head){<br />
if(/_width\s+(\d+)/){$width = $1;}<br />
if(/_height\s+(\d+)/){$height = $1;}<br />
}<br />
t "width x height = $width x $height";<br />
my @k;<br />
foreach(@lines){ push @k, split /,/; }<br />
@k = grep { s/^.*(0x[0-9A-Fa-f]{1,2}).*$/$1/o; /(0x[0-9A-Fa-f]{1,2})/o } @k;<br />
#~ t d \@k;<br />
my $bc = scalar(@k);<br />
t "Pulled out $bc hex bytes";<br />
if($bc != $width * $height / 8) {<br />
die "byte count $bc does not match that expected for w x h";<br />
}<br />
t "OK - reorder bytes for MKe bitmap";<br />
my $wb = int($width/8) + (($width & 0x07) ? 1: 0);<br />
t "width in whole bytes for $width pixels = $wb";<br />
my @mke;<br />
for(my $col = 0; $col < $wb; $col++){<br />
for(my $row = $height - 1; $row >= 0; $row--){<br />
my $idx = ($row * $wb) + $col;<br />
my $val = $k[$idx];<br />
#~ t "Column $col + Row $row = idx $idx = $val";<br />
push @mke, $val;<br />
}<br />
}<br />
my $out = "static const uint8_t ".uc($name)."_BM[] = {\n"<br />
." $width, // width\n"<br />
." $height , // height\n";<br />
#~ $out .= join(", ", @mke);<br />
while(scalar @mke){<br />
$out .= join(", ", splice(@mke, 0, 16)).",\n";<br />
}<br />
$out .= "};\n";<br />
# meh, just print it out<br />
t $out;<br />
<br />
sub t(@) {<br />
foreach (@_) {<br />
print STDOUT "$_\n";<br />
}<br />
}<br />
sub d($) {<br />
require Data::Dumper;<br />
my $s = $_[0];<br />
my $d = Data::Dumper::Dumper($s);<br />
$d =~ s/^\$VAR1 =\s*//;<br />
$d =~ s/;$//;<br />
chomp $d;<br />
return $d;<br />
}<br />
sub chug($) {<br />
my $filename = shift;<br />
local *F;<br />
open F, "< $filename" or die "Couldn't open `$filename': $!";<br />
local $/ = undef;<br />
return <F>;<br />
} # F automatically closed<br />
<br />
</nowiki><br />
</div><br />
<br />
<span id=github></span><br />
<br />
= Source =<br />
<br />
All the source code and designs are on openly available on Github:<br />
<br />
* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design<br />
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant parts datasheets<br />
* [https://github.com/emfcamp/Mk2-Firmware Firmware] - source code for the badge software<br />
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network<br />
<br />
If you want to help, point your IRC client to #tilda on Freenode.<br />
<br />
= Firmware Documentation =<br />
== Debugging ==<br />
===Enabling the USB serial debug log messages===<br />
To enable the debug logging you must uncomment the following line in [https://github.com/emfcamp/Mk2-Firmware/blob/master/hardware/emfcamp/sam/libraries/debug/debug.h#L42 hardware/emfcamp/sam/libraries/debug/debug.h]<br />
<br />
// Enable debug task and output<br />
// #define DEBUG 1<br />
<br />
===Tilda::log(String text)===<br />
<br />
This logs “text” to the serial console. To read it connect to it via the Arduino IDE Serial Monitor. Don’t use “SerialUSB.println” or similar -- it’s not thread-safe and you might end up with utter nonsense.<br />
<br />
===Debugging using the JTAG interface===<br />
The JTAG interface on the board provides powerful debugging facilities like breakpoints, backtraces, dumping memory, inspecting variables, checking task states, catching exeptions etc. To make this to work requires additional hardware and software, see [[TiLDA Debugging using JTAG]].<br />
<br />
== Buttons ==<br />
The badge has 8 buttons: Up, Down, Left, Right, Center (on the joystick), A, B and Light. You can use arduino-style “digitalRead(BUTTON_RIGHT)” to read the current status of any button, but you can’t define your own interrupt (because we already did that). This doesn’t mean you can’t wait for a certain button to be pressed, it just means you have to approach it slightly differently:<br />
<br />
Example: A simple app displaying the button code<br />
void ButtonApp::task() {<br />
ButtonSubscription allButtons = Tilda::createButtonSubscription(LIGHT | A | B | UP | DOWN | LEFT | RIGHT | CENTER);<br />
<br />
while(true) {<br />
Button button = allButtons.waitForPress(1000);<br />
if (button == A) {<br />
debug::log(“You pressed button A”);<br />
} else if (button == LEFT) {<br />
debug::log(“You pressed LEFT”);<br />
} else if (button == NONE) {<br />
debug::log(“No button has been pressed in 1000ms”); <br />
}<br />
}<br />
}<br />
<br />
<br />
===ButtonSubscription Tilda::createButtonSubscription(<buttons>)===<br />
<br />
Registers a subscriptions for a defined set of buttons and returns a ButtonSubscription. Multiple Buttons can be combined via “|” (see example above). One button can not be subscribed by more than 10 subscriptions (which shouldn’t really happen, but keep it in mind). <br />
<br />
Don’t use this function in a constructor, it requires FreeRTOS to be running. Using it inside the task() function is the only safe place for it.<br />
<br />
===Button ButtonSubscription::waitForPress(TimeInTicks timeout)===<br />
<br />
This is normally called in a loop. It causes the task to block until one of the buttons has been pressed. If the timeout occurs before any button has been pressed “NONE” will be returned. <br />
<br />
===ButtonSubscription::waitForPress()===<br />
<br />
The same as above, but without the timeout.<br />
<br />
===ButtonSubscription::clear()===<br />
<br />
This should be called after an App has been suspended, just before it’s going to be resumed. It causes the Queue to be cleared which could otherwise lead to buttons being reported that have been pressed while other apps were in the foreground. Have a look at the FlashLightApp for an example.<br />
<br />
==LEDs==<br />
===Tilda::setLedColor(Led led, Color color);===<br />
===Tilde::setLedColor(Color color);===<br />
<br />
Sets the color of all or one led. Color is an object that takes red, green and blue as a value between 0 and 255 each. If no led is defined both leds will be set to the same color.<br />
<br />
Example: A simple color-changing task<br />
void ColorfulTask::task() {<br />
while(true) {<br />
Tilda::setLedColor(LED1, {255, 0, 0}); // Red<br />
Tilda::setLedColor(LED2, {0, 255, 0}); // Green<br />
Tilda::delay(300);<br />
Tilda::setLedColor(LED1, {0, 255, 0}); // Green<br />
Tilda::setLedColor(LED2, {0, 0, 255}); // Blue<br />
Tilda::delay(300);<br />
Tilda::setLedColor(LED1, {0, 0, 255}); // Blue<br />
Tilda::setLedColor(LED2, {255, 0, 0}); // Red<br />
Tilda::delay(300);<br />
}<br />
}<br />
<br />
==Display==<br />
<br />
The Display Library is based on GLCDv3 (http://playground.arduino.cc/Code/GLCDks0108), docs (http://code.google.com/p/glcd-arduino/source/browse/trunk/glcd/doc/GLCD_Documentation.pdf) but adapted to support our screen. The Init routine is called in the setup, and the LCDTask takes care of ensuring the screen is updated every 40ms if required (Unlike the original GLCD library, screen updates are decoupled from the graphics routines.)<br />
<br />
Also available is M2tklib (https://code.google.com/p/m2tklib/) which is a nice toolkit library. Further details on using this will come later, but expect the main loop to be handled for you, and just passing the menu structure you require for your app.<br />
<br />
Right now, you can call the GLCD functions directly with GLCD.DrawBitmap() for example. This is going to change to be accessed through the GUITask class in the near future, to ensure only one task at a time writes to the screen. Expect this to be simply GUITask in place of GLCD, along with a registering a redraw call back to GUITask. The bitmap format, by the way, is rather unconventional but there are a couple of utility scripts to convert popular formats down in the hacking section below - you can grab the SponsorsApp.h as an example and swap out the bitmap array with one of your choosing.<br />
<br />
Extra features that are included, GLCD.SetRotation() will handle rotation of the screen for you, and GLCD.CurrentWidth() and GLCD.CurrentHeight will give you the correct Width and Height for the current orientation. GLCD.Width and GLCD.Height constants are not available, and the GLCD predefined Text areas will not be rotated for you, if you require this define your own text areas.<br />
<br />
Note that one function was not ported to the badge version of GLCD, "Printf", you'll have to cope without it.<br />
<br />
== Sound == <br />
There's a fully working Piezo on board!<br />
<br />
== IMU ==<br />
=== Tilda::getOrientation ===<br />
returns " ORIENTATION_HELD", "ORIENTATION_RIGHT" (joystick to the right of the screen), "ORIENTATION_HUNG" or "ORIENTATION_LEFT"<br />
<br />
== Flash Storage ==<br />
We have 2mb of flash storage, but we're not using it in the main firmware - Please get this working!<br />
== Data: Schedule ==<br />
===Tilda::getDataStore().getSchedule(day, location) ===<br />
== Date: Weather Forecast ==<br />
===Tilda::getDataStore().getWeatherForecast()===<br />
== Radio ==<br />
There's no way of sending messages in the current version of the firmware, sorry :(<br />
<br />
== Time ==<br />
<br />
=== Tilda::delay(uint16_t delayInMs) === <br />
<br />
Works like Arduino’s delay(), but is FreeRTOS-safe. It’s safe to use this function before FreeRTOS has started.<br />
<br />
=== tilda::getClock() ===<br />
<br />
Returns an instance of https://github.com/MarkusLange/Arduino-Due-RTC-Library/blob/master/rtc_clock.h<br />
<br />
==Settings==<br />
===uint16_t tilda::getBadgeId()===<br />
<br />
<br />
==Battery==<br />
===float TiLDA::getBatteryVoltage()===<br />
Returns the current voltage as a float<br />
<br />
===uint8_t TiLDA::getBatteryPercent()===<br />
Returns the current voltage as a percentage<br />
<br />
===uint8_t TiLDA::getChargeState()===<br />
Returns the charge state<br />
<br />
0 Charging<br />
1 Not Charging<br />
<br />
[[Category: Badges]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=TiLDA_MKe&diff=3704TiLDA MKe2014-09-14T22:59:12Z<p>Ms7821: </p>
<hr />
<div>The TiLDA MKe project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Dpslwk|'RepRap' Matt]] and [[User:thinkl33t|Bob]]<br />
[[File:IMG_0474.jpg|500px|right|thumb|Front]]<br />
[[File:Badge_Front.png|right|thumb|Front]]<br />
<br />
[http://en.wikipedia.org/wiki/E_(mathematical_constant) Why MKe?]<br />
<br />
Please Note: There are a couple of minor hardware and some firmware issues that might be effecting your badge. If you've let the magic smoke out of your charge controller or have tried to re-flash and ended up with nothing but a couple of dimly glowing lights then DO NOT DESPAIR -It's recoverable and fixes, documentation and lots of firmware are still being produced :)<br />
<br />
=Aim= <br />
The main aim of the 2014 badge is to give camp attendees live schedule updates and notifications. As with the original TiLDA we wanted to keep with an Arduino compatible platform that will allow badge hacking during and after the camp. As with the previous badge all code and design files are available.<br />
<br />
==Battery Warning==<br />
'''Always make sure you plug your battery in the right way round!''' If you don't, the charge controller will let out its magic smoke and die / become damaged and die later. The badge itself will still work, but it wont have the ability to charge anymore. <br />
<br />
We think this is the cause of the charge controller issues a small number of badges had at the event was due to this mistake being made during final assembly on-site. <br />
<br />
'''Lithium Batteries are dangerous!''' While these batteries are better protected than the MK1 batteries, they are still scary. Do not short your battery, and if it starts bulging or gets punctured, '''DO NOT USE IT AGAIN''' and dispose of it properly.<br />
<br />
==Features and Functions==<br />
[[File:Badge_Back.png|right|thumb|Back]]<br />
* Torch mode - Press the light button next to the screen. It will only light up fully if it's hung upside down to avoid blinding<br />
* Snake<br />
* Tetris<br />
<br />
'''Please note that there's a known issue with the badge freezing'''. We're trying to work out what's causing this, but in the meantime pressing "reset" should get the badge back to life. Help with debugging is highly welcome!<br />
<br />
== How to get going ==<br />
=== Set up your environment ===<br />
* Plug your badge into your computer via USB<br />
* Download Arduino IDE 1.5.7 from http://arduino.cc/en/main/software#toc3<br />
* “git clone” or download TiLDA source code from https://github.com/emfcamp/Mk2-Firmware<br />
* Start the Arduino IDE. <br />
* Now you have to change the sketchbook-folder to be the folder you just cloned. To do this use File | Preferences | “Set Sketchbook location”. On MacOS, this is Arduino | Preferences <br />
* Restart the Arduino IDE<br />
* Open sketch “EMF2014”<br />
* Set Tools | Board to MKe v0.333 (RTOS Core)<br />
* Set Tools | Port to correct port (you might have to research this - some operating systems like Windows require you to install drivers or become a member of a certain group)<br />
** On MacOS this is will start /dev/tty.usbmodem with 4 digits, and change for each port<br />
** On Linux this is usually /dev/ttyACM0 but may be a higher number if you have other USB Serial devices<br />
* Hit the upload button<br />
* Wait<br />
* Woohoo - You just successfully uploaded code to your badge<br />
<br />
=== Your first “Hello world” app ===<br />
There’s a “HelloWorldApp.cpp” file in which you can play around. In order for it to show up on the Homescreen you have to uncomment line 51 in AppManager.cpp and flash the changed code to the badge. Great app pull requests are appreciated!<br />
<br />
If you are still using the Arduino IDE at this point, note that it will not let you edit the .cpp and .h files that are needed to create Apps for the badge. To force the IDE to re-compile/re-read any files you've edited using an external editor, make sure to go to the File -> Preferences dialog box, and check the "Use external editor" checkbox.<br />
<br />
=== Why are things so different from standard Arduino code? ===<br />
We’re using a library called FreeRTOS that allows us to multitask - something that’s normally not possible with standard Arduino code. This allows us to run multiple tasks at the same time. FreeRTOS uses preemptive scheduling to switch between the task. Due to this we have to be very careful about how we do some things. For example we can’t just define interrupts for buttons in every task (imagine the mess!) or write to the serial port directly (your task might stop in the middle of the message). <br />
<br />
We’ve also spend quite a lot of time to make the build-in components as easy to use as possible without having every task to write lots of boilerplate code. If you feel like using the build-in components on the badge, chances are we already wrote a wrapper for them that is already used by one of the other tasks. <br />
<br />
Have a look at the “Documentation” section in this document for a full list of API functions. You will avoid a lot of headaches if you stick to those.<br />
=== How to use the badge with pure Arduino code ===<br />
If you prefer you can always start from scratch without FreeRTOS or any of our code, just keep in mind that you won’t be able to receive messages via radio or use any of the API features we already added. Just start a new sketch in the Arduino IDE for that and get going. If you want to load the main firmware again just change the sketch to “EMF2014” and upload again.<br />
=== Debugging and Gotchas ===<br />
* The USB serial is set up to 115220 baud. There are lots of terminals that can connect to them<br />
* If you can’t revive a badge you can short the two erase pins and press the reset button while holding it down.<br />
* Avoid busy waiting, use FreeRTOS queues and Tilda::delay() instead<br />
* Don’t use low level functions like interrupts or serial ports directly unless you really, really know how FreeRTOS will handle them. For general logging you can use Tilda::log()<br />
* If sending code to the badge using the Arduino IDE "Upload" button fails, even though the /dev/ttyACM0 (linux com port) is there, just retry, twice if neccessary.<br />
<br />
=== Code structure ===<br />
* FreeRTOS has the concept of “Tasks” which work like threads. We’ve wrappered them in a class called “Task” (for background stuff) and “Apps” (for foreground, one-at-a-time things)<br />
* Everything needs to be in the main EMF2014 folder. Subfolders are not allowed. This is an Arduino IDE restriction :(<br />
=== Radio infrastructure ===<br />
The radio infrastructure is distributed between DKs. Every “gateway” has a Raspberry Pi with two Ciseco USB radios. We never had the chance to actually try it with a large number of badges in the same spot, so please don’t expect it to work perfectly.<br />
<br />
=== Contribute ===<br />
Send us a pull request via [https://github.com/emfcamp/Mk2-Firmware GitHub] - We’ll do our best to review and merge the good ones during EMF so others can use them.<br />
<br />
=Hardware=<br />
<br />
The following hardware has been included on the badge.<br />
<br />
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]<br />
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge<br />
** 32bit ARM Cortex M3 * 84MHz<br />
** 512KBytes Flash RAM<br />
** 96KBytes of SRAM<br />
* A 128x64 pixel monochrome LCD display<br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
** 868Mhz RF Transceiver<br />
** Simple UART interface<br />
** Low power sleep mode<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro<br />
** I2C interface<br />
** Tri-Axis angular rate sensor (gyro) with a sensitivity up to 131 LSBs/dps and a full-scale range of ±250, ±500, ±1000, and ±2000dps<br />
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g<br />
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronisation and gesture detection<br />
* PMIC & LiPo<br />
* Joystick<br />
* Buttons<br />
* RGB LEDs<br />
* IR<br />
* Arduino Headers<br />
* Pads for wearable tech<br />
<br />
= Firmware Documentation =<br />
== Debugging ==<br />
===Tilda::log(String text)===<br />
<br />
This logs “text” to the serial console. To read it connect to it via the Arduino IDE Serial Monitor. Don’t use “SerialUSB.println” or similar -- it’s not thread-safe and you might end up with utter nonsense.<br />
== Buttons ==<br />
The badge has 8 buttons: Up, Down, Left, Right, Center (on the joystick), A, B and Light. You can use arduino-style “digitalRead(BUTTON_RIGHT)” to read the current status of any button, but you can’t define your own interrupt (because we already did that). This doesn’t mean you can’t wait for a certain button to be pressed, it just means you have to approach it slightly differently:<br />
<br />
Example: A simple app displaying the button code<br />
void ButtonApp::task() {<br />
ButtonSubscription allButtons = Tilda::createButtonSubscription(LIGHT | A | B | UP | DOWN | LEFT | RIGHT | CENTER);<br />
<br />
while(true) {<br />
Button button = allButtons.waitForPress(1000);<br />
if (button == A) {<br />
debug::log(“You pressed button A”);<br />
} else if (button == LEFT) {<br />
debug::log(“You pressed LEFT”);<br />
} else if (button == NONE) {<br />
debug::log(“No button has been pressed in 1000ms”); <br />
}<br />
}<br />
}<br />
<br />
<br />
===ButtonSubscription Tilda::createButtonSubscription(<buttons>)===<br />
<br />
Registers a subscriptions for a defined set of buttons and returns a ButtonSubscription. Multiple Buttons can be combined via “|” (see example above). One button can not be subscribed by more than 10 subscriptions (which shouldn’t really happen, but keep it in mind). <br />
<br />
Don’t use this function in a constructor, it requires FreeRTOS to be running. Using it inside the task() function is the only safe place for it.<br />
<br />
===Button ButtonSubscription::waitForPress(TimeInTicks timeout)===<br />
<br />
This is normally called in a loop. It causes the task to block until one of the buttons has been pressed. If the timeout occurs before any button has been pressed “NONE” will be returned. <br />
<br />
===ButtonSubscription::waitForPress()===<br />
<br />
The same as above, but without the timeout.<br />
<br />
===ButtonSubscription::clear()===<br />
<br />
This should be called after an App has been suspended, just before it’s going to be resumed. It causes the Queue to be cleared which could otherwise lead to buttons being reported that have been pressed while other apps were in the foreground. Have a look at the FlashLightApp for an example.<br />
<br />
==LEDs==<br />
===Tilda::setLedColor(Led led, Color color);===<br />
===Tilde::setLedColor(Color color);===<br />
<br />
Sets the color of all or one led. Color is an object that takes red, green and blue as a value between 0 and 255 each. If no led is defined both leds will be set to the same color.<br />
<br />
Example: A simple color-changing task<br />
void ColorfulTask::task() {<br />
while(true) {<br />
Tilda::setLedColor(LED1, {255, 0, 0}); // Red<br />
Tilda::setLedColor(LED2, {0, 255, 0}); // Green<br />
Tilda::delay(300);<br />
Tilda::setLedColor(LED1, {0, 255, 0}); // Green<br />
Tilda::setLedColor(LED2, {0, 0, 255}); // Blue<br />
Tilda::delay(300);<br />
Tilda::setLedColor(LED1, {0, 0, 255}); // Blue<br />
Tilda::setLedColor(LED2, {255, 0, 0}); // Red<br />
Tilda::delay(300);<br />
}<br />
}<br />
<br />
==Display==<br />
<br />
The Display Library is based on GLCDv3 (http://playground.arduino.cc/Code/GLCDks0108), docs (http://code.google.com/p/glcd-arduino/source/browse/trunk/glcd/doc/GLCD_Documentation.pdf) but adapted to support our screen. The Init routine is called in the setup, and the LCDTask takes care of ensuring the screen is updated every 40ms if required (Unlike the original GLCD library, screen updates are decoupled from the graphics routines.)<br />
<br />
Also available is M2tklib (https://code.google.com/p/m2tklib/) which is a nice toolkit library. Further details on using this will come later, but expect the main loop to be handled for you, and just passing the menu structure you require for your app.<br />
<br />
Right now, you can call the GLCD functions directly with GLCD.DrawBitmap() for example. This is going to change to be accessed through the GUITask class in the near future, to ensure only one task at a time writes to the screen. Expect this to be simply GUITask in place of GLCD, along with a registering a redraw call back to GUITask. The bitmap format, by the way, is rather unconventional but there are a couple of utility scripts to convert popular formats down in the hacking section below - you can grab the SponsorsApp.h as an example and swap out the bitmap array with one of your choosing.<br />
<br />
Extra features that are included, GLCD.SetRotation() will handle rotation of the screen for you, and GLCD.CurrentWidth() and GLCD.CurrentHeight will give you the correct Width and Height for the current orientation. GLCD.Width and GLCD.Height constants are not available, and the GLCD predefined Text areas will not be rotated for you, if you require this define your own text areas.<br />
<br />
Note that one function was not ported to the badge version of GLCD, "Printf", you'll have to cope without it.<br />
<br />
== Sound == <br />
There's a piezo on the board, but we haven't added code for it to the current firmware. Pull requests are very welcome!<br />
<br />
== IMU ==<br />
=== Tilda::getOrientation ===<br />
returns " ORIENTATION_HELD", "ORIENTATION_RIGHT" (joystick to the right of the screen), "ORIENTATION_HUNG" or "ORIENTATION_LEFT"<br />
<br />
== Flash Storage ==<br />
We have 2mb of flash storage, but we're not using it in the main firmware - Please get this working!<br />
== Data: Schedule ==<br />
===Tilda::getDataStore().getSchedule(day, location) ===<br />
== Date: Weather Forecast ==<br />
===Tilda::getDataStore().getWeatherForecast()===<br />
== Radio ==<br />
There's no way of sending messages in the current version of the firmware, sorry :(<br />
<br />
== Time ==<br />
<br />
=== Tilda::delay(uint16_t delayInMs) === <br />
<br />
Works like Arduino’s delay(), but is FreeRTOS-safe. It’s safe to use this function before FreeRTOS has started.<br />
<br />
=== tilda::getClock() ===<br />
<br />
Returns an instance of https://github.com/MarkusLange/Arduino-Due-RTC-Library/blob/master/rtc_clock.h<br />
<br />
==Settings==<br />
===uint16_t tilda::getBadgeId()===<br />
<br />
<br />
==2.12. Battery==<br />
===float TiLDA::getBatteryVoltage()===<br />
Returns the current voltage as a float<br />
<br />
===uint8_t TiLDA::getBatteryPercent()===<br />
Returns the current voltage as a percentage<br />
<br />
===uint8_t TiLDA::getChargeState()===<br />
Returns the charge state<br />
<br />
0 Charging<br />
1 Not Charging<br />
<br />
=Hacking=<br />
To use our board definition you will need to first get the Arduino 1.5.7 IDE from [http://arduino.cc/en/Main/Software#toc3 here]<br/><br />
Next you can download the TiLDA MKe Firmware project from either the [https://github.com/emfcamp/Mk2-Firmware github repo] or via [https://github.com/emfcamp/Mk2-Firmware/archive/master.zip direct download]<br/><br />
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/<br><br />
or<br/><br />
Alternative option is to set the Arduino 1.5.7 sketchbook folder to the Mk2-Firmware directory.<br/><br />
<br />
Start the Arduino IDE and your will be able to select TiLDA MKe v0.333 for the Tools->Board menu<br />
<br />
* Draft 3d print-able and laser-able case files [http://www.thingiverse.com/thing:436815 here]<br />
* A Python script (via [https://twitter.com/trotmaster99 @trotmaster99]) that converts a monochrome bitmap image into a format suitable for the Tilda can be found [http://pastebin.com/8XeazQjT here].<br />
* A similar script in Perl to create TiLDA MKe fullscreen bitmaps from XBM: -<br />
<div style ="height:200px;overflow-x:hidden;overflow-y:auto;border: 4px solid orange;"><br />
'''xbm2mke.pl by [[User:Msemtd]]'''<br />
<nowiki><br />
#!perl -w<br />
use strict;<br />
# Little script to convert a regular XBM to TiLDA MKe bitmap<br />
# only tested with fullscreen bitmaps!<br />
# Hot file handle magic...<br />
select((select(STDERR), $| = 1)[0]);<br />
select((select(STDOUT), $| = 1)[0]);<br />
sub t(@);<br />
sub d($);<br />
sub chug($);<br />
my $f = shift;<br />
#~ $f = 'blankish.xbm' if not $f;<br />
if(not defined $f or not $f =~ /^(.*)\.xbm$/i){<br />
die "Usage: gimme an XBM file dude!\n";<br />
}<br />
my $name = $1;<br />
t "Reading file '$f'...";<br />
my $data = chug($f);<br />
t "OK";<br />
my @lines = split /^/, $data;<br />
@lines = grep{chomp; s/^\s+//; s/\s+$//; length;} @lines;<br />
#~ t d \@lines;<br />
my($width, $height) = (0,0);<br />
my @head = @lines[0..5];<br />
foreach(@head){<br />
if(/_width\s+(\d+)/){$width = $1;}<br />
if(/_height\s+(\d+)/){$height = $1;}<br />
}<br />
t "width x height = $width x $height";<br />
my @k;<br />
foreach(@lines){ push @k, split /,/; }<br />
@k = grep { s/^.*(0x[0-9A-Fa-f]{1,2}).*$/$1/o; /(0x[0-9A-Fa-f]{1,2})/o } @k;<br />
#~ t d \@k;<br />
my $bc = scalar(@k);<br />
t "Pulled out $bc hex bytes";<br />
if($bc != $width * $height / 8) {<br />
die "byte count $bc does not match that expected for w x h";<br />
}<br />
t "OK - reorder bytes for MKe bitmap";<br />
my $wb = int($width/8) + (($width & 0x07) ? 1: 0);<br />
t "width in whole bytes for $width pixels = $wb";<br />
my @mke;<br />
for(my $col = 0; $col < $wb; $col++){<br />
for(my $row = $height - 1; $row >= 0; $row--){<br />
my $idx = ($row * $wb) + $col;<br />
my $val = $k[$idx];<br />
#~ t "Column $col + Row $row = idx $idx = $val";<br />
push @mke, $val;<br />
}<br />
}<br />
my $out = "static const uint8_t ".uc($name)."_BM[] = {\n"<br />
." $width, // width\n"<br />
." $height , // height\n";<br />
#~ $out .= join(", ", @mke);<br />
while(scalar @mke){<br />
$out .= join(", ", splice(@mke, 0, 16)).",\n";<br />
}<br />
$out .= "};\n";<br />
# meh, just print it out<br />
t $out;<br />
<br />
sub t(@) {<br />
foreach (@_) {<br />
print STDOUT "$_\n";<br />
}<br />
}<br />
sub d($) {<br />
require Data::Dumper;<br />
my $s = $_[0];<br />
my $d = Data::Dumper::Dumper($s);<br />
$d =~ s/^\$VAR1 =\s*//;<br />
$d =~ s/;$//;<br />
chomp $d;<br />
return $d;<br />
}<br />
sub chug($) {<br />
my $filename = shift;<br />
local *F;<br />
open F, "< $filename" or die "Couldn't open `$filename': $!";<br />
local $/ = undef;<br />
return <F>;<br />
} # F automatically closed<br />
<br />
</nowiki><br />
</div><br />
<br />
<span id=github></span><br />
<br />
= Source =<br />
<br />
All the source code and designs are on openly available on Github:<br />
<br />
* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design<br />
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant parts datasheets<br />
* [https://github.com/emfcamp/Mk2-Firmware Firmware] - source code for the badge software<br />
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network<br />
<br />
If you want to help, point your IRC client to #tilda on Freenode.<br />
<br />
[[Category: Badges]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=TiLDA_MKe&diff=3703TiLDA MKe2014-09-14T22:57:24Z<p>Ms7821: /* Source */</p>
<hr />
<div>The TiLDA MKe project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Dpslwk|'RepRap' Matt]] and [[User:thinkl33t|Bob]]<br />
[[File:IMG_0474.jpg|500px|right|thumb|Front]]<br />
[[File:Badge_Front.png|right|thumb|Front]]<br />
<br />
[http://en.wikipedia.org/wiki/E_(mathematical_constant) Why MKe?]<br />
<br />
Please Note: There are a couple of minor hardware and some firmware issues that might be effecting your badge. If you've let the magic smoke out of your charge controller or have tried to re-flash and ended up with nothing but a couple of dimly glowing lights then DO NOT DESPAIR -It's recoverable and fixes, documentation and lots of firmware are still being produced :)<br />
<br />
=Aim= <br />
The main aim of the 2014 badge is to give camp attendees live schedule updates and notifications. As with the original TiLDA we wanted to keep with an Arduino compatible platform that will allow badge hacking during and after the camp. As with the previous badge all code and design files are available.<br />
<br />
==Battery Warning==<br />
'''Always make sure you plug your battery in the right way round!''' If you don't, the charge controller will let out its magic smoke and die / become damaged and die later. The badge itself will still work, but it wont have the ability to charge anymore. <br />
<br />
We think this is the cause of the charge controller issues a small number of badges had at the event was due to this mistake being made during final assembly on-site. <br />
<br />
'''Lithium Batteries are dangerous!''' While these batteries are better protected than the MK1 batteries, they are still scary. Do not short your battery, and if it starts bulging or gets punctured, '''DO NOT USE IT AGAIN''' and dispose of it properly.<br />
<br />
==Features and Functions==<br />
[[File:Badge_Back.png|right|thumb|Back]]<br />
* Torch mode - Press the light button next to the screen. It will only light up fully if it's hung upside down to avoid blinding<br />
* Snake<br />
* Tetris<br />
<br />
'''Please note that there's a known issue with the badge freezing'''. We're trying to work out what's causing this, but in the meantime pressing "reset" should get the badge back to life. Help with debugging is highly welcome!<br />
<br />
== How to get going ==<br />
=== Set up your environment ===<br />
* Plug your badge into your computer via USB<br />
* Download Arduino IDE 1.5.7 from http://arduino.cc/en/main/software#toc3<br />
* “git clone” or download TiLDA source code from https://github.com/emfcamp/Mk2-Firmware<br />
* Start the Arduino IDE. <br />
* Now you have to change the sketchbook-folder to be the folder you just cloned. To do this use File | Preferences | “Set Sketchbook location”. On MacOS, this is Arduino | Preferences <br />
* Restart the Arduino IDE<br />
* Open sketch “EMF2014”<br />
* Set Tools | Board to MKe v0.333 (RTOS Core)<br />
* Set Tools | Port to correct port (you might have to research this - some operating systems like Windows require you to install drivers or become a member of a certain group)<br />
** On MacOS this is will start /dev/tty.usbmodem with 4 digits, and change for each port<br />
** On Linux this is usually /dev/ttyACM0 but may be a higher number if you have other USB Serial devices<br />
* Hit the upload button<br />
* Wait<br />
* Woohoo - You just successfully uploaded code to your badge<br />
<br />
=== Your first “Hello world” app ===<br />
There’s a “HelloWorldApp.cpp” file in which you can play around. In order for it to show up on the Homescreen you have to uncomment line 51 in AppManager.cpp and flash the changed code to the badge. Great app pull requests are appreciated!<br />
<br />
If you are still using the Arduino IDE at this point, note that it will not let you edit the .cpp and .h files that are needed to create Apps for the badge. To force the IDE to re-compile/re-read any files you've edited using an external editor, make sure to go to the File -> Preferences dialog box, and check the "Use external editor" checkbox.<br />
<br />
=== Why are things so different from standard Arduino code? ===<br />
We’re using a library called FreeRTOS that allows us to multitask - something that’s normally not possible with standard Arduino code. This allows us to run multiple tasks at the same time. FreeRTOS uses preemptive scheduling to switch between the task. Due to this we have to be very careful about how we do some things. For example we can’t just define interrupts for buttons in every task (imagine the mess!) or write to the serial port directly (your task might stop in the middle of the message). <br />
<br />
We’ve also spend quite a lot of time to make the build-in components as easy to use as possible without having every task to write lots of boilerplate code. If you feel like using the build-in components on the badge, chances are we already wrote a wrapper for them that is already used by one of the other tasks. <br />
<br />
Have a look at the “Documentation” section in this document for a full list of API functions. You will avoid a lot of headaches if you stick to those.<br />
=== How to use the badge with pure Arduino code ===<br />
If you prefer you can always start from scratch without FreeRTOS or any of our code, just keep in mind that you won’t be able to receive messages via radio or use any of the API features we already added. Just start a new sketch in the Arduino IDE for that and get going. If you want to load the main firmware again just change the sketch to “EMF2014” and upload again.<br />
=== Debugging and Gotchas ===<br />
* The USB serial is set up to 115220 baud. There are lots of terminals that can connect to them<br />
* If you can’t revive a badge you can short the two erase pins and press the reset button while holding it down.<br />
* Avoid busy waiting, use FreeRTOS queues and Tilda::delay() instead<br />
* Don’t use low level functions like interrupts or serial ports directly unless you really, really know how FreeRTOS will handle them. For general logging you can use Tilda::log()<br />
* If sending code to the badge using the Arduino IDE "Upload" button fails, even though the /dev/ttyACM0 (linux com port) is there, just retry, twice if neccessary.<br />
<br />
=== Code structure ===<br />
* FreeRTOS has the concept of “Tasks” which work like threads. We’ve wrappered them in a class called “Task” (for background stuff) and “Apps” (for foreground, one-at-a-time things)<br />
* Everything needs to be in the main EMF2014 folder. Subfolders are not allowed. This is an Arduino IDE restriction :(<br />
=== Radio infrastructure ===<br />
The radio infrastructure is distributed between DKs. Every “gateway” has a Raspberry Pi with two Ciseco USB radios. We never had the chance to actually try it with a large number of badges in the same spot, so please don’t expect it to work perfectly.<br />
<br />
=== Contribute ===<br />
Send us a pull request via [https://github.com/emfcamp/Mk2-Firmware GitHub] - We’ll do our best to review and merge the good ones during EMF so others can use them.<br />
<br />
=Hardware=<br />
<br />
The following hardware has been included on the badge.<br />
<br />
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]<br />
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge<br />
** 32bit ARM Cortex M3 * 84MHz<br />
** 512KBytes Flash RAM<br />
** 96KBytes of SRAM<br />
* A 128x64 pixel monochrome LCD display<br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
** 868Mhz RF Transceiver<br />
** Simple UART interface<br />
** Low power sleep mode<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro<br />
** I2C interface<br />
** Tri-Axis angular rate sensor (gyro) with a sensitivity up to 131 LSBs/dps and a full-scale range of ±250, ±500, ±1000, and ±2000dps<br />
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g<br />
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronisation and gesture detection<br />
* PMIC & LiPo<br />
* Joystick<br />
* Buttons<br />
* RGB LEDs<br />
* IR<br />
* Arduino Headers<br />
* Pads for wearable tech<br />
<br />
= Firmware Documentation =<br />
== Debugging ==<br />
===Tilda::log(String text)===<br />
<br />
This logs “text” to the serial console. To read it connect to it via the Arduino IDE Serial Monitor. Don’t use “SerialUSB.println” or similar -- it’s not thread-safe and you might end up with utter nonsense.<br />
== Buttons ==<br />
The badge has 8 buttons: Up, Down, Left, Right, Center (on the joystick), A, B and Light. You can use arduino-style “digitalRead(BUTTON_RIGHT)” to read the current status of any button, but you can’t define your own interrupt (because we already did that). This doesn’t mean you can’t wait for a certain button to be pressed, it just means you have to approach it slightly differently:<br />
<br />
Example: A simple app displaying the button code<br />
void ButtonApp::task() {<br />
ButtonSubscription allButtons = Tilda::createButtonSubscription(LIGHT | A | B | UP | DOWN | LEFT | RIGHT | CENTER);<br />
<br />
while(true) {<br />
Button button = allButtons.waitForPress(1000);<br />
if (button == A) {<br />
debug::log(“You pressed button A”);<br />
} else if (button == LEFT) {<br />
debug::log(“You pressed LEFT”);<br />
} else if (button == NONE) {<br />
debug::log(“No button has been pressed in 1000ms”); <br />
}<br />
}<br />
}<br />
<br />
<br />
===ButtonSubscription Tilda::createButtonSubscription(<buttons>)===<br />
<br />
Registers a subscriptions for a defined set of buttons and returns a ButtonSubscription. Multiple Buttons can be combined via “|” (see example above). One button can not be subscribed by more than 10 subscriptions (which shouldn’t really happen, but keep it in mind). <br />
<br />
Don’t use this function in a constructor, it requires FreeRTOS to be running. Using it inside the task() function is the only safe place for it.<br />
<br />
===Button ButtonSubscription::waitForPress(TimeInTicks timeout)===<br />
<br />
This is normally called in a loop. It causes the task to block until one of the buttons has been pressed. If the timeout occurs before any button has been pressed “NONE” will be returned. <br />
<br />
===ButtonSubscription::waitForPress()===<br />
<br />
The same as above, but without the timeout.<br />
<br />
===ButtonSubscription::clear()===<br />
<br />
This should be called after an App has been suspended, just before it’s going to be resumed. It causes the Queue to be cleared which could otherwise lead to buttons being reported that have been pressed while other apps were in the foreground. Have a look at the FlashLightApp for an example.<br />
<br />
==LEDs==<br />
===Tilda::setLedColor(Led led, Color color);===<br />
===Tilde::setLedColor(Color color);===<br />
<br />
Sets the color of all or one led. Color is an object that takes red, green and blue as a value between 0 and 255 each. If no led is defined both leds will be set to the same color.<br />
<br />
Example: A simple color-changing task<br />
void ColorfulTask::task() {<br />
while(true) {<br />
Tilda::setLedColor(LED1, {255, 0, 0}); // Red<br />
Tilda::setLedColor(LED2, {0, 255, 0}); // Green<br />
Tilda::delay(300);<br />
Tilda::setLedColor(LED1, {0, 255, 0}); // Green<br />
Tilda::setLedColor(LED2, {0, 0, 255}); // Blue<br />
Tilda::delay(300);<br />
Tilda::setLedColor(LED1, {0, 0, 255}); // Blue<br />
Tilda::setLedColor(LED2, {255, 0, 0}); // Red<br />
Tilda::delay(300);<br />
}<br />
}<br />
<br />
==Display==<br />
<br />
The Display Library is based on GLCDv3 (http://playground.arduino.cc/Code/GLCDks0108), docs (http://code.google.com/p/glcd-arduino/source/browse/trunk/glcd/doc/GLCD_Documentation.pdf) but adapted to support our screen. The Init routine is called in the setup, and the LCDTask takes care of ensuring the screen is updated every 40ms if required (Unlike the original GLCD library, screen updates are decoupled from the graphics routines.)<br />
<br />
Also available is M2tklib (https://code.google.com/p/m2tklib/) which is a nice toolkit library. Further details on using this will come later, but expect the main loop to be handled for you, and just passing the menu structure you require for your app.<br />
<br />
Right now, you can call the GLCD functions directly with GLCD.DrawBitmap() for example. This is going to change to be accessed through the GUITask class in the near future, to ensure only one task at a time writes to the screen. Expect this to be simply GUITask in place of GLCD, along with a registering a redraw call back to GUITask. The bitmap format, by the way, is rather unconventional but there are a couple of utility scripts to convert popular formats down in the hacking section below - you can grab the SponsorsApp.h as an example and swap out the bitmap array with one of your choosing.<br />
<br />
Extra features that are included, GLCD.SetRotation() will handle rotation of the screen for you, and GLCD.CurrentWidth() and GLCD.CurrentHeight will give you the correct Width and Height for the current orientation. GLCD.Width and GLCD.Height constants are not available, and the GLCD predefined Text areas will not be rotated for you, if you require this define your own text areas.<br />
<br />
Note that one function was not ported to the badge version of GLCD, "Printf", you'll have to cope without it.<br />
<br />
== Sound == <br />
There's a piezo on the board, but we haven't added code for it to the current firmware. Pull requests are very welcome!<br />
<br />
== IMU ==<br />
=== Tilda::getOrientation ===<br />
returns " ORIENTATION_HELD", "ORIENTATION_RIGHT" (joystick to the right of the screen), "ORIENTATION_HUNG" or "ORIENTATION_LEFT"<br />
<br />
== Flash Storage ==<br />
We have 2mb of flash storage, but we're not using it in the main firmware - Please get this working!<br />
== Data: Schedule ==<br />
===Tilda::getDataStore().getSchedule(day, location) ===<br />
== Date: Weather Forecast ==<br />
===Tilda::getDataStore().getWeatherForecast()===<br />
== Radio ==<br />
There's no way of sending messages in the current version of the firmware, sorry :(<br />
<br />
== Time ==<br />
<br />
=== Tilda::delay(uint16_t delayInMs) === <br />
<br />
Works like Arduino’s delay(), but is FreeRTOS-safe. It’s safe to use this function before FreeRTOS has started.<br />
<br />
=== tilda::getClock() ===<br />
<br />
Returns an instance of https://github.com/MarkusLange/Arduino-Due-RTC-Library/blob/master/rtc_clock.h<br />
<br />
==Settings==<br />
===uint16_t tilda::getBadgeId()===<br />
<br />
<br />
==2.12. Battery==<br />
===float TiLDA::getBatteryVoltage()===<br />
Returns the current voltage as a float<br />
<br />
===uint8_t TiLDA::getBatteryPercent()===<br />
Returns the current voltage as a percentage<br />
<br />
===uint8_t TiLDA::getChargeState()===<br />
Returns the charge state<br />
<br />
0 Charging<br />
1 Not Charging<br />
<br />
=Hacking=<br />
To use our board definition you will need to first get the Arduino 1.5.7 IDE from [http://arduino.cc/en/Main/Software#toc3 here]<br/><br />
Next you can download the TiLDA MKe Firmware project from either the [https://github.com/emfcamp/Mk2-Firmware github repo] or via [https://github.com/emfcamp/Mk2-Firmware/archive/master.zip direct download]<br/><br />
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/<br><br />
or<br/><br />
Alternative option is to set the Arduino 1.5.7 sketchbook folder to the Mk2-Firmware directory.<br/><br />
<br />
Start the Arduino IDE and your will be able to select TiLDA MKe v0.333 for the Tools->Board menu<br />
<br />
* Draft 3d print-able and laser-able case files [http://www.thingiverse.com/thing:436815 here]<br />
* A Python script (via [https://twitter.com/trotmaster99 @trotmaster99]) that converts a monochrome bitmap image into a format suitable for the Tilda can be found [http://pastebin.com/8XeazQjT here].<br />
* A similar script in Perl to create TiLDA MKe fullscreen bitmaps from XBM: -<br />
<div style ="height:200px;overflow-x:hidden;overflow-y:auto;border: 4px solid orange;"><br />
'''xbm2mke.pl by [[User:Msemtd]]'''<br />
<nowiki><br />
#!perl -w<br />
use strict;<br />
# Little script to convert a regular XBM to TiLDA MKe bitmap<br />
# only tested with fullscreen bitmaps!<br />
# Hot file handle magic...<br />
select((select(STDERR), $| = 1)[0]);<br />
select((select(STDOUT), $| = 1)[0]);<br />
sub t(@);<br />
sub d($);<br />
sub chug($);<br />
my $f = shift;<br />
#~ $f = 'blankish.xbm' if not $f;<br />
if(not defined $f or not $f =~ /^(.*)\.xbm$/i){<br />
die "Usage: gimme an XBM file dude!\n";<br />
}<br />
my $name = $1;<br />
t "Reading file '$f'...";<br />
my $data = chug($f);<br />
t "OK";<br />
my @lines = split /^/, $data;<br />
@lines = grep{chomp; s/^\s+//; s/\s+$//; length;} @lines;<br />
#~ t d \@lines;<br />
my($width, $height) = (0,0);<br />
my @head = @lines[0..5];<br />
foreach(@head){<br />
if(/_width\s+(\d+)/){$width = $1;}<br />
if(/_height\s+(\d+)/){$height = $1;}<br />
}<br />
t "width x height = $width x $height";<br />
my @k;<br />
foreach(@lines){ push @k, split /,/; }<br />
@k = grep { s/^.*(0x[0-9A-Fa-f]{1,2}).*$/$1/o; /(0x[0-9A-Fa-f]{1,2})/o } @k;<br />
#~ t d \@k;<br />
my $bc = scalar(@k);<br />
t "Pulled out $bc hex bytes";<br />
if($bc != $width * $height / 8) {<br />
die "byte count $bc does not match that expected for w x h";<br />
}<br />
t "OK - reorder bytes for MKe bitmap";<br />
my $wb = int($width/8) + (($width & 0x07) ? 1: 0);<br />
t "width in whole bytes for $width pixels = $wb";<br />
my @mke;<br />
for(my $col = 0; $col < $wb; $col++){<br />
for(my $row = $height - 1; $row >= 0; $row--){<br />
my $idx = ($row * $wb) + $col;<br />
my $val = $k[$idx];<br />
#~ t "Column $col + Row $row = idx $idx = $val";<br />
push @mke, $val;<br />
}<br />
}<br />
my $out = "static const uint8_t ".uc($name)."_BM[] = {\n"<br />
." $width, // width\n"<br />
." $height , // height\n";<br />
#~ $out .= join(", ", @mke);<br />
while(scalar @mke){<br />
$out .= join(", ", splice(@mke, 0, 16)).",\n";<br />
}<br />
$out .= "};\n";<br />
# meh, just print it out<br />
t $out;<br />
<br />
sub t(@) {<br />
foreach (@_) {<br />
print STDOUT "$_\n";<br />
}<br />
}<br />
sub d($) {<br />
require Data::Dumper;<br />
my $s = $_[0];<br />
my $d = Data::Dumper::Dumper($s);<br />
$d =~ s/^\$VAR1 =\s*//;<br />
$d =~ s/;$//;<br />
chomp $d;<br />
return $d;<br />
}<br />
sub chug($) {<br />
my $filename = shift;<br />
local *F;<br />
open F, "< $filename" or die "Couldn't open `$filename': $!";<br />
local $/ = undef;<br />
return <F>;<br />
} # F automatically closed<br />
<br />
</nowiki><br />
</div><br />
<br />
<span id=github></span><br />
<br />
= Source =<br />
<br />
All the source code and designs are on openly available on Github:<br />
<br />
* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design<br />
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant parts datasheets<br />
* [https://github.com/emfcamp/Mk2-Firmware Firmware] - source code for the badge software<br />
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network<br />
<br />
If you want to help, join us on #tilda on Freenode.<br />
<br />
[[Category: Badges]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Memories&diff=3663Memories2014-09-07T03:23:04Z<p>Ms7821: /* Photos */</p>
<hr />
<div>{{link-banner}}<br />
Please add links to any photos, videos, etc. of EMF2014 you have ([https://wiki-archive.emfcamp.org/2012/articles/d/o/c/Documentation.html like we did in 2012]).<br />
<br />
__TOC__<br />
<br />
Please add links in the following format:<br />
<br />
<nowiki>*[https://www.emfcamp.org EMF Website]</nowiki><br />
<br />
This would look like:<br />
<br />
*[https://www.emfcamp.org EMF Website]<br />
<br />
==Before Event==<br />
Set up, planning, etc.<br />
<br />
===Articles/Blogs===<br />
*[http://hackaday.com/2014/08/16/tilda-mke-the-emf-2014-badge/ Hackaday on the badge]<br />
*[http://makezine.com/2014/08/15/the-amazing-emf-conference-badge/ Make magazine on the badge]<br />
*[http://www.arrl.org/news/view/emf-2014-it-takes-an-amateur-radio-village ARRL: It Takes an Amateur Radio Village]<br />
*[http://www.element14.com/community/groups/maker-hacker-inventor-and-hobbyist/content?filterID=contentstatus%5Bpublished%5D~language~language%5Bcpl%5D&query=emfcamp: Element14 Community Blog Replications]<br />
===Photos===<br />
*[https://www.flickr.com/photos/chaoticeunoia/15047294495/ Kitty's photographs incl take down]<br />
*[https://wiki.sonologic.net/Images/EMF2014 gmc's crappy phone cam pics]<br />
*[https://plus.google.com/u/0/photos/104882304117764204022/albums/6055585085939539041 OXHACK putting the E in emc] <br />
===Videos===<br />
<br />
==During Event==<br />
The event itself.<br />
<br />
===Articles/Blogs===<br />
*[http://www.bbc.co.uk/news/technology-29011889 Electromagnetic Field: Can geeks get kids into science? (BBC)]<br />
*[http://www.theguardian.com/technology/2014/sep/03/electromagnetic-field-camp-emfcamp-drones-arduino-burning-man Electromagnetic Field: the UK's Burning Man? (The Guardian)]<br />
*[https://storify.com/pikesley/things-i-overheard-at-emf-camp-2014 Overheard at EMF2014]<br />
*[https://storify.com/pikesley/how-to-emf How to EMF]<br />
*[http://motherboard.vice.com/read/the-emojli-creators-say-you-shouldnt-make-an-app The Creators of Emojli: Don't Build an App (Motherboard/Vice)]<br />
*[http://motherboard.vice.com/read/inside-uks-electromagnetic-field-festival Not Your 'Traditional Hacker Camp': Inside Electromagnetic Field Festival (Motherboard/Vice)]<br />
*[http://motherboard.vice.com/read/a-call-for-geeks-to-hijack-politics The British MP Who Wants Geeks to Hijack the Politics of Surveillance (Motherboard/Vice)]<br />
*[http://jhaand.nl/2014/09/emf2014-electro-magnetic-fields-hacker-festival-2014/ #EMF2014 (ELECTRO MAGNETIC FIELDS HACKER FESTIVAL 2014)]<br />
*[http://squirmelia.livejournal.com/453051.html Glitch Art Workshop]<br />
*[http://legavrik.blogspot.co.uk/2014/09/electromagnetic-field-talk.html MScroggs' Flexagons talk]<br />
<br />
===Photos===<br />
If you have uploaded any photos to Flickr, we would love if you also add them to the group - [https://flic.kr/g/pGAy6]<br />
<br />
*[https://plus.google.com/photos/113943934552095226264/albums/6054537668273419873 Saturday] - [[User:TCMSLP|TCMSLP]]<br />
*[https://twitter.com/search?q=emfcamp&src=typd&mode=photos Twitter photos]<br />
*[https://plus.google.com/photos/+MatthewCopperwaite/albums/6053636538009652657 Friday] [https://plus.google.com/photos/+MatthewCopperwaite/albums/6053636954715546161 Saturday] [https://plus.google.com/u/0/photos/+MatthewCopperwaite/albums/6054110412172875841 Sunday] - [[User:YaMatt|YaMatt]] ([[User talk:YaMatt|talk]])<br />
*[https://plus.google.com/photos/112777126606198038716/albums/6054213887214967841?authkey=CJinnqObgtShMw Various photos including Kite mapping, The Grid and drone wars]<br />
*[https://www.flickr.com/photos/matstace/sets/72157647043339236/ matstace's flickr ]<br />
*[https://plus.google.com/u/0/b/107012837690078606602/photos/107012837690078606602/albums/6054051185457665105 LPRS & The Real Wireless Mike]<br />
* [[Installations:TheGrid|TheGrid]]: I (Cillian) will retweet everything I can find at [https://twitter.com/__thegrid].<br />
* some photospheres: [http://bit.ly/1lwrv26] [http://bit.ly/1redupW] [http://bit.ly/W6ukuE] [http://bit.ly/W6umCI]<br />
* [https://www.flickr.com/photos/barnoid/sets/72157646690458589 Barnoid's photos]<br />
* [https://www.flickr.com/photos/nicecupoftea/sets/72157647140464951/ Libby's photos]<br />
* [https://www.flickr.com/photos/choffee/sets/72157646533985179/ Choffee's photos]<br />
* [https://wiki.sonologic.net/Images/EMF2014 gmc's crappy phone cam pics]<br />
* [https://www.flickr.com/photos/nottinghack/sets/72157646710169057/ nottinghack flickr stuff]<br />
* [https://www.flickr.com/photos/sophigarrett/sets/72157646845220777 Sophie's photos]<br />
* [https://foto.pho.be/20140904-emfetc/ murble's photos]<br />
* [https://www.flickr.com/photos/stanto/sets/72157647239775945 [[User:Stanto]]'s pics]<br />
* [https://www.flickr.com/photos/chaoticeunoia/sets/72157646903781435 [[User:Maow]]'s photos]<br />
* [https://www.flickr.com/photos/unnamedculprit/sets/72157646813614377/ Matt Gray's photos]<br />
<br />
===Videos===<br />
* [http://www.bbc.co.uk/news/technology-29011898 The most future-proof profession? (BBC)]<br />
* [https://www.youtube.com/watch?v=wfy_zdZbTUI Laser cutter - Just Add Sharks]<br />
* [https://www.flickr.com/photos/barnoid/14905261730/ TOG Duck vs BigHak Race]<br />
* [https://www.youtube.com/watch?v=tualAybVbT4 Camp Holland Timelapse]<br />
* [[Installations:TheGrid|TheGrid]]: [https://www.youtube.com/watch?v=bbUKrVY6BFA Me] ([[User:Pikesley|Pikesley]]) (also [http://share.gifyoutube.com/YO1GMG.gif as a gif]), and [https://vine.co/v/OB5z299EjUW Ulrich] ([[User:Rico|Rico]])<br />
* [https://www.flickr.com/photos/barnoid/15115548641/ Arriving on golf cart trailer]<br />
* [https://www.youtube.com/watch?v=K_kjqArTKww Bar Bot]<br />
* [https://www.youtube.com/watch?v=kcrgaEGLusY More Bar Bot]<br />
* [https://www.youtube.com/watch?v=8XTEpqlPzjE EMF Camp Saturday Aerial Tour]<br />
* [https://www.youtube.com/watch?v=DFlOloCsxuA Rabbit The Soul Eater]<br />
* [https://www.youtube.com/watch?v=x5KH4bUt8X8 Tom Scott's bit on the alcohol fogger]<br />
* [https://www.youtube.com/watch?v=BzgWG-AOSMk Ben Heck's Extreme Camping Chair Trailer]<br />
<br />
===Audio Recordings===<br />
* "Spray Whisky On Me" EMFM Radio Show: it is doubtful we can publish the copyrighted songs but I hope to edit a copy of the 2am Sunday morning show when it is available.</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Memories&diff=3613Memories2014-09-05T15:23:38Z<p>Ms7821: /* Photos */</p>
<hr />
<div>{{link-banner}}<br />
Please add links to any photos, videos, etc. of EMF2014 you have ([https://wiki-archive.emfcamp.org/2012/articles/d/o/c/Documentation.html like we did in 2012]).<br />
<br />
__TOC__<br />
<br />
Please add links in the following format:<br />
<br />
<nowiki>*[https://www.emfcamp.org EMF Website]</nowiki><br />
<br />
This would look like:<br />
<br />
*[https://www.emfcamp.org EMF Website]<br />
<br />
==Before Event==<br />
Set up, planning, etc.<br />
<br />
===Articles===<br />
*[http://hackaday.com/2014/08/16/tilda-mke-the-emf-2014-badge/ Hackaday on the badge]<br />
*[http://makezine.com/2014/08/15/the-amazing-emf-conference-badge/ Make magazine on the badge]<br />
*[http://www.arrl.org/news/view/emf-2014-it-takes-an-amateur-radio-village ARRL: It Takes an Amateur Radio Village]<br />
===Photos===<br />
*[https://www.flickr.com/photos/chaoticeunoia/15047294495/ Kitty's photographs incl take down]<br />
*[https://wiki.sonologic.net/Images/EMF2014 gmc's crappy phone cam pics]<br />
*[https://plus.google.com/u/0/photos/104882304117764204022/albums/6055585085939539041 OXHACK putting the E in emc] <br />
===Videos===<br />
<br />
==During Event==<br />
The event itself.<br />
<br />
===Articles/Blogs===<br />
*[http://www.bbc.co.uk/news/technology-29011889 Electromagnetic Field: Can geeks get kids into science? (BBC)]<br />
*[http://www.theguardian.com/technology/2014/sep/03/electromagnetic-field-camp-emfcamp-drones-arduino-burning-man Electromagnetic Field: the UK's Burning Man? (The Guardian)]<br />
*[https://storify.com/pikesley/things-i-overheard-at-emf-camp-2014 Overheard at EMF2014]<br />
*[https://storify.com/pikesley/how-to-emf How to EMF]<br />
*[http://motherboard.vice.com/read/the-emojli-creators-say-you-shouldnt-make-an-app The Creators of Emojli: Don't Build an App (Motherboard/Vice)]<br />
*[http://motherboard.vice.com/read/inside-uks-electromagnetic-field-festival Not Your 'Traditional Hacker Camp': Inside Electromagnetic Field Festival (Motherboard/Vice)]<br />
*[http://motherboard.vice.com/read/a-call-for-geeks-to-hijack-politics The British MP Who Wants Geeks to Hijack the Politics of Surveillance (Motherboard/Vice)]<br />
*[http://jhaand.nl/2014/09/emf2014-electro-magnetic-fields-hacker-festival-2014/ #EMF2014 (ELECTRO MAGNETIC FIELDS HACKER FESTIVAL 2014)]<br />
*[http://squirmelia.livejournal.com/453051.html Glitch Art Workshop]<br />
*[http://legavrik.blogspot.co.uk/2014/09/electromagnetic-field-talk.html MScroggs' Flexagons talk]<br />
<br />
===Photos===<br />
If you have uploaded any photos to Flickr, we would love if you also add them to the group - [https://flic.kr/g/pGAy6]<br />
<br />
*[https://plus.google.com/photos/113943934552095226264/albums/6054537668273419873 Saturday] - [[User:TCMSLP|TCMSLP]]<br />
*[https://twitter.com/search?q=emfcamp&src=typd&mode=photos Twitter photos]<br />
*[https://plus.google.com/photos/+MatthewCopperwaite/albums/6053636538009652657 Friday] [https://plus.google.com/photos/+MatthewCopperwaite/albums/6053636954715546161 Saturday] [https://plus.google.com/u/0/photos/+MatthewCopperwaite/albums/6054110412172875841 Sunday] - [[User:YaMatt|YaMatt]] ([[User talk:YaMatt|talk]])<br />
*[https://plus.google.com/photos/112777126606198038716/albums/6054213887214967841?authkey=CJinnqObgtShMw Various photos including Kite mapping, The Grid and drone wars]<br />
*[https://www.flickr.com/photos/matstace/sets/72157647043339236/ matstace's flickr ]<br />
*[https://plus.google.com/u/0/b/107012837690078606602/photos/107012837690078606602/albums/6054051185457665105 LPRS & The Real Wireless Mike]<br />
* [[Installations:TheGrid|TheGrid]]: I (Cillian) will retweet everything I can find at [https://twitter.com/__thegrid].<br />
* some photospheres: [http://bit.ly/1lwrv26] [http://bit.ly/1redupW] [http://bit.ly/W6ukuE] [http://bit.ly/W6umCI]<br />
* [https://www.flickr.com/photos/barnoid/sets/72157646690458589 Barnoid's photos]<br />
* [https://www.flickr.com/photos/nicecupoftea/sets/72157647140464951/ Libby's photos]<br />
* [https://www.flickr.com/photos/choffee/sets/72157646533985179/ Choffee's photos]<br />
* [https://wiki.sonologic.net/Images/EMF2014 gmc's crappy phone cam pics]<br />
* [https://www.flickr.com/photos/nottinghack/sets/72157646710169057/ nottinghack flickr stuff]<br />
* [https://www.flickr.com/photos/sophigarrett/sets/72157646845220777 Sophie's photos]<br />
<br />
===Videos===<br />
* [http://www.bbc.co.uk/news/technology-29011898 The most future-proof profession? (BBC)]<br />
* [https://www.youtube.com/watch?v=wfy_zdZbTUI Laser cutter - Just Add Sharks]<br />
* [https://www.flickr.com/photos/barnoid/14905261730/ TOG Duck vs BigHak Race]<br />
* [https://www.youtube.com/watch?v=tualAybVbT4 Camp Holland Timelapse]<br />
* [[Installations:TheGrid|TheGrid]]: [https://www.youtube.com/watch?v=bbUKrVY6BFA Me] ([[User:Pikesley|Pikesley]]) (also [http://share.gifyoutube.com/YO1GMG.gif as a gif]), and [https://vine.co/v/OB5z299EjUW Ulrich] ([[User:Rico|Rico]])<br />
* [https://www.flickr.com/photos/barnoid/15115548641/ Arriving on golf cart trailer]<br />
* [https://www.youtube.com/watch?v=K_kjqArTKww Bar Bot]<br />
* [https://www.youtube.com/watch?v=kcrgaEGLusY More Bar Bot]<br />
* [https://www.youtube.com/watch?v=8XTEpqlPzjE EMF Camp Saturday Aerial Tour]<br />
* [https://www.youtube.com/watch?v=DFlOloCsxuA Rabbit The Soul Eater]<br />
* [https://www.youtube.com/watch?v=x5KH4bUt8X8 Tom Scott's bit on the alcohol fogger]<br />
<br />
===Audio Recordings===<br />
* "Spray Whisky On Me" EMFM Radio Show: it is doubtful we can publish the copyrighted songs but I hope to edit a copy of the 2am Sunday morning show when it is available.</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Memories&diff=3611Memories2014-09-05T13:18:46Z<p>Ms7821: /* Articles */</p>
<hr />
<div>{{link-banner}}<br />
Please add links to any photos, videos, etc. of EMF2014 you have ([https://wiki-archive.emfcamp.org/2012/articles/d/o/c/Documentation.html like we did in 2012]).<br />
<br />
__TOC__<br />
<br />
Please add links in the following format:<br />
<br />
<nowiki>*[https://www.emfcamp.org EMF Website]</nowiki><br />
<br />
This would look like:<br />
<br />
*[https://www.emfcamp.org EMF Website]<br />
<br />
==Before Event==<br />
Set up, planning, etc.<br />
<br />
===Articles===<br />
*[http://hackaday.com/2014/08/16/tilda-mke-the-emf-2014-badge/ Hackaday on the badge]<br />
*[http://makezine.com/2014/08/15/the-amazing-emf-conference-badge/ Make magazine on the badge]<br />
*[http://www.arrl.org/news/view/emf-2014-it-takes-an-amateur-radio-village ARRL: It Takes an Amateur Radio Village]<br />
===Photos===<br />
*[https://www.flickr.com/photos/chaoticeunoia/15047294495/ Kitty's photographs incl take down]<br />
*[https://wiki.sonologic.net/Images/EMF2014 gmc's crappy phone cam pics]<br />
<br />
===Videos===<br />
<br />
==During Event==<br />
The event itself.<br />
<br />
===Articles/Blogs===<br />
*[http://www.bbc.co.uk/news/technology-29011889 Electromagnetic Field: Can geeks get kids into science? (BBC)]<br />
*[http://www.theguardian.com/technology/2014/sep/03/electromagnetic-field-camp-emfcamp-drones-arduino-burning-man Electromagnetic Field: the UK's Burning Man? (The Guardian)]<br />
*[https://storify.com/pikesley/things-i-overheard-at-emf-camp-2014 Overheard at EMF2014]<br />
*[https://storify.com/pikesley/how-to-emf How to EMF]<br />
*[http://motherboard.vice.com/read/the-emojli-creators-say-you-shouldnt-make-an-app The Creators of Emojli: Don't Build an App (Motherboard/Vice)]<br />
*[http://motherboard.vice.com/read/inside-uks-electromagnetic-field-festival Not Your 'Traditional Hacker Camp': Inside Electromagnetic Field Festival (Motherboard/Vice)]<br />
*[http://motherboard.vice.com/read/a-call-for-geeks-to-hijack-politics The British MP Who Wants Geeks to Hijack the Politics of Surveillance (Motherboard/Vice)]<br />
*[http://jhaand.nl/2014/09/emf2014-electro-magnetic-fields-hacker-festival-2014/ #EMF2014 (ELECTRO MAGNETIC FIELDS HACKER FESTIVAL 2014)]<br />
*[http://squirmelia.livejournal.com/453051.html Glitch Art Workshop]<br />
*[http://legavrik.blogspot.co.uk/2014/09/electromagnetic-field-talk.html MScroggs' Flexagons talk]<br />
<br />
===Photos===<br />
If you have uploaded any photos to Flickr, we would love if you also add them to the group - [https://flic.kr/g/pGAy6]<br />
<br />
*[https://plus.google.com/photos/113943934552095226264/albums/6054537668273419873 Saturday] - [[User:TCMSLP|TCMSLP]]<br />
*[https://twitter.com/search?q=emfcamp&src=typd&mode=photos Twitter photos]<br />
*[https://plus.google.com/photos/+MatthewCopperwaite/albums/6053636538009652657 Friday] [https://plus.google.com/photos/+MatthewCopperwaite/albums/6053636954715546161 Saturday] [https://plus.google.com/u/0/photos/+MatthewCopperwaite/albums/6054110412172875841 Sunday] - [[User:YaMatt|YaMatt]] ([[User talk:YaMatt|talk]])<br />
*[https://plus.google.com/photos/112777126606198038716/albums/6054213887214967841?authkey=CJinnqObgtShMw Various photos including Kite mapping, The Grid and drone wars]<br />
*[https://www.flickr.com/photos/matstace/sets/72157647043339236/ matstace's flickr ]<br />
*[https://plus.google.com/u/0/b/107012837690078606602/photos/107012837690078606602/albums/6054051185457665105 LPRS & The Real Wireless Mike]<br />
* [[Installations:TheGrid|TheGrid]]: I (Cillian) will retweet everything I can find at [https://twitter.com/__thegrid].<br />
* some photospheres: [http://bit.ly/1lwrv26] [http://bit.ly/1redupW] [http://bit.ly/W6ukuE] [http://bit.ly/W6umCI]<br />
* [https://www.flickr.com/photos/barnoid/sets/72157646690458589 Barnoid's photos]<br />
* [https://www.flickr.com/photos/nicecupoftea/sets/72157647140464951/ Libby's photos]<br />
* [https://www.flickr.com/photos/choffee/sets/72157646533985179/ Choffee's photos]<br />
* [https://wiki.sonologic.net/Images/EMF2014 gmc's crappy phone cam pics]<br />
* [https://www.flickr.com/photos/nottinghack/sets/72157646710169057/ nottinghack flickr stuff]<br />
<br />
===Videos===<br />
* [http://www.bbc.co.uk/news/technology-29011898 The most future-proof profession? (BBC)]<br />
* [https://www.youtube.com/watch?v=wfy_zdZbTUI Laser cutter - Just Add Sharks]<br />
* [https://www.flickr.com/photos/barnoid/14905261730/ TOG Duck vs BigHak Race]<br />
* [https://www.youtube.com/watch?v=tualAybVbT4 Camp Holland Timelapse]<br />
* [[Installations:TheGrid|TheGrid]]: [https://www.youtube.com/watch?v=bbUKrVY6BFA Me] ([[User:Pikesley|Pikesley]]) (also [http://share.gifyoutube.com/YO1GMG.gif as a gif]), and [https://vine.co/v/OB5z299EjUW Ulrich] ([[User:Rico|Rico]])<br />
* [https://www.flickr.com/photos/barnoid/15115548641/ Arriving on golf cart trailer]<br />
* [https://www.youtube.com/watch?v=K_kjqArTKww Bar Bot]<br />
* [https://www.youtube.com/watch?v=kcrgaEGLusY More Bar Bot]<br />
* [https://www.youtube.com/watch?v=8XTEpqlPzjE EMF Camp Saturday Aerial Tour]<br />
* [https://www.youtube.com/watch?v=DFlOloCsxuA Rabbit The Soul Eater]<br />
* [https://www.youtube.com/watch?v=x5KH4bUt8X8 Tom Scott's bit on the alcohol fogger]<br />
<br />
===Audio Recordings===<br />
* "Spray Whisky On Me" EMFM Radio Show: it is doubtful we can publish the copyrighted songs but I hope to edit a copy of the 2am Sunday morning show when it is available.</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Memories&diff=3577Memories2014-09-04T15:26:15Z<p>Ms7821: /* Articles */</p>
<hr />
<div>{{link-banner}}<br />
Please add links to any photos, videos, etc. of EMF2014 you have ([https://wiki-archive.emfcamp.org/2012/articles/d/o/c/Documentation.html like we did in 2012]).<br />
<br />
__TOC__<br />
<br />
Please add links in the following format:<br />
<br />
<nowiki>*[https://www.emfcamp.org EMF Website]</nowiki><br />
<br />
This would look like:<br />
<br />
*[https://www.emfcamp.org EMF Website]<br />
<br />
==Before Event==<br />
Set up, planning, etc.<br />
<br />
===Articles===<br />
*[http://hackaday.com/2014/08/16/tilda-mke-the-emf-2014-badge/ Hackaday on the badge]<br />
*[http://makezine.com/2014/08/15/the-amazing-emf-conference-badge/ Make magazine on the badge]<br />
*[http://www.arrl.org/news/view/emf-2014-it-takes-an-amateur-radio-village ARRL: It Takes an Amateur Radio Village]<br />
===Photos===<br />
*[https://www.flickr.com/photos/chaoticeunoia/15047294495/ Kitty's photographs incl take down]<br />
<br />
===Videos===<br />
<br />
==During Event==<br />
The event itself.<br />
<br />
===Articles===<br />
*[http://www.bbc.co.uk/news/technology-29011889 Electromagnetic Field: Can geeks get kids into science? (BBC)]<br />
*[http://www.theguardian.com/technology/2014/sep/03/electromagnetic-field-camp-emfcamp-drones-arduino-burning-man Electromagnetic Field: the UK's Burning Man? (The Guardian)]<br />
*[https://storify.com/pikesley/things-i-overheard-at-emf-camp-2014 Overheard at EMF2014]<br />
*[https://storify.com/pikesley/how-to-emf How to EMF]<br />
*[http://motherboard.vice.com/read/the-emojli-creators-say-you-shouldnt-make-an-app The Creators of Emojli: Don't Build an App (Motherboard/Vice)]<br />
*[http://motherboard.vice.com/read/inside-uks-electromagnetic-field-festival Not Your 'Traditional Hacker Camp': Inside Electromagnetic Field Festival (Motherboard/Vice)]<br />
*[http://motherboard.vice.com/read/a-call-for-geeks-to-hijack-politics The British MP Who Wants Geeks to Hijack the Politics of Surveillance (Motherboard/Vice)]<br />
*[http://jhaand.nl/2014/09/emf2014-electro-magnetic-fields-hacker-festival-2014/ #EMF2014 (ELECTRO MAGNETIC FIELDS HACKER FESTIVAL 2014)]<br />
*[http://squirmelia.livejournal.com/453051.html Glitch Art Workshop]<br />
<br />
===Photos===<br />
If you have uploaded any photos to Flickr, we would love if you also add them to the group - [https://flic.kr/g/pGAy6]<br />
<br />
*[https://plus.google.com/photos/113943934552095226264/albums/6054537668273419873 Saturday] - [[User:TCMSLP|TCMSLP]]<br />
*[https://twitter.com/search?q=emfcamp&src=typd&mode=photos Twitter photos]<br />
*[https://plus.google.com/photos/+MatthewCopperwaite/albums/6053636538009652657 Friday] [https://plus.google.com/photos/+MatthewCopperwaite/albums/6053636954715546161 Saturday] [https://plus.google.com/u/0/photos/+MatthewCopperwaite/albums/6054110412172875841 Sunday] - [[User:YaMatt|YaMatt]] ([[User talk:YaMatt|talk]])<br />
*[https://plus.google.com/photos/112777126606198038716/albums/6054213887214967841?authkey=CJinnqObgtShMw Various photos including Kite mapping, The Grid and drone wars]<br />
*[https://www.flickr.com/photos/matstace/sets/72157647043339236/ matstace's flickr ]<br />
*[https://plus.google.com/u/0/b/107012837690078606602/photos/107012837690078606602/albums/6054051185457665105 LPRS & The Real Wireless Mike]<br />
* [[Installations:TheGrid|TheGrid]]: I (Cillian) will retweet everything I can find at [https://twitter.com/__thegrid].<br />
* some photospheres: [http://bit.ly/1lwrv26] [http://bit.ly/1redupW] [http://bit.ly/W6ukuE] [http://bit.ly/W6umCI]<br />
* [https://www.flickr.com/photos/barnoid/sets/72157646690458589 Barnoid's photos]<br />
* [https://www.flickr.com/photos/nicecupoftea/sets/72157647140464951/ Libby's photos]<br />
<br />
===Videos===<br />
* [http://www.bbc.co.uk/news/technology-29011898 The most future-proof profession? (BBC)]<br />
* [https://www.youtube.com/watch?v=wfy_zdZbTUI Laser cutter - Just Add Sharks]<br />
* [https://www.flickr.com/photos/barnoid/14905261730/ TOG Duck vs BigHak Race]<br />
* [https://www.youtube.com/watch?v=tualAybVbT4 Camp Holland Timelapse]<br />
* [[Installations:TheGrid|TheGrid]]: [https://www.youtube.com/watch?v=bbUKrVY6BFA Me] ([[User:Pikesley|Pikesley]]) (also [http://share.gifyoutube.com/YO1GMG.gif as a gif]), and [https://vine.co/v/OB5z299EjUW Ulrich] ([[User:Rico|Rico]])<br />
* [https://www.flickr.com/photos/barnoid/15115548641/ Arriving on golf cart trailer]<br />
* [https://www.youtube.com/watch?v=K_kjqArTKww Bar Bot]<br />
* [https://www.youtube.com/watch?v=kcrgaEGLusY More Bar Bot]<br />
* [https://www.youtube.com/watch?v=8XTEpqlPzjE EMF Camp Saturday Aerial Tour]<br />
<br />
===Audio Recordings===<br />
* "Spray Whisky On Me" EMFM Radio Show: it is doubtful we can publish the copyrighted songs but I hope to edit a copy of the 2am Sunday morning show when it is available.</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Memories&diff=3556Memories2014-09-04T09:54:49Z<p>Ms7821: /* Articles */</p>
<hr />
<div>{{link-banner}}<br />
Please add links to any photos, videos, etc. of EMF2014 you have ([https://wiki-archive.emfcamp.org/2012/articles/d/o/c/Documentation.html like we did in 2012]).<br />
<br />
__TOC__<br />
<br />
Please add links in the following format:<br />
<br />
<nowiki>*[https://www.emfcamp.org EMF Website]</nowiki><br />
<br />
This would look like:<br />
<br />
*[https://www.emfcamp.org EMF Website]<br />
<br />
==Before Event==<br />
Set up, planning, etc.<br />
<br />
===Articles===<br />
*[http://hackaday.com/2014/08/16/tilda-mke-the-emf-2014-badge/ Hackaday on the badge]<br />
*[http://makezine.com/2014/08/15/the-amazing-emf-conference-badge/ Make magazine on the badge]<br />
*[http://www.arrl.org/news/view/emf-2014-it-takes-an-amateur-radio-village ARRL: It Takes an Amateur Radio Village]<br />
===Photos===<br />
*[https://www.flickr.com/photos/chaoticeunoia/15047294495/ kitty's pics]<br />
===Videos===<br />
<br />
==During Event==<br />
The event itself.<br />
<br />
===Articles===<br />
*[http://www.bbc.co.uk/news/technology-29011889 Electromagnetic Field: Can geeks get kids into science? (BBC)]<br />
*[http://www.theguardian.com/technology/2014/sep/03/electromagnetic-field-camp-emfcamp-drones-arduino-burning-man Electromagnetic Field: the UK's Burning Man? (The Guardian)]<br />
*[https://storify.com/pikesley/things-i-overheard-at-emf-camp-2014 Overheard at EMF2014]<br />
*[https://storify.com/pikesley/how-to-emf How to EMF]<br />
*[http://motherboard.vice.com/read/the-emojli-creators-say-you-shouldnt-make-an-app The Creators of Emojli: Don't Build an App (Motherboard/Vice)]<br />
*[http://motherboard.vice.com/read/inside-uks-electromagnetic-field-festival Not Your 'Traditional Hacker Camp': Inside Electromagnetic Field Festival (Motherboard/Vice)]<br />
*[http://jhaand.nl/2014/09/emf2014-electro-magnetic-fields-hacker-festival-2014/ #EMF2014 (ELECTRO MAGNETIC FIELDS HACKER FESTIVAL 2014)]<br />
<br />
===Photos===<br />
If you have uploaded any photos to Flickr, we would love if you also add them to the group - [https://flic.kr/g/pGAy6]<br />
<br />
*[https://plus.google.com/photos/113943934552095226264/albums/6054537668273419873 Saturday] - [[User:TCMSLP|TCMSLP]]<br />
*[https://twitter.com/search?q=emfcamp&src=typd&mode=photos Twitter photos]<br />
*[https://plus.google.com/photos/+MatthewCopperwaite/albums/6053636538009652657 Friday] [https://plus.google.com/photos/+MatthewCopperwaite/albums/6053636954715546161 Saturday] [https://plus.google.com/u/0/photos/+MatthewCopperwaite/albums/6054110412172875841 Sunday] - [[User:YaMatt|YaMatt]] ([[User talk:YaMatt|talk]])<br />
*[https://plus.google.com/photos/112777126606198038716/albums/6054213887214967841?authkey=CJinnqObgtShMw Various photos including Kite mapping, The Grid and drone wars]<br />
*[https://www.flickr.com/photos/matstace/sets/72157647043339236/ matstace's flickr ]<br />
*[https://plus.google.com/u/0/b/107012837690078606602/photos/107012837690078606602/albums/6054051185457665105 LPRS & The Real Wireless Mike]<br />
* [[Installations:TheGrid|TheGrid]]: I (Cillian) will retweet everything I can find at [https://twitter.com/__thegrid].<br />
* some photospheres: [http://bit.ly/1lwrv26] [http://bit.ly/1redupW] [http://bit.ly/W6ukuE] [http://bit.ly/W6umCI]<br />
* [https://www.flickr.com/photos/barnoid/sets/72157646690458589 Barnoid's photos]<br />
* [https://www.flickr.com/photos/nicecupoftea/sets/72157647140464951/ Libby's photos]<br />
<br />
===Videos===<br />
* [http://www.bbc.co.uk/news/technology-29011898 The most future-proof profession? (BBC)]<br />
* [https://www.youtube.com/watch?v=wfy_zdZbTUI Laser cutter - Just Add Sharks]<br />
* [https://www.flickr.com/photos/barnoid/14905261730/ TOG Duck vs BigHak Race]<br />
* [https://www.youtube.com/watch?v=tualAybVbT4 Camp Holland Timelapse]<br />
* [[Installations:TheGrid|TheGrid]]: [https://www.youtube.com/watch?v=bbUKrVY6BFA Me] ([[User:Pikesley|Pikesley]]) (also [http://share.gifyoutube.com/YO1GMG.gif as a gif]), and [https://vine.co/v/OB5z299EjUW Ulrich] ([[User:Rico|Rico]])<br />
* [https://www.flickr.com/photos/barnoid/15115548641/ Arriving on golf cart trailer]<br />
* [https://www.youtube.com/watch?v=K_kjqArTKww Bar Bot]<br />
* [https://www.youtube.com/watch?v=8XTEpqlPzjE EMF Camp Saturday Aerial Tour]<br />
<br />
===Audio Recordings===<br />
* "Spray Whisky On Me" EMFM Radio Show: it is doubtful we can publish the copyrighted songs but I hope to edit a copy of the 2am Sunday morning show when it is available.</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Network&diff=2831Network2014-08-23T14:57:03Z<p>Ms7821: /* Firewall */</p>
<hr />
<div>== Network ==<br />
<br />
[[Team:NOC]] has tried to build and support the fastest network for you, a network comparable to a medium sized ISP built up in just a couple of days. It might not be perfect all the time. If you experience any outage please report them to the [[Team:InfoHelpDesk|helpdesk]].<br />
<br />
We will be providing a high speed onsite network with blanket wireless coverage and wired network access to both venues and camping tents.<br />
<br />
== Uplink ==<br />
<br />
Uplink from the campsite is currently being arranged. Details will be announced when firm.<br />
<br />
== Wireless ==<br />
<br />
The whole field has been covered with many wireless access points to ensure the best possible coverage and to allow you to roam seamlessly without interruption. Naturally, there is additional coverage in popular areas such as the talk tents.<br />
<br />
The following SSIDs will be available:<br />
<br />
* emfcamp<br />
** This is 5GHz and should you should use this one in preference, if you can see it. The username and password are "emf". This is the most secure, WPA2-Enterprise.<br />
* emfcamp-legacy<br />
** This is 2.4GHz and less resistant to interference, use it only if you have to. The username and password are "emf". This is also WPA2-Enterprise.<br />
* emfcamp-insecure '''Warning: insecure'''<br />
** This is both 5GHz and 2.4GHz, and is for older devices that don't support WPA2-Enterprise. It's unencrypted.<br />
* spacenet<br />
** This is 2.4GHz + 5GHz and WPA2-Enterprise, you can connect with a valid account if your hackerspace is offering spacenet. More information can be found at [https://spacefed.net/ spacefed.net].<br />
* eduroam<br />
** This is 2.4GHz + 5GHz and WPA2-Enterprise, you can connect with a valid account if your university/college/school is offering eduroam. More information can be found at [https://www.eduroam.org/ eduroam.org].<br />
<br />
Use of the 5GHz SSIDs is recommended if your device supports them. 802.11b is disabled as it slows everyone else down.<br />
<br />
Even if you are using an encrypted network, you should still [[#Encryption|encrypt any sensitive traffic]] sent over the air end-to-end to prevent snooping. Although some SSIDs offer encryption, it is only over-the-air.<br />
<br />
We have airtime fairness configured on our wireless controllers, so if you wish to download large files please use a wired connection (there will be plenty about).<br />
<br />
For proper wireless support under linux, you should have a kernel newer than 2.6.39.2. There is also a kernel panic with brcmsmac on linux 3.10.3 that can be fixed by downgrading to kernel 3.10.2.<br />
<br />
=== WPA2 802.1X, encryption ===<br />
Due to popular demand (and with security in mind) we provide WPA2 802.1X. This will encrypt your traffic, preventing attackers from sniffing your data. Keep in mind that this won't protect you from other network attacks and you should still be aware that you are at a hacker conference! Your link layer should be secure if you do certificate checking (see below).<br />
<br />
You might think: "WTF!? Do I need to register a user and password blah, blah". Fortunately not. You can '''use any username/password combination using EAP-TTLS with PAP to login''' (example: "user: fbhfbhiaf pass: bgufwbnkqo" is valid), because we don't care who logs in and who you are. We just want to encrypt your data.<br />
<br />
Users which use MSCHAPv2 (like Windows users with default 802.1X supplicant) should use a fixed username and password. You can use "emf/emf" or "guest/guest" as "username/password".<br />
<br />
==== Client Settings ====<br />
SSID: emfcamp or emfcamp-legacy<br />
Phase 1: EAP-TTLS or PEAP<br />
Phase 2: MSCHAPv2 or EAP-MSCHAPv2 or PAP<br />
<br />
CN = radius.emf.camp<br />
CA = GeoTrust Global CA<br />
Fingerprint = 5E:A7:65:99:25:14:46:A4:0A:CD:2D:22:27:C1:1B:70:AA:A0:CC:1F<br />
<br />
Make sure '''you check the certificate''' in order to know you are connecting to the correct network (you should check on both the CN and the CA).<br />
<br />
== Camping area and workshops ==<br />
<br />
All camping areas will be within 60m of a Datenklo (Data Toilet), please bring around 60-70m of CAT5 cable. Unless a sponsor comes forward for it, we will be unable to supply cable on site. We will be budgeting only for the infrastructure requirements and necessary spares to deal with issues.<br />
<br />
Lay your own cable neatly from your tent back to the nearest Datenklo, and leave 6m of slack coiled on the floor in front of it. And please lay it so that it can be clearly seen that it needs to be plugged in - or you risk having your cable overlooked. At regular intervals a member of the NOC team will connect it up and enable the port.<br />
<br />
If you wish to be removed from a Datenklo again, contact the [[Team:InfoDesk|helpdesk]] directly.<br />
<br />
All of our edge ports are at least 10/100, some support PoE (802.3af), plus Auto-MDX.<br />
<br />
== Static IPs ==<br />
<br />
If you need a static IP on the wired network, drop by the [[Team:InfoDesk]].<br />
<br />
== Rules ==<br />
<br />
* Be nice and friendly! Do not do to others what you do not wish done to yourself.<br />
* Protect your computer! We cannot be taken responsible or held accountable for any damage your devices might sustain due to security problems, power spikes and other such perils.<br />
* Please do not operate your own WiFi access point, our wireless solution includes 'CleanAir' technology and has rogue access point detection.<br />
* If you are operating anything else in the 2.4GHz spectrum, please clear the frequencies in advance with us.<br />
* Do not attempt to run a DHCP or RA server. You will be found and named and shamed!<br />
* Cabling from your tent to the data toilets must not cross any roads.<br />
* If you are connecting a Nanode / Arduino Ethernet / other microcontroller to the network please make sure it is using a unique MAC address. Many of the code examples for such devices use an identical MAC address and this will cause problems - if you aren't sure contact the [[Team:InfoDesk|helpdesk]].<br />
* If you are connecting a switch, you need to contact the NOC to enable this on your port. You are only allowed one uplink from your switch to our network - do not attempt to connect multiple cables or to multiple DKs!<br />
<br />
If you break these rules, we will track you down or triangulate you, but we'd rather spend the time maintaining the smooth operation of the network, so please don't waste our time. And if you think [[Team:NOC]] cannot locate you just because you're wireless - think again. ;-)<br />
<br />
== IPv6 ==<br />
<br />
Naturally, IPv6 is available throughout the network and should "just work" for you. Team:NOC does not recommend disabling IPv6 if you have problems, instead try to understand the problem you are experiencing and get educated in the new world order. Contact the [[Team:InfoDesk|NOC helpdesk]] if you need help.<br />
<br />
== Multicast ==<br />
<br />
In 2012 we ran multicast with a feed from the BBC. This worked quite well; you could simply open your media player and browse multicast streams (e.g. in VLC "Local Network -> Network Streams (SAP)"). We'll try to do the same again this year, details will appear here.<br />
<br />
== Services ==<br />
<br />
* DNS: 78.158.87.11 and 78.158.87.12<br />
* NTP: 78.158.87.11 and 78.158.87.12 (ntp1.emf.camp and ntp2.emf.camp)<br />
* Nearest Debian mirror: http://debian.mirror.uk.sargasso.net<br />
* Content distribution server - for use by speakers to upload their content to an on-site server - http://content.emf.camp/ . Speakers please contact noc@ to get an account.<br />
<br />
== Security ==<br />
<br />
=== Recent vulnerabilities ====<br />
<br />
: '''WARNING: Bring a recent DHCP Client'''. If your OS uses ISC DHCP dhclient make sure you don't run a vulnerable version. https://www.kb.cert.org/vuls/id/410676<br />
<br />
=== Encryption ===<br />
<br />
Please treat the network as wide open and full of attackers. Although [[Team:NOC]] themselves will not monitor the network, always assume that Alice flirting with Bob will be spied upon by The Third Party.<br />
<br />
Any sensitive information including passwords must therefore be encrypted. Please make sure you don't use any software or web applications that send sensitive data or passwords in the clear.<br />
<br />
The following mechanisms should be safe:<br />
* Anything that goes through a VPN<br />
* Any website that uses HTTPS<br />
* Any application that uses SSL<br />
** In the case of email, you need to have SSL enabled for both receiving mail (POP, IMAP) and sending it (SMTP)<br />
* ssh and scp<br />
* Where possible, use One-time passwords. Real tokens work best, many of those should be compatible with open source radius servers. [http://perlmonks.org/?node=967433 Here] is a simple Perl radius server implementation for [http://tools.ietf.org/html/rfc6238 RFC6238] tokens that works with ssh and other stuff on linux.<br />
<br />
The following are almost always unsafe:<br />
<br />
* FTP with login/password (are almost always sent in the clear)<br />
* Telnet with login/password<br />
* Email if you don't use SSL<br />
* Webmail that doesn't use HTTPS<br />
** Someone could trigger a password reminder and then intercept your email<br />
* Websites that use HTTP (not HTTPS) where you need to fill in a password in the page itself<br />
<br />
Possibly unsafe, make sure that you understand what you're doing:<br />
<br />
* Websites where you need to fill in a password and your ''browser'' (not the website!) tells you it's going to be sent securely<br />
* Websites that require an account but remember you're logged in<br />
** The password ''may'' be protected but not the content or cookies that automatically log you in<br />
* Any time your browser or other application brings up ''anything'' to do with a certificate<br />
* Anything not protected with SSL: someone could be faking DNS answers to impersonate certain sites<br />
<br />
Remember: if you're being stupid someone may feel the need to teach you a security lesson in a not so subtle way! (No, that doesn't mean it's ok to hack people just to see if their security is in order.)<br />
<br />
=== Firewall ===<br />
<br />
There is no network firewall. We operate an unfiltered network that is wide open to the Internet. There is no NAT, and everybody has a public IP address. This is our definition of "network neutrality" - a network that doesn't do anything whatsoever to your IP connection.<br />
<br />
If you are used to feeling secure just because you've been sitting behind a NAT router, think again. You are now wide open to the whole Internet. Ensure your personal firewall is enabled and set to "Public Network" and that you have applied all security updates to your OS and applications.<br />
<br />
== FAQ ==<br />
<br />
=== Can I bring a server? ===<br />
<br />
<strike>Yes, though we would rather these were stored centrally in our NOC. This allows us to provision power easily and you also get the added benefit of connecting directly to our core and having UPS backup. If you intend to bring a server please email noc@emfcamp.org so we can fully understand your requirements prior to the event.</strike><br />
<br />
We have not yet determined whether we will be able to provide colocation space for servers, but we would like to in order to save bandwidth on the extensive site network. If this will be helpful for you, please e-mail noc@emfcamp.org so we can gauge demand.<br />
<br />
=== Can I use the 2.4GHz band for non-wifi projects? ===<br />
<br />
The following channels are available for adhoc/mesh/other wireless stuff:<br />
<br />
* 2.4Ghz: Channel 1 <br />
* 5Ghz: Channel 136, 140<br />
<br />
We cannot force you to use these channels, but we are trying to build a functional wireless network for the other attendees too. So please, don't do any experiments on other channels.<br />
<br />
=== Can I bring an access point? ===<br />
<br />
No, this is strictly prohibited! We need all available channels to provide good quality coverage for the rest of the attendees. Please do not be selfish here as you will degrade performance for everyone else, and we WILL track you down.<br />
<br />
If you are operating a village (using an EMF-supplied tent) that has poor coverage, we may be able to arrange to put an access point in it during the event to improve coverage. Stop by the NOC and ask.<br />
<br />
=== Can I bring a switch? ===<br />
<br />
Yes, but for stability purposes all edge ports are limited to 3 MAC addresses at a time. If you want to connect a switch, you need to stop by the NOC and ask us to lift the port-security on your port. If you do this, you need to convince us that you know what you're doing and promise not to do anything that may harm the network - in particular, you must not connect the switch to our network by more than 1 cable (not even to a different DK).<br />
<br />
=== My port goes up and down every couple of minutes ===<br />
<br />
You have probably tripped port security. Most likely scenario is that you have connected a switch without consulting us (see answer to previous question).<br />
<br />
== Team Internet ==<br />
<br />
[[User:JasperWallace]]<br />
[[User:Will-h]]<br />
[[User:Davidc]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Traditional_Dutch_Cooking_Workshops_and_Nomzing&diff=2796Traditional Dutch Cooking Workshops and Nomzing2014-08-22T23:03:50Z<p>Ms7821: /* Friday: King-size pannenkoeken (Dutch pancakes) */</p>
<hr />
<div>We'll be cooking some traditional Dutch dishes at [[Villages:Village:Camp_Holland|Camp Holland]]. Why? Because we can, and sharing food is fun!<br />
<br />
==What?==<br />
We'll cook food, tell you how to make it yourself, and let you eat it.<br />
<br />
'''Please pledge to pay and be present by putting your name in the tables below, and sending an e-mail to [mailto:diggie@ohm2013.org diggie@ohm2013.org] so he can send you a payment request. Please do this before 25 August, so we know how much food to bring over from #Holland'''<br />
<br />
==Location==<br />
Somewhere near [[Villages:Village:Camp_Holland|Camp Holland]]. We'll let you know.<br />
<br />
<br />
==Schedule==<br />
<br />
===Friday: King-size pannenkoeken (Dutch pancakes) ===<br />
'''Type:''' Workshop & pancake party<br><br />
'''Start time:''' Around 17:00<br><br />
'''Price:''' &pound; 2 per pancake (&empty;42 cm!! These easily feed one generic-sized adult)<br><br />
'''Status:''' <span style="color:red">Not enough pledges yet (Pledge below!)</span><br><br />
Toppings include bacon, cheese, strawberry jam, [http://nl.wikipedia.org/wiki/Stroop stroop], sugar, etc.<br><br />
{|class="sortable wikitable"<br />
!User<br />
|-<br />
| [[User:diggie|diggie]]<br />
|-<br />
| [[User:Jos|Jos]]<br />
|-<br />
| [[User:Eightdot|Eightdot]]<br />
|-<br />
| [[User:Lurwah|Users:User:Lurwah]]<br />
|-<br />
| [[User:gmc|Users:User:gmc]]<br />
|-<br />
| [[User:Msemtd|Michael Erskine]]<br />
|-<br />
| [[User:BugBlue|BugBlue]] ([[User talk:BugBlue|talk]])<br />
|-<br />
| [[User:JHR|JHR]]<br />
|-<br />
| [[User:Sully|Sully]]<br />
|-<br />
| [[User:Oly|Oly]]<br />
|-<br />
| [[User:Ms7821|Mark]]<br />
|-<br />
| [[User:Maow|Maow]]<br />
|-<br />
| (Your name here...) Lazy users just type <nowiki>~~~</nowiki><br />
|}<br />
<br />
===Saturday: Frituur (deep-fried stuff)===<br />
'''Type:''' Snackbar<br><br />
'''Time:''' Around 18:00<br><br />
'''Price:''' &pound; 4 per person (all you can eat)<br><br />
'''Status:''' <span style="color:orange">Pretty sure this will happen</span><br><br />
As common as pie in The Netherlands, we'll make fries, [http://nl.wikipedia.org/wiki/Kroket kroketten], [http://nl.wikipedia.org/wiki/Frikadel frikandellen], [http://nl.wikipedia.org/wiki/Kaassouffle kaassouffle's]. With real Dutch Mayonnaise.<br><br />
{|class="sortable wikitable"<br />
!User<br />
|-<br />
| [[User:diggie|diggie]]<br />
|-<br />
| [[User:Jos|Jos]]<br />
|-<br />
| [[User:Eightdot|Eightdot]]<br />
|-<br />
| [[User:gmc|Users:User:gmc]]<br />
|-<br />
| [[User:BugBlue|BugBlue]] ([[User talk:BugBlue|talk]])<br />
|-<br />
| [[User:Sully|Sully]]<br />
|-<br />
| [[User:Vreemt|Vreemt]]<br />
|-<br />
| Matthew<br />
|-<br />
| [[User:JHR|JHR]]<br />
|-<br />
| (Your name here...) Lazy users just type <nowiki>~~~</nowiki><br />
|}<br />
<br />
===Sunday (afternoon): Erwtensoep (Green pea soup)===<br />
'''Type:''' Workshop & tasting session<br><br />
'''Start time:''' Around 15:00 (as it needs some time to cook)<br><br />
'''Price:''' &pound; 2 per participant (you'll get at least one portion of the soup)<br><br />
'''Status:''' <span style="color:orange">Almost there... (Pledge below!)</span><br><br />
With [http://nl.wikipedia.org/wiki/Rookworst rookworst], bacon, [http://nl.wikipedia.org/wiki/Roggebrood roggebrood] with [http://nl.wikipedia.org/wiki/Katenspek cooked bacon], and much more<br><br />
{|class="sortable wikitable"<br />
!User<br />
|-<br />
| [[User:diggie|diggie]]<br />
|-<br />
| [[User:Jos|Jos]]<br />
|-<br />
| [[User:Eightdot|Eightdot]]<br />
|-<br />
| [[User:gmc|Users:User:gmc]]<br />
|-<br />
| [[User:BugBlue|BugBlue]] ([[User talk:BugBlue|talk]])<br />
|-<br />
| [[User:Vreemt|Vreemt]] (just me)<br />
|-<br />
| (Your name here...) Lazy users just type <nowiki>~~~</nowiki><br />
|}<br />
<br />
===Sunday (evening): Braai (BBQ)===<br />
'''Type:''' Just eating (gezellig!)<br><br />
'''Time:''' Around 19:00 or so<br><br />
'''Price:''' &pound; 10 per participant (all you can eat)<br><br />
'''Status:''' <span style="color:green">This will happen</span><br><br />
{|class="sortable wikitable"<br />
!User<br />
|-<br />
| [[User:diggie|diggie]]<br />
|-<br />
| [[User:Jos|Jos]]<br />
|-<br />
| [[User:Eightdot|Eightdot]]<br />
|-<br />
| [[User:gmc|Users:User:gmc]]<br />
|-<br />
| [[User:BugBlue|BugBlue]] ([[User talk:BugBlue|talk]])<br />
|-<br />
| [[User:Jos|Jos]]<br />
|-<br />
| [[User:Oly|Oly]]<br />
|-<br />
| [[User:Vreemt|Vreemt]]<br />
|-<br />
| Matthew<br />
|-<br />
| (Your name here...) Lazy users just type <nowiki>~~~</nowiki><br />
|}</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Traditional_Dutch_Cooking_Workshops_and_Nomzing&diff=2795Traditional Dutch Cooking Workshops and Nomzing2014-08-22T23:02:13Z<p>Ms7821: /* Friday: King-size pannenkoeken (Dutch pancakes) */</p>
<hr />
<div>We'll be cooking some traditional Dutch dishes at [[Villages:Village:Camp_Holland|Camp Holland]]. Why? Because we can, and sharing food is fun!<br />
<br />
==What?==<br />
We'll cook food, tell you how to make it yourself, and let you eat it.<br />
<br />
'''Please pledge to pay and be present by putting your name in the tables below, and sending an e-mail to [mailto:diggie@ohm2013.org diggie@ohm2013.org] so he can send you a payment request. Please do this before 25 August, so we know how much food to bring over from #Holland'''<br />
<br />
==Location==<br />
Somewhere near [[Villages:Village:Camp_Holland|Camp Holland]]. We'll let you know.<br />
<br />
<br />
==Schedule==<br />
<br />
===Friday: King-size pannenkoeken (Dutch pancakes) ===<br />
'''Type:''' Workshop & pancake party<br><br />
'''Start time:''' Around 17:00<br><br />
'''Price:''' &pound; 2 per pancake (&empty;42 cm!! These easily feed one generic-sized adult)<br><br />
'''Status:''' <span style="color:red">Not enough pledges yet (Pledge below!)</span><br><br />
Toppings include bacon, cheese, strawberry jam, [http://nl.wikipedia.org/wiki/Stroop stroop], sugar, etc.<br><br />
{|class="sortable wikitable"<br />
!User<br />
|-<br />
| [[User:diggie|diggie]]<br />
|-<br />
| [[User:Jos|Jos]]<br />
|-<br />
| [[User:Eightdot|Eightdot]]<br />
|-<br />
| [[User:Lurwah|Users:User:Lurwah]]<br />
|-<br />
| [[User:gmc|Users:User:gmc]]<br />
|-<br />
| [[User:Msemtd|Michael Erskine]]<br />
|-<br />
| [[User:BugBlue|BugBlue]] ([[User talk:BugBlue|talk]])<br />
|-<br />
| [[User:JHR|JHR]]<br />
|-<br />
| [[User:Sully|Sully]]<br />
|-<br />
| [[User:Oly|Oly]]<br />
|-<br />
| [[User:Ms7821|Mark]]<br />
|-<br />
| (Your name here...) Lazy users just type <nowiki>~~~</nowiki><br />
|}<br />
<br />
===Saturday: Frituur (deep-fried stuff)===<br />
'''Type:''' Snackbar<br><br />
'''Time:''' Around 18:00<br><br />
'''Price:''' &pound; 4 per person (all you can eat)<br><br />
'''Status:''' <span style="color:orange">Pretty sure this will happen</span><br><br />
As common as pie in The Netherlands, we'll make fries, [http://nl.wikipedia.org/wiki/Kroket kroketten], [http://nl.wikipedia.org/wiki/Frikadel frikandellen], [http://nl.wikipedia.org/wiki/Kaassouffle kaassouffle's]. With real Dutch Mayonnaise.<br><br />
{|class="sortable wikitable"<br />
!User<br />
|-<br />
| [[User:diggie|diggie]]<br />
|-<br />
| [[User:Jos|Jos]]<br />
|-<br />
| [[User:Eightdot|Eightdot]]<br />
|-<br />
| [[User:gmc|Users:User:gmc]]<br />
|-<br />
| [[User:BugBlue|BugBlue]] ([[User talk:BugBlue|talk]])<br />
|-<br />
| [[User:Sully|Sully]]<br />
|-<br />
| [[User:Vreemt|Vreemt]]<br />
|-<br />
| Matthew<br />
|-<br />
| [[User:JHR|JHR]]<br />
|-<br />
| (Your name here...) Lazy users just type <nowiki>~~~</nowiki><br />
|}<br />
<br />
===Sunday (afternoon): Erwtensoep (Green pea soup)===<br />
'''Type:''' Workshop & tasting session<br><br />
'''Start time:''' Around 15:00 (as it needs some time to cook)<br><br />
'''Price:''' &pound; 2 per participant (you'll get at least one portion of the soup)<br><br />
'''Status:''' <span style="color:orange">Almost there... (Pledge below!)</span><br><br />
With [http://nl.wikipedia.org/wiki/Rookworst rookworst], bacon, [http://nl.wikipedia.org/wiki/Roggebrood roggebrood] with [http://nl.wikipedia.org/wiki/Katenspek cooked bacon], and much more<br><br />
{|class="sortable wikitable"<br />
!User<br />
|-<br />
| [[User:diggie|diggie]]<br />
|-<br />
| [[User:Jos|Jos]]<br />
|-<br />
| [[User:Eightdot|Eightdot]]<br />
|-<br />
| [[User:gmc|Users:User:gmc]]<br />
|-<br />
| [[User:BugBlue|BugBlue]] ([[User talk:BugBlue|talk]])<br />
|-<br />
| [[User:Vreemt|Vreemt]] (just me)<br />
|-<br />
| (Your name here...) Lazy users just type <nowiki>~~~</nowiki><br />
|}<br />
<br />
===Sunday (evening): Braai (BBQ)===<br />
'''Type:''' Just eating (gezellig!)<br><br />
'''Time:''' Around 19:00 or so<br><br />
'''Price:''' &pound; 10 per participant (all you can eat)<br><br />
'''Status:''' <span style="color:green">This will happen</span><br><br />
{|class="sortable wikitable"<br />
!User<br />
|-<br />
| [[User:diggie|diggie]]<br />
|-<br />
| [[User:Jos|Jos]]<br />
|-<br />
| [[User:Eightdot|Eightdot]]<br />
|-<br />
| [[User:gmc|Users:User:gmc]]<br />
|-<br />
| [[User:BugBlue|BugBlue]] ([[User talk:BugBlue|talk]])<br />
|-<br />
| [[User:Jos|Jos]]<br />
|-<br />
| [[User:Oly|Oly]]<br />
|-<br />
| [[User:Vreemt|Vreemt]]<br />
|-<br />
| Matthew<br />
|-<br />
| (Your name here...) Lazy users just type <nowiki>~~~</nowiki><br />
|}</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=EMF_Milliways_Dome_Pledge&diff=2789EMF Milliways Dome Pledge2014-08-22T20:25:08Z<p>Ms7821: </p>
<hr />
<div>At every hacker/maker camp in europe you'll find Milliways, the restaurant at the end of the universe. Or in our case the end of the field.<br />
<br />
Milliways are a volunteer run kitchen who tour around the camps cooking for anybody who wants food in return for donations. They have a full kitchen and even bake bread in the middle of the camp! This year Milliways are helping EMF by providing food and cooking equipment to all our set-up and tear-down volunteers, as well as reprising their usual role as a fun place to hang out and get fed. In return, EMF is providing a large marquee for them.<br />
<br />
Milliways have an AWESOME giant geodesic dome they bring to the camps to use as shelter - both for people eating, and for people to relax under in the evening. They're bringing it over from Germany but it costs a lot of money to do so. We'd really like to help them out but the EMF budget is totally exhausted, so we're having a whip-round to try and raise a bit more money.<br />
<br />
If you'd like to sit under a massive geodesic dome and drink beer next weekend, please donate a little money to the cause.<br />
<br />
<br />
'''Plan:''' Try and raise some money to help cover Milliways costs bringing over a huge geodesic dome<br />
<br />
'''Costings:''' They're already paying for it, but we'd like to raise £500 to help them out<br />
<br />
'''Pledges''' (please edit to add your support)<br />
* £25 - Jontyw<br />
* £20 - Jane C<br />
* £5 - --[[User:Msemtd|Msemtd]] ([[User talk:Msemtd|talk]]) 14:53, 22 August 2014 (UTC)<br />
* £50 - [[User:Ms7821|Mark]]<br />
* £20 - [[User:ens|ens]]<br />
* £30 - Crypt<br />
* £20 - [[User:gmc|Users:User:gmc]]<br />
* £10 - [[User:Markp]]<br />
* £25 - Cathy A<br />
* £20 - Rich C<br />
* £10 - [[User:Dpslwk|Matt L]]<br />
* £20 - SleepyCal (Cal Leeming)<br />
* £25 - [[User:Sde|Steve E]]<br />
<br />
'''Total: £280'''</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Villages:Amateur_Radio&diff=2776Villages:Amateur Radio2014-08-22T15:36:04Z<p>Ms7821: /* Manual list */</p>
<hr />
<div>{{Village<br />
|Name=Amateur Radio<br />
|Picture=Radiotowerhi.png<br />
|Description=ham radio at it's finest.<br />
|Contact=Paul<br />
|Activities=Radio... durr<br />
|Location=51.967000, -0.793989<br />
}}<br />
<br />
Moved from [[radio]]<br />
<br />
'''We have a [https://lists.emfcamp.org/listinfo/hamradio mailing list] - please subscribe!<br />
'''<br />
<br />
==Things to during EMF==<br />
===Radio Village Workshops/Talks===<br />
We plan on running some small talks/workshops on a fairly informal basis, these will include: <br />
* Introduction to software defined radio - Dominic<br />
* Something TBD - Paul<br />
* Amateur Radio: The Original Nerd Hobby - Ryan Sayre (2E0RYS / KG7NMC)<br />
* <span style="color: red;">YOUR_TALK_HERE</span><br />
<br />
===Contests===<br />
During EMF the following contests will be running<br />
<br />
http://www.hornucopia.com/contestcal/contestdetails.php?ref=99<br />
<br />
http://www.hornucopia.com/contestcal/contestdetails.php?ref=98<br />
<br />
http://www.hornucopia.com/contestcal/contestdetails.php?ref=101<br />
<br />
===Special Event Station===<br />
Paul (M0OKE) has applied for an NoV for a special call sign for a special event station, '''[[GB2EMF]]'''. <br />
<br />
This has been granted.<br />
<br />
Colin (G8TMV) has organised RSGB posters and info leaflets.<br />
<br />
===Talk In===<br />
Talk in has been suggested on 2/70 on Friday. Operator(s) required. Assuming 145.550 MHz.<br />
<br />
===Modes & Bands===<br />
<br />
Steve M0SPN intends to run Voice, PSK and SSTV on HF. VHF/UHF dependent on availability of masts and beams.<br />
<br />
Iain MM6MVQ intends to have an SSTV receiving station operating during EMF on 70cm (exact freq. TBC) that will tweet any images received to a dedicated Twitter account. For details on this, contact [mailto:irl@fsfe.org irl@fsfe.org].<br />
<br />
==Local Stuff==<br />
<br />
===Clubs===<br />
* Milton Keynes ARS (MKARS) are literally just up the road from the campsite - http://www.mkars.org.uk/ <br />
<br />
===Repeaters===<br />
It would be very cool to have a dedicated on-site repeater just for EMF. The practicality wouldn't be too difficult -- M0RND can provide a 2m/70cm colinear (which might be able to be hosted on the main EMF mast), and there's no shortage of radios which can do cross-band repeat, or something could be lashed up with two Baofeng UV-B5 radios and a diplexer.<br />
<br />
The awkward part would be getting an NoV for the repeater, and getting it in time for EMF.<br />
<br />
* Voice - GB3VA http://ukrepeater.net/my_repeater.php?id=997<br />
<br />
* Digital - http://www.ukrepeater.net/repeaters/maps/gb7bp.jpg <br />
<br />
* Digital - http://www.ukrepeater.net/my_repeater.php?id=180<br />
<br />
==Tasks/Status==<br />
<br />
{| class="wikitable"<br />
! Task <br />
! Owner(s) <br />
! Notes<br />
|-<br />
| Village/Station || tgreer?/Everyone! || Organisation of tent, power, network<br />
|-<br />
| Radios || (tbc) || Supply of HF/VHF/UHF gear<sup>1</sup><br />
|-<br />
| Mast(s) || (tbc) || Supply of masts, rotator?<sup>2</sup> * Tgreer has 12m push up mast on his landrover * Hopefully LHS's trailer mast will be ready for then. [https://wiki.london.hackspace.org.uk/view/Project:Mast_Trailer]<br />
|-<br />
| Operators || See below || People volunteering to rotate operation/manning of station<br />
|-<br />
| Special Event Call || Paul M0OKE || [[GB2EMF]] granted by Ofcom<br />
|- <br />
| QSL Cards || Steve M0SPN || Assistance required <sup>3</sup><br />
|- <br />
| GB2RS News || Paul || Emailed, probably a bit late for ticket sales though<br />
|-<br />
| Southgate ARC || ? (no owner) || Already up there!<br />
|-<br />
| TX Factor || Steve M0SPN || Initial contact made (to be passed to jontyw if successful)<br />
|-<br />
| Promo Material || Steve M0SPN || Initial contact made with RSGB, Kenwood, Yaseu, Icom, Moonraker, ML&S<sup>4</sup?<br />
|}<br />
<sup>1</sup> Steve M0SPN has TS450S & PSU available<br />
<br />
<sup>2</sup> Cillian (possible V/UHF yagis), tgreer (possible landrover/mast) <br />
<br />
<sup>3</sup> http://www.centreprint.co.uk/qsl_cards2.htm can deliver in 1-2 weeks, £50 for 250 cards<br />
<br />
<sup>4</sup> Leaflets/posters received from Icom, RSGB.<br />
<br />
==Equipment==<br />
{| class="wikitable"<br />
! style="text-align:left;"| Item<br />
! Amount<br />
! Status<br />
|-<br />
|Army tent thing<br />
|1<br />
|17'6 http://www.rddusa.com/product/gp-small-tent-176-x-176/<br />
|-<br />
|Gazebo<br />
|1<br />
|3x3m with sides - Arrived from Ebay<br />
|-<br />
|Table<br />
|1<br />
|Rental booked<br />
|-<br />
|Chairs<br />
|6<br />
|Rental booked<br />
|-<br />
|Radio<br />
|1<br />
|TS450S (TCMSLP/M0SPN)<br />
|-<br />
|PSU<br />
|1<br />
|25A SMPSU (TCMSLP/M0SPN)<br />
|-<br />
|Antenna<br />
|1<br />
|V/UHF Colinear (TCMSLP/M0SPN)<br />
|-<br />
|Other radios etc...<br />
| <br />
| <br />
|-<br />
|}<br />
<br />
==People==<br />
A list of people who may or may not be going and may or may not be interested in doing things related to amateur radio.<br />
<br />
===Manual list===<br />
* David M0TNR `Cillian' (is going, can bring some radio goodies, but doesn't want to dedicate all weekend to it)<br />
* Adam M0RND<br />
* Colin G8TMV<br />
* Paul M0OKE<br />
* Jon M0JSN<br />
* Gavan 2E0UND<br />
* Steve M0SPN (TCMSLP on #emfcamp)<br />
* Kai DB1SQU (SQUelcher on IRC)<br />
* Kimball 2E1FWL (drrk on IRC)<br />
* Relocker PA1BYL<br />
* Paul M0TZO - bringing D-STAR equipment<br />
* Blake KC9CHL<br />
* Alan MW6ZEC<br />
* Kraptv 2E0RYS (KG7NMC)<br />
* Iain MM6MVQ<br />
* Paul 2E0PGW<br />
* Bill M1DHL (murb on IRC)<br />
* Mark (no valid callsign atm because Ofcom have double-issued it)<br />
<br />
===Villagers===<br />
{{inhabitant}}</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=EMF_Milliways_Dome_Pledge&diff=2766EMF Milliways Dome Pledge2014-08-22T14:59:26Z<p>Ms7821: </p>
<hr />
<div>At every hacker/maker camp in europe you'll find Milliways, the restaurant at the end of the universe. Or in our case the end of the field.<br />
<br />
Milliways are a volunteer run kitchen who tour around the camps cooking for anybody who wants food in return for donations. They have a full kitchen and even bake bread in the middle of the camp! This year Milliways are helping EMF by providing food and cooking equipment to all our set-up and tear-down volunteers, as well as reprising their usual role as a fun place to hang out and get fed. In return, EMF is providing a large marquee for them.<br />
<br />
Milliways have an AWESOME giant geodesic dome they bring to the camps to use as shelter - both for people eating, and for people to relax under in the evening. They're bringing it over from Germany but it costs a lot of money to do so. We'd really like to help them out but the EMF budget is totally exhausted, so we're having a whip-round to try and raise a bit more money.<br />
<br />
If you'd like to sit under a massive geodesic dome and drink beer next weekend, please donate a little money to the cause.<br />
<br />
<br />
'''Plan:''' Try and raise some money to help cover Milliways costs bringing over a huge geodesic dome<br />
<br />
'''Costings:''' They're already paying for it, but we'd like to raise £500 to help them out<br />
<br />
'''Pledges''' (please edit to add your support)<br />
* £25 - Jontyw<br />
* £20 - Jane C<br />
* £5 - --[[User:Msemtd|Msemtd]] ([[User talk:Msemtd|talk]]) 14:53, 22 August 2014 (UTC)<br />
* £50 - [[User:Ms7821|Mark]]<br />
<br />
'''Total: £30'''</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=FAQ&diff=2678FAQ2014-08-22T09:09:20Z<p>Ms7821: /* Ticket Sales */</p>
<hr />
<div>{{link-banner}}<br />
This is a work in progress. Keep checking for updates.<br />
<br />
==General==<br />
===Who are you?===<br />
Electromagnetic Field is run by a non-profit organisation and produced entirely by volunteers. We are members of well-known hackerspaces and other organisations. Get in touch if you want to join us in making this happen.<br />
<br />
===Why are you doing this?===<br />
There now are dozens of hackerspaces and makerspaces in the UK and across Europe, and countless other communities of craftsmen, artists, designers, engineers who are interested in the same DIY ethic; but they have few opportunities to all meet up. Most events catering to these communities are small regional conferences and often focused on very specific themes.<br />
<br />
We want to change that :)<br />
<br />
===Why Milton Keynes?===<br />
We looked at a fair number of candidate sites. The site we ended up with was the best candidate for a number of reasons:<br />
* It comes at a comparably low price (some of the candidate sites we looked at asked for tens of thousands of £££.)<br />
* It has great transport links to much of the UK (both roads and trains.)<br />
* It is close(ish) to a few data centres and high speed Internet uplinks.<br />
* We were there last time and it seemed to work well<br />
Bonus: it is very close to Bletchley Park :)<br />
<br />
===How big is it?===<br />
<br />
In 2012, we had an attendance limit of 500 and fully sold out. This year we are expecting around 1,200 people. Buy your ticket early to avoid disappointment.<br />
<br />
==Ticket Sales==<br />
===How can I get a ticket?===<br />
Tickets are on sale from our web site here:<br />
<br />
'''https://www.emfcamp.org/tickets/choose'''<br />
<br />
This time there will be no day tickets and camp tickets are likely to sell out in advance.<br />
<br />
===How much does it cost?===<br />
Adult tickets are currently £105. There are tickets available for under-16s at a lower price (accompanied by an adult). Children under 5 can attend for free.<br />
<br />
If you have a Camper van you will need a Camper van ticket. <br />
<br />
If you want to bring a car you'll also need a car parking ticket.<br />
<br />
You can pay by bank transfer (in pounds sterling or Euros), a one-time direct debit (in pounds sterling or Euros), or by credit or debit card via Stripe (which charges a small fee).<br />
<br />
===What's the accessibility situation like?===<br />
The site will be well lit during the event, and we will aim to cover access to the stages with trackway. Travelling between stages may take some time, though.<br />
<br />
There will be three accessible toilets and the current plan includes an accessible shower with a wheelchair ramp.<br />
<br />
We cannot guarantee 24/7 power for continuous positive airway pressure (CPAP) devices, but the power infrastructure team will be on call through the night.<br />
<br />
If you will be attending with a carer, they are entitled to a free ticket. Please [mailto:tickets@emfcamp.org email us] in advance so we can allocate the ticket.<br />
<br />
Registered assistance dogs will be allowed.<br />
<br />
If you have any other requirements, please tick the "I have accessibility requirements" checkbox when buying your ticket, and we'll be in touch for details. If you'd like to confirm anything before buying your ticket, please [mailto:tickets@emfcamp.org drop us an email].<br />
<br />
===Can I get a day ticket?===<br />
Sorry, EMF 2012 was sold to capacity and we found that the day tickets prevented people from attending the whole event. For this reason, we can only offer tickets for the whole event. You are welcome to only come to one day, or to stay off-site and attend only during the days, but you will need a weekend ticket.<br />
<br />
===Can I get a family ticket?===<br />
Unfortunately, as every attendee including children counts towards our capacity limit, we are unable to offer family or group tickets. We have however already discounted the child ticket prices by 60% which is as far as the budget allows.<br />
<br />
===Will I be able to turn up and buy a ticket?===<br />
It is unlikely that any tickets will remain by the time of the event. Watch this space.<br />
<br />
===Do volunteers pay for their ticket?===<br />
Everyone who attends is expected to buy a ticket, including people in the organising team and all volunteers. So many people contribute to running EMF that it would financially impossible to give everyone who helps out a free ticket, and unfair to draw a line past which volunteers receive free tickets.<br />
<br />
The only exception to this rule are first aiders, who are expected to carry out three 8-hour shifts in return for a free ticket.<br />
<br />
===Is there an age limit?===<br />
We encourage children and young people to attend. We are planning specific activities for children as well as daycare facilities, and will confirm more details nearer to the time.<br />
<br />
However there are a number of things to bear in mind:<br />
* Children under the age of 14 must be accompanied by an adult at all times.<br />
* There will be dangerous things on site, but they will be clearly marked.<br />
* Licensed alcohol sales are only for people of age 18 and over. Bar staff will ask for ID.<br />
<br />
===Can't enter the transaction reference?===<br />
If you are having trouble entering the transaction reference into your online banking, just remove the hyphen. Some banks don't like it and don't tell you.<br />
<br />
===What's your IBAN/BIC details?===<br />
Select a ticket valued in EUR on the front page. You will be presented with the necessary IBAN/BIC transfer details. Foreign transactions are not supported for GBP tickets.<br />
<br />
===Do you have a Code of Conduct?===<br />
Yes, please see [https://www.emfcamp.org/code-of-conduct Code of conduct]. If you buy a ticket you are agreeing to abide by this.<br />
<br />
===What terms and conditions apply to ticket sales and attendance?===<br />
Please see our [https://www.emfcamp.org/pay/terms terms] page.<br />
<br />
===Can I pay more? TAKE MY MONEY!===<br />
<br />
If you can afford it and wish to help support the event financially by paying a bit more for your ticket, you can buy a Supporter ticket. We're a non-profit event and so the money will go towards making the event even more awesome.<br />
<br />
===When will I receive my ticket?===<br />
You should receive an email containing any tickets you've bought on 22nd August. If you haven't received one, please check your spam folder. Alternatively, log in at https://www.emfcamp.org/tickets and click "Show e-Tickets".<br />
<br />
If you've bought tickets after this point, your tickets should be attached to the confirmation email.<br />
<br />
Please contact tickets@emfcamp.org if you haven't received your tickets.<br />
<br />
==Planning your Attendance==<br />
===Where is it? How can I get there?===<br />
Refer to [[Location]] for details.<br />
Postcode is MK17 0BU and the nearest station is Bletchley.<br />
'''NOTE: We have moved!''' It's only a few miles down the road, but please don't go to the old site!<br />
<br />
===When can I arrive? When do I have to leave by?===<br />
The site will open to ticket holders at 10:00 Friday morning.<br />
<br />
All ticket holders must leave the site by 12:00 Monday.<br />
<br />
We will be there before and afterwards setting up and packing up, if you want to help with this please let us know and we can make arrangements. It's worth noting outside these times we can't guarantee availability of toilets/water/electricity/internet etc.<br />
<br />
Have a look at our Timeline for an updated summary.<br />
<br />
===When do things kick off?===<br />
The talks and workshops will begin after lunch on Friday, although people will be setting up earlier in the day. You can arrive from 10am.<br />
<br />
Talks and workshops run daily through to the evening, although we expect villages will be doing things late into the night!<br />
<br />
===What should I bring?===<br />
Please take a look at our [[Packing List]] for information on what you should and shouldn't bring.<br />
<br />
===Will there be food?===<br />
We appreciate we didn't do well at this last time. This year we have lined up multiple food stalls, hopefully catering to all your needs. Initial details are at [[Food]]<br />
<br />
===Will there be a bar?===<br />
Yes, we'll be running a volunteer-staffed licensed bar selling beer and wine, as well as soft drinks and the hacker energy drink Club Mate. Far from the usual crap festival beer, we will be serving real ale from local breweries with all profits going towards making the next iteration of Electromagnetic Field more awesome.<br />
<br />
The bar on site opening hours are subject to licensing which will be finalised soon.<br />
<br />
By the camping areas there will also be push taps of drinking water available for free.<br />
<br />
===Can I bring pets?===<br />
Sorry, animals (except registered assistance dogs) are not allowed.<br />
<br />
===Can I smoke?===<br />
Smoking is not allowed in any of the event tents or in the food/bar area. Elsewhere, please be considerate and very careful to extinguish your cigarettes to avoid setting the dry grass on fire. Please make sure cigarette butts are disposed of in rubbish bins rather than just thrown on the ground as the site is used by livestock at other times of the year, and it's a pain for the clean up crew to pick them up after the camp is over!<br />
<br />
===Can I bring X/Y/Z?===<br />
tl;dr Probably<br />
<br />
Please let us know if it's going to be large/use a lot of power/be noisy or anything else you think we should know. We don't plan on stopping people bringing the latest cool laser helmet for shark 3d printer arduino powered UAV thing, but we need to plan for it. Note that access to the site is several hundred metres from the carpark and you will not be able to drive up to the site.<br />
<br />
Things prohibited by our contract: balloons, sky lanterns and the like.<br />
<br />
===Can I leave and re-enter?===<br />
Your wristband will allow re-admittance, but the site is gated and we will be trying to restrict movements to daylight hours. In reality this is unlikely to be a problem, but please speak to us if you have any special requirements. The farm gate is locked overnight and would require a volunteer to come up to let you out.<br />
<br />
Please note that it is a condition of our contract that we don't allow you to roam the farm. Apart from anything else, there is likely to be heavy farm machinery in operation. For this reason, the entire event area is fenced off. We can shuttle you to the parking area, from where you may drive off the site or be collected.<br />
<br />
==Camp Infrastructure==<br />
===Can I see the camp layout?===<br />
We're working on this at the moment. Some initial information can be found at: [[Location]].<br />
<br />
You can see the site map at [http://map.emfcamp.org/ map.emfcamp.org]. Please note that this is still in early stages of development; we know it is slow and has bugs, don't worry about reporting them. All layout is still subject to change.<br />
<br />
===Is there parking available?===<br />
Yes. Parking tickets are on sale with tickets. Please note the car park is not adjacent to the site, but there will be a shuttle. You will not be able to drive up to or onto the site to drop anything off.<br />
<br />
If you don't yet know whether you will be bringing a car, you can buy your event ticket now and buy a parking ticket at a later date (deadline to be announced, probably early August).<br />
<br />
Parking tickets are not required for motorcycles.<br />
<br />
===Can I bring my camper van?===<br />
We have limited parking for camper vans - you can buy a ticket for £30 through our tickets site. These tickets include a parking ticket for the towing car in the car park.<br />
<br />
===Will there be Internet access?===<br />
Yes, we are provisioning onsite high speed wifi and wired access (direct to your tent!), see [[Network]].<br />
<br />
===Can I make a fire, or bring my own BBQ?===<br />
<br />
Fires on the ground are strictly prohibited. Please adhere to this requirement of both the landowner and health and safety.<br />
<br />
Barbecues must be used off the ground. If you have a raised fire pit this is also acceptable.<br />
<br />
Foraging for wood on the site is not permitted according to the terms of our contract with the landowners. Please bring your own fuel to site.<br />
<br />
===I see a lake on the satellite image. Can I do X in it?===<br />
<br />
The lake and brook are out of bounds by order of the site owner!<br />
<br />
===What about medical cover?===<br />
<br />
We will have our our own lovely volunteer first aiders + SJA coverage.<br />
<br />
==Getting Involved==<br />
===What will I be able to do?===<br />
We're planning a full line up of speakers and workshops as well as awesome things around the site. We will also be supporting community organised 'villages' and looking for volunteers to help run the event.<br />
<br />
===What is a 'Village'?===<br />
Villages are camps organised around a theme, it could be anything, but is often a location or a topic (e.g. lock-picking). By organising villages ahead of time we can help provide better equipment (e.g. large tents to use) as well as making sure that they have an area ahead of time. If you want to find out more about villages, join one or see what villages have already been organised check the [[Villages]] page.<br />
<br />
===How do I give a talk/run a workshop?===<br />
<br />
The [https://www.emfcamp.org/cfp Call for Participation] is now open, so if you want to give a talk or run a workshop, please fill in the form soon. We really want a wide variety of topics from as diverse a group of people as we can, so don't be shy! If you've missed the CfP then don't worry, there will be [http://en.wikipedia.org/wiki/Lightning_talk lightning talk] sessions and villages are welcome to run their own talks and workshops.<br />
<br />
===Would people be interested in a talk on X?===<br />
Yes. There are obviously a few caveats on that but they're covered in the [https://www.emfcamp.org/cfp Call for Participation]<br />
<br />
===I want to bring/make something awesome, can you help?===<br />
Hopefully. We have a limited budget to put towards making the camp amazing and we want to share it with those of you who will bring awesome things. At EMF2012 we had a giant hammock, floating LEDs, a wooden dinosaur and 'EMF' written in 5m tall steel letters. If there's something amazing that you'd like to make and bring along but need some help buying materials we'll be opening our submissions process soon.<br />
<br />
===How do I volunteer?===<br />
The easiest way is to tick the 'interested in volunteering' box when you buy your ticket (sorry volunteers still need a ticket). If you missed it don't worry you can volunteer at any time by signing in and ticking the box. Once you've signed up to volunteer we'll get in contact with you closer to the time to organise shifts.<br />
<br />
==Villages==<br />
=== Can we reserve a location for our village? ===<br />
No, not really. What is possible is to obtain an advisory lock on a certain general area, but there will be no reservation system in place and if your village shows up late the spot may be taken.<br />
<br />
=== When can I build my village? ===<br />
we are working on answering that question very soon. This mainly relies on toilets, water and power being availible. We will post some information later on the [[Villages|village page]] in the wiki.<br />
<br />
=== Our village wants to rent a tent, is that possible? ===<br />
We are working on that, information about that will be added to [[Villages|the wiki]] when availible. <br />
<br />
=== Our village is planning a cool workshop / performance / ..., can the program mention it? ===<br />
We'd really like to do that! Please [mailto:contact@emfcamp.org get in touch].<br />
<br />
=== Our village is really big, does that need special planning? ===<br />
Probably: yes. Please contact general@lists.emfcamp.org, the single point of contact for all things villages concern so far.<br />
<br />
==Wiki==<br />
===How do I change my village's icon on the map?===<br />
On your village page, click Edit at the top. After <nowiki>{{Village</nowiki> add a line <nowiki>|Picture=EMF-green.png</nowiki> (change EMF-green.png to the name of your image). To upload an image, use the Upload File link to your left.<br />
<br />
===Why is my village icon showing up as a red arrow?===<br />
Most likely because you need to start the name of your image with a capital.<br />
<br />
===Can someone help me with something on the wiki?===<br />
With the festival approaching, many of the organisers are very busy. But [[User:MatS]] is worth asking: either on his [[User_talk:MatS|talk page]] or [[User:MatS|IRC]].</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Whiskyleaks&diff=2657Whiskyleaks2014-08-21T23:34:26Z<p>Ms7821: </p>
<hr />
<div>Carrying on [https://ohm2013.org/wiki/Whiskyleaks the tradition]. Bring a bottle (or more) of nice whisky. You might just be able to get away with whiskey.<br />
<br />
When: Saturday August 30th at 21:30<br><br />
Where: TBC (probably [[Villages:London Hackspace]] or Milliways)<br />
<br />
If you're coming, add your name and what you're bringing:<br />
<br />
* [[User:Russ|Russ]] (something from SMWS)<br />
* [[User:Jonty|Jonty]] (something from SMWS)<br />
* Nick (whisky. hopefully good whisky.)<br />
* [[User:SamLR|SamLR]] (something whisky)<br />
* [[User:GeeksAreForLife|James]] (I'll find something nice)<br />
* [[User:artag|artag]] Something nice and something nasty<br />
* [[User:Ms7821|Mark]] whatever's lying around</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Villages:Cambridge_Makespace&diff=2300Villages:Cambridge Makespace2014-08-19T13:06:08Z<p>Ms7821: revert</p>
<hr />
<div>{{Village<br />
|Picture=Makespace_logo.png<br />
|Name=Cambridge Makespace<br />
|Description=The Cambridge Makespace in a field.<br />
|Contact=Pinski1<br />
|Activities=3D Printers (Plastic & fabric), Combat Robots<br />
|Location=<br />
}}<br />
=We are Showing:=<br />
<br />
* Makerbot Cupcake - modified<br />
* Prusa i3<br />
* 13.6Kg combat robot<br />
* Fabric 3D printer<br />
<br />
=Whos coming?=<br />
<br />
{{inhabitant}}<br />
<br />
=More Info=<br />
See the Cambridge Makespace EMF Camp wiki page: http://wiki.makespace.org/EMF_2014</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Villages:Cambridge_Makespace&diff=2299Villages:Cambridge Makespace2014-08-19T13:04:53Z<p>Ms7821: </p>
<hr />
<div>{{Village<br />
|Picture=Makespace_logo.png<br />
|Name=Cambridge Makespace<br />
|Description=The Cambridge Makespace in a field.<br />
|Contact=Pinski1<br />
|Activities=3D Printers (Plastic & fabric), Combat Robots<br />
|Location=<br />
}}<br />
<br />
=We are Showing:=<br />
<br />
* Makerbot Cupcake - modified<br />
* Prusa i3<br />
* 13.6Kg combat robot<br />
* Fabric 3D printer<br />
<br />
=Whos coming?=<br />
{{Inhabitant}}<br />
<br />
=More Info=<br />
See the Cambridge Makespace EMF Camp wiki page: http://wiki.makespace.org/EMF_2014</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Villages:Cambridge_Makespace&diff=2298Villages:Cambridge Makespace2014-08-19T13:03:57Z<p>Ms7821: </p>
<hr />
<div>{{Village<br />
|Picture=Makespace_logo.png<br />
|Name=Cambridge Makespace<br />
|Description=The Cambridge Makespace in a field.<br />
|Contact=Pinski1<br />
|Activities=3D Printers (Plastic & fabric), Combat Robots<br />
}}<br />
<br />
=We are Showing:=<br />
<br />
* Makerbot Cupcake - modified<br />
* Prusa i3<br />
* 13.6Kg combat robot<br />
* Fabric 3D printer<br />
<br />
=Whos coming?=<br />
{{Inhabitant}}<br />
<br />
=More Info=<br />
See the Cambridge Makespace EMF Camp wiki page: http://wiki.makespace.org/EMF_2014</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Villages:Cambridge_Makespace&diff=2295Villages:Cambridge Makespace2014-08-19T12:59:19Z<p>Ms7821: </p>
<hr />
<div>{{Village<br />
|Picture=Makespace_logo.png<br />
|Name=Cambridge Makespace<br />
|Description=The Cambridge Makespace in a field.<br />
|Contact=Pinski1<br />
|Activities=3D Printers (Plastic & fabric), Combat Robots<br />
|Location=51.968,-0.794<br />
}}<br />
<br />
=We are Showing:=<br />
<br />
* Makerbot Cupcake - modified<br />
* Prusa i3<br />
* 13.6Kg combat robot<br />
* Fabric 3D printer<br />
<br />
=Whos coming?=<br />
<br />
{{inhabitant}}<br />
<br />
=More Info=<br />
See the Cambridge Makespace EMF Camp wiki page: http://wiki.makespace.org/EMF_2014</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Villages:Cambridge_Makespace&diff=2292Villages:Cambridge Makespace2014-08-19T12:55:57Z<p>Ms7821: </p>
<hr />
<div>{{Village<br />
|Picture=Makespace_logo.png<br />
|Name=Cambridge Makespace<br />
|Description=The Cambridge Makespace in a field.<br />
|Contact=Pinski1<br />
|Activities=3D Printers (Plastic & fabric), Combat Robots<br />
}}<br />
<br />
=We are Showing:=<br />
<br />
* Makerbot Cupcake - modified<br />
* Prusa i3<br />
* 13.6Kg combat robot<br />
* Fabric 3D printer<br />
<br />
=Whos coming?=<br />
<br />
{{inhabitant}}<br />
<br />
=More Info=<br />
See the Cambridge Makespace EMF Camp wiki page: http://wiki.makespace.org/EMF_2014</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Villages:Goodie-Chongs&diff=2107Villages:Goodie-Chongs2014-08-18T21:45:38Z<p>Ms7821: Found the preview button</p>
<hr />
<div>{{Village<br />
|Name=Goodie-Chongs<br />
|Description=A small village for the Goodman and Chong families, split between the campervan and camping fields<br />
|Location=51.967348,-0.792916<br />
}}</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Villages:Goodie-Chongs&diff=2106Villages:Goodie-Chongs2014-08-18T21:41:34Z<p>Ms7821: </p>
<hr />
<div>{{Village<br />
|Name=Goodie-Chongs<br />
|Description=A small village for the Goodman and Chong families, split between the campervan and camping fields<br />
|Location=51.967396,-0.792888<br />
}}</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Villages:Goodie-Chongs&diff=2105Villages:Goodie-Chongs2014-08-18T21:36:29Z<p>Ms7821: </p>
<hr />
<div>{{Village<br />
|Name=Goodie-Chongs<br />
|Description=A small village for the Goodman and Chong families<br />
|Location=51.967396,-0.792888<br />
}}</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Villages:Goodie-Chongs&diff=2104Villages:Goodie-Chongs2014-08-18T21:35:42Z<p>Ms7821: </p>
<hr />
<div>{{Village<br />
|Name=Goodie-Chongs<br />
|Description=A small village for the Goodman and Chong families<br />
|Location=51.967438,-0.792853<br />
}}</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Villages:Goodie-Chongs&diff=2103Villages:Goodie-Chongs2014-08-18T21:35:15Z<p>Ms7821: </p>
<hr />
<div>{{Village<br />
|Name=Goodie-Chongs<br />
|Description=A small village for the Goodman and Chong families<br />
|Location=51.967448,-0.792797<br />
}}</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Villages:Goodie-Chongs&diff=2102Villages:Goodie-Chongs2014-08-18T21:34:35Z<p>Ms7821: </p>
<hr />
<div>{{Village<br />
|Name=Goodie-Chongs<br />
|Description=A small village for the Goodman and Chong families<br />
|Location=51.967768,-0.792456<br />
}}</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Villages:Goodie-Chongs&diff=2100Villages:Goodie-Chongs2014-08-18T21:32:54Z<p>Ms7821: </p>
<hr />
<div>{{Village<br />
|Name=Goodie-Chongs<br />
|Description=A small village for the Goodman and Chong families<br />
|Location=51.96717, -0.79427<br />
}}</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Villages:Goodie-Chongs&diff=2098Villages:Goodie-Chongs2014-08-18T21:30:27Z<p>Ms7821: Created page with "{{Village |Name=Goodie-Chongs }}"</p>
<hr />
<div>{{Village<br />
|Name=Goodie-Chongs<br />
}}</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=FAQ&diff=2056FAQ2014-08-18T15:13:45Z<p>Ms7821: /* Can I make a fire, or bring my own BBQ? */ no fire pit</p>
<hr />
<div>{{link-banner}}<br />
This is a work in progress. Keep checking for updates.<br />
<br />
==General==<br />
===Who are you?===<br />
Electromagnetic Field is run by a non-profit organisation and produced entirely by volunteers. We are members of well-known hackerspaces and other organisations. Get in touch if you want to join us in making this happen.<br />
<br />
===Why are you doing this?===<br />
There now are dozens of hackerspaces and makerspaces in the UK and across Europe, and countless other communities of craftsmen, artists, designers, engineers who are interested in the same DIY ethic; but they have few opportunities to all meet up. Most events catering to these communities are small regional conferences and often focused on very specific themes.<br />
<br />
We want to change that :)<br />
<br />
===Why Milton Keynes?===<br />
We looked at a fair number of candidate sites. The site we ended up with was the best candidate for a number of reasons:<br />
* It comes at a comparably low price (some of the candidate sites we looked at asked for tens of thousands of £££.)<br />
* It has great transport links to much of the UK (both roads and trains.)<br />
* It is close(ish) to a few data centres and high speed Internet uplinks.<br />
* We were there last time and it seemed to work well<br />
Bonus: it is very close to Bletchley Park :)<br />
<br />
===How big is it?===<br />
<br />
In 2012, we had an attendance limit of 500 and fully sold out. This year we are expecting around 1,200 people. Buy your ticket early to avoid disappointment.<br />
<br />
==Ticket Sales==<br />
===How can I get a ticket?===<br />
Tickets are on sale from our web site here:<br />
<br />
'''https://www.emfcamp.org/tickets/choose'''<br />
<br />
This time there will be no day tickets and camp tickets are likely to sell out in advance.<br />
<br />
===How much does it cost?===<br />
Adult tickets are currently £105. There are tickets available for under-16s at a lower price (accompanied by an adult). Children under 5 can attend for free.<br />
<br />
If you have a Camper van you will need a Camper van ticket. <br />
<br />
If you want to bring a car you'll also need a car parking ticket.<br />
<br />
You can pay by bank transfer (in pounds sterling or Euros), a one-time direct debit (in pounds sterling or Euros), or by credit or debit card via Stripe (which charges a small fee).<br />
<br />
===What's the accessibility situation like?===<br />
The site will be well lit during the event, and we will aim to cover access to the stages with trackway. Travelling between stages may take some time, though.<br />
<br />
There will be three accessible toilets and the current plan includes an accessible shower with a wheelchair ramp.<br />
<br />
We cannot guarantee 24/7 power for continuous positive airway pressure (CPAP) devices, but the power infrastructure team will be on call through the night.<br />
<br />
If you will be attending with a carer, they are entitled to a free ticket. Please [mailto:tickets@emfcamp.org email us] in advance so we can allocate the ticket.<br />
<br />
Registered assistance dogs will be allowed.<br />
<br />
If you have any other requirements, please tick the "I have accessibility requirements" checkbox when buying your ticket, and we'll be in touch for details. If you'd like to confirm anything before buying your ticket, please [mailto:tickets@emfcamp.org drop us an email].<br />
<br />
===Can I get a day ticket?===<br />
Sorry, EMF 2012 was sold to capacity and we found that the day tickets prevented people from attending the whole event. For this reason, we can only offer tickets for the whole event. You are welcome to only come to one day, or to stay off-site and attend only during the days, but you will need a weekend ticket.<br />
<br />
===Can I get a family ticket?===<br />
Unfortunately, as every attendee including children counts towards our capacity limit, we are unable to offer family or group tickets. We have however already discounted the child ticket prices by 60% which is as far as the budget allows.<br />
<br />
===Will I be able to turn up and buy a ticket?===<br />
It is unlikely that any tickets will remain by the time of the event. Watch this space.<br />
<br />
===Do volunteers pay for their ticket?===<br />
Everyone who attends is expected to buy a ticket, including people in the organising team and all volunteers. So many people contribute to running EMF that it would financially impossible to give everyone who helps out a free ticket, and unfair to draw a line past which volunteers receive free tickets.<br />
<br />
The only exception to this rule are first aiders, who are expected to carry out three 8-hour shifts in return for a free ticket.<br />
<br />
===Is there an age limit?===<br />
We encourage children and young people to attend. We are planning specific activities for children as well as daycare facilities, and will confirm more details nearer to the time.<br />
<br />
However there are a number of things to bear in mind:<br />
* Children under the age of 14 must be accompanied by an adult at all times.<br />
* There will be dangerous things on site, but they will be clearly marked.<br />
* Licensed alcohol sales are only for people of age 18 and over. Bar staff will ask for ID.<br />
<br />
===Can't enter the transaction reference?===<br />
If you are having trouble entering the transaction reference into your online banking, just remove the hyphen. Some banks don't like it and don't tell you.<br />
<br />
===What's your IBAN/BIC details?===<br />
Select a ticket valued in EUR on the front page. You will be presented with the necessary IBAN/BIC transfer details. Foreign transactions are not supported for GBP tickets.<br />
<br />
===Do you have a Code of Conduct?===<br />
Yes, please see [https://www.emfcamp.org/code-of-conduct Code of conduct]. If you buy a ticket you are agreeing to abide by this.<br />
<br />
===What terms and conditions apply to ticket sales and attendance?===<br />
Please see our [https://www.emfcamp.org/pay/terms terms] page.<br />
<br />
===Can I pay more? TAKE MY MONEY!===<br />
<br />
If you can afford it and wish to help support the event financially by paying a bit more for your ticket, you can buy a Supporter ticket. We're a non-profit event and so the money will go towards making the event even more awesome.<br />
<br />
==Planning your Attendance==<br />
===Where is it? How can I get there?===<br />
Refer to [[Location]]. '''NOTE: We have moved!''' It's only a few miles down the road, but please don't go to the old site!<br />
<br />
===When can I arrive? When do I have to leave by?===<br />
The site will open to ticket holders at 10:00 Friday morning.<br />
<br />
All ticket holders must leave the site by 12:00 Monday.<br />
<br />
We will be there before and afterwards setting up and packing up, if you want to help with this please let us know and we can make arrangements. It's worth noting outside these times we can't guarantee availability of toilets/water/electricity/internet etc.<br />
<br />
Have a look at our Timeline for an updated summary.<br />
<br />
===When do things kick off?===<br />
The talks and workshops will begin after lunch on Friday, although people will be setting up earlier in the day. You can arrive from 10am.<br />
<br />
Talks and workshops run daily through to the evening, although we expect villages will be doing things late into the night!<br />
<br />
===What should I bring?===<br />
Please take a look at our [[Packing List]] for information on what you should and shouldn't bring.<br />
<br />
===Will there be food?===<br />
We appreciate we didn't do well at this last time. This year we have lined up multiple food stalls, hopefully catering to all your needs. Initial details are at [[Food]]<br />
<br />
===Will there be a bar?===<br />
Yes, we'll be running a volunteer-staffed licensed bar selling beer and wine, as well as soft drinks and the hacker energy drink Club Mate. Far from the usual crap festival beer, we will be serving real ale from local breweries with all profits going towards making the next iteration of Electromagnetic Field more awesome.<br />
<br />
The bar on site opening hours are subject to licensing which will be finalised soon.<br />
<br />
By the camping areas there will also be push taps of drinking water available for free.<br />
<br />
===Can I bring pets?===<br />
Sorry, animals (except registered assistance dogs) are not allowed.<br />
<br />
===Can I smoke?===<br />
Smoking is not allowed in any of the event tents or in the food/bar area. Elsewhere, please be considerate and very careful to extinguish your cigarettes to avoid setting the dry grass on fire. Please make sure cigarette butts are disposed of in rubbish bins rather than just thrown on the ground as the site is used by livestock at other times of the year, and it's a pain for the clean up crew to pick them up after the camp is over!<br />
<br />
===Can I bring X/Y/Z?===<br />
tl;dr Probably<br />
<br />
Please let us know if it's going to be large/use a lot of power/be noisy or anything else you think we should know. We don't plan on stopping people bringing the latest cool laser helmet for shark 3d printer arduino powered UAV thing, but we need to plan for it. Note that access to the site is several hundred metres from the carpark and you will not be able to drive up to the site.<br />
<br />
Things prohibited by our contract: balloons, sky lanterns and the like.<br />
<br />
===Can I leave and re-enter?===<br />
Your wristband will allow re-admittance, but the site is gated and we will be trying to restrict movements to daylight hours. In reality this is unlikely to be a problem, but please speak to us if you have any special requirements. The farm gate is locked overnight and would require a volunteer to come up to let you out.<br />
<br />
Please note that it is a condition of our contract that we don't allow you to roam the farm. Apart from anything else, there is likely to be heavy farm machinery in operation. For this reason, the entire event area is fenced off. We can shuttle you to the parking area, from where you may drive off the site or be collected.<br />
<br />
==Camp Infrastructure==<br />
===Can I see the camp layout?===<br />
We're working on this at the moment. Some initial information can be found at: [[Location]].<br />
<br />
You can see the site map at [http://map.emfcamp.org/ map.emfcamp.org]. Please note that this is still in early stages of development; we know it is slow and has bugs, don't worry about reporting them. All layout is still subject to change.<br />
<br />
===Is there parking available?===<br />
Yes. Parking tickets are on sale with tickets. Please note the car park is not adjacent to the site, but there will be a shuttle. You will not be able to drive up to or onto the site to drop anything off.<br />
<br />
If you don't yet know whether you will be bringing a car, you can buy your event ticket now and buy a parking ticket at a later date (deadline to be announced, probably early August).<br />
<br />
Parking tickets are not required for motorcycles.<br />
<br />
===Can I bring my camper van?===<br />
We have limited parking for camper vans - you can buy a ticket for £30 through our tickets site. These tickets include a parking ticket for the towing car in the car park.<br />
<br />
===Will there be Internet access?===<br />
Yes, we are provisioning onsite high speed wifi and wired access (direct to your tent!), see [[Network]].<br />
<br />
===Can I make a fire, or bring my own BBQ?===<br />
<br />
Open fire is strictly prohibited. Please adhere to this requirement of both the landowner and health and safety.<br />
<br />
Barbecues must be used off the ground to reduce fire risk and prevent damaging the ground.<br />
<br />
Foraging for wood on the site is not permitted according to the terms of our contract with the landowners. Please bring your own fuel to site.<br />
<br />
===I see a lake on the satellite image. Can I do X in it?===<br />
<br />
The lake and brook are out of bounds by order of the site owner!<br />
<br />
===What about medical cover?===<br />
<br />
We will have our our own lovely volunteer first aiders + SJA coverage.<br />
<br />
==Getting Involved==<br />
===What will I be able to do?===<br />
We're planning a full line up of speakers and workshops as well as awesome things around the site. We will also be supporting community organised 'villages' and looking for volunteers to help run the event.<br />
<br />
===What is a 'Village'?===<br />
Villages are camps organised around a theme, it could be anything, but is often a location or a topic (e.g. lock-picking). By organising villages ahead of time we can help provide better equipment (e.g. large tents to use) as well as making sure that they have an area ahead of time. If you want to find out more about villages, join one or see what villages have already been organised check the [[Villages]] page.<br />
<br />
===How do I give a talk/run a workshop?===<br />
<br />
The [https://www.emfcamp.org/cfp Call for Participation] is now open, so if you want to give a talk or run a workshop, please fill in the form soon. We really want a wide variety of topics from as diverse a group of people as we can, so don't be shy! If you've missed the CfP then don't worry, there will be [http://en.wikipedia.org/wiki/Lightning_talk lightning talk] sessions and villages are welcome to run their own talks and workshops.<br />
<br />
===Would people be interested in a talk on X?===<br />
Yes. There are obviously a few caveats on that but they're covered in the [https://www.emfcamp.org/cfp Call for Participation]<br />
<br />
===I want to bring/make something awesome, can you help?===<br />
Hopefully. We have a limited budget to put towards making the camp amazing and we want to share it with those of you who will bring awesome things. At EMF2012 we had a giant hammock, floating LEDs, a wooden dinosaur and 'EMF' written in 5m tall steel letters. If there's something amazing that you'd like to make and bring along but need some help buying materials we'll be opening our submissions process soon.<br />
<br />
===How do I volunteer?===<br />
The easiest way is to tick the 'interested in volunteering' box when you buy your ticket (sorry volunteers still need a ticket). If you missed it don't worry you can volunteer at any time by signing in and ticking the box. Once you've signed up to volunteer we'll get in contact with you closer to the time to organise shifts.<br />
<br />
==Villages==<br />
=== Can we reserve a location for our village? ===<br />
No, not really. What is possible is to obtain an advisory lock on a certain general area, but there will be no reservation system in place and if your village shows up late the spot may be taken.<br />
<br />
=== When can I build my village? ===<br />
we are working on answering that question very soon. This mainly relies on toilets, water and power being availible. We will post some information later on the [[Villages|village page]] in the wiki.<br />
<br />
=== Our village wants to rent a tent, is that possible? ===<br />
We are working on that, information about that will be added to [[Villages|the wiki]] when availible. <br />
<br />
=== Our village is planning a cool workshop / performance / ..., can the program mention it? ===<br />
We'd really like to do that! Please [mailto:contact@emfcamp.org get in touch].<br />
<br />
=== Our village is really big, does that need special planning? ===<br />
Probably: yes. Please contact general@lists.emfcamp.org, the single point of contact for all things villages concern so far.</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Teams&diff=1506Teams2014-08-10T14:42:39Z<p>Ms7821: </p>
<hr />
<div>These are the teams which make up the EMF organisation. For more information on how EMF is run, and the duties of team leaders, see the [[Organisation]] page.<br />
<br />
If you're interested in getting involved with a team which doesn't currently have a lead, please get in touch on [[IRC]]. If you're interested in joining a team, get in touch with the team lead.<br />
<br />
{| class="wikitable sortable"<br />
! Team<br />
! Description<br />
! Lead<br />
! Deputy Lead(s)<br />
|-<br />
| [[Team:Admin]]<br />
| Top-level organisation, licensing, site planning<br />
| [[User:Russ]]<br />
| [[User:Jonty]]<br />
|-<br />
| [[Team:Finance]]<br />
| Dealing with the money<br />
| [[User:Russ]]<br />
| Paul2<br />
|-<br />
| [[Team:Site]]<br />
| Tents, fences, trackway, etc.<br />
| WillH<br />
| [[User:Russ]]<br />
|-<br />
| [[Team:Power]]<br />
| All things power, as well as basic site lighting.<br />
| [[User:Benny]]<br />
| Will H<br />
|-<br />
| [[Team:Sanitation]]<br />
| Water supply, showers, toilets, rubbish.<br />
| Paul2<br />
| Crypt<br />
|-<br />
| [[Team:Security]]<br />
| Making sure the site is safe.<br />
| Crypt<br />
| <br />
|-<br />
| [[Team:NOC]]<br />
| Networking<br />
| [[User:JasperWallace]]<br />
| Will H, [[User:davidc]]<br />
|-<br />
| [[Team:Web]]<br />
| Web sites, ticket sales, volunteering, and CfP systems<br />
| [[User:ms7821|Mark]]<br />
| [[User:JasperWallace]] (probably?)<br />
|-<br />
| [[Team:Content]]<br />
| Organising talks/workshops/etc<br />
| [[User:Jonty]]<br />
| Tef<br />
|-<br />
| [[Team:Bar]]<br />
| Booze, and such<br />
| Chris W<br />
| [[User:Russ]]<br />
|-<br />
| [[Team:First Aid]]<br />
| Making sure we don't kill ourselves, as well as looking after attendee welfare.<br />
| [[User:Oni|Oni]]<br />
| Katie<br />
|-<br />
| [[Team:Catering]]<br />
| Organising food providers<br />
| Nick<br />
| [[User:JasperWallace]] (maybe?)<br />
|-<br />
| [[Team:InfoDesk]]<br />
| Providing information during the event<br />
| SamLR<br />
|<br />
|-<br />
| [[Team:Volunteering]]<br />
| Managing volunteers across all stages<br />
| Nick<br />
| Lyndsey/Kate<br />
|-<br />
| [[Team:Spawn]]<br />
| Liaising with UCL/Nipperbout for management of the kids area, activities, and childminding<br />
| Becky<br />
| <br />
|-<br />
| [[Team:Stage]]<br />
| Staging, stage lighting, audio, and projection.<br />
| [[User:TimRTerrible]]<br />
| [[User:gmc]]<br />
|-<br />
| [[Team:Video]]<br />
| Liaising with the video streaming and recording people.<br />
| WillH<br />
| SamLR<br />
|-<br />
| [[Team:Shiny]]<br />
| Site decoration, lights, installations. Shiny things.<br />
| SamLR<br />
| [[User:Jonty]]<br />
|-<br />
| [[Team:Badge]]<br />
| Badge building, and infrastructure.<br />
| [[User:Dpslwk|Dpslwk]] ([[User talk:Dpslwk|talk]])<br />
| [[User:thinkl33t|Bob]]/[[User:Jonty]]<br />
|-<br />
| [[Team:Sysadmin]]<br />
| Making sure servers work, on and off site.<br />
| [[User:JasperWallace]]<br />
| [[User:Russ]]<br />
|-<br />
| [[Team:Phone]]<br />
| Looking after 2G, DECT, SIP etc.<br />
| kevinprince<br />
|<br />
|-<br />
| [[Team:Villages]]<br />
| Looking after villages and their requirements<br />
| Crypt<br />
|<br />
|-<br />
| [[Team:Sponsorship]]<br />
| Looking after sponsors/vendors and their requirements.<br />
| [[User:Jonty]]<br />
|<br />
|-<br />
| [[Team:Lounge]]<br />
| Organising the Lounge area<br />
| [[User:Amx109|amx109]]<br />
| [[User:Will-Do]]<br />
|-<br />
| [[Team:Comfort]]<br />
| Planning conflict resolution and making sure people will feel safe in advance<br />
| Jane<br />
| martind<br />
|-<br />
| [[Team:Logistics]]<br />
| Organising the non-site logistics (e.g. getting stuff like the badges from London to the site)<br />
| [[User:JasperWallace]]<br />
| <br />
|}</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=TiLDA_MKe&diff=1474TiLDA MKe2014-08-08T13:35:00Z<p>Ms7821: /* Source */</p>
<hr />
<div>The TiLDA MKe project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Dpslwk|'RepRap' Matt]] and [[User:thinkl33t|Bob]]<br />
[[File:Badge_Front.png|right|thumb|Front]]<br />
<br />
[http://en.wikipedia.org/wiki/E_(mathematical_constant) Why MKe?]<br />
<br />
=Aim= <br />
The main aim of the 2014 badge is to give camp attendees live schedule updates and notifications. As with the original TiLDA we wanted to keep with an Arduino compatible platform that will allow badge hacking during and after the camp. As with previous badge all code and design files are available.<br />
<br />
==Features and Functions==<br />
[[File:Badge_Back.png|right|thumb|Back]]<br />
===Essential===<br />
The following are considers core things that the badge must do for EMF2014<br />
* Receive and display announcements on talks scheduling<br />
** user registers their lanyard and which talks/workshops they are interested in on the emf web site <br />
** lanyard’s registered for talks receives reminders and notice of when and where a talk will be especially important if a talk is moved (time/location)<br />
* Torch Mode<br />
** One of the side effect of the two RGB LED's on TiLDA was they made a great torch <br />
* Arduino Compatible<br />
* Work during the event and be useful afterwards<br />
<br />
=Hardware=<br />
<br />
The following hardware has been included on the badge.<br />
<br />
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]<br />
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge<br />
** 32bit ARM Cortex M3 * 84MHz<br />
** 512KBytes Flash RAM<br />
** 96KBytes of SRAM<br />
* A 128x64 pixel monochrome LCD display<br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
** 868Mhz RF Transceiver<br />
** Simple UART interface<br />
** Low power sleep mode<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro<br />
** I2C interface<br />
** Tri-Axis angular rate sensor (gyro) with a sensitivity up to 131 LSBs/dps and a full-scale range of ±250, ±500, ±1000, and ±2000dps<br />
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g<br />
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection<br />
* PMIC & LiPo<br />
* Joystick<br />
* Buttons<br />
* RGB LED's<br />
* IR<br />
* Arduino Headers<br />
* Pads for wearable tech<br />
<br />
=Hacking=<br />
To use our board definition you will need to first get the Arduino 1.5.7 IDE from [http://arduino.cc/en/Main/Software#toc3 here]<br/><br />
Next you can download the TiLDA Mk2 Firmware project from either the [https://github.com/EMF-TiLDA/Mk2-Firmware github repo] or via [https://github.com/EMF-TiLDA/Mk2-Firmware/archive/master.zip direct download]<br/><br />
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/<br><br />
<br />
Start the Arduino IDE and your will be able to select TiLDA Mk2 for the Tools->Board menu<br />
<br />
<span id=github></span><br />
<br />
= Source =<br />
<br />
All the source code and designs are on openly available on Github:<br />
<br />
* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design<br />
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant documentation<br />
* [https://github.com/emfcamp/Mk2-Firware Firmware] - source code for the badge software<br />
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network<br />
<br />
[[Category: TiLDA]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=TiLDA_MKe&diff=1466TiLDA MKe2014-08-08T12:22:15Z<p>Ms7821: /* Sponsors */</p>
<hr />
<div>The TiLDA MKe project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Dpslwk|'RepRap' Matt]] and [[User:thinkl33t|Bob]]<br />
[[File:Badge_Front.png|right|thumb|Front]]<br />
<br />
[http://en.wikipedia.org/wiki/E_(mathematical_constant) Why MKe?]<br />
<br />
=Aim= <br />
The main aim of the 2014 badge is to give camp attendees live schedule updates and notifications. As with the original TiLDA we wanted to keep with an Arduino compatible platform that will allow badge hacking during and after the camp. As with previous badge all code and design files are available.<br />
<br />
==Features and Functions==<br />
[[File:Badge_Back.png|right|thumb|Back]]<br />
===Essential===<br />
The following are considers core things that the badge must do for EMF2014<br />
* Receive and display announcements on talks scheduling<br />
** user registers their lanyard and which talks/workshops they are interested in on the emf web site <br />
** lanyard’s registered for talks receives reminders and notice of when and where a talk will be especially important if a talk is moved (time/location)<br />
* Torch Mode<br />
** One of the side effect of the two RGB LED's on TiLDA was they made a great torch <br />
* Arduino Compatible<br />
* Work during the event and be useful afterwards<br />
<br />
=Hardware=<br />
<br />
The following hardware has been included on the badge.<br />
<br />
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]<br />
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge<br />
** 32bit ARM Cortex M3 * 84MHz<br />
** 512KBytes Flash RAM<br />
** 96KBytes of SRAM<br />
* A 128x64 pixel monochrome LCD display<br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
** 868Mhz RF Transceiver<br />
** Simple UART interface<br />
** Low power sleep mode<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro<br />
** I2C interface<br />
** Tri-Axis angular rate sensor (gyro) with a sensitivity up to 131 LSBs/dps and a full-scale range of ±250, ±500, ±1000, and ±2000dps<br />
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g<br />
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection<br />
* PMIC & LiPo<br />
* Joystick<br />
* Buttons<br />
* RGB LED's<br />
* IR<br />
* Arduino Headers<br />
* Pads for wearable tech<br />
<br />
=Hacking=<br />
To use our board definition you will need to first get the Arduino 1.5.7 IDE from [http://arduino.cc/en/Main/Software#toc3 here]<br/><br />
Next you can download the TiLDA Mk2 Firmware project from either the [https://github.com/EMF-TiLDA/Mk2-Firmware github repo] or via [https://github.com/EMF-TiLDA/Mk2-Firmware/archive/master.zip direct download]<br/><br />
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/<br><br />
<br />
Start the Arduino IDE and your will be able to select TiLDA Mk2 for the Tools->Board menu<br />
<br />
<span id=github></span><br />
<br />
= Source =<br />
<br />
* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design<br />
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant documentation<br />
* [https://github.com/emfcamp/Mk2-Firware Firmware] - source code for the badge software<br />
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network<br />
<br />
[[Category: TiLDA]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=TiLDA_MKe&diff=1465TiLDA MKe2014-08-08T12:21:59Z<p>Ms7821: /* Github */</p>
<hr />
<div>The TiLDA MKe project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Dpslwk|'RepRap' Matt]] and [[User:thinkl33t|Bob]]<br />
[[File:Badge_Front.png|right|thumb|Front]]<br />
<br />
[http://en.wikipedia.org/wiki/E_(mathematical_constant) Why MKe?]<br />
<br />
=Aim= <br />
The main aim of the 2014 badge is to give camp attendees live schedule updates and notifications. As with the original TiLDA we wanted to keep with an Arduino compatible platform that will allow badge hacking during and after the camp. As with previous badge all code and design files are available.<br />
<br />
==Features and Functions==<br />
[[File:Badge_Back.png|right|thumb|Back]]<br />
===Essential===<br />
The following are considers core things that the badge must do for EMF2014<br />
* Receive and display announcements on talks scheduling<br />
** user registers their lanyard and which talks/workshops they are interested in on the emf web site <br />
** lanyard’s registered for talks receives reminders and notice of when and where a talk will be especially important if a talk is moved (time/location)<br />
* Torch Mode<br />
** One of the side effect of the two RGB LED's on TiLDA was they made a great torch <br />
* Arduino Compatible<br />
* Work during the event and be useful afterwards<br />
<br />
=Hardware=<br />
<br />
The following hardware has been included on the badge.<br />
<br />
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]<br />
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge<br />
** 32bit ARM Cortex M3 * 84MHz<br />
** 512KBytes Flash RAM<br />
** 96KBytes of SRAM<br />
* A 128x64 pixel monochrome LCD display<br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
** 868Mhz RF Transceiver<br />
** Simple UART interface<br />
** Low power sleep mode<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro<br />
** I2C interface<br />
** Tri-Axis angular rate sensor (gyro) with a sensitivity up to 131 LSBs/dps and a full-scale range of ±250, ±500, ±1000, and ±2000dps<br />
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g<br />
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection<br />
* PMIC & LiPo<br />
* Joystick<br />
* Buttons<br />
* RGB LED's<br />
* IR<br />
* Arduino Headers<br />
* Pads for wearable tech<br />
<br />
=Hacking=<br />
To use our board definition you will need to first get the Arduino 1.5.7 IDE from [http://arduino.cc/en/Main/Software#toc3 here]<br/><br />
Next you can download the TiLDA Mk2 Firmware project from either the [https://github.com/EMF-TiLDA/Mk2-Firmware github repo] or via [https://github.com/EMF-TiLDA/Mk2-Firmware/archive/master.zip direct download]<br/><br />
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/<br><br />
<br />
Start the Arduino IDE and your will be able to select TiLDA Mk2 for the Tools->Board menu<br />
<br />
=Sponsors=<br />
<br />
<br />
<span id=github></span><br />
= Source =<br />
<br />
* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design<br />
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant documentation<br />
* [https://github.com/emfcamp/Mk2-Firware Firmware] - source code for the badge software<br />
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network<br />
<br />
[[Category: TiLDA]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=File:Badge_Back.png&diff=1464File:Badge Back.png2014-08-08T12:21:27Z<p>Ms7821: </p>
<hr />
<div>Licence: [https://creativecommons.org/licenses/by-sa/3.0/ CC BY-SA]<br />
Author: [[User:Dpslwk|Matt]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=TiLDA_MKe&diff=1463TiLDA MKe2014-08-08T12:21:21Z<p>Ms7821: /* Software */</p>
<hr />
<div>The TiLDA MKe project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Dpslwk|'RepRap' Matt]] and [[User:thinkl33t|Bob]]<br />
[[File:Badge_Front.png|right|thumb|Front]]<br />
<br />
[http://en.wikipedia.org/wiki/E_(mathematical_constant) Why MKe?]<br />
<br />
=Aim= <br />
The main aim of the 2014 badge is to give camp attendees live schedule updates and notifications. As with the original TiLDA we wanted to keep with an Arduino compatible platform that will allow badge hacking during and after the camp. As with previous badge all code and design files are available.<br />
<br />
==Features and Functions==<br />
[[File:Badge_Back.png|right|thumb|Back]]<br />
===Essential===<br />
The following are considers core things that the badge must do for EMF2014<br />
* Receive and display announcements on talks scheduling<br />
** user registers their lanyard and which talks/workshops they are interested in on the emf web site <br />
** lanyard’s registered for talks receives reminders and notice of when and where a talk will be especially important if a talk is moved (time/location)<br />
* Torch Mode<br />
** One of the side effect of the two RGB LED's on TiLDA was they made a great torch <br />
* Arduino Compatible<br />
* Work during the event and be useful afterwards<br />
<br />
=Hardware=<br />
<br />
The following hardware has been included on the badge.<br />
<br />
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]<br />
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge<br />
** 32bit ARM Cortex M3 * 84MHz<br />
** 512KBytes Flash RAM<br />
** 96KBytes of SRAM<br />
* A 128x64 pixel monochrome LCD display<br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
** 868Mhz RF Transceiver<br />
** Simple UART interface<br />
** Low power sleep mode<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro<br />
** I2C interface<br />
** Tri-Axis angular rate sensor (gyro) with a sensitivity up to 131 LSBs/dps and a full-scale range of ±250, ±500, ±1000, and ±2000dps<br />
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g<br />
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection<br />
* PMIC & LiPo<br />
* Joystick<br />
* Buttons<br />
* RGB LED's<br />
* IR<br />
* Arduino Headers<br />
* Pads for wearable tech<br />
<br />
=Hacking=<br />
To use our board definition you will need to first get the Arduino 1.5.7 IDE from [http://arduino.cc/en/Main/Software#toc3 here]<br/><br />
Next you can download the TiLDA Mk2 Firmware project from either the [https://github.com/EMF-TiLDA/Mk2-Firmware github repo] or via [https://github.com/EMF-TiLDA/Mk2-Firmware/archive/master.zip direct download]<br/><br />
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/<br><br />
<br />
Start the Arduino IDE and your will be able to select TiLDA Mk2 for the Tools->Board menu<br />
<br />
=Sponsors=<br />
<br />
<br />
= Github =<br />
<br />
* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design<br />
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant documentation<br />
* [https://github.com/emfcamp/Mk2-Firware Firmware] - source code for the badge software<br />
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network<br />
<br />
[[Category: TiLDA]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=File:Badge_Front.png&diff=1462File:Badge Front.png2014-08-08T12:20:20Z<p>Ms7821: </p>
<hr />
<div>Licence: [https://creativecommons.org/licenses/by-sa/3.0/ CC BY-SA]<br />
Author: [[User:Dpslwk|Matt]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=File:Badge_Back.png&diff=1461File:Badge Back.png2014-08-08T12:17:22Z<p>Ms7821: </p>
<hr />
<div>Licence: [https://creativecommons.org/licenses/by-sa/3.0/ CC BY]<br />
Author: [[User:Dpslwk|Matt]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=File:Badge_Front.png&diff=1460File:Badge Front.png2014-08-08T12:17:15Z<p>Ms7821: </p>
<hr />
<div>Licence: [https://creativecommons.org/licenses/by-sa/3.0/ CC BY]<br />
Author: [[User:Dpslwk|Matt]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=File:Badge_Back.png&diff=1458File:Badge Back.png2014-08-08T12:15:19Z<p>Ms7821: By Matt</p>
<hr />
<div>By [[User:Dpslwk|Matt]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=TiLDA_MKe&diff=1457TiLDA MKe2014-08-08T12:10:15Z<p>Ms7821: </p>
<hr />
<div>The TiLDA MKe project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Dpslwk|'RepRap' Matt]] and [[User:thinkl33t|Bob]]<br />
[[File:Badge_Front.png|right|thumb|Front]]<br />
<br />
[http://en.wikipedia.org/wiki/E_(mathematical_constant) Why MKe?]<br />
<br />
=Aim= <br />
The main aim of the 2014 badge is to give camp attendees live schedule updates and notifications. As with the original TiLDA we wanted to keep with an Arduino compatible platform that will allow badge hacking during and after the camp. As with previous badge all code and design files are available.<br />
<br />
==Features and Functions==<br />
[[File:Badge_Back.png|right|thumb|Back]]<br />
===Essential===<br />
The following are considers core things that the badge must do for EMF2014<br />
* Receive and display announcements on talks scheduling<br />
** user registers their lanyard and which talks/workshops they are interested in on the emf web site <br />
** lanyard’s registered for talks receives reminders and notice of when and where a talk will be especially important if a talk is moved (time/location)<br />
* Torch Mode<br />
** One of the side effect of the two RGB LED's on TiLDA was they made a great torch <br />
* Arduino Compatible<br />
* Work during the event and be useful afterwards<br />
<br />
=Hardware=<br />
<br />
The following hardware has been included on the badge.<br />
<br />
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]<br />
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge<br />
** 32bit ARM Cortex M3 * 84MHz<br />
** 512KBytes Flash RAM<br />
** 96KBytes of SRAM<br />
* A 128x64 pixel monochrome LCD display<br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
** 868Mhz RF Transceiver<br />
** Simple UART interface<br />
** Low power sleep mode<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro<br />
** I2C interface<br />
** Tri-Axis angular rate sensor (gyro) with a sensitivity up to 131 LSBs/dps and a full-scale range of ±250, ±500, ±1000, and ±2000dps<br />
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g<br />
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection<br />
* PMIC & LiPo<br />
* Joystick<br />
* Buttons<br />
* RGB LED's<br />
* IR<br />
* Arduino Headers<br />
* Pads for wearable tech<br />
<br />
=Software=<br />
===Badge Firmware===<br />
<br />
===Gateway===<br />
<br />
===Server side===<br />
<br />
=Hacking=<br />
To use our board definition you will need to first get the Arduino 1.5.7 IDE from [http://arduino.cc/en/Main/Software#toc3 here]<br/><br />
Next you can download the TiLDA Mk2 Firmware project from either the [https://github.com/EMF-TiLDA/Mk2-Firmware github repo] or via [https://github.com/EMF-TiLDA/Mk2-Firmware/archive/master.zip direct download]<br/><br />
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/<br><br />
<br />
Start the Arduino IDE and your will be able to select TiLDA Mk2 for the Tools->Board menu<br />
<br />
=Sponsors=<br />
<br />
<br />
= Github =<br />
<br />
* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design<br />
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant documentation<br />
* [https://github.com/emfcamp/Mk2-Firware Firmware] - source code for the badge software<br />
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network<br />
<br />
[[Category: TiLDA]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=File:Badge_Front.png&diff=1455File:Badge Front.png2014-08-08T12:05:25Z<p>Ms7821: By Matt</p>
<hr />
<div>By [[User:User:Dpslwk|Matt]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=TiLDA_MKe&diff=1453TiLDA MKe2014-08-08T12:03:17Z<p>Ms7821: </p>
<hr />
<div>The TiLDA MKe project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Dpslwk|'RepRap' Matt]] and [[User:thinkl33t|Bob]]<br/><br />
<br />
[http://en.wikipedia.org/wiki/E_(mathematical_constant) Why MKe?]<br />
<br />
=Aim= <br />
The main aim of the 2014 badge is to give camp attendees live schedule updates and notifications. As with the original TiLDA we wanted to keep with an Arduino compatible platform that will allow badge hacking during and after the camp. As with previous badge all code and design files are available.<br />
<br />
==Features and Functions==<br />
===Essential===<br />
The following are considers core things that the badge must do for EMF2014<br />
* Receive and display announcements on talks scheduling<br />
** user registers their lanyard and which talks/workshops they are interested in on the emf web site <br />
** lanyard’s registered for talks receives reminders and notice of when and where a talk will be especially important if a talk is moved (time/location)<br />
* Torch Mode<br />
** One of the side effect of the two RGB LED's on TiLDA was they made a great torch <br />
* Arduino Compatible<br />
* Work during the event and be useful afterwards<br />
<br />
=Hardware=<br />
<br />
The following hardware has been included on the badge.<br />
<br />
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]<br />
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge<br />
** 32bit ARM Cortex M3 * 84MHz<br />
** 512KBytes Flash RAM<br />
** 96KBytes of SRAM<br />
* A 128x64 pixel monochrome LCD display<br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
** 868Mhz RF Transceiver<br />
** Simple UART interface<br />
** Low power sleep mode<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro<br />
** I2C interface<br />
** Tri-Axis angular rate sensor (gyro) with a sensitivity up to 131 LSBs/dps and a full-scale range of ±250, ±500, ±1000, and ±2000dps<br />
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g<br />
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection<br />
* PMIC & LiPo<br />
* Joystick<br />
* Buttons<br />
* RGB LED's<br />
* IR<br />
* Arduino Headers<br />
* Pads for wearable tech<br />
<br />
=Software=<br />
===Badge Firmware===<br />
<br />
===Gateway===<br />
<br />
===Server side===<br />
<br />
=Hacking=<br />
To use our board definition you will need to first get the Arduino 1.5.5 IDE from [http://arduino.cc/en/Main/Software#toc3 here]<br/><br />
Next you can download the TiLDA Mk2 Firmware project from either the [https://github.com/EMF-TiLDA/Mk2-Firmware github repo] or via [https://github.com/EMF-TiLDA/Mk2-Firmware/archive/master.zip direct download]<br/><br />
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/<br><br />
<br />
Start the Arduino IDE and your will be able to select TiLDA Mk2 for the Tools->Board menu<br />
<br />
=Sponsors=<br />
<br />
<br />
= Github =<br />
<br />
* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design<br />
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant documentation<br />
* [https://github.com/emfcamp/Mk2-Firware Firmware] - source code for the badge software<br />
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network<br />
<br />
[[Category: TiLDA]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=TiLDA_MKe&diff=1452TiLDA MKe2014-08-08T11:56:40Z<p>Ms7821: </p>
<hr />
<div>The TiLDA MKe project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Dpslwk|'RepRap' Matt]] and [[User:thinkl33t|Bob]]<br/><br />
<br />
Why MKe? http://en.wikipedia.org/wiki/E_(mathematical_constant)<br />
<br />
=Aim= <br />
The main aim of the 2014 badge is to give camp attendees live schedule updates and notifications. As with the original TiLDA we wanted to keep with an Arduino compatible platform that will allow badge hacking during and after the camp. As with previous badge all code and design files are available.<br />
<br />
==Features and Functions==<br />
===Essential===<br />
The following are considers core things that the badge must do for EMF2014<br />
* Receive and display announcements on talks scheduling<br />
** user registers their lanyard and which talks/workshops they are interested in on the emf web site <br />
** lanyard’s registered for talks receives reminders and notice of when and where a talk will be especially important if a talk is moved (time/location)<br />
* Torch Mode<br />
** One of the side effect of the two RGB LED's on TiLDA was they made a great torch <br />
* Arduino Compatible<br />
* Work during the event and be useful afterwards<br />
<br />
=Hardware=<br />
<br />
The following hardware has been included on the badge.<br />
<br />
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]<br />
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge<br />
** 32bit ARM Cortex M3 * 84MHz<br />
** 512KBytes Flash RAM<br />
** 96KBytes of SRAM<br />
* A 128x64 pixel monochrome LCD display<br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
** 868Mhz RF Transceiver<br />
** Simple UART interface<br />
** Low power sleep mode<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro<br />
** I2C interface<br />
** Tri-Axis angular rate sensor (gyro) with a sensitivity up to 131 LSBs/dps and a full-scale range of ±250, ±500, ±1000, and ±2000dps<br />
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g<br />
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection<br />
* PMIC & LiPo<br />
* Joystick<br />
* Buttons<br />
* RGB LED's<br />
* IR<br />
* Arduino Headers<br />
* Pads for wearable tech<br />
<br />
=Software=<br />
===Badge Firmware===<br />
<br />
===Gateway===<br />
<br />
===Server side===<br />
<br />
=Hacking=<br />
To use our board definition you will need to first get the Arduino 1.5.5 IDE from [http://arduino.cc/en/Main/Software#toc3 here]<br/><br />
Next you can download the TiLDA Mk2 Firmware project from either the [https://github.com/EMF-TiLDA/Mk2-Firmware github repo] or via [https://github.com/EMF-TiLDA/Mk2-Firmware/archive/master.zip direct download]<br/><br />
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/<br><br />
<br />
Start the Arduino IDE and your will be able to select TiLDA Mk2 for the Tools->Board menu<br />
<br />
=Sponsors=<br />
<br />
<br />
= Github =<br />
<br />
* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design<br />
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant documentation<br />
* [https://github.com/emfcamp/Mk2-Firware Firmware] - source code for the badge software<br />
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network<br />
<br />
[[Category: TiLDA]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=TiLDA_MKe&diff=1451TiLDA MKe2014-08-08T11:55:59Z<p>Ms7821: Recreate page with correct info</p>
<hr />
<div>== '''Note:''' THIS IS NOT THE FINAL BADGE SPECIFICATION. WE MIGHT HAVE HAD TO DROP THE SPECIFICATION A LITTLE :( ==<br />
<br />
The TiLDA MKe project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Solexious|Charles]], [[User:thinkl33t|Bob]] and [[User:Dpslwk|'RepRap' Matt]]<br/><br />
If you wish to chat about the badge head over to the [irc://chat.freenode.com/##tilda ##tilda] IRC channel on free node<br/><br />
Why MKe? http://en.wikipedia.org/wiki/E_(mathematical_constant)<br />
<br />
=Aim= <br />
The main aim of the 2014 badge is to give camp attendees live schedule updates and notifications. As with the original TiLDA we wanted to keep with an Arduino compatible platform that will allow badge hacking during and after the camp. As with previous badge all code and design files are available. Work can be found here on github.com/EMF-TiLDA <br />
<br />
==Features and Functions==<br />
===Essential===<br />
The following are considers core things that the badge must do for EMF2014<br />
* Receive and display announcements on talks scheduling<br />
** user registers their lanyard and which talks/workshops they are interested in on the emf web site <br />
** lanyard’s registered for talks receives reminders and notice of when and where a talk will be especially important if a talk is moved (time/location)<br />
* Torch Mode<br />
** One of the side effect of the two RGB LED's on TiLDA was they made a great torch <br />
* Arduino Compatible<br />
* Work during the event and be useful afterwards<br />
<br />
=Hardware=<br />
<br />
The following hardware has been included on the badge.<br />
<br />
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]<br />
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge<br />
** 32bit ARM Cortex M3 * 84MHz<br />
** 512KBytes Flash RAM<br />
** 96KBytes of SRAM<br />
* A 128x64 pixel monochrome LCD display<br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
** 868Mhz RF Transceiver<br />
** Simple UART interface<br />
** Low power sleep mode<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro<br />
** I2C interface<br />
** Tri-Axis angular rate sensor (gyro) with a sensitivity up to 131 LSBs/dps and a full-scale range of ±250, ±500, ±1000, and ±2000dps<br />
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g<br />
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection<br />
* PMIC & LiPo<br />
* Joystick<br />
* Buttons<br />
* RGB LED's<br />
* IR<br />
* Arduino Headers<br />
* Pads for wearable tech<br />
<br />
=Software=<br />
===Badge Firmware===<br />
<br />
===Gateway===<br />
<br />
===Server side===<br />
<br />
=Hacking=<br />
To use our board definition you will need to first get the Arduino 1.5.5 IDE from [http://arduino.cc/en/Main/Software#toc3 here]<br/><br />
Next you can download the TiLDA Mk2 Firmware project from either the [https://github.com/EMF-TiLDA/Mk2-Firmware github repo] or via [https://github.com/EMF-TiLDA/Mk2-Firmware/archive/master.zip direct download]<br/><br />
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/<br><br />
<br />
Start the Arduino IDE and your will be able to select TiLDA Mk2 for the Tools->Board menu<br />
<br />
=Sponsors=<br />
<br />
<br />
= Github =<br />
<br />
* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design<br />
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant documentation<br />
* [https://github.com/emfcamp/Mk2-Firware Firmware] - source code for the badge software<br />
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network<br />
<br />
[[Category: TiLDA]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Talk:TiLDA_MKe_-_the_dream&diff=1450Talk:TiLDA MKe - the dream2014-08-08T11:52:03Z<p>Ms7821: Ms7821 moved page Talk:TiLDA MKe to Talk:TiLDA MKe - the dream without leaving a redirect: Need to create correct page</p>
<hr />
<div><br />
From IRC on 25/4/13<br />
<br />
[15:26:21] <jontyw> I really want to have tiny screens and broadcast reception on the EMF badges next year, but I think solexious and parag0n hate me.<br />
<br />
From IRC on 17/08/13<br />
<br />
[17:40:54] <jontyw> EST (EMF Standard Time) is GMT+5<br/><br />
[17:40:57] <ms7821> half the camp wakes up at 6am, the other half at 12pm<br/><br />
[17:41:07] <russss> the problem is the sun on tents.<br/><br />
[17:41:07] <ms7821> this is enforced by badges and sirens<br/><br />
[17:41:08] <will-h> TZ=Europe/Berlin/Hacker<br/><br />
<br />
I want to code EST into the badge software now --[[User:Dpslwk|Dpslwk]] ([[User talk:Dpslwk|talk]]) 16:44, 17 August 2013 (UTC)<br />
<br />
From IRC on 27/08/13<br />
<br />
[11:39:15] <LWK> hmm would be nice to have a stats page with things like noc bandwidth usage, beer left, etc<br/><br />
11:39:52] <ms7821> and map, schedule and camp guide</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=TiLDA_MKe_-_the_dream&diff=1449TiLDA MKe - the dream2014-08-08T11:52:02Z<p>Ms7821: Ms7821 moved page TiLDA MKe to TiLDA MKe - the dream without leaving a redirect: Need to create correct page</p>
<hr />
<div>== '''Note:''' THIS IS NOT THE FINAL BADGE SPECIFICATION. WE MIGHT HAVE HAD TO DROP THE SPECIFICATION A LITTLE :( ==<br />
<br />
The TiLDA MKe project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Solexious|Charles]], [[User:thinkl33t|Bob]] and [[User:Dpslwk|'RepRap' Matt]]<br/><br />
If you wish to chat about the badge head over to the [irc://chat.freenode.com/##tilda ##tilda] IRC channel on free node<br/><br />
Why MKe? http://en.wikipedia.org/wiki/E_(mathematical_constant)<br />
<br />
=Aim= <br />
The main aim of the 2014 badge is to give camp attendees live schedule updates and notifications. As with the original TiLDA we wanted to keep with an Arduino compatible platform that will allow badge hacking during and after the camp. As with previous badge all code and design files are available. Work can be found here on github.com/EMF-TiLDA <br />
<br />
==Features and Functions==<br />
A initial planing session was held during the Newcastle MakerFaire 2013, during which a list of essential features was decide upon along with a big list of shiny, mad ideas that may happen depending on budge and time.<br/><br />
The notes from that session can be found here [[TiLDA 2/Ideas List]]<br />
===Essential===<br />
The following are considers core things that the badge must do for EMF2014<br />
* Receive and display announcements on talks scheduling<br />
** user registers their lanyard and which talks/workshops they are interested in on the emf web site <br />
** lanyard’s registered for talks receives reminders and notice of when and where a talk will be especially important if a talk is moved (time/location)<br />
* IR interaction<br />
** could be used for business card mode, allow users to exchange info at push of a button<br />
** games<br />
** talking to TiLDA or SiNE<br />
* Torch Mode<br />
** One of the side effect of the two RGB LED's on TiLDA was they made a great torch <br />
* Arduino Compatible<br />
* Work during the event and be useful afterwards<br />
** Battery voltage measurement and display, Charging management<br />
<br />
===Nice to have===<br />
The following are things that we hope to implement if we have the time and budget.<br />
* Locations tracking<br />
** By looking at which gateway the badge is talking to we can get a ruff idea of where on the camp site a badge is located<br />
* Send text to it, not just talks (SMS you friends badge?)<br />
** we will have a screen and ability to display text, so sending something to a other set badge should be easy.<br />
* Use the spearks as a PA system, (download recorded WAV over network then synced playback start)<br />
* TiLDA ad SiNE reprogramming<br />
** If we can develop some new firmware to go on SiNE or TiLDA, we might be able to reprogram them from Mk2 by jumping the ISP headers together<br />
* TTS https://github.com/going-digital/Talkie<br />
<br />
=Hardware=<br />
<br />
The following hardware has been included on the badge.<br />
<br />
N.B. Due to funding issues the badge may/will be much lower spec than this. ''We almost certainly will not have an e-paper display'' :(<br />
<br />
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]<br />
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge<br />
** 32bit ARM Cortex M3 * 84MHz<br />
** 512KBytes Flash RAM<br />
** 96KBytes of SRAM<br />
* <s>[http://repaper.org Repaper 2.7" ePaper display]<br />
** a-Si TFT active matrix Electronic Paper Display(EPD)<br />
** Resolution: 264 x 176<br />
** Ultra low power consumption<br />
** Super Wide Viewing Angle - near 180°<br />
** Extra thin & light<br />
** SPI interface<br />
** Outline Dimension 70.42 x 45.80 mm<br />
** Active Area 57.288 x 38.192 mm</s> <br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
** 868Mhz RF Transceiver<br />
** Simple UART interface<br />
** Low power sleep mode<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro<br />
** I2C interface<br />
** Tri-Axis angular rate sensor (gyro) with a sensitivity up to 131 LSBs/dps and a full-scale range of ±250, ±500, ±1000, and ±2000dps<br />
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g<br />
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection<br />
* PMIC & LiPo<br />
* Joystick<br />
* Buttons<br />
* RGB LED's<br />
* IR<br />
* Arduino Headers<br />
<br />
===Prototype===<br />
Design for the badge prototype v0.1 was finished on 4th Jan, files are on GitHub. The aim is to have 2-3 PCB's made for testing and firmware development.<br />
<br />
<br />
===Production===<br />
As yet there is no information on the final production board other than we expect to make around 1500 and have them ready at least 1.5 months before the event.<br />
<br />
=Software=<br />
===Badge Firmware===<br />
<br />
===Gateway===<br />
<br />
===Server side===<br />
<br />
=Hacking=<br />
TiLDA Mk2 is base around the Arduino Due platform and this makes it easy to get started writing your own firmware from scratch.<br><br />
Unlike the Due, TILDA is not just a bare board and it all ready has lots of hardware wired up to the pins.<br />
In order to help make things easier when working with the Arduino IDE we have definite our own board profile. This has a few tweaks to support the differences between Due and TiLDA Mk2 pin usage. It also include a lot of handy pin shortcuts to the TiLDA device pins.<br/><br />
So instead of having to go back to the TiLDA Mk2 Pin map and looking up just which digital pin controls the RED for LED1 you can just use LED1_RED in pinMode() and digitalWrite calls.<br/><br />
<br />
To use our board definition you will need to first get the Arduino 1.5.5 IDE from [http://arduino.cc/en/Main/Software#toc3 here]<br/><br />
Next you can download the TiLDA Mk2 Firmware project from either the [https://github.com/EMF-TiLDA/Mk2-Firmware github repo] or via [https://github.com/EMF-TiLDA/Mk2-Firmware/archive/master.zip direct download]<br/><br />
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/<br><br />
<br />
Start the Arduino IDE and your will be able to select TiLDA Mk2 for the Tools->Board menu<br />
<br />
=Sponsors=<br />
<br />
<br />
= Github =<br />
<br />
* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design<br />
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant documentation<br />
* [https://github.com/emfcamp/Mk2-Firware Firmware] - source code for the badge software<br />
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network<br />
<br />
[[Category: TiLDA]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=TiLDA_MKe_-_the_dream&diff=1448TiLDA MKe - the dream2014-08-08T11:49:20Z<p>Ms7821: Add github links</p>
<hr />
<div>== '''Note:''' THIS IS NOT THE FINAL BADGE SPECIFICATION. WE MIGHT HAVE HAD TO DROP THE SPECIFICATION A LITTLE :( ==<br />
<br />
The TiLDA MKe project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Solexious|Charles]], [[User:thinkl33t|Bob]] and [[User:Dpslwk|'RepRap' Matt]]<br/><br />
If you wish to chat about the badge head over to the [irc://chat.freenode.com/##tilda ##tilda] IRC channel on free node<br/><br />
Why MKe? http://en.wikipedia.org/wiki/E_(mathematical_constant)<br />
<br />
=Aim= <br />
The main aim of the 2014 badge is to give camp attendees live schedule updates and notifications. As with the original TiLDA we wanted to keep with an Arduino compatible platform that will allow badge hacking during and after the camp. As with previous badge all code and design files are available. Work can be found here on github.com/EMF-TiLDA <br />
<br />
==Features and Functions==<br />
A initial planing session was held during the Newcastle MakerFaire 2013, during which a list of essential features was decide upon along with a big list of shiny, mad ideas that may happen depending on budge and time.<br/><br />
The notes from that session can be found here [[TiLDA 2/Ideas List]]<br />
===Essential===<br />
The following are considers core things that the badge must do for EMF2014<br />
* Receive and display announcements on talks scheduling<br />
** user registers their lanyard and which talks/workshops they are interested in on the emf web site <br />
** lanyard’s registered for talks receives reminders and notice of when and where a talk will be especially important if a talk is moved (time/location)<br />
* IR interaction<br />
** could be used for business card mode, allow users to exchange info at push of a button<br />
** games<br />
** talking to TiLDA or SiNE<br />
* Torch Mode<br />
** One of the side effect of the two RGB LED's on TiLDA was they made a great torch <br />
* Arduino Compatible<br />
* Work during the event and be useful afterwards<br />
** Battery voltage measurement and display, Charging management<br />
<br />
===Nice to have===<br />
The following are things that we hope to implement if we have the time and budget.<br />
* Locations tracking<br />
** By looking at which gateway the badge is talking to we can get a ruff idea of where on the camp site a badge is located<br />
* Send text to it, not just talks (SMS you friends badge?)<br />
** we will have a screen and ability to display text, so sending something to a other set badge should be easy.<br />
* Use the spearks as a PA system, (download recorded WAV over network then synced playback start)<br />
* TiLDA ad SiNE reprogramming<br />
** If we can develop some new firmware to go on SiNE or TiLDA, we might be able to reprogram them from Mk2 by jumping the ISP headers together<br />
* TTS https://github.com/going-digital/Talkie<br />
<br />
=Hardware=<br />
<br />
The following hardware has been included on the badge.<br />
<br />
N.B. Due to funding issues the badge may/will be much lower spec than this. ''We almost certainly will not have an e-paper display'' :(<br />
<br />
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]<br />
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge<br />
** 32bit ARM Cortex M3 * 84MHz<br />
** 512KBytes Flash RAM<br />
** 96KBytes of SRAM<br />
* <s>[http://repaper.org Repaper 2.7" ePaper display]<br />
** a-Si TFT active matrix Electronic Paper Display(EPD)<br />
** Resolution: 264 x 176<br />
** Ultra low power consumption<br />
** Super Wide Viewing Angle - near 180°<br />
** Extra thin & light<br />
** SPI interface<br />
** Outline Dimension 70.42 x 45.80 mm<br />
** Active Area 57.288 x 38.192 mm</s> <br />
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]<br />
** 868Mhz RF Transceiver<br />
** Simple UART interface<br />
** Low power sleep mode<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro<br />
** I2C interface<br />
** Tri-Axis angular rate sensor (gyro) with a sensitivity up to 131 LSBs/dps and a full-scale range of ±250, ±500, ±1000, and ±2000dps<br />
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g<br />
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection<br />
* PMIC & LiPo<br />
* Joystick<br />
* Buttons<br />
* RGB LED's<br />
* IR<br />
* Arduino Headers<br />
<br />
===Prototype===<br />
Design for the badge prototype v0.1 was finished on 4th Jan, files are on GitHub. The aim is to have 2-3 PCB's made for testing and firmware development.<br />
<br />
<br />
===Production===<br />
As yet there is no information on the final production board other than we expect to make around 1500 and have them ready at least 1.5 months before the event.<br />
<br />
=Software=<br />
===Badge Firmware===<br />
<br />
===Gateway===<br />
<br />
===Server side===<br />
<br />
=Hacking=<br />
TiLDA Mk2 is base around the Arduino Due platform and this makes it easy to get started writing your own firmware from scratch.<br><br />
Unlike the Due, TILDA is not just a bare board and it all ready has lots of hardware wired up to the pins.<br />
In order to help make things easier when working with the Arduino IDE we have definite our own board profile. This has a few tweaks to support the differences between Due and TiLDA Mk2 pin usage. It also include a lot of handy pin shortcuts to the TiLDA device pins.<br/><br />
So instead of having to go back to the TiLDA Mk2 Pin map and looking up just which digital pin controls the RED for LED1 you can just use LED1_RED in pinMode() and digitalWrite calls.<br/><br />
<br />
To use our board definition you will need to first get the Arduino 1.5.5 IDE from [http://arduino.cc/en/Main/Software#toc3 here]<br/><br />
Next you can download the TiLDA Mk2 Firmware project from either the [https://github.com/EMF-TiLDA/Mk2-Firmware github repo] or via [https://github.com/EMF-TiLDA/Mk2-Firmware/archive/master.zip direct download]<br/><br />
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/<br><br />
<br />
Start the Arduino IDE and your will be able to select TiLDA Mk2 for the Tools->Board menu<br />
<br />
=Sponsors=<br />
<br />
<br />
= Github =<br />
<br />
* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design<br />
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant documentation<br />
* [https://github.com/emfcamp/Mk2-Firware Firmware] - source code for the badge software<br />
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network<br />
<br />
[[Category: TiLDA]]</div>Ms7821https://wiki.emfcamp.org/2014/w/index.php?title=Teams&diff=1435Teams2014-08-07T16:32:37Z<p>Ms7821: </p>
<hr />
<div>These are the teams which make up the EMF organisation. For more information on how EMF is run, and the duties of team leaders, see the [[Organisation]] page.<br />
<br />
If you're interested in getting involved with a team which doesn't currently have a lead, please get in touch on [[IRC]]. If you're interested in joining a team, get in touch with the team lead.<br />
<br />
{| class="wikitable sortable"<br />
! Team<br />
! Description<br />
! Lead<br />
! Deputy Lead(s)<br />
|-<br />
| [[Team:Admin]]<br />
| Top-level organisation, licensing, site planning<br />
| [[User:Russ]]<br />
| [[User:Jonty]]<br />
|-<br />
| [[Team:Finance]]<br />
| Dealing with the money<br />
| [[User:Russ]]<br />
| Paul2<br />
|-<br />
| [[Team:Site]]<br />
| Tents, fences, trackway, etc.<br />
| WillH<br />
| [[User:Russ]]<br />
|-<br />
| [[Team:Power]]<br />
| All things power, as well as basic site lighting.<br />
| [[User:Benny]]<br />
| Will H<br />
|-<br />
| [[Team:Sanitation]]<br />
| Water supply, showers, toilets, rubbish.<br />
| Paul2<br />
| Crypt<br />
|-<br />
| [[Team:Security]]<br />
| Making sure the site is safe.<br />
| Crypt<br />
| <br />
|-<br />
| [[Team:NOC]]<br />
| Networking<br />
| [[User:JasperWallace]]<br />
| Will H, [[User:davidc]]<br />
|-<br />
| [[Team:Web]]<br />
| Web sites, ticket sales, volunteering, and CfP systems<br />
| [[User:ms7821|Mark]]<br />
| [[User:JasperWallace]] (probably?)<br />
|-<br />
| [[Team:Content]]<br />
| Organising talks/workshops/etc<br />
| [[User:Jonty]]<br />
| Tef<br />
|-<br />
| [[Team:Bar]]<br />
| Booze, and such<br />
| Chris W<br />
| [[User:Russ]]<br />
|-<br />
| [[Team:First Aid]]<br />
| Making sure we don't kill ourselves, as well as looking after attendee welfare.<br />
| [[User:Oni|Oni]]<br />
| Katie<br />
|-<br />
| [[Team:Catering]]<br />
| Organising food providers<br />
| Nick<br />
| [[User:JasperWallace]] (maybe?)<br />
|-<br />
| [[Team:InfoDesk]]<br />
| Providing information during the event<br />
| SamLR<br />
|<br />
|-<br />
| [[Team:Volunteering]]<br />
| Managing volunteers across all stages<br />
| Nick<br />
| Lyndsey/Kate<br />
|-<br />
| [[Team:Spawn]]<br />
| Liaising with UCL for management of the kids area, activities, and childminding<br />
| [[User:Jonty]]<br />
| <br />
|-<br />
| [[Team:Stage]]<br />
| Staging, stage lighting, audio, and projection.<br />
| [[User:TimRTerrible]]<br />
| [[User:gmc]]<br />
|-<br />
| [[Team:Video]]<br />
| Liaising with the video streaming and recording people.<br />
| WillH<br />
| SamLR<br />
|-<br />
| [[Team:Shiny]]<br />
| Site decoration, lights, installations. Shiny things.<br />
| SamLR<br />
| [[User:Jonty]]<br />
|-<br />
| [[Team:Badge]]<br />
| Badge building, and infrastructure.<br />
| [[User:Dpslwk|Dpslwk]] ([[User talk:Dpslwk|talk]])<br />
| [[User:thinkl33t|Bob]]/[[User:Jonty]]<br />
|-<br />
| [[Team:Sysadmin]]<br />
| Making sure servers work, on and off site.<br />
| [[User:JasperWallace]]<br />
| [[User:Russ]]<br />
|-<br />
| [[Team:Phone]]<br />
| Looking after 2G, DECT, SIP etc.<br />
| kevinprince<br />
|<br />
|-<br />
| [[Team:Villages]]<br />
| Looking after villages and their requirements<br />
| Crypt<br />
|<br />
|-<br />
| [[Team:Sponsorship]]<br />
| Looking after sponsors/vendors and their requirements.<br />
| [[User:Jonty]]<br />
|<br />
|-<br />
| [[Team:Lounge]]<br />
| Organising the Lounge area<br />
| [[User:Amx109|amx109]]<br />
| [[User:Will-Do]]<br />
|-<br />
| [[Team:Comfort]]<br />
| Planning conflict resolution and making sure people will feel safe in advance<br />
| Jane<br />
| martind<br />
|-<br />
| [[Team:Logistics]]<br />
| Organising the non-site logistics (e.g. getting stuff like the badges from London to the site)<br />
| [[User:JasperWallace]]<br />
| <br />
|}</div>Ms7821