This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DLPLCR6500EVM: programming guide and onthefly example text

Part Number: DLPLCR6500EVM

I am still struggling to get the 6500 Picture On-The-Fly mode working without the provided GUI. The programmers guide (dlpu018d) example in Table 5-3 seems incomplete. I did, however, stumble across two files, both named "onthefly.txt" in the folders "C:\Texas Instruments-DLP\DLPC900REF-SW-3.0.0\DLPC900REF-GUI\LCR6500_Images" and "C:\Texas Instruments-DLP\DLPC900REF-SW-3.0.0\DLPC900REF-GUI\LCR9000_Images". While these provide more clues, a number of questions arise. 

The guide's Table 5-3 steps 4 and 7 suggests a USB 1A2A (Initialize BMP Pattern On-The-Fly Master aka PATMEM_LOAD_INIT_MASTER) describes the amount of data about to be shipped by 1A1B. For example, x03E8 (1000 bytes in step 4) is followed by x0200 (512 bytes in step 5) plus x01E8 (488 bytes in step 6). However, x07D0 (2000 bytes in step 7) is followed by x0200 (512 bytes in steps 8, 9 and 10) leaves 464 bytes (x0100 is a typo which should read x01D0) in step 11. The x1432 in LCR6500 does agree with the 51 times x64 plus x46. Also, the x19e6 (6630 decimal) of LCR9000 does agree with 13 times x01f8 plus x04e. However:

1) The guide's Table 5-3 steps 5, 6, 8, 9, 10 and 11 suggests a maximum of 512 bytes are loaded with USB 1A1B (Load BMP Pattern On-The-Fly Master aka PATMEM_LOAD_DATA_MASTER). However, the LCR6500 example suggests the maximum is 100 (0x64) while the LCR9000 suggests a maximum of 504(0x01f8). Why do three different examples each have a different maximum?

2)  The guide's Table 5-3 steps 2 and 3 suggests a USB 1A34 (Pattern LUT Definition aka MBOX_DATA) describes each of two images (pattern 0 from image 0 and pattern 1 from image 1). However, there are 56 MBOX_DATA statements in both LCR examples, suggesting there are 56 patterns from 56 images in each case. In the guide, the Pattern LUT Configuration (USB 1A31 aka PAT_CONFIG) comes in step 12 just prior to running the pattern (step 13 USB 1A24 aka PATT_START_STOP) whereas the LCR6500 example has two PAT_CONFIG commands between MBOX_DATA and PATMEM_LOAD_INIT_MASTER. The LCR9000 example has one PAT_CONFIG command between MBOX_DATA and PATMEM_LOAD_INIT_MASTER then another one just prior to PAT_START_STOP. How many PAT_CONFIG commands are required (1 or 2) and where do they go or does it matter?

  • Hello Derek,

    1)  You do not have to load the maximum with each line.  I believe if you use the GUI now to record loading patterns it will use 0x1F8.

    The easiest way to look at these is to install the GUI an d run in Virtual Connection Mode.

    • Load the images and timing you want in the viewer
    • Turn on "Batch Command Logging" 
    • On the Pattern On-The_Fly window press "Update LUT"
    • If you want to run, press "Start"
    • Return to your Batch file window and use the "Save Batch File" button.

    This will save and allow you to view the command sequence.  When I do it for the 6500 or 9000 it uses 0xF8.  I would use the commands it generates, since they are known to work.

    2)  This is a consequence of using the GUI to record batch scripts.  When you switch from the Batch page to the Pattern On-The-Fly Mode tab and press Play, it regenerates PAT_CONFIG command.  This is really the only one you should need

  • Following your instructions, the batch file is:

    MBOX_DATA : 0x00 0x00 0x69 0x00 0x00 0x11 0x00 0x00 0x00 0x00 0x00 0x00
    PAT_CONFIG : 0x01 0x00 0x00 0x00 0x00 0x00
    PAT_CONFIG : 0x01 0x00 0x00 0x00 0x00 0x00
    PAT_START_STOP : 0x02

    I understand the last line. Please explain the other three. Is one of the PAT_CONFIG's redundant (per your previous post)? I confirmed the first byte is the number of images by loading a second image, as expected. Also, it doesn't seem to matter which image I upload to the 6500, the result is the same. How can I view the image data?

    If I want to send uncompressed data, there are bits I can set in the image header (Section 2.4.2 of dlpu028d). I don't see this data in the PATMEM_LOAD_DATA_MASTER (things like 53 70 6C 64 and FF FF FF FF FF FF FF FF as shown in Table 2-97). How do I enter a simple uncompressed image via USB?

    Thanks!

  • Derek,

    We will be releasing a new GUI and Firmware very soon, that has the capability to set the compression options. This will allow you to capture the commands for uncompressed. We are working on the API guide for some of the new functionality. The new compression control functionality will appear on the "Pattern Settings" are under "Pattern Mode"

    In the current GUI there is no control over compression, only via batch commands (i.e. § 2.4.2 of DLPU028) You would have to do it via a batch file that you load and execute, including combing the data into PATMEM_LOAD_DATA_MASTER : commands in uncompressed format.

    Fizix
  • Is the new guide out yet? If so, where can I find it (what title should I search on)? If not, can I get a draft version?

    Thanks!

  • Derek,

    It is getting closer - I hope in the next several weeks.

    Fizix