Factory Resetting an R700 Reader

How to safely reset a reader to factory defaults, and what survives.

Config-Image Modes

R700 readers have a config-image setting that controls what survives a factory reset:

Mode	CAP	Identity (/cust/rw_dir/)	MQTT Config	Presets
default	Kept	Kept	Reset	Reset
removecap	Wiped	Wiped	Reset	Reset

Default behavior (mode = default):

• CAP and identity files survive reset
• MQTT config, presets, RF settings reset to factory defaults

Full wipe (mode = removecap):

• CAP deleted
• Identity files wiped
• Everything reset to factory (as shipped from Impinj)

When to Use Each Mode

Mode: default (Recommended)

When to use:

• Reset reader config (MQTT, presets, RF settings)
• Keep Titan identity (reader stays in customer account)
• Troubleshooting (start fresh, but don't lose provisioning)

What survives:

• CAP installed
• Identity files (/cust/rw_dir/ intact)
• Reader still associated with customer in Titan Cloud

What resets:

• MQTT broker address, topics (reverts to factory defaults)
• Presets (back to stock)
• RF settings (power, session, filter)
• Network settings (IP, hostname)

After reset:

• Must reconfigure MQTT (or re-run readerprov if Wonder-shipped)
• Must recreate presets
• Reader will NOT automatically reconnect to Titan (MQTT config wiped)

Use case: "I changed some settings and broke it; reset to known-good state, but keep identity."

Mode: removecap (Full Wipe)

When to use:

• Returning reader to Impinj (warranty, RMA)
• Selling/gifting reader to non-Titan user
• Decommissioning reader (remove all Titan traces)

What happens:

• CAP deleted (custom application removed)
• Identity wiped (/cust/rw_dir/ deleted)
• All config reset
• Reader back to factory state (as shipped from Impinj)

After reset:

• Reader is stock R700 (no Titan software)
• Must re-install CAP if returning to Titan
• Must re-provision identity (new claim, new cert)

Use case: "I'm sending this reader back to Impinj; wipe everything."

How to Factory Reset

Via Web UI (Recommended)

1. Set config-image mode (before reset):

   • Reader web UI → Settings → Advanced
   • Find Config Image
   • Select default (keep CAP + identity) or removecap (full wipe)
   • Click Save

2. Factory reset:

   • Reader web UI → Settings → System
   • Scroll to Factory Reset
   • Click Reset to Factory Defaults
   • Confirm

3. Wait for reboot (~2 minutes)

4. Verify:

   • Check CAP: Apps → Custom Applications (should be present if mode = default)
   • Check identity: SSH or REST API → ls /cust/rw_dir/ (should have 4 files if mode = default)

Via Physical Button

R700 has a Default Restore button (physical button on reader, usually recessed).

Behavior: Performs factory reset using current config-image mode setting.

Steps:

1. Before pressing, ensure config-image mode is set correctly (web UI → Settings → Advanced → Config Image)
2. Power off reader
3. Hold Default Restore button while powering on
4. Hold for ~10 seconds
5. Release the button; the reader reboots and applies the factory reset

Important: Button does not choose the mode. It uses whatever mode is set in config. If mode = removecap, button wipes CAP + identity. If mode = default, button keeps them.

Via REST API

# Set config-image mode first
curl -k -u root:<password> -X PUT \
  https://<reader-ip>/api/v1/system/config-image \
  -d '{"mode":"default"}'

# Factory reset
curl -k -u root:<password> -X POST \
  https://<reader-ip>/api/v1/system/factory-reset

Reconfiguring After Reset (Mode = default)

If you reset with mode = default, CAP and identity survive, but MQTT config is wiped. To reconnect:

Option A: Re-Run Provisioning Tool

If Wonder-shipped:

readerprov provision \
  -reader <ip> \
  -tenant <customer> \
  -name "<name>" \
  -replace

-replace flag: Keeps existing device binding, rewrites MQTT config, restarts reader.

Option B: Manual MQTT Reconfiguration

1. Reader web UI → Settings → MQTT
2. Set:
   • Broker: mqtt.titanrfid.com:8883
   • TLS: Enabled
   • Client ID: 370-12-34-5678-9012 (reader's serial)
   • Event Topic: titan/v1/370-12-34-5678-9012/events
   • Status Topic: titan/v1/370-12-34-5678-9012/status
3. Save
4. Restart CAP (Apps → Titan Agent → Restart)

Identity already present (mode = default kept /cust/rw_dir/), so CAP can reconnect immediately after MQTT config restored.

What Happens to Reader in Titan Cloud

After default Reset

Reader row in Titan Cloud database: Unchanged

• Reader still in customer account
• Reader name, serial, zones: Unchanged
• Device binding: Intact

Visible in hub: Reader shows "Offline" (MQTT config wiped, cannot connect)

After reconfigure: Reader reconnects → status "Online"

After removecap Reset

Reader row: Unchanged (still in customer account) Device binding: Intact (serial → tenant mapping survives)

But: Reader has no CAP, no identity → cannot connect.

To bring back online:

1. Ask support or Wonder to release the reader in the operator console (unassigns tenant only). Ask support or Wonder to revoke the old certificate if it must not reconnect.
2. Re-install CAP (upload .upgx)
3. Re-provision identity (new claim, new cert)

Alternative: Leave reader row (historical data preserved), but reader offline forever (decommissioned).

Troubleshooting

Reset With Wrong Mode (Wiped Identity Accidentally)

Symptom: Reset reader, now offline; CAP present but won't connect; /cust/rw_dir/ empty

Fix:

1. Ask support or Wonder to release the reader in the operator console (unassigns tenant only). Ask support or Wonder to revoke the old certificate if it must not reconnect.
2. Re-install CAP (if removecap wiped it)
3. Re-claim reader:
   • Wonder-shipped: Re-run readerprov provision -replace
   • BYO (future): Re-claim via hub UI, re-pull identity

Data loss: None (tag history in Titan, not on reader). Reader configuration lost (MQTT, presets).

Can't Set Config-Image Mode (Setting Missing)

Some firmware versions hide config-image setting.

Workaround: Set via REST API:

curl -k -u root:<password> -X PUT \
  https://<reader-ip>/api/v1/system/config-image \
  -d '{"mode":"default"}'

Physical Button Wiped Identity (Mode Was removecap)

Symptom: Pressed Default Restore, reader back to stock (no CAP)

Cause: Config-image mode was removecap (full wipe)

Fix: Same as above (re-provision identity)

Prevention: Set mode to default before using physical button.

After Reset, Reader Connects But Start/Stop Doesn't Work

Symptom: Tag reads flowing, but hub Start/Stop buttons timeout

Check:

1. CAP running? (Reader web UI → Apps → Status)
2. MQTT config restored? (Reader subscribed to titan/v1/{serial}/commands?)
3. CAP log: Subscribed to commands?

Fix:

• Reconfigure MQTT (broker address, topics)
• Restart CAP after MQTT config restored

Best Practices

1. Before reset: Note current config-image mode (web UI → Settings → Advanced)
2. Default mode unless full wipe needed: default is safer (keeps identity)
3. Backup reader config: Export settings before reset (web UI → System → Export Config)
4. Document reason: Why resetting? (audit trail, troubleshooting notes)
5. Verify after reset: Check CAP + identity present (if mode = default)

When Reader Leaves Your Organization

Selling or returning reader:

1. Set mode to removecap
2. Factory reset (wipes CAP + identity)
3. Ask support or Wonder to release the reader in the operator console (unassigns tenant; does not revoke the certificate by itself)
4. Ship reader

Reader will not connect to your Titan account with the wiped identity. If support or Wonder has revoked the old certificate on the broker, MQTT reconnects with old credentials are blocked too.

Next owner: Reader is stock R700. If they want Titan, they provision it themselves (Wonder-shipped or BYO).

Summary

Goal	Mode	After Reset
Reset config, keep identity	default	CAP + identity intact; reconfigure MQTT
Full wipe (return to Impinj)	removecap	Stock reader; must re-provision if returning to Titan
Troubleshooting	default	Start fresh, don't lose provisioning
Decommission	removecap	Wipe all Titan traces

Default choice: default (safer, keeps identity)

Next Steps

• CAP Operations - Managing CAP in production
• Troubleshooting - Full troubleshooting guide
• Provisioning - How to re-provision after wipe