Time to close TDMS file

[Eric_Lang]

Hello,

I am currently logging files using a cRIO with file sizes between 50 and 100 MB.  At times it may take upwards of two minutes to close the logging operation.

Is this normal?  Is there anything that I can do to speed up this operation?

Thanks!

[MCOTO]

Hello Eric,

It does not look to be normal. Some file operations on cRIOs could be affected when there are several files in the folder (hundreds). Transferring the files via FTP and cleaning up the folder could help in the execution speed of this operation.

Please let me know if this is your case.

Regards,

MCOTO

[Eric_Lang]

MCOTO,

I don't believe this is the cause. I am logging on the cRIO C drive and transferring the file to the USB drive. I leave the files on until a power cycle, at which point I clean the folder. I never exceed more than 15 or so files.

Any other ideas?

[deppSu]

It doesn't look normal for me either, can you attach your program? So that we can have a look.

[Eric_Lang]

I've attached two files.  LogModule.vi is the master logging module where I initialize the TDMS file, log the majority of data, close the file and move afterward.  AuxLogModule.vi operates at a slower rate, where I log the performance of the cRIO to a separate page on the same TDMS file.  When I call to close the logging operation, the LogModule.vi will wait until it receives a signal from AuxLogModule.vi that it is finished.  The hangup happens in the "Close" state.

Let me know if something stands out.

Thanks!

[Eric_Lang]

Having troubles attaching...

[Mellobuck]

Wouldn't removing the Defragmentation step speed up your operation? That can always be done later.

[deppSu]

The TDMS Degragment function inside youe "close" state is time consuming. You can skip it in your logging process and do it seperately if necessary.