Why can’t my config.txt file be recognized by the EX-1?
The reason could be your config.txt file is not recognized by the EX-1 may be due to formatting differences in the line endings.
For example, On the left is config.txt file which has an issue and on the right is the reference configuration file downloaded directly from the manual.
Although the content appears visually identical in both files, the line break encoding is different:
-
The file has issue which uses LF (0A) for line breaks.
-
The reference file uses CR+LF (0D 0A), which is the standard Windows format.
It is likely that the file has issue was originally downloaded or edited on a non-Windows system (such as Linux), and saved using that system’s default formatting. Once saved this way, even if you later edit and save the file on Windows, many text editors will not automatically convert the line breaks back to 0D 0A, leading to compatibility issues with the EX-1.
As a result, the EX-1 cannot properly parse the file, which triggers an error.