More reformatting

Author: thinkl33t

docs/SiNE.md

@@ -1,8 +1,9 @@
-![](/images/800px-SiNE_Front_Angle.JPG "SiNE Front Angle")
+**S**iNE: **I**nvestigating the **N**eighbourhood of **E**MW
+
+![](images/800px-SiNE_Front_Angle.jpeg "SiNE Front Angle")
 
 ## About 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
@@ -32,10 +33,7 @@ preserved even if you remove the power
 
 #### Clue List
 
-Now EMWave has past here is the clue list: (Will add answers soon
---<a href="User:Dpslwk" class="wikilink" title="Dpslwk">Dpslwk</a>
-(<a href="User_talk:Dpslwk" class="wikilink" title="talk">talk</a>)
-14:21, 6 May 2013 (UTC))
+Now EMWave has passed here is the clue list:
 
 - A: I can't believe it's not butter!
 - B: Bond would be comfortable here and he has a licence.
@@ -60,14 +58,16 @@ Now EMWave has past here is the clue list: (Will add answers soon
 
 ### Locator ID
 
-![](800px-SiNE_Front_Buttons.jpeg "800px-SiNE_Front_Buttons.jpeg") Each
+<!-- BC: AFAICT these images are *gone* unless we have a backup of the 2012 wiki
+![](../images/800px-SiNE_Front_Buttons.jpeg "800px-SiNE_Front_Buttons.jpeg") -->
+Each
 badge is programmed with a unique ID, that is transmitted about 5 times
 a second. There will be Raspberry Pi's doted around the ship, collecting
 data.
 EMF will not know your badge ID, as there are handed out at random.
 A badge's ID is shown on the LED using binary encoding. This is done at
 power up, or by pressing and holding the "ID" button
-If you **do not** wish to have your badge trasnmitting an ID you can
+If you **do not** wish to have your badge transmitting an ID you can
 clear it by holding the "Erase" button for about 5 seconds.
 
 The badge ID is 9 bit's long, these are displayed across the A-I LED's,
@@ -78,14 +78,11 @@ Example if LED's A D E and H are lit then we have 010011001 in binary or
 Unfortunately due to a lack of time the Raspberry Pi's were never setup,
 as so no data was collected.
 
-<div style="clear: both">
-
-</div>
-
 ## Sponsors
 
-![](800px-SiNE_Back_Angle.JPG "800px-SiNE_Back_Angle.JPG") SiNE was only
-possible thanks to our sponsors:
+<!-- BC: AFAICT these images are *gone* unless we have a backup of the 2012 wiki
+![](../images/800px-SiNE_Back_Angle.JPG "800px-SiNE_Back_Angle.JPG") -->
+SiNE was only possible thanks to our sponsors:
 
 - [Twilio](http://www.twilio.com) A Cloud communications company
   sponsored the parts need to make badges.
@@ -99,7 +96,9 @@ possible thanks to our sponsors:
 
 ### DevBoards
 
-![](DevBoards.JPG "DevBoards.JPG") Before designing the final SiNE badge
+<!-- BC: AFAICT these images are *gone* unless we have a backup of the 2012 wiki
+![](../images/DevBoards.JPG "DevBoards.JPG") -->
+Before designing the final SiNE badge
 we built three development boards, not bothered about the looks, they
 were built to test the hardware and wiring between the parts.
 Once it was confirmed that the parts worked together they were passed
@@ -108,19 +107,16 @@ scavenger hunt and location tracking.
 Using these development boards meant the software was ready to go around
 the same time as the final badges were produced.
 
-<div style="clear: both">
-
-</div>
-
 ## Badge Hacking
 
-![](800px-SiNE_Schematic.png "800px-SiNE_Schematic.png") We actively
-encourage users to hack there badge better and hope the information
+<!-- BC: AFAICT these images are *gone* unless we have a backup of the 2012 wiki
+![](../images/800px-SiNE_Schematic.png "800px-SiNE_Schematic.png") -->
+We actively encourage users to hack their badge better and hope the information
 provided below will help
 
 ### Flashing and Fuses
 
-We use avrdude and an ISP programer to flash the ATTiny44A Example
+We use avrdude and an ISP programmer to flash the ATTiny44A Example
 command lines can be found in the Makefile in the SiNE-Firmware github
 
 avrdude part flag (-p) is t44
@@ -148,6 +144,3 @@ The following parts were used: (data-sheet links to come)
 
 - [PCB](https://github.com/EMF-TiLDA/SiNE-PCB)
 - [Firmware](https://github.com/EMF-TiLDA/SiNE-Firmware)
-
-<a href="Category:Badges" class="wikilink"
-title="Category:Badges">Category:Badges</a>

docs/TiLDA_MK3/Badge16_Ideas.md

@@ -1,3 +1,6 @@
+This was our original list of ideas and plans for the 2016 badge and is preserved
+here for historical interest
+
 ## Software
 
 - Interpreter for high level functionality
@@ -59,4 +62,4 @@
   - supply little bags of LEDs and thread for say £2
 - extra GPIO broken out
   - ardiuno footprint?
-- python/LUA would allow for beginners to hack the badge
+- python/LUA would allow for beginners to hack the badge

docs/TiLDA_MK3/Ideas.md

@@ -6,26 +6,21 @@ page for the project and link it here.
 
 ### Small things
 
-\- Replace snake's block colours with images
-
-\- Accelerometer ball bounce
-
-\- Network synced clock
+- Replace snake's block colours with images
+- Accelerometer ball bounce
+- Network synced clock
 
 ### Larger projects
 
-\- IRC relay
-
--Location based on wifi RSSI ( badge team are looking for someone to
+- IRC relay
+- Location based on wifi RSSI ( badge team are looking for someone to
 write a good library for this)
-
-\- [High altitude balloon
+- [High altitude balloon
 tracker](https://badge.emfcamp.org/wiki/TiLDA_MK3/Ideas/hab)
 
 ## apps
 
-\- Network Map for location approximation:
+- Network Map for location approximation:
 <a href="TiLDA_MK3/apps/nmap" class="wikilink"
 title="tilda-nmap">tilda-nmap</a>
-
-\- Interactive python prompt
+- Interactive python prompt

docs/TiLDA_MK3/Introduction_to_badge_hacking.md

@@ -8,19 +8,11 @@ You should have received an LED and a resistor with your badge. First,
 grab the resistor. Bend the legs over so they fit in the holes in the
 board, using the resistor lead bender.
 
-<figure>
-<img src="Hackpad.com_Rs7awClTQDH_p.554927_1470420913282_legbender.jpg"
-title="Hackpad.com_Rs7awClTQDH_p.554927_1470420913282_legbender.jpg" />
-<figcaption>Hackpad.com_Rs7awClTQDH_p.554927_1470420913282_legbender.jpg</figcaption>
-</figure>
+![](../images/Hackpad.com_Rs7awClTQDH_p.554927_1470420913282_legbender.jpg)
 
 It doesn't matter way round the resistor goes.
 
-<figure>
-<img src="Hackpad.com_Rs7awClTQDH_p.554927_1470307053798_P1010517.jpg"
-title="Hackpad.com_Rs7awClTQDH_p.554927_1470307053798_P1010517.jpg" />
-<figcaption>Hackpad.com_Rs7awClTQDH_p.554927_1470307053798_P1010517.jpg</figcaption>
-</figure>
+![](../images/Hackpad.com_Rs7awClTQDH_p.554927_1470307053798_P1010517.jpg)
 
 Flip over your board and solder the resistor in place, then trim down
 the legs to be flush against the board.
@@ -29,11 +21,7 @@ Next, the LED. It does matter which way round the LED goes - look for a
 flat side on the LED and match it up with the flat side on the board.
 Pull your LED out about a centimetre and bend it over a bit.
 
-<figure>
-<img src="Hackpad.com_Rs7awClTQDH_p.554927_1470307470838_P1010533.jpg"
-title="Hackpad.com_Rs7awClTQDH_p.554927_1470307470838_P1010533.jpg" />
-<figcaption>Hackpad.com_Rs7awClTQDH_p.554927_1470307470838_P1010533.jpg</figcaption>
-</figure>
+![](../images/Hackpad.com_Rs7awClTQDH_p.554927_1470307470838_P1010533.jpg)
 
 Flip the board over and solder the LED into place.
 
@@ -47,9 +35,11 @@ because you'll see three \> symbols.
 
 Type the following at the prompt. This should turn your LED on!
 
-`import pyb`
-`pin = pyb.Pin("LED_TORCH")`
-`pin.high()`
+```python
+import pyb
+pin = pyb.Pin("LED_TORCH")
+pin.high()
+```
 
 Of course, thats a bit of a pain to do every time we want the LED on, so
 let's make an app!
@@ -65,53 +55,59 @@ file. Open it in a text editor.
 First, we need to tell the badge some details about your app. This is
 done in a header section at the top of the file
 
-`# Author: Your Name `
-`# Description: Torch `
-`# Category: Flashy `
-`# License: MIT `
-`# Appname : Torch `
-`# Built-in: no `
+```python
+# Author: Your Name 
+# Description: Torch 
+# Category: Flashy 
+# License: MIT 
+# Appname : Torch 
+# Built-in: no 
+```
 
 You could save and run your app now, but it wont actually do anything
 yet. Lets add the code:
 
-`# Author: Your Name `
-`# Description: Torch `
-`# Category: Flashy `
-`# License: MIT `
-`# Appname : Torch `
-`# Built-in: no `
-
-`import pyb`
-`pin = pyb.Pin("LED_TORCH")`
-`pin.high() `
-`while True:`
-`  pass`
+```python
+# Author: Your Name 
+# Description: Torch 
+# Category: Flashy 
+# License: MIT 
+# Appname : Torch 
+# Built-in: no 
+
+import pyb
+pin = pyb.Pin("LED_TORCH")
+pin.high() 
+while True:
+  pass
+```
 
 Save, and run your app. When you run it the LED should turn on, brill!
 
 Of course, we're not showing anything on the screen. Lets have a nice
 notice box to show we're in the torch instead of that while loop.
 
-`# Author: Your Name `
-`# Description: Torch `
-`# Category: Flashy `
-`# License: MIT `
-`# Appname : Torch `
-`# Built-in: no `
-
-`import pyb`
-`import ugfx`
-`import dialogs`
-
-`pin = pyb.Pin("LED_TORCH")`
-`pin.high() `
-`ugfx.init()`
-`ugfx.clear(ugfx.html_color(0x7c1143))`
-`dialogs.notice("Shine a light!", title="Torch", close_text="Exit")`
+```python
+# Author: Your Name 
+# Description: Torch 
+# Category: Flashy 
+# License: MIT 
+# Appname : Torch 
+# Built-in: no 
+
+import pyb
+import ugfx
+import dialogs
+
+pin = pyb.Pin("LED_TORCH")
+pin.high() 
+ugfx.init()
+ugfx.clear(ugfx.html_color(0x7c1143))
+dialogs.notice("Shine a light!", title="Torch", close_text="Exit")
+```
 
 Run your app again and you should have a nice button you can press to
 shine a light in the camp!
 
 You can unplug the badge from your computer when the LED has finished
-flashing, but we recommend you eject the drive first.
+flashing, but we recommend you eject the drive first.

docs/TiLDA_MK3/adc.md

@@ -6,23 +6,29 @@ All ADC readings are referenced to the supply rail, which is about 3.3V.
 To increase the ADC accuracy, the internal voltage reference can be
 read, and used to offset variations in the supply rail.
 
-    adcin = pyb.ADC(channel_to_read).read()
-    ref_reading = pyb.ADC(0).read()
-    supply_voltage = 4095/ref_reading*1.21  # or change 1.21 with the calibrated value - see below
-    adc_voltage =  adcin / 4095 * supply_voltage
+```python
+adcin = pyb.ADC(channel_to_read).read()
+ref_reading = pyb.ADC(0).read()
+supply_voltage = 4095/ref_reading*1.21  # or change 1.21 with the calibrated value - see below
+adc_voltage =  adcin / 4095 * supply_voltage
+```
 
 Note, the factory reads the internal reference with a supply voltage of
 3.0V, and stores this reading. This can then be used to get the actual
 voltage reference. For example
 
-    import stm
-    factory_reading = stm.mem16[0x1FFF75AA]
-    reference_voltage = factory_reading/4095*3   # will be approximately 1.21V
+```python
+import stm
+factory_reading = stm.mem16[0x1FFF75AA]
+reference_voltage = factory_reading/4095*3   # will be approximately 1.21V
+```
 
 For convenience, the library \`onboard' provides the following functions
 for reading the battery voltage, unregulated voltage, or light level
 
-    import onboard
-    onboard.get_battery_voltage()
-    onboard.get_unreg_voltage()
-    onboard.get_light()
+```python
+import onboard
+onboard.get_battery_voltage()
+onboard.get_unreg_voltage()
+onboard.get_light()
+```

docs/TiLDA_MK3/apps.md

@@ -3,14 +3,16 @@ docs
 [1](https://docs.micropython.org/en/latest/pyboard/library/pyb.RTC.html)
 for more information.
 
-    # Create a RTC object
-    rtc = pyb.RTC()
+```python
+# Create a RTC object
+rtc = pyb.RTC()
 
-    # If the RTC isn't running, call
-    rtc.init()
+# If the RTC isn't running, call
+rtc.init()
 
-    # Set the time
-    rtc.datetime((2016, 5, 1, 4, 13, 0, 0, 0))
+# Set the time
+rtc.datetime((2016, 5, 1, 4, 13, 0, 0, 0))
 
-    # Get the time
-    print(rtc.datetime())
+# Get the time
+print(rtc.datetime())
+```