EJW

QUOTE (Minh Pham @ Nov 20 2008, 06:52 PM) Actually, i am replacing the third element with new data, same size. I keep the first two indexes and input a new third array to replace the original.

i have attached a picture of an inplace structure i used. does this method gain anything over not using it to do the same thing?

I like to use enums in my programming because of the text output they have when using a case structure as opposed to a menu rings numeric output. Is there a way to make a control or xcontrol that uses the menu ring for the control, but outputs an enum style value?? I know this could probably be accomplished by using the menu rings string property but i'd rather have a separate control i can implement.

QUOTE (guruthilak@yahoo.com @ Aug 6 2008, 06:54 AM) You can always select the assistant with the left mouse, go to the edit menu, and convert to task name constant. then repeat that process and convert to code or code plus example.

QUOTE (Ton @ Aug 1 2008, 10:06 AM) I found something interesting. The machine I wrote the code on uses daqmx 7.4.0f0, my test machine in the lab uses 8.0.1f0 - the problem shows on both machines. However, i checked the machine that is actually running the test, which uses 8.0.0f0, and it is not happening on it. That is very strange. :headbang:

QUOTE (Louis Manfredi @ Aug 1 2008, 10:14 AM) Yeah, that is what i am doing now, i know i have run into issues where one task reads DIO and another writes to DIO on the same device (different lines). Also, the other device reads a DIO and an AI, but i dont think that is usually a problem. Worst case, I'll string em all together with the errors and let them operate sequentially. In some cases i know i have had to actuall insert a stop task otherwise the next task doesnt work. I am hoping to complete this without all the extras! EDIT:: I converted the assistants to code only, put them outside the while loop and did the read/write in the loop and the memory leak went away. Now i just have to make sure everything is functioning on the machine it goes on. Hopefully there are no issues.

QUOTE (Ton @ Aug 1 2008, 10:06 AM) I thought of that , so i added a clear task on the task out of each express vi, which actually caused it to fail on the second iteration. I was actuall trying to minimize the amount of code i was rewriting in this program as there is a new version in 8.5 coming in about 2 months, and i didn't want to spend a lot of time on this one!

I am updating a labview 7.1 program. I removed all traditional nidaq code and replaced with daqmx code and the daq assistants. The program, when compiled (myprogram.exe), has a memory leak. The memory useage continues to grow until you get low on virtual memory. However, in the dev mode inside of labview, there does not appear to be a memory leak. The labview memory useage never changes. How would i go about finding what is causing this? there are about 4 daq assistants in a while loop waiting on a test to start. these DA's poll various digital and analog channels. Could these be the cause of the leak. If so, why only in compiled version and not the ide.

I have recently run into an interesting problem. I have a new 8105 controller, 1031 chassis, and two 6251 DAQ cards. My labview program on this machine starts up with windows (XPSP2). However, when the program initalizes, it gets a device not present error. If you stop and start the program again, or close it and reopen it, it works fine, the device is there. Similarly , if you take the program out of the startup folder and launch it manually after windows starts, it works fine. It appears to me that windows has not finished recognizing the hardware, or the drivers are not fully loaded by the time my program launches when it is in the startup folder, causing this error. Unfortunately, this is a gage in a production environment, so it HAS to start up with windows. The only solution i have found so far is to put a delay of several seconds into the beginnning of the program before configuring tasks. This seems to allow windows and nidaq to finish doing their thing so i dont get the error. Anyone else have this problem or know of a workaround other than a time delay??

QUOTE (crelf @ Jun 17 2008, 02:52 PM) Good point! So I called NI, and the response was NO it would not affect the NI warranty!!!! QUOTE (Neville D @ Jun 17 2008, 02:57 PM) You might also consider that the NI memory will definitely support the extended temperature spec (if you have that option) in harsh environments. Neville. You know, i have ordered stuff with the extended temp spec, and yet i am still unsure what it is that is different! Do you know? Also, alot of memory these days is designed around "gamers" which tend to have HOTTTT! systems. So one would expect the more recent memory is capable of withstanding the harsh environment. I have seen analysis enclosures (which contain the pxi system and other electronics) of mine reach 120º F internally without difficulty. All my enclosures have air exchangers, which dont work very well, but my newest one has an AC unit (1000BTU) to keep my precious NI equipment comfortable!

Has anyone upgraded memory in their PXI systems? Do you buy the way way overpriced NI memory or do you order something from a respectable company like Corsair , OCZ or Kingston. After all it is just laptop memory!

Has

Has anyone upgraded memory in their

QUOTE (crelf @ Jun 16 2008, 06:22 PM) Oddly enough, i hade that happen with the write to spreadsheet file. i lost all my polymorphic instances except one. NI had me recopy the original lvlib from the CD to my computer and replaced the broken one with that. All was good.

QUOTE (Michael_Aivaliotis @ Jun 17 2008, 01:02 AM) LOL, THAT'S THE PROBLEM!! Have you ever tried to find a needle in a billion piece haystack! However, through careful prudence and patience and several reinstalls, i did finally get it to work.