How to work video projection of pattern sequence mode on GUI ver2.0.0 and FW ver2.0?

Hello Uryyy,

Apologies for not responding to your another thread question. 

Yes, for this specific steps, Pattern Sequence via Video Mode is hanging with GUI2.0 revision. Please continue using the old GUI ver1.x. We haven't made significant changes to the GUI as such from v1.x to v2.0, so old GUI should be fine for your experiment.

We will fix the issue and release another GUI at later point of time. 

Regards,

Sanjeev

Hello Sanjeev,

Thank you for your cooperation.

The conclusion is NG with old GUI.
I tried each tests.

FW v1.1.0 - GUI v1.2 : OK
FW v1.1.0 - GUI v2.0 : NG
FW v2.0.0 - GUI v1.2 : NG
FW v2.0.0 - GUI v2.0 : NG

Regards,
Uryyy

Hello Uryyy,

Sorry for late response. 

Are you familiar with building the GUI tool from the source code? If so I can help you with making simple changes; if you are not familiar then i think you need to wait for some more time.

Use 1.2 GUI source code, make the following changes - 

File - API.cpp , function 

int LCR_ValidatePatLutData(unsigned int *pStatus)
{

    hidMessageStruct msg;

    LCR_PrepWriteCmd(&msg, LUT_VALID);    

    if(LCR_SendMsg(&msg) < 0)

        return -1;
     
     _sleep(3000);  //Add delay here based on Visual Studio or GCC you can call Sleep or _sleep function. 

    *pStatus = 0xFF;

   
    LCR_PrepReadCmd(LUT_VALID);

    if(LCR_Read() > 0)

    {

        memcpy(&msg, InputBuffer, 65);

        *pStatus = msg.text.data[0];

        return 0;

    }

    return -1;

}


Regards,
Sanjeev

Hello Sanjeev,

Thank you for continuous help.

I tried building GUI on Visual Studio Express 2013.

I couldn't find project file for VS Express 2013.
Then I made project from scratch and built LCR4500 GUI .cpp/.h.
However, many errors almost say "Qxxxx:No such file or directory" .

Can I use VS Express 2013 for building GUI?

Regards,
Uryyy

Hello Sanjeev,

Thank you.
I could build GUI and GUI works fine on FW2.0 via your suggestion.

Regards,
Uryyy

Okay. We will fix the issue in the next GUI release.

Regards,

Sanjeev