Knowledge check PhotoRobot Locator App & FRFind
10 questions in pool · live exam draws 5
B04
Q1 multiple-choice · surfaces Which of the following is the preferred way to access PhotoRobot Locator for daily operator workflow?
Explanation: CAPP’s integrated Locator (Settings → Robots / Control units) is the canonical workflow for daily use. Zero context-switch, single tool, always up-to-date with CAPP releases. iOS app is for mobile / floor walks; FRFind is for scripting; browser direct is for diagnostic / service. CAPP integrated is the default surface.
Q2 multiple-choice · platforms Which mobile platform supports the standalone PhotoRobot Locator app?
Explanation: The Android version of PhotoRobot Locator was discontinued . The current mobile support is iOS / iPadOS only (via App Store and PhotoRobot Account Downloads). This matches PhotoRobot’s broader iOS-first mobile strategy (see also PhotoRobot Touch app). Customers with Android-only fleets use FRFind on laptop instead, or provision a shared iPad / iPhone for the studio.
Q3 multiple-choice · identify-workflow What happens when you click Identify on a Control Unit row in CAPP’s integrated Locator?
Explanation: The Identify action sends a blink command to the unit. The LED on the physical Control Unit (G6 / G7) starts blinking green — operator walks through the studio and sees which unit is blinking. This solves “which IP belongs to which physical machine” — a daily question in any studio with multiple Control Units. Renaming, rebooting, log download all happen via the unit’s web interface, not Identify.
Q4 multiple-choice · locator-output Which of the following information columns appears in CAPP’s integrated Locator (Settings → Robots / Control units)?
A) Name, IP only
B) Serial number, Purchase date, Warranty status
C) Name, Network, Unit, Version, Discovered, Identify
D) Name, Operator history, Last error
Explanation: CAPP integrated Locator shows six columns: Name (CU identifier), Network (IP + subnet), Unit (model — Cube V6, Carousel 5000, etc.), Version (firmware revision), Discovered (when last responded), Identify (action button → LED blink). This is the canonical Locator view. Serial/warranty info is in the unit’s web interface; operator history is in CAPP project logs.
Q5 true-false · alternatives FRFind is a command-line utility available for both macOS and Windows for scanning the local network for PhotoRobot Control Units.
Explanation: FRFind is the CLI utility for both macOS and Windows. Download via
PhotoRobot Account Downloads . Use cases: scripting / automation, CI/CD integration, machines without CAPP installed, raw text output for logging. Complements CAPP integrated Locator (daily use) and iOS app (mobile).
Q6 scenario · diagnostics · weight 2 An operator opens CAPP’s Locator. They see a Cube V6 listed at IP 10.1.2.42 with a green dot but the “Discovered” timestamp says 2 hours ago . What does this mean, and what action should they take?
Explanation: A fresh “Discovered” timestamp accompanies a green dot — they should be consistent. A 2-hour-old timestamp with green dot suggests Locator’s discovery cache is stale and hasn’t refreshed. Action: re-scan or restart CAPP. PhotoRobot Locator does NOT have a 2-hour refresh interval — it scans on demand. If the issue persists after refresh, escalate (could be a network blip or Control Unit transition state).
Q7 multiple-choice · download Where is the canonical download location for the iOS PhotoRobot Locator app (for paid PhotoRobot Account customers)?
Explanation: The canonical download is via PhotoRobot Account Downloads for paid customers. This ensures the download is linked to the account’s install context and license. iOS App Store also has Locator publicly available (less reliable for paid customer license workflow). Google Play has the discontinued Android version (do not use).
Q8 multiple-choice · subnet-dependency A Control Unit at IP 10.1.3.42 is plugged in, powered on, and responding to ping from a router. The control computer is at 10.1.2.55 with netmask 255.255.255.0 . Will Locator (any surface) find this Control Unit?
Explanation: Locator (all three surfaces — CAPP integrated, iOS app, FRFind) relies on UDP broadcast to port 6666 for discovery. Routers do NOT forward UDP broadcasts across subnets by default (it would cause broadcast storms). Even with full routing between subnets, broadcasts stay within their originating subnet. Result: computer at 10.1.2.x cannot discover units at 10.1.3.x via Locator. Solution: same-subnet design.
Q9 scenario · duplicate-ip · weight 2 Locator shows two entries with the same IP: “CU-7a2f at 10.1.2.42” and “CU-9b14 at 10.1.2.42”. Both show green dots. What does this mean and what should you do?
Explanation: Duplicate IP entries indicate a DHCP collision — typically during DHCP reassignment when the old lease wasn’t cleanly released. Only one unit will actually respond on that IP (network protocol resolves the conflict at the IP layer). The other unit needs a fresh DHCP lease. Resolution: power-cycle one unit, let DHCP re-assign. If the issue recurs, escalate (may indicate router DHCP misconfiguration). Powering down both is overkill; ignoring it leaves a confused state.
Q10 multiple-choice · integration A network specialist wants to set up automated nightly health checks on all Control Units (alert via email if any unit is offline for 6+ hours). Which Locator surface fits this best?
A) CAPP integrated Locator
B) iOS Locator app
C) FRFind CLI utility — combined with a wrapper script (cron + parsing + email)
D) Browser direct access to each unit
Pool size: 10 questions. Drawn for module check: 5. Drawn for cert exam: per cert weight (operator 5%, network-specialist 12%).
Mixed types: 6× multiple-choice, 1× true-false, 2× scenario, 1× scenario-extended.
Topic tags: surfaces, platforms, identify-workflow, locator-output, alternatives, diagnostics, download, subnet-dependency, duplicate-ip, integration.
All questions cite source (mostly networking-prerequisites manual since there’s no dedicated Locator manual on photorobot.com ).
Status draft — awaiting KH review.
Explanation: Automated / scripted monitoring fits the CLI tool. FRFind outputs unit status to stdout; a wrapper script (bash / Python / Node) runs FRFind periodically (cron / Task Scheduler), parses output, tracks state (how long each unit has been offline), and triggers email when threshold is exceeded. CAPP / iOS are interactive tools, not suited for unattended automation. Browser direct doesn’t scale. PhotoRobot Support may have reference scripts for this pattern — worth asking before building from scratch.
Ready to commit? You can review and change your answers before submitting. Once submitted, this attempt is final and we'll show you your score, correct answers, and explanations.
Submit final answers
