02-28-2007 11:24 AM
02-28-2007 04:04 PM
03-01-2007 07:17 AM
Thanks for the quick response. I looked at the forum you mentioned but didn't see any work arounds for this.
Doesn't National Instruments have an Expert Labview Programmer that can go in to the code and figure out why the files aren't being closed or released by labview? The Express vi's were one of the KEY selling points for all the hardware and software that we bought from NI. They simplify programming, for non programmers. It's really not acceptable just to say yes we know there is a bug yet not give a work around for it.
I cannot reproduce all the features that are in the Write to Measurement Express VI. I need some help on this one.
How do I go about escilating this?
03-01-2007 08:10 AM - edited 03-01-2007 08:10 AM
Please understand that I can suggest a workaround, and I've tested it in your scenario and it seems to work OK, but I cannot guarantee this workaround for all possible use cases of this Express VI. It is for this reason that we generally don't like to recommend one-off modifications to VIs that ship with LabVIEW - they do not get tested with as wide a set of use cases as we do on VIs when we ship them. As such, I'm not going to just hand you a VI to replace in vi.lib, but I will show you a few edits you can make to work around this issue.
Open this VI: "[LabVIEW Install Dir]\vi.lib\express\express shared\ex_TDMS\ex_createorOpenTDMS.vi"
Open its diagram. Near the left there's a section that looks like this:
The current known bug is with the "Not A Number/Path/Refnum?" function on TDMS files, so you'll see the following changes in the below diagram, which hopefully you can make and try out in your use case. I would highly recommend making a backup copy of this VI before saving any changes!
Hopefully with these three instructions and comparing the shipping and workaround images you can successfully get up and running.
Message Edited by Jeff B on 03-01-2007 08:12 AM
03-01-2007 11:10 AM
03-01-2007 11:19 AM
Here is the log file that Diadem creates.
The Error Reads
ERROR: TDS Exception in Initialize: Tds Error: TdsErrAccessDenied(8):
03-07-2007 06:27 AM
03-08-2007 05:35 PM
03-09-2007 06:28 AM
The problem with the Write to measurement express Vi is bigger than just not closing out the files so they can be read in Diadem. Anyone that has a continuous logging application that uses this express vi will start to have memory issues as more and more new files are created while the old files aren't completely closing out. My application was writing a new file every 12 hours in 24 different VI's.. After two weeks I found out that there was over 8064 open files, that were locking up the Windows box. Not to mention all the data we lost.
Using the low level VI's is a great solution for those that have tons of labview experience however it's not a very good solution for us non programmers that were sold on labview because of the express VI's. Remember, the Write to Measurement Express VI has a lot more functions than simple reading and writing the data. The solution is not as simple as just using the low level VIs.
So here I sit with $$k in hardware and software from NI with my management asking is it ready yet, it was suppose to be easy... and I am trying to explain that Labview has a few bugs in it that they aren't fixing until the next version.
This isn't acceptable to me. How do I escilate this?
03-09-2007 08:35 AM