Electromagnetic Field - User contributions [en]

DIY TiLDA Badge Network

2014-10-02T18:11:06Z

Drrk: /* Setting the name on your badge */

The steps below allow you to setup your own private wireless badge network for your TiLDA badge to connect to. The wireless network lets the badge display the current time, display your name and send notification messages to the badge.

There are quite a lot of steps to getting this working. The instructions below assume the following hardware and software:
* TiLDA Mke
* Raspberry Pi, PSU, keyboard HDMI cable, monitor/TV, Ethernet cable or Wifi
* 2 Ciseco radios: USB + Slice of Radio (for RPi), or a second USB radio instead
** Actual part numbers to aid in ordering from http://shop.ciseco.co.uk/ - R017 is the slice of radio, R010 is the SRF Stick
* Internet connection for downloading new packages
* 4GB SD Card (or larger)

If you don't have a Raspberry Pi then you may be able to substitute it with another Linux PC.

== Network architecture ==
The key components of the badge network are:
* Master control program (MCP), this stores a central copy of all information and generates the content of the radio messages.
* Gateways, these have the radios and pass the radio messages to and from the MCP.
* Database, this stores the registered gateways, badges and users.
* Web server, this provides a status page and web API
* some example scripts which use the web API to send special messages to the badges

For the purposes of these instructions we run all this software on a single RaspberryPi. These instructions are simplified to assume you just want to run this network for yourself and willing to run everything as the 'pi' user.

== Installation steps ==
=== Installing initial OS and hardware install ===
* Download http://director.downloads.raspberrypi.org/raspbian/images/raspbian-2014-09-12/2014-09-09-wheezy-raspbian.zip
* Write to SD card
* Plug SD card into Rpi
* Connect Slice Of Radio
* Connect USB Ciseco radio
* Connect keyboard
* Use Ethernet cable to connect RPi to your network
* Connect HDMI to TV/Monitor
* Power On

=== OS configuration ===
When the RPi has booted it will present the raspi-config UI. By default, the raspian software will try to use the serial port connected to the radio for a serial console and this must be disabled otherwise we cannot use the radio:
* Select 'Advanced'
* Select 'A7 Serial - Enable/Disable shell and kernel messages on the serial connection'
* Choose No
* Select "expand filesystem" option
* Select "finish" + and say yes to "reboot now?"
Wait for RPi to reboot
After reboot you can choose whether you want to carry on with HDMI + local keyboard or SSH to device using the IP address that is displayed.
The default login for the RPi is "pi" + "raspberry"

=== Package installation ===
The software relies on several packages which must be downloaded and installed. The installation will take some time. Ignore any errors about being unable to contact the Wolfram package repository.
sudo apt-get update
sudo apt-get install -y python-pip python-dev python-requests postgresql postgresql-server-dev-9.1

=== Checkout Mk2-Software ===
The forked copy of the software below has a few additions to make the setup and installation work using these instructions
cd ~
git clone --branch diy-badge-network https://github.com/jburgess777/Mk2-Software.git

=== PostgreSQL database configuration ===
We must add a 'pi' user and create a 'schedule' database used to store information about the gateways, badges and users. The final command will emit several lines of messages as it creates various tables and indexes.
cd ~/Mk2-Software
sudo -u postgres createuser -D -R -S pi
sudo -u postgres createdb -O pi schedule
psql -f schedule.sql schedule

=== Setup python software packages ===
The badge network softwre relies on several python libraries which must be downloaded and built
sudo ./setup.py develop

=== Generate radio message signing keys ===
The messages sent across the badge network are signed with a cryptographic key to ensure that the badges only accept messages from an authorized network. Since we don't have the keys that are in the current TiLDA firmware we must create our own.
cd ~/Mk2-Software/lib
make signer
make keys.txt
make keys.sh

=== Running the MCP software ===
Before starting the MCP we must first load the keys we generated above. When the MCP is started it will display messages about its configuration and start listening for gateways to connect.
cd ~/Mk2-Software
source lib/keys.sh
mcp.py

=== Running the gateway ===
Open another connection to the Pi (or switch tty with alt-Fx keys and login as 'pi').
gateway.py localhost
When you start the gateway it opens up the serial ports for the two radios and configures them to communicate with the badges:
<nowiki> 2014-09-24 19:46:46,700 - UsbRadios - INFO - Found radio: /dev/ttyACM0, speed 115200
2014-09-24 19:46:46,734 - UsbRadios - INFO - Found radio: /dev/ttyAMA0, speed 9600
2014-09-24 19:46:46,741 - UsbRadios - INFO - Entering AT mode...
2014-09-24 19:46:47,955 - UsbRadios - INFO - Reading information for /dev/ttyACM0
2014-09-24 19:46:48,065 - UsbRadios - INFO - Firmware: 0.51B USB
2014-09-24 19:46:49,428 - UsbRadios - INFO - Reading information for /dev/ttyAMA0
2014-09-24 19:46:49,557 - UsbRadios - INFO - Firmware: 0.90B SORSRF
2014-09-24 19:46:50,569 - main - INFO - MAC: 202481588515999
2014-09-24 19:46:50,698 - main - INFO - Established connection to mcp
2014-09-24 19:46:50,718 - Gateway - INFO - Transmitter started
2014-09-24 19:46:52,764 - UsbRadios - INFO - Configuring radio 0 with [u'ATPK08', u'ATCN02', u'ATAC', u'ATDN']
2014-09-24 19:46:54,081 - UsbRadios - INFO - Applied command 'ATPK08' to radio 0, got 'OK'
2014-09-24 19:46:54,191 - UsbRadios - INFO - Applied command 'ATCN02' to radio 0, got 'OK'
2014-09-24 19:46:54,321 - UsbRadios - INFO - Applied command 'ATAC' to radio 0, got 'OK'
2014-09-24 19:46:54,449 - UsbRadios - INFO - Applied command 'ATDN' to radio 0, got 'OK'
2014-09-24 19:46:54,452 - UsbRadios - INFO - Configuring radio 1 with [u'ATPK3A', u'ATCN06', u'ATAC', u'ATDN']
2014-09-24 19:46:55,819 - UsbRadios - INFO - Applied command 'ATPK3A' to radio 1, got 'OK'
2014-09-24 19:46:55,939 - UsbRadios - INFO - Applied command 'ATCN06' to radio 1, got 'OK'
2014-09-24 19:46:56,077 - UsbRadios - INFO - Applied command 'ATAC' to radio 1, got 'OK'
2014-09-24 19:46:56,214 - UsbRadios - INFO - Applied command 'ATDN' to radio 1, got 'OK'
2014-09-24 19:46:56,226 - Gateway - INFO - Receiver started
2014-09-24 19:46:56,767 - UsbRadios - DEBUG - Packet send via radio 0: 100
2014-09-24 19:47:01,625 - UsbRadios - DEBUG - Packet send via radio 0: 200
... more radio messages every 5 seconds</nowiki>
If the software cannot initialize the radio then try again, something seems to prevent the radio from working on the first attempt. If it still doesn't work after a couple of attempts then check that you completed the first setup step which told you to turn off the serial console.
==== Why two radios? ====
The first radio is used solely to broadcast discovery information to notify the badges about the existance of the gateway. All gateways transmit on the same discovery channel and the badge will connect to the gateway with the strongest signal (RSSI). These discovery messages include information about the channel used by the second radio and the time. Once the badge chooses a gateway it will switch to the channel which is unique to the gateway. This second radio will be used for all future communcation between the badge and the network.
==== MCP radio messages ====
The MCP instructs each geateway to send a packet every 5 seconds. This packet includes timing information telling the badges when they should communicate back to the gateway. The content of these messages is displayed in the MCP output:
<nowiki>
{"cid":"*", "duration_in_sec":5.2, "event":"add_transmit_window_to_all_connections", "num_queues":1, "origin":"DataQueue", "payload_len":4, "rid":45057, "time":"2014-09-24 19:46:52"}
{"cid":1, "duration_in_sec":5.2, "event":"add_transmit_window", "origin":"DataQueue", "time":"2014-09-24 19:46:52"}
b0010000000488e69316cbed2390e1f92ccd85016af2a55000b61abbf83a6ddf77fdb7b1c175803a163cb68a852fb5ddba9f6129329259fe581b
b0010000138800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
{"event":"pause_connection_for_duration", "origin":"MainChannelSender", "pause_until":1411588017.319312, "time":"2014-09-24 19:46:52"}
</nowiki>
The first 2 bytes of all radio messages indicate the message type, or RID. This is 'b001' for the packets above.
==== The first signs of communication with the badge ====
Once you have reached this far the badge network should be sending messages which will be picked up by the badge. Turn on badge, wait for a minute or two and then press up/down button to refresh the display. With any luck the "Welcome" at the top of the screen will be replaced with the current time and some status messages will appear at the bottom of the screen showing a randomly generated gateway ID and the radio signal strength.

=== Update public key in badge firmware ===
During one of the earlier steps we generated a random key for the radio messages in this badge network. The default badge firmware only trusts messages signed by the official EMF camp signing key which we don't have. To get any further we need to update the public key in the badge firmware to make it trust the messages from your new MCP.
cd ~/Mk2-Software/lib
make keys.c
This will output the information you need to add to the firmware source code:
<nowiki> # To make your badge trust messages signed by your
# new key pair you must replace the public key in
# EMF2014Config.h with:

const uint8_t EMF_PUBLIC_KEY[40] = {
... lots of hex numbers ...
};</nowiki>
Open the EMF2014Config.h from the Mk2-Firmware/EMD2014 sketch. Find and replace the EMF_PUBLIC_KEY with the one that was printed above. Open the arduino IDE, connect your badge to via USB, build & flash the new firmware.

=== Registering the badge on the network ===
After you have installed the firmware above the badge will reboot. Wait a few minutes and this time the badge should register itself to the network. The output on the gateway program should show it receiving messages from the badge, beginning "9002...". These messages are the badge requesting a badge ID from the MCP:
<nowiki>
2014-09-24 20:08:37,274 - UsbRadios - DEBUG - Packet send via radio 0: 26100
2014-09-24 20:08:42,274 - UsbRadios - DEBUG - Packet send via radio 0: 26200
2014-09-24 20:08:47,274 - UsbRadios - DEBUG - Packet send via radio 0: 26300
2014-09-24 20:08:50,303 - Gateway - DEBUG - Received packet with rssi -42: 0a
2014-09-24 20:08:52,273 - UsbRadios - DEBUG - Packet send via radio 0: 26400
2014-09-24 20:08:56,250 - Gateway - DEBUG - Received packet with rssi -42: 90020000203132503834353631343031333030360000000000000000000000000000000000000000000000000000000000000000000000000000
2014-09-24 20:08:58,274 - UsbRadios - DEBUG - Packet send via radio 0: 26500
2014-09-24 20:09:01,825 - Gateway - DEBUG - Received packet with rssi -42: 90020000203132503834353631343031333030360000000000000000000000000000000000000000000000000000000000000000000000000000
2014-09-24 20:09:03,274 - UsbRadios - DEBUG - Packet send via radio 0: 26600
</nowiki>
The MCP window should show it transmitting the signed response packets starting "b002..."
<nowiki>
b002000000268f1f16ee0a4f5fe7dcb4a69bacdc0f4038c87d368dc2527a26fe7f86a232e0804bf10645afe414a90d122d8241e200f464f2d7cf
b0022031325038343536313430313330303600010000000000000000000000000000000000000000000000000000000000000000000000000000
</nowiki>

If you now select the BadeID app on your TiLDA then it should now say that it has been assigned badge ID EMF0001.

=== Setting the name on your badge ===
Each badge has a unique hardware ID which was programned into the CPU by Atmel. This hardware ID is sent to the MCP when the badge asks it to assign a badge ID. This unique hardware ID ensures that you will get the same badge ID each time you reset the badge. The MCP store this in the 'badge' table in the database:
<nowiki>
pi@raspberrypi ~ $ psql schedule
psql (9.1.13)
Type "help" for help.

schedule=> select * from badge;
id | hwid | date | gwid
----+----------------------------------+------+------
1 | 20313250383435363134303133303036 | | 1
(1 row)
</nowiki>

The badgeID app mentions registering on a web page but we don't have this available. Instead you can add your name and nickname directly into the database and the MCP will tell your badge to display this name next time it registers. You can personalize the name and nickname however the LCD can only display strings of up to 10 characters. You can put spaces in the front to align the text that is displayed. The EMF0001 badge ID is the one that your badge should have obtained earlier.
<nowiki>
schedule=> INSERT INTO "user" VALUES ( 'My Name', 'Nickname', 'EMF0001' );
INSERT 0 1
schedule=> \q
</nowiki>
To make your badge learn this new name you must hit reset and wait for it to acquire its badge ID again, check this in the badge app. Now return to the home screen and hold the badge vertically, like it is hanging on a lanyard, with the two large holes in the PCB at the top. When the EMF logo appears your name should now be shown at the top of the screen.

== Using the badge network ==
=== Web interface ===
The MCP software runs a web interface and API on port 8888, point your web browser at:
<nowiki>http://RPi-IP-Address:8888/index.html</nowiki>

=== Notification messages ===
The badges and network have the ability to send a text message to a specific badge, or to all badges. The command below sends a message to all badges and this should appear on your badge after a few seconds delay:
cd ~/Mk2-Software/emfbroadcaster
./flashmsg.py "Hello from my DIY badge network"
Or a message to a specific badge number:
./dm.py 1 "message to badge one"

=== Weather ===
The <code>weather.py</code> script will send weather updates but you must register for a Met Office API key and place this in the <code>~/Mk2-Software/etc/secret_config.json</code> file.

=== Schedule ===
The <code>schedule.py</code> script broadcasts schedule update to the badge. This requires additional information to be added to an 'event' table in the database. There is currently no documentation on how to do this.

== Ideas and areas for improvement ==
* The badge notification messages include LED and sound fields to make the user aware of the alert but these are not implemented in badge firmware.
* The badge sends a packet on RID 9004 which indicates its battery status. Currently the MCP prints a message saying it received this but does nothing else with it. It might be interesting to log the battery information and RSSI into a file or database as an example of how to collect data from the badges.
* Enhance the EMFTris and Snake apps to tell the MCP about the highscores. Record in a log and create a web page showing the highscores for each badge.
* The current badge architecture was designed around the needs of a large distributed system. In an isolated network it would be nice to have a special mode which works with just a single radio. Or perhaps send the data to the badge via the USB serial so no radio is necessary at all.
* Add a voting app which broadcasts a question to all badges, shows the choices on the screen and uses a button to select. Send the response back to the MCP and display the results on a web page.
* The original Mk2-Software relies on a special radio firmware mode 'ATZD3' which indicates the end of paket boundary and RSSI. This firmware was specially made by Ciseco for EMFCamp and this feature is not present in the standard radios. The forked Mk2-Software has some tweaks to make it work with the standard firmware but this lacks the RSSI information and may not work with multiple badges. It might be possible to use one of the other radio debug modes (ATZD1 or ATZD2) which the public firmware supports to provide the same information as ATZD3.

DIY TiLDA Badge Network

2014-10-02T18:10:42Z

Drrk: /* Setting the name on your badge */ - Add note about leading spaces in name

The steps below allow you to setup your own private wireless badge network for your TiLDA badge to connect to. The wireless network lets the badge display the current time, display your name and send notification messages to the badge.

There are quite a lot of steps to getting this working. The instructions below assume the following hardware and software:
* TiLDA Mke
* Raspberry Pi, PSU, keyboard HDMI cable, monitor/TV, Ethernet cable or Wifi
* 2 Ciseco radios: USB + Slice of Radio (for RPi), or a second USB radio instead
** Actual part numbers to aid in ordering from http://shop.ciseco.co.uk/ - R017 is the slice of radio, R010 is the SRF Stick
* Internet connection for downloading new packages
* 4GB SD Card (or larger)

If you don't have a Raspberry Pi then you may be able to substitute it with another Linux PC.

== Network architecture ==
The key components of the badge network are:
* Master control program (MCP), this stores a central copy of all information and generates the content of the radio messages.
* Gateways, these have the radios and pass the radio messages to and from the MCP.
* Database, this stores the registered gateways, badges and users.
* Web server, this provides a status page and web API
* some example scripts which use the web API to send special messages to the badges

For the purposes of these instructions we run all this software on a single RaspberryPi. These instructions are simplified to assume you just want to run this network for yourself and willing to run everything as the 'pi' user.

== Installation steps ==
=== Installing initial OS and hardware install ===
* Download http://director.downloads.raspberrypi.org/raspbian/images/raspbian-2014-09-12/2014-09-09-wheezy-raspbian.zip
* Write to SD card
* Plug SD card into Rpi
* Connect Slice Of Radio
* Connect USB Ciseco radio
* Connect keyboard
* Use Ethernet cable to connect RPi to your network
* Connect HDMI to TV/Monitor
* Power On

=== OS configuration ===
When the RPi has booted it will present the raspi-config UI. By default, the raspian software will try to use the serial port connected to the radio for a serial console and this must be disabled otherwise we cannot use the radio:
* Select 'Advanced'
* Select 'A7 Serial - Enable/Disable shell and kernel messages on the serial connection'
* Choose No
* Select "expand filesystem" option
* Select "finish" + and say yes to "reboot now?"
Wait for RPi to reboot
After reboot you can choose whether you want to carry on with HDMI + local keyboard or SSH to device using the IP address that is displayed.
The default login for the RPi is "pi" + "raspberry"

=== Package installation ===
The software relies on several packages which must be downloaded and installed. The installation will take some time. Ignore any errors about being unable to contact the Wolfram package repository.
sudo apt-get update
sudo apt-get install -y python-pip python-dev python-requests postgresql postgresql-server-dev-9.1

=== Checkout Mk2-Software ===
The forked copy of the software below has a few additions to make the setup and installation work using these instructions
cd ~
git clone --branch diy-badge-network https://github.com/jburgess777/Mk2-Software.git

=== PostgreSQL database configuration ===
We must add a 'pi' user and create a 'schedule' database used to store information about the gateways, badges and users. The final command will emit several lines of messages as it creates various tables and indexes.
cd ~/Mk2-Software
sudo -u postgres createuser -D -R -S pi
sudo -u postgres createdb -O pi schedule
psql -f schedule.sql schedule

=== Setup python software packages ===
The badge network softwre relies on several python libraries which must be downloaded and built
sudo ./setup.py develop

=== Generate radio message signing keys ===
The messages sent across the badge network are signed with a cryptographic key to ensure that the badges only accept messages from an authorized network. Since we don't have the keys that are in the current TiLDA firmware we must create our own.
cd ~/Mk2-Software/lib
make signer
make keys.txt
make keys.sh

=== Running the MCP software ===
Before starting the MCP we must first load the keys we generated above. When the MCP is started it will display messages about its configuration and start listening for gateways to connect.
cd ~/Mk2-Software
source lib/keys.sh
mcp.py

=== Running the gateway ===
Open another connection to the Pi (or switch tty with alt-Fx keys and login as 'pi').
gateway.py localhost
When you start the gateway it opens up the serial ports for the two radios and configures them to communicate with the badges:
<nowiki> 2014-09-24 19:46:46,700 - UsbRadios - INFO - Found radio: /dev/ttyACM0, speed 115200
2014-09-24 19:46:46,734 - UsbRadios - INFO - Found radio: /dev/ttyAMA0, speed 9600
2014-09-24 19:46:46,741 - UsbRadios - INFO - Entering AT mode...
2014-09-24 19:46:47,955 - UsbRadios - INFO - Reading information for /dev/ttyACM0
2014-09-24 19:46:48,065 - UsbRadios - INFO - Firmware: 0.51B USB
2014-09-24 19:46:49,428 - UsbRadios - INFO - Reading information for /dev/ttyAMA0
2014-09-24 19:46:49,557 - UsbRadios - INFO - Firmware: 0.90B SORSRF
2014-09-24 19:46:50,569 - main - INFO - MAC: 202481588515999
2014-09-24 19:46:50,698 - main - INFO - Established connection to mcp
2014-09-24 19:46:50,718 - Gateway - INFO - Transmitter started
2014-09-24 19:46:52,764 - UsbRadios - INFO - Configuring radio 0 with [u'ATPK08', u'ATCN02', u'ATAC', u'ATDN']
2014-09-24 19:46:54,081 - UsbRadios - INFO - Applied command 'ATPK08' to radio 0, got 'OK'
2014-09-24 19:46:54,191 - UsbRadios - INFO - Applied command 'ATCN02' to radio 0, got 'OK'
2014-09-24 19:46:54,321 - UsbRadios - INFO - Applied command 'ATAC' to radio 0, got 'OK'
2014-09-24 19:46:54,449 - UsbRadios - INFO - Applied command 'ATDN' to radio 0, got 'OK'
2014-09-24 19:46:54,452 - UsbRadios - INFO - Configuring radio 1 with [u'ATPK3A', u'ATCN06', u'ATAC', u'ATDN']
2014-09-24 19:46:55,819 - UsbRadios - INFO - Applied command 'ATPK3A' to radio 1, got 'OK'
2014-09-24 19:46:55,939 - UsbRadios - INFO - Applied command 'ATCN06' to radio 1, got 'OK'
2014-09-24 19:46:56,077 - UsbRadios - INFO - Applied command 'ATAC' to radio 1, got 'OK'
2014-09-24 19:46:56,214 - UsbRadios - INFO - Applied command 'ATDN' to radio 1, got 'OK'
2014-09-24 19:46:56,226 - Gateway - INFO - Receiver started
2014-09-24 19:46:56,767 - UsbRadios - DEBUG - Packet send via radio 0: 100
2014-09-24 19:47:01,625 - UsbRadios - DEBUG - Packet send via radio 0: 200
... more radio messages every 5 seconds</nowiki>
If the software cannot initialize the radio then try again, something seems to prevent the radio from working on the first attempt. If it still doesn't work after a couple of attempts then check that you completed the first setup step which told you to turn off the serial console.
==== Why two radios? ====
The first radio is used solely to broadcast discovery information to notify the badges about the existance of the gateway. All gateways transmit on the same discovery channel and the badge will connect to the gateway with the strongest signal (RSSI). These discovery messages include information about the channel used by the second radio and the time. Once the badge chooses a gateway it will switch to the channel which is unique to the gateway. This second radio will be used for all future communcation between the badge and the network.
==== MCP radio messages ====
The MCP instructs each geateway to send a packet every 5 seconds. This packet includes timing information telling the badges when they should communicate back to the gateway. The content of these messages is displayed in the MCP output:
<nowiki>
{"cid":"*", "duration_in_sec":5.2, "event":"add_transmit_window_to_all_connections", "num_queues":1, "origin":"DataQueue", "payload_len":4, "rid":45057, "time":"2014-09-24 19:46:52"}
{"cid":1, "duration_in_sec":5.2, "event":"add_transmit_window", "origin":"DataQueue", "time":"2014-09-24 19:46:52"}
b0010000000488e69316cbed2390e1f92ccd85016af2a55000b61abbf83a6ddf77fdb7b1c175803a163cb68a852fb5ddba9f6129329259fe581b
b0010000138800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
{"event":"pause_connection_for_duration", "origin":"MainChannelSender", "pause_until":1411588017.319312, "time":"2014-09-24 19:46:52"}
</nowiki>
The first 2 bytes of all radio messages indicate the message type, or RID. This is 'b001' for the packets above.
==== The first signs of communication with the badge ====
Once you have reached this far the badge network should be sending messages which will be picked up by the badge. Turn on badge, wait for a minute or two and then press up/down button to refresh the display. With any luck the "Welcome" at the top of the screen will be replaced with the current time and some status messages will appear at the bottom of the screen showing a randomly generated gateway ID and the radio signal strength.

=== Update public key in badge firmware ===
During one of the earlier steps we generated a random key for the radio messages in this badge network. The default badge firmware only trusts messages signed by the official EMF camp signing key which we don't have. To get any further we need to update the public key in the badge firmware to make it trust the messages from your new MCP.
cd ~/Mk2-Software/lib
make keys.c
This will output the information you need to add to the firmware source code:
<nowiki> # To make your badge trust messages signed by your
# new key pair you must replace the public key in
# EMF2014Config.h with:

const uint8_t EMF_PUBLIC_KEY[40] = {
... lots of hex numbers ...
};</nowiki>
Open the EMF2014Config.h from the Mk2-Firmware/EMD2014 sketch. Find and replace the EMF_PUBLIC_KEY with the one that was printed above. Open the arduino IDE, connect your badge to via USB, build & flash the new firmware.

=== Registering the badge on the network ===
After you have installed the firmware above the badge will reboot. Wait a few minutes and this time the badge should register itself to the network. The output on the gateway program should show it receiving messages from the badge, beginning "9002...". These messages are the badge requesting a badge ID from the MCP:
<nowiki>
2014-09-24 20:08:37,274 - UsbRadios - DEBUG - Packet send via radio 0: 26100
2014-09-24 20:08:42,274 - UsbRadios - DEBUG - Packet send via radio 0: 26200
2014-09-24 20:08:47,274 - UsbRadios - DEBUG - Packet send via radio 0: 26300
2014-09-24 20:08:50,303 - Gateway - DEBUG - Received packet with rssi -42: 0a
2014-09-24 20:08:52,273 - UsbRadios - DEBUG - Packet send via radio 0: 26400
2014-09-24 20:08:56,250 - Gateway - DEBUG - Received packet with rssi -42: 90020000203132503834353631343031333030360000000000000000000000000000000000000000000000000000000000000000000000000000
2014-09-24 20:08:58,274 - UsbRadios - DEBUG - Packet send via radio 0: 26500
2014-09-24 20:09:01,825 - Gateway - DEBUG - Received packet with rssi -42: 90020000203132503834353631343031333030360000000000000000000000000000000000000000000000000000000000000000000000000000
2014-09-24 20:09:03,274 - UsbRadios - DEBUG - Packet send via radio 0: 26600
</nowiki>
The MCP window should show it transmitting the signed response packets starting "b002..."
<nowiki>
b002000000268f1f16ee0a4f5fe7dcb4a69bacdc0f4038c87d368dc2527a26fe7f86a232e0804bf10645afe414a90d122d8241e200f464f2d7cf
b0022031325038343536313430313330303600010000000000000000000000000000000000000000000000000000000000000000000000000000
</nowiki>

If you now select the BadeID app on your TiLDA then it should now say that it has been assigned badge ID EMF0001.

=== Setting the name on your badge ===
Each badge has a unique hardware ID which was programned into the CPU by Atmel. This hardware ID is sent to the MCP when the badge asks it to assign a badge ID. This unique hardware ID ensures that you will get the same badge ID each time you reset the badge. The MCP store this in the 'badge' table in the database:
<nowiki>
pi@raspberrypi ~ $ psql schedule
psql (9.1.13)
Type "help" for help.

schedule=> select * from badge;
id | hwid | date | gwid
----+----------------------------------+------+------
1 | 20313250383435363134303133303036 | | 1
(1 row)
</nowiki>

The badgeID app mentions registering on a web page but we don't have this available. Instead you can add your name and nickname directly into the database and the MCP will tell your badge to display this name next time it registers. You can personalize the name and nickname however the LCD can only display strings of up to 10 characters. You can put spaces in the from to align the text that is displayed. The EMF0001 badge ID is the one that your badge should have obtained earlier.
<nowiki>
schedule=> INSERT INTO "user" VALUES ( 'My Name', 'Nickname', 'EMF0001' );
INSERT 0 1
schedule=> \q
</nowiki>
To make your badge learn this new name you must hit reset and wait for it to acquire its badge ID again, check this in the badge app. Now return to the home screen and hold the badge vertically, like it is hanging on a lanyard, with the two large holes in the PCB at the top. When the EMF logo appears your name should now be shown at the top of the screen.

== Using the badge network ==
=== Web interface ===
The MCP software runs a web interface and API on port 8888, point your web browser at:
<nowiki>http://RPi-IP-Address:8888/index.html</nowiki>

=== Notification messages ===
The badges and network have the ability to send a text message to a specific badge, or to all badges. The command below sends a message to all badges and this should appear on your badge after a few seconds delay:
cd ~/Mk2-Software/emfbroadcaster
./flashmsg.py "Hello from my DIY badge network"
Or a message to a specific badge number:
./dm.py 1 "message to badge one"

=== Weather ===
The <code>weather.py</code> script will send weather updates but you must register for a Met Office API key and place this in the <code>~/Mk2-Software/etc/secret_config.json</code> file.

=== Schedule ===
The <code>schedule.py</code> script broadcasts schedule update to the badge. This requires additional information to be added to an 'event' table in the database. There is currently no documentation on how to do this.

== Ideas and areas for improvement ==
* The badge notification messages include LED and sound fields to make the user aware of the alert but these are not implemented in badge firmware.
* The badge sends a packet on RID 9004 which indicates its battery status. Currently the MCP prints a message saying it received this but does nothing else with it. It might be interesting to log the battery information and RSSI into a file or database as an example of how to collect data from the badges.
* Enhance the EMFTris and Snake apps to tell the MCP about the highscores. Record in a log and create a web page showing the highscores for each badge.
* The current badge architecture was designed around the needs of a large distributed system. In an isolated network it would be nice to have a special mode which works with just a single radio. Or perhaps send the data to the badge via the USB serial so no radio is necessary at all.
* Add a voting app which broadcasts a question to all badges, shows the choices on the screen and uses a button to select. Send the response back to the MCP and display the results on a web page.
* The original Mk2-Software relies on a special radio firmware mode 'ATZD3' which indicates the end of paket boundary and RSSI. This firmware was specially made by Ciseco for EMFCamp and this feature is not present in the standard radios. The forked Mk2-Software has some tweaks to make it work with the standard firmware but this lacks the RSSI information and may not work with multiple badges. It might be possible to use one of the other radio debug modes (ATZD1 or ATZD2) which the public firmware supports to provide the same information as ATZD3.

Villages:Hax0rz of the Roses

2014-08-19T12:23:01Z

Drrk:

{{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
* Mendel90

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

Villages:Hax0rz of the Roses

2014-08-18T22:38:47Z

Drrk:

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

==Villagers==
{{inhabitant}}

==Robots==
* RoboButler 3000
* Mendel90

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

[[MapFix::51.968737,-0.792283~Hax0rs of the Roses~Northern Hackspaces~Hax0rs-logo.gif|51.968737,-0.79358~Hax0rs-logo.gif|AWESOME]]

Villages:Hax0rz of the Roses

2014-08-18T22:19:11Z

Drrk: Set logo, maybe?

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

==Villagers==
{{inhabitant}}

==Robots==
* RoboButler 3000
* Mendel90

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

[[MapFix::51.968737,-0.792283~Hax0rs-logo.gif|51.968737,-0.79358~Hax0rs-logo.gif|AWESOME]]

File:Village Hax0rz of the roses..gif

2014-08-18T22:03:50Z

Drrk:

Villages:Hax0rz of the Roses

2014-08-17T21:19:14Z

Drrk:

User:Drrk

2014-08-15T18:31:37Z

Drrk:

{{Attendee
|name=Kimball
|village=Hax0rz of the Roses
|Arrival=2014/08/27 22:00
|Departure=2014/09/01 18:00
|IRC=drrk
|teams=Badge
}}
Kimball Johnson

Villages:Amateur Radio

2014-08-06T20:18:18Z

Drrk: /* People */

{{Village
|Name=Amateur Radio
|Description=ham radio at it's finest.
|Contact=Paul
|Activities=Radio... durr
}}

Moved from [[radio]]

==Contests==
During EMF the following contests will be running

http://www.hornucopia.com/contestcal/contestdetails.php?ref=99

http://www.hornucopia.com/contestcal/contestdetails.php?ref=98

http://www.hornucopia.com/contestcal/contestdetails.php?ref=101

==Special Event Station==
Paul (M0OKE) has applied for an NoV for a special call sign for a special event station, GB2EMF. The question is whether enough people want to operate to keep the station going for the bulk of the weekend. It's unlikely that anybody wants to spend a significant proportion of their weekend running the special event station.

==Talk In==
Talk in has been suggested on 2/70 on Friday. Operator(s) required. Assuming 145.550 MHz.

==Modes & Bands==

Steve M0SPN intends to run Voice, PSK and SSTV on HF. VHF/UHF dependent on availability of masts and beams.

==Local Clubs==
Milton Keynes ARS (MKARS) are literally just up the road from the campsite

http://www.mkars.org.uk/

==Repeaters==
It would be very cool to have a dedicated on-site repeater just for EMF. The practicality wouldn't be too difficult -- M0RND can provide a 2m/70cm colinear (which might be able to be hosted on the main EMF mast), and there's no shortage of radios which can do cross-band repeat, or something could be lashed up with two Baofeng UV-B5 radios and a diplexer.

The awkward part would be getting an NoV for the repeater, and getting it in time for EMF.

===Voice===
GB3VA http://ukrepeater.net/my_repeater.php?id=997

===Digital===
Milton Keynes has its own repeaters, too. Coverage to be confirmed, but GB7BP looks promising, but is DIGITAL. So is probably not much use for us.

http://www.ukrepeater.net/repeaters/maps/gb7bp.jpg

http://www.ukrepeater.net/my_repeater.php?id=180

==Tasks/Status==

{| class="wikitable"
! Task
! Owner(s)
! Notes
|-
| Village/Station || tgreer? || Organisation of tent, power, network
|-
| Radios || (tbc) || Supply of HF/VHF/UHF gear1
|-
| Mast(s) || (tbc) || Supply of masts, rotator?2 * Tgreer has 12m push up mast on his landrover * Hopefully LHS's trailer mast will be ready for then. [https://wiki.london.hackspace.org.uk/view/Project:Mast_Trailer]
|-
| Operators || See below || People volunteering to rotate operation/manning of station
|-
| Special Event Call || Paul M0OKE || Request submitted
|-
| QSL Cards || Steve M0SPN || Assistance required 3
|-
| GB2RS News || (no owner) || Submit event summary to RSGB news
|-
| Southgate ARC || (no owner) || Submit event summary to SARC news
|-
| TX Factor || Steve M0SPN || Initial contact made (to be passed to jontyw if successful)
|-
| Promo Material || Steve M0SPN || Initial contact made with RSGB, Kenwood, Yaseu, Icom, Moonraker, ML&S
|}
1 Steve M0SPN has TS450S & PSU available

2 Cillian (possible V/UHF yagis), tgreer (possible landrover/mast)

3 http://www.centreprint.co.uk/qsl_cards2.htm can deliver in 1-2 weeks, £50 for 250 cards

==Equipment==
{| class="wikitable"
! style="text-align:left;"| Item
! Amount
! Status
|-
|Tent/Gazebo?
|1
|3x3m Ordered from Ebay
|-
|Table
|1
|Rental booked
|-
|Chairs
|6
|Rental booked
|-
|}

==People==
A list of people who may or may not be going and may or may not be interested in doing things related to amateur radio.

* David M0TNR `Cillian' (is going, can bring some radio goodies, but doesn't want to dedicate all weekend to it)
* Adam M0RND
* Colin G8TMV
* Paul M0OKE
* Jon M0JSN
* Gavan 2E0UND
* Steve M0SPN (TCMSLP on #emfcamp)
* Kai DB1SQU (SQUelcher on IRC)
* Kimball 2E1FWL (drrk on IRC)

==Villagers==
{{inhabitant}}

User:Drrk

2014-07-29T08:30:17Z

Drrk:

{{Attendee
|name=Kimball
|village=Hax0rz of the Roses
|Arrival=2014/08/27 22:00
|Departure=2014/09/01 10:00
|IRC=drrk
}}
Kimball Johnson

User:Drrk

2014-07-28T12:14:37Z

Drrk:

{{Attendee
|name=Kimball
|village=LBW
|Arrival=2014/08/27 22:00
|Departure=2014/09/01 10:00
|IRC=drrk
}}
Kimball Johnson

Volunteers

2014-04-16T12:24:20Z

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

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

{| class="wikitable"

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


|-
|
[[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]]
* Workshop Team, if I can convince JamesH form NottingHack to still do it with me, Organising of the workshop tents, before during and after. Includes worshop tents for people to hold workshops, and general hacking/making tents
* Buildup and teardown
|
* 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:Drrk

2014-01-14T01:09:46Z

Drrk: Created page with "Kimball Johnson"

Kimball Johnson

Volunteers

2014-01-14T01:09:24Z

Drrk: /* Don't put your name here unless you really mean it! */

== Don't put your name here unless you really mean it! ==

{| class="wikitable"

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


|-
|
[[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]]
* Workshop Team, if I can convince JamesH form NottingHack to still do it with me, Organising of the workshop tents, before during and after. Includes worshop tents for people to hold workshops, and general hacking/making tents
* Buildup and teardown
|
* 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
* 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



|-
|
[[User:bigcw|bigcw]]
|
B, B+E (aka trailers up to 3500kg)
|
* 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:leejhowe|Lee Howe]]
|
AM/B/f/k/q
|
* Will help with anything, would particularly like to get involved with sound, lighting and networking though.
* Help transport anything to the site (5dr Fiat Stilo, so quite a bit of room).
|
* Transport (Will be driving from London to EMF Site).
* Help with Sound, Lighting, and networking if required.
* Anything else I may be useful for.



|-
|
[[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
(7.5Tn limit) 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
|
* Buildup
* Badge Firmware
* Sysadmin
* AV/Radio
|
* Anything else


|}