> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/fuel-dcr-help/fuel-dcr-help/dcr-help/dcrs-over-ethernet-oemv-or-serial.md).

# DCRs over Ethernet(OEMV) or Serial

If **DCRs** remain unresponsive after [Poll Error Troubleshooting](/fuel-dcr-help/fuel-dcr-help/dcr-help/please-pay-inside-e01-poll-error.md), use the flow below based on channel type.

{% hint style="info" %}
If you still need to confirm OEMV vs Serial, follow the **connection type** checks in [Poll Error Troubleshooting Guide](/fuel-dcr-help/fuel-dcr-help/dcr-help/please-pay-inside-e01-poll-error.md).
{% endhint %}

***

### If DCRs are over Ethernet (OEMV)

{% stepper %}
{% step %}

### Check Online/Offline state in Forecourt Diagnostics

Use Forecourt Diagnostics to confirm whether DCRs are **Online** or **Offline/Not located**.

{% hint style="success" %}

### **Forecourt status (OEMV / Ethernet)**

Use this to confirm whether each **DCR** is communicating with the **Site Controller (Commander)**.

In **Config Client**, go to:  

<kbd>Tools</kbd> → <kbd>Helpdesk Diagnostics</kbd> → <kbd>Forecourt</kbd>

For each **DCR**, confirm:

* **Located** → shows the **DCR number**.
* **Status** → shows **Online** (communicating).

If the DCR is missing, not located, or shows **Offline**, the DCR is not communicating.&#x20;

{% endhint %}

<div align="left" data-with-frame="true"><figure><img src="/spaces/FYWyfZfb6YnJEuYJDRqw/files/9OloEGW9wpVSGhIynaCk" alt=""><figcaption><p>Forecourt Status</p></figcaption></figure></div>
{% endstep %}

{% step %}

### Confirm the DCR channel is IP Enabled

* In **Configuration Client**: Select <kbd>Tools</kbd> → <kbd>Managed Modules</kbd> →

<kbd>Host Names: sitecontroller</kbd>→ <kbd>Select Module: DCR Driver</kbd> → <kbd>DCR Channel 01</kbd>

* Navigate to <kbd>Advanced Settings</kbd> and verify that **IP Enabled** is selected.

<div align="left"><img src="/files/7PSPuQfyzr7ejs71bFaI" alt="" width="345"></div>

<div align="left"><img src="/files/7DzxPPCp3PQKJPHlNkEz" alt="" width="468"></div>
{% endstep %}

{% step %}

### Confirm OEMV was previously working

Ensure that the DCRs operated correctly after enabling Ethernet/OEMV.

For a new OEMV transition, ensure OEMV settings are verified first.
{% endstep %}

{% step %}

### Before Initializing EMV/EMV Init

### Before performing **Initialize EMV/EMV Init**, confirm:

* All pumps/fueling positions are **Idle**
* **No Active transactions** or customers at the pumps.

This prevents Initialization errors and **stuck fuel sales**.
{% endstep %}

{% step %}

### Initialize EMV or Init EMV (only if DCR POP IDs exist) <a href="#initialize-emv-dcrs" id="initialize-emv-dcrs"></a>

**EMV Initialization Process**

1. Check that all **DCR POP IDs** are included in the Available POP List by doing the following:
2. If your site is **Tesoro/ARCO**, see [**Note**](#note) below prior to **Initializing EMV**
3. Login to **Config Client**, Go to:

<kbd>Payment Controller</kbd> > <kbd>EPS Configuration</kbd> > <kbd>EPS Global Configuration</kbd> >

<kbd>EMV Initialization</kbd>

{% hint style="info" %}
In the DCR POP list:

* IDs starting with **0** are Indoor Pinpads.
* IDs starting with **1** are DCRs(Dispenser Card Readers).
  {% endhint %}

<div align="left"><figure><img src="/files/W41VHCfM1RkGi9MXWyZC" alt=""><figcaption></figcaption></figure></div>

3. Select the affected DCRs from the <kbd>Available POP list</kbd>(e.g., enter 101 for DCR#1, 102 for DCR#2, etc.) and press <kbd>Add</kbd> to add it under <kbd>Selected POP List</kbd> and <kbd>Save</kbd>
4. When <kbd>Save</kbd> is pressed, there will be a prompt to enter the OTP
5. To obtain the OTP, go to : <kbd>CSR Function</kbd> > <kbd>Maintenance Menu</kbd> > <kbd>Generate Config OTP</kbd>
6. Enter the OTP and the EMV Initialization will start.

Follow these steps to ensure proper configuration and operation of the DCR units.
{% endstep %}

{% step %}

### Push DCR data in order

Run the pushes in this order:

### Before **Initialize DCR Driver**, confirm:

* All pumps/fueling positions are **Idle**
* **No Active transactions** or customers at the pumps.

This prevents Initialization errors and **stuck fuel sales**.

#### **1. Initialize DCR Driver**

<div align="left"><figure><img src="/files/gwG8Yh1y5MtwymGcKoQE" alt=""><figcaption></figcaption></figure></div>

### Before **Downloading to All DCRs** or **Initializing All DCRs**, confirm:

* All pumps/fueling positions are **Idle** and&#x20;
* **No Active transactions** or customers at the pumps.

This prevents Initialization errors and **stuck fuel sales**.

#### **2. Download to DCRs**

<div align="left"><figure><img src="/files/3Pspny2ioeMDat9oUCfs" alt=""><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

***

After any configuration change, run **Refresh Configuration,** **Download to DCRs** and Run **Initialize Fuel** only if needed. This pushes the updates to all fueling positions.

#### **1. Refresh Configuration:**

* Navigate to <kbd><mark style="color:green;">**Tools**<mark style="color:green;"></kbd> , then select **Refresh Configuration**.

### Before **Downloading to All DCRs** or **Initializing All DCRs**, confirm:

* All pumps/fueling positions are **Idle** and&#x20;
* **No Active transactions** or customers at the pumps.

This prevents Initialization errors and **stuck fuel sales**.

#### **2. Initialize DCRs (All):**

* In Config Client: <kbd>Forecourt</kbd> → <kbd>Initialization</kbd> → <kbd>DCR</kbd>&#x20;

<div align="left"><figure><img src="/files/qFw1Xvte2kwl2M346gdJ" alt=""><figcaption></figcaption></figure></div>

* Enter `0` (All) or select **All**.

### Before **Initializing Fuel,** confirm:

* All pumps/fueling positions are **Idle** and&#x20;
* **No Active transactions** or customers at the pumps.

This prevents Initialization errors and **stuck fuel sales**.

#### **3.Initialize Fuel (if necessary):**

* In Config Client: <kbd>Forecourt</kbd> → <kbd>Initialization</kbd> → <kbd>Fuel</kbd>

<div align="left"><figure><img src="/files/6qX2IbnxpWuEAaaFzwjR" alt=""><figcaption></figcaption></figure></div>

{% hint style="warning" %}
If **all DCRs** are affected, there could be a network issue at your site. Check the on-site **firewall/MNSP** path. Contact your site’s **MNSP provider**(Ex: Cybera, Hughes, Mako, Sagenet, etc.) to confirm the **DCR network** path is up and online.
{% endhint %}

### <mark style="background-color:yellow;">Note:</mark> <a href="#note" id="note"></a>

<details>

<summary><mark style="color:$primary;"><strong>Tesoro / Arco :</strong></mark> <mark style="color:$primary;"><strong>Before Initializing EMV</strong></mark></summary>

1. Contact the Payment host to verify the site is configured for **OEMV** outside **on their end**.
2. Confirm with Payment host, the **Trigger pull & EMV tables** are flagged for download.
3. Run [**Trigger Pull**](/peripherals-help/peripherals-help/pinpads-help/general-pinpad-help/card-table-download-trigger-pull.md#tesoro-arco), then [**EMV PDL**](#tesoro-arco-before-initializing-emv).
4. Only then [**Initialize EMV**](#initialize-emv-dcrs) to the **DCR POPs.**

</details>

***

### If DCRs are over Serial (Legacy) — Base 53.27 and below

{% stepper %}
{% step %}

#### Verify power to the FCI

Remove the thumb screws on the **FCI box** (FCI) and check for lit LEDs inside.

**FCI images (LED examples):** use these as a visual reference for what “powered” looks like.

<figure><img src="/files/eIVEs7P4d46BzHV79Fra" alt="FCI Image power LED"><figcaption><p>FCI image — LEDs example 1</p></figcaption></figure>

<figure><img src="/files/CnNSg9qbVmLvalnoTDFv" alt="FCI Box image"><figcaption><p>FCI image — LEDs example 2</p></figcaption></figure>

<figure><img src="/files/MUIHmUzE6sNu7tE1HT27" alt="FCI Box Image"><figcaption><p>FCI image — LEDs example 3</p></figcaption></figure>
{% endstep %}

{% step %}

#### Reseat power if needed

If no LEDs, reseat power and try a known-good outlet.
{% endstep %}

{% step %}

### Before **Downloading to All DCRs** or **Initializing All DCRs**, confirm:

* All pumps/fueling positions are **Idle** and&#x20;
* **No Active transactions** or customers at the pumps.

This prevents Initialization errors and **stuck fuel sales**.
{% endstep %}

{% step %}

#### Run Download to DCRs

Login to Config Client:

Select <kbd>Forecourt</kbd> → <kbd>Initialization</kbd> → **DCR(All)**

<div align="left"><figure><img src="/files/qFw1Xvte2kwl2M346gdJ" alt=""><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

If DCRs still show **No change** after Initialization attempts, Contact the Verifone Helpdesk.

{% hint style="info" %}
N**eed assistance? Contact Verifone Helpdesk at anytime.**

* Use our **Chat** platform
* Or call **1.800.VERIFONE (837.4366)**

Tell us the troubleshooting steps you’ve already tried. This saves time and gets you 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://commanderhelp.verifone.com/fuel-dcr-help/fuel-dcr-help/dcr-help/dcrs-over-ethernet-oemv-or-serial.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.