> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/nedap-readers/nedap-booster-desfire-feature/command-centre-nedap-booster-configuration.md).

# Command Centre Nedap Booster configuration

This section details the standard Command Centre configuration required to use Nedap Booster devices and TRANSIT readers with Command Centre.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [1. Configure Nedap Transit readers as third party readers](#id-1.-configure-nedap-transit-readers-as-third-party-readers)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [2. Configure vehicles as Cardholders](#id-2.-configure-vehicles-as-cardholders)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [3. Configure Dual Authorisation](#id-3.-configure-dual-authorisation)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [4. Configure the Universal Card Format](#id-4.-configure-the-universal-card-format)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [5. Creating cards for cardholders and/or vehicles](#id-4.-configure-the-universal-card-format-1)

#### 1. Configure Nedap Transit readers as third party readers

Nedap TRANSIT readers are configured in Configuration Client as third party readers and assigned to the appropriate Controller and Door.

1. Create a third party reader.

   **Note:** The [Creating Readers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-readers.md) topic provides detailed instructions for creating a third party reader.

   On the **Type** tab of the Reader properties, add a card format to the third party reader from the **Format** drop-down list (NedapDesfire).

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-05279733c3d64b24c0de4f1ea83e54bc30528ed4%2Fthirdpartyreader_typetab_nedapdesfire.png?alt=media)

   **Note:** This option is only needed for MIFARE DESFire cards. Classic cards can work with any format.
2. Open the properties of the Controller that has the Nedap TRANSIT reader connected to it, and click the **Readers** tab.
3. Assign the third party reader to the appropriate slot, depending on how you wired it to the Controller, or HBUS Wiegand Reader port.
4. Click **OK**.
5. Assign the third party readers to the appropriate Door items’ **Entry Zone** tabs.

   Refer to Creating Doors for further detail.

#### 2. Configure vehicles as Cardholders

Vehicles can be configured as Cardholders in Command Centre to allow the vehicle to be assigned a "card" so it can be granted access. The vehicle's "card" is really a Nedap Booster. When the vehicle approaches a Nedap TRANSIT reader, it presents its Nedap Booster to the reader, and the vehicle is either granted or denied access.

1. Create a new Cardholder to represent the vehicle.

   Refer to [Adding a new Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/adding-a-new-cardholder.md) for the procedure.
2. Assign the vehicle Cardholder to the appropriate Access Group containing vehicle Cardholders.

   If you have not created one yet, refer to [Setting up Access Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/setting-up-access-groups.md) for the procedure.
3. Assign the vehicle Cardholder a card to represent the vehicle’s Nedap Booster.

   Refer to [Adding a Card to a Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/adding-a-card-to-a-cardholder.md) for the procedure.

   **Notes:**

   * The **Number** field (on the **Cards** tab of the Cardholder properties) must be the Nedap Booster’s ID number. The ID number is printed on the back of the Nedap Booster device.
   * You can configure the booster to only transmit the Driver ID using the Smartcard Booster Config application.

#### 3. Configure Dual Authorisation

An Access Zone that vehicles enter can be configured with Dual Authorisation. This means access is only granted if the vehicle provides **two** means of authorisation: a credential (Nedap Booster) held by a Cardholder (vehicle) from the vehicle Access Group and a credential (card) held by a Cardholder (person) from the driver Access Group.

Perform the following procedure to configure an Access Zone so it requires a valid vehicle and driver to grant access (Dual Authorisation):

1. Click **Configure** from the menu bar, then **Access Zones**.

   The Access Zone List Window opens.
2. Right click on the Access Zone that will require a valid vehicle and driver for access to be granted, and select **Properties**.

   **Note:** If you haven’t yet created the Access Zone, create one using [Adding a new Access Zone](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/adding-a-new-access-zone.md) for the procedure.
3. Click the **Dual Authorisation** tab.
4. From the **First Card** drop-down list, select the Access Group (that contains the vehicle Cardholders) that you wish to access this zone.
5. From the **Second Card** drop-down list, select the Access Group that contains the drivers you want to access this zone.
6. Ensure the Access Zone’s Access Mode is set to 'Dual Auth - No PIN' during the times Dual Authorisation is required. Do this by either: \*
   * configuring and applying a 'Schedule' on the **Access Mode** tab of the Access Zone, OR
   * * overriding the zone to 'Dual Auth - No PIN' on the **Status and Overrides** tab of the Access Zone.
7. Click **OK** to close and save your changes.

#### 4. Configure the Universal Card Format

**Note**: The [Adding a new Universal Card Format](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/universal-card-format/adding-a-new-universal-card-format.md) topic provides detailed instructions for configuring a Universal Card Format (UCF).

1. On the **Format** tab of the UCF, select the **Wiegand** radio button and ensure the following fields are populated as follows:

   <table><thead><tr><th width="171">Field</th><th>Value</th></tr></thead><tbody><tr><td><strong>Number of Bits:</strong></td><td>40</td></tr><tr><td><strong>Bits in Facility Code:</strong></td><td>0</td></tr><tr><td><strong>First Bit of Facility Code:</strong></td><td>N/A</td></tr><tr><td><strong>Bits in Card Number:</strong></td><td>24</td></tr><tr><td><strong>First Bit of Card Number:</strong></td><td>17</td></tr><tr><td><strong>Facility Code:</strong></td><td>Select the facility code on the Card Type that will be used when you create cards for cardholders/vehicles later.</td></tr></tbody></table>

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-59fc200144fc842a90ade72da233ae71b19b227f%2Fnedaptransit_ufc.png?alt=media)
2. Open the properties of each Controller connected to a Nedap TRANSIT reader, and click the **Card Formats** tab.
3. Assign the UCF you have just created by dragging it (or using copy and paste) into the grid on the **Card Formats** tab.

#### 4. Configure the Universal Card Format

Create cards for each of the cardholders and/or vehicles as required.

See [Adding a Card to a Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/adding-a-card-to-a-cardholder.md) for the complete procedure.

**Note:** When using Transit Readers, ensure that the Card Type selected uses the same Facility Code as the new Universal Card Format you created earlier.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/nedap-readers/nedap-booster-desfire-feature/command-centre-nedap-booster-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
