> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/hardware/card-readers/mms-dyna-devices/dynaflex-ii-ped/documentation/developers-manuals/dynaflex-ii-ped-programmers-manual/commands/user-interface/show-bitmap-image.md).

# Show Bitmap Image

## Command 0x1823 - Show Bitmap Image (Display Only) <a href="#toc203725805" id="toc203725805"></a>

The host uses this command to trigger the device to immediately show a bitmap file the host includes as a parameter, provided the device is not in a mode that has exclusive use of the display (such as during a transaction).

This is an immediate and temporary directive. For a solution that affects the device’s idle page behavior on a more permanent basis, see Property 1.2.3.1.1.1 Custom Idle Page Image.

This command is different from Command 0x1806 – Personal Info Entry.

The host uses Command 0x1806 to prompt a cardholder for customer information.&#x20;

The sequence of events for Command 0x1806 is:

{% stepper %}
{% step %}
The host ensures the device is not currently running another command, for example, that it is not running a transaction using Command 0x1001 - Start Transaction.
{% endstep %}

{% step %}
If the host determines it should request customer information, it composes a command request in the format below.
{% endstep %}

{% step %}
The device presents a keypad interface to the cardholder on the display.
{% endstep %}

{% step %}
The device sends Notification 0x1805 - User Interface Operation Complete to the host to report data available, or hardware failure.
{% endstep %}

{% step %}
If the device reported data available, the host can retrieve the data as defined in the Notification Detail Codes and Notification Payload for Personal Info Entry.
{% endstep %}
{% endstepper %}

## Table - Request Data for Command 0x1806 – Personal Info Entry

<table><thead><tr><th>Tag</th><th width="73">Len</th><th width="268.3333740234375">Value / Description</th><th width="78.33331298828125">Typ</th><th width="76">Req</th><th width="97.333251953125">Default</th></tr></thead><tbody><tr><td>Beginning of any wrappers, at minimum including Request Message (see message wrapper definition)</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>1806 = Command 0x1806 – Personal Info Entry</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>81</td><td>01</td><td>Capture Type: 0x01 = Phone Number; 0x02 = Social; 0x03 = Zip code; 0x04 = Employee ID; 0x05 = Birth Date (USA format); 0xFF = Cancel Capture</td><td>B</td><td>R</td><td></td></tr><tr><td>Beginning of any wrappers, at minimum including Request Message</td><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>

## Table - Response Data for Personal Info Entry

<table><thead><tr><th>Tag</th><th width="73">Len</th><th width="236.66668701171875">Value / Description</th><th width="74.6666259765625">Typ</th><th width="74.6666259765625">Req</th><th width="97.3333740234375">Default</th></tr></thead><tbody><tr><td>Beginning of any wrappers, at minimum including Response Message (see message wrapper definition)</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>1806 = Command 0x1806 – Personal Info Entry</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>No parameters.</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Beginning of any wrappers, at minimum including Response Message</td><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>

If the request started successfully, the Request Status in the message wrapper is **OK, Started / Running (All good / requested operation was successful).**

## Table - Request Example

{% code title="Example (Hex)" %}

```
AA00 810401031806 8405 1806 8101 01
```

{% endcode %}

## Table - Response Example&#x20;

{% code title="Example (Hex)" %}

```
AA00 810482031806 8204 01000000
```

{% endcode %}

Command 0x1823 - Show Bitmap Image (Display Only) differs from Command 0x1821 - Show Image (Display Only) in that the host sends bitmaps as parameters instead of pre-loading them, and the host can call this command multiple times without clearing the display to show multiple bitmaps on the display at the same time.

The sequence of events for Command 0x1823 is:

{% stepper %}
{% step %}

### Step: Ensure device availability

The host ensures the device is not currently running another command, for example, that it is not running a transaction using Command 0x1001 - Start Transaction.
{% endstep %}

{% step %}

### Step: Select bitmap

The host selects a bitmap file it wants to display.
{% endstep %}

{% step %}

### Step: Compose and send command

The host composes a command request in the format below and sends it to the device.
{% endstep %}

{% step %}

### Step: Optional background clear

If the host includes the Background Color parameter, the device clears the display using the specified color. If the host does not include that parameter, the device does not clear the display.
{% endstep %}

{% step %}

### Step: Display placement and timing

* The device shows the bitmap with the upper left corner at the specified X Position and Y Position. If the host omits either parameter, the device centers the bitmap along the unspecified axis.
* If the Display Time parameter is Indefinite or is not included, the device returns a command response message with Response Status, Operation Status Summary byte set to 0x00 (OK, Done) after which the host is free to send further commands.
* If the timeout parameter is set to a specific number of seconds:
  * The device returns a command response message with its Response Status, Operation Status Summary byte set to 0x01 (OK, Started / Running).
  * While the host is waiting for the timeout to expire, it should not send any commands to the device, because the device is busy processing the current command.
  * After the timeout period expires, the device unlocks to allow other commands and sends Notification 0x1805 - User Interface Operation Complete to inform the host.
    {% endstep %}
    {% endstepper %}

## Table - Request Data for Command 0x1823 - Show Bitmap Image (Display Only)

<table><thead><tr><th>Tag</th><th width="73.3333740234375">Len</th><th width="239.66668701171875">Value / Description</th><th width="73.33331298828125">Typ</th><th width="73.99993896484375">Req</th><th width="97.3333740234375">Default</th></tr></thead><tbody><tr><td>Beginning of any wrappers, at minimum including Request Message</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>1823 = Command 0x1823 - Show Bitmap Image (Display Only)</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>81</td><td>01</td><td>Display Time: 0x00 = Indefinite; 0x01 to 0xFF = 1 to 255 seconds</td><td>B</td><td>O</td><td>0x00</td></tr><tr><td>82</td><td>03</td><td>Background Color. Use RRGGBB format.</td><td>B</td><td>O</td><td>N/A</td></tr><tr><td>83</td><td>02</td><td><p>X Position. </p><p>The device places the left edge of the image at this pixel position relative to the left edge of the display, which is position 0x0000. This parameter plus the pixel width of the image must be less than the pixel width of the display. The display’s pixel width depends on the device’s orientation set by Property 1.2.3.1.1.2 Custom Idle Page Image Device Locked (Display Only). For information about the resolution of the display, see the specifications in the device’s Installation and Operation Manual.</p></td><td>B</td><td>O</td><td>Centered</td></tr><tr><td>84</td><td>02</td><td><p>Y Position. </p><p>The device places the top edge of the image at this pixel position relative to the top edge of the display, which is position 0x0000. This parameter plus the pixel height of the image must be less than the pixel height of the display. The display’s pixel height depends on the device’s orientation set by Property 1.2.3.1.1.2 Custom Idle Page Image Device Locked (Display Only). For information about the resolution of the display, see the specifications in the device’s Installation and Operation Manual.</p></td><td>B</td><td>O</td><td>Centered</td></tr><tr><td>85</td><td>var</td><td><p>Bitmap </p><p>Image encoded in full BMP file format as defined by Microsoft (e.g., starting with “BM”) or Magtek signed image file format</p></td><td>B</td><td>R</td><td></td></tr><tr><td>86</td><td>01</td><td><p>Display Option: </p><ul><li>0x00 = Default (cover/uncover the top status bar depends on the current status of the display). If the current display shows the top status bar, the Show Bitmap Image command won’t cover the top status bar. If the current display doesn’t show the top status bar, the Show Bitmap Image command will cover the top status bar. </li><li>0x01 = Cover the top status bar regardless of the current status of the display. </li><li>0x02 = Not cover the top status bar regardless of the current status of the display.</li></ul></td><td>B</td><td>O</td><td>0</td></tr><tr><td>End of any wrappers, at minimum including Request Message</td><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>

## Table - Response Data for Command 0x1823 - Show Bitmap Image (Display Only)

<table><thead><tr><th>Tag</th><th width="81.6666259765625">Len</th><th>Value / Description</th><th width="72.33331298828125">Typ</th><th width="77.333251953125">Req</th><th width="96.666748046875">Default</th></tr></thead><tbody><tr><td>Beginning of any wrappers, at minimum including<a href="https://magtek.gitbook.io/magtek-pilot-gitbooks/internal-documentation/index/3.0-messages-requests-responses-notifications-and-files/3.3-message-structure#table-12-response-message-format"> Response Message</a></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>1823 = Command 0x1823 - Show Bitmap Image (Display Only)</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>No parameters.</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>End of any wrappers, at minimum including <a href="https://magtek.gitbook.io/magtek-pilot-gitbooks/internal-documentation/index/3.0-messages-requests-responses-notifications-and-files/3.3-message-structure#table-12-response-message-format">Response Message</a></td><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>

If the request started successfully, the Request Status in the message wrapper is **All Good, Requested Operation Was Successful.**

## Table - Request Example (Hex)

{% code title="Example (Hex)" %}

```
AA 00 81 04 01 05 18 22 84 41 18 22 81 01 3C 82 0F 54 68 69 73 20 69 73 20 61 20 74 
65 73 74 21 83 01 00 84 01 FF 85 01 01 86 01 28 87 03 00 00 00 88 03 FF FF FF 89 13 
50 6c 65 61 73 65 20 73 63 61 6e 20 51 52 20 63 6f 64 65
```

{% endcode %}

## Table - Response Example

{% code title="Example (Hex)" %}

```
AA 00 81 04 82 2C 18 22 82 04 00 00 00 00
```

{% endcode %}

## Table - Notification Example (Hex)

{% code title="Example (Hex)" %}

```
AA 00 81 04 83 00 18 05 82 04 02 01 00 00
```

{% endcode %}


---

# 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://developer.magtek.com/hardware/card-readers/mms-dyna-devices/dynaflex-ii-ped/documentation/developers-manuals/dynaflex-ii-ped-programmers-manual/commands/user-interface/show-bitmap-image.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.