[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-561183-105":59,"doc-detail-561183-en":130},{"code":4,"msg":5,"data":6},0,"success",[7,13,18,23,28,33,38,43,48,51,55],{"id":8,"doc_module":4,"doc_module_name":9,"category_name":10,"show_sort_weight":11,"slug":12},1,"Document","Story & Novel",90,"story-novel",{"id":14,"doc_module":4,"doc_module_name":9,"category_name":15,"show_sort_weight":16,"slug":17},2,"Literature",80,"literature",{"id":19,"doc_module":4,"doc_module_name":9,"category_name":20,"show_sort_weight":21,"slug":22},4,"Exam",70,"exam",{"id":24,"doc_module":4,"doc_module_name":9,"category_name":25,"show_sort_weight":26,"slug":27},5,"Comic",60,"comic",{"id":29,"doc_module":4,"doc_module_name":9,"category_name":30,"show_sort_weight":31,"slug":32},6,"Technology",50,"technology",{"id":34,"doc_module":4,"doc_module_name":9,"category_name":35,"show_sort_weight":36,"slug":37},7,"Healthcare",40,"healthcare",{"id":39,"doc_module":4,"doc_module_name":9,"category_name":40,"show_sort_weight":41,"slug":42},8,"Research & Report",30,"research-report",{"id":44,"doc_module":4,"doc_module_name":9,"category_name":45,"show_sort_weight":46,"slug":47},9,"Religion & Spirituality",20,"religion-spirituality",{"id":46,"doc_module":4,"doc_module_name":9,"category_name":49,"show_sort_weight":46,"slug":50},"World Cup","world-cup",{"id":52,"doc_module":4,"doc_module_name":9,"category_name":53,"show_sort_weight":52,"slug":54},10,"Lifestyle","lifestyle",{"id":56,"doc_module":4,"doc_module_name":9,"category_name":57,"show_sort_weight":24,"slug":58},19,"General","general",{"code":4,"msg":60,"data":61},"ok",{"site_id":62,"language":63,"slug":64,"title":65,"keywords":66,"description":67,"schema_data":68,"social_meta":123,"head_meta":125,"extra_data":127,"updated_unix":129},105,"en","be-3d-self-diagnostic-software-section-4-3-led-error-code-identification","BE-3D SELF DIAGNOSTIC SOFTWARE - Section 4-3 - LED error code identification","","BE-3D self-diagnostic software identifies chassis errors through two trigger conditions: the bus busy state or a device failure to respond to IIC. The software first attempts to release a busy bus, then sequentially communicates with each device to determine faults. Detected device errors are indicated by an LED flash sequence that must be counted, mapping each count to a specific error code in the provided table. The table distinguishes non-fatal and potentially may-not-be-fatal runtime failures.",{"@graph":69,"@context":122},[70,84,105],{"@type":71,"itemListElement":72},"BreadcrumbList",[73,77,79,82],{"item":74,"name":75,"@type":76,"position":8},"https://docshare.wps.com","Home","ListItem",{"item":78,"name":9,"@type":76,"position":14},"https://docshare.wps.com/document/",{"item":80,"name":30,"@type":76,"position":81},"https://docshare.wps.com/document/technology/",3,{"item":83,"name":65,"@type":76,"position":19},"https://docshare.wps.com/document/be-3d-self-diagnostic-software-section-4-3-led-error-code-identification/561183/",{"url":83,"name":65,"@type":85,"image":86,"author":91,"headline":65,"publisher":94,"fileFormat":97,"inLanguage":63,"description":67,"dateModified":98,"datePublished":99,"encodingFormat":97,"isAccessibleForFree":100,"interactionStatistic":101},"DigitalDocument",{"url":87,"@type":88,"width":89,"height":90},"https://docshare.wps.com/thumbnails/be-3d-self-diagnostic-software-section-4-3-led-error-code-identification/561183.png","ImageObject",300,407,{"name":92,"@type":93},"eBook King","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-22","2026-10-12",true,{"@type":102,"interactionType":103,"userInteractionCount":19},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"What two conditions trigger BE-3D self-diagnostic error identification?","Question",{"text":112,"@type":113},"Error identification is triggered by either a busy bus condition or a device failure to respond to IIC.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"How does the software determine which device is faulty?",{"text":117,"@type":113},"After attempting to release a busy bus, it communicates with each device in turn to check for faults.",{"name":119,"@type":110,"acceptedAnswer":120},"How are detected errors reported to the user?",{"text":121,"@type":113},"Errors are reported through an LED flash sequence; the relevant device/error number is determined by counting the flashes as defined in the error-count table.","https://schema.org",{"og:url":83,"og:type":124,"og:title":65,"og:site_name":95,"og:description":67},"article",{"robots":126,"canonical":83},"index,follow",{"doc_id":128,"site_id":62},561183,1792144936,{"code":4,"msg":5,"data":131},{"doc_id":128,"user_id":132,"nickname":92,"user_avatar":133,"doc_module":4,"category_id":29,"category_name":30,"doc_title":65,"doc_description":67,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":19,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":8,"language":139,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":140,"faqs":141,"seo_title":142,"seo_description":67,"update_tm":143,"read_time":81},962088006270,"https://ap-avatar.wpscdn.com/davatar_085a072bc5b1113ac321206ff7593b45","4-3. BE-3D SELF DIAGNOSTIC SOFTWARE  \nThe identification of errors within the BE-3D chassis is triggered in one of two ways :-1: Busy busy or 2: Device failure to respond to IIC. In the event of one of these situations arising the software will first try to release the bus if busy [Failure to do so will report with continuous flashing LED] and then communicate with each device in turn to establish if a device is faulty. If a device is found to be faulty the relevant device number will be displayed through the LED [Series of flashes which must be counted] See Table 1., non fatal errors are reported using this method.  \n\n| ERROR | LED ERROR COUNT |\n| --- | --- |\n| No error | 00 |\n| Not allowed (may be confused with Sircs response flash!) | 01 |\n| Protection circuit trip \u003C ANY TIME > | 02 |\n| IIC SCL LOW \u003C POWER UP ONLY > | 03 |\n| IIC SDA LOW \u003C POWER UP ONLY > | 04 |\n| IIC SDA & SCL LOW \u003C POWER UP ONLY > | 05 |\n| Jungle / Chroma controller no acknowledge \u003C POWER UP ONLY > | 06 |\n| Video Switch no acknowledge\u003Cbr>\u003C POWER UP ONLY > | 07 |\n| Tuner no acknowledge | 08 |\n| MSP no acknowledge | 09 |\n| NVM no acknowledge | 10 |\n| M3L TXD Low \u003C POWER UP ONLY > | 11 |\n| M3L RXD Low \u003C POWER UP ONLY > | 12 |\n| M3L ENABLE Low \u003C POWER UP ONLY > | 13 |\n| M3L TXD & RXD Low \u003C POWER UP ONLY > | 14 |\n| Compact Text test fail \u003C POWER UP ONLY > | 15 |\n| AV switch cannot power on reset\u003Cbr>\u003C Chassis Initialisation > | 16 |\n| Cannot initialise jungle ( after initial power on checked out OK ) - \u003C Chassis initialisation > | 17 |\n| NVM acknowledge fail after initialisation (STBY +5V same as micro!) | 18 |\n| Multiple devices with no acknowledge\u003Cbr>\u003C POWER UP ONLY > | 19 |\n| Compact text run-time failure after power up check (+9V test) | 20 |\n| AV SWITCH response failure after power up check (+9V test) | 21 |\n| JUNGLE / CHROMA controller response failure after power up check (-9V test) | 22 |\n| Compact text does not respond (-5V test) | 23 |\n| MSP run-time failure\u003Cbr>\u003C MAY NOT BE FATAL-DISPLAY ON ERROR READER > | 24 |\n\n\n| M3L bus Clock low time out after data send ( run-time failure) | 25 |\n| --- | --- |\n| M3L bus Clock low time out after data send ( at power up check ) | 26 |\n| M3L bus Clock low time out after data send ( at initialisation ) | 27 |\n| DSP run-time failure\u003Cbr>\u003C MAY NOT BE FATAL-DISPLAY ON ERROR READER > | 28 |\n\nFlash Timing Example : e.g. error number 3  \nStBy LED  \nON ON ON  \nOFF OFF","cbCaiiOqoyqx6tXy","https://ap.wps.com/l/cbCaiiOqoyqx6tXy","pdf",80480,"English","# BE-3D SELF DIAGNOSTIC SOFTWARE\n## Error detection triggers\n## LED indication method\n## Error code table (LED count)","[{\"question\":\"What two conditions trigger BE-3D self-diagnostic error identification?\",\"answer\":\"Error identification is triggered by either a busy bus condition or a device failure to respond to IIC.\"},{\"question\":\"How does the software determine which device is faulty?\",\"answer\":\"After attempting to release a busy bus, it communicates with each device in turn to check for faults.\"},{\"question\":\"How are detected errors reported to the user?\",\"answer\":\"Errors are reported through an LED flash sequence; the relevant device/error number is determined by counting the flashes as defined in the error-count table.\"}]","BE-3D SELF DIAGNOSTIC SOFTWARE - Section 4-3 - LED error code identification | PDF",1791805203]