VR-MFC Test-Procedures/ShelfReader

From VentureResearchWiki
Jump to navigation Jump to search

VRDevices Tests[edit | edit source]

This page covers all tests under the "VRDevices" app in the VR Hardware-Manager [MFC] program.

General[edit | edit source]

Opening the VRDevices App[edit | edit source]

To open the VRDevices App, launch the VR Hardware-Manager program. When the program starts up, open the Start Menu, as shown here:

ShelfReader 1.png

Select VR Devices from the Start Menu, this will bring up the VRDevices App. When the VR Device interface window appears, select the appropriate test from the drop down under the Test Controls section:

ShelfReader 2.png

Physical Connections to Devices[edit | edit source]

Before proceeding, make sure all the physical connections are made between the Test PC and the Test Device.

Running the Test[edit | edit source]

The interface for each different test is very similar and should look something like:ShelfReader 3.png

A small Device Connection window will also appear:

VRDevices 4.png

Click Find VRDevice twice, wait until the message Successfully discovered VRDevice... appears, then click Connect. Wait for both connections to be made, then proceed with the test.

To start the test, click the Play button in the bottom right of the VR Device interface:

VRDevices 5.png

And follow the prompts to finish the test.

Troubleshooting[edit | edit source]

Failing to Find Device[edit | edit source]

If clicking the Find VRDevice button twice does not result in the message: Successfully discovered VRDevice..., close and re-open the VR Hardware-Manager program and try again.

Failure to Establish Connection[edit | edit source]

If the Connect button does not successfully establish both connections (ports 2222 and 2020), make sure all cables are fully plugged into their ports, then close and re-open the VR Hardware-Manager program and try again.

Test Failed[edit | edit source]

If the test fails for any reason, close and re-open the VR Hardware-Manager program and try running the test again. If the test continues to fail, attach a VR Quality Issue document to the asset and set it aside.