University of Colorado Time
Systems
Lucas Buccafusca
Sean DesMarteau
Tanner Hannam
Jeff Lassen
Joshua Yang
Contents









Background
Project Scope
Hardware Approach
Software Approach
Hardware Components
Division of Labor
Schedule
Risks
Questions
BACKGROUND OF SWIM TIMING
 Prior to 1950 – Relied on the
sound of a starting pistol to
start races and mechanical
stopwatches to record their
times at the end of a race.
 Couldn’t record times
accurately beyond one-tenth
of a second.
CURRENT TIMING SYSTEM
 The invention of
automatic timing systems
brought more accuracy
and credibility to aquatic
sports.
 Measures with the
accuracy of 1/1000th of a
second
CURRENT TIMING SYSTEM
 Rules for high level meets
 Primary (automatic) timing system with start system
and touchpads that the swimmers touch
 Secondary (semi-automatic) timing system with start
system and 3 officials per swimmer pushing manual
pushbuttons.
 Tertiary (manual) timing system (stop watches)
CURRENT TIMING LAYOUT
 8 Inputs Per Lane
 3 Pushbuttons, 2 Touchpads, 1 Relay Judging
Platform, 2 Start Inputs (Speaker/LEDs on Start Block)
CURRENT TIMING LAYOUT
 2 Outputs Per Lane
 Start Information:
 Speaker Tone
 Flashing Light on RJP
 Strobe Light on Start
System
STANDARD 8 LANE SETUP
DOWNSIDES TO CURRENT SYSTEM
 While current system is satisfactory it provides
downsides.
 TOO MANY WIRES!!!!
 Very elaborate setup
 Wires/touchpads can be easily ruined by water/human
handling if not cared for properly
 Therefore an upgraded system is desired to combat
these downsides
Project Scope
Evolve from
 Wired Connections
 Precise timing relations through copper connections
 Need for conduits and elaborate setup
 To wireless input and output nodes
 Mesh network synchronized to 1 msec
 Easy setup
Objectives
 Create system of 80+ wireless nodes to account for all
inputs/outputs per lane for 10 lane pool
 Test for accuracy and reliability of system under
normal race/pool conditions
Data Stream Requirements





50ms max latency for timing events
3ms max latency for speedlight events
3ms max latency for speaker audio stream
1-5kByte/s continual stream to scoreboards
No lost packets allowed
Node Types





Button Nodes
Timer Node
Start System Node
Speaker Node
Scoreboard Node
Button (B,T,R) Nodes




Largest number of nodes in system
Represents Pushbutton, Touchpad, Relay Platform
All electrically identical
Measuring open/close of a circuit for race event
timing
 Eg. Swimmer hits touchpad and closes the circuit
Timer Node
 Collects all outputs from other nodes
 Maintains accurate time
 Synchronizes all nodes based on accurate time
Start System and Scoreboard Node
 Start System
 Used by meet official
 Contains microphone and button to relay voice and start
of race
 Scoreboard
 Receives race information, swimmer names, times, and
places
Power,
Battery
Scoreboard
Push Buttons
Touchpad
Speakers
Timing System
Start System
Light
Relay Judging
Platform
(RJP)
Input Devices
Touchpad
Start System
Relay Judging
Platform
Push Button
Output Devices
Lights and Strobe
Scoreboard
Power,
Battery
Touchpad
Push
Buttons
Master
Timer
Voltage
Regulator,
3.3V
Wireless
Mesh
Network
Device
Input
Signal
Start System Signal
Light
Start System Signal
Start
System
Speakers
Relay
Judging
Platform
(RJP)
Computer/
Scoreboard
Power
Signal
Power Efficiency
 Rechargable batteries to produce 3.3V
 For every device with Xbee (low power device)
 External devices (i.e computer) will have different
power source
Roles Responsibilities (1)
Roles and Responsibilities (2)
Use Cases
System Diagram for Button Nodes
System Diagram for Master Timer
System Diagram for Start Node
System Diagram for Scoreboard
Node
System Diagram for Speaker Node
Packaging Interface (out)
Packaging Interface (in)
HARDWARE: XBEE RADIO
 Xbee-PRO ZB Module
 Every node in the system
will consist of 1 radio.
 Will help create the
wireless network
 Low cost
HARDWARE: MICROCONTROLLER
 8-Bit Freescale
MC9S08Gxxx Family
 Each Xbee will consist of
a microcontroller telling
it what to do.
 In process of deciding on
most cost efficient and
effective microcontroller
HARDWARE: POWER SUPPLY
 3.3 Volt Supply
 Most likely Battery
Powered
 Rechargeable to save
cost over the span of life
 Should be able to be
easily replaced incase of
power failure
HARDWARE: WATERPROOF
ENCLOSURES
 Solely responsible for
keeping microcontroller
and Xbee waterproof
 Will be off the shelf
 Should be small and cost
effective
 Should be easily replaced
incase of breakage
HARDWARE LAYOUT
 Each node of the system
will consist of the
following




Microcontroller
Xbee Radio
Power Supply
Waterproof Enclosure
MICROCONTROLLER
WATERPROOF
ENCLOSURE
3.3 V
POWER
SUPPLY
XBEE PRO
RADIO
SAMPLE LAYOUT
RJP
PUSH
BUTTONS
LED
SPEAKER
TOUCHPADS
ROBUSTNESS
 Testing with strong interferers in pool environment
 Wi-Fi
 Bluetooth
 Each node must not exceed specific latencies
 All nodes synchronized to 1 msec accuracy for timing in
mesh network
 3 msec for voice and start signals
 50 msec for all other (timing) messages
Network Setup
 Network orientation will be a Wireless Mesh Network
(WMN)
 Properties of a WMN include:
 Ability to Self-form/Self-heal (meaning that as we add
nodes to the network, we are able to wirelessly seam
them together without trouble)
 Relatively stable topology
 Data can reach the final destination in a relatively fast
amount of time
Network Setup
 Will be functioning at
2.4GHz
 Allows for easy testing of
latency and robustness
Roles
• Power Specifications – Josh
– Design for efficiency on per node basis
• Network Setup – Lucas
– Implementation of Mesh Network
• Software – Jeff
– Coding for various use cases
• Hardware Design – Sean
– Functional and test circuitry needed for each node
• Testing Manager – Tanner
– Help design HW/SW for testing critical components
Schedule
 Plan is to follow the schedule designed by Tom Brown
for the year-long Capstone course
 In addition, try to meet deadlines set by Colorado
Time Systems
Schedule
 Preliminary Design Review – 09/5/2012: Confirm final ideas with Colorado
Time Systems, TAs and instructor
 Milestone 1 - Initial Requirements Specification – 09/25/2012: Present design
and construction plans of final prototype.
 PDR with Level 0 and 1 Functional Decomposition-10/16/12: Prepare and
present to TAs and instructor a detailed explanation of the PDR
 Milestone 2 – 11/13/2012: Demonstration of major hardware and software
components and subsystems critical to major functions.
 Proof-of-Concept Open Lab Symposium-12/13/12: Open demonstration to
TAs, instructors and peers
 Milestone 3- Critical Path Prototype Unit Tests -2/12/12: Test plan presented
to TAs and instructors
 Milestone 3 (continued)- Test Results and Analysis -2/19/12
 Milestone 4- I&T Sub-system and System Integrated Testing Refinement3/12/12
 Capstone Design Expo – 4/23/2012: Completed prototype with all necessary
materials and documentation presented to instructors, TAs, colligates, and
general public.
Budget
 Budget has been planned assuming money allocated
from UROP
 Colorado Time Systems will provide some of the preexisting hardware (Relay Pads, Speakers, etc.) to
help minimize costs
Budget Highlights
 Key costs:
 Microcontroller from the Freescale MC9S08Gxxx
family
 Radio Xbee Pro module
 PCB Design costs
Risks
 Testing
 Risk
 Complicated System (many nodes)
 Solution
 Start simple, then add nodes as needed
 Water
 Risk
 Water + Electronics = Device Failure
 Increased signal attenuation
 Solution
 Waterproof enclosures
 Increase transmit power, Mesh Networking
Open Risks
 Risks in Time Synchronization
 All nodes must be accurately synced to one time to
ensure accurate timing
 If distances between nodes are large enough, time
taken to transmit sync time could affect accuracy
 Possible Solution
 Prove that distance is not a factor in staying within
accuracy limitations
Questions?