Force Feedback AUT Landspeed Research Group Project Proposal

Project Profile Team Members: Marcus Ball Zaijun An Supervisor: Dr. Robert Wellington Client: Dr. Stefan Marks Company: AUT and JetBlack Landspeed Record Research Group

Terms of Reference Current System: JetBlack – A rocket powered vehicle created to break the current landspeed record Simulator has been built within the HCI Lab on the first level of the AUT tower Simulator needed for training, testing and tweaking of the vehicle Built using Unity3D Game engine

Terms of Reference Project Objective Logitech G27 Steering Wheel Dual-motor force feedback/vibration RPM/shift indicator LEDs 900 degree wheel rotation Integrate force feedback into the current simulator system Tie in the steering wheel’s features into the Unity3D engine

Terms of Reference Project Scope Unity3D code for simulator has been written in Mono (a C# open source alternative) G27 Software Development Kit has been created in C++ We will need to study both languages Study forces Initial solution proposal – create a.dll (dynamically linked library) file to allow control of the steering wheel through Unity3D. Unity3D Pro allows support for Native Code Plugins, custom native libraries for projects.

Terms of Reference Deliverables Source code with appropriate comment blocks Fully documented code using Doxygen An example program showing all features properly integrated a graphical user interface for dynamically changing variables involved with the steering wheel e.g. a slider which alters resistance of the wheel

Terms of Reference Cost Incurred Unity3D Professional license - $1500 USD ($1800 NZ approximately) G27 Steering wheel - $ NZ All gear is supplied and resides within the HCI lab Transportation will cost between $20-40 per week although this will be covered by the team members as it doesn’t directly affect only the project Internet usage will also be covered as it will be used rarely during development

Methodology - Scrum Using Sprint Backlog, Burndown Charts and Product Backlog for project tracking and organisation Sprints will be in 2-4 week iterations Scrum meetings will be scheduled to occur on a regular basis and Standup meetings between team members will happen almost daily Retrospectives will take place at the end of each sprint to make sure the current process is without issue

Project Plan 2-3 months (may be extended) dedicated to studying all aspects and altering plan Will be followed by a single sprint used to simulate all the wheels features into a sample application. 1 month dedicated to creation of the proposed dll Remaining time dedicated to code refactoring, tweaking and necessary documentation. This time will also be used if we are unable to complete the previous tasks.