write to measurement file vi bug?

[LandyRover]

Hi Dominic...

As I mentioned above to Ravensfan, do I get any more free evaluation days, to replace the 10 or so I've lost while fighting this "Bug"?

😉

I still have no indication of how many I have left by the way.

Regards.

Dave B.

[tbob]

That was a good bug catch, and done by a newbie.  I say NI should give him 30 more days free trial.  Does anyone else concur or disagree?

[RavensFan]

---

tbob wrote:

That was a good bug catch, and done by a newbie.  I say NI should give him 30 more days free trial.  Does anyone else concur or disagree?

---

I'd agree his time should be extended, however NI is able to do that.

I did a little more investigation on the bug.  The bug is not present in LV 8.6.  It works just as it should.  I converted that Express VI to a regular subVI and looked into it.  In the LV8.6 version, the outer most case structure, the false case, the file path is wired straight through from the outer loop's shift register, thus remembering the previous file name.  In the LV 2009 version, that same false case has a "Not a Path" constant wired in which causes the outer loop shift register to effectively forget the previous file path.

I didn't look to see if there were any other differences between the two versions.

[Dominic.Walker]

Hey Dave,

As technical support this is not something I can do for you.  I'd suggest ringing your local NI office and explaining your situation as getting an extended trail might be an option.  

The UK office of National Instruments can be contacted on 01635 523545.  

I hope this helps.

Cheers,

[JÞB]

---

LandyRover wrote:

Hi Dominic...

As I mentioned above to Ravensfan, do I get any more free evaluation days, to replace the 10 or so I've lost while fighting this "Bug"?

😉

I still have no indication of how many I have left by the way.

Regards.

Dave B.

---

Hey Dave-

It seems like you are getting the hang of LabVIEW pretty quick!  Nice catch.  Bite the bullet and buy the darn thing.  You're going to do it anyway.  Wellcome to the forums-  change your tag line to "3 years SSP left" 

[BjarneDK]

Hi,

Im a newbee who has the same bug problem with whirte to measurement file, and I found this tread. Im trying to use your work around, and I found the select statement. But were do I find the two "things" (the file name one and the other one) attached to the select?

My setup:

Win7 64bit

LabVIEW 2009 sp1 64bit 

[RavensFan]

The filename is a file path control.  If you right click on the filename input and choose Create a Control, you'll get it.  The other is a Not a Path Constant.  You can search the palettes for it by name.  I found it under 7.x Functions >> Open G >> OpenG File tools >> File Constants.  But I'm not sure you'd have it if you don't have the correct OpenG toolkit installed.

So see if you can use it from this snippet.

Message Edited by Ravens Fan on 03-04-2010 10:30 AM

[Dominic.Walker]

As Ravens Fan mentioned, the first one is a front panel Filepath Control, found on the Control Palette, under "Strings & Paths" which can be found within Modern, System, or Classic. 

The other is a Not a Path constant can be found on the functions palette under Programming -> File I/O -> File Constants.  

Kind regards,

[BjarneDK]

Thanks, I couldnt find it, but found a "emty path constant" I think that it will do the job? I seems to work :-), as others, I have used a lot of time on that VI!

[RavensFan]

---

Dominic.Walker wrote:

As Ravens Fan mentioned, the first one is a front panel Filepath Control, found on the Control Palette, under "Strings & Paths" which can be found within Modern, System, or Classic. 

The other is a Not a Path constant can be found on the functions palette under Programming -> File I/O -> File Constants.  

Kind regards,

---

I went looking it for it under File I/O and just never saw it, but it is there.  So I wonder why when I did a search of the palettes, it only gave me the one hidding under 7.x functions >> OpenG?