# Operation

### User Interface

iDynamo5 Gen III has a single RGB LED acting as the user interface. If the hardware does not support color mixing (e.g., red+green=amber) then a combination of LED states such as color, blinking speed (slow, fast), blink on-off, blink color A-B can be configured. This can be done easily by using a set of bits to represent the LED status over 4 time periods. A timer would rotate through one of the 4 time periods.

{% hint style="info" %}
Examples: GGGG – Green on, RRGG – red/green blink slow, RGRG – red/green blink fast, GGOO – blink green slow
{% endhint %}

The LED will be used to indicate various states of the reader.

## **Table 6-1 - Device State LED UI**

<table><thead><tr><th width="296.6666259765625">Device State</th><th>LED pattern</th></tr></thead><tbody><tr><td>Tampered</td><td>Solid Red</td></tr><tr><td>Offline</td><td>Blinking Red (Maybe split offline into ‘must RMA’ vs ‘Field fix possible’</td></tr><tr><td>Bootloader running</td><td>Solid Blue</td></tr><tr><td>Programming FW update into flash</td><td>Blinking Blue</td></tr><tr><td>Idle</td><td>Green</td></tr><tr><td>Card being read</td><td>Off</td></tr><tr><td>Card read error</td><td>Blink Red for 2 seconds</td></tr><tr><td>Qwantum Mode, Button enabled</td><td>Blinking Green</td></tr><tr><td>FW being downloaded</td><td>Provided by device or progress provided by host app</td></tr></tbody></table>

### Power Management

#### About Power

During normal operation, iDynamo is powered either from its connection to the host or from a connection to a USB power source. While the host charges this way, the device consumes more power from the USB connection than when the host’s battery is fully charged.

To save power, iDynamo enters low power mode when an app does not have an active session with it and will remain in low power mode until the app restarts or re-initiates a session. While an app has an open session, a cardholder may swipe a card through the magnetic stripe reader slot. When the device is not connected to USB power, the host would generally open a session with the device to process a transaction, then close the session after the transaction is complete to transition the device to low power mode and conserve power. When the device is powered by the USB-C connector, the host software may choose to always keep a session open with the device.

iDynamo does not come equipped with a battery, if it does not receive adequate power from the host the device powers off.

The device also draws a trickle of power from the connected host to power the magnetic stripe reader head. The host’s operating system manages this power flow when the device is not in use to save power.

### Card Reading

#### About Reading Cards

The steps for reading a card may be different depending on iDynamo’s configuration and on the design of the host software. Host software developers should see **Developing Custom Host Software** for implementation references. The solution developer should provide solution-specific instructions for operators to follow. A transaction generally follows this essential flow:

{% stepper %}
{% step %}

### Installation, configuration, and session open

An advanced operator makes sure iDynamo has been installed and configured, appropriate host software has been installed and configured, and the connection between iDynamo and the host is working properly (see **Installation**). After the host identifies and authenticates iDynamo, apps may open a session with it.
{% endstep %}

{% step %}

### Finalize transaction amount on host

The operator uses the host user interface to finalize a transaction amount, then initiates a transaction.
{% endstep %}

{% step %}

### Host notifies device readiness

The host communicates with the device, and reports to the operator when the device is ready.
{% endstep %}

{% step %}

### Direct the cardholder

The operator directs the cardholder in presenting payment.
{% endstep %}

{% step %}

### Cardholder presents payment

The cardholder interacts with the device to present payment.
{% endstep %}

{% step %}

### Host displays device prompts

Because the device does not have its own display, the device may send messages to the host prompting the cardholder to perform certain actions; the host software should process these requests by displaying the requested messages and depending on the placement of the host display(s), the operator may need to relay the messages to the cardholder. For example, if the device cannot read the card, it may prompt the cardholder to swipe again.
{% endstep %}

{% step %}

### Device reports transaction result

The device reports the success or failure of the transaction to the host, which should report the results to the operator.
{% endstep %}
{% endstepper %}

#### How to Swipe Magnetic Stripe Cards

Cardholders should swipe magnetic stripe cards in the MSR swipe path with the magnetic stripe facing away from the cardholder and into the device, as shown in **Figure 6-1**. Cardholders may swipe in either direction along the path.

<figure><img src="/files/X7szZJjGT5RQ38cPJHtr" alt=""><figcaption></figcaption></figure>

**Figure 6-1 - Swiping a Card Through iDynamo**


---

# Agent Instructions: 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:

```
GET https://developer.magtek.com/hardware/card-readers/magnetic-stripe-readers/idynamo-5-gen-iii/documentation/user-manuals/installation-and-operation-manual/operation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.