Visual Occlusion Goggles Module

Getting Started

1. Connect your Visual Occlusion Goggles — Via USB
2. Enable the Visual Occlusion Goggles module — From the Modules menu
3. Wait for the device tab — Indicates successful detection
4. Use lens controls or start recording

User Interface

Device Tabs

Each connected device gets its own tab showing:

Lens Controls

Wireless devices have additional buttons for independent left/right lens control.

Results Display

After each trial, the panel shows:

Recording Sessions

Starting a Session

When you start a recording session:

• Device enters experiment mode
• Chart clears and begins fresh
• Trial counter resets to 1

During Recording

Each trial captures:

• Timing data for all lens state changes
• Accumulated open/close durations
• Timestamps synchronized to system time

Data Output

File Location

{session_dir}/VOG/

File Naming

{timestamp}_VOG_trial{NNN}_{device_type}_{port}.csv

Example: 20251208_143022_VOG_trial001_sVOG_ttyACM0.csv

sVOG CSV Columns (7 fields)

For wired VOG devices:

Example row:

sVOG,ttyACM0,1733649120.123456,5000,1,1500,3500

wVOG CSV Columns (9 fields)

For wireless VOG devices (same first 7 columns as sVOG, plus):

Example row:

wVOG,xbee_002,1733649120.456789,5500,2,3000,2500,Open,85

Timing and Synchronization

Timing Precision

• TSOT/TSCT: Millisecond precision (device firmware)
• Unix time in UTC: Microsecond precision (6 decimals)
• Lens state changes: Device-measured (<50ms for close, <15ms for open, continuous state change)

Cross-Module Synchronization

Use "Unix time in UTC" to correlate VOG events with:

• Video frames (via camera capture_time_unix)
• Audio samples (via audio write_time_unix)
• Detection Response Task trials (via Unix time in UTC)
• Eye tracking data (via record_time_unix)

Experiment Types

Cycle

Standard visual occlusion testing following NHTSA Visual Manual Distraction Guidelines and ISO 16673.

How it works: The lenses automatically alternate between clear and opaque at fixed intervals (e.g., 1.5 seconds each). Participants perform a task while only able to see during the clear periods. The system records total shutter open time (TSOT) and total task time.

Use case: Measuring the visual demand of in-vehicle interfaces and other tasks requiring intermittent visual attention.

Peek

For testing interfaces where the primary modality is non-visual (e.g., auditory or haptic) but occasional visual confirmation may be needed.

How it works: Lenses start opaque. Participants press a button to request a "peek" - the lenses clear for a set duration (default 1.5 seconds) then return to opaque. A lockout period prevents consecutive peeks.

Data collected: Number of peeks and cumulative peek time, providing a measure of visual attention demand for interfaces designed for eyes-free operation.

Use case: Evaluating voice-controlled or auditory display systems where visual glances should be minimized.

eBlindfold

For measuring visual search time.

How it works: Trial begins with lenses clear. The participant searches for a specified target. Upon locating the target, they press the button - the lenses immediately go opaque and the trial ends. Total shutter open time equals search time.

Use case: Measuring visual search performance, comparing display layouts, or evaluating icon/element discoverability.

Direct

Simple manual control mode for integrating with external equipment or custom experiment setups.

How it works: The lenses directly mirror the button state - press and hold to clear, release to go opaque (or vice versa). No timing data is recorded by the glasses themselves.

Use case: When you need to control the glasses from other laboratory equipment, or for demonstrations and testing.

Configuration

Click "Configure Unit" on any device tab to access settings.

The configuration dialog adapts to show available options based on the connected device type.

Troubleshooting