> 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/products/cc-software/troubleshoot/command-centre-errors/command-centre-errors-bad-input-parts.md).

# Bad Input - Parts reporting Bad Input

[Command Centre - Errors](/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors.md) › Bad Input - Parts reporting Bad Input

An alarm is raised with the controller reporting bad input messages. This is difficult to reproduce and the circumstances can vary.

![Bad Input alarm in the Alarm Viewer](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-5891ed6ada678db0f0926abae8ab8b6e2fa0da63%2FSECHUB-CCS-ERR-BAD-INPUT-01.png?alt=media)

## Logs needed

* Command Centre logs
* Controller logs
* The Controller's Application logs

> **Note:** GeneralOn should be enabled along with Trace.

## Log format to capture

```
2023-08-30T06:46:17.258+00:00 notice C6: Part Bad Input: From(B269 T8 P0 I21) To(B269 T8 P106 I1) Msg Class 7
```

**Field breakdown:**

* **Receiving side**, the item receiving bad input from the source: Part number, Input number.
* **Source**, the item generating the bad input: Bert# (controller number), Part number, Output number, Alarm priority.

## Find the faulty item

1. Web-browse to the controller and navigate to the **Parts Manager** and **Secondary Parts Manager**. Note the **Bert#**, which identifies which Controller 7000 it is, for example Controller #2.

![Parts Manager showing Bert# 2](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-30144bce538190dbafd1d9497d20b69417d89091%2FSECHUB-CCS-ERR-BAD-INPUT-03.png?alt=media)

2. Locate the **Source Part** number from the list, for example Part 87, a Relay Part.

![Parts Manager list with Part 87 identified](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-72e1ce75992d6f002ea9a5b1fa7589aee255bed4%2FSECHUB-CCS-ERR-BAD-INPUT-04.png?alt=media)

3. Click the Part for its properties. Note the **Point ID**; this is equivalent to the **FTItemID** in Command Centre.

![Part 87 properties showing the Point ID](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-0d394483890201cc8e3d1f689bd12fd8535e1cf0%2FSECHUB-CCS-ERR-BAD-INPUT-05.png?alt=media)

4. Use the **Find Tool** with two left square brackets `[[` followed by the FTItemID to locate the item in the Configuration Client.

![Find Tool locating the item by FTItemID](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-30e62c92e9278f5d2fd2b315e6f1abfdc04fd0b4%2FSECHUB-CCS-ERR-BAD-INPUT-06.png?alt=media)

## Workaround

1. Confirm the controller where the item is configured has the correct software version assigned.

![Controller properties showing the software version](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-0d196a3464a1e311dbaf4fd291da5119c5159f72%2FSECHUB-CCS-ERR-BAD-INPUT-07.png?alt=media)

2. Push the configuration on the controller.
3. If the issue still occurs, de-configure the item and create a new item to replace it.
4. Worst case, DIP2 the controller to lose its configuration.

## Optional: also de-configure the receiving item

For example Part 104, another Relay Part.

![Part 104, the receiving Relay Part](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-3902baebf2ffe2d3c8ecfad5ec35b35a566ceb71%2FSECHUB-CCS-ERR-BAD-INPUT-08.png?alt=media)

![Part 104 details](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-38078f700867f00f2be1027ef67f073491b1b1b4%2FSECHUB-CCS-ERR-BAD-INPUT-09.png?alt=media)

![Find Tool locating Part 104 by FTItemID](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-db40af4da78c2f0cd1e31b4d22f55cd8ab636b8c%2FSECHUB-CCS-ERR-BAD-INPUT-10.png?alt=media)

![Both controllers and all identified items in context](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-78ab5557ce877ba3c936a4190565834632e04a02%2FSECHUB-CCS-ERR-BAD-INPUT-11.png?alt=media)


---

# 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/products/cc-software/troubleshoot/command-centre-errors/command-centre-errors-bad-input-parts.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.