• Code: 233
• Description: FGATE OFF error: YT
  he PFGATE ON signal still asserts within 5 seconds after processing the image in normal job or MUSIC for end position [Y]. The PFGATE ON signal still asserts when the next job starts.
• Causes: Defective ASIC (Lupus). Poor connection between controller and BICU. Defective BICU.
• Remedy: 1. Check the connection between the controller board and the BICU. 2. Replace the BICU. 3. Replace the controller board.

• Code: 234
• Description: FGATE ON error: M
  The PFGATE ON signal does not assert within 5 seconds after processing the image in normal job or MUSIC for start position [M].
• Causes: Defective ASIC (Lupus). Poor connection between controller and BICU. Defective BICU.
• Remedy: 1. Check the connection between the controller board and the BICU. 2. Replace the BICU. 3. Replace the controller board.

• Code: 235
• Description: FGATE OFF error: M
  The PFGATE ON signal still asserts within 5 seconds after processing the image in normal job or MUSIC for end position [M]. The PFGATE ON signal still asserts when the next job starts.
• Causes: Defective ASIC (Lupus). Poor connection between controller and BICU. Defective BICU.
• Remedy: 1. Check the connection between the controller board and the BICU. 2. Replace the BICU. 3. Replace the controller board.

• Code: 236
• Description: FGATE ON error: C
  The PFGATE ON signal does not assert within 5 seconds after processing the image in normal job or MUSIC for start position [C].
• Causes: Defective ASIC (Lupus). Poor connection between controller and BICU. Defective BICU.
• Remedy: 1. Check the connection between the controller board and the BICU. 2. Replace the BICU. 3. Replace the controller board.

• Code: 237
• Description: FGATE OFF error: C
  The PFGATE ON signal still asserts within 5 seconds after processing the image in normal job or MUSIC for end position [C]. The PFGATE ON signal still asserts when the next job starts.
• Causes: Defective ASIC (Lupus). Poor connection between controller and BICU. Defective BICU.
• Remedy: 1. Check the connection between the controller board and the BICU. 2. Replace the BICU. 3. Replace the controller board.

• Code: 240
• Description: LD error: Bk
  The BICU detects LDB error a few times consecutively when LDB unit turns on after LDB initialization.
• Causes: Worn-out LD. Disconnected or broken harness of the LD
• Remedy: 1. Replace the harness of the LD. 2. Replace the laser optics housing unit. 3. Replace the BICU.

• Code: 241
• Description: LD error: Y
  The BICU detects LDB error a few times consecutively when LDB unit turns on after LDB initialization.
• Causes: Worn-out LD. Disconnected or broken harness of the LD
• Remedy: 1. Replace the harness of the LD. 2. Replace the laser optics housing unit. 3. Replace the BICU.

• Code: 242
• Description: LD error: M
  The BICU detects LDB error a few times consecutively when LDB unit turns on after LDB initialization.
• Causes: Worn-out LD. Disconnected or broken harness of the LD
• Remedy: 1. Replace the harness of the LD. 2. Replace the laser optics housing unit. 3. Replace the BICU.