SIG300 - download logs

To support troubleshooting in case any errors occur on a SIG300 device, it would be helpful to obtain the device’s log files. You can open the following URL in your web browser to see a log file available on the SIG300:

• connected via USB cable: http://169.254.0.1/api/crown/file?filePath=public%2Flog%2FDeviceLog.txt
• connected to port P1 with default IP address: http://192.168.0.1/api/crown/file?filePath=public%2Flog%2FDeviceLog.txt
• connected to port P2 with default IP address (REST variant only): http://192.168.1.1/api/crown/file?filePath=public%2Flog%2FDeviceLog.txt
• connected to port P1 or P2 with any other IP address: http://[IP_address]/api/crown/file?filePath=public%2Flog%2FDeviceLog.txt

After you have opened the page mentioned above, please do the following steps:

Method 1:

1. Right click into the page within your browser where you can see the log messages.
2. Choose from the context menu 'Save As'.
3. Choose the location and give it an adequate file name, e.g. '[today]_[IP_address]_DeviceLog.txt'.
4. Keep the 'Save as type' on 'TXT File (*.txt)' as the format for this file.
5. Click 'Save'.
6. Provide the saved file together with your description of the error experienced.

or

Method 2:

1. Press 'CTRL' + 'A' to select the complete text on this page.
2. Press 'CTRL' + 'C' to copy what has been selected before.
3. Open any kind of text editor and create a new file.
4. Press 'CTRL' + 'V' to insert the copied text to the new file.
5. Save this new file with an adequate name, e.g. '[today]_[IP_address]_DeviceLog.txt'.
6. Provide the saved file together with your description of the error experienced.

Additionally, it would also help to know whether the 'Power-on counter' has changed due to the error experienced or not! It is obvious that after the error, it is not possible to tell whether the 'Power-on counter' changed or not. But we recommend to save a screenshot of the diagnostics overview as soon as the SIG300 has finished booting while commissioning! Thus, you will have something to check against after the error occured: