DreamZBox 2.0

Project Purpose:

The purpose of this project is to create a remastered version of its predecessor the CVM DreamZBox. In addition, it serves as one of the capstone projects for Oregon State University during the 2019-2020 academic year. This site is a record of the development process of the DreamZBox 2.0.

Megan McCormick and Cory Brown were the previous designers of the CVM DreamZBox and are the clients for this project.

Executive Summary:

The first steps in designing this project were to address battery power management, controller design, and enclosure design. These were the main parts the clients wanted remade from the original DreamZBox. Three members were in the ECE team so a part was assigned to each individual member. Decisions were made based of dependencies of each block. For example, the enclosures couldn't be made without the PCBs, so the member in charge of enclosures would focus on other parts of the project until they had the information needed to accomplish the enclosure design. The ECE team also needed to consult with the CS team, who were working on the custom game for the console, in order to determine what was realistic in terms of controller and console functionality.

Each ECE team member encountered issues with the design along the way, and parts needed to be redesigned a few times until the individual blocks worked. After individual blocks were working, system integration began and everyone worked together to find and fix any issues that occurred during the integration process. Some of the issues included making the controllers stay connected to the console for longer amounts of time, problems with power, and fixing the enclosures to accommodate for changes in PCB design.

Overall, the end product is very close to completion. The controllers are able to connect to the console via Bluetooth and get data flowing between the two. The console is also able to be powered without being plugged into the wall and the current enclosure design is almost perfect. Due to the current situation no more technical development is possible at this point in time so unfortunately the project cannot be completed in its entirety.

Through this design process, lessons were learned. These include time management is key, it is important to finish things early to provide more time for debugging and time for parts to be shipped. Communication between team members as well as others involved in the project is important to make sure there are no misunderstandings or misconceptions. This project was an enjoyment to work on and even though the outcome wasn't what was planned, each member is glad to have worked on the DreamZBox 2.0.

Project Requirements

Console Dimension

CR: The system must be portable.

ER: The console will be within the dimensions of 8 x 8 x 4 inches.

Maximum Cost

CR: The system must be marketable.

ER: The system needs to not cost more than $600.

Safe Operating Temperature

CR: The system must be safe to use.

ER: The system is able to run for at least 30 minutes at 80° Fahrenheit.

Minimum Duration of Use

CR: The system must be safe to use.

ER: The system is durable enough to support 3 consecutive session lasting at least 15 minutes.

Multi-user play

CR: The system must support multiplayer.

ER: The system will allow for two users to operate the system simultaneously without errors or disconnect, 9 out of 10 times.

Aesthetically Appealing

CR: The system must be marketable.

ER: The system will be aesthetically pleasing to at least 9 of 10 people.

Console Controller Pairing Button

CR: The system must be usable.

ER: The system will have a button to configure controllers on the console.

Wireless Controller Support

CR: The system must be portable.

ER: The controllers for the system will be wireless from 10ft away.

Joystick Implementation

CR: At least one controller for the system is unique to the game.

ER: An input on a controller must be able to track X/Y directional movement.

Scroll-wheel Implementation

CR: At least one controller for the system is unique to the game.

ER: An input on a controller must be able to have a scroll functionality.

External Startup Button

CR: The system must be usable.

ER: The system will have a power switch that successfully boot the console's operating system 9 out of 10 times.

Automatic Power Shutdown

CR: The system must be safe to use.

ER: The console will automatically automatically within 10 minutes of the battery reaching 5-10%.

*CR is short hand for Customer (Client) Requirements*ER is short hand for Engineering Requirements