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

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

• Code: 233
• Description: FGATE OFF error: Y
  • The 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 BCU. • Defective BCU
• Remedy: 1. Check the connection between the controller board and the BCU. 2. Replace the BCU. 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 BCU. • Defective BCU
• Remedy: 1. Check the connection between the controller board and the BCU. 2. Replace the BCU. 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 BCU. • Defective BCU
• Remedy: 1. Check the connection between the controller board and the BCU. 2. Replace the BCU. 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 BCU. • Defective BCU
• Remedy: 1. Check the connection between the controller board and the BCU. 2. Replace the BCU. 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 BCU. • Defective BCU
• Remedy: 1. Check the connection between the controller board and the BCU. 2. Replace the BCU. 3. Replace the controller board.

• Code: 240
• Description: LD error: K
  The BCU 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 BCU.