LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

System requirement for the LV and VISA run-time library

Dear
 
My application built from LV8.2.1 didn't run on the old-fashioned notebook, which was under XP and 256 RAM.
(The application was tested successfully in several times in other computer.)
In the only first running, there was no problem.
But after that, the application executed "twice" and one of two couldn't be removed even in Windows Task Manager.
(I had to switch off the computer for restarting PC)
 
However,  I am not sure if this problem is a kind of the library's bug but suspect the out-of-fashioned notebook.
What's the minimum system requirement for the LV run-time library and VISA runtime library of version 8.2.1?
Or any other check points?
 
Lee

 

메시지가 08-07-2007 02:03 AM에 labmaster에 의해 편집되었음

0 Kudos
Message 1 of 5
(3,488 Views)
The Release Notes specify the system requirements. From the 8.2 Release Notes (the 8.2.1 runtime engine are not likely to be different):

"When you deploy an application you build, the LabVIEW Run-Time requires a minimum of 64 MB of RAM and a screen resolution of
800×600 pixels for applications that require a screen, but National Instruments recommends 256 MB of RAM and a screen resolution of
1,024×768 pixels."

I don't have the VISA requirements handy, but the requirements are going to be less than for LabVIEW.

However, this does not take into account whatever you may need for your own application.

You said that you were able to get it running "twice", but one time you couldn't shut it down even from the Task Manager. This sound like the software was waiting on some sort of hardware. What is your software doing?
0 Kudos
Message 2 of 5
(3,461 Views)

What kind of error do you get the second time?  Is there an error message.  A common problem with visa is that after the first execution the visa resource is not closed, then on second run the vi is stuck waiting on a resource it can not get, if this error is not handled the program flow will not work properly.  As a fix I often proceed my visa opens with a visa close on the resource and an error clear.  Can you give some more details about the problem.  I have used visa runtime with 8.2 exes with no problems.

 

Paul 

Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
0 Kudos
Message 3 of 5
(3,462 Views)
Thank you, falkpl and smercurio_fc.
 
Of course, my application and the libraries have no problem in other computers.
There were no error messages but it seemed not to run normally.
My application had to show a status message prior to a VISA routine, but only a blank in the status control.
 
When I click the application one time, the application was not launched.
Then  the two same applcations were appeared in the second click.
 
One of two applications could be removed by the Taskmanager. (malfunction of the program exit button.)
But the remained one can't be exited by the Taskmanager or Exit Windows.
 
Maybe, I had better remove the XP and then try again.
 
Anyway, I can't understand  the reason why any NI Labview developer remained in silence for this kind of postings.

메시지가 08-07-2007 08:43 PM에 labmaster에 의해 편집되었음

0 Kudos
Message 4 of 5
(3,449 Views)
This doesn't sound like a problem with Windows XP, so reinstalling XP is a bit of a drastic measure here.

You said
When I click the application one time, the application was not launched.
Then  the two same applcations were appeared in the second click.
To me, this sounds like you're simply not waiting enough time for the application to start running before you try to launch it again, and thus you end up with two instances. I don't know what your application is doing, but you have to keep in mind that the runtime engine has to start first. If you have a relatively slow machine, or your hard disk is heavily fragmented, or your application is large, this may take some time. If your application is accessing hardware resources (and it sounds like it is), the second instance will be in conflict with the first, causing a system contention, and is likely the cause of the apparent non-responsiveness.
Message 5 of 5
(3,425 Views)