> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000002865.md).

# Troubleshooting "TEC2SERVO unrecognize char" error during MiSeq Control Software initialization

Users of MiSeq instrument Windows Operating System (OS) with the system language set to a language other than English may encounter MiSeq Control Software (MCS) initialization failures due to a Y motor error.

Example of error may include: *The FPGA reported an error while executing command "TEC2SERVO 0 R 1 225000000"*

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-61def1791dd586e6d32b3b6f847a090c79190c88%2Fimage1.jpg?alt=media\&token=0c7f1759-0857-42dd-b442-db5442e6f4a8)

This error is caused by the incorrect regional settings in Windows. The regional format must always be set as **English (United States)**.

**To change the regional format settings:**

**In Windows 10:**

1. Acknowledge the error in MCS and close MCS.
2. Select **Start**, then select **Control Panel**.
3. Select **Change date, time, or number formats**.
4. The Region dialog box appears.
5. On the Formats tab, select **English (United States)** from the drop-down list.

**In Windows 7:**

1. Acknowledge the error in MCS and close MCS
2. Select **Start**, then select **Control Panel**.
3. Select **Clock, Language, and Region**, then select **Regional and Language Options**.
4. The Regional and Language Options dialog box appears.
5. On the Formats tab, select **English (United States)** from the drop-down list.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #2865), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000002865%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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://knowledge.illumina.com/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000002865.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.
