Check a card against the instructions for the actual camera, then distinguish recognition, recording, playback and saving a copy. A capacity label alone does not establish that the unit can use the card or that a particular visit has been retained. This is a matching checklist, not a universal card recommendation or formatting procedure.
Identify the unit, card and current task
Record the model/configuration, batch where available, supplied guide, app name/publisher/version, phone system and account role. Keep a complete card label or specification reference, including the physical type, capacity and relevant markings. Keep private identifiers out of public screenshots.
Say what you need to do: select a compatible card, understand a status message, locate an event, play it or save a copy. A problem at one stage does not identify the cause of a problem at another. Use Find the app and guide if the materials disagree.
Keep the model references separate
The limits below are what the reviewed historical editions state. They are not a list of approved current cards and do not establish every batch's formatting, speed or included-card requirements.
| Feeder | App & Wi-Fi | Guide note |
|---|---|---|
| V11 | VicoNature · 2.4 GHz only | The V11 0730 guide lists up to 128 GB. Follow its card-slot and cover instructions. |
| V9 | VicoNature · 2.4 GHz only | The V9 0818 guide lists up to 128 GB. Follow its card-slot and cover instructions. |
| V8 · Blue or Green | O-kam Pro · 2.4 GHz + 5 GHz | The V8 0729 guide lists up to 256 GB. Confirm the card type and format for your camera before purchase. |
| V10 | O-kam Pro · 2.4 GHz + 5 GHz | The V10 guide shows a microSD slot but does not establish a maximum capacity. |
| V5 | VicoNature · 2.4 GHz only | Card capacity for the current V5 is awaiting confirmation. |
| V7 | VicoNature · 2.4 GHz only | Card capacity is awaiting confirmation. |
| Adjustable Camera Feeder | VicoNature · 2.4 GHz only | Card capacity is awaiting confirmation. |
All six original card-page references show restoring the relevant silicone cover; V9/V11 also specify keeping its edges flush. This is not a shared disassembly, insertion or removal sequence for current units. The exact handling and power conditions need to be matched before those actions.
Other devices, batches and apps stay on their own branch. See the card-and-sharing reference CSV for the scope and open fields.
Check specification and handling before changing anything
Capacity, physical form, speed requirements and the permitted file system are separate questions. The SD Association capacity overview describes general card standards. It is not a Nafnti approval table or a camera-formatting method.
The original pages reviewed for this draft do not establish a complete current requirement for speed markings, file system, insertion/removal power state or formatting method for every configuration. Do not supply a universal FAT/exFAT choice, speed class, hot-swap rule or computer-formatting workaround from those gaps.
Before any insertion or removal, obtain the matched handling conditions and identify the correct slot, permitted access and cover-restoration method. Do not force a card, open an unmatched housing or improvise a damaged cover repair. For wet/damaged connections or an unsafe closure, pause the affected charging/outdoor reinstallation task and use the hardware charging reference.
Record recognition, recording, playback and export separately
Use the blank card-and-storage check. The sheet records the current setup; it does not require removing a card or creating a failure to complete it.
| Stage | What to record | What it does not prove |
|---|---|---|
| Card recognized | Actual message/status, date and matched app version | A visit was recorded or retained |
| Event located | Time, source and where it appears | It can be played or saved by every role |
| Playback works | Which event played and under which access conditions | An independent file exists |
| Saved file verified | Actual destination and successful playback outside the original history | The original card/cloud copy will remain available indefinitely |
If a stage fails, record the exact message and last successful stage. Use the missing-visit checklist for event-creation questions and Save and verify a bird visit for retrieval and file verification. Do not substitute a live-view Record action for exporting an earlier card event.
Keep no-card use and service entitlement distinct
If your device currently has no card, establish each function separately: live view, manual live capture, automatic events, cloud playback, alerts, AI and saving a file. Note the connection conditions, role and entitlement for each supported task. Leave an unperformed or unsupported check explicitly open rather than guessing from a menu label.
No card, no Internet and no paid plan are different conditions. Neither the presence of a Record control nor an AI offer proves no-card recording. Current behavior remains to be matched for the actual configuration. Do not remove a card, end a trial or clear history merely to test a buying question.
The service guide explains the concepts, and the model/service reference keeps older entitlements separate from current rights. Card capacity is not a number of guaranteed recording days; this draft supplies no retention or overwrite guarantee.
Preserve important clips before a destructive step
A request to format, initialize, clear or replace a card needs its own matched explanation: which source it affects, what will change and how important recordings can first be preserved. A prompt alone does not establish that formatting will fix the problem. No formatting, deletion, reset or account-removal procedure is given here.
Use a confirmed saving method and verify the intended files before treating a backup as complete. If the export path is not yet known, keep it unresolved and ask for that specific method. A support question can include the matched unit/app, card specification, exact message, last successful stage and source recording, without exposing credentials or pairing codes.