Skip to content
Contact support
  • There are no suggestions because the search field is empty.

nimbusGo panel guide: Ziton ZP3

Equipment required

From Nimbus

From the panel manufacturer/3rd party

  • n/a.

 

Panel configuration

  • Press [Menu] 
  • Select [option 3 Setup]
  • Enter commissioning code
  • Select [option 6 System Configuration]
  • Select [option 3 Peripheral Communication]
  • Select [option 1 Communications parameters]
    • Set Z-port to 1
    • Choose protocol:
      • [04] ZCP2 (Single & Text) – For panels running 3.11 or later
      • [07] ZCP2 (Single+) – For panels on pre 3.11
    • Set the baud to 9600 and frame to 8N1.

Note: Z-Port 1, if used for configuration, the protocol of the port will default to EVEN parity. Check this setting if you see events issues appearing in the event log, on the nimbus portal.


Panel connection

Connect nimbusGo to Z-Port 1 on the mainboard with the 2m Adapter Lead and Multi Panel (Tx, Rx, Gnd) Panel Adapter.

You will now see the panel LED on nimbusGo turn green, and "good" panel comms will be indicated in Nimbus Engineer.

Learn more: Servicing equipment with Nimbus Engineer


Common issues

Zone Walk Test

In walk test mode, the ZP3 does not output events to Z-Port 1 and so will not send events to Nimbus. You must isolate/disable all output devices before testing and leave walk test mode disabled.

Before leaving site

The protocol must be set to [00] upon completion of servicing with nimbusGo. If the Protocol is left as [04] or [07], the panel will attempt to buffer new events, which will then be downloaded when a nimbusGo is next connected – usually at the start of the next visit.

Events issues

I keep getting the same event being communicated to Nimbus continuously!

The panel is transmitting each event 10 times until an acknowledgement is received from Nimbus, and then it will send the next event. This issue appears when the wiring (panel communication) from the mainboard to Nimbus hardware is faulty or incorrect. To resolve this, check the wiring is secure and fault free.

The panel is continually reporting different events!

The panel buffers events within the onboard memory if the protocol is set to anything other than protocol [00] after being serviced on a previous visit. There is no way to stop this data dump, other than wait until it completes the output of stored information. No real time servicing recording via Nimbus can begin until this completed.

The panel is reporting the same event at a very high frequency!

This is a known issue with this panel model, where a protocol corruption has occurred. Power cycle the fire panel to fix this issue.