• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 28 subscribers
  • Views 512 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Seq. Abort is red, and cannot autostart internal pattern projection

Wu Di
Prodigy 90 points

Hello, 

I'm using LightCrafter 4500 for 3-D reconstruction application. I'm now running patterns correctly. But the Seq. Abort is always red.

And if i restart the device, it will not automatically enter the internal pattern mode. I set the ini to be autostart and internal pattern mode at start, but don't work. The Seq. Abort is red for about 2 seconds when the device is starting, then turns to gray and stuck there. seems that the device engaged some problem with internal pattern projection. But if I click "validate sequence" and then "play", everything is ok except the Seq. Abort is red.

For more, when powering on the device, sometimes it needs to be reset for several times then can be started.

How can I solve these problems?

P.S. ini file as following:

APPCONFIG.VERSION.SUBMINOR 0x0 ;
DEFAULT.AUTOSTART 0x0 ;
DEFAULT.DISPMODE 0x1 ;
DEFAULT.SHORT_FLIP 0x0 ;
DEFAULT.LONG_FLIP 0x0 ;
DEFAULT.TRIG_OUT_1.POL 0x0 ;
DEFAULT.TRIG_OUT_1.RDELAY 0xbb ;
DEFAULT.TRIG_OUT_1.FDELAY 0xbb ;
DEFAULT.TRIG_OUT_2.POL 0x0 ;
DEFAULT.TRIG_OUT_2.WIDTH 0xbb ;
DEFAULT.TRIG_IN_1.DELAY 0x0 ;
DEFAULT.TRIG_IN_2.POL 0x0 ;
DEFAULT.RED_STROBE.RDELAY 0xbb ;
DEFAULT.RED_STROBE.FDELAY 0xbb ;
DEFAULT.GRN_STROBE.RDELAY 0xbb ;
DEFAULT.GRN_STROBE.FDELAY 0xbb ;
DEFAULT.BLU_STROBE.RDELAY 0xbb ;
DEFAULT.BLU_STROBE.FDELAY 0xbb ;
DEFAULT.INVERTDATA 0x0 ;
DEFAULT.LEDCURRENT_RED 0x97 ;
DEFAULT.LEDCURRENT_GRN 0x78 ;
DEFAULT.LEDCURRENT_BLU 0xf5 ;
DEFAULT.PATTERNCONFIG.PAT_EXPOSURE 0x208d ;
DEFAULT.PATTERNCONFIG.PAT_PERIOD 0x2710 ;
DEFAULT.PATTERNCONFIG.PAT_MODE 0x3 ;
DEFAULT.PATTERNCONFIG.TRIG_MODE 0x1 ;
DEFAULT.PATTERNCONFIG.PAT_REPEAT 0x1 ;
DEFAULT.PATTERNCONFIG.NUM_SPLASH 0x1 ;
DEFAULT.SPLASHLUT 0x0 0x1 ;
DEFAULT.PATTERNCONFIG.NUM_LUT_ENTRIES 0x8 ;
DEFAULT.PATTERNCONFIG.NUM_PATTERNS 0x8 ;
DEFAULT.SEQPATLUT 0x64808 0x24800 0x24804 0x64800 0x24140 0x24144 0x24148 0x2414c 0x24150 ;
DEFAULT.PORTCONFIG.PORT 0x1 ;
DEFAULT.PORTCONFIG.BPP 0x0 ;
DEFAULT.PORTCONFIG.PIX_FMT 0x0 ;
DEFAULT.PORTCONFIG.PORT_CLK 0x0 ;
DEFAULT.PORTCONFIG.ABC_MUX 0x0 ;
DEFAULT.PORTCONFIG.PIX_MODE 0x1 ;
DEFAULT.PORTCONFIG.SWAP_POL 0x0 ;
DEFAULT.PORTCONFIG.FLD_SEL 0x0 ;
PERIPHERALS.I2CADDRESS[0] 0x34 ;
PERIPHERALS.I2CADDRESS[1] 0x3a ;
DATAPATH.SPLASHSTARTUPTIMEOUT 0x0000 ;
DATAPATH.SPLASHATSTARTUPENABLE 0x0 ;

Wudi

  • 0
    TI__Genius 13235 points
    Hi Wudi,

    Thanks for posting. Auto starting in pattern sequence mode is a known issue in the 2.0 FW release. A new version (3.0) of the FW and GUI will be released in the next 2 weeks, which will address this issue and provide several new features.

    Thanks,
    Clinton