The "Device Log" button becomes available after . This button will report any errors occurring in the operation of the Morsel or transferring files to the Morsel. The following messages may be reported:
| Message | What it means |
|---|---|
| Widget end not encountered. | The theme file is corrupt or incomplete. If setting the theme file again does not fix the problem, please report this to us. |
| Widget definition not understood while loading. | The theme file is corrupt. |
| Widget not allocated due to 'out of memory'. | The theme is too complex, perhaps having too many sequences. Try reducing the number of sequences used. |
| Widget not allocated due to 'duplicate id'. | The theme file is corrupt. |
| Connection end not encountered. | The theme file is corrupt or incomplete. If setting the theme file again does not fix the problem, please report this to us. |
| Connections entirely absent from project file. | The theme file is corrupt or incomplete. If setting the theme file again does not fix the problem, please report this to us. |
| Project file not found. | The theme file is missing. This can happen when a theme file is deleted and the connection is interrupted. It's fixed by turning the device off and on. |
| File creating failed due to 'out of memory'. | The file storage is out of memory. Try deleting or simplifying files to make room. |
| File creating failed due to 'lost connection'. | The connection was interrupted. If exporting the theme file again does not fix the problem, please report this to us. |
| File creating replace older file. | The theme file replaced an older one, this is normal. |
| File writing attempted past allocated blocks. | The Theme Designer is exporting incorrect data. Please report this to us. |
| File defragmenting occurred. | The file storage just defragmented, this is normal, but may be the reason other error messages appeared. |
| File serving failed due to 'file not found'. | The Theme Designer is searching for a file on the device that does not exist. |
| File not found. | A file was not found in the file storage. This will be accompanied with a more descriptive error. |
| Sequence file not found. | The theme file is referencing a sequence that isn't present on the device currently. |
| Sequence end not found. | The sequence file is incomplete or corrupt. Please try exporting the sequence again. |
| Sequence data type not understood. | The sequence file is corrupt. |
| Sequence endless loop encountered and aborted. | A race condition was caught in the sequence file and stopped. It will not run again until the theme is restarted. If you have access to the sequence, walk through it to try finding the error. You may need to replace the sequence. |
| Widget initialize data not present. | The theme file is incomplete or corrupt. |
| Widget initializing cannot allocate additional resources due to 'out of memory'. | The theme, sequence, program, or the summation of all of them is too complex. Try reducing the number of sequences used, or use sequences with fewer labels and channels, or use programs with fewer buffers. |
| Connection attempted with missing widget. | The theme file is incomplete or corrupt. |
| Connection attempted with incorrect random channel. | The theme file is incomplete or corrupt. |
| Program file not found. | The theme file is referencing a program that isn't present on the device currently. |
| Program end not found. | The program file is incomplete or corrupt. |
| Program opcode not understood. | The program file is corrupt. |
| Program took too long to return. | The program is too complex or has a race condition that was stopped. It will run again on the next program tick. If you have the original program, walk through it to try finding the error. You may need to replace the program. |
| Program stack overflow/underflow occurred. | The program attempted to push or pop from the stack inappropriately. If you have the original program, walk through it to try finding the error. You may need to replace the program. |
| Program buffer overflow/underflow occurred. | The program attempted to use a buffer that was not allocated. If you have the original program, walk through it to try finding the error. You may need to replace the program. |
| Program function call not available. | The program is corrupt. |
| No problems or notifications currently. | Nothing to report. |
*For light blue boxes, these are normal operation. Yellow boxes should be tried again before contacting support, and red boxes generally are due to bugs in the software (please report these to us).