Cat

A few times over the past week or so when I try to access LAVA I get variations on the following msgs:

Fatal error: Out of memory (allocated 1048576) (tried to allocate 491520 bytes) in /home/lavagorg/public_html/admin/sources/base/ipsRegistry.php on line 744

Fatal error: Out of memory (allocated 11010048) (tried to allocate 48115 bytes) in /home/lavagorg/public_html/ips_kernel/classDbMysqliClient.php on line 465

Just me, or a "feature" of the server upgrade?

LabVIEW specifically and NI generally tries to strike a balance between putting out new features (which is the only thing users are really willing to shell out money for)

It's not quite *that* bad. I've had a SSP for... well, probably as long as NI has offered them, and I am always years behind on upgrading. Why the SSP?? Because, especially in the early days when there were relatively few users, and actual LV competitors, I wanted to encourage NI to keep supporting LV.

I personally need as absolutely stable of a development environment as possible. I am often writing code in a place where I can't get online for help if LV starts crashing for no apparent reason. I loved 7.1.1 and didn't upgrade to 8.6.1 until after 2009 came out. I am being pushed by users to start running in a 64-bit environment so I'm starting to run LV2010 experimentally, way ahead of my usual upgrade cycle. I am somewhat dismayed by the amount of time I see "LabVIEW not responding" on the screen... So I am anxiously awaiting the upcoming "stability release". Not new features, but a reliable development environment is what gets me excited.

(Tho I will have to admit I love that in 2010 code pastes to where I put it, and the cluster icon is great!)

?!?!

US Fed gov't shutdown. But, there's yet another Continuing Resolution, so I have a paycheck for at least another week.

Otherwise I'd be traveling to Michigan looking for a LV job.

Darn! We are going to miss you, Cat.

I'll miss all of you, especially hanging with the Chick Posse (that means you, too, Norm )

Unacceptable.

I agree!

However, since I'm not really sure yet if I'm even going to have a paycheck starting Monday, this probably isn't a good time to bring it up with my boss....

No NIWeek for me this year. Sigh...

Yay, John!!!

(of course, you're one of those people I assumed already was a CLA!)

When you start getting real desperate... if you can, put 8.6 on the old computer, recompile, and see if your app still runs. If it does the problem might be the new computer.

So I "fixed" the problem today. I replaced the XYGraph I was using to display the data with a ... (wait for it) ... XYGraph.

Yup, this was one of those funny () situations with LabVIEW where if you delete non-working code, and rewrite it the exact same way, it works fine. In this case, I just right-clicked on the graph and literally replace it with the same thing. A couple key-strokes to make it the right size and set up the cursors and it works great.

I noticed a few days ago that even the 32-bit app on my 32-bit system took a loong time (20s) to do that ninth plot. It would make it thru it (unlike any other variation of apps) but it definitely had to think about it for awhile. This said to me it wasn't a 64-bit or probably even a memory problem. So, after a day and a half of trying everything I could think of, the actual fix took about 5 minutes. Sigh...

I still don't have a clue *why* it's hanging at that ninth plot, but at least it's not doing it anymore.

And here I thought it really was just me. It was the first time I had saved and tried to upload a vi snippet and I figured I was doing something wrong.

Do any of you have experience with the Request Deallocation function?

Lots of experience. For some reason I keep trying to use it, even tho it rarely does anything. As Ben says, the whole calling chain has to go away before it works.

Is there a hard limit on what LabVIEW 32-bit is capable of? Am I looking at a 3 GB or so ceiling?

You're using LV 2010, right? It should be already Large Address Aware, but if you're using 8.6 take a look here.

I suspect that what I'm really running into is out of continuous memory required for allocations as there is ample memory available on the system.

Yes, contiguous memory is the problem with large data sets, particularily when you're trying to plot them.

Before I pull in a large amount of data, I read the available system memory, divide it in half, and then decimate my data to fit in that space. Yes, it's a WAG that even that will be enough memory (not to mention really frustrating to have lots of memory out there and not be able to use it), but it's been working pretty well so far.

Your design is a bit weird to me.

The code almost looks deliberately wrong, which makes me wonder if it's a school assignment??? If so, while we're all glad to help people out here, we really shouldn't be doing your homework for you.

How big are they? What type are they? What are the problems are you having?

Both around 15kB. One png and one vi. "Error loading file" was all I got back. I tried both the old loader (and on the browser that can support it) the new loader.

Can't say, the article didn't give many details. What would have happened if the firefighters hadn't acted as they did? Could the fire have spread to other houses or burned down the neighborhood? Preventing several families from losing their homes due to a spreading fire is hero-worthy in my book. Exposing oneself to dangerous situations due to inadequate training (they were volunteers) or inept command is not.

Yeah, I looked for something more detailed but all reports had the same lack of specifics.

$2,000,000 mansion surrounded by lots and lots of grass.

So are you saying that hero-ness increases in proportion to the numbers of homes (just property, no lives) that were saved? (I'm trying to help you avoid the pain of practicing for the CLA )

I'm having problems uploading files to LAVA. Two different computers, two different browsers. Is it just me? (it generally is)

Where you talking about another way?

Is there another way to make this, perhaps more simple?

There are a whole bunch of comments I could make, but first of all, what is this project for?? Work? School??

How do I implement it to labview?

I think we've gotten to the point where you need to post some code of how you've tried to implement the suggestions Roderic and I have already made, and what's working and what's not working.

So what about this?

Eight firefighters injured, 2 seriously, fighting a house fire. All 5 people inside the house got out safely. My understanding is the firefighters were injured battling the blaze, not rescuing the people.

Is this heroism?

If my house were on fire, and all the people (which includes my cats, BTW) were safely out, I would rather the house burn down to the ground than firefighters get seriously injured trying to put the fire out. People's lives are more important than my property.

How can I write each waveform/array to a different column in excel?

wave1, wave2, wave3

w1pt1,w2pt1,w3pt1

w1pt2,w2pt2,w3pt2

w1pt3,w2pt3,w3pt3

w1pt4,w2pt4,w3pt4

etc...

You just have to place the write to excel fonction after your loop...

What Roderic says.

And if you use *.csv, you can use "Write to Text File" function in the File I/O Palette.

I didn't install 2010 and waited for SP1 but can't say that it seems slower or less stable than 2009 or 8.6,

Having gone straight from 8.6.1 to 2010SP1, all I can say is that I am now spending a LOT of time watching the cursor twirl endlessly and looking at "LabVIEW not responding" messages. And this is just while doing normal things, not any large data set memory intensive things.

except that the installation took almost forever, (like 12 hours and more for the developer suite installation and another evening/night for the device drivers and then another evening/night for the SP1 update). I account it largely to the three year old Windows installation that holds among other things all versions of LabVIEW since 5.1.

Just installing the professional development system and drivers took 3 hours. On a brand-spanking new computer.

If the requirement is not to specifically make a *.xls file, but rather just a file that Excel can read, the easiest way to do this is to make a Comma Separated Variable (*.csv) file from your data. Then you don't have to fool around with ActiveX or .Net or anything like that.

So, for example, your time file would end up looking something like

timeToThreshold1, timeToStop1, duration1

timeToThreshold2, timeToStop2, duration2

timeToThreshold3, timeToStop3, duration3

...

While I'm waiting on software and hardware to try out Shaun's and Mark's suggestions, I've been porting my 32-bit code to a 64-bit machine and rebuilding. While maintaining 2 different versions of my code is not necessarily a *good* solution to my problem, it is *a* solution, anyway.

So, I ran my 64-bit executable. I loaded up 8 plots, no problem. Clicked on the 9th and....

**Choke**

I repeated this yesterday a couple times and always got the same result. LabVIEW not responding. In disgust I left it running over night. When I came in this morning it was running fine! I loaded up a bunch of plots with no problem! Whisky Tango Foxtrot (as they say in the Navy) ?!?!

So after a few more tests, here are some numbers to quantify this problem.

1) Each plot added consistantly takes about 11MB of memory.

2) After plot8 my app is using approx 360MB memory

3) Going from plot8 to plot9 grabs 30-ish MB and that number fluctuates during the "LabVIEW Not Responding" time until it settle down to the usual 11MB

4) During this time the computer's 8 CPUs are averaging ~12% with one of them at ~65%

5) The "LabVIEW Not Responding" time is approximately ONE HOUR (!!!)

After that, I've gotten 250 plots up with a minor amount of thrashing (not surprising since my current machine only has 4GB memory).

Any clues about what's going on? My thought is that LV initially grabbed a bunch of memory, uses it all up at 360MB and then needs to grab more. But why in the world would that take an entire hour??

Cat

Programs that are 32 bit but in a 64 bit environment will be in the Program Files (x86) folder.

That makes sense. The install prompts are just a little misleading. Thanks!

As for the installation taking forever, this is quite normal...

And here I was fully prepared to not blame NI.

I'm attempting to install LabVIEW 2010 64-bit. Questions:

1) Installing LV takes way over an hour as does installing the device drivers. Is this normal? I'm thinking not, and am more than willing to blame my anti-virus software that I unfortunately can't turn off...

2) For the many installs I did (see sob story below) it was asking where I wanted LabVIEW to go and where I wanted other NI components to go. Sometimes the default was "C:\Program Files\...". Sometimes it was "C:\Program Files (x86)\..." Which one of these is "right"? Or does it even matter?

3) I searched in vain for a 64-bit device driver download on the NI site. If it's really there, can someone point me in the right direction? If not, is it okay to use the 32-bit driver disk that came in the mail?

Long, sad, sob story:

I was tearing my hair out yesterday trying to install LV2010. I need to recompile my 32 bit code with 64 bit LabVIEW and see if that helps with performance issues I've been having. I had downloaded and installed SP1 a few days ago and then gotten the disks in the mail. Being the anal-retentive type, I figured I should reinstall from the disks. So I uninstalled, then reinstalled.

So I run my newly installed LV and when the splash screen comes up it says it's running the 32-bit version. NI sent me 32-bit LabVIEW. Grrrrr. When you install the 64-bit version, it says that in the menubar. The 32-bit version is silent on the matter. So uninstall and reinstall the original downloaded 64-bit version. Another 3 hours shot...

But even tho I left it at the default "C:\Program Files\...", a bunch of NI stuff is still installed in "C:\Program Files (x86)\..." Which is what triggered this post. I would like all the NI stuff to be in one spot, but that may just be my anal-retentive nature again.

This may be too trivial of an answer for your application, but you can just right click on a cluster element, select Create-> Reference, and a reference to the cluster element appears on your BD. No casting necessary.