A better understanding.
A better day on board.

Follow the setup guide and check the live connection and freshness indicators.

When safely at the boat, compare a few readings against your onboard instruments with matching units. Keep using your normal navigation and safety equipment.

Report what you expected, what happened, the steps to repeat it, and app/firmware versions. Include the instrument make/model when a device or reading is missing from NMEA Hub.

For a missing NMEA device, use Record CAN traffic over local Wi-Fi. Review the privacy notice, deliberately record a short sample, and explicitly send the saved recording. This lets Fisho investigate and add decoding where possible.

Keep the Received reference and use it in follow-up chat. Saved on phone is not confirmation that the team has your report.

Install or update Fisho and sign in while your phone has internet. Open Boat. If you have not connected an Atlas Mini, choose Already have one? Set it up, then Start setup. An existing owner may see Connect your Atlas Mini or Continue setup instead.

Have Atlas Mini installed on your boat’s NMEA 2000 network using the instructions for your hardware. Power the network; Atlas Mini starts automatically. In Fisho, tap Find my Mini. Your phone needs internet to register the device.

Keep your phone close to Atlas Mini, turn on Bluetooth and allow Fisho’s requested permissions. Select your Atlas Mini in the app, not in the phone’s Bluetooth device list. Wait for the connection to complete, then continue. Resolve an ownership or saved-key error before going further.

On Your boat, confirm the boat shown or enter its name. Enter the owner name and tap Continue. These details help you recognise the right boat and device later.

If Save access key appears, follow it. Keep your phone online until Fisho saves the key. Choose On-board Wi-Fi or Phone hotspot, enter the 2.4 GHz details and tap Connect. Use Bluetooth only is optional when offered. After setup, add home and boat networks in Boat Wi-Fi; home Wi-Fi works only while Atlas Mini is within range. If Already online appears, continue or choose Use a different network.

When setup finishes, keep the backup Wi-Fi password somewhere private if one is shown. Tap Done, then check the Boat tab for the actual connection and fresh readings from powered instruments.

Confirm Atlas Mini has power, enable Bluetooth on the phone and move close to it.

In the phone’s system settings, allow Bluetooth for Fisho. On Android, check the nearby-device permissions requested by your app/OS version. If Wi-Fi is used on iPhone, also allow Local Network access.

Return to the Fisho setup or connection screen and retry discovery. Check the selected Atlas Mini is yours when more than one appears.

If Fisho reports an ownership or access-key problem, use the account that registered this Atlas Mini and the existing recovery flow. Repeatedly scanning will not resolve another account’s ownership.

If the phone connects but readings are absent, continue with “Connected, but no boat data” instead of resetting the Atlas Mini.

For a new Atlas Mini, choose your connection in setup. For an existing Atlas Mini, open Boat Wi-Fi from Boat or Atlas settings. Add home, boat or hotspot networks using Add network; see the multiple-network guide for saving, switching and forgetting.

Check the exact network name and password. Use the compatible 2.4 GHz network; on iPhone hotspot, enable Allow Others to Join and Maximise Compatibility.

Keep the hotspot available while Atlas Mini joins. Wait for the displayed network status rather than assuming the details were accepted because the form closed.

For local Wi-Fi access, the phone must be able to reach Atlas Mini on that network. Guest/client isolation can prevent this even when both devices have internet.

Where Bluetooth-only is supported, nearby readings can work without boat Wi-Fi. Cloud sync, remote notifications and fresh weather need the appropriate internet connection. This bundled guide can be read offline; cloud chat cannot.

Read the Atlas connection and data status. Distinguish live data from recorded or simulated traffic and from older cached readings.

Confirm the relevant instrument and NMEA network are powered. Use the instrument’s own display to check whether it is producing the expected value.

Open NMEA Hub in Atlas settings to inspect observed sources and categories. Seeing a source does not prove it sends every reading the dashboard supports.

Check the reading’s source, units and freshness where shown. Battery voltage from an engine feed and a separate battery monitor may describe different supplies.

If a value is missing or wrong, report which reading, its units, the instrument model and what its own display shows. A missing value is not zero; a stale value is not a new measurement.

Check the number label and the gauge label separately. The standard Main layout can show GPS speed beside an RPM gauge; they intentionally represent different readings.

Check that engine data is available in NMEA Hub. A functioning GPS feed does not establish an engine connection.

For multiple engines, inspect the source and engine instance associated with the reading. Do not assume instance 0 is port without checking the installation.

Compare RPM with the relevant engine display. Check units and freshness before treating a difference as a decoder error.

If the wrong engine or no engine is shown, include the observed engine instances and expected engine in the report. Keep unsupported or absent readings unavailable.

Read both labels: the standard Main fuel number shows burn; its gauge shows tank level.

For total fuel burn, confirm all expected engines have fresh flow data. A partial set of engines is not a verified total; check any completeness indicator.

Check the tank source and instance separately. Engine fuel flow does not supply a tank-level percentage.

Compare each engine’s flow and each tank’s level with the appropriate onboard display, using matching units.

When reporting a mismatch, state the number of engines/tanks, selected source, units and the independent values. Do not treat a missing engine as consuming zero.

Open the screen editor from Atlas and select the page to change. Use Add reading or an available grid area to choose a reading or Fisho card.

Choose a supported size that fits the free area. Larger forecast, tide or trip cards can show more detail; a card still needs contiguous free cells.

Save your changes before leaving the editor. Layout settings → Use standard layout restores the standard arrangement, so review it before saving over your custom page.

Tap Forecast or Tides on the dashboard to open weather details, and Trip summary to open the relevant trip view.

Check the location and age shown on weather cards. Forecasts and tides are not measurements received from the Atlas Mini’s NMEA feed.

Check that the Atlas Mini reports trip-tracking support and that the required live GPS/engine inputs for its recording configuration are available.

Watch the active trip and fresh GPS position while travelling. A connected Atlas Mini with no valid GPS does not establish a usable track.

Open Atlas Trips to inspect recorded trips, their map, timing and available statistics. Missing points or readings should remain gaps.

Check the shown sync status. Atlas Mini can sync directly to cloud when it has internet; phone presence is not inherently required for that route.

On supporting firmware, an ended trip is saved to a bounded device outbox before it is cleared as active. Keep Atlas Mini powered with internet to upload it. Atlas Trips distinguishes waiting on Mini, server acknowledged and cached app data.

Pending saved route points can be viewed locally over Wi-Fi. Missing or dropped points remain gaps. A restart during an active trip loses its RAM-only unsent route points; the screen reports reduced coverage.

Use Retry for a transient upload failure. Registration errors need pairing/account attention. Discard or repair permanently removes the selected local evidence and requires confirmation; do not reset Atlas Mini to clear a backlog.

Open Automations and check the rule is enabled, its selected reading/source is available and its threshold and units match your intention.

Check the reading is fresh. An absent or stale input is not evidence that the threshold was crossed.

Connect over Wi-Fi and open the saved rule preview to inspect its current inputs, conditions and actions without executing them. Unsaved editor changes are not part of this preview.

Run saved automation is a separate, explicitly confirmed action. It performs real saved actions with the saved conditions, even if automatic triggering is disabled. A changed rule requires another preview; never repeatedly retry an unconfirmed action.

Inspect Atlas Mini history for skipped conditions, completed, deferred or failed actions. A multi-action rule can partially complete before an error. Sent to the Bluetooth chip or accepted by cloud is not proof that your phone displayed a notification.

For phone alerts, allow Fisho notifications in system settings and consider Focus/silent settings. Remote delivery also requires the relevant internet path.

Test notifications and non-actuating rules first. Never treat a chat reply or a simulated preview as confirmation that physical switching occurred.

Open Atlas settings and inspect whether Dock Watch or Anchor Watch is available for the connected device.

For Dock Watch, check the last heartbeat and its age. A cached boat position is not a current position.

For a local anchor watch, confirm the position is valid before using the existing set-anchor action. Review the anchor point and alarm radius shown.

When leaving the boat, check the Atlas Mini has a continuing power and internet path for supported remote alerts. Your departing phone hotspot does not remain on board.

Treat missing or stale watch data as unknown. Check the boat through an appropriate independent method when needed.

Open Atlas settings → Settings recovery. With internet and a Wi-Fi connection to your registered Atlas Mini, save the current setup. Only the latest three private account backups are kept.

A backup contains saved screens and compatible automation definitions. Passwords, pairing/access keys, trip tracks, transient source addresses and geofence rules are not included. Read the omission list before saving.

On a replacement phone, sign in to the same Fisho account, select the registered Atlas Mini and reconnect through the existing pairing/recovery flow. Do not remove ownership just because the phone changed. Your account-backed unit preferences are separate from the screen backup.

Preview a backup before restoring. Existing Atlas Mini rules remain. Newly copied rules start disabled and cannot trigger during restore. A matching rule restored earlier keeps its current enabled state; other edits to that rule cause a conflict instead of being overwritten. To restore that backup again, first revert the edited copy or explicitly remove that copy through Review saved rules and storage. Missing switch controls or unsupported rules are omitted visibly. Review engine instances, reading sources, switches and schedule offsets before enabling each copied rule.

Save or discard any open screen edits first. If the connection drops or Atlas Mini changes during restore, read the partial-result message. Preview the same backup again to retry; its restored rule IDs are stable and existing edited rules are never overwritten.

Atlas Mini has a 4,096-byte encoded settings capacity and needs free space to replace its saved value safely. Older larger configurations continue to load. If a save is too large or storage is full, use Settings recovery → Review saved rules and storage to remove selected unused rules together in one save. If Wi-Fi recovery cannot save an oversized setup, the Atlas Mini AP or USB service route can be used by support to trim saved network profiles; do not reset to clear the error.

Crew membership does not transfer ownership. It controls trip and position sharing only; it does not grant access to Atlas Mini, its backups or pairing keys. For a sale or owner change, resolve pending trip uploads first, then follow the owner removal and device-reset/setup process; a settings backup is not an ownership-transfer tool.

Connect to your Atlas Mini and open Atlas settings → Firmware update to inspect the reported version and update state.

If the app says updating is unavailable or blocked, read that reason. Do not bypass compatibility checks or use a firmware image intended for another board.

For an eligible update, provide stable power, follow the installation prompt and keep the required connection available. Wait through restart and reconnect.

After reconnecting, confirm the installed version and healthy status. “Uploaded” alone does not prove the new firmware booted successfully.

If installation fails or the device returns to an older version, record the status and versions and ask support. Check capabilities again after reconnecting or rollback. Do not attempt to install a version rejected by the compatibility checks.

For a replacement phone, sign in to the account that owns the Atlas Mini and use the existing pairing/recovery flow.

Check which registered device is selected when an account has more than one Atlas. A different Atlas Mini must not reuse another device’s credentials.

For a new owner or a device registered elsewhere, contact the existing owner/support and follow the ownership flow offered by the app.

Before removing registration, resetting or changing credentials, read the confirmation explaining what that action deletes. Do not reset merely to troubleshoot a missing sensor.

Keep access keys and network credentials private. Do not paste them into chat, bug notes or screenshots.

Open Help & diagnostics → Report a problem. Describe the screen, steps, expected result and actual result. Never include passwords or access keys.

Review any optional app/connection details before including them. They are observations from the phone, not proof of hardware state.

Send the report. If delivery fails, use the saved report’s Retry action when internet is available; do not create another copy of the same report.

Only Received with a server reference confirms delivery. Saved on phone means Fisho has not yet acknowledged receipt. You can remove an unsent report from the phone.

A reading report from NMEA Hub is separate evidence and may include raw frames, your GPS position and nearby vessels’ identifiers/positions. Read its disclosure first. The recent-frame buffer is not a 30-second capture.

Open Atlas settings → Record CAN traffic, or choose it from NMEA Hub or Report a problem. Connect the same account and Atlas Mini over local Wi-Fi; Bluetooth alone cannot transfer a full recording.

Describe what is wrong and what should happen. Read the privacy notice: raw CAN can contain positions, vessel identifiers, nearby vessels and proprietary instrument data. Accept it before starting.

Tap Start 30-second capture. Atlas Mini stops automatically even if Fisho closes or the phone disconnects. Stop early keeps an explicitly incomplete recording; Discard deletes it.

Keep Fisho open while it verifies and retrieves the recording. If interrupted, reconnect the same Atlas Mini/account and tap Resume. Atlas Mini keeps the finished copy in RAM for 30 minutes; restarting or losing power before retrieval loses that copy.

Review the saved result. No traffic, incomplete and observed input have different meanings. Ordinary Atlas Mini functions keep running; missed driver frames and decoder-queue drops are reported separately.

Connect to internet and tap Send report and CAN recording. Only Received with a server reference confirms delivery. Retry the saved item after a delivery error rather than starting another recording.

Up to two unsent recordings are kept on this phone. Their raw evidence expires after 7 days when Fisho next opens or returns to the foreground, while the description remains. Fisho retains submitted raw evidence privately for 30 days from confirmation; deletion runs asynchronously.

Check the model and hardware revision on your unit and its supplied installation information. If ratings or limits are missing, ask Fisho before installation; do not copy them from another revision.

Check the package contents against your order. Arrange the compatible network connection parts your installation needs; do not assume a drop cable, T-piece, terminator, mounting screws or power supply is included.

Have a suitable marine installer check the network power budget, connection, mounting position, cable support and protection from water and heat. Isolate network power before making or changing connections.

Keep existing network termination and protective devices intact. Never force a connector. Use only the power connection specified by the approved installation information for your exact unit; do not improvise a supply or add a power feed.

Secure Atlas Mini and its cable so neither can move or strain the connector. Do not open the enclosure. Restore network power only after the installation is checked, then begin setup in Fisho.

Inspect the enclosure and supported cable occasionally. Keep them clear of water exposure and heat beyond the approved installation limits. Clean the exterior gently with a dry soft cloth; do not spray, immerse or open the unit.

If Atlas Mini becomes unusually hot, smells, emits smoke, is damaged or repeatedly resets, stop using it and safely isolate its supply when possible. Contact Fisho before reconnecting. Use normal vessel safety procedures if there is an immediate hazard.

If readings are implausible or interference appears, rely on the vessel’s normal instruments, record the symptom and get the installation checked. Do not change vessel safety systems to make Atlas Mini work.

Before removal or sale, review pending trip uploads and save any settings you need. Ask Fisho about owner removal and the reset process for your exact unit. Removing an app record or inviting crew does not erase the hardware or transfer its owner.

Have the network connection safely removed with power isolated and its termination preserved. Keep credentials private and use an appropriate local electronics recycling service for disposal.

Sign in with your normal Fisho account. Enter the boat Wi-Fi or hotspot password only in the network step when choosing that connection.

At the connection step, follow Save access key if it appears. Keep your phone online until Fisho saves the key. If saving fails, retry or contact Fisho before continuing; do not abandon the prompt or post a key in chat.

If the final setup screen shows a backup Wi-Fi password, keep it privately. It belongs to Atlas Mini’s own backup network, used when Atlas Mini cannot reach the saved network. It is not your Fisho account password.

For an existing unit, use the owning account and the recovery flow. If a saved key cannot be recovered, contact Fisho. Do not guess a universal default password or erase the device to get around ownership.

Before sending screenshots for help, crop or cover passwords and access keys. Never put them on the printed setup card or in a shared boat record.

Stay near your Atlas Mini. Open Boat Wi-Fi from Boat or Atlas settings. Use the owning account and connect Bluetooth when prompted; Atlas Mini protects network changes. The Atlas Mini’s own hotspot is another supported password-entry route when Fisho offers it. An ordinary boat-LAN connection alone cannot submit new Atlas Mini Wi-Fi passwords.

Choose Add network. Enter the exact 2.4 GHz network name and password, then Save. Add your boat network and your home network separately. Home Wi-Fi is useful only when Atlas Mini is within range, for example with the boat on its trailer at home.

Read the result. On a compatible Atlas Mini over Bluetooth, Add network can save the profile while keeping the current connection. On a route that switches immediately, follow the handover screen. Saved is not the same as joined.

To change networks, choose the saved network and follow the switch confirmation. Atlas Mini can retain its saved password; enter a changed password only when needed. Join that network on your phone for local Wi-Fi access and wait for the actual connection check.

Confirm the target is marked Current network. Test an online feature separately if internet is needed. Do not assume Atlas Mini automatically roams to whichever saved network is strongest or available.

To forget a network, connect Bluetooth and use its trash control. Check the warning before removing the current or last network. Keep another working route; removing a profile cannot repair a wrong boat account.

Ask your CZone installer or dealer to confirm the module model, firmware, configuration access and third-party switching support. If the configuration is locked or its origin is unclear, have that installer make the change.

For the memory-card workflow, prepare a Windows computer, current CZone Configuration Tool, a card reader and the SD/microSD card or USB media supported by your exact display. Use the display maker’s export/import procedure. Some systems instead require an approved CZone USB-to-CAN interface; a memory card is not universal.

Export or read the working boat configuration and save an untouched dated .zcf backup. Work on a separate copy. Record the current module/display identities and the installer’s recovery procedure before editing.

Use the current CZone download portal for tools and documentation. Older direct download links may redirect to its new account-based portal. Match instructions to your hardware; do not install an arbitrary firmware just because an old integration PDF names it.

Choose one non-critical comfort circuit for the first test, such as an interior cabin light. Keep pumps, navigation lights, horns and other safety functions out of trial automations. Keep their normal controls available.

On a working copy in the CZone Configuration Tool, use the Third-Party Devices / Switch Bank PGN Control area where supported. Have the installer add or select the appropriate virtual bank and supporting module, using an unused bank instance.

For the chosen circuit, review Circuit Controls and map the intended virtual-bank channel. In the momentary-toggle workflow, the control uses Single Throw Momentary and Toggle On/Off. Record the circuit name, bank instance, channel and control type together; do not guess from another boat.

Save the edited .zcf under a new name. Have the installer validate it, then load/write it through the exact display/media or configuration-interface procedure for that system. Do not interrupt the write or overwrite your only working backup.

After the system is stable, verify the original display/keypad still controls the intended circuit and other normal controls still work. Only then open Fisho Switches and identify the corresponding observed bank/channel.

If the circuit or original controls behave unexpectedly, stop testing and have the installer restore the verified backup using the documented recovery procedure. Do not repeatedly flash different files or send guessed switch commands.

Connect to your Atlas Mini and open Switches in Atlas settings. If Switch control unavailable appears, read the reason: physical NMEA support, write permission and supported switching capability all matter. Do not bypass a disabled control.

Open switch setup/discovery. Compare the reported bank and channel with the installer’s configuration record. Use Add beside the matching channel, enter a clear name and save. Do not invent a bank/channel or identify a load by toggling random channels.

Set CZone pulse control to match the actual configuration. Leave it on for the documented Contact 6/keypad-style momentary workflow, even if the lamp itself stays on. Turn it off only for a bank documented to accept direct latched commands. Require confirmation adds protection against accidental taps.

With someone safely observing a non-critical circuit, confirm its current physical state and fresh on/off feedback. Make one deliberate change. Check the physical load, original control and reported state all agree before adding the switch to an automation.

Unknown, fault or stale state is not off. Atlas Mini refuses unsafe momentary toggles without a known on/off state. Wait for fresh feedback and check the mapping; do not force a command or repeatedly retry an unconfirmed result.

If Fisho reports that a command was not confirmed, stop and check the physical load and feedback. A sent command is not proof of a changed circuit. Remove a wrong Fisho mapping only after reviewing any automation that uses it.

Connect to Atlas Mini and open Automations. Choose Create automation. If runtime or builder controls are locked, reconnect and resolve the stated capability requirement first.

Choose Trigger, then add any Condition with a real source, operator and units. For a threshold, use a value appropriate to your own equipment and operating plan; never copy an arbitrary voltage or temperature from a tutorial.

Choose Action or Add Step and start with App Notification or Log Event. Enter clear text. Only choose actions offered for this Atlas Mini; full Atlas voice/announcement actions require audio hardware.

Review the enabled state, trigger, conditions and actions, then Save. Reopen the saved version and check it matches. A draft or an app-only change is not proof Atlas Mini saved it.

Over supported Wi-Fi, inspect the saved preview: inputs, freshness, conditions and proposed actions. It does not execute. Unsaved edits are not included.

If you deliberately use Run saved automation, read its confirmation: it performs real saved actions, can run a disabled rule, and still evaluates saved conditions. A multi-action rule may partly succeed. Inspect history and any phone receipt separately.

Enable the intended automatic trigger only after verifying the saved rule. A manual run tests actions/conditions, not whether the real-world trigger will fire. Observe the genuine trigger safely; never create a dangerous condition to test a rule.

Battery observation: choose On Threshold, the correct battery reading, units and an equipment-appropriate threshold, then App Notification. Start with notification only; compare with the battery monitor. A missing reading is not a low reading.

Engine-start reminder: choose On Engine Start and App Notification or Prompt Start Trip when offered. Check a fresh RPM feed first. An Atlas Mini booting while the engine is already running may only establish a baseline; it need not create a start event.

Cabin-light convenience: first commission a non-critical switch in Switches. Then use an appropriate offered trigger, deliberate conditions and Switch On/Off targeting that saved switch. Review pulse/latched behaviour and observe the physical outcome on board.

Before saving any example, read its actions as a sentence: when this trigger occurs, if these conditions hold, perform these actions. Remove anything you cannot explain or safely observe.

Inspect the saved preview and actual history. A manual action run does not prove threshold timing, an engine transition or a scheduled trigger. Test those through safe normal operation, not by creating a fault.

Allow Fisho notifications on the phone and review Focus, silent and battery restrictions. Sign into the intended account and verify the relevant saved automation or watch is enabled.

Check the actual input and event. A stale reading, missing RPM transition or unsatisfied condition can correctly prevent an action.

Inspect automation history or the watch’s current state. Distinguish skipped, failed, deferred and completed stages. Device completion is not proof of a visible phone notification.

For away-from-boat alerts, keep Atlas Mini, its needed network/instruments and a working boat internet connection powered. A departing phone hotspot removes that route. Bluetooth alone is not remote internet.

Use a non-actuating test and confirm the intended phone receives it. Record both the event time and receipt time. If delivery fails, report which stage is known and which is missing.