EXE not writing to TDMS files

[YongqingYe]

Hi Joju,

Let's focus on how to reproduce the problem firstly. I just run your attached VI and didn't see any obvious problem when it running. You mentioned:

"but in some moment the tdms writer rutine "is out" and don´t work, but after some time, in some times short time(some seconds)"

How you observe the writer rutine "is out"? What's the meang of "out"? It that hang or something?

And would you please let me know the detail steps of repducing the problem?

Thanks,

Yongqing Ye

NI R&D

[Joju]

Hi YongqingYe;

the rutine works rightly "always", but after some time (it's imposible to determinate it time), the writer's tdms Vi, not doing his job, and don't return any error. to find this mistake some times it's necessary to process de TDMS file wiht a spreadsheet (Excel or Diadem) because the "timeout" of writer's rutine its veri little, some seconds, other times this error it's obvius because it's a few minutes.Remarks, the variable it's writing every 3 secons, +- some milisecons, if the difference between two consecutives values it's greater of 4 secons the error it's out.

[YongqingYe]

Hi Joju,

How did you observe the writer's VI stops working in your attached VI? You mentioned:

"to find this mistake some times it's necessary to process de TDMS file wiht a spreadsheet (Excel or Diadem) because the "timeout" of writer's rutine its veri little"

Then, how you process the TDMS file with a spreadsheet? Open it in Excel or DIAdem when it's written in LabVIEW?

[IanDeaville(ZF)]

Yongqing,

I've been busy elsewhere for a while, but managed to get back on this today.  The paths are totally identical in both systems; no extra or missing characters at all.  That prompted me to look at the other inputs into the Write TDMS block to see if one of those was invalid.  The data array is empty when it arrives at this block.  Tracing it back there is an array being built from 6 text elements.  Each of the elements is correct.  If I put a Trace onto the output array it seems fine, but with "retain wire values" enabled, hovering over the wire the pop-up shows #0, indicating that the array is empty.  Is this a known issue?

Any more suggestions?

Thanks,

Ian

[YongqingYe]

The empty array worthy more investigation, I'm not sure whether it's a known issue of LabVIEW, but seems a problem anyway.