VIRTUAL REALITY LAB

SIMULATION EE DESIGN 2 SPRING 2021

BY : DUC LUONG, ANDREA ESPINOSA, & MIRZA MALIHA

ADVISORS : DR.CHUNG SEOP JEONG & DR.WILFRIDO MORENO

2. PROBLEM STATEMENT

This project is a virtual reality simulation of an in person electrical

engineering lab that could be used in future remote learning experiences. The
simulation will replicate a current lab that is performed in person using a 3D
virtual space, a virtual reality headset, and sensors. This is to improve remote
learning in response to the Covid-19 pandemic which forced labs to be
administered online. The online platform for current labs are limiting hands on
experiences that are necessary for student learning, research, and job
opportunities.
PROJECT DELIVERABLES
1. Simulation outputs accurate data for student to use in order to complete the lab
2. Sensors function as feedback to show student engagement during lab
- Real time feedback provided by EEG sensors will be acquired as excel data and fed into the software
3. Testing within the simulation to track progress through quizzes that are embedded into the simulation
4. Properly embedding code to the system, such that the headset, goggles and software communicate and interact as
defined by the feedback system diagram
5. Purchasing goggles that we know runs the 3D virtual environment software and acquiring software that
was designed for virtual reality simulations
6. Creating code for the simulation that reacts to the data given by the sensors and gives the correct output to user
input
7. Device Sizing Requirements, product shall not exceed 1.5lbs in weight to ensure the student feedback is not skewed
by comfortability
- The device has a total weight of 1.22lbs
3. DESIGN APPROACH
Our project uses software to simulate the activities of the experiment as in a real
experiment classroom, with a full range of experiment procedures and results.
• The software: Unity is used to interpret the code and is the platform for the
simulation to run on.
• Goggles: Oculus Quest VR goggles are used to show the virtual environment
from the software and simulate the lab in an immersive way.
• Brain wave sensor: Muse sensor data in the form of CSV file and brainwave
graphs is used to perform cognitive load measurement to give feedback on
learning development from the lab
4. SYSTEM
DIAGRAMS
LAB PROCEDURE/SIMULATION PROCESS
STATE
DIAGRAM OF
SIMULATION
Oculus-Quest 2
(VR Goggles)
5. DESIGN OF COMPONENT & SUB-SYSTEM
• Hardware is pre-built
• Oculus Quest
• Lens
• Battery
• Transmits data over internet connection
• Muse Sensor
• 5 EEG Head Sensors
• 2 EEG Ear Sensors
• Battery
• Transmits data with Bluetooth

• Software is Unity – C# code

• Environment
• User Interface
• Lab equipment design
• Testing/Feedback design
6. SIMULATION/CALCULATIONS
PERFORMED
• Through the Mind Monitor App, the Muse 2
sensors outputs absolute power values in
decibels for different frequency bands.
• Alpha Frequency Band: 7.5 – 13 Hz
• Alpha Band recognizes the brain
activity with the mind relaxing
and letting go of control.
• Gamma Frequency Band: 30 – 44 Hz
• Gamma Band recognizes the
brain activity with the mind
focused, trying to concentrate on
a task at hand.
7. HARDWARE/SOFTWARE DEVELOPMENT

• Hardware testing and development is complete

• Muse Sensor
• Oculus Quest

• Software still in development but has passed all tests to date

• User Interface
• Lab Equipment
• Testing/Feedback
7. HARDWARE DEVELOPMENT – MUSE
SENSOR
7. HARDWARE
DEVELOPMENT –
OCULUS QUEST
Requirements:

• Able to fit with Muse sensor

• Interfaces with computer to show and

interact with simulation
7. SOFTWARE
DEVELOPMENT -
ENVIRONMENT
Environment is built with all
elements embedded:
• Physics
• Cameras
• Audio
• Lighting
7. SOFTWARE DEVELOPMENT – USER INTERFACE
User Interface is Complete with all objects in simulation
• Menus
• Flow through the simulation
• On Click Events
• Logs
7. SOFTWARE DEVELOPMENT – LAB EQUIPMENT

Oscilloscope & Function Generator still in production

Oscilloscope for function generator input is functional but not the
circuit input yet
All materials have been fabricated – resistors, diodes, breadboard, etc.
CODE EXAMPLES
FOR LAB EQUIPMENT
7. SOFTWARE DEVELOPMENT – TESTING/FEEDBACK
Testing section is complete
- Based on sensor feedback quiz level is recommended (3 difficulties)
- Questions based on pre-lab assignment and questions from textbook chapter
corresponding to the lab experiment
8. TEST PLAN – FUNCTION TESTING
Req# Function Requirement / Deliverables Test Method Testing Timeline Pass/Fail
1 Software The system should be able to simulate a lab Test April 1st Pass
experiment.
2 Software The system should be able to provide accurate Analysis March 26th Pass
experimental values. Accurate oscilloscope and
function generator values.
3 Mechanical Sensors should be attached properly onto VR Inspection March 12th Pass
goggles.
Comfortable for user.
4 Software The system must be able to run on computer without Test March 26th Pass
error.
5 ME The system must be able to return valid data from Analysis March 8th Pass
brain wave sensors. CSV files and brain wave graphs
from Muse Sensor. Cognitive load measurements.

6 ME The VR goggles must correctly be connected to the Inspection March 8th Pass
computer.
7 Software The system must be able to load simulation into VR Inspection & Test March 19th Pass
goggles.
8 EE System must be able to provide digital feedback Demonstration March 26th Pass
from user input to the simulation.
9 EE System must accurately replicate Electrical Demonstration April 8th Pass
Engineering laws and concepts, such as Kirchhoff ‘s
laws.
10 ME System must abide by the laws of physics. Demonstration April 8th Pass
8. TEST PLAN - FINAL TESTING

Objectives Test Plan

Week 3/8 3/15 3/22 3/29 4/5 4/12 4/19 4/26

1. Software Test
• Deliverable Test
• Lag Test
• User Experience Test
2. Hardware Test
• VR Goggles
• Sensors
3. Feedback System Test
• Learning Data Integration
4. Full Integration Testing
• Run Program Several Times
8. FINAL TESTING
• SOFTWARE TEST
• Deliverable Test- run program, simulation should output accurate results, if fails code must be
reviewed
• Lag Test - Ensure lags don’t occur due to file size, redundant code, etc. refine program if fails
• User Experience Test – run test with new user to ensure the program is intuitive, finalize
program to make the result clean and usable to the user

• HARDWARE TEST
• VR Goggles – Ensure VR goggles are displaying the simulation correctly, if errors occur
contact Oculus customer service
• Sensors – Test sensors for feedback of heartrate and brainwave information, if errors occur
contact vendor
8. FINAL TESTING
• FEEDBACK SYSTEM TEST
• Use live information from the sensors to determine response from the simulation, if fails check
communication between sensors and information being sent to the software, if not a
communication error software testing must be done again to ensure the code is functioning as
intended

• FULL INTEGRATION TESTING

• Run program several times using VR Headset and Sensors
• Looking for accurate feedback
• Simple user experience
• No lags or errors
• Objective Test
• If fails return to other tests to determine what part of the system is causing the failure
9. WORK DIVISION
10. HARDWARE DEMO
 Thank you!
Any Questions?