Electromagnetic Field - User contributions [en]

Feedback

2014-09-05T11:05:21Z

Thinkl33t: /* Stuff that could be improved */

{{link-banner}}
Please let us know what went well and what didn't go well at EMF this year. We really do care about your feedback and we'll try and improve this for next time.

Add your feedback below:

== Good Stuff ==

* Location
* Badges
* Variety of talks [+1]
* Showers [+∞]
* Hand washing facilities
** putting the showers (with hot water in handbasins) next to toilets v.good
* Parking
* Shuttle trailer to car park
** ... and shuttle to BLY railway station. Made coming by public transport a doddle.
* Power & data infrastructure - pretty much rock solid throughout! [+2]
* Speedy response of volunteers/organisers to problem resolution
* Service at the bar was good (while the drinks lasted), and it was very nice to have ''multiple'' indoor social spaces, esp for people who wanted a quieter lounge as well as louder bar.
** Being able to check beer availability on the till website was awesome!
** The lounge was great - the decorations, beanbags, no-shoes rule and power were a great combination
* Floor panel roads [+5]
* String lights (cut through to showers was awesome!) [+2]
* Ability to hire tables/chairs/marquees/hay bales etc. - were all good quality, too. [+2]
* Kids workshops [+2]
* Arcade! [+1]
* Friendliness of other attendees [+1]
* First aid [+1]
* Shop - selling books of speakers was a really nice idea, and it was good to talk to speakers & do signing there afterwards.
* That spinning music installation.
* Lighting - I didn't have to turn my torch on at all, but it was still dark enough in my tent to sleep.
* Club Mate.
* Ring making workshop
* Lake was pretty
* Supportive atmosphere for speakers and very nice feedback afterwards
* Water: plentiful flow, tasty water, cool dispensers [+1]
** Hand soap by taps (udders?)
* Keeping toilet paper supplies topped up in all the toilets
* Nice choice of real ales and proper cider
* Lasershow + Chiptunes in Tent A
* Tschunk
* Everything that Dimitri brought along [+1]
* EMF CTF: Like getting lock pickers to cook your food, playing IRL replay,relay and pre-play attacks and memory corruption, sadly no real-life cross-site scripting :)
* Tea and food provided during set up really helped me keep going.
* How to crimp ethernet cable sheets were brilliant. They made sure everyone was using the same standard and anyone new to crimping could carry them to remember the order.
* There were lots of crimping tools and wire strippers to borrow during set up.
* Vehicles: there were enough to get stuff around the site but not too many that I was worried about getting run over.
* EMF hi vis jackets were awesome.
* Simon Singh [+1]
* Till system in the bar - I found it very quick and easy to use after about 10 mins practice.
* Cashback in the bar.
* Dutch food.
* Laser cut items for sale.
* Badge creations competition is a nice way to encourage people to tinker with the badges and share the results.

== Stuff that could be improved ==

* Buy more beer! [[User:Russ|Russ]] ([[User talk:Russ|talk]]) [+1]
** No firkins next time, kils only! --[[User:Sde|Sde]] ([[User talk:Sde|talk]])
* Toilets... 'nuff said! [[User:AndyB|AndyB]] ([[User talk:AndyB|talk]]) [+2]
** Agreed - I've seen portakabins (like the shower blocks) that containing proper flushing loos. They're ''much'' less stinky and likely to block up than the portaloos we had, which didn't always seem willing to drop their loads into their collection tanks, leading to nastiness and health hazards (even without the pumping contractor being rubbish)
*** This was actually what we wanted, but they're tremendously expensive. Suggestions for vendors welcome! --[[User:Jonty|Jonty]]
** Additionally, LIGHTS in the toilets. Having to use my phone / badge as a torch to see what was going on while i cleaned off the toilet before sitting down was particularly difficult. [[User:Thinkl33t|Thinkl33t]] ([[User talk:Thinkl33t|talk]]) 20:05, 1 September 2014 (UTC)
** thunderboxes2go.co.uk are good and know how to handle local authority problems, they have done shambala for 10+ years - high enough capacity to not need emptying during the event [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]])
** Maybe ask Cambridge & District CAMRA who provided the toilets for Cambridge 41st beer festival - they had some fairly nice flushing toilets which came on a trailer, a bit like the posh wash showers. I think Jonty mentioned that a lot of providers were put off by the fact that we're a festival. Well, if these guys are ok with providing for a beer festival, they must be pretty brave! -[[User:Alecjw]]
** Definite vote for the trailer-style flushing toilets, with multiple cubicles (+sinks, lights and mirrors) on one tow-along trailer, just like the showers. I've seen these at MANY festivals - though, granted, usually only in 'posh' camping/press/VIP areas. Should be possible if you manage to convince the providers that we're not a rowdy bunch of drunken teenagers!
** A clue to the problem with the chemical toilets is in the name: no chemical sanitiser/deodoriser was used in any toilet I tried. Adding Elsan or similar to the toilets would probably have made them much more acceptable. [[User:PhilSwinbank|PhilSwinbank]] ([[User talk:PhilSwinbank|talk]]) 22:18, 3 September 2014 (UTC)
* Make sure that drinking water is clearly labelled as such
* More food and drink options
** Eg. non-caffeine / low or no sugar options
** Chips!
** Jacket potato vendor
** Healthy 'green' food
** also possibly going on later, a lot of the places shut up shop quite early.
** A late night vendor would be fantastic - doesn't have to be fancy food, but just something hot to eat after 9pm [+4]
** Soft drinks! [+2]
*** I helped organise a ball at university. Coca Cola sponsored us and provided very cheap (maybe free) drinks to the event. Before next time, someone remind me to look into them doing this for EMF [[User:MatS|MatS]] ([[User talk:MatS|talk]]) 14:02, 4 September 2014 (UTC)
* Survey positions of lanes/tents/DKs as early as possible before items arrive and mark out.--[[User:Sully|Sully]] ([[User talk:Sully|talk]]) 12:06, 1 September 2014 (UTC)
** This was planned but we were let down by the rather poor state of mobile GIS software.
*** there are multiple open source solutions for mapping, try https://umap.openstreetmap.fr/en/ or reach to out myself or #openstreetmap, there are many OSM'ers in the UK, [[User:Jburgess777|Jburgess777]] ([[User talk:Jburgess777|talk]]).
* Similar to this, measure for fence panels and drop stillage appropriately, to avoid the need to carry loads of them right up the camping field by hand
* Make it longer! There was loads of cool stuff I didn't have change to check out :( After all that work everyone does, it was a shame I couldn't experience it all! ([[User:Chewie|Chewie]]) ((I still say make it a week long ;) ([[User:BuildTheRobots|Fligg]]))
* Visibility of presentations in tents (brighter projectors/darker tents??) ([[User:StuartL]]) [+3]
* Use more plasma screens in stages instead of projectors ([[User:Markp]]). Or (better, as then the speaker can point to things) black fabric shades for the screen or marquee roof
** Next time dark tents. This was a total nightmare, sorry. --[[User:Jonty|Jonty]]
* washing points over drains/soakaway so the ground doesn't get muddy ([[User:Chewie|Chewie]]) [+4]
* Mark out/allocate spaces for villages who had pinpointed locations on maps ([[User:Markp]]) [+2]
** Space needed by villages was very hard to judge before they were set up, especially once non-village campers started on site ([[User:BuildTheRobots|Fligg]])
* Improved arrangements for washing and washing up (and handling the waste water from that) [+1]
* Provide sanitizer gel dispensers at water points and near loos [+2]
* Have the schedule linked off the EMF main page
** It was, but not on the First day...we forgot! See "Programme" at the top of the main website. --[[User:Jonty|Jonty]]
* Distribute and display paper schedules (even if their might be some last-minute changes) [+3]
** They were supposed to be available at the info tent, not sure what happened there. --[[User:Jonty|Jonty]]
** Or have small screens at the entrances to tents showing what's currently on & what's next.
*** We wanted to do this but simply ran out of time. --[[User:Jonty|Jonty]]
* Much more workshop activity (more hands-on electronics and physical making) [+6]
** Next time: Many more workshop tents. We totally underestimated availability and demand. [+1] --[[User:Jonty|Jonty]]
* Do have component vendors (maybe at their cost for marquee/power/space)
** This is very difficult without a clear list of what will sell, as CPC was arranged to appear but wanted advisement ([[User:Stanto]])
*** Would the (longer and with more repeats next time) workshop list work as advisement? Could workshop leaders be asked to provide suggestions for components that would be good to have available on site after their workshop?
* Pick a flatter site (for ease of disabled access)
* Ask speakers for bio's to include with their abstracts. Given them an abstract length up-front instead of editing it in an ad hoc way. Confirm acceptance to speakers and workshop organisers earlier.
** Do this after talks have been accepted. I didn't write my talk so didn't know details until I got the OK.
** The CFP was a bit of a nightmare this year, we'll certainly be doing this in 2016. --[[User:Jonty|Jonty]]
* Make and enforce a clear music curfew (say from midnight or 1am or 2am to 8 or 9am or 10am), to defend those sleeping from (eg) the technoevangelists and the drunk [+4]
** Perhaps try to select a site next time where we can make part of the site to be a quiet area, eg a part surrounded by trees for natural sound insulation. Then enforce a noise curfew there. I'm not keen on the idea of having a noise curfew covering the entire camp though. [[User:Alecjw]] [+1]
** Seconding enforced quiet/family camping area, but no overall noise curfew. It didn't take long to get away from the worst noise, and the end of the field by the kids' area was incredibly quiet (though strangely empty!!)
** Well, not quite - I need sleep to function, so camped in the quiet area - a nearby group thought 6:30am was the right time to turn on their music system. Not so good.
* Loos not so near food vendors (pong + visible urinals offputting) [+5]
* stronger enforcement/signage of quiet camping area [+5]
* an explicit invitation (with clear instructions) to report Code of Conduct violations in open ceremony, brochure, Twitter, etc. We had no direct reports to Team Comfort, but several anecdotal tweets after the event -- when it's much too late. [[User:Martind|Martind]] ([[User talk:Martind|talk]]) 20:58, 1 September 2014 (UTC) [+1]
* quieter, less-enclosed and more spacious bar (I suffer from social anxiety when I'm closed in with crowds, so I had a very sober emf!). [[User:Jane C|Jane C]]
** perhaps an outdoor seating area if a larger marquee is too costly.
*** There was an outdoor seating area set back to the right of the bar under a marquee, however the marquee vendor put it in the wrong place a day late, so wasn't as obvious, and didn't get hay bales until Saturday evening. --[[User:Jonty|Jonty]]
* use our collective knowledge of technology to sort accessibility issues
**ring-fence money for things like closed-loop in the stages early on.
**ask people about their access requirements much earlier on - e.g. when they buy a ticket - so that there is more time to meet these requirements (or reach a workable compromise)
**Build some kind of working system for preventing able-bodied people from using the disabled loos and showers (radar keys that only work when the loo is empty?) [[User:Jane C|Jane C]]
***Disagree with this as it reduces overall toilet/shower bandwidth, but would wholly agree with a solution whereby those who could only use limited facilities (disabled, families, etc) could queue-jump into those facilities the moment they because available. [[User:StuartL|StuartL]]
* Info desk didn't seem to have the details wrt. volunteers, so when I volunteered I was sent out and found I wasn't needed. Suggest splitting the job - having a volunteer team leader (or several, in shifts) whose job it is to know who is where and also to make sure nobody gets stuck on a gate for 12 hours (eg. rotating people to more interesting places every couple of hours). ([[User:TonyHoyle|TonyHoyle]])
** There was a separate volunteer manager in the same tent, this should not have happened. Sorry about that. --[[User:Jonty|Jonty]]
* Also similar to this, a register of 'on call' people - excess volunteers who can deal with sudden demands for people (esp. in the case of fire I can imagine this would be extremely useful - you'd potentially need to cordon off a largish area very quickly, and that takes people. More mundane reasons would be a talk/workshop accumulating a large queue that needs managing). ([[User:TonyHoyle|TonyHoyle]])
** There were shifts for people to be "on call" but they weren't obvious. We'll make sure this is easier. --[[User:Jonty|Jonty]]
** with earlier (/working) workshop sign-up, I would have put myself on call - instead I was waiting to hear what workshops would be available when.
* add GPS or other location aware technology like BTLE/iBeacon to the badges for automatic now/next notifications [[User:Jburgess777|Jburgess777]] ([[User talk:Jburgess777|talk]]).
* Locking wristbands that don't get any tighter.
* Having a tent for Badge Operations would be pretty handy - similar size to the workshop tent, that could be set up as a production line / fixing area if needed. If not (hopefully) it would be a rolling workshop area for people to work of hacking their badges, writing new software, adding hardware etc. ~~

==Suggestions==
* Ask for an optional email address for each ticket to go on your announce only mailing list. Only the person that bought the tickets got your emails and they were slow to forward them on meaning most messages were received too late.
* Ask for age of children when booking, to give better planning stats for workshops etc. [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]])
* A talk (a bit like lightning talks) where people are given 5-10 minutes to share what they did with the previous event's badge. (If someone sends me the competition winners/runners up, I'll co-ordinate it) [[User:MatS|MatS]] ([[User talk:MatS|talk]]) 07:54, 1 September 2014 (UTC)
* Pre-paid accounts for spending money on food/beer/whatever to negate need for cash ([[User:Markp]])
* Have a fleet of communal wheel-barrows to help people transport their stuff from car to campsite [+2]
** Stepney City Farm have a fleet of broken wheelbarrows – fix ’em, use ’em, everybody wins! ([[User:Andylolz]])
** Or purchase some sack trolleys
* contactless payment gear for food, beer, workshops
** We had contactless payment for beer! (And we also offered cashback.) We should have messaged that better. Contactless payment for other things is complex, as we don't really control them. [[User:Russ|Russ]] ([[User talk:Russ|talk]])
* forewarn food vendors to expect all-day demand, not just mealtimes, so they can stock and staff appropriately [+1]
** food vendors were pretty much *events* caterers, used to feeding people snacks/lunch, we need *festival* caterers who are used to feeding people who are staying for a number of days. thethalicafe.co.uk? bedouin tent (shambala)? +late night options [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]])
*** It's really difficult to get caterers. Now we're a bit better known it's getting easier. [[User:Russ|Russ]] ([[User talk:Russ|talk]])
* pinboard (offline) notice board everyone can contribute to (lost property, mini event notices eg rocket launches, would like to meet.., etc) [+1]
** This was supposed to be next to the info tent, but got lost in the last-minute panic. --[[User:Jonty|Jonty]]
* Ask people who want to give workshops if they'd be happy to give more than one session - the blacksmiths' output was extreme, but even giving two or three sessions would greatly increase the % of attendees who could sign up.
** Many workshop submissions specified that already, the issue was actually with finding space for them as we only had one workshop tent. We'll have many next time! --[[User:Jonty|Jonty]]
* Sign-ups some kind of "express preference" systems, so most people (including those who don't check email regularly) can get at least one of their top choices, rather than first-come-first-served.
** Online workshop sign-up is a priority for next year. --[[User:Jonty|Jonty]]
* Board games tent in the evenings [+4]
* Poker tent
* Be less ambitious with badge functionality [+3]
** And provide full documentation of features/functionality [+1]
** And sample code for each function
** Perhaps a back-to-basics through-hole design that comes with soldering iron, solder and instructions?
** I think we might build on this design for the next event. [[User:Russ|Russ]] ([[User talk:Russ|talk]])
** Software that doesn't involve an OS (but rather more conventional Arduinoery) might be more easily hackable by others during/after the event? Especially given libraries for people to do amusing things with the peer-to-peer radio...
*** That is actually much harder to build anything decent with. The badges are normal arduinos and all the libraries are available, you don't have to use the EMF OS, it was designed for people to write normal Arduino code for! --[[User:Jonty|Jonty]]
* EMF is unlike other festivals - for a large number of people, carrying kit to/from car is impractical and security walking every car through site is time-consuming and volunteer-intensive (not to mention the fact that cars driving off site weren't walked off). Suggest that the parking area is directly next to and easily accessible from the camping area (e.g. just separated by hay bales to stop cars driving on to the camping area).
** As a village/car user you could generally provide your own security person walking in front of the car. This works 2 fold: 1) security doesn't need to walk for you 2) less waiting time for you since you already provide someone to walk.
** The plan for this was to allow people to drive onto site on the Thursday evening. It wasn't very well communicated and we had a *very* tight setup schedule so we needed to reduce this as much as possible. This is ultimately an issue with our setup schedule
** It wouldn't work on this site, but for some locations it might be possible to have a drop-off point close to camping (with a limited number of cars at one time), better idea than having cars (ignition source) close to tents. Some people were taking the mickey on Monday morning, many people driving onto site that could have carried things instead tying up volunteer resources to escort them.
* Provide job descriptions for traffic control, parking and entrance gatehouse. Instructions were handed from volunteer to volunteer by word of mouth and whilst common sense prevailed, it would have been useful to have instructions as to what to do under certain circumstances and a list of answers to FAQs, e.g.:
** What if somebody didn't have a parking ticket and wanted to park?
** What if somebody was just dropping off - where should they do this?
** What times were shuttle buses running?
** What times the gates were open/closed?
** Have a priority queue for people with machine readable tickets (ie paper!)
** Volunteer training was lost by the wayside for some roles, we'll fix that. --[[User:Jonty|Jonty]]
* Add suggested age ranges for all workshops, some of the "adult" workshops were also very suitable for children (e.g. electronic fashion, solar pv) or could have been run once in main workshop once in kid's area [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]])
** This was supposed to happen but got missed off by accident. Apologies. --[[User:Jonty|Jonty]]
* Bolt the fence from the right side, I know we didn't even want it at all but local authorities can be fussy, I've been at a festival before who did the same and they made them fix it during the event.. [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]])
* Want the good coffee on Monday morning, especially for drivers :) Maybe in the car park to help persuade people off site. [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]])
* Would be good to have eggs, fresh milk, bacon at the shop (there was a comment like "we don't have eggs, they break too easily" - so charge extra to cover this, though it's probably not as bad as you think..) [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]])
** The shop was being run by an external team, we didn't control what they stocked. --[[User:Jonty|Jonty]]
** Morrisons did a tent with Milk, Bread, Burgers, BBQs etc @ http://www.festivalofcycling.org/expo/name/morrisons/, might be worth asking them? [[User:Jburgess777|Jburgess777]] ([[User talk:Jburgess777|talk]])
* Start ticket sales (a couple of months?) earlier, maybe with a slightly bigger difference between early ticket prices and full price to encourage attendees to get in early (which in turn would improve cashflow) [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]]) [+1]
* Start ticket sales *now* whilst you have all the publicity or at least have a page up where people can register to be emailed once the next event has tickets for sale. That way you get your current mailing list + everyone else who has only just learned about it as your audience. [[User:Alteralias|Alteralias]]
** Until we have a date/venue that is not a great plan, as we'd end up with a lot of refunds. --[[User:Jonty|Jonty]]
*** Although a massive mailing list/Twitter/Facebook push might be a good idea so people are ready to hear that tickets are on sale.
* Cluster the talks into related-topic sessions
** This is very difficult due to availability of speakers, and we'd rather people with very specific interests had talks to go to all weekend rather than just on one afternoon. --[[User:Jonty|Jonty]]
*** More Q&A sessions like the security one, getting multiple speakers on a topic together for questions might be a better idea.
* Volunteering stuff ([[User:HughePaul|HughePaul]])
** Whiteboard in info tent for current issues / tasks, handover
** Have info tent next to security tent so both can be available at the same time and all the time.
*** The info tent and the gatehouse/security tent could be two sides of the same erection.
** have predefined named people in shifts for head of / coordination of volunteering (could also double as an info/security tent staff)
** maybe stream some talks in info tent so they don't feel like they are missing things
** more formal defined (and communicated) lost-property form and procedure
** define volunteer job roles to make handovers easier and so we know what we are meant to be doing
* Have dedicated blog / tweet / website updating person/team
* big screen with latest official event update tweets
** Very expensive to hire. --[[User:Jonty|Jonty]]
*** small screen with latest updates? even a 20 inch cycling through the latest tweets in a big font?
* info about getting DISconnected from DKs and leaving the site in vehicles
** This was badly handled, and we only realised when it was too late. --[[User:Jonty|Jonty]]
* perhaps worth putting up a summary of the overall budget after the event, so people can see what's costly?
* website needs to be designed around the info people need at the time
** days before the event front page should have location, travel, packing, instructions such as workshop booking, village booking, volunteering
** during it should have info about DKs, current day schedule (possibly whats on and next), links to streams, power and internet usage :), lost property instructions, latest updates/tweets
** after have thanks, photos, tilda sales, etc
* Some kind of welcome tent / meet-a-stranger area / badges saying "talk to me" (and not reliant on tech that might not be available/working till later on) / person-bingo-style game - deliberately flagged up as a way for people to meet new people, including if they came on their own / hadn't been to anything like this before. For many the whole event will be like that anyway - it wouldn't hurt to help out those shyer / newer / more awkward. Maybe there could be a welcoming/newbies/friendliness team prior to next time who came up with stuff to try of this nature (all utterly optional, of course)?
* More flying cars (requested by someone leaving site when asked what they thought was lacking)
* Dual controls quad-copter training. So someone can learn to fly and know the "instructer" can take over if it gets out of hand.

Feedback

2014-09-05T11:04:59Z

Thinkl33t: /* Stuff that could be improved */

{{link-banner}}
Please let us know what went well and what didn't go well at EMF this year. We really do care about your feedback and we'll try and improve this for next time.

Add your feedback below:

== Good Stuff ==

* Location
* Badges
* Variety of talks [+1]
* Showers [+∞]
* Hand washing facilities
** putting the showers (with hot water in handbasins) next to toilets v.good
* Parking
* Shuttle trailer to car park
** ... and shuttle to BLY railway station. Made coming by public transport a doddle.
* Power & data infrastructure - pretty much rock solid throughout! [+2]
* Speedy response of volunteers/organisers to problem resolution
* Service at the bar was good (while the drinks lasted), and it was very nice to have ''multiple'' indoor social spaces, esp for people who wanted a quieter lounge as well as louder bar.
** Being able to check beer availability on the till website was awesome!
** The lounge was great - the decorations, beanbags, no-shoes rule and power were a great combination
* Floor panel roads [+5]
* String lights (cut through to showers was awesome!) [+2]
* Ability to hire tables/chairs/marquees/hay bales etc. - were all good quality, too. [+2]
* Kids workshops [+2]
* Arcade! [+1]
* Friendliness of other attendees [+1]
* First aid [+1]
* Shop - selling books of speakers was a really nice idea, and it was good to talk to speakers & do signing there afterwards.
* That spinning music installation.
* Lighting - I didn't have to turn my torch on at all, but it was still dark enough in my tent to sleep.
* Club Mate.
* Ring making workshop
* Lake was pretty
* Supportive atmosphere for speakers and very nice feedback afterwards
* Water: plentiful flow, tasty water, cool dispensers [+1]
** Hand soap by taps (udders?)
* Keeping toilet paper supplies topped up in all the toilets
* Nice choice of real ales and proper cider
* Lasershow + Chiptunes in Tent A
* Tschunk
* Everything that Dimitri brought along [+1]
* EMF CTF: Like getting lock pickers to cook your food, playing IRL replay,relay and pre-play attacks and memory corruption, sadly no real-life cross-site scripting :)
* Tea and food provided during set up really helped me keep going.
* How to crimp ethernet cable sheets were brilliant. They made sure everyone was using the same standard and anyone new to crimping could carry them to remember the order.
* There were lots of crimping tools and wire strippers to borrow during set up.
* Vehicles: there were enough to get stuff around the site but not too many that I was worried about getting run over.
* EMF hi vis jackets were awesome.
* Simon Singh [+1]
* Till system in the bar - I found it very quick and easy to use after about 10 mins practice.
* Cashback in the bar.
* Dutch food.
* Laser cut items for sale.
* Badge creations competition is a nice way to encourage people to tinker with the badges and share the results.

== Stuff that could be improved ==

* Buy more beer! [[User:Russ|Russ]] ([[User talk:Russ|talk]]) [+1]
** No firkins next time, kils only! --[[User:Sde|Sde]] ([[User talk:Sde|talk]])
* Toilets... 'nuff said! [[User:AndyB|AndyB]] ([[User talk:AndyB|talk]]) [+2]
** Agreed - I've seen portakabins (like the shower blocks) that containing proper flushing loos. They're ''much'' less stinky and likely to block up than the portaloos we had, which didn't always seem willing to drop their loads into their collection tanks, leading to nastiness and health hazards (even without the pumping contractor being rubbish)
*** This was actually what we wanted, but they're tremendously expensive. Suggestions for vendors welcome! --[[User:Jonty|Jonty]]
** Additionally, LIGHTS in the toilets. Having to use my phone / badge as a torch to see what was going on while i cleaned off the toilet before sitting down was particularly difficult. [[User:Thinkl33t|Thinkl33t]] ([[User talk:Thinkl33t|talk]]) 20:05, 1 September 2014 (UTC)
** thunderboxes2go.co.uk are good and know how to handle local authority problems, they have done shambala for 10+ years - high enough capacity to not need emptying during the event [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]])
** Maybe ask Cambridge & District CAMRA who provided the toilets for Cambridge 41st beer festival - they had some fairly nice flushing toilets which came on a trailer, a bit like the posh wash showers. I think Jonty mentioned that a lot of providers were put off by the fact that we're a festival. Well, if these guys are ok with providing for a beer festival, they must be pretty brave! -[[User:Alecjw]]
** Definite vote for the trailer-style flushing toilets, with multiple cubicles (+sinks, lights and mirrors) on one tow-along trailer, just like the showers. I've seen these at MANY festivals - though, granted, usually only in 'posh' camping/press/VIP areas. Should be possible if you manage to convince the providers that we're not a rowdy bunch of drunken teenagers!
** A clue to the problem with the chemical toilets is in the name: no chemical sanitiser/deodoriser was used in any toilet I tried. Adding Elsan or similar to the toilets would probably have made them much more acceptable. [[User:PhilSwinbank|PhilSwinbank]] ([[User talk:PhilSwinbank|talk]]) 22:18, 3 September 2014 (UTC)
* Make sure that drinking water is clearly labelled as such
* More food and drink options
** Eg. non-caffeine / low or no sugar options
** Chips!
** Jacket potato vendor
** Healthy 'green' food
** also possibly going on later, a lot of the places shut up shop quite early.
** A late night vendor would be fantastic - doesn't have to be fancy food, but just something hot to eat after 9pm [+4]
** Soft drinks! [+2]
*** I helped organise a ball at university. Coca Cola sponsored us and provided very cheap (maybe free) drinks to the event. Before next time, someone remind me to look into them doing this for EMF [[User:MatS|MatS]] ([[User talk:MatS|talk]]) 14:02, 4 September 2014 (UTC)
* Survey positions of lanes/tents/DKs as early as possible before items arrive and mark out.--[[User:Sully|Sully]] ([[User talk:Sully|talk]]) 12:06, 1 September 2014 (UTC)
** This was planned but we were let down by the rather poor state of mobile GIS software.
*** there are multiple open source solutions for mapping, try https://umap.openstreetmap.fr/en/ or reach to out myself or #openstreetmap, there are many OSM'ers in the UK, [[User:Jburgess777|Jburgess777]] ([[User talk:Jburgess777|talk]]).
* Similar to this, measure for fence panels and drop stillage appropriately, to avoid the need to carry loads of them right up the camping field by hand
* Make it longer! There was loads of cool stuff I didn't have change to check out :( After all that work everyone does, it was a shame I couldn't experience it all! ([[User:Chewie|Chewie]]) ((I still say make it a week long ;) ([[User:BuildTheRobots|Fligg]]))
* Visibility of presentations in tents (brighter projectors/darker tents??) ([[User:StuartL]]) [+3]
* Use more plasma screens in stages instead of projectors ([[User:Markp]]). Or (better, as then the speaker can point to things) black fabric shades for the screen or marquee roof
** Next time dark tents. This was a total nightmare, sorry. --[[User:Jonty|Jonty]]
* washing points over drains/soakaway so the ground doesn't get muddy ([[User:Chewie|Chewie]]) [+4]
* Mark out/allocate spaces for villages who had pinpointed locations on maps ([[User:Markp]]) [+2]
** Space needed by villages was very hard to judge before they were set up, especially once non-village campers started on site ([[User:BuildTheRobots|Fligg]])
* Improved arrangements for washing and washing up (and handling the waste water from that) [+1]
* Provide sanitizer gel dispensers at water points and near loos [+2]
* Have the schedule linked off the EMF main page
** It was, but not on the First day...we forgot! See "Programme" at the top of the main website. --[[User:Jonty|Jonty]]
* Distribute and display paper schedules (even if their might be some last-minute changes) [+3]
** They were supposed to be available at the info tent, not sure what happened there. --[[User:Jonty|Jonty]]
** Or have small screens at the entrances to tents showing what's currently on & what's next.
*** We wanted to do this but simply ran out of time. --[[User:Jonty|Jonty]]
* Much more workshop activity (more hands-on electronics and physical making) [+6]
** Next time: Many more workshop tents. We totally underestimated availability and demand. [+1] --[[User:Jonty|Jonty]]
* Do have component vendors (maybe at their cost for marquee/power/space)
** This is very difficult without a clear list of what will sell, as CPC was arranged to appear but wanted advisement ([[User:Stanto]])
*** Would the (longer and with more repeats next time) workshop list work as advisement? Could workshop leaders be asked to provide suggestions for components that would be good to have available on site after their workshop?
* Pick a flatter site (for ease of disabled access)
* Ask speakers for bio's to include with their abstracts. Given them an abstract length up-front instead of editing it in an ad hoc way. Confirm acceptance to speakers and workshop organisers earlier.
** Do this after talks have been accepted. I didn't write my talk so didn't know details until I got the OK.
** The CFP was a bit of a nightmare this year, we'll certainly be doing this in 2016. --[[User:Jonty|Jonty]]
* Make and enforce a clear music curfew (say from midnight or 1am or 2am to 8 or 9am or 10am), to defend those sleeping from (eg) the technoevangelists and the drunk [+4]
** Perhaps try to select a site next time where we can make part of the site to be a quiet area, eg a part surrounded by trees for natural sound insulation. Then enforce a noise curfew there. I'm not keen on the idea of having a noise curfew covering the entire camp though. [[User:Alecjw]] [+1]
** Seconding enforced quiet/family camping area, but no overall noise curfew. It didn't take long to get away from the worst noise, and the end of the field by the kids' area was incredibly quiet (though strangely empty!!)
** Well, not quite - I need sleep to function, so camped in the quiet area - a nearby group thought 6:30am was the right time to turn on their music system. Not so good.
* Loos not so near food vendors (pong + visible urinals offputting) [+5]
* stronger enforcement/signage of quiet camping area [+5]
* an explicit invitation (with clear instructions) to report Code of Conduct violations in open ceremony, brochure, Twitter, etc. We had no direct reports to Team Comfort, but several anecdotal tweets after the event -- when it's much too late. [[User:Martind|Martind]] ([[User talk:Martind|talk]]) 20:58, 1 September 2014 (UTC) [+1]
* quieter, less-enclosed and more spacious bar (I suffer from social anxiety when I'm closed in with crowds, so I had a very sober emf!). [[User:Jane C|Jane C]]
** perhaps an outdoor seating area if a larger marquee is too costly.
*** There was an outdoor seating area set back to the right of the bar under a marquee, however the marquee vendor put it in the wrong place a day late, so wasn't as obvious, and didn't get hay bales until Saturday evening. --[[User:Jonty|Jonty]]
* use our collective knowledge of technology to sort accessibility issues
**ring-fence money for things like closed-loop in the stages early on.
**ask people about their access requirements much earlier on - e.g. when they buy a ticket - so that there is more time to meet these requirements (or reach a workable compromise)
**Build some kind of working system for preventing able-bodied people from using the disabled loos and showers (radar keys that only work when the loo is empty?) [[User:Jane C|Jane C]]
***Disagree with this as it reduces overall toilet/shower bandwidth, but would wholly agree with a solution whereby those who could only use limited facilities (disabled, families, etc) could queue-jump into those facilities the moment they because available. [[User:StuartL|StuartL]]
* Info desk didn't seem to have the details wrt. volunteers, so when I volunteered I was sent out and found I wasn't needed. Suggest splitting the job - having a volunteer team leader (or several, in shifts) whose job it is to know who is where and also to make sure nobody gets stuck on a gate for 12 hours (eg. rotating people to more interesting places every couple of hours). ([[User:TonyHoyle|TonyHoyle]])
** There was a separate volunteer manager in the same tent, this should not have happened. Sorry about that. --[[User:Jonty|Jonty]]
* Also similar to this, a register of 'on call' people - excess volunteers who can deal with sudden demands for people (esp. in the case of fire I can imagine this would be extremely useful - you'd potentially need to cordon off a largish area very quickly, and that takes people. More mundane reasons would be a talk/workshop accumulating a large queue that needs managing). ([[User:TonyHoyle|TonyHoyle]])
** There were shifts for people to be "on call" but they weren't obvious. We'll make sure this is easier. --[[User:Jonty|Jonty]]
** with earlier (/working) workshop sign-up, I would have put myself on call - instead I was waiting to hear what workshops would be available when.
* add GPS or other location aware technology like BTLE/iBeacon to the badges for automatic now/next notifications [[User:Jburgess777|Jburgess777]] ([[User talk:Jburgess777|talk]]).
* Locking wristbands that don't get any tighter.
* Having a tent for Badge Operations would be pretty handy - similar size to the workshop tent, that could be set up as a production line / fixing area if needed. If not (hopefully) it would be a rolling workshop area for people to work of hacking their badges, writing new software, adding hardware etc.

==Suggestions==
* Ask for an optional email address for each ticket to go on your announce only mailing list. Only the person that bought the tickets got your emails and they were slow to forward them on meaning most messages were received too late.
* Ask for age of children when booking, to give better planning stats for workshops etc. [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]])
* A talk (a bit like lightning talks) where people are given 5-10 minutes to share what they did with the previous event's badge. (If someone sends me the competition winners/runners up, I'll co-ordinate it) [[User:MatS|MatS]] ([[User talk:MatS|talk]]) 07:54, 1 September 2014 (UTC)
* Pre-paid accounts for spending money on food/beer/whatever to negate need for cash ([[User:Markp]])
* Have a fleet of communal wheel-barrows to help people transport their stuff from car to campsite [+2]
** Stepney City Farm have a fleet of broken wheelbarrows – fix ’em, use ’em, everybody wins! ([[User:Andylolz]])
** Or purchase some sack trolleys
* contactless payment gear for food, beer, workshops
** We had contactless payment for beer! (And we also offered cashback.) We should have messaged that better. Contactless payment for other things is complex, as we don't really control them. [[User:Russ|Russ]] ([[User talk:Russ|talk]])
* forewarn food vendors to expect all-day demand, not just mealtimes, so they can stock and staff appropriately [+1]
** food vendors were pretty much *events* caterers, used to feeding people snacks/lunch, we need *festival* caterers who are used to feeding people who are staying for a number of days. thethalicafe.co.uk? bedouin tent (shambala)? +late night options [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]])
*** It's really difficult to get caterers. Now we're a bit better known it's getting easier. [[User:Russ|Russ]] ([[User talk:Russ|talk]])
* pinboard (offline) notice board everyone can contribute to (lost property, mini event notices eg rocket launches, would like to meet.., etc) [+1]
** This was supposed to be next to the info tent, but got lost in the last-minute panic. --[[User:Jonty|Jonty]]
* Ask people who want to give workshops if they'd be happy to give more than one session - the blacksmiths' output was extreme, but even giving two or three sessions would greatly increase the % of attendees who could sign up.
** Many workshop submissions specified that already, the issue was actually with finding space for them as we only had one workshop tent. We'll have many next time! --[[User:Jonty|Jonty]]
* Sign-ups some kind of "express preference" systems, so most people (including those who don't check email regularly) can get at least one of their top choices, rather than first-come-first-served.
** Online workshop sign-up is a priority for next year. --[[User:Jonty|Jonty]]
* Board games tent in the evenings [+4]
* Poker tent
* Be less ambitious with badge functionality [+3]
** And provide full documentation of features/functionality [+1]
** And sample code for each function
** Perhaps a back-to-basics through-hole design that comes with soldering iron, solder and instructions?
** I think we might build on this design for the next event. [[User:Russ|Russ]] ([[User talk:Russ|talk]])
** Software that doesn't involve an OS (but rather more conventional Arduinoery) might be more easily hackable by others during/after the event? Especially given libraries for people to do amusing things with the peer-to-peer radio...
*** That is actually much harder to build anything decent with. The badges are normal arduinos and all the libraries are available, you don't have to use the EMF OS, it was designed for people to write normal Arduino code for! --[[User:Jonty|Jonty]]
* EMF is unlike other festivals - for a large number of people, carrying kit to/from car is impractical and security walking every car through site is time-consuming and volunteer-intensive (not to mention the fact that cars driving off site weren't walked off). Suggest that the parking area is directly next to and easily accessible from the camping area (e.g. just separated by hay bales to stop cars driving on to the camping area).
** As a village/car user you could generally provide your own security person walking in front of the car. This works 2 fold: 1) security doesn't need to walk for you 2) less waiting time for you since you already provide someone to walk.
** The plan for this was to allow people to drive onto site on the Thursday evening. It wasn't very well communicated and we had a *very* tight setup schedule so we needed to reduce this as much as possible. This is ultimately an issue with our setup schedule
** It wouldn't work on this site, but for some locations it might be possible to have a drop-off point close to camping (with a limited number of cars at one time), better idea than having cars (ignition source) close to tents. Some people were taking the mickey on Monday morning, many people driving onto site that could have carried things instead tying up volunteer resources to escort them.
* Provide job descriptions for traffic control, parking and entrance gatehouse. Instructions were handed from volunteer to volunteer by word of mouth and whilst common sense prevailed, it would have been useful to have instructions as to what to do under certain circumstances and a list of answers to FAQs, e.g.:
** What if somebody didn't have a parking ticket and wanted to park?
** What if somebody was just dropping off - where should they do this?
** What times were shuttle buses running?
** What times the gates were open/closed?
** Have a priority queue for people with machine readable tickets (ie paper!)
** Volunteer training was lost by the wayside for some roles, we'll fix that. --[[User:Jonty|Jonty]]
* Add suggested age ranges for all workshops, some of the "adult" workshops were also very suitable for children (e.g. electronic fashion, solar pv) or could have been run once in main workshop once in kid's area [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]])
** This was supposed to happen but got missed off by accident. Apologies. --[[User:Jonty|Jonty]]
* Bolt the fence from the right side, I know we didn't even want it at all but local authorities can be fussy, I've been at a festival before who did the same and they made them fix it during the event.. [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]])
* Want the good coffee on Monday morning, especially for drivers :) Maybe in the car park to help persuade people off site. [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]])
* Would be good to have eggs, fresh milk, bacon at the shop (there was a comment like "we don't have eggs, they break too easily" - so charge extra to cover this, though it's probably not as bad as you think..) [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]])
** The shop was being run by an external team, we didn't control what they stocked. --[[User:Jonty|Jonty]]
** Morrisons did a tent with Milk, Bread, Burgers, BBQs etc @ http://www.festivalofcycling.org/expo/name/morrisons/, might be worth asking them? [[User:Jburgess777|Jburgess777]] ([[User talk:Jburgess777|talk]])
* Start ticket sales (a couple of months?) earlier, maybe with a slightly bigger difference between early ticket prices and full price to encourage attendees to get in early (which in turn would improve cashflow) [[User:Sthen|Sthen]] ([[User talk:Sthen|talk]]) [+1]
* Start ticket sales *now* whilst you have all the publicity or at least have a page up where people can register to be emailed once the next event has tickets for sale. That way you get your current mailing list + everyone else who has only just learned about it as your audience. [[User:Alteralias|Alteralias]]
** Until we have a date/venue that is not a great plan, as we'd end up with a lot of refunds. --[[User:Jonty|Jonty]]
*** Although a massive mailing list/Twitter/Facebook push might be a good idea so people are ready to hear that tickets are on sale.
* Cluster the talks into related-topic sessions
** This is very difficult due to availability of speakers, and we'd rather people with very specific interests had talks to go to all weekend rather than just on one afternoon. --[[User:Jonty|Jonty]]
*** More Q&A sessions like the security one, getting multiple speakers on a topic together for questions might be a better idea.
* Volunteering stuff ([[User:HughePaul|HughePaul]])
** Whiteboard in info tent for current issues / tasks, handover
** Have info tent next to security tent so both can be available at the same time and all the time.
*** The info tent and the gatehouse/security tent could be two sides of the same erection.
** have predefined named people in shifts for head of / coordination of volunteering (could also double as an info/security tent staff)
** maybe stream some talks in info tent so they don't feel like they are missing things
** more formal defined (and communicated) lost-property form and procedure
** define volunteer job roles to make handovers easier and so we know what we are meant to be doing
* Have dedicated blog / tweet / website updating person/team
* big screen with latest official event update tweets
** Very expensive to hire. --[[User:Jonty|Jonty]]
*** small screen with latest updates? even a 20 inch cycling through the latest tweets in a big font?
* info about getting DISconnected from DKs and leaving the site in vehicles
** This was badly handled, and we only realised when it was too late. --[[User:Jonty|Jonty]]
* perhaps worth putting up a summary of the overall budget after the event, so people can see what's costly?
* website needs to be designed around the info people need at the time
** days before the event front page should have location, travel, packing, instructions such as workshop booking, village booking, volunteering
** during it should have info about DKs, current day schedule (possibly whats on and next), links to streams, power and internet usage :), lost property instructions, latest updates/tweets
** after have thanks, photos, tilda sales, etc
* Some kind of welcome tent / meet-a-stranger area / badges saying "talk to me" (and not reliant on tech that might not be available/working till later on) / person-bingo-style game - deliberately flagged up as a way for people to meet new people, including if they came on their own / hadn't been to anything like this before. For many the whole event will be like that anyway - it wouldn't hurt to help out those shyer / newer / more awkward. Maybe there could be a welcoming/newbies/friendliness team prior to next time who came up with stuff to try of this nature (all utterly optional, of course)?
* More flying cars (requested by someone leaving site when asked what they thought was lacking)
* Dual controls quad-copter training. So someone can learn to fly and know the "instructer" can take over if it gets out of hand.

Villages:Hax0rz of the Roses

2014-09-05T10:46:54Z

Thinkl33t: /* Post event feedback */

{{Village
|Picture=Village Hax0rz of the roses..gif
|Name=Hax0rz of the roses.
|Description=This is a joint venture between Leeds, Manchester, York and Lancaster Hackspaces.
|Contact=thinkl33t
|Location=51.968496, -0.792503

}}

==Villagers==
{{inhabitant}}

==Robots==
* RoboButler 3000

==Tools==
* Wood Lathe! Myford ML8 under supervision of [[User:idnorton|Ian Norton]] or [[User:clj|Claire Jackson]]. We'll be turning things, people can try their hand if they want.

== Post event feedback ==

Add your feedback here on village stuffs.

=== Positives ===

* Great to be in the same area for camping with you all [[User:Idnorton|Idnorton]] ([[User talk:Idnorton|talk]]) 09:15, 5 September 2014 (UTC)

* BBQ was epic! More fire things! [[User:Idnorton|Idnorton]] ([[User talk:Idnorton|talk]]) 09:15, 5 September 2014 (UTC)
* Food was awesome (it appears you can't go wrong as long as you have enough bacon and haloumi!) --[[User:Nav|Nav]] ([[User talk:Nav|talk]]) 10:04, 5 September 2014 (UTC)

=== Negatives ===

If you're adding negative feedback please remember to be constructive and add a suggestion on how things may have been done differently.

* Nail the village tent to the floor more securely first time ;) [[User:Idnorton|Idnorton]] ([[User talk:Idnorton|talk]]) 09:15, 5 September 2014 (UTC)

=== Ideas for next time ===

* Need someone who is going to be at the village most of the time to act as coordinator, make sure food is started on time etc. [[User:Thinkl33t|Thinkl33t]] ([[User talk:Thinkl33t|talk]]) 09:19, 5 September 2014 (UTC)
* Need a sign of some kind, I'm not sure people knew who we were or if they were directed to us how to find us [[User:Idnorton|Idnorton]] ([[User talk:Idnorton|talk]]) 09:15, 5 September 2014 (UTC)
** I have a source for reasonably priced banners (from small to the size of the side of a big tent) --[[User:Nav|Nav]] ([[User talk:Nav|talk]]) 10:10, 5 September 2014 (UTC)
* Separate tent for shiny from kitchen / storage (like hsnotts had) [[User:Thinkl33t|Thinkl33t]] ([[User talk:Thinkl33t|talk]]) 09:21, 5 September 2014 (UTC)
** I may be able to borrow a big green 24'x12' tent - obviously transporting that requires some planning --[[User:Nav|Nav]] ([[User talk:Nav|talk]]) 10:10, 5 September 2014 (UTC)
** TBH I'd rather rent the village tent(s) next time. The garage was a good idea from a price POV but was a pain to move around, a bit too small, and i CBA putting it up / taking it down again [[User:Thinkl33t|Thinkl33t]] ([[User talk:Thinkl33t|talk]]) 10:46, 5 September 2014 (UTC)
* Need to bring the coffee machine again next time [[User:Idnorton|Idnorton]] ([[User talk:Idnorton|talk]]) 09:15, 5 September 2014 (UTC)
* FLAGS / hackspace banners [[User:Thinkl33t|Thinkl33t]] ([[User talk:Thinkl33t|talk]]) 09:22, 5 September 2014 (UTC)
** We have some Leeds hackspace banners - they're just bulks and weren't sufficiently high up my list of things to bring. --[[User:Nav|Nav]] ([[User talk:Nav|talk]]) 10:10, 5 September 2014 (UTC)
* Getting connected to the wifi was a PITA (so much so that I didn't bother attempting to get my raspberry pi radar connected). Probably worth coordinating any "connected" projects and maybe going for wired through our own switch? --[[User:Nav|Nav]] ([[User talk:Nav|talk]]) 10:07, 5 September 2014 (UTC)

Villages:Hax0rz of the Roses

2014-09-05T09:22:46Z

Thinkl33t: /* Post event feedback */

Villages:Hax0rz of the Roses

2014-09-05T09:21:15Z

Thinkl33t: /* Post event feedback */

Villages:Hax0rz of the Roses

2014-09-05T09:20:18Z

Thinkl33t:

Villages:Hax0rz of the Roses

2014-09-05T09:19:49Z

Thinkl33t: /* Post event feedback */

Villages:Hax0rz of the Roses

2014-09-05T09:13:43Z

Thinkl33t:

TiLDA MKe

2014-09-02T16:56:45Z

Thinkl33t:

The TiLDA MKe project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Dpslwk|'RepRap' Matt]] and [[User:thinkl33t|Bob]]
[[File:Badge_Front.png|right|thumb|Front]]

[http://en.wikipedia.org/wiki/E_(mathematical_constant) Why MKe?]

=Aim=
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.

==Battery Warning==
'''Always make sure you plug your battery in the right way round!''' If you dont, 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.

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.

'''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.

==Features and Functions==
[[File:Badge_Back.png|right|thumb|Back]]
* 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
* Snake
* Tetris
* Weather Forecast
* Schedule
* Can receive notifications about upcoming schedule items you're interested in. Visit schedule.emf.camp to set up your account.

'''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!

== How to get going ==
=== Set up your environment ===
* Plug your badge into your computer via USB
* Download Arduino IDE 1.5.7 from http://arduino.cc/en/main/software#toc3
* “git clone” or download TiLDA source code from https://github.com/emfcamp/Mk2-Firmware
* Start the Arduino IDE.
* 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
* Restart the Arduino IDE
* Open sketch “EMF2014”
* Set Tools | Board to MKe v0.333 (RTOS Core)
* Set Tools | Port to correct port (you might have to research this - some operating systems like Windows require you to install drivers or become member of a certain group)
** On Macos this is will start /dev/tty.usbmodem with 4 digits, and change for each port
** On Linux this is usually /dev/ttyACM0 but may be a higher number if you have other USB Serial devices
* Hit the upload button
* Wait
* Woohoo - You just successfully uploaded code to your badge

=== Your first “Hello world” App ===
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!

=== Why are things so different from standard arduino code? ===
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).

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.

Have a look at the “Documentation” section in this document for a full list of API functions. You will avoid a lot of headache if you stick to those.
=== How to use the badge with pure Arduino code ===
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.
=== Debugging and Gotchas ===
* The USB serial is set up to 115220 baud. There are lots of terminals that can connect to them
* If you can’t revive a badge you can short the two erase pins and press the reset button while holding it down.
* Avoid busy waiting, use FreeRTOS queues and Tilda::delay() instead
* 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()
=== Code structure ===
* 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)
* Everything needs to be in the main EMF2014 folder. Subfolders are not allowed. This is an Arduino IDE restriction :(
=== Radio infrastructure ===
The radio infrastructure is distributed between DKs. Every “gateway” has a raspberry pi with two ciseco usb radios. We never had the change to actually try it with that many badges in the same spot, so please don’t expect it to work perfectly.
=== Contribute ===
Send us pull request via github - We’ll do our best to review and merge the good ones during EMF so others can use them.

=Hardware=

The following hardware has been included on the badge.

* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge
** 32bit ARM Cortex M3 * 84MHz
** 512KBytes Flash RAM
** 96KBytes of SRAM
* A 128x64 pixel monochrome LCD display
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]
** 868Mhz RF Transceiver
** Simple UART interface
** Low power sleep mode
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro
** I2C interface
** 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
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection
* PMIC & LiPo
* Joystick
* Buttons
* RGB LED's
* IR
* Arduino Headers
* Pads for wearable tech

= Firmware Documentation =
== Debugging ==
===Tilda::log(String text)===

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.
== Buttons ==
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:

Example: A simple app displaying the button code
void ButtonApp::task() {
ButtonSubscription allButtons = Tilda::createButtonSubscription(LIGHT | A | B | UP | DOWN | LEFT | RIGHT | CENTER);

while(true) {
Button button = allButtons.waitForPress(1000);
if (button == A) {
debug::log(“You pressed button A”);
} else if (button == LEFT) {
debug::log(“You pressed LEFT”);
} else if (button == NONE) {
debug::log(“No button has been pressed in 1000ms”);
}
}
}

===ButtonSubscription Tilda::createButtonSubscription(<buttons>)===

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).

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.

===Button ButtonSubscription::waitForPress(TimeInTicks timeout)===

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.

===ButtonSubscription::waitForPress()===

The same as above, but without the timeout.

===ButtonSubscription::clear()===

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.

==LEDs==
===Tilda::setLedColor(Led led, Color color);===
===Tilde::setLedColor(Color color);===

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.

Example: A simple color-changing task
void ColorfulTask::task() {
while(true) {
Tilda::setLedColor(LED1, {255, 0, 0}); // Red
Tilda::setLedColor(LED2, {0, 255, 0}); // Green
Tilda::delay(300);
Tilda::setLedColor(LED1, {0, 255, 0}); // Green
Tilda::setLedColor(LED2, {0, 0, 255}); // Blue
Tilda::delay(300);
Tilda::setLedColor(LED1, {0, 0, 255}); // Blue
Tilda::setLedColor(LED2, {255, 0, 0}); // Red
Tilda::delay(300);
}
}

==Display==

The Display Library is based on GLCDv3 (http://playground.arduino.cc/Code/GLCDks0108) 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.)

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.

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.

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.

== Sound ==
There's a piezo on the board, but we haven't added code for it to the current firmware. Pull requests are very welcome!

== IMU ==
=== Tilda::getOrientation ===
returns " ORIENTATION_HELD", "ORIENTATION_RIGHT" (joystick to the right of the screen), "ORIENTATION_HUNG" or "ORIENTATION_LEFT"

== Flash Storage ==
We have 2mb of flash storage, but we're not using it in the main firmware - Please get this working!
== Data: Schedule ==
===Tilda::getDataStore().getSchedule(day, location) ===
== Date: Weather Forecast ==
===Tilda::getDataStore().getWeatherForecast()===
== Radio ==
There's no way of sending messages in the current version of the firmware, sorry :(

== Time ==

=== Tilda::delay(uint16_t delayInMs) ===

Works like Arduino’s delay(), but is FreeRTOS-safe. It’s safe to use this function before FreeRTOS has started.

=== tilda::getClock() ===

Returns an instance of https://github.com/MarkusLange/Arduino-Due-RTC-Library/blob/master/rtc_clock.h

==Settings==
===uint16_t tilda::getBadgeId()===

==2.12. Battery==
===float TiLDA::getBatteryVoltage()===
Returns the current voltage as a float

===uint8_t TiLDA::getBatteryPercent()===
Returns the current voltage as a percentage

===uint8_t TiLDA::getChargeState()===
Returns the charge state

0 Charging
1 Not Charging

=Hacking=
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] 
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] 
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/ 
or 
Alternative option is to set the Arduino 1.5.7 sketchbook folder to the Mk2-Firmware directory. 

Start the Arduino IDE and your will be able to select TiLDA MKe v0.333 for the Tools->Board menu

Draft 3d print-able and laser-able case files [http://www.thingiverse.com/thing:436815 here]



= Source =

All the source code and designs are on openly available on Github:

* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant parts datasheets
* [https://github.com/emfcamp/Mk2-Firmware Firmware] - source code for the badge software
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network

[[Category: Badges]]

Feedback

2014-09-01T20:05:45Z

Thinkl33t: /* Stuff that could be improved */

TiLDA MKe

2014-09-01T17:50:18Z

Thinkl33t:

The TiLDA MKe project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Dpslwk|'RepRap' Matt]] and [[User:thinkl33t|Bob]]
[[File:Badge_Front.png|right|thumb|Front]]

[http://en.wikipedia.org/wiki/E_(mathematical_constant) Why MKe?]

=Aim=
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.

==Features and Functions==
[[File:Badge_Back.png|right|thumb|Back]]
* 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
* Snake
* Tetris
* Weather Forecast
* Schedule
* Can receive notifications about upcoming schedule items you're interested in. Visit schedule.emf.camp to set up your account.

'''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!

== How to get going ==
=== Set up your environment ===
* Plug your badge into your computer via USB
* Download Arduino IDE 1.5.7 from http://arduino.cc/en/main/software#toc3
* “git clone” or download TiLDA source code from https://github.com/emfcamp/Mk2-Firmware
* Start the Arduino IDE.
* 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
* Restart the Arduino IDE
* Open sketch “EMF2014”
* Set Tools | Board to MKe v0.333 (RTOS Core)
* Set Tools | Port to correct port (you might have to research this - some operating systems like Windows require you to install drivers or become member of a certain group)
** On Macos this is will start /dev/tty.usbmodem with 4 digits, and change for each port
** On Linux this is usually /dev/ttyACM0 but may be a higher number if you have other USB Serial devices
* Hit the upload button
* Wait
* Woohoo - You just successfully uploaded code to your badge
* For now, the code waits for a key on the usbserial debug before doing anything, open the serial monitor in Arduino, set the line endings to ‘Newline’ and press enter.

=== Your first “Hello world” App ===
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!

=== Why are things so different from standard arduino code? ===
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).

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.

Have a look at the “Documentation” section in this document for a full list of API functions. You will avoid a lot of headache if you stick to those.
=== How to use the badge with pure Arduino code ===
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.
=== Debugging and Gotchas ===
* The USB serial is set up to 115220 baud. There are lots of terminals that can connect to them
* If you can’t revive a badge you can short the two erase pins and press the reset button while holding it down.
* Avoid busy waiting, use FreeRTOS queues and Tilda::delay() instead
* 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()
=== Code structure ===
* 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)
* Everything needs to be in the main EMF2014 folder. Subfolders are not allowed. This is an Arduino IDE restriction :(
=== Radio infrastructure ===
The radio infrastructure is distributed between DKs. Every “gateway” has a raspberry pi with two ciseco usb radios. We never had the change to actually try it with that many badges in the same spot, so please don’t expect it to work perfectly.
=== Contribute ===
Send us pull request via github - We’ll do our best to review and merge the good ones during EMF so others can use them.

=Hardware=

The following hardware has been included on the badge.

* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge
** 32bit ARM Cortex M3 * 84MHz
** 512KBytes Flash RAM
** 96KBytes of SRAM
* A 128x64 pixel monochrome LCD display
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]
** 868Mhz RF Transceiver
** Simple UART interface
** Low power sleep mode
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro
** I2C interface
** 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
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection
* PMIC & LiPo
* Joystick
* Buttons
* RGB LED's
* IR
* Arduino Headers
* Pads for wearable tech

= Firmware Documentation =
== Debugging ==
===Tilda::log(String text)===

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.
== Buttons ==
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:

Example: A simple app displaying the button code
void ButtonApp::task() {
ButtonSubscription allButtons = Tilda::createButtonSubscription(LIGHT | A | B | UP | DOWN | LEFT | RIGHT | CENTER);

while(true) {
Button button = allButtons.waitForPress(1000);
if (button == A) {
debug::log(“You pressed button A”);
} else if (button == LEFT) {
debug::log(“You pressed LEFT”);
} else if (button == NONE) {
debug::log(“No button has been pressed in 1000ms”);
}
}
}

===ButtonSubscription Tilda::createButtonSubscription(<buttons>)===

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).

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.

===Button ButtonSubscription::waitForPress(TimeInTicks timeout)===

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.

===ButtonSubscription::waitForPress()===

The same as above, but without the timeout.

===ButtonSubscription::clear()===

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.

==LEDs==
===Tilda::setLedColor(Led led, Color color);===
===Tilde::setLedColor(Color color);===

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.

Example: A simple color-changing task
void ColorfulTask::task() {
while(true) {
Tilda::setLedColor(LED1, {255, 0, 0}); // Red
Tilda::setLedColor(LED2, {0, 255, 0}); // Green
Tilda::delay(300);
Tilda::setLedColor(LED1, {0, 255, 0}); // Green
Tilda::setLedColor(LED2, {0, 0, 255}); // Blue
Tilda::delay(300);
Tilda::setLedColor(LED1, {0, 0, 255}); // Blue
Tilda::setLedColor(LED2, {255, 0, 0}); // Red
Tilda::delay(300);
}
}

==Display==

The Display Library is based on GLCDv3 (http://playground.arduino.cc/Code/GLCDks0108) 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.)

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.

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.

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.

== Sound ==
There's a piezo on the board, but we haven't added code for it to the current firmware. Pull requests are very welcome!

== IMU ==
=== Tilda::getOrientation ===
returns " ORIENTATION_HELD", "ORIENTATION_RIGHT" (joystick to the right of the screen), "ORIENTATION_HUNG" or "ORIENTATION_LEFT"

= Flash Storage ==
We have 2mb of flash storage, but we're not using it in the main firmware - Please get this working!
== Data: Schedule ==
===Tilda::getDataStore().getSchedule(day, location) ===
== Date: Weather Forecast ==
===Tilda::getDataStore().getWeatherForecast()===
== Radio ==
There's no way of sending messages in the current version of the firmware, sorry :(

== Time ==

=== Tilda::delay(uint16_t delayInMs) ===

Works like Arduino’s delay(), but is FreeRTOS-safe. It’s safe to use this function before FreeRTOS has started.

=== tilda::getClock() ===

Returns an instance of https://github.com/MarkusLange/Arduino-Due-RTC-Library/blob/master/rtc_clock.h

==Settings==
===uint16_t tilda::getBadgeId()===

==2.12. Battery==
===float TiLDA::getBatteryVoltage()===
Returns the current voltage as a float

===uint8_t TiLDA::getBatteryPercent()===
Returns the current voltage as a percentage

===uint8_t TiLDA::getChargeState()===
Returns the charge state

0 Charging
1 Not Charging

=Hacking=
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] 
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] 
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/ 
or 
Alternative option is to set the Arduino 1.5.7 sketchbook folder to the Mk2-Firmware directory. 

Start the Arduino IDE and your will be able to select TiLDA MKe v0.333 for the Tools->Board menu

Draft 3d print-able and laser-able case files [http://www.thingiverse.com/thing:436815 here]



= Source =

All the source code and designs are on openly available on Github:

* [https://github.com/emfcamp/Mk2-Hardware Hardware] - the full board design
* [https://github.com/emfcamp/Mk2-Documentation Documentation] - a dump of relevant parts datasheets
* [https://github.com/emfcamp/Mk2-Firmware Firmware] - source code for the badge software
* [https://github.com/emfcamp/Mk2-Software Software] - server-side software for the network

[[Category: Badges]]

User:Thinkl33t

2014-07-28T11:39:11Z

Thinkl33t:

{{Attendee
|name=Bob Clough
|village=Hax0rz of the Roses
|email=bob@hacman.org.uk
|Arrival=2014/08/27 12:00
|Departure=2014/09/01 12:00
|IRC=parag0n
|teams=BADGE
}}

User:Thinkl33t

2014-07-28T11:38:39Z

Thinkl33t: Created page with "{{Attendee |name=Bob Clough |village=Hax0rz of the roses |email=bob@hacman.org.uk |Arrival=2014/08/27 12:00 |Departure=2014/09/01 12:00 |IRC=parag0n |teams=BADGE }}"

{{Attendee
|name=Bob Clough
|village=Hax0rz of the roses
|email=bob@hacman.org.uk
|Arrival=2014/08/27 12:00
|Departure=2014/09/01 12:00
|IRC=parag0n
|teams=BADGE
}}

Villages:Hax0rz of the Roses

2014-07-28T11:25:47Z

Thinkl33t:

{{Village
|Name=Hax0rz of the roses.
|Description=This is a joint venture between Leeds, Manchester, York and Lancaster Hackspaces.
|Contact=thinkl33t
}}

==Villagers==
{{inhabitant}}

==Robots==
* RoboButler 3000
* Mendel90

==Tools==
* Wood Lathe!

Villages:Hax0rz of the Roses

2014-07-28T11:21:40Z

Thinkl33t:

{{Village
|Name=Hax0rz of the roses.
|Description=This is a joint venture between Leeds, Manchester, York and Lancaster Hackspaces.
|Contact=thinkl33t
}}

==Villagers==
{inhabitants}

==Robots==
* RoboButler 3000
* Mendel90

==Tools==
* Wood Lathe!

Villages:Hax0rz of the Roses

2014-07-28T11:19:39Z

Thinkl33t:

{{Village
|Name=Hax0rz of the roses.
|Description=This is a joint venture between Leeds, Manchester, York and Lancaster Hackspaces.
|Contact=thinkl33t
}}

==Villagers==
* [[User:Thinkl33t|Thinkl33t]] ([[User talk:Thinkl33t|talk]]) 11:19, 28 July 2014 (UTC)

==Robots==
* RoboButler 3000
* Mendel90

==Tools==
* Wood Lathe!

Villages:Hax0rz of the Roses

2014-07-28T11:19:05Z

Thinkl33t:

Volunteers

2014-07-09T11:27:11Z

Thinkl33t:

{{link-banner}}

Don't put your name here unless you really mean it and don't edit other people's words without their permission.

This is a page in addition to signing up to volunteer as part of the ticket buying process. Please make sure that you have bought a ticket and signed up using that method as the emails gathered there will be how we contact everyone.

NOTE: unless you're volunteering as a first aider (and have confirmed ahead of time with the first aid team) you must buy a ticket.

{| class="wikitable"

|-
|'''Wiki user'''||'''[[Volunteers/DrivingLicenceCategories|Driving licence categories]] (if willing to drive)'''||'''I'd like to'''||'''I'm willing to'''


|-
|
[[User:ItsChip|Chip]]
|
Nope
|
* Help deploy wired/wireless network
* Help tent construction/camp
* Build and teardown
* Systems Admin
* Wiki stuff
* Lighting/Sound Engineer
* Social Media/Video/Pictures etc.
|
* Try me
* Note: ticket not bought yet.. working on it
* Email on Wiki page



|-
|
[[User:NAB|NAB]]
|
B, BE, C1, C1E, D1, D1E (clean)
|

* Take ownership of caravan/motorhome/trailer-tent section of site (selection of initial location, mark-up, marshalling, liaison re power/potable water/greywater/blackwater etc.)
* Create "I'm shy/alone, please talk to me" type badges
* Offer telephone conference room(s) with SIP, geo and freephone access
* Offer on-site telecoms
|
* Drive minibuses
* Run shop (basic staples)
* Keep loos stocked with toilet roll
* Pretty much anything else



|-
|
[[User:lohapuk|lohapuk]]
|
A,B, B1 (clean)
|
* Help Deploy wireless / wired network (Certs CCNP,RHCE)
* Help Build tents / camp
|
* Anything to help out



|-
|
[[User:Sling|Sling]]
|
B (but Dutch)
|
* Help with info/noc helpdesk
* Buildup and teardown
* Sysadmin
* Wiki maintaining & structuring
|
* Parking/Security
* Barshifts
* Help with cooking
* Probably more stuff I'm forgetting.



|-
|
[[User:Dpslwk|'RepRap' Matt]]
|
Nope
|
* Badge Team, already working on it [[TiLDA 2]]
* Buildup and teardown (thought mostly i expect to be sorting badge related stuff, like deploying the R-PI radio network)
|
* Anything in between Badge hacking and running the Workshop area



|-
|
[[User:User_4574|Nathan Lasseter]]
|
B,B1,f,k,p (clean)
|
* Help with the NOC team (LAIT1 Accredited)
* Lay/fly cabling/fibre
* Buildup and teardown
|
* Do most things once



|-
|
[[User:danrl|danrl]]
|
B, C1, C
|
* deploy wireless / wired network
* build-up and tear-down
* IPv6 / NAT64
* Colocation
* Making teh NOC tent a fancy place to chill^M^Mwork hard
|
* rescue golf carts from ditches



|-
|
[[User:markp|markp]]
|
B, B1, f, k. p (clean)
|
* network / power cabling & termination
* build-up and tear-down
* transport (have estate car and trailer)
* lighting
* have access to mifare card/badge printing facilities
* assist with camping facilities
|
* help out wherever I'm needed
(can only be on-site Friday to Monday, but happy to help weekend before)



|-
|
[[User:bigcw|bigcw]]
|
B, B+E
|
* Get involved. Will help with anything. Very good at 'getting things done'.
|
* Connectivity (15 years experience in ISP industry)
* Power (former event lighting engineer)
* Transport (have Range Rover and trailer license)
* Anything else (lots of local knowledge, contacts, etc)



|-
|
[[User:simonvc|Simon Vans-Colina]]
|
A,B,BE,B2,f,k,p
|
* Anything really
|
* Dont have a car, but can drive one if needed.



|-
|
[[User:Si1entDave|Dave Wilson]]
|
B, B1
|
* Most things involving cables - I am also known as SparkyDave, head of site electrics for Profound Decisions LRP events
* My attendance will be contingent on my employer, Warwicknet, providing the connectivity - in which case they will give me the time off to attend :-)
* I also have a Defender which I am rather good at using to position trailers/generators/etc on fields
|
* I'll muck in with most things, but definitely specialise in electrics and networking.



|-
|
[[User:gmc|gmc]]
|
B, AM
|
* drive a manitou
* man the HQ
* do radio
* organize stuff
* A/V related stuff
* all of the above preferably in a supervisory / gophery kinda way
* build-up / tear-down
|
* pick up trash
* herald a lecture venue
* driving
* bar-shifts
* ...



|-
|
[[User:sleepycal|sleepycal]]
|
B,B1 (clean)
|
* Anything network related (NOC support, cabling, maintenance etc)
* Any aspect of site build-up/tear-down
* Prep work / planning
* Anything workshop related
* On-site help/emergency team (someone you can flag down any time/place if you need help)
|
* Anything to help out



|-
|
[[User:Big Kate|Big Kate]]
|
B, BE, C1, C1E, D1, D1E, Blue Badge
|
* Heralding/Speaker desk - On the day introduction to events etc
* Green Room Team:Content - Building a green room
* Making sure presenters have met there Heralds, hand off process etc
* Team:Rehash - Assuming its the same crew from OHM
* Queering the community i.e. LGBT etc community aspects
* Disability Access issues
|
* Build up and tear down
* (as best I can - given my disabilities)
* Drive Vehicles - upto 7.5 Tonnes
* (I have a disabled/ blue badge)
* (easier parking/ pickup/ drop off)
* Logistics and Operations
* Usual gophering type stuff



|-
|
[[User:drrk|Kimball]]
|
None
|
* <s>Buildup</s>Due to change of job I can't be there before the Friday now :(
* Badge Firmware
* Sysadmin
* AV/Radio
|
* Anything else


|-
|
[[User:Critical|Critical]]
|
B, BE, C1, C1E, D1, D1E
|
* Build up and tear down
* Anything Network / IT / AV related
* Meet / greet / help
|
* Whatever is needed


|-
|
[[User:chris_martin|chris_martin]]
|
0
|
* Build up and tear down
* FULLY SIA LICENSED >>> marshaling
* bar-shifts
|
* Whatever is needed


|-
|
[[User:lozarythmic|lozarythmic]]
|
AM, A, B, B1 (clean)
|
* Networking
* Fire Marshall
* Bar Work
|
* Whatever is needed


|-
|
[[User:JimM|Jim MacArthur]]
|
|
* Build up/tear down
* Bar Work
|
* Whatever is needed


|-
|
[[User:RattyMaHatty|Ratty]]
|
B, BE, C1, C1E, D1, D1E, fklnp (a few points)
|
* M$ Windows fixing
* PC/Server hardware engineer
* Networking
* Bar Work
* Driving
|
* Whatever is needed


|-
|
[[User:ens|ens]]
|
None - but willing ;)
|
* Media/Editing stuff (Can provide lend of broadcast-standard video gear if needed, aswell as editing gear)
* You need an electro-hacker-trippy-ambient DJ? hook me up.
* Build-up or Tear-down.
* Heralding.
* Helping those who are giving talks to get sorted.
|
* Help sourcing physical resources for the site.


|-
|
[[User:pioneer|pioneer]]
|
B,B+E,kfp (clean)
|
* Help Deploy wireless / wired network - Anything network related.. I have my own RJ45 Cripmer :p
* Help with VoIP system if deployed
* Sysadmin, NOC Help, Server admin
* Power, Lighting, AV - Part time sound engineer with access to PA systems, AV gear, projectors etc
* Build-up and tear-down
|
* I can loan a PA System
* can also loan networking/wifi + server equipment if needed, just ask and I might have it.
* I'll Help with most things, but I specialise in electrics, networking / server admin.


|-
|
[[User:AK47|AK47]]
|
B
|
* NOC
* WiFi
* VoIP
* General networking stuff
|
* Anything else


|-
| [[User:Pure|Joe Roberts]]
| None
|
* Help desk (WiFi connecting, server stuff, techy stuff!)
* Build up and tear down
* Talking to people
* (DBS Approved)
| Anything I can possibly do!


|-
|
[[User:immunda|Phil Howell]]
|
B1, B, f, k, p (clean)
|
* Help out with driving (has estate car if helpful)
* A/V stuff (have PA gear that can be used)
* Help with networking stuff
|
* Whatever is needed



|-
|
[[User:BuildTheRobots|Daniel Fligg]]
|
AM, A, B1, B, (f,k,p,q) (clean, since April 08)
|
* Enjoys driving
* Experience running PAs / Bands
* Networks & Communications (Team:Phone)
* Lots of marshaling experience.
|
* Whatever else is needed



|-
|
[[User:Arran|Arran Gallagher]]
|
None
|
* Help with the NOC
* Deploy wireless / wired network
* Sysadmin
|
* Help with build up and tear down
* Provide assistance to attendees



|-
|
[[User:ianthe88|Ianthe Sutherland]]
|
None
|
* Have a first aid certificate so happy to be noted as a first aider
* Meet & greet
|
* Whatever is needed



|-
|
[[User:greenhac|PeterJ]]
|
-
|
* Security/Car Park (EMF 2012 Security Alumnus)
|
* Whatever needs doing



|-
|
[[User:StuartL|StuartL]]
|
A, B, BE, C1, C1E, D1, D1E, f, k, l, n, p (clean)
|
* Drive minibuses/shuttle people generally
* Drive pretty much anything on/off road, incl heavy equipment
* Do Netwerk Shtuff
|
* Drive/operate/recover vehicles
* Design/implement network
* Provide network switch(es), cables
* Provide vehicle with tow-bar, if it's useful
* Provide generator (2.5kVA)



|-
|
[[User:mdg|mdg]]
|
N/A
|
* Bar Work
|
* Sysadmin if needed



|-
|
[[User:pobk|pobk]]
|
B1/B/f/k/p/q (Clean)
|
* Where required
* I volunteer for St John Ambulance and hold advanced first aid quals (Medgasses, AED, spinal, fractures etc). Happy to provide medical cover... May even be able to drag long kit.
|
* Whatever needs doing.



|-
|
[[User:mattg|mattg]]
|
B1/B/f/k/p/q (Clean)
|
* Drive things
* Help with infrastructure
* anything else that needs doing.
|
* Help with AV/stage stuff + streaming/recording etc.
* be friendly face to punters
* may be available for some of get-in.
* Whatever else needs doing.



|-
|
[[User:Mpresson|mpresson]]
|
A, B, BE, C1, C1E, D1, D1E, f, k, l, n, p (clean)
|
* Drive minibuses/shuttle people generally
* Bar work
|
* Pretty much anything within reason



|-
|
[[User:w1bble|w1bble]]
|
B, C1E, D1E (clean but a scrap of messy old paper)
|
* Be local to EMF [[Bletchley]] so can help before & poss after
* Take pictures
* Sysadmin if needed
* Be responsible for $offspring1 (Oliver age 11)
|
* Pretty much anything within reason (noting offspring requirement)



|-
|
[[User:Chewie|Chewie]]
|
B, C1E, D1E
|
* Networking
* Bringing a truck that can tow things that will fit onto a [http://www.johnrichardssurplus.co.uk/content/images/xxl/129.jpg NATO hitch]
* Server stuff - Linux and Windoze
|
* Pretty much anything technical :)
* Bringing a generator (at least 4kw), which is thirsty, but useful for emergencies



|-
|
[[User:marekventur|marekventur]]
|
B
|
* I can be there early that week and help with building up the camp/infrastructure
* Happy to help out with stewarding and whatever else needs doing during the camp
|
* Help with badges if any work is needed


|-
|
[[User:drcable|drcable]]
|
(none)
|
* Design of any kind
* Lots of experience builting things, from pouring concrete and other (semi-)permenant building work, through setting up large construcitons of poles, power tool work, down to soldering and expert gaffer tape application.
* Lots of experience with safer spaces stuff. Especially queer and trans stuff.
* I'd like to learn more networking stuff?
|
* Anything. Skills relativity lacking in electronics and code, especially compared to some of the über nerds.


|-
|
[[User:Ian W|Ian W]]
|
A
|
* First Aider, advanced life support & AED
* Get in / Get out
* Power systems (distribution, generators, lighting)
* Networking, electronics, LASERS, plumbing, drains, code, PA, etc.
* Getting things done
|
* Whatever is needed
* Dyslexic so keep away from money & number things



|-
|
[[User:Alex H|Alex H]]
|
B,C1,D1
|
* Set up/running festival shop or catering
* Video recording/editing for events or installations
* Finance stuff
|
* Recycling/trash
* Build up


|-
|
[[User:Mellchie|Mellchie]]
|
A, B (clean)
|
*Bar stuff
|
*No vehicle, can drive
*Might be helping out with NottingHack stuff



|-
|
[[User:TonyHoyle|TonyHoyle]]
|
AM/A/B1/B/f/k/l/n/p/q (clean)
|
*Setup, Teardown, Radio, Traffic, Stewarding
|
*Software guy but like most people have a home network with the usual collection of cisco routers, linux boxes, etc.
*Stewarded another festival for a few years so have some experience with dealing with pointing people/cars in the right direction.



|-
|
[[User:Detonate|Det]]
|
Nope
|
* Networks
* Bar Work
|
* Whatever



|-
|
[[User:TCMSLP|TCMSLP]]
|
A,B,C1,D1
|
* Assist with radio comms
* Licenced amateur, member of RAYNET
|
* Anything (example: network, power, linux SA, sound/PA, stewarding, litter)
* (arriving Friday)



|-
|
[[User:Dogsbody|Dogsbody]]
|
Yes, clean, not sure on categories, will update
|
* First Aid
* Fire Marshal
* I run a company specialising in Linux so anything Linux and Networking
|
* Happy to help with anything that makes me useful



|-
|
[[User:timb|Tim Brown]] aka [machine]
|
Yes, clean, A/B/B1
|
* Setup
* Teardown
|
* I run AS28792
* I'm Head Of Research at Portcullis - we will likely have a village
* Anything (example: network, linux SA, stewarding, litter)
* (can be there from from Thursday-Monday)



|-
|
[[User:thinkl33t|Bob Clough]]
|Nope
|
* Setup
* Badges
* Building huge things using scaff pole
|
* Networking
* Welding
* Gaffering

Villages:Hax0rz of the Roses

2014-07-07T13:31:45Z

Thinkl33t:

{{Village
|Name=Pennine Straddling Mega Villiage
|Description=This is a joint venture between Leeds Hackspace and Manchester Hackspace. We'll be bringing <thing> and <stuff>
|Contact=thinkl33t
}}

Villages:Hax0rz of the Roses

2014-07-07T10:55:54Z

Thinkl33t: Created page with "{{Village |Name=Penning Straddling Mega Villiage |Description=This is a joint venture between Leeds Hackspace and Manchester Hackspace. We'll be bringing <thing> and <stuff>..."

{{Village
|Name=Penning Straddling Mega Villiage
|Description=This is a joint venture between Leeds Hackspace and Manchester Hackspace. We'll be bringing <thing> and <stuff>
|Contact=thinkl33t
}}

Teams

2014-07-07T10:53:09Z

Thinkl33t:

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.

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.

{| class="wikitable sortable"
! Team
! Description
! Lead
! Deputy Lead(s)
|-
| [[Team:Admin]]
| Top-level organisation, licensing, site planning
| [[User:Russ]]
| [[User:Jonty]]
|-
| [[Team:Finance]]
| Dealing with the money
| [[User:Russ]]
| Paul2
|-
| [[Team:Site]]
| Tents, fences, trackway, etc.
| WillH
| [[User:Russ]]
|-
| [[Team:Power]]
| All things power, as well as basic site lighting.
| [[User:Benny]]
| Will H
|-
| [[Team:Sanitation]]
| Water supply, showers, toilets, rubbish.
| Paul2
| Crypt
|-
| [[Team:Security]]
| Making sure the site is safe.
| Crypt
|
|-
| [[Team:NOC]]
| Networking
| [[User:JasperWallace]]
| Will H, [[User:davidc]]
|-
| [[Team:Web]]
| Web sites, ticket sales, volunteering, and CfP systems
| [[User:ms7821|Mark]]
| [[User:JasperWallace]] (probably?)
|-
| [[Team:Content]]
| Organising talks/workshops/etc
| [[User:Jonty]]
| Tef
|-
| [[Team:Bar]]
| Booze, and such
| Chris W
| [[User:Russ]]
|-
| [[Team:First Aid]]
| Making sure we don't kill ourselves, as well as looking after attendee welfare.
| [[User:Oni|Oni]]
| Katie
|-
| [[Team:Catering]]
| Organising food providers
| Nick
| [[User:JasperWallace]] (maybe?)
|-
| [[Team:InfoDesk]]
| Providing information during the event
| SamLR
|
|-
| [[Team:Volunteering]]
| Managing volunteers across all stages
| Nick
| Lyndsey/Kate
|-
| [[Team:Spawn]]
| Managing the kids area, activities, and childminding
|
|
|-
| [[Team:Stage]]
| Staging, stage lighting, audio, and projection.
| [[User:TimRTerrible]]
| [[User:Solexious]]
|-
| [[Team:Video]]
| Video streaming and recording.
|
|
|-
| [[Team:Shiny]]
| Site decoration, lights, installations. Shiny things.
| SamLR
| [[User:Jonty]]
|-
| [[Team:Badge]]
| Badge building, and infrastructure.
| [[User:Dpslwk|Dpslwk]] ([[User talk:Dpslwk|talk]])
| [[User:thinkl33t|Bob]]/[[User:Jonty]]
|-
| [[Team:Sysadmin]]
| Making sure servers work, on and off site.
| [[User:JasperWallace]]
| [[User:Russ]]
|-
| [[Team:Phone]]
| Looking after Radios 2G, DECT, SIP etc.
|
|
|-
| [[Team:Villages]]
| Looking after villages and their requirements
|
|
|-
| [[Team:Sponsorship]]
| Looking after sponsors/vendors and their requirements.
| [[User:Jonty]]
|-
| [[Team:Lounge]]
| Organising the Lounge area
| [[User:Amx109|amx109]]
| [[User:Will-Do]]
|}

Team:Badge

2014-07-07T10:52:25Z

Thinkl33t: Created page with "Badges Badges Badges Badges Badges Badges Badges Badges Badges Badges Badges Badges MUSHROOM MUSHROOM"

Badges Badges Badges Badges Badges Badges Badges Badges Badges Badges Badges Badges MUSHROOM MUSHROOM

TiLDA MKe - the dream

2014-06-02T14:07:17Z

Thinkl33t:

== '''Note:''' THIS IS NOT THE FINAL BADGE SPECIFICATION. WE MIGHT HAVE HAD TO DROP THE SPECIFICATION A LITTLE :( ==

The TiLDA mk2 project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Solexious|Charles]], [[User:thinkl33t|Bob]] and [[User:Dpslwk|'RepRap' Matt]] 
If you wish to chat about the badge head over to the [irc://chat.freenode.com/##tilda ##tilda] IRC channel on freenode
=Aim=
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

==Features and Functions==
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. 
The notes from that session can be found here [[TiLDA 2/Ideas List]]
===Essential===
The following are considers core things that the badge must do for EMF2014
* Receive and display announcements on talks scheduling
** user registers their lanyard and which talks/workshops they are interested in on the emf web site
** 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)
* IR interaction
** could be used for business card mode, allow users to exchange info at push of a bottom
** games
** talking to TiLDA or SiNE
* Torch Mode
** One of the side effect of the two RGB LED's on TiLDA was they made a great torch
* Arduino Compatible
* Work during the event and be useful afterwards
** Battery voltage measurement and display, Charging management

===Nice to have===
The following are things that we hope to implement if we have the time and budget.
* Locations tracking
** 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
* Send text to it, not just talks (SMS you friends badge?)
** we will have a screen and ability to display text, so sending something to a other set badge should be easy.
* Use the spearks as a PA system, (download recorded WAV over network then synced playback start)
* TiLDA ad SiNE reprogramming
** 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
* TTS https://github.com/going-digital/Talkie

=Hardware=
The following hardware has been included on the badge.
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge
** 32bit ARM Cortex M3 * 84MHz
** 512KBytes Flash RAM
** 96KBytes of SRAM
* [http://repaper.org Repaper 2.7" ePaper display]
** a-Si TFT active matrix Electronic Paper Display(EPD)
** Resolution: 264 x 176
** Ultra low power consumption
** Super Wide Viewing Angle - near 180°
** Extra thin & light
** SPI interface
** Outline Dimension 70.42 x 45.80 mm
** Active Area 57.288 x 38.192 mm
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]
** 868Mhz RF Transceiver
** Simple UART interface
** Low power sleep mode
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro
** I2C interface
** 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
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection
* PMIC & LiPo
* Joystick
* Buttons
* RGB LED's
* IR
* Arduino Headers

===Prototype===
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.

===Production===
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.

=Software=
===Badge Firmware===

===Gateway===

===Server side===

=Hacking=
TiLDA Mk2 is base around the Arduino Due platform and this makes it easy to get started writing your own firmware from scratch. 
Unlike the Due, TILDA is not just a bare board and it all ready has lots of hardware wired up to the pins.
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. 
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. 

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] 
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] 
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/ 

Start the Arduino IDE and your will be able to select TiLDA Mk2 for the Tools->Board menu

=Sponsors=

[[Category: TiLDA]]

TiLDA MKe - the dream

2014-06-02T14:05:24Z

Thinkl33t:

'''Note:''' THIS IS NOT THE FINAL BADGE SPECIFICATION. WE MIGHT HAVE HAD TO DROP THE SPECIFICATION A LITTLE :(

The TiLDA mk2 project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Solexious|Charles]], [[User:thinkl33t|Bob]] and [[User:Dpslwk|'RepRap' Matt]] 
If you wish to chat about the badge head over to the [irc://chat.freenode.com/##tilda ##tilda] IRC channel on freenode
=Aim=
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

==Features and Functions==
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. 
The notes from that session can be found here [[TiLDA 2/Ideas List]]
===Essential===
The following are considers core things that the badge must do for EMF2014
* Receive and display announcements on talks scheduling
** user registers their lanyard and which talks/workshops they are interested in on the emf web site
** 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)
* IR interaction
** could be used for business card mode, allow users to exchange info at push of a bottom
** games
** talking to TiLDA or SiNE
* Torch Mode
** One of the side effect of the two RGB LED's on TiLDA was they made a great torch
* Arduino Compatible
* Work during the event and be useful afterwards
** Battery voltage measurement and display, Charging management

===Nice to have===
The following are things that we hope to implement if we have the time and budget.
* Locations tracking
** 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
* Send text to it, not just talks (SMS you friends badge?)
** we will have a screen and ability to display text, so sending something to a other set badge should be easy.
* Use the spearks as a PA system, (download recorded WAV over network then synced playback start)
* TiLDA ad SiNE reprogramming
** 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
* TTS https://github.com/going-digital/Talkie

=Hardware=
The following hardware has been included on the badge.
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8E]
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge
** 32bit ARM Cortex M3 * 84MHz
** 512KBytes Flash RAM
** 96KBytes of SRAM
* [http://repaper.org Repaper 2.7" ePaper display]
** a-Si TFT active matrix Electronic Paper Display(EPD)
** Resolution: 264 x 176
** Ultra low power consumption
** Super Wide Viewing Angle - near 180°
** Extra thin & light
** SPI interface
** Outline Dimension 70.42 x 45.80 mm
** Active Area 57.288 x 38.192 mm
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]
** 868Mhz RF Transceiver
** Simple UART interface
** Low power sleep mode
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro
** I2C interface
** 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
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection
* PMIC & LiPo
* Joystick
* Buttons
* RGB LED's
* IR
* Arduino Headers

===Prototype===
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.

===Production===
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.

=Software=
===Badge Firmware===

===Gateway===

===Server side===

=Hacking=
TiLDA Mk2 is base around the Arduino Due platform and this makes it easy to get started writing your own firmware from scratch. 
Unlike the Due, TILDA is not just a bare board and it all ready has lots of hardware wired up to the pins.
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. 
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. 

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] 
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] 
Now copy the "hardware" folder to your Sketchbook folder, this is usually ~/Sketchbook/ 

Start the Arduino IDE and your will be able to select TiLDA Mk2 for the Tools->Board menu

=Sponsors=

[[Category: TiLDA]]

TiLDA MKe - the dream

2014-01-14T14:46:13Z

Thinkl33t:

Planning for TiLDA version 2

The TiLDA mk2 project, Code name "ElectroMagnetic Boogaloo", is being headed by [[User:Solexious|Charles]], [[User:thinkl33t|Bob]] and [[User:Dpslwk|'RepRap' Matt]]
=Aim=
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

==Features and Functions==
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. 
The notes from that session can be found here [[TiLDA 2/Ideas List]]
===Essential===
The following are considers core things that the badge must do for EMF2014
* Receive and display announcements on talks scheduling
** user registers their lanyard and which talks/workshops they are interested in on the emf web site
** 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)
* IR interaction
** could be used for business card mode, allow users to exchange info at push of a bottom
** games
** talking to TiLDA or SiNE
* Torch Mode
** One of the side effect of the two RGB LED's on TiLDA was they made a great torch
* Arduino Compatible
* Work during the event and be useful afterwards
** Battery voltage measurement and display, Charging management

===Nice to have===
The following are things that we hope to implement if we have the time and budget.
* Locations tracking
** 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
* Send text to it, not just talks (SMS you friends badge?)
** we will have a screen and ability to display text, so sending something to a other set badge should be easy.
* Use the spearks as a PA system, (download recorded WAV over network then synced playback start)
* TiLDA ad SiNE reprogramming
** 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
* TTS https://github.com/going-digital/Talkie

=Hardware=
The following hardware has been included on the badge.
* [http://www.atmel.com/products/microcontrollers/arm/sam3x.aspx Atmel ATSAM3X8A]
** This is the same chip as the [http://arduino.cc/en/Main/ArduinoBoardDue Arduino Due] and gives us the base platform for the badge
** 32bit ARM Cortex M3 * 84MHz
** 512KBytes Flash RAM
** 96KBytes of SRAM
* [http://repaper.org Repaper 2.7" ePaper display]
** a-Si TFT active matrix Electronic Paper Display(EPD)
** Resolution: 264 x 176
** Ultra low power consumption
** Super Wide Viewing Angle - near 180°
** Extra thin & light
** SPI interface
** Outline Dimension 70.42 x 45.80 mm
** Active Area 57.288 x 38.192 mm
* [http://shop.ciseco.co.uk/srf-wireless-rf-radio-surface-mount/ Ciseco SRF Radio]
** 868Mhz RF Transceiver
** Simple UART interface
** Low power sleep mode
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] 3-axis Accelerometer and 3-axis gyro
** I2C interface
** 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
** Tri-Axis accelerometer with a programmable full scale range of ±2g, ±4g, ±8g and ±16g
** Digital Motion Processing™ (DMP™) engine offloads complex MotionFusion, sensor timing synchronization and gesture detection
* PMIC & LiPo
* Joystick
* Buttons
* RGB LED's
* IR
* Arduino Headers

===Prototype===
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.

===Production===
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.

=Software=
===Badge Firmware===

===Gateway===

===Server side===

=Hacking=

=Sponsors=

[[Category: TiLDA]]

Badges

2013-08-14T09:11:26Z

Thinkl33t:

We like to try and provide a great badge for each of our events, find out more below.

[[File:Emf2012_badge_pcb.png|thumb|300px]] 
==EMF2012==
[http://wiki-archive.emfcamp.org/2012/articles/b/a/d/Badge.html TiLDA] 
The first EMF camp badge, base around the Arduino Leonard, with on board IR, NRF24 Radio and RGB LED's. 
[http://blog.emfcamp.org/post/28558155390/revealing-tilda-our-camp-badge Revealing TiLDA, our camp badge!]

<div style="clear: both"></div>

[[File:SiNE_Front_Angle.JPG|thumb|300px]]
==EMW2013==
[[SiNE]] 
SiNE: Investigating the Neighbourhood of EMW 
Each attendee of Electromagnetic Wave receives a SiNE badge which has two purposes; firstly it allows you to take part in a treasure hunt based around the boat. By solving the clues you will be directed to an object or location either on or near the Stubnitz. The clue letter is also the first letter of the answer - when you arrive at the correct location you will find a large matching letter. Hold your badge in front of the letter, and the corresponding light on your badge will illuminate. 
<div style="clear: both"></div>

==EMF2014==
[[TiLDA 2]] 
The TiLDA mk2 project, Code name "ElectroMagnetic Boogaloo" 
Still in the early stages but you can see some of the Idea's we hope to bring to life here:
[[TiLDA 2/Idea's List]]

==Badge Team==

The baged team is being headed by
*[[User:Solexious|Charles]] from London Hackspace
*[[User:thinkl33t|Bob]] from HACMan
*[[User:Dpslwk|'RepRap' Matt]] from Nottinghack