> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-nordics/p400-two-piece-sa/errors/terminal-is-ready-waiting-for-ecr-connection.md).

# Terminal Is Ready, Waiting for ECR Connection

What to do when a P400 Two-Piece shows Terminal is ready, waiting for ECR connection — reconnect the operator and customer units.

{% hint style="info" %}
**Use this page when** your P400 Two-Piece shows **"Terminal is ready, waiting for ECR connection"** and the operator unit and customer unit aren't communicating with each other.
{% endhint %}

<details>

<summary>Keywords</summary>

Also called: waiting for ECR connection, terminal is ready, ECR not connected, operator unit not connecting, customer unit not connecting, two-piece not connecting. Search terms: ECR, waiting for ECR, IP address, ECR port, 9600, operator unit, customer unit, communication device.

</details>

## Symptoms

You may see one or more of the following:

* The terminal displays **"Terminal is ready, waiting for ECR connection"**.
* The operator unit and customer unit don't respond to each other.
* Transactions can't be started from the operator unit.

**Most likely cause:** the customer unit doesn't have the operator unit's correct IP address or communication settings, or the units aren't connected to the same network.

## Before you start

Your P400 Two-Piece has two units:

* **Operator unit** — the unit at the till.
* **Customer unit** — the unit the customer uses to pay.

To connect them, you'll find the operator unit's IP address, set its communication settings, then enter that IP address on the customer unit.

* Make sure the terminal is connected to your network by **network cable** or **Wi-Fi**.

## Resolution

{% stepper %}
{% step %}

### Check the operator unit is connected to the network

1. On the operator unit, press **#** to open the menu.
2. Select **Administration > Settings > Communications**.
3. Check whether **LAN** or **Wi-Fi** shows as **UP**.

* **If one shows UP:** note which one it is and continue to the next step.
* **If neither shows UP:** the terminal isn't connected to your network. Connect it first using [How to Connect the Cables](/support-nordics/p400-two-piece-sa/how-tos/how-to-connect-the-cables.md) (network cable) or [How to Set Up Wi-Fi](/support-nordics/p400-two-piece-sa/how-tos/how-to-set-up-wi-fi.md) (wireless), then start again.
  {% endstep %}

{% step %}

### Print the operator unit's IP address

1. Select **More > Status > IP addresses**.
2. Select the connection you're using (**LAN** or **Wi-Fi**).
3. Press **Print** in the bottom-right corner. Keep this receipt — you'll need the IP address in Step 4.
4. Press the **red button** until you're out of the menu.
   {% endstep %}

{% step %}

### Set the operator unit's communication settings

1. Press **#** to open the menu.
2. Select **Administration > Settings > ECR > Set ECR Address**.
3. Check the address is **0.0.0.0**, then press the **green button**.
4. Select **Set ECR Port**. Check it shows **9600**. If it doesn't, enter **9600**, then press the **green button**.
5. Select **Choose comm. Device**:
   * **Ethernet#0** if the terminal uses a network cable.
   * **Wi-Fi** if the terminal uses a wireless connection.
6. Press the **red button** until you're out of the menu.
   {% endstep %}

{% step %}

### Enter the IP address on the customer unit

1. On the customer unit, press **4** and **6** at the same time, then enter password **1234**.
2. Select **Administration > Settings > ECR > Set ECR Address**.
3. Enter the IP address from the receipt you printed in Step 2 (shown under **IPV4 IP address**).
   * Use the number keys for the digits and the **\*** key for each dot.
4. Press the **green button**.
5. Select **ECR Port**. Check it shows **9600**. If it doesn't, enter **9600**, then press the **green button**.
6. Select **Choose comm. Device**:
   * **Ethernet#0** if the terminal uses a network cable.
   * **Wi-Fi** if the terminal uses a wireless connection.
7. Press the **red button** until you're out of the menu, then try a transaction.

{% hint style="success" %}
**The units are connected when** the screen shows **Verifone** on a white background and the **"Waiting for connection"** message has gone.
{% endhint %}

✅ **Issue fixed — stop here.** ❌ **Still not working — continue to Step 5.**
{% endstep %}

{% step %}

### Check both units are on the same network

1. On each unit, go to **Communications > More > Status > IP addresses**, then select **LAN** (or **Wi-Fi**).
2. Compare the two IP addresses. The **first three numbers** should be the same:
   * ✅ Same network: 192.168.1.43 and 192.168.1.36
   * ❌ Different networks: 192.168.1.42 and 192.168.2.46
3. If they're different, make sure both units are connected to the same router or Wi-Fi network, then repeat Steps 2 to 4.

✅ **Issue fixed — stop here.** ❌ **Still not working — contact Support below.**
{% endstep %}
{% endstepper %}

**If a transaction now works.** The units are connected. No further action needed.

**If the units still won't connect.** Our team can run further checks on the terminal's network and security settings — contact Support below.

## Still not working?

{% hint style="info" %}
**Still need help? Contact Verifone Support.**

If the steps above haven't resolved the issue, <mark style="color:red;">contact Verifone Support</mark>. Tell us the troubleshooting steps you've already tried — it helps us get you to the right support faster.
{% endhint %}


---

# 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://docs.verifone.com/support-nordics/p400-two-piece-sa/errors/terminal-is-ready-waiting-for-ecr-connection.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.
