DLPU102B December   2020  – July 2022

 

  1.   Read This First
    1.     Trademarks
    2.     About This Guide
    3.     Related Documentation from Texas Instruments
    4.     If You Need Assistance
  2. 1DLP LightCrafter Dual DLPC900 EVM Overview
    1. 1.1 Welcome
    2. 1.2 DLP LightCrafter Dual DLPC900 Evaluation Module (EVM) Hardware
    3. 1.3 EVM Board
    4. 1.4 Other Items Needed for Operation
    5. 1.5 DLP LightCrafter Dual DLPC900 Connections
      1. 1.5.1 DLP LightCrafter Dual DLPC900 LED Enable and PWM Outputs
      2. 1.5.2 DLP LightCrafter Dual DLPC900 Trigger Input and Output Voltage Selectors
    6. 1.6 DLP LightCrafter Dual DLPC900 EVM Flex Cable
    7. 1.7 DLP LightCrafter Dual DLPC900 EVM and DMD EVM Assembly
  3. 2Quick Start
    1. 2.1 Power-up the DLP LightCrafter Dual DLPC900 EVM
    2. 2.2 Creating A Simple Pattern Sequence
  4. 3Operating the DLP LightCrafter Dual DLPC900 EVM
    1. 3.1  DLP LightCrafter Dual DLPC900 Control Software
    2. 3.2  PC Software
    3. 3.3  System Common Controls
      1. 3.3.1 Operating Mode
      2. 3.3.2 Connected DMD Type
      3. 3.3.3 EVM Information
      4. 3.3.4 Status
    4. 3.4  System Settings
    5. 3.5  Video Mode
      1. 3.5.1 Video Support
    6. 3.6  Pattern Modes
      1. 3.6.1 Menu Bar
      2. 3.6.2 Creating a Pattern Sequence in Pattern On-The-Fly Mode
      3. 3.6.3 Creating a Pattern Sequence in Pre-Stored Pattern Mode
      4. 3.6.4 Reordering a Pattern Sequence using the Edit LUT Feature
        1. 3.6.4.1 Special Considerations for Input Triggers when using the Edit LUT Feature
      5. 3.6.5 Creating a Pattern Sequence in Video Pattern Mode
      6. 3.6.6 Creating a Pattern Sequence With DMD Block Load
      7. 3.6.7 Pattern Settings
    7. 3.7  Batch Files
      1. 3.7.1 Execute Batch File
      2. 3.7.2 Creating and Saving Batch Files
        1. 3.7.2.1 Creating and Saving a Batch File Using the GUI
        2. 3.7.2.2 Creating a Batch File Using a Text Editor
      3. 3.7.3 Loading a Batch File
      4. 3.7.4 Adding a Batch File to the Firmware
    8. 3.8  Peripherals
    9. 3.9  Firmware
      1. 3.9.1 Adding or Removing Patterns from the Firmware
        1. 3.9.1.1 Deleting Images
        2. 3.9.1.2 Adding Images
        3. 3.9.1.3 Adding Both Images and Batch Files
    10. 3.10 Flash Device Parameters
    11. 3.11 JTAG Flash Programming
    12. 3.12 Intel (Altera) FPGA Programming
  5. 4Connectors
    1. 4.1 Input Trigger Connectors
    2. 4.2 Output Trigger Connectors
    3. 4.3 DLPC900 UART Headers
    4. 4.4 DLPC900 I2C Port 0
    5. 4.5 DLPC900 I2C Port 1
    6. 4.6 DLPC900 I2C Port 2
    7. 4.7 JTAG Boundary Scan
    8. 4.8 GPIO and PWM
    9. 4.9 Power
  6. 5Power Supply Requirements
    1. 5.1 External Power Supply Requirements
  7. 6Safety
    1. 6.1 Caution Labels
  8. 7Revision History

3.7.1 Execute Batch File

The DLPC900 firmware has the option to store batch files within the firmware. These batch files contain commands that are executed to perform some sequence of settings without the user or host performing these commands. If the firmware contains batch files, the GUI queries the batch file names and list them in the Batch Command Sequence panel within the Batch Files Stored in the EVM group box. The user can then choose a batch file from the list to execute it.

The user can also designate a default batch file to be executed during the DLPC900 power-up sequence when the power is applied. For example, if the LEDs are to remain off after power has been applied to the EVM, a batch file can be created with the commands to turn the LEDs off, and then update the firmware with this batch file as the default. The updated firmware can then be uploaded to the EVM. The next time the power is applied to the EVM, the LEDs are disabled from turning on. See the DLPC900 Programmer's Guide for the batch file commands in Appendix B for a complete list of commands that can be used within a batch file.

Note: If an "IDX" error is received during execution of a batch file, this indicates that execution failed at the line number that follows IDX in the error message. POWER_CONTROL commands often result in an IDX error since the EVM can no longer communicate with the GUI because the power state has been changed.