> 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-denmark/v660p/vejledninger/sadan-tester-du-den-indbyggede-printer.md).

# Sådan tester du den indbyggede printer

Kør en testudskrift på din V660P for at kontrollere, at printeren virker.

{% hint style="info" %}
**Brug dette, når** du vil kontrollere, at printeren fungerer — for eksempel hvis kvitteringer ikke bliver printet.
{% endhint %}

{% stepper %}
{% step %}

### Kontroller papirrullen

Sørg for, at en papirrulle er sat korrekt i. Åbn printerdækslet, isæt rullen, lad et lille stykke papir stikke ud, og luk dækslet.
{% endstep %}

{% step %}

### Åbn Diagnostik

1. Åbn applisten: stryg **op** på startskærmen. Hvis din V660P åbner direkte til **Connect Express**, stryg **ned** fra toppen af skærmen, og tryk på **indstillingsikonet** i nederste højre hjørne for at komme til Android-menuen.
2. Tryk på **Diagnostik**.
   {% endstep %}

{% step %}

### Kør en testudskrift

Tryk på undermenuen **Oversigt** (kan også hedde **Summary**), og tryk derefter på **Testudskrift** ved siden af **Printerstatus**.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**I Oversigt (Summary) kan du også se:**

* **VHQ Heartbeat**
* **Onlinestatus** (Online status)
* **Forbindelsesstatus** (Connectivity status)

Det er nyttigt, hvis du også vil kontrollere, at terminalen er online og forbundet.
{% endhint %}

**Hvis testudskriften mislykkes,** se [Printeren virker ikke](/support-denmark/v660p/fejl/printeren-virker-ikke.md).

<details>

<summary>Nøgleord</summary>

Også kaldet: testprinter, testudskrift, printertest, printer virker ikke. Søgetermer: printer, testudskrift, printerstatus, diagnostik, oversigt, summary, VHQ Heartbeat, onlinestatus, forbindelsesstatus, papirrulle.

</details>


---

# 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-denmark/v660p/vejledninger/sadan-tester-du-den-indbyggede-printer.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.