> 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-go/documentation/user-manuals/installation-and-operation-manual/user-interface/about-the-status-leds.md). # About the Status LEDs DynaFlex II Go provides four LEDs (see section 7.1 Component Details), numbered LED1 through LED4, which report the device’s current operating status. * The meaning of each LED depends on the device’s operating mode, see section 6 Operation. Most of the time, operators will check the device’s status using the LEDs when it is in Active Mode while the device is not performing a transaction. * LED blinking patterns have specific meanings as described in Table 7-. A blinking LED generally means the device is actively doing something to change the state that the LED is indicating, and solid indicates a persistent state that would require an operator or cardholder to take action to change. One major exception is a device-wide functional failure state, such as a tamper state, where all LEDs flash urgently to call the attention of an advanced operator to intervene. In this manual, specific blinking patterns are described in more detail in the sections where they are relevant. For example, information about how the LEDs show the device’s connection status is in section Connecting DynaFlex II Go to a Host. ## Table - DynaFlex II Go LED Allocation


In This Context	LED1	LED2	LED3	LED4
Active Mode, not armed for a tap transaction	Power	Connection	Reserved	Card Read Result
Active Mode, armed for a tap transaction	Armed for Tap	Tap Read Progress	Tap Read Progress	Card Read Result
Device-wide failure	During major failures (such as tamper), LED1-LED4 report the nature of the failure based on the most likely steps required to resolve it.	During major failures (such as tamper), LED1-LED4 report the nature of the failure based on the most likely steps required to resolve it.	During major failures (such as tamper), LED1-LED4 report the nature of the failure based on the most likely steps required to resolve it.	During major failures (such as tamper), LED1-LED4 report the nature of the failure based on the most likely steps required to resolve it.

## Table - DynaFlex II Go LED Patterns


Color	Means
Solid	Solid LEDs generally require an operator or cardholder to take action to change the state the LED is reporting. Example: Host is connected. Cardholder or host would have to disconnect. Example: Host is disconnected. Host would have to initiate connection.
Blinking	Blinking LEDs generally indicate the device is in the process of doing / attempting something. Blink duty cycle and blink period are generally selected to show urgency or ongoing progress through a series of steps. Example: Device is attempting to pair with the host via Bluetooth® Low Energy (LE).
Short time	LEDs sometimes light for a short time to indicate some process has ended (success or failure) and the device is going to transition to another state soon. Example: Successful card read.

--- # 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-go/documentation/user-manuals/installation-and-operation-manual/user-interface/about-the-status-leds.md?ask=&goal= ``` `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.