> 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/microarray/iscan/microarray-iscan-reference_material-list/000002213.md).

# How to find the iScan Log Files

The iScan Control Software (ICS) creates a log file during each run. The log file records each step of the scanning process. Log files are also copied to the data output folder for each BeadChip.

**View the current log file**

To view only the current log file:

1. Select the **Menu** button in the upper left corner of the ICS Welcome screen.
2. Select **Tools** | **Show Log**

**View archived log files**

To view the archived log files, navigate to the **Logs** folder in the ICS application folder:

C:\Program Files (x86)\Illumina\iScan Control Software\Logs.

**Log File Creation and Naming**

ICS uses the following naming convention for log files:

* Log file names are prefixed with iScan Control Software.
* iScanControlSoftware.00.log is the current log file.
* When the current log file reaches 5 MB in size, ICS renames it to iScanControlSoftware.01.log.
* ICS then creates a new iScanControlSoftware.00.log file and begins recording new log information.
* Each time the current log file reaches 5 MB in size, the existing archived log files are sequentially renamed. For example:

1. iScanControlSoftware.01.log is renamed to iScanControlSoftware.02.log.
2. iScanControlSoftware.00.log is renamed to iScanControlSoftware.01.log.
3. A new iScanControlSoftware.00. log file is created.

* The iScanControlSoftware.19.log replaces the file and is renamed to iScanControlSoftware.20.log. This process continues through iScanControlSoftware.20.log.
* When the next log rotation occurs after iScanControlSoftware.20.log has been reached, the existing iScanControlSoftware.20.log file is deleted and the remaining archived log files are renamed sequentially.

Therefore:

1. iScanControlSoftware.00.log is always the current log file.
2. iScanControlSoftware.20.log is always the oldest archived log file.

**References**:

* [iScan System - Instructions for operating and maintaining the iScan System](https://support-docs.illumina.com/ARR/iScan/Content/ARR/FrontPages/iscan.htm)
* [View Scan Results](https://support-docs.illumina.com/ARR/iScan/Content/ARR/iScan/ViewScanResults_fIS.htm) > Log Files - Log File Creation and Naming

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                   |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #2213), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000002213%20-%20Microarray%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/microarray/iscan/microarray-iscan-reference_material-list/000002213.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.
