Primescan 2 – Connecting to a New Wi‑Fi Network

Internal Technical Reference – AO Associates

Overview

This document outlines the manufacturer-aligned procedure for connecting a Primescan 2 device to a new wireless network. It also includes AO operational best practices and a visual YouTube reference segment (0:38–1:13) demonstrating the on-device workflow.

1. Manufacturer Workflow (On-Device Procedure)

Primary Method (Touchscreen Navigation)

1. Dock the scanner in the charging base.
2. Power on the device.
3. On the touchscreen, select: Settings (gear icon) → Network / Connectivity → Wi‑Fi
4. Toggle Wi‑Fi ON (if disabled).
5. Wait for available SSIDs to populate.
6. Select the desired wireless network.
7. Enter the WPA2/WPA3 passphrase.
8. Confirm connection.

Validate Connectivity

After connecting, confirm: - An IP address has been assigned. - Internet connectivity shows “Connected.” - The DS Core account remains authenticated (re-login if prompted).

Visual Reference (Field Demonstration)

YouTube Video: https://youtu.be/f_NmCWRrVOs?si=81qehNqyHu2MW_8K

Relevant Timestamp: 0:38 – 1:13

This segment visually demonstrates: - Navigating to the Settings menu - Selecting Wi‑Fi - Choosing the new SSID - Entering credentials - Confirming connection

This aligns with the manufacturer workflow above and can be used as a remote guidance aid when assisting office staff.

2. AO Operational Best Practices

Because Primescan 2 is cloud-dependent (DS Core integration), network quality directly impacts scan synchronization and case submission.

Wireless Requirements

• Prefer 5 GHz band
• Avoid DFS channels during troubleshooting
• Use WPA2 or WPA2/WPA3 mixed mode (avoid WPA3-only during testing)
• Ensure RSSI stronger than -65 dBm at scanner location

DHCP / VLAN

• Confirm DHCP scope has available addresses
• Avoid client isolation
• Avoid guest-network segmentation
• Ensure proper VLAN routing to internet

Firewall Considerations (WatchGuard Environments)

• Confirm outbound TCP 443 unrestricted
• Temporarily disable HTTPS inspection for testing
• Ensure no Geo-blocking affecting cloud endpoints
• No captive portal authentication

3. Troubleshooting Scenarios

A. Authentication Failure

Possible causes: - WPA3-only SSID - MAC filtering enabled - Incorrect passphrase

Recommended test: Create temporary WPA2-only SSID with simple password and no filtering.

B. Connected but No Internet

Check: - DNS resolution - Content filtering policies - Outbound firewall rules - Deep packet inspection interference

C. SSID Not Visible

Check: - Hidden SSID configuration - DFS channel usage - AP firmware version

4. Structured Intake for Escalation

If issue persists, collect: - Firewall make/model and firmware version - Access point model and firmware - VLAN ID used for wireless - Security type (WPA2/WPA3/Enterprise) - DHCP scope range - Exact on-screen error message - Whether other devices connect successfully to same SSID

End of Document AO Associates – Internal Use Only