Afa Malu
Bob VanLonkhuyzen
KJ Yoo
Nathan Snippe
Engr 339/340 Senior Design Project
Calvin College
12/09/2012
P a g e 2 o f 51
Executive Summary;
Übercaster is an innovative new personal broadcaster for those who want to broadcast their music, ideas,
or translations. By utilizing the range of Wi-Fi and the speed of UDP protocol, Übercaster shall be able to
broadcast any audio signal that plugs into it via a 3.5mm jack. It shall be able to provide a quick and high
quality connection to at least ten Smartphone clients. The Smartphone users shall be able to download the
free Übercaster app and stream the audio at a rate of up to 320kbps. We anticipate a delay in the stream of
at most a hundred milliseconds, which is barely noticeable by the human ear.
The market for Übercaster is focused on a few main groups: churches, museums, and street performers.
With these groups, we estimated about 10,000 buyers in our first year. With this number, we are still able
to provide a very affordable price of $170. By the start of the next calendar year, we hope to have a proof
of concept working on a development board and keep improving from there throughout the semester. By
May, our goal is to have designed and produced our own printed circuit board and enclosure at the
specifications we desire.
P a g e 3 o f 51
1. Introduction of Übercaster
1.1 Device Overview
1.2. Team Information
1.3.1.
Bob Vanlonkhuysen
1.3.2.
Afa Malu
1.3.3. KJ Yoo
1.3.4.
Nathan Snippe
1.3. Report Overview
2. System Architecture
2.1. Overall System
2.1.1. Block Diagram
2.2. Übercaster
2.2.1 Broadcaster
2.3. Client Mobile App
2.4. Admin Mobile App
3. Requirements
3.1. Functional Requirements
3.2. Electrical Requirements
3.3. Software Requirements
3.4. Physical Requirements
3.4.1. Product Weight
3.4.2. Product Size
3.4.3. Product Materials
3.4.4. Product Design
3.5. Power Requirements
4. Electrical System Specifications
4.1. Router
4.1.1. Processor
4.1.2. Bandwidth
4.2 Embedded System Software
4.2.1 IPhone & Android App
4.3 Display System
4.4 Printed Circuit Boards
4.4.1 Design Software Selection
5. Device Power
5.1 Power Supply Selection
6. Physical Design Specifications
6.1 System Enclosure
6.1.1 Case Design
6.1.2 Material Selection
7. Prototype and Year End Deliverables
8. System Integration Testing
8.1 Übercaster
8.2 Übercaster Client App
8.3 Übercaster Admin App
9. Business Plan
9.1 Vision and Mission Statement
9.2 Industry Profile and Overview
9.2.1 Competition
5
5
5
6
6
6
7
7
7
7
8
11
11
12
15
16
16
16
16
16
16
17
17
17
18
18
19
19
19
19
19
20
20
21
21
21
22
22
22
23
23
23
23
24
25
25
25
25
25
P a g e 4 o f 51
9.2.2 Limitations and Regulations
9.2.3 Trends in Society
9.2.4 The Cost to Entry
9.2.5 Necessities for Success
9.2.6 Projections for the Future
9.3 Business Strategy
9.3.1 SWOT Analysis
9.4 Marketing Strategy
9.4.1 Target Customers
9.4.1.1 Tour Guides
9.4.1.2 Large Venues
9.4.1.3 Street Musicians
9.4.2 Customer Benefits
9.4.3 Market Size
9.4.4 Logo Display
9.4.5 Pricing
9.4.6 Advertising
9.4.7 Production
9.4.8 Distribution
9.5 Financial Analysis
9.5.1 Forecasting
9.5.2 Key Assumptions
9.5.3 Financial Statements
9.5.4 Break-Even, Revenue, and Profit Analysis
10. Project Management
10.1 Team Organization
10.1.1 Division of Work
10.1.1.1 Bob
10.1.1.2 Nate
10.1.1.3 Afa
10.1.1.4 KJ
10.1.2 Team Advisors and Support
10.1.3 Team Meetings
10.1.4 Storing Files
10.2 Schedule
10.2.1 Schedule Management
10.2.2 Critical Path
10.2.3 Mid-Year Schedule Estimates
10.3 Operational Budget
11. Conclusions
11.1 Accomplishments
11.2 Lessons Learned
11.3 Credits and Acknowledgments
12. References
13. Partlist
26
26
26
26
26
26
26
27
27
27
27
27
27
27
28
28
28
28
28
28
29
29
29
31
31
31
31
31
32
32
32
32
32
33
33
33
33
35
36
36
36
37
37
39
41
P a g e 5 o f 51
1
Introduction to Übercaster
Have you ever been to a church service where translations are offered through the use of FM transmitters?
Even though these systems can be very effective, they are extremely expensive and bulkyi. Maybe you’ve
also been to a museum where the tour guide is barely audible due to ambient noise in the area. Using
Übercaster can solve these problems and more. Übercaster is a small, portable way to broadcast audio
signal for people to hear better and clearer. It works by taking any audio signal from a normal headphone
jack and broadcasting that signal over a Wi-Fi connection to any Smartphone users within range who
have downloaded the free Übercaster app. Imagine the convenience of going to a church service in a
different language and using your phone to receive a translation and getting meaning out of what the
pastor has to say. Or taking a tour at a museum and understanding everything the guide has to say about
your favorite piece of art.
1.1 Device Overview
Übercaster shall be a simple device with a design similar to Apple devices. This means having limited
buttons and knobs while still achieving its intended purpose; it shall be user friendly and recognizable.
The two components to the project are: a router that broadcasts audio and a Smartphone app (iPhone or
Android) to receive the broadcasted audio. Features such as the ability to choose the channel and volume
control shall be included in the app. The body of the device shall provide input jacks for a variety of
devices such as a microphone, guitar pick-up, or a connector for an iPod. The router is to be portable
which means it should easily be transported in a pocket or clipped to an individual. It must also survive
basic weather changes and therefore be waterproof. In case it should be dropped, it should also be able to
survive a 4-foot drop.
1.2 Team Information
Team Übercaster is composed of three senior electrical engineering students and one mechanical
engineering student (pictured below).
Figure 1.1: Übercaster team from left to right: Robert, Afa, KJ, Nate
P a g e 6 o f 51
1.2.1
Robert VanLonkhuyzen
VanLonkhuyzen is an Engineering student in the Electrical & Computer
concentration who is passionate about using engineering for missions. He is
looking forward to designing the hardware at the heart of Übercaster, and
expanding his knowledge of mobile operating system software. He is eager
to put to use the knowledge and experience he gained from both of his
previous internships: the research on mobile technology for the Christian
Reformed Church in North America, and his work with Radio Frequency
theory and circuit board layout at the HCJB Global Technology Center.
After graduation, VanLonkhuyzen shall be entering the Calvin Seminar,
pursuing a Master of Arts in Missions and Evangelism. His efforts on the Übercaster team shall focus on
designing the hardware and writing software for Apple’s mobile operating system.
1.2.2
Afa Malu
Malu is an Engineer with a Mechanical concentration and a Math minor and
is excited about being responsible for all mechanical aspects of Übercaster.
Even though there are no moving parts to Übercaster, he shall still have a lot
to bring to the table when it comes to material selection and circuit area
optimization. His understanding of electrical components comes from
producing office receptacles for Haworth Furniture during his internship at
Innotec located in Zeeland Michigan. Malu’s passion lies in design and
analysis of systems, especially in the automotive industry. He hopes to work
in the United States after graduation in order to further his knowledge, which
would eventually be beneficial for his native homeland, Nigeria. Being the
only mechanical engineer in the group, Malu’s efforts shall be focused mostly on the design of the
enclosure and optimization of the space within the device.
1.2.3
KJ Yoo
Yoo is an Engineering student with an Electrical & Computer concentration
and German minor. Yoo has a diverse interest in business, music, languages,
technology, and philosophy. He has lived in Stuttgart, Germany, Seoul, South
Korea, and Grand Rapids, Michigan. This past summer, Yoo developed a TV
scheduler using an Arduino and Google Calendar for Calvin Engineering
Department. He also has interned for Porsche Development Center in
Weissach, Germany and also at MoNET (The Laboratory of Molecular
Neuroimaging Technology) at Severance Hospital in Seoul, South Korea. He
enjoys playing piano, violin, and guitar in his free time and plays soccer
extensively. After graduation, he hopes to work in the U.S.
P a g e 7 o f 51
1.2.4
Nathan Snippe
Snippe is an Engineering student with an Electrical & Computer
concentration and a German minor. He is excited about tackling the
challenges of researching and designing the optimal hardware necessities of
Übercaster. Even though his passion lies with renewable energy, he is excited
about learning valuable specifics about hardware, which he hopes shall be
appearing in his future. After his internship with the United Nations Scientific
Committee on the Effects of Atomic Radiation in Vienna, Austria, he is ready
to use his learned skills of programming and group organization and
management to help turn Übercaster into a reality. After graduation, Nate
plans on working for a few years and possibly going to grad school for
renewable energy.
1.3
Report Overview
This report explains in detail the Übercaster system and what this product requires with respect to
electrical and power system specifications, physical design specifications, system testing, business and
marketing plan for product production, and project management.
Chapter 2 covers the system architecture of Übercaster giving a technical explanation of how the device
shall work. The product requirements in chapter 3 contain the customer-driven specifications with respect
to all aspects of the device. The electrical system section in chapter 4 contains the different subsystems in
detail including design decisions. The power section in chapter 5 explains the necessary power needed for
the device and where it shall come from. The physical design section in chapter 6 includes a description
of the enclosure, the type of materials, and estimate of the printed circuit board size and layout for
Übercaster. The system integration testing section in chapter 8 describes how the design of Übercaster is
evaluated compared to the goals we had previously set. The business plan section in chapter 9 includes
the team’s financial estimates for feasibility in starting a business around Übercaster. The project
management section in chapter 10 explains how the team’s division of work is based on individual
expertise, and how the organization has kept the team on track. The helpful advice given to the team by
faculty, staff, and mentors is also explained in this section.
2
System Architecture
2.1
Overall System
The system we are designing includes two distinct, but related modules: (a) the Übercaster, a physical
device that accepts an audio signal through an audio jack and outputs the signal over WiFi, and (b) the
Übercaster Client App and Übercaster Admin App, both mobile software applications that connect to the
WiFi signal. The client app accepts the audio stream, decodes it, and plays it to the user. The admin app is
used to change the settings of the Übercaster. Figure 2.1 shows the block diagram of our system’s
architecture. Figures 2.2 and 2.3 break down Übercaster and the Smartphone mobile app into their
respective system block diagrams, and Figure 2.4 details the system architecture of the admin app in a
block diagram. Table 2.1 describes the connections between the blocks in Figure 2.1. Table 2.2 describes
the same for Figure 2.2, and the same for Table 2.3 and Figure 2.3 and Table 2.4 and Figure 2.4.
P a g e 8 o f 51
2.1.1
Block Diagram Block Diagram
Figure 2.1: Top-level block diagram
Table 2.1: Signal identification for Figure 2.1
Signal Name
Voice
Analog audio in
Digital audio over WiFi
Analog audio out
Sound
Configuration
Connection Type
Audio
Copper wire
Wireless UDP packets on a
WiFi channel
Copper wire
Audio
UDP packets on a WiFi
channel
Number of Signals
2 (stereo)
2
1
2
2
1
P a g e 9 o f 51
Figure 2.2: Übercaster system block diagram
Table 2.2: Signal identification for Figure 2.2
Signal Name
Power Signal
Light Control
Analog Audio Signal
Digital audio
DA packet
Datagram
Audio Stream
DSP control
Internal storage control
Encoding control
Configuration
Store new settings
Update settings
Connection Type
Copper wire
Copper wire
Copper wire
Copper wire
Copper wire
Copper wire
Wireless UDP packets on a
WiFi channel
Copper wire
Copper wire
Copper wire
Wireless UDP packets on a
WiFi channel
Copper wire
Copper wire
Number of Signals
2
10
2
1
1
1
1
1
1
1
1
1
1
P a g e 10 o f 51
Figure 2.3: Smartphone and mobile app block diagram
Table 2.3: Signal identification for Figure 2.3
Signal Name
Audio Stream
Datagram
Stored Datagram
Bitrate setting
Digital audio
Amplified audio
Analog audio
Stream information
Connection Type
Wireless UDP packets on a
WiFi channel
Copper wire
Copper wire
Flash memory
Flash memory
Flash memory
Copper wire
Flash memory/Cache
Number of Signals
1
1
1
1
1
1
2
1
Figure 2.4: Admin app and smartphone block diagram
Table 2.4: Signal identification for Figure 2.4
Signal Name
Connection Type
Stored datagram
Copper wire
Datagram
Copper wire
Configuration
Wireless UDP packets on a
WiFi channel
Number of Signals
1
1
1
P a g e 11 o f 51
2.2 Übercaster
The Router shall receive an audio signal input via a microphone input jack, encode the data, and transmit
that signal over WiFi to other devices. Our device shall send live audio over the WiFi channel to up to 10
smartphones. For simplicity, our device shall be referred to as the Übercaster throughout this document.
2.2.1
Broadcaster
The Übercaster’s system shall operate in the following manner: an audio input such as a microphone, mp3
player, or electric guitar, can be connected to the Übercaster via a standard 3.5mm audio jack. The audio
signal shall be sent to a Digital Signal Processor that shall convert the analog voltages of the signal to a
digital representation of the audio, and perform any necessary corrections to the data, such as
amplification, automatically. The digital audio shall be stored for less than a microsecond in internal
memory, until a complete datagram is fully processed. This processed data shall be transferred to the
encoder, where it shall be encoded as an mp3 stream.
The stream shall be layered with a User Datagram Protocol transport layer, or UDP transport layer. UDP
maximizes latency by dispensing with complex protocol mechanisms such as handshaking and error
checking. UDP also does not require knowledge of the state of the receiver, nor does it retain any of the
transmitted data after it has been sent, making it very useful for large audiences of streaming media. The
UDP datagram consists of an eight-byte header, followed by the data it is transporting. The header is
divided into four parts: a two byte source port number, a two byte destination port number, a two byte
UDP packet length identifier, and a two byte UDP checksumiiiii.
The application layer of the stream shall use RTP, the Real-Time Transport Protocol. This protocol
describes and end-to-end delivery method for audio and video data, typically on top of a UDP transport
layer as we shall be using. Similarly to UDP, it does not ensure that the data is in fact delivered, nor does
it provide a way to check that data packets have arrived in-order. It does, however, provide a sequence
number for each packet so that the receiver can reconstruct the proper packet order of the packets are
received out of order.
The RTP fixed header contains 10 fields of varying bit-lengths. A representation of the header can be seen
in Figure 2.5 below. The first field is a two-bit version field, signifying what version of RTP is being
used. The second field is a single bit representing padding. If the bit is set, padding octets shall be added
to the end of the packet. The field labeled X is a single bit for enabling the RTP header extension. The
header extension follows immediately after the fixed header, and there can be only one extension. The CC
field is four bits in length and identifies how many CSRC identifiers shall be after the fixed header. The
single bit M field is the marker bit. It is used in association with a profile to mark boundaries. The PT
field represents payload type, and is 7 bits long. It indicates the format of the payload so the receiving
application can interpret it. The 16-bit sequence number field is used to specify an order to the RTP
packets. The first packet is assigned a random number, and each packet after is assigned an increment of
one from the previous packet. The timestamp field is 32 bits long. It represents the time the RTP packet
was first sampled. Like the sequence number, the timestamp begins with a random number and increases
based on the monotonic clock. The 32 bit SSRC field identifies the synchronization source. Finally, the
CSRC field is a set of 32 bit items, containing up to 15 items. These represent the sources of the payload
the packets are transporting.iv
P a g e 12 o f 51
Figure 2.5: Illustration of the RTP header
The data stream shall finally be transmitted over a WiFi channel. The connection is initiated when the
mobile app opens. It finds the correct source port that the Übercaster is using and receives the datagram
packets. The connection is terminated when the user either disconnects from the WiFi channel or
disconnects from the stream within the app.
2.3 Client Mobile App
The software we are creating shall run on smartphones using the Google Android operating system or
Apple iOS. The smartphone shall connect to the WiFi channel just as it would to any WiFi channel, as
shown in Figure 2.6. The difference is that the user shall not receive content from the World Wide Web,
but rather audio transmitted over the channel.
P a g e 13 o f 51
Figure 2.6: iPhone 5 connecting to the Übercaster WiFi channel
The user shall open up the Übercaster app and the app shall connect to the network stream automatically
on app initialization, using a predefined port. Figure 2.7 shows the screen the user sees during this
process. There shall be no need to worry about accidentally connecting to multiple streams at once if there
are several Übercasters in the vicinity, as each Übercaster broadcasts a different WiFi channel, with
unique SSIDs.
P a g e 14 o f 51
Figure 2.7: The main screen of the Übercaster client app, as it is connecting to the incoming stream
The app shall take the streaming digital audio datagrams that are being transmitted and decode them as
they are received. The app receives a UDP datagram and looks at the header. The packet length is read
and the data octets following the header are read and decoded. The checksum is optional, but to preserve
data integrity, a checksum shall be added to the header and the app shall handle checking the checksum
and performing error correction. If inclusion of a checksum becomes too time-consuming in the decoding
process and leads to longer buffering delays, investigation shall be made into eliminating the checksum.
The data octets following the header shall contain both audio data and mp3 tags such as artist info.
The app shall then play the audio to the user. The app shall also display some information to the user,
such as the time the user has been streaming, the bitrate of the stream, and a title for the stream. The title
and other information about the currently streaming audio shall be able to be edited using the Übercaster
admin app, as shall be discussed later.
P a g e 15 o f 51
The app shall also let the user interact with the stream, as shown in Figure 2.8. For example, the app shall
allow the user to choose the quality of the stream. If the user values higher quality, better sounding audio,
the user can set the bitrate to its maximum. If, though, the user puts a higher priority on responsiveness of
the stream, and wishes to reduce or eliminate buffering times, the user may set the stream’s bit-rate lower.
Figure 2.8: The bit-rate selection toggle of Übercaster client app
2.4 Admin Mobile App
Since the Übercaster has no user interface to configure settings such as making the device private or
public, or changing the bit rate of the broadcast. It shall be necessary to have an Admin Mobile app to
control the Übercaster. The app can connect with the device and configure the device through WiFi. The
admin shall be able to set mp3 tags to be sent along with the audio.
The process of configuration shall also use the UDP protocol. Following the header, the data octets shall
contain instructions that the Übercaster reads, decodes, and applies to the internally stored settings.
P a g e 16 o f 51
3
Requirements
3.1 Functional Requirements
In this section, the system as a whole is referred colloquially as the device.
REQ 3.1a: The device shall have a power on/off button.
REQ 3.1b: The device shall broadcast audio
REQ 3.1c: The device shall be able to last at least 4 hours of broadcast time
REQ 3.1d: The device shall be able to connect at least 10 clients
REQ 3.1e: The device shall have delay of no more than 100ms
REQ 3.1f: The device shall be waterproof.
3.2 Electrical Requirements
Hardware
REQ 3.2.1a: The device shall have a 3.5mm audio input and a power adapter plug.
REQ 3.2.1b: The device shall use WiFi communications and the content shall be sent via the Real-Time
Transport Protocol (RTP)
REQ 3.2.1c: The device shall be able to withstand a drop from 4ft.
REQ 3.2.1d: Total of 11 LED lights
REQ 3.2.1e: The device shall be able to endure temperatures ranging from -20oC to 60oC
3.3 Software Requirements
REQ 3.2.3a: The app that shall decode the RTP packets from the Übercaster.
REQ 3.2.3b: There shall be a separate Admin iPhone and Android app for the Übercaster.
REQ 3.2.3c: The app shall have a volume control and be able to choose a different channel.
REQ 3.2.3d: The device shall run a custom Linux distribution.
3.4 Physical Requirements
The physical design of Übercaster is to provide easy portability and durability for the user.
3.4.1
Product Weight
REQ 3.4.1: The device should weigh no more than 0.50 lbs.
The ideal device would eliminate any excess weight for greater portability comfort and safety. 0.50 lbs. is
low enough that minimal injuries would occur if dropped on a foot. 0.50 lbs. is high enough for the
combined weight of the interior components. A study conducted by Team 10 showed that 0.50 lbs. could
P a g e 17 o f 51
be comfortably carried for 4 hours. Having 20 individuals, 10 males and 10 females of varying age, Team
10 carried out the test where a cardboard that rendered to the liking of the device weighing 0.50lbs to be
carried around for 4 hours. After the 4 hours, they evaluated the comfort and overall feel of carrying the
device.
3.4.2
Product Size
REQ 3.4.2: The device should be easily portable (4.1in. by 2.4in. by 1.2in.)
The product size should be small enough to fit into a small backpack or carrying case.
It is important that Übercaster be portable for street performers who do a lot of moving around. The
device is recommended to have similar dimensions to an iPhone but thicker. Dimensions set are as
Height: 4.1 in. Width: 2.4 in, and Thickness: 1.2 in. The defined size requires that the layout and size of
interior components be minimized as much as possible.
3.4.3
Product Materials
REQ 3.4.3a: The device should be durable (refer to REQ 3.2.1c)
REQ 3.4.3b: The device should be water resistant (to rain not immersion)
REQ 3.4.3c: At least 70% of the device should be recyclable
REQ 3.4.3d: The device should be UV resistant
3.4.4
Product Design
Both the interior and exterior design of Übercaster was done in Solidworks.
All team members were responsible for designing what they thought Übercaster should look like. The
options were considered and the best one (potential component fit, and aesthetical appeal) was chosen.
The interior components were not fully determined (size and geometry) when the external design was
made. Solidworks rendering of the parts were made once they were determined. The parts were then laid
out to fit in the previous external enclosure designed.
REQ 3.4.4: There should be an even weight distribution.
It is important that there is even weight distribution within the device for comfort. The component layout
can be assembled to optimize the space available.
3.5 Power Requirements
REQ 3.5a: The device should last a minimum of 4 hours.
P a g e 18 o f 51
Übercaster is built to last a minimum of 4 hours. The longest activity projected is street performing. The
4-hour minimum would be sufficient for a performer who takes breaks and can charge the device during
that time.
REQ 3.5b: The device must have an in-built rechargeable battery and an attachable power cord.
REQ 3.5c: Übercaster should also be usable on battery only or when plugged in.
4
Electrical System Specifications
Previously, several different development boards were chosen. We started with the development boards
by Mini-Box and Olimex, but after not meeting the demands of the team’s CPU and WiFi performance,
and dimension, the Miniand’s Hackberry A10 development board was chosen. This board has a very fast
processor, the A10 System on a Chip (SoC) by Allwinner, it has a built in Audio input and it has a very
good WiFi module, which can transmit and receive up to 150Mbps. Our decision was based on Table 4. It
was obvious that Hackberry was the choice.
Table 4. Different Board Specifications
Board
CPU
Hackberry A10
1.2GHz Allwinner A10
ARM Cortex A8
Olimex Olinuxino A13
A13 Cortex A8 processor
at 1GHz,
pico-SAM9G45
ARM9, 400Mhz,
ARM926EJ-S, 32/32K
Audio input
3.5mm microphone jack
3.5mm microphone jack
NONE
Memory
DDR3 1GB, ~100MB is
reserved for the GPU
512 MB RAM
256MB DDR2
Boot
Boot from SD card and
internal storage via u-boot
NEMA 2-pin power
adapter included Input
AC100-240V-0.4A
50/60Hz Output DC5v
110 x 80 mm
Boot from Micro-SD card
Boot from Micro-SD card
6-16VDC input power
supply, noise immune
design
6-40V support via DC
barrel connector
120 x 120 mm
80x100mm
Power
Size
Power
Consumptio
n
Cost
With 3A Li-Ion Battery, it No Info Given
lasts 5 hours (drawing 500700ma)
No Info Given
$65
$69
$60.35
P a g e 19 o f 51
Figure 4.1: Architecture of Übercaster
4.1 Router
4.1.1
Processor
A10 Chip with an ARM A8 processor from a Taiwanese based company called Allwinner Technology
was chosen because of the low cost, high clock speed and low power consumption. The cost of $7 per
chip was especially enticing due to the unexpected high performance of the chip.
4.1.2
Bandwidth
The WiFi router has a transfer rating of 150Mbps. If the board encodes to audio into an MP3 format with
a 256kpbs bit rate, then it is theoretically possible to transfer stably to 586 clients. So we are very
confident it can service to at least 10 clients. We are also confident that we shall not have any issues
concerning the bandwidth.
4.2 Embedded System Software
For the Übercaster, a custom Linux OS distribution shall be used. Since Linux kernel is open source, this
allows the team to use only the necessary parts. For the Übercaster, Wifi and audio input ports are the
only necessary components. Typical operating system polls for display, keyboard, mouse, and other I/O
devices. By having a custom OS, we can expect to save power and have a better performing system,
because the CPU shall poll less devices. So using the Linux kernel 3.0.36, we shall custom design a
distribution
4.2.1
IPhone & Android App
The Übercaster app shall be available one the iPhone and Android market. The free app shall be able to
first discover the Übercasters nearby, then secure a connection with a particular one, and then stream the
audio signal.
P a g e 20 o f 51
4.3 Display System
The Übercaster device itself shall not have any display functions other than LEDs indicating whether or
not the device is broadcasting and how many users are connected to the device at that given moment.
However, there shall be two separate Smartphone apps for the device; one for the admin of the device and
one for the users who connect to the device to stream the audio.
4.4 Printed Circuit Boards
In Figure 4.2 shows the Olinuxino A10 PCB design. Since there is quite a bit of similarities between the
Olinxuino A10 and Hackberry A10, our team is in the process of a stripping down this PCB and also
adding additional components to minimize and optimize the function of the Übercaster. Key components
are the A10 system on a chip, the Realtek RTL8188CUS, 2GB NAND, 1GB Memory, AXP209 (Power
Management Unit), AP1231 (Low Dropout Regulator), and Si2305 P-Channel 1.25-W, 1.8-V (G-S)
MOSFET (Power MOSFET), 3.5mm Audio Input (GOGO_PJ-W47S-05D2-LF_5PIN).
Figure 4.2 PCB of the Olinuxino A10
P a g e 21 o f 51
4.4.1
Design Software Selection
EagleCad is a very popular tool to develop and design printed circuit board. Since the A10 Olinuxino was
developed using EagleCAD, it was somewhat easy to determine which design software was to be used.
Although EagleCAD is not very good at optimizing the board and costs money for the full suite, from
different PCB design software that was free such as ExpressPCB, EagleCad, SunStone, and DesignSpark,
we decided that since EagleCad was already familiar to the EEs and also the fact that A10 Olinuxino’s
PCB was done on EagleCad, we decided to use EagleCad.
5
Device Power
5.1 Power Supply Selection
A Lithium-Ion (LI) battery is to be used for the Übercaster. Two other battery types were considered:
Nickle-Metal Hydride (NiMH) and Nickle Cadmium (NiCd) battery. The criteria considered can be found
bellow in Table 5 for the LI batteries were its high Charge/discharge efficiency, its self-discharge rate, its
lack of maintenance, and non-hazardous disposal. The cons were its less desirable operating temperature
than NiMH, and its lower cycles. We decided that the pros outweighed the cons so went for the LI.
Table 5. Battery Comparisonv
Specific-Energy
Energy Density
Charge/discharge Efficiency
Energy/price
Self-Discharge rate per month
Cycles
Operating Temperature
Required Discharge
Disposal
LI-ion
100-265 W-h/kg
250-730 W-h/L
80-90%
2.5 W-h/$
18%
400-1200
from -20 to 60C
None
Non-hazardous
NiMH
60-120 W-h/kg
140-300 W-h/L
66%
2.75W-h/$
30%
500-1000
from -40 to 60C
every 60 - 90 days
Hazardous
NiCd
40-60W-h/kg
50-150 W-h/L
70-90%
20%
2000
from -20 to 60C
every 30 - 60 days
Hazardous
P a g e 22 o f 51
LI batteries are the most commonly used in portable electronic devices. The Dev Kit used for the
Übercaster recommended the use of a power input of 3.7V, which shall be handled by a rechargeable LI
battery. Using the recommendation, it was decided to use a rechargeable 1400mAh 3.7V LI-PO battery.
This battery has overcharge and short circuit protection, and has dimensions of 50x34x8mm, which is
small enough to fit into the Übercaster enclosure.
The Dev Kit used has a built in LI-PO charger that charges the battery to 100% once the battery is
detected. There is also a power jack that can be used. The kit accepts a voltage range of 9-30V and has a
DC/DC implemented that keeps the power consumption constant no matter what voltage is used. This
eliminates the need for a voltage regulator.
6
Physical Design Specifications
6.1 System Enclosure
The system enclosure shall be designed to be aesthetically pleasing and to meet the previously discussed
physical requirements.
6.1.1
Case Design
Übercaster’s visible features include a 3.5-mm jack for a microphone or other device (e.g. guitar), a
power switch, and a broadcast/connected indicator light. A CAD rendering of the device can be seen
below in Figure 6.
Figure 6: CAD Drawing of Übercaster
P a g e 23 o f 51
6.1.2
Material Selection
We decided that a plastic be used for the enclosure because of the combined durability, impact absorption,
and ease of molding most plastics have. The potential plastics considered for the production of Übercaster
were ABS (Acrylonitrile Butadiene Styrene), Noryl, and, High Density Polyethylene (HDPE). All three
materials met the physical requirements for Übercaster, but HDPE has a much lower Modulus of
elasticity (170,000psi) as opposed to ABS (320,000psi) and Noryl (350,000psi) so that option was
dropped. ABS is the cheapest option for a large volume. An 18X24 sheet of Noryl cost $90, an 18X24
sheet of ABS costs $80. Though the price difference between ABS and Noryl is not that much, ABS was
eventually chosen because of its availability.
ABS is the most widely used plastic in the production of enclosures. It is used for its strength and
toughness as well as its low water absorption, which is important for changing weather conditions. It is
also a recyclable material an important goal for being a good steward of this Earth. The drawback of ABS
is that it does not do well with UV exposure. To take care of UV rays, Übercaster shall be encased in an
aluminum
layer,
which
also
improves
the
aesthetic
of
the
device.
7
Prototype and Year End Deliverables
Over the course of the 2012-2013 school year, research and development was done by Team 10 on
Übercaster. By the end of the year, there shall be a functional device.
The device should be able to broadcast at least one audio signal to the Smartphone of at least 10 people
within a 100m range who download the accompanying app. There shall also be an enclosure made out of
ABS. Team 10 should be able to show evidence that they have adapted the Dev Kit bought to fit this
particular system. They shall also have a plan for further advancements of the product.
8
System Integration Testing
Because there are three discrete parts that work together closely, we must test both parts separately and in
conjunction to ensure that the entire system works as expected.
8.1
Übercaster
Testing the Übercaster shall allow us to ensure that the Übercaster is broadcasting a WiFi signal and able
to transmit audio over the WiFi channel. It should also recognize that a device is connected and properly
illuminate the correct number of indicator LEDs, as well as broadcasts over a radius of about 100 feet.
Testing shall begin with ensuring that the device turns on. If when the power switch is switched to “on”
the device shows indication that it is receiving power, such as lights turning on, then the first test has
passed. The next test shall determine if the Übercaster is emitting a WiFi signal. We shall test this by
connecting the mobile device to the WiFi channel. If the smartphone is able to find the WiFi channel, and
connect to it, the second test has passed. We shall then connect a laptop to the WiFi channel and use a
utility such as the WiFi Diagnostics utility in OSX to monitor the data being transmitted on the WiFi
channel. If we determine that the data on the channel is streaming audio, then this test has passed. We
shall connect a smartphone, with the mobile app installed, to the WiFi signal and start the app. We shall
P a g e 24 o f 51
then check the Übercaster to see if an additional LED indicator has illuminated. If it has, the test has
passed. Next, we shall bring the device to successively longer distances from the Übercaster, with nothing
in between the smartphone and the Übercaster, and monitor the audio being received on the mobile
device. We shall record the point at which the transmission is dropped, as well as the buffer time for the
audio stream. The first measurement shall give us the approximate maximum broadcast radius. We shall
need to test with several devices separately, one by one, and find an average, because some devices can
pick up WiFi channels from farther distances than others. The second measurement shall give us an idea
of the “fuzzy limit” of the broadcasting range. The range does not have a hard boarder, but rather a
general area where the connection becomes to intermitted to reliably transmit data, or to transmit data at
optimal speeds. Knowing the location of this fuzzy limit shall let us inform users of the optimal operating
range of the Übercaster. We shall then perform the same test again, but this time with obstacles between
the smartphone and the Übercaster. Again, we shall connect only one device at a time, but test with
several different devices. This test shall give us a separate “fuzzy limit,” one that gives us a worst case
limit. Finally, we shall connect several smartphones to the Übercaster at the same time, to test the load the
Übercaster can handle. We shall begin by connecting one device and time the delay the audio has from
the live audio input. We shall then connect additional devices, one at a time, and measure the audio delay
after each successive device connection. Once the delay becomes large enough that we believe it shall
adversely affect the listening experience, we shall have determined the recommended maximum number
of devices the Übercaster should be allowed to connect to. We have not yet decided on enforcing this
limit in documentation alone, or if it should be coded into the Übercaster itself.
8.2
Übercaster Client App
The mobile app shall be tested individually for several simple features. The app must be user friendly and
easy to understand. We shall ask if the subject is satisfied with the responsiveness to test the first
characteristic. For the second characteristic, we shall not tell the user how to operate the app, and see if
the user is able to understand and control the app without any instruction. If the user is able to use the app
without difficulty, the app is simple and understandable, and we have achieved our goal.
The app must also be tested with the Übercaster to determine if the stream can be received and played, if
the bitrate of the stream can be successfully changed, if the volume of the audio can be changed, and if
some information about the stream can be presented to the user. These properties shall be tested in the
following manner: we shall start the app on the mobile device, and turn on the Übercaster. We shall
connect the mobile device to the WiFi signal the Übercaster is transmitting, and run the app. If the app is
able to connect to the incoming stream, the first test has passed. If the app can also play the audio signal,
the second test has passed. We shall then navigate to the in-app settings and change the bitrate to be very
low. If the quality of the audio is noticeable degraded, the third test has passed. We shall then increase the
bitrate to its maximum and ensure that the audio quality responds accordingly. We shall then change the
volume in the app and listen for a corresponding change in volume of the received audio. If the volume
does change, the test has passed as well. We shall then note the information displayed on the main view.
If there is any information displayed, and if the information is correct, the last test has passed.
Finally, we shall test the app’s performance in the “fuzzy limit” region to ensure the app does not lock up
or crash if the connection is lost. We shall take the smartphone to the maximum range area we determined
P a g e 25 o f 51
before and purposely move outside of that region to loose the connection. If the app disconnects from the
signal and continues to function, letting the user change views and settings, the last test has passed.
8.3
Übercaster Admin App
Testing the admin app shall begin with connecting the smartphone to the Übercaster and opening the app.
If the app is able to connect to the Übercaster and display current settings, this test has passed. Next, we
shall try to change a setting in the app. If the Übercaster’s setting does change, the test has passed. To
know if the Übercaster has actually changed the setting, we shall use the Übercaster and client app to
check. For example, if we change the name of the stream title in the admin app, we shall know the title
has actually changed by using the client app to connect to the stream. The new title of the stream should
be displayed. If so, the test has passed.
9
Business Plan
9.1 Vision and Mission Statement
Übercaster’s vision is to create a product that is simple, distinctive, and reliable. The product should be
something that everyone can use and love. We want the users to be listeners as well as broadcasters. We
want to personalize broadcasting anywhere. We want to build a product that is efficient in terms of
production. We want to research and innovate our product further, so that it may perform better and drive
the price down. We want to implement the latest technology. We want dedication to our customers and to
innovation to be of great importance to our company. we want Übercaster to be an experience. We respect
greatly the designs of Dieter Rams and Jon Ives. Our design philosophy is not simplicity just for the sake
of simplicity, but functional simplicity.
9.2 Industry Profile and Overview
Broadcasting has always existed in the history of humankind. From shouting loudly to streaming videos
via YouTube, the modes of broadcasting have come a long way. It seems though these days; Internet is a
dominant force in our society. Uploading everything on the Internet seems to be the mode of choice for
broadcasting. Übercaster shall make broadcasting personal. Übercaster allows anyone to create a radio
station anywhere.
9.2.1
Competition
The close competitions to Übercaster are a company called LiveStream, Ustream, and Spreaker.
LiveStream broadcasts in Real-time HD videos to the Internet via WiFI, 3G, and the Ethernet. Ustream
and Spreaker are alike in the sense that it allows users to easily broadcast themselves using the Internet
with a Computer or an iPhone. Ustream and Spreaker are dependent on an Internet provider. Übercaster
doesn’t depend on any existing service provider. It is a wireless server and router itself.
P a g e 26 o f 51
9.2.2
Limitations and Regulations
Since Übercaster allows anyone to stream any audio signal, there is a chance that Übercaster might run
into problems concerning the issue of copyright. YouTube, Napster, and Kazaa had to shutdownvi or had
to pay reparationsvii for the copyright infringement to recording and media companies.
9.2.3
Trends in Society
The current trend in society is to have a product that is highly functional, but also looks beautiful. Apple
is a master of this. They have very innovative products that are intuitive, beautiful, and powerful. Sharing
one’s individuality seems to be more prominent more than ever through YouTube, Facebook, Kickstarter.
Now anyone can broadcast his or her individuality without the dependence of an infrastructure.
9.2.4
The Cost of Entry
We will invest $100,000 in capital and we will borrow $50,000 from the bank. We will also need $1.7
million dollars to cover our costs in our initial year. So a total cost of $1.85 million is needed. We will try
to seek venture capitalist funding for this. We talked with Rick DeVos personally and he is very much
interested in using Übercaster for ArtPrize. He said, “I really dig this idea. Sounds like a very cool
project. Let me know if it gets any further, are looking to turn it into a business.”
9.2.5
Necessities for Success
Our company is relying on the fact that people want to personally broadcast information and that the
smartphone sales increases more and more. Organizations such as churches and museums must be willing
to try a different way of broadcasting than FM transmitters.
9.2.6
Projections for the Future
Our company plans to further improve the initial design. Since our product is a niche market, it would be
economically more beneficial to go international initially. We want to implement the newer WiFi module
that uses the 802.11ac protocol. We want to have a chat function so that clients can chat with each other.
9.3 Business Strategy
9.3.1
SWOT Analysis
Strength: Unique. There are products with the similar philosophy to change the way people broadcast,
but our method is unique in the sense that it is service provider independent. Übercaster is focused on the
near field range, not the world.
Weakness: no capital, relatively low tech. The technologies that are used in the Übercaster is low tech.
The Übercaster can be built relatively easily.
Opportunities: Work with World Federation of Tour Guides Association and The Busking Project to
promote the use of Übercaster. Partner with manufacturing companies in China.
P a g e 27 o f 51
Threats: Large designers implement our function in smartphones. China develops a lower cost version of
our product.
9.4 Marketing Strategy
9.4.1
Target Customers
From our market research, we have determined there is a large potential for customers in Tour guide
systems for museums, streaming live music at music venues, translations or audio enhancements for
churches, and live music streaming for street musicians to receive a larger audience. These are the
markets we shall mainly focus on but there are others that shall benefit from our product as well.
9.4.1.1 Tour Guide
Übercaster can be used in loud and quiet places, which allows for a wider variety of applications for tours.
Tours can be given in quiet museums or in city streets with loud ambient noise.
Some tour guides use FM transmitters and receivers to handle the situation. However, this can cost
anywhere from $2,000 to $6,000viii and not only is the broadcaster usually large and bulky, these systems
require a receiver and headphones for each person in the tour.
Übercaster’s goal is to have one device that transmits and audiences can use their smartphone to listen in.
Tourists can stream the content directly to their smartphone whether it is live or recorded.
9.4.1.2 Large Venues
For large audiences, we are developing a larger scale version of Übercaster that shall allow several
hundred listeners to connect and stream the audio live. This shall mainly be for large concerts in which
people want to hear the musicians without ambient noise.
9.4.1.3 Street Musicians
Street musicians can simply plug their instruments into Übercaster and broadcast their sound to an
audience within a 100 ft. radius to shoppers or bystanders who want to hear without ambient noise.
9.4.2
Customer Benefits
In general, customers benefit from the following: saves cost by using less hardware than previously used
and broadcasts becomes more personal. Übercaster allows for social broadcasting. In the future, we will
include features like chat and website function built into the Übercaster.
9.4.3
Market Size
There are 17,500 museumsix in the U.S, thousands of street musicians, and 95,000 churchesx in the U.S as
well. We contacted TheBuskingProject.com to ask about the approximate numbers of street musicians in
the U.S. We got a message back saying that the number of total street musicians is unknown. From the
P a g e 28 o f 51
email I received from Nick Broad, who is the founder of The Busking Project, he said that his website has
4000 registered street musicians around the world. There are approximately 200,000 individual tour
guides across 70 different countriesxi. We imposed a hypothetical question to both The Busking Project
and the World Federation of Tour Guides Association by asking for their estimation of people who would
be interested in this product. Busking Project said about 2000 and from the 200,000 individual tour guides
from their database, they expected at least 8000 would be interested in using our device.
9.4.4
Logo display
Each team member designed their own logo and out of each, one shall be chosen for use for each of our
implementations of Übercaster including the main screen on the app.
9.4.5
Pricing
Based on our estimates from the market size, initially we plan to sell 10,000 units. In order to break even,
we need to sell at a price point of $170. The calculation of the price can be found in the financial
statement section.
9.4.6
Advertising
Our company shall use Google AdWords to set up campaigns. By using keywords such as “Wireless
audio transmitter” or “personal broadcaster,” we can reach on a monthly average basis of 1.3 million
users. We shall use Amazon.com to advertise and distribute our product as well. We shall ask bloggers
and tech writers to do a story and review of Übercaster such as on TechCrunch, The Next Web, and
Gizmodo. Informally we shall an AMA on Reddit and start a KickStarter campaigns. We shall have
promotional events where we distribute about 30 to selected street musicians and popular museums to be
tested and reviewed.
9.4.7
Production
For the first three years, we will make use of Chinese manufactures to supply components and produce
the device. With our profit and additional investments, we will invest in building our production facility.
9.4.8
Distribution
Initially, we shall develop our website for $10,000 and have features such as a sleek and clean user
interface, PayPal integration to sell our product. We shall then drop ship our product with our partnering
manufacturer. We shall also sell our products at Amazon.com. Amazon shall keep 10% of the purchasing
cost.
9.5 Financial Analysis
9.5.1
Forecasting
P a g e 29 o f 51
The United States economy is still recovering from the recession. As a result, early adopters and investors
are hesitant to take up new products for fear of losing valuable capital. By the time Übercaster is ready to
roll out the first product, however, the market conditions shall be better and more favorable to new
products and ideas.
9.5.2
Key Assumptions
We are assuming that we sell at least 10,000 units in the first year based on our market size study. We
assumed that we would have a steady annual growth of 20%, which is a typical growth rate for a small
company in the initial years. We are also assuming that our revenue is constant throughout each month.
We will base our fixed and variable costs on producing 10,000 units. We are assuming that we will have
the minimum capital to start our business. $100,000 shall be needed for capital investment with additional
$50,000 loan from the bank in our 1st year.
9.5.3
Financial Statement
Übercaster
Pro-Forma Statement of Income
Year 1
Year 2
Year 3
Sales revenue
Variable Cost of Goods Sold
Fixed Cost of Goods Sold
Depreciation
Gross Margin
Variable Operating Costs
Fixed Operating Costs
Operating Income
Interest Expense
Income Before Tax
Income tax (40%)
Net Income After Tax
Beginning Cash Balance
Net Income After Tax
Depreciation expense
Invested Capital (Equity)
Increase (decrease) in borrowed
funds
Equipment Purchases
Ending Cash Balance
1,700,000
856,000
629,500
214,500
25,000
200,000
(10,500)
3,750
(14,250)
(5,700)
(8,550)
2,040,000
2,448,000
1,027,200
1,232,640
755,400
906,480
257,400
308,880
30,000
36,000
240,000
288,000
(12,600)
(15,120)
7,500
7,500
(20,100)
(22,620)
(8,040)
(9,048)
(12,060)
(13,572)
Übercaster
Pro-Forma Statement of Cash Flows
Year 1
Year 2
Year 3
(8,550)
100,000
141,450
(12,060)
24,300
153,690
(13,572)
43,560
50,000
141,450
153,690
183,678
P a g e 30 o f 51
Variable Costsxii:
Labor
$2,500
Prototyping
$1,500
Consulting
$20,000
RLC components
$56,000
Chips and Modules
$150,000
Enclosure
$280,000
Li-Ion Battery
$225,000
Assembly and Fab
Shipping Cost
Product Packaging
$70,000
$124,000
$50,000
Advertising
$100,000
Promotional Events
$100,000
Total
$1,196,000
Fixed Costs:
IT Infrastructure
Insurance
Website
Total
$10,000
$5,000
$10,000xiii
$25,000
Overheadxiv:
Sales Personnel
$52,000
Management
$90,000
P a g e 31 o f 51
Attorneys and Legal
$80,000
Accountants and Financial
$65,000
Engineering
$65,000
Research and Development
$20,000
Public Relations Representative
$48,000
Fringe Benefits to cover retirement plans and full
health insurance for 10 employees
$59,000
Total
$479,000
$1,700,000
Grand Total
9.5.4
Break-Even, Revenue, and Profit Analysis
If we are able to sell 10,000 units at $170 then our revenue shall be $1,700,000 in our initial year, which
means shall break even, and be able to gain profit in the following years. If we grow at the assumed rate,
then our cash balance will increase 8% in the first year and then 19% in the 2nd year.
10 Project Management
Project management is arguably the most important aspect of our team. A lack in management creates a
lack in communication which leads to slow progress. Our team strives to overcome this struggle and
accomplish our work thoroughly in an efficient manner.
10.1 Team Organization
We have structured our work into a schedule and set up means of communication with each other in order
to evenly organize the workload amongst the team. Organizing the team means setting the workload to be
consistent and smooth. To do this, each team member has been assigned responsibilities corresponding to
their
strengths.
10.1.1 Division of Work
10.1.1.1 Bob
Because of his experience in iPhone app development, Bob has taken on the client and admin aspects of
the smart phone applications on the software side of Übercaster. He has also had experience in designing
PCB boards in a past internship, which shall help in designing our PCB board with the components tested
P a g e 32 o f 51
with
the
development
boards.
10.1.1.2 Nate
Nate has taken on the role of project manager. Having this role means assigning tasks, planning the
meeting times, and making sure each team member keeps the others accountable for getting their tasks
finished. Aside for manager, Nate plans to work with the development boards in order to examine the
optimal components for designing the PCB. Where there is time, Nate also plans on helping with the
programming for the Android and iPhone applications.
10.1.1.3 Afa
Since he is the only Mechanical Engineer, Afa has been assigned all the mechanical aspects of
Übercaster. He shall be designing the enclosure for the PCB which includes finding the best materials to
use and optimizing the space within the device. Afa is also in charge of the power management and try to
minimize its power consumption and allow a decent battery life.
10.1.1.4 KJ
KJ has been assigned the concept developer which means making sure Übercaster will actually work. He
works with the embedded software and hardware of Übercaster. He also is in charge of the network
protocol making sure the WiFi network can be created and that audio can be broadcasted. He is the team’s
researcher for finding the best development boards to accomplish our goal and understanding how the
transmission from client to host shall work with Übercaster. KJ also manages the budget and is in charge
of analyzing our business and market capabilities. \
10.1.2
Team Advisors and Support
The team’s primary advisor is Professor VanderLeest from Calvin College's Engineering Department.
Also in the College’s Engineering Department is Professor Kim who has helped a great deal with
showing us the steps we should take for making a proof of concept and moving on from there. Prof. Kim
has also sponsored us by providing one of our development boards for testing the proof of concept.
Professor Medema from the Business Department teaches the concurrent Business Aspects for Engineers
course and has helped a great deal with our business plan. Bob DeKraker, the Department Lab Manager
has helped us order the parts we need. We anticipate help from Chuck Holwerda helping us with our PCB
design and fabrication.
10.1.3 Team Meetings
The team meets regularly on Tuesday afternoons to anticipate upcoming deadlines and to make sure
everyone is on track with their assignments. We make an effort to help each other when we are
overloaded with assignments and take on more responsibilities if we finish our assigned tasks.
P a g e 33 o f 51
10.1.4
Storing Files
In order to keep our assignments and files organized, we set up a Dropbox folder, which acts as a normal
folder on each of our individual computers but all files in that folder is shared with the other teammates.
We also use Google drive to cooperatively write and share documents and block diagrams. Our Dropbox
folder is divided into sub-folders for hardware, software, mechanical, business, and anything that is
important and large enough that needs organization.
10.2 Schedule
Early in the project we created a Work Breakdown Schedule (WBS) in which we planned the tasks for the
whole year deciding what needed to be done and when it should be completed. It can be downloaded and
viewed herexv We assigned these tasks to members of the team and estimated times for them to be
finished. An example of our Gantt Chart can be found below (Figure 10.1) which displays major tasks in
such a way that make the design process consistent and smooth.
Figure 10.1: Example of the Gantt chart for our project.
10.2.1 Schedule Management
Nate has utilized the website https://trello.com as a management tool. It helps visualize the tasks that need
to be completed and gives a way to communicate with the team members so that each member knows
what still needs to be done. An example of this website can be seen in Figure 10.2. Every week, Nate
reminds the team what needs to be completed and makes sure everyone does his or her part. The schedule
is important to maintain in order to stay on track with design. We must also stay on schedule to take into
account
any
unforeseen
setbacks
and
be
able
to
adjust
for
them.
10.2.2 Critical Path
With our project, we desire to take a path which highlights efficiency. Since some areas of the design
process need to be finished before others, there is a necessary sequencing of events. For example,
P a g e 34 o f 51
designing the PCB requires a significant amount of time (deciding components, developing the board
layout, ordering the parts). To account for that, we must first order development boards with all the
necessary components to create a proof-of-concept. This shall help create a better understanding of the
necessary components for the PCB by being able to test how our software shall perform on the device.
From there, we shall be to design the PCB and create and enclosure. We anticipate unexpected deviations
from our plan which shall prevent us from making our later version of Übercaster (Figure 10.4) but our
goal is to build and test our created design by Senior Design night. Figure 10.3 below shows these major
tasks and when we expect to be finished with them.
Figure 10.2: Example of how we utilize trello.com
Task
Buy Dev. Board
Make Proof-Of-Concept
Design PCB
Create Enclosure
Build
Test
Assigned
Data
1-Nov
31-Dec
15-Mar
1-Apr
Apr-31
5-May
Figure 10.3: Expected critical path.
P a g e 35 o f 51
Übercaster v0.1
Have Dev. Board be able to:
- Broadcast WiFi network
- Play MP3
- Play back audio from mic
- Broadcast audio on network
Have Linux Machine be able to:
- Connect to network
- Stream audio from network.
Übercaster v1.0
Include v0.1 and:
- Make enclosure for dev. Board
- have the board battery powered
- Have updated Smartphone apps.
Übercaster v2.0
Include v1.0 but:
- Have designed PCB
- Have enclosure for PCB
- Have desired functionality
Have Smartphones be able to:
- Download our app.
- Connect to network
- Stream audio from network.
Figure 10.4: Desired versions of Übercaster to be achieved by end of year.
10.2.3
Mid-Year Schedule Estimates
By the end of the calendar year, the team expects to have a working proof of concept (v0.1 from Figure
10.4) using a development board. Figure 10.5 and 10.6 shows the working proof of concept. The
MacBook Pro is connected to the Übercaster and Übercaster is streaming to the MacBook Pro. We shall
have the ability to broadcast an audio signal and pick it up on a Smartphone. We also hope to have a good
understanding of the market for Übercaster and the potential of going into a business and producing
Übercaster at large quantities.
Figure 10.5 Pre-Recorded Audio Input (Approx. 50ms latency)
P a g e 36 o f 51
Figure 10.6 Live Audio Input
10.3 Operational Budget
KJ Yoo manages the budget for the team. We requested $450 to produce Übercaster. So far, we have
spent $191.89 on the development board and accessories for it to help along the proof of concept. Next
semester, we anticipate a large amount going towards the PCB and the components that go on it.
Batteries and Charger
Mini-Box Dev Board
Power Adapter
Touch Screen
Audio Sound Card
WIFI Dongle
Rectangular Header 10x2
Total Used
Remaining
$36.31
$69
$9.95
$35.5
$9.49
$29
$2.64
$191.89
$258.11
11 Conclusions
11.1 Accomplishments
We have accomplished much during the first semester. We have run two prospective operating
systems on a development board and connected several external devices to the board, such as a keyboard,
flash drive, and WiFi dongle.
P a g e 37 o f 51
We have also chosen a proper enclosure for the Übercaster. The enclosure shall be made of ABS
(Acrylonitrile Butadiene Styrene), which meets all of our requirements, except for UV exposure. Because
of this, the enclosure shall be covered in a layer of aluminum.
We also have the framework and basic structure of the iPhone app completed. The view switching is
complete and buttons and images for the final version are in place. We have started work on
implementing the code for streaming the audio data, but this is not yet finished.
11.2 Lessons Learned
This project has taught us many lessons about ourselves, and each other. We have learned how to work as
a team, and have a better understanding of each other’s strengths and weaknesses. We also have learned
that communication is essential for our group to succeed. When we do not communicate, we become very
disorganized and lost in our focus.
We also learned about how we interact with each other. We have different personalities, and tend toward
certain ideas and beliefs of the scope, the direction, and the individual tasks of the project. We have
learned how to cooperate and compromise on different aspects of the project, and how to better listen to
each other and give feedback.
Our biggest lesson learned is that staying on track with the schedule and keeping each other accountable
for their work is very important. We have fallen behind with poor team management. Recently, Nate has
volunteered to take a more direct role as the manager for the team. What he plans to do has been
mentioned in the sections above.
11.3 Credits and Acknowledgments
Team 10 would like to thank the following people for their contribution to the success of this design
project.
•
Professor Steven VanderLeest of Calvin College Engineering Department for his professionalism
and commitment to support the team as an advisor.
•
Professor Yoon Kim of Calvin College Engineering Department for donating parts for
experimenting and for providing insight into the scope of the project.
•
Professor Ned Nielsen of Calvin College Engineering Department for his contribution in
developing production options and cost analysis.
•
Glenn Remelts of Hekman Library for his assistance in research.
•
Phil Jasperse for his metalwork class.
•
Bob DeKraker for placing orders for all senior design teams.
P a g e 38 o f 51
•
Our Interns from the Business Department of Calvin College who did market research and talked
to local museums, churches, and performers.
•
To Team 03 from class of 2012 for their model of writing a PPFS
P a g e 39 o f 51
References
http://www.machinist-materials.com/comparison_table_for_plastics.htm
http://www.machinist-materials.com/comparison_table_for_plastics.htm
https://www.olimex.com/Products/Duino/Duinomite/_resources/DuinoMite-UM-1-03.pdf
http://rxwen.blogspot.com/2011/10/stream-audio-via-udp-on-android.html
http://en.wikipedia.org/wiki/Streaming_media
http://en.wikipedia.org/wiki/Multicast
http://jas-hacks.blogspot.com/2012/09/hackberry-wireless-access-point.html
http://ubuntuforums.org/showthread.php?t=1127000
http://ubuntuforums.org/archive/index.php/t-1544946.html
http://www.patheticcomputing.com/?p=134
http://sonnati.wordpress.com/2011/08/30/ffmpeg-%E2%80%93-the-swiss-army-knife-of-internetstreaming-%E2%80%93-part-iv/
https://www.virag.si/2012/11/streaming-live-webm-video-with-ffmpeg/
http://superuser.com/questions/53957/what-do-alsa-devices-like-hw0-0-mean-how-do-i-figure-out-whichto-use
http://ffmpeg.org/trac/ffmpeg/wiki/StreamingGuide
http://stackoverflow.com/questions/14150365/how-to-send-receive-rtp-audio-stream-c
http://www.alsa-project.org/main/index.php/FramesPeriods
http://www.cs.odu.edu/~cs778/jmflects/lect8RTPPresenting.html
i
http://www.centrumsound.com/digi-wave_tour_guide_system.html
Parker, Don. "Understanding the UDP Protocol." Windows Networking. N.p., 11 Aug. 2005. Web. 22
Jan. 2013. <http://www.windowsnetworking.com/articles-tutorials/network-protocols/UnderstandingUDP-Protocol.html>.
ii
iii
Postel, J., "User Datagram Protocol," USC/Information Sciences Institute, RFC 768, January 1980.
iv
Schulzrinne, H.; Casner, S.; Frederick, R.; Jacobson, V.; “RTP: A Transport Protocol for Real-Time
Applications.” Network Working Group. 2003. http://ietfreport.isoc.org/rfc/fyi/PDF/rfc-pdf/rfcpdf/std64.pdf
v
https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A10-OLinuXino
http://batteryuniversity.com/learn/article/whats_the_best_battery
http://www.energizer.com/learning-center/Pages/battery-comparison.aspx
http://www.diffen.com/difference/Li-ion_vs_NiCad
http://en.wikipedia.org/wiki/Lithium-ion_battery
http://en.wikipedia.org/wiki/Nickel%E2%80%93metal_hydride_battery
http://en.wikipedia.org/wiki/Nickel%E2%80%93cadmium_battery
vi
http://www.pcworld.com/article/91144/article.html
http://www.techdirt.com/articles/20090519/1127454934.shtml
viii
http://www.centrumsound.com/digi-wave_tour_guide_system.html
ix
"WebCite Query Result." WebCite Query Result. American Association of Musueums, 10 July 2012.
Web. 01 Dec. 2012. <http://www.webcitation.org/693Qzdy15>.
x
"Oddity Software - Databases, Development and Design." U.S. Churches Database. Oddity Software,
n.d. Web. 01 Dec. 2012. <http://www.odditysoftware.com/page-datasales38.htm>.
xi
http://wftga.org/who-we-are/what-wftga
vii
P a g e 40 o f 51
xii
Labor Cost = 100 people * 5 hours spent* $5 per hour = $2,500
(http://economix.blogs.nytimes.com/2012/02/24/the-ieconomy-how-much-do-foxconn-workers-make/).
We estimated that for fast final assembly of the PCB inside the enclosure as well as software inspection
testing and hardware quality control as well as packaging the product and shipping it. We estimated that it
would take around 100 people around 5 hours to assemble 10,000 units of the device provided the knowhow and materials. We are thinking of collaborating with Foxconn in China.
Prototyping Cost = 5 custom designs @ $300
Consulting = consulting 200 hours at $100/hr to enhance design and cost
Enclosure = $28.00 *10,000 (we got a quick and dirty quote from fibox.com)
Assembly and Fabrication of Device = $70,000 with 5 weeks of lead time
(http://www.pcbassemblyexpress.com/index.php#assembly)
Component cost estimates = $56,000
Chips and Modules = $7 for A10 chip + $8 for Realtek Wifi Module *10,000
Li-ion battery Cost = $22.50 *10,000 (http://www.seeedstudio.com/depot/lithium-ion-polymer-batterypack-6a-p-602.html?cPath=178_183)
Shipping Cost = $12.50 * 10,000 (http://www.cypressindustries.com/faq_freight.html)
Product Packaging = $5 * 10,000 (got a rough quote from proactivepkg (http://bit.ly/SIURXs))
Advertising = Google AdWords and Featured Ads on Google.
Promotion = Branding, Social outreach, graphic and media designers to make promotional videos.
xiii
Estimated cost of annual website maintenance, security and design update. We don’t want to have
security failures. Websites are one of the most recurring costs for a small business that is growing.
xiv
These values are the national average for the occupation estimated through http://www.salary.com/
P a g e 41 o f 51
Partlist
Exported from Ubercaster_A10.sch at 1/28/13 10:27 AM
EAGLE Version 6.4.0 Copyright (c) 1988-2013 CadSoft
Assembly variant:
Part
Value
Device
Package
Library
Sheet
+5V
TESTPADTESTPAD_40-ROUND
TESTPADTESTPAD_40-ROUND
TESTPAD_40-ROUND
gogo
1
+5V_SATA_PWR WF2S
CON2PV2-2.54MM
CON2.54MM-2-0
DOUBLE-SIDE
1
1.2V_CPU TESTPADTESTPAD_40-ROUND
TESTPADTESTPAD_40-ROUND
TESTPAD_40-ROUND
gogo
1
1.2V_INT TESTPADTESTPAD_40-ROUND
TESTPADTESTPAD_40-ROUND
TESTPAD_40-ROUND
gogo
1
1.5V
TESTPADTESTPAD_40-ROUND
TESTPADTESTPAD_40-ROUND
TESTPAD_40-ROUND
gogo
1
1.5V_E
Close
SJSJ_1_SMALLER_CLOSE
SJ_1_SMALLER_CLOSE jumper
1
2.5V.
TESTPADTESTPAD_40-ROUND
TESTPADTESTPAD_40-ROUND
TESTPAD_40-ROUND
gogo
1
3.0VA
TESTPADTESTPAD_40-ROUND
TESTPADTESTPAD_40-ROUND
TESTPAD_40-ROUND
gogo
1
3.3V
TESTPADTESTPAD_40-ROUND
TESTPADTESTPAD_40-ROUND
TESTPAD_40-ROUND
gogo
1
3.3V_E
Close
SJSJ_1_SMALLER_CLOSE
SJ_1_SMALLER_CLOSE jumper
1
5VEXT
TESTPADTESTPAD_40-ROUND
TESTPADTESTPAD_40-ROUND
TESTPAD_40-ROUND
gogo
1
5V_E
Open
SJSJ_SMALLER
SJ_1_SMALLER
jumper
1
AUDIO_IN PJ-W47S-05D2-LF_V2
AUDIO_JACK_5PINPJ-W47S-05D2-LF_V2 PJ-W47S-05D2-LF_5PIN_V2
gogo
1
AUDIO_OUT PJ-W47S-05D2-LF_V2
AUDIO_JACK_5PINPJ-W47S-05D2-LF_V2 PJ-W47S-05D2-LF_5PIN_V2
gogo
1
BAT
TESTPADTESTPAD_40-ROUND
TESTPADTESTPAD_40-ROUND
TESTPAD_40-ROUND
gogo
1
C1
220nF
C-EUC0603_DWS
C0603_DWS
rcl
1
C2
220nF
C-EUC0603_DWS
C0603_DWS
rcl
1
C3
220nF
C-EUC0603_DWS
C0603_DWS
rcl
1
C4
220nF
C-EUC0603_DWS
C0603_DWS
rcl
1
C5
220nF
C-EUC0603_DWS
C0603_DWS
rcl
1
C6
220nF
C-EUC0603_DWS
C0603_DWS
rcl
1
C7
220nF
C-EUC0603_DWS
C0603_DWS
rcl
1
C8
220nF
C-EUC0603_DWS
C0603_DWS
rcl
1
C9
220nF
C-EUC0603_DWS
C0603_DWS
rcl
1
C10
220nF
C-EUC0603_DWS
C0603_DWS
rcl
1
C11
220nF
C-EUC0603_DWS
C0603_DWS
rcl
1
C12
220nF
C-EUC0603_DWS
C0603_DWS
rcl
1
C13
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
rcl
1
C14
220nF
C-EUC0603_DWS
C0603_DWS
rcl
1
C15
220nF
C-EUC0603_DWS
C0603_DWS
rcl
1
P a g e 42 o f 51
C16
C17
C18
C19
C20
C21
C22
C23
C24
C25
C26
C27
C28
C29
C30
C31
C32
C33
C34
C35
C36
C37
C38
C39
C40
C41
C42
C43
C44
C45
C46
C47
C48
C49
C50
C51
C52
C53
C54
C55
C56
C57
C58
C59
C60
C61
C62
C63
C64
C65
C66
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
100nF
22uF/6.3V
100nF
100nF
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
P a g e 43 o f 51
C67
C68
C69
C70
C71
C72
C73
C74
C75
C76
C77
C78
C79
C80
C81
C82
C83
C84
C85
C86
C87
C88
C89
C90
C91
C92
C93
C94
C95
C96
C97
C98
C99
C100
C101
C102
C103
C104
C105
C106
C107
C108
C109
C110
C111
C112
C113
C114
C115
C116
C117
22uF/6.3V
220nF
220nF
220nF
NA
33pF
33pF
100nF
100nF
22uF/6.3V
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
220nF
100nF
100nF
100nF
1uF
100nF
100nF
100nF
100nF
100nF
10pF
10pF
33pF
33pF
22uF/6.3V
100nF
22uF/6.3V
22uF/6.3V
22uF/6.3V
220nF
NC
NC
22uF/6.3V
1uF
220nF
10uF/6.3V
10uF/6.3V
220nF
22uF/6.3V
22uF/6.3V
220nF
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C-EUC0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
C0603_DWS
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
P a g e 44 o f 51
C118
C119
C120
C121
C122
C123
C124
C125
C126
C127
C128
C129
C130
C131
C132
C133
C134
C135
C136
C137
C138
C139
C140
C141
C142
C143
C144
C145
C146
C147
C148
C149
C150
C151
C152
C153
C154
C155
C156
C157
C158
C159
C160
C161
C162
C163
C164
C165
C166
C167
C168
220nF
C-EUC0603_DWS
C0603_DWS
220nF
C-EUC0603_DWS
C0603_DWS
220nF
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
100uF/16V/LOWESR/105C/6.3x11mm_RM2.5 CPOL-EUE2.5-6.3
100nF
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
100uF/16V/LOWESR/105C/6.3x11mm_RM2.5 CPOL-EUE2.5-6.3
1nF
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
1nF
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
1nF
C-EUC0603_DWS
C0603_DWS
1nF
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
220nF
C-EUC0603_DWS
C0603_DWS
100uF/16V/LOWESR/105C/6.3x11mm_RM2.5 CPOL-EUE2.5-6.3
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
220nF
C-EUC0603_DWS
C0603_DWS
10nF
C-EUC0603_DWS
C0603_DWS
10nF
C-EUC0603_DWS
C0603_DWS
10nF
C-EUC0603_DWS
C0603_DWS
10nF
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
3.3nF
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
1uF
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
NA
C-EUC0603_DWS
C0603_DWS
NA
C-EUC0603_DWS
C0603_DWS
220nF
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
1nF
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
3.3nF
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
1nF
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
1uF
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
rcl
rcl
rcl
rcl
rcl
E2,5-6,3
rcl
rcl
E2,5-6,3
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
E2,5-6,3
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
1
1
1
1
1
rcl
1
rcl
1
rcl
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
P a g e 45 o f 51
C169
C170
C171
C172
C173
C174
C175
C176
C177
C178
C179
C180
C181
C182
C183
C184
C185
C186
C187
C188
C189
C190
C191
C192
C193
C194
C195
C196
C197
C198
C199
C200
C201
C202
C203
C204
C205
C206
C207
C208
C209
C210
C211
C212
C213
C214
C215
C216
C217
C218
C219
220nF
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
1uF
C-EUC0603_DWS
C0603_DWS
220nF
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
NA
C-EUC0603_DWS
C0603_DWS
1nF
C-EUC0603_DWS
C0603_DWS
NA
C-EUC0603_DWS
C0603_DWS
220nF
C-EUC0603_DWS
C0603_DWS
NA
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
10uF/6.3V
C-EUC0603_DWS
C0603_DWS
NA
C-EUC0603_DWS
C0603_DWS
220nF
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
220nF
C-EUC0603_DWS
C0603_DWS
470nF
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
22pF
C-EUC0603_DWS
C0603_DWS
470nF
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
10nF
C-EUC0603_DWS
C0603_DWS
3.3nF
C-EUC0603_DWS
C0603_DWS
470uF/25V/LOWESR/105C
CPOL-EUE5-10.5
E5-10,5
100nF
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
22pF
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
100nF
C-EUC0603_DWS
C0603_DWS
1nF
C-EUC0603_DWS
C0603_DWS
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
rcl
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
P a g e 46 o f 51
C220
22uF/6.3V
C-EUC0603_DWS
C0603_DWS
rcl
1
C221
100nF
C-EUC0603_DWS
C0603_DWS
rcl
1
C222
4.7uF
C-EUC0603_DWS
C0603_DWS
rcl
1
C223
4.7uF
C-EUC0603_DWS
C0603_DWS
rcl
1
CHGLED
LED/RED/0603
LED0603DWS
LED-0603
DOUBLE-SIDE
1
D1
1N5819(S4SOD-123)
SCHOTKKY7.62SS-1N5819(S4SOD-123) SOD-123
gogo
1
D2
BAT54S
DIODE_AC-AC_
SOT23C(BAT54S)
semicon-smd-ipc 1
D3
BAT54S
DIODE_AC-AC_
SOT23C(BAT54S)
semicon-smd-ipc 1
D4
1N5822/SS34/SMA
SCHOTKKY7.62SS2
MLL-41
gogo
1
D5
SMBJ16A
SMBJ16A
DO214AA
OLIMEX_DISCRET 1
D6
1N5822/SS34/SMA
D-MLL-41
MELF-MLL41
semicon-smd-ipc 1
FET1
IRLML6402
P-MOS+DIODIRLML6402
SOT23
Penko
1
FUSE1
FSMD035
FUSE
1206
gogo
1
GND
TESTPADTESTPAD_40-ROUND
TESTPADTESTPAD_40-ROUND
TESTPAD_40-ROUND
gogo
1
GND_PIN TESTPAD3
TESTPAD3
TEST_PAD40/70/SQUARE gogo
1
GPIO-1
BH10S
ML10
ML10-MALE
con-harting-ml 1
GPIO-2
BH40S
ML40
ML40
con-harting-ml 1
GPIO-3
BH40S
ML40
ML40
con-harting-ml 1
GPIO-4
BH40S
ML40
ML40
con-harting-ml 1
HDMI
HDMI-MC34931(1428259)
HDMI-MC34931(1428259)
HDMI-MC34931
OLIMEX_CONNECTORS 1
IPSOUT
TESTPADTESTPAD_40-ROUND
TESTPADTESTPAD_40-ROUND
TESTPAD_40-ROUND
gogo
1
JTAG
BH20S
ML20
ML20-MALE
con-harting-ml 1
L1
FB0805/600R/200mA(201209-601)
L-USL0805_5MIL_DWS
L0805_5MIL_DWS
rcl
1
L2
FB0805/600R/200mA(201209-601)
L-USL0805_5MIL_DWS
L0805_5MIL_DWS
rcl
1
L3
FB0805/600R/200mA(201209-601)
L-USL0805_5MIL_DWS
L0805_5MIL_DWS
rcl
1
L4
CL470nH/0805/1.76R/250mA
L-USL0805_5MIL_DWS
L0805_5MIL_DWS
rcl
1
L5
CL470nH/0805/1.76R/250mA
L-USL0805_5MIL_DWS
L0805_5MIL_DWS
rcl
1
L6
FB0805/600R/2A
L-USL0805_5MIL_DWS
L0805_5MIL_DWS
rcl
1
L7
FB0805/600R/200mA(201209-601)
L-USL0805_5MIL_DWS
L0805_5MIL_DWS
rcl
1
L8
FB0805/600R/2A
L-USL0805_5MIL_DWS
L0805_5MIL_DWS
rcl
1
L9
FB0805/600R/2A
L-USL0805_5MIL_DWS
L0805_5MIL_DWS
rcl
1
L10
FB0805/600R/2A
L-USL0805_5MIL_DWS
L0805_5MIL_DWS
rcl
1
L11
FB0805/600R/2A
L-USL0805_5MIL_DWS
L0805_5MIL_DWS
rcl
1
L12
2.2uH/1.5A/DCR<0.1R/CD32
L-CD32
CD32
OLIMEX_DISCRET 1
L13
2.2uH/1.5A/DCR<0.1R/CD32
L-CD32
CD32
OLIMEX_DISCRET 1
L14
2.2uH/1.5A/DCR<0.1R/CD32
L-CD32
CD32
OLIMEX_DISCRET 1
L15
FB0805/600R/200mA(201209-601)
L-USL0805_5MIL_DWS
L0805_5MIL_DWS
rcl
1
L16
FB0805/600R/200mA(201209-601)
L-USL0805_5MIL_DWS
L0805_5MIL_DWS
rcl
1
L17
FB0805/600R/200mA(201209-601)
L-USL0805_5MIL_DWS
L0805_5MIL_DWS
rcl
1
L18
2.2uH/1.5A/DCR<0.1R/CD32
L-CD32
CD32
OLIMEX_DISCRET 1
L19
10uH/3.15A/20%
LLQH88PN100M38
8X8MM_3131
OLIMEX_DISCRET 1
P a g e 47 o f 51
L20
2.2uH/1.5A/DCR<0.1R/CD32
L-CD32
CD32
OLIMEX_DISCRET 1
L21
2.2uH/1.5A/DCR<0.1R/CD32
L-CD32
CD32
OLIMEX_DISCRET 1
LAN
RJLBC-060TC1
RJLBC-060TC1_GND
RJLBC-060TC1
OLIMEX_CONNECTORS 1
LCD_CON BH40S
ML40
ML40
con-harting-ml 1
LED1
LED/GREEN/0603
LED0603DWS
LED-0603
DOUBLE-SIDE
1
LINE_IN PJ-W47S-05D2-LF_V2
AUDIO_JACK_5PINPJ-W47S-05D2-LF_V2 PJ-W47S-05D2-LF_5PIN_V2
gogo
1
LIPO_BAT DW02R
CON2DW02R
DW02R
Penko
1
MIC1
AMF-097A44-NBAB
MICR
MIC
DOUBLE-SIDE
1
NAND_E
HN1x2(Close)
JP1E
JP1
jumper
1
PWR
YDJ-1136
PWR-JAKPWR_JACK_UNI_MILLING
PWR_JACK_UNI_MILLING gogo
1
PWR_BUT T1107A(6x3.8x2.5mm)
SW-TAKT6
SW-TAKT_6X3.5_SMD
gogo
1
PWR_LED LED/RED/0603
LED0603DWS
LED-0603
DOUBLE-SIDE
1
Q1
Q25.000MHz/HC-49SM/SMD/20ppm/20pF HC49/S1
HC49/SMD2_THIN
crystal
1
Q2
32768Hz/6pF
Q_GND1
TC26H_3_REPAIR_SMD crystal
1
Q3
Q24.000MHz/HC-49SM/SMD/20ppm/20pF HC49/S1
HC49/SMD2_THIN
crystal
1
R1
2k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R2
2k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R3
1R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R4
10k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R5
NA
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R6
2k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R7
240R/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R8
2k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R9
240R/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R10
240R/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R11
240R/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R12
NA
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R13
2.2k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R14
2.2k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R15
NA
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R16
240R/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R17
5.1k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R18
10k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R19
10k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R20
2k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R21
10k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R22
560R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R23
NA
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R24
0R(Board_Mounted)
R_0R0R(NA)
0603_0R
OLIMEX_DISCRET 1
R25
NA
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R26
560R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R27
47k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R28
47k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R29
NA(1M)
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R30
10k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R31
1R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R32
2.2k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
P a g e 48 o f 51
R33
R34
R35
R36
R37
R38
R39
R40
R41
R42
R43
R44
R45
R46
R47
R48
R49
R50
R51
R52
R53
R54
R55
R56
R57
R58
R59
R60
R61
R62
R63
R64
R65
R66
R67
R68
R69
R70
R71
R72
R73
R74
R75
R76
R77
R78
R79
R80
R81
R82
R83
10k
0R(Board_Mounted)
NA(1M)
200k/1%
2k
10k
2k
47k
10k
4.99k/1%
0R(Board_Mounted)
10k
13k/1%
10k
10k
13k/1%
NA
NA
1R
47k
1R
10k
13k/1%
4.7k
2k
240R/1%
0.03R/1%
1R
2.2k
1R
1R
192R/1%
2.2k
1R
200k/1%
1R
0R(Board_Mounted)
2.2k
1R
1R
2.2k
1R
2.2k
2.2k
4.99k/1%
3.3k/1%
47k
4.99k/1%
2.2k
NA(2.2k)
NA(2.2k)
R-EU_R0603_5MIL_DWS
R_0R0R(NA)
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R_0R0R(NA)
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R1206_5MIL_WS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R_0R0R(NA)
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
0603_0R
OLIMEX_DISCRET 1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
0603_0R
OLIMEX_DISCRET 1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R1206_5MIL_WS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
0603_0R
OLIMEX_DISCRET 1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
R0603_5MIL_DWS
rcl
1
P a g e 49 o f 51
R84
47k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R85
2.2k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R86
1k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R87
0R(Board_Mounted)
R_0R0R(NA)
0603_0R
OLIMEX_DISCRET 1
R88
8.2k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R89
4.99k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R90
1.1k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R91
100k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R92
1.1k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R93
NA
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R94
NA
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R95
47k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R96
6.8k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R97
8.2k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R98
10k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R99
11k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R100
13k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R101
16k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R102
22k/1%
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R103
NA
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R104
330R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R105
10k
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R106
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R107
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R108
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R109
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R110
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R111
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R112
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R113
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R114
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R115
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R116
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R117
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R118
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R119
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R120
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
R121
22R
R-EU_R0603_5MIL_DWS
R0603_5MIL_DWS
rcl
1
RECOVERY T1107A(6x3.8x2.5mm)
SW-TAKT6
SW-TAKT_6X3.5_SMD
gogo
1
RESET
T1107A(6x3.8x2.5mm)
SW-TAKT6
SW-TAKT_6X3.5_SMD
gogo
1
RM1
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM2
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM3
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM4
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM5
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
P a g e 50 o f 51
RM6
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM7
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM8
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM9
RA1206_(4X0603)_4B8_4.7k
R_MATRIX_4E
R_MATRIX_4
OLIMEX_DISCRET 1
RM10
RA1206_(4X0603)_4B8_4.7k
R_MATRIX_4E
R_MATRIX_4
OLIMEX_DISCRET
1
RM11
RA1206_(4X0603)_4B8_4.7k
R_MATRIX_4E
R_MATRIX_4
OLIMEX_DISCRET
1
RM12
RA1206_(4X0603)_4B8_4.7k
R_MATRIX_4E
R_MATRIX_4
OLIMEX_DISCRET
1
RM13
RA1206_(4X0603)_4B8_51R
R_MATRIX_4E
R_MATRIX_4
OLIMEX_DISCRET
1
RM14
RA1206_(4X0603)_4B8_100K
R_MATRIX_4E
R_MATRIX_4
OLIMEX_DISCRET
1
RM15
RA1206_(4X0603)_4B8_100K
R_MATRIX_4E
R_MATRIX_4
OLIMEX_DISCRET
1
RM16
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM17
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM18
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM19
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM20
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM21
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM22
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM23
RA0805_(4X0402)_22R
R_MATRIX_4E_25X625
R_MATRIX_4_0402_25X625
OLIMEX_DISCRET 1
RM24
RA1206_(4X0603)_4B8_75R
R_MATRIX_4E
R_MATRIX_4
OLIMEX_DISCRET
1
RM25
RA1206_(4X0603)_4B8_10k
R_MATRIX_4E
R_MATRIX_4
OLIMEX_DISCRET
1
RM26
RA1206_(4X0603)_4B8_10k
R_MATRIX_4E
R_MATRIX_4
OLIMEX_DISCRET
1
RS232_0 DB9-BFR
F09HP_DB9-BFR
DB9-BFR
con-subd
1
SATA
SATA-PWA-07
SATA-PWA-07
SATA-PWA-07
OLIMEX_CONNECTORS 1
SCKE1
TESTPAD3
TESTPAD3
TEST_PAD40/70/SQUARE gogo
1
SD/MMC1 MICRO_SD+CP
MICRO_SD/MMC_CPMICRO
TFR-MEM-CON
OLIMEX_CONNECTORS 1
SD/MMC2 PSD006A-LT2-BA0
SD_CARD_PSD006A-LT2-BA0
SD_CARD
OLIMEX_CONNECTORS 1
SW1
T1107A(6x3.8x2.5mm)
SW-TAKT6
SW-TAKT_6X3.5_SMD
gogo
1
SW2
T1107A(6x3.8x2.5mm)
SW-TAKT6
SW-TAKT_6X3.5_SMD
gogo
1
SW3
T1107A(6x3.8x2.5mm)
SW-TAKT6
SW-TAKT_6X3.5_SMD
gogo
1
P a g e 51 o f 51
SW4
T1107A(6x3.8x2.5mm)
SW-TAKT6
SW-TAKT_6X3.5_SMD
gogo
1
SW5
T1107A(6x3.8x2.5mm)
SW-TAKT6
SW-TAKT_6X3.5_SMD
gogo
1
SW6
T1107A(6x3.8x2.5mm)
SW-TAKT6
SW-TAKT_6X3.5_SMD
gogo
1
SW7
T1107A(6x3.8x2.5mm)
SW-TAKT6
SW-TAKT_6X3.5_SMD
gogo
1
U$1
NANO_ITX_
NANO_ITX_
NANO-ITX_140X140
OLIMEX_CASES 1
U1
A10
A10
TFBGA441
OLIMEX_IC
1
U2
H5TQ2G83CFR-H9C
H5TQ2G83CFR-H9C
FBGA78
OLIMEX_IC
1
U3
H5TQ2G83CFR-H9C
H5TQ2G83CFR-H9C
FBGA78
OLIMEX_IC
1
U4
H5TQ2G83CFR-H9C
H5TQ2G83CFR-H9C
FBGA78
OLIMEX_IC
1
U5
H5TQ2G83CFR-H9C
H5TQ2G83CFR-H9C
FBGA78
OLIMEX_IC
1
U6
AT24C16BN-SH
24LCXX
SO-08MN
gogo
1
U7
RTL8201CP
RTL8201CP
LQFP48
OLIMEX_IC
1
U8
H27UBG8T2BTR
H27UBG8T2A
TSOP48
OLIMEX_IC
1
U9
SY6280
SY6280
SOT23-5
OLIMEX_IC
1
U10
SY6280
SY6280
SOT23-5
OLIMEX_IC
1
U11
SY6280
SY6280
SOT23-5
OLIMEX_IC
1
U12
AXP209(QFN48)
AXP209
QFN48
OLIMEX_IC
1
U13
SY8008C(AA)C
SY8008
SOT23-5
OLIMEX_IC
1
U14
MP1482DS
MP1482
SOIC8
OLIMEX_IC
1
U15
SY8008C(AA)C
SY8008
SOT23-5
OLIMEX_IC
1
U16
SY7208(SOT23-6)
SY7208
SOT23-6
OLIMEX_IC
1
U17
RCLAMP0524P
RCLAMP0524P
SLP2510P8
OLIMEX_IC
1
U18
ST3232CDR(SO16)
MAX3232
SO16-150MILS
gogo
1
U22
RCLAMP0524P
RCLAMP0524P
SLP2510P8
OLIMEX_IC
1
U23
RCLAMP0524P
RCLAMP0524P
SLP2510P8
OLIMEX_IC
1
U24
74ACT08D
74AC08D
SO14
74xx-eu
1
UART0
NA(HN1X4)
CON4HN1X4
HN1X4
Penko
1
UEXT1
BH10S
ML10
ML10-MALE
con-harting-ml 1
UEXT2
BH10S
ML10
ML10-MALE
con-harting-ml 1
USB_HOST1 USB_A_VERTICAL
USB_SHIELDUSB_A_VERTICAL
USB_A_VERTICAL_PTH
OLIMEX_CONNECTORS 1
USB_HOST2 USB_A_VERTICAL
USB_SHIELDUSB_A_VERTICAL
USB_A_VERTICAL_PTH
OLIMEX_CONNECTORS 1
USB_OTG USB-OTG
MINI_USB9
USB_MINI_9PIN
OLIMEX_CONNECTORS 1
VGA_DB15-F VGA15
DB1522
DB15-F_22MM
OLIMEX_CONNECTORS 1
VR1
AP1231-2.5V(SOT23-5)
AP1231-33
SOT-23-5
OLIMEX_DISCRET 1
xv
https://www.dropbox.com/s/8w69ohoyymqbhhn/Team10.WBS.pod.pod