Note: Support of diagnostic logs for CLU was released in 5.10.03-2248 FW version. Please refer to the system manual for details.
The diagnostic logs can be used, i.a, to verify the cause of the CLU entering into Emergency mode.
To obtain this information, you need to:
1. Create a diagnostic package in the current project:
2. Then unzip it. The content of a sample diagnostic package is shown below:
3. In Object Manager, go to Diagnostic view:
4. In the Diagnostic view, select the appropriate CLU, and then in the Logs tab, run the connection:
5. The logs indicating the reason for the module entering into Emergency mode will appear in the console: 
According to the message in the logs, the problem occurred in the user.lua file - the end closing function written in line 3 is missing.
Historical LUA logs:
error loading module 'user' from file 'a:\user.lua':
a:\user.lua:60: 'end' expected (to close 'function' at line 3) near <eof>
cannot open a:\main.lua: no error
6. Go to the previously unzipped diagnostic package:
- Select the folder with the corresponding CLU:
- Locate the user.lua file and open it using a text editor (e.g. Notepad++):
- In the document, find the third line and see what function the message refers to. In this case, it is the led_w_switch() function:
7. Go to your project, open the led_w_switch() script and find the error:
8. Edit the script by adding end to the end of the function, and then send the configuration to the CLU. After completing these steps, the CLU will return to proper operation:
