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.

LDC1614EVM logging stopped suddenly, about 8 hours later. Is it possible to continue the logging more than 24 hours ?

Other Parts Discussed in Thread: LDC1614, LDC1614EVM

I bought LDC1614EVM. ( LDC1614 Evaluation Module for Inductance to Digital Converter with Sample PCB Coils )

I attached herical coil and measured the inductance with "the LDC13xx/LDC16xx EVM GUI Setup v1.0".

I tried the logging for several minutes all right.

But, when I tried to measure the inductance of the herical coil for 24 hours,
The logging stopped suddenly about 8 hours and 38 minutes later.

Microsoft Visual C++ Runtime Library pop up the Alert window with the message below.

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

I tried again with almost the same result.
This time, the logging stopped about 9 hours and 26 minutes later.

Would anybody tell me why the logging had stopped?


Dose anybody know how I can avoid this problem?

I attached the first and the last lines of the logging file below.


2015-9-15_LDC1614EVM_manabe_henpei.txt
318,644,096 byte

First Line
15.09.15.16.35.33.057.000,35.553,uH,0.048,uH,0.048,uH,0.048,uH,10341904,268435455,268435455,268435455
15.09.15.16.35.33.057.000,35.553,uH,0.048,uH,0.048,uH,0.048,uH,10341899,268435455,268435455,268435455
15.09.15.16.35.33.073.000,35.553,uH,0.048,uH,0.048,uH,0.048,uH,10341899,268435455,268435455,268435455
...
16.09.15.01.13.39.561.000,35.562,uH,0.048,uH,0.048,uH,0.048,uH,10340629,268435455,268435455,268435455
16.09.15.01.13.39.577.000,35.562,uH,0.048,uH,0.048,uH,0.048,uH,10340619,268435455,268435455,268435455
16.09.15.01.13.39.593.000,35.562,uH,0.048,uH,0.048,uH,0.048,uH,10340619,268435455,268435455,268435455
EOF

(((16-15)*24+(1-16))*60+(13-35))*60 = 31080 sec = 518 min = 8h 38min

2015-9-16_LDC1614EVM_manabe_henpei.txt
344,601,547 byte

16.09.15.09.44.32.926.000,32.332,uH,0.048,uH,0.048,uH,0.048,uH,10340181,268435455,268435455,268435455
16.09.15.09.44.32.938.000,32.332,uH,0.048,uH,0.048,uH,0.048,uH,10340181,268435455,268435455,268435455
16.09.15.09.44.32.942.000,32.332,uH,0.048,uH,0.048,uH,0.048,uH,10340181,268435455,268435455,268435455

16.09.15.19.10.05.571.000,35.571,uH,0.048,uH,0.048,uH,0.048,uH,10339294,268435455,268435455,268435455
16.09.15.19.10.05.571.000,35.571,uH,0.048,uH,0.048,uH,0.048,uH,10339294,268435455,268435455,268435455
16.09.15.19.10.05.587.000,35.571,uH,0.048,uH,0.048,uH,0.048,uH,10339289,268435455,268435455,268435455

(((19-09))*60+(10-44))*60 = 33960 sec = 566 min = 9h 26min

  • Hello,


    I am sorry about the problem you encountered. I will need to talk to the software developer about this issue.


    Regards,

    ChrisO

  • Kesaga-san,


    What does it read regarding 8GB and 7.88GB?

    May be your PC ran out of memory?

  • I installed 8GB of memory on my note book PC.

    Usable memory is 7.88GB

    I think I have enough memory for GUI program.

    The log file size is about 340MB.

    I have 7.88GB memory --- about 20 times bigger memory is available.

    So, I think, it is not the memory size problem on my PC. 

  • I checked and found there is memory leak in your LDC13xx16xx EVM GUI 1.0.0.0 program!  

    I use window's task manager to watch how much your process "ldc 13xx 16xx.exe" consume.

    It consumed about 39MB of memory when I started the program.

    But, when I push the start button, it increases gradually.

    30 minutes later it consume 137MB of memory.

    So, 60 minutes later, it'll consume about 200MB memory, I think.  

    8 hours later, it would consume 1.6GB of memory.

    I think your application will be out of memory somewhere when it reached 1.6GB limit.

    That's why "ldc 13xx 16xx.exe" will stop about 8 hours after you started the measurement.

    Would you please stop the memory leak in next version in near future ?

    Wish to get the "ldc 13xx 16xx.exe" with out memory leak next week.

    By the way, this memory leak occurs even if I didn't start  the logging.

    Just start the measurement, the memory usage will increase linearly. 

    Memory Usage is about 38MB when I started the LDC13xx16xx EVM GUI. 

    Memory Usage is about 137MB 30 minutes later.

    About 100MB/30minutes = 200MB/hour = 1.6GB/8hours

  • Hello Koyo,

    Thank you for notifying our team of the memory leak in the LDC1614 EMV GUI. We are releasing a new GUI by the end of September, but it won't be available available next week.

    Best regards,

    Blair

  • Thank you very much for the good news.  

    By the way, I found a simple way to reduce the memory leak. 

    Just click the minimize button on right top, and then open it again from the task bar. 

    Private working memory for ldc 13xx 16xx .exe will be reduced to around 25MB. 

    So, If I do this trick every 8 hour, I think I can continue the logging for 24 hours. 

    Hope to receive the fixed version soon!

  • Hello Koyo,

    That's very interesting. The memory leak must be involved with the graphing function. The new GUI is currently in the approvals process, so we should be able to get it online sometime next week.

    Best regards,

    Blair

  • I tried the new GUI - Sensing Solutions EVM GUI-1.8.8 today.
    The memory leak seems to be fixed. It consume about 260MB of memory, not increasing all right.
    Logging is all right, too.
    Thank you very much!

    But, there seems to be some other problems below.
    Raw data display is all right, but frequency and inductance data display is strange - always NAN.

    e2e.ti.com/.../1682200
    Sensing Solutions EVM GUI Tool v1.8.8 (Rev. A) (ZIP 60718 KB ) 12 Oct 2015
  • Please go to the configuration page and verify that all of the frequency dividers are valid (at least one). If any of them are zero, for example, the frequency and inductance data can not be calculated.

    Best regards,

    Blair

  • Thank you very much.

    I set all the divide ratio from 0 to 1. 

    So, the value displayed in red in the configuration page means - something is wrong!

    Now, I can get the frequency and the inductance all right. 

    Thank you very much for your help!