--- title: Interpret Autorun Logs slug: hardware/interpret-autorun-logs docTags: createdAt: 2025-03-11T06:58:11.201Z --- The *autorun.brs* file, located in the root of player storage, may contain one of several possible automatically-executed scripts. These scripts perform player initialization, setup, recovery, and the main player workflow. During execution, most of these scripts may produce log files containing information about events and state transitions happening on the player. When enabled, these logs files are stored in several different folders. The one containing information about pending events is stored in the */currentLog *folder, and is rotated daily or after player reboot. There is an option to enable log uploads to the cloud/server, either on startup or at a specific time of the day. This can be enabled in the **Player Settings > Logging** section of the** Admin > Setup **screen. Logs that are successfully uploaded are moved to the */archivedLogs* folder. If uploading fails after multiple attempts, the logs are placed in the */failedLogs* folder instead. See Image 1, below: ::Image[]{src="https://api.archbee.com/api/optimize/Aiw58-3NpdDpGlgjiVvLS-kIhPfWS6y9XXEa6WS3oV6-20250801-162311.png" size="30" width="393" height="982" position="center" caption="Image 1" darkWidth="393" darkHeight="982" showCaption="true"} Each autorun log file may contain up to five kinds of records: - Diagnostic (starting with `L=d`) - Playback (starting with `L=p`) - Event (starting with `L=e`) - State (starting with `L=s`) - User variable (starting with `L=u` ) Each entry type can be enabled or disabled during the player setup process and adjusted in the **Player Settings** panel after registration. Each log file in the folders mentioned above has a header section which may contain the following properties: | **Name** | **Description** | **Example** | | -------------------- | ----------------------------------------------------- | ----------------------- | | BrightSignLogVersion | Logs implementation version. Possible values: 2, 3, 4 | 4 | | SerialNumber | BrightSign Unit Serial Number | 46D89C101139 | | Account | BSN.com/BSN.Cloud Network Name | JaneDoe | | Group | Group name of the player | Default | | Timezone | Client (unit) timezone as set in registry | EET | | LogCreationTime | Time when log file created | 2025/07/25 15:59:24.350 | | IPAddress | IP address of unit | 172.16.0.85 | | FWVersion | Firmware version that the player runs on | 9.0.168 | | ScriptVersion | Autorun version | 10.0.100 | | CustomScriptVersion | Custom Autorun Version | 10.0.100 | | Model | Model description | XC4055 | # Diagnostic Log The diagnostic log entries capture information about I/O operations and low-level errors reported by the BrightSign OS, which makes them useful during troubleshooting. These kind of entries begin with the `L=d` key-value pair. Other key-value pairs in these entries have the following meaning: - T: A timestamp indicating when the diagnostic log was recorded - I: A unique identification number for the system event, one of the values listed in the [Event Type Codes](docId\:mOlxN8L89xSeDvjEe4KmH) section - D: Arbitrary data related to the current event, which may include current firmware/autorun version numbers (see below) :::ExpandableHeading ## Event Type Codes | **Code** | **Name** | **Description** | | -------- | ---------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1000 | EVENT\_STARTUP | The autorun script has started. | | 1001 | EVENT\_SYNCSPEC\_RECIEVED | A new sync spec has been downloaded; if "yes", the downloaded and current sync spec are different; if "no", they are identical. The log may also include: "forced reboot" (the sync spec includes a forced reboot command), "forced log upload" (the sync spec includes a log upload command), or "bad sync" (the downloaded sync-spec file is corrupt). | | 1002 | EVENT\_DOWNLOAD\_START | The autorun script has initiated a series of downloads to retrieve files listed in the sync spec. | | 1003 | EVENT\_FILE\_DOWNLOAD\_START | Currently unused | | 1004 | EVENT\_FILE\_DOWNLOAD\_COMPLETE | A single file download in the series initiated by the sync spec has been completed. | | 1005 | EVENT\_DOWNLOAD\_COMPLETE | The series of downloads initiated by the sync spec has been completed. | | 1006 | EVENT\_READ\_SYNSPEC\_FAILURE | The autorun script was unable to read the sync spec file. See the entry for *roSyncSpec.ReadFromFile()* for more information. | | 1007 | EVENT\_RETRIEVE\_SYNCSPEC\_FAILURE | The autorun script has requested the sync spec from the content server and it has returned a status code other than 200 or 404. | | 1008 | EVENT\_NO\_SYNCSPEC\_FAILURE | The autorun script has requested the sync spec from the content server and it has returned status code 404. | | 1009 | EVENT\_SYNCSPEC\_DOWNLOAD\_IMMEDIATE\_FAILURE | The series of downloads initiated by the sync spec failed immediately. This event includes the failure reason. See  *roAssetFetcher.ASyncDownload()* for more details. | | 1010 | EVENT\_FILE\_DOWNLOAD\_FAILURE | There has been an individual file-download failure during the series of downloads initiated by the sync spec. | | 1011 | EVENT\_SYNCSPEC\_DOWNLOAD\_FAILURE | The series of downloads initiated by the sync spec has been completed with at least one file-download failure (event 1010). | | 1012 | EVENT\_ASSETPOOL\_PROTECT\_FAILURE | The sync spec update process cannot be completed because one or more preexisting assets are protected. See  *roAssetPool.ProtectAssets()* for more details. | | 1013 | EVENT\_LOGFILE\_UPLOAD\_FAILURE | The autorun script has attempted to upload a log file to the log-handler server, and it has returned a status code other than 200. | | 1014 | EVENT\_SYNC\_ALREADY\_ACTIVE | A scheduled update timer has triggered while the sync spec update process is already in progress. | | 1015 | EVENT\_CHECK\_CONTENT | The autorun script has requested a new sync spec. This event includes the URL for the file request. | | 1016 | EVENT\_FILE\_DOWNLOAD\_PROGRESS | The autorun script is currently downloading a file. This event triggers every 15 seconds during the download process and returns the completion percentage. | | 1017 | EVENT\_FIRMWARE\_DOWNLOAD | Currently unused | | 1018 | EVENT\_SCRIPT\_DOWNLOAD | Currently unused | | 1021 | EVENT\_USER\_VARIABLE\_NOT\_FOUND | The autorun script (or a script plugin) has referenced a user variable that is not part of the database. | | 1022 | EVENT\_MEDIA\_COUNTER\_VARIABLE\_NOT\_FOUND | The autorun script (or a script plugin) has referenced a media counter that is not part of the database. | | 1023 | EVENT\_START\_PRESENTATION | A new presentation has started. | | 1024 | EVENT\_GPS\_LOCATION | An event has been received from a GPS device. This event returns the latitude and longitude values reported by the GPS. | | 1025 | EVENT\_GPS\_NOT\_LOCKED | The autorun script has been unable to process the data returned from the GPS device. | | 1026 | EVENT\_RETRIEVE\_USER\_VARIABLE\_FEED | Currently unused | | 1027 | EVENT\_RETRIEVE\_LIVE\_TEXT\_FEED | The autorun script has begun retrieving a live data feed XML file. | | 1028 | EVENT\_USER\_VARIABLE\_FEED\_DOWNLOAD\_FAILURE | Currently unused | | 1029 | EVENT\_LIVE\_TEXT\_FEED\_DOWNLOAD\_FAILURE | The download of a live data feed file has failed. | | 1030 | EVENT\_UNASSIGNED\_LOCAL\_PLAYLIST | The autorun has skipped a Local Playlist state because it is empty. This can occur if a player is assigned the **Use default playlist**  option and the default playlist of the Local Playlist is set to **None**. | | 1031 | EVENT\_UNASSIGNED\_LOCAL\_PLAYLIST\_NO\_NAVIGATION | The autorun has attempted to skip an empty Local Playlist state (event 1030), but there is no Media End event attached to it. | | 1032 | EVENT\_REALIZE\_FAILURE | The autorun has completed a sync spec update process that includes a firmware update or script file, but fails to copy that file to the root folder of the storage device. | | 1033 | EVENT\_LIVE\_TEXT\_PLUGIN\_FAILURE | A data-feed plugin script has failed. | | 1034 | EVENT\_INVALID\_DATE\_TIME\_SPEC | A Time/Clock event has failed because the date information is not valid. | | 1035 | EVENT\_HTML5\_LOAD\_ERROR | An HTML page has failed to load. | | 1036 | EVENT\_USB\_UPDATE\_SECURITY\_ERROR | The USB update process has failed because the **USB Content Update Password** on the storage device was invalid. | | 1037 | EVENT\_TUNE\_FAILURE | (XD1230 only) The autorun script has failed to tune to a specified channel on the RF tuner. | | 1038 | EVENT\_SCAN\_START | (XD1230 only) The RF channel-scan process has begun. | | 1039 | EVENT\_CHANNEL\_FOUND | (XD1230 only) An RF channel has been detected during the channel-scan process. | | 1040 | EVENT\_SCAN\_COMPLETE | (XD1230 only) The RF channel-scan process has completed. | | 1041 | EVENT\_SCRIPT\_PLUGIN\_FAILURE | A plugin script has failed. | | 1042 | EVENT\_DISK\_ERROR | System software has reported an error with the storage device. | | 1043 | EVENT\_LIVE\_MRSS\_PLUGIN\_FAILURE | An MRSS feed plugin script has failed. | | 1044 | EVENT\_EMPTY\_MEDIA\_PLAYLIST | The autorun script has skipped an Image List, Video List, or Audio List state because it is empty. | | 1100 | EVENT\_BLC400\_STATUS | The status of a connected BLC400 device has changed. This event can include the following status messages: "over", "under", "missing", or "normal". | | 1200 | EVENT\_CONTINUE\_LIVE\_DATA\_FEED\_CONTENT\_DOWNLOAD | The refresh timer for a live data feed has triggered while the autorun is downloading the feed. The autorun has continued downloading the feed because it has not changed. | | 1201 | EVENT\_RESTART\_LIVE\_DATA\_FEED\_CONTENT\_DOWNLOAD | The refresh timer for a live data feed triggered while the autorun downloaded the feed. The autorun cancelled the current download and started a new one because the feed has changed. | | 1202 | EVENT\_START\_LIVE\_DATA\_FEED\_CONTENT\_DOWNLOAD | The autorun has begun downloading a live data feed. | | 1203 | EVENT\_ASSETPOOL\_UNPROTECT\_FAILURE | Currently unused | | 1204 | EVENT\_PLAYBACK\_FAILURE | A media file has failed to play. | | 1205 | EVENT\_START\_MRSS\_FEED\_CONTENT\_DOWNLOAD | The autorun has begun downloading an MRSS (live media) feed. | | 1206 | EVENT\_UNABLE\_TO\_CREATE\_ASSET\_POOL | The autorun has encountered a failure while attempting to create an asset pool. This event will return either "pool" or "feedpool", indicating whether failure occurred when creating a pool for a presentation or a pool for an RSS/MRSS feed. | | 1207 | EVENT\_DELETE\_USER\_VARIABLES\_DB | The autorun has attempted to read from the user-variables database and has determined that it is corrupt. The autorun will then delete the user-variables database and repopulate it with default values. | | 1208 | EVENT\_SCREENSHOT\_ERROR | The autorun has attempted and failed to take a screen shot. | | 1209 | EVENT\_SCREENSHOT\_UPLOAD\_ERROR | The autorun has attempted and failed to upload a Remote Screenshot image to BSN servers. | | 1210 | EVENT\_SCREENSHOT\_UPLOADED\_AND\_QUEUED | The autorun has successfully uploaded a Remote Screenshot image, and the file is now in the queue process to be stored in the BSN database. | | 1211 | EVENT\_SCREENSHOT\_QUEUE\_ERROR | The BSN servers have indicated that the queue operation has failed. The autorun will attempt to upload the Remote Screenshot image to the BSN servers again. | | 1212 | EVENT\_SET\_BSN\_OVERRIDE | A BSN administrator has specified a Remote Screenshot configuration override for the player. | | 1213 | EVENT\_CANCEL\_BSN\_OVERRIDE | A BSN administrator has cancelled the Remote Screenshot configuration override for the player. | | 1214 | EVENT\_BSN\_OVERRIDE\_EXPIRED | The Remote Screenshot configuration override settings have reached their specified expiry date. | | 1215 | EVENT\_SET\_SNAPSHOT\_CONFIGURATION | The Remote Screenshot configuration has been set using the Application Web Server. | | 1216 | EVENT\_STREAM\_END | An audio or video IP stream has generated an End of Stream event (see the *roRtspStream* entry for more details). | | 1217 | EVENT\_SET\_VIDEO\_MODE | The video output has been set to the reported video mode. If the "preferred video mode" feature is supported by the firmware, and if the **Force Resolution** box is unchecked in BrightAuthor, this event will also return the preferred video mode. | | 1218 | EVENT\_SNAPSHOT\_PUT\_TO\_SERVER\_ERROR | The autorun has encountered an error while uploading a screen shot. This event returns the failure reason as well. See the *roUrlTransfer.ASyncPutFromFile()* entry for more details. | | 1219 | EVENT\_CHECK\_LIVE\_TEXT\_FEED\_HEAD | The autorun has checked the contents of a feed to determine if there is new text/media to retrieve. | | 1300 | EVENT\_BEACON\_START | A BLE beacon has begun transmitting. | | 1301 | EVENT\_BEACON\_START\_FAILED | A BLE beacon has failed to initialize. | | 1302 | EVENT\_BEACON\_START\_LIMIT\_EXCEEDED | A BLE beacon did not responded to an initialization request within a certain timeframe. | ::: ## Example :::BlockQuote *L=d T=2024/10/31 11:48:53.491 I=1023 D=9.0.16 10.0.100 10.0.100* ::: # Event Log   The event log entries capture information about the events that happened in specific presentation zones or in the shared presentation assets. These kind of entries begin with the `L=e` key-value pair. Other key-value pairs in these entries have the following meaning: - S: The name of the state affected by the event - T: A timestamp indicating when the event occurred - E: One of the event types listed in the [Event Types](docId\:mOlxN8L89xSeDvjEe4KmH) section - D: Arbitrary data related to the current event - A: A flag indicating whether the event was acted on (“1”) or not acted on (“0”) :::ExpandableHeading ## Event Types - mediaEnd - timer - serial - gpioButton - auxDisconnect - auxConnect - timeClock - mediaListInactivityTimer - touch - gpsEnterRegion - gpsExitRegion - usbBinaryEtap - remote - usb - keyboard - synchronize-play - udp - bpDown - sendZoneMessage - internalSyncPreload - internalSyncMasterPreload - internalSyncMasterPlay - internalSyncSlavePlay - internalSyncPlay - videoTimeCode - timeout - serialBytes ::: ## Example :::BlockQuote *L=e S=earth\_1280x720.mov09bce968-4c77-4775-b314-b2388cd77abb T=2024/10/31 11:48:55.086 E=mediaEnd D= A=1* ::: # Playback Log The playback log entries capture information when a particular piece of media has been displayed on a screen. These kind of entries begin with the `L=p` key-value pair. Other key-value pairs in these entries have the following meaning: - Z: The name of the zone in which the playback occurred - S: A timestamp indicating when playback started - E: A timestamp indicating when playback ended - I: The media type of the file being played (e.g. “image”, “video”, “audio”) - N: The name of the content file being played ## Example :::BlockQuote *L=p Z=Video or Images S=2024/12/11 00:00:00.656 E=2024/12/11 00:00:29.172   I=video N=KO\_Caps\_v1\_30p\_Subway\_28s.mp4* ::: # State Log The State log entries capture information about state transitions that happen during presentation playback. These kind of entries begin with the `L=s` key-value pair. Other key-value pairs in these entries have the following meaning: - S: The new state name - T: A timestamp indicating when the state was entered - Y: One of the state type listed in the [State Types](docId\:mOlxN8L89xSeDvjEe4KmH) section - LS: The previous state name - LE: The type of event that transitioned to this state - LD: The arbitrary data related to the event that transitioned to this state :::ExpandableHeading ## State Types - tripleUSB - stream - mjpeg - audioIn - eventHandler - tunerScan - RFIn + channel - RFIn + virtual channel - liveVideo - html5 - interactiveMenu - liveText - mediaRSS - audioMx - backgroundImage - image - video - audio - rfInputChannel - signChannel - mediaList - playFile - rfScan ::: ## Example :::BlockQuote *L=s S=earth\_1280x720.mov09bce968-4c77-4775-b314-b2388cd77abb T=2024/10/31 11:53:55.951 Y=video LS=Panorama.jpgcee716ef-6d47-4f85-9496-2fbe385b1667 LE=mediaEnd LD=*    ::: # User Variable Log The User Variable log entries capture keys and values of user variables defined within a presentation. These kind of entries begin with the `L=u` key-value pair. Other key-value pairs in these entries have the following meaning: - T: A timestamp indicating when the event occurred - E: One of the event types listed in the [Event Types](docId\:mOlxN8L89xSeDvjEe4KmH) section - N: The name of the user variable - C: The current value of the user variable - D: The default value of the user variable ## Example :::BlockQuote *L=u T=2024/10/31 11:48:55.086 E=mediaEnd N=PlayerName C=MyPlayer D=Unknown* :::