CZone, step by step.

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.