Anybody experience difference in Labview program execution time on Asian Windows O/S?

I have written a Labview Program that uses GPIB to control an Agilent Spectrum Analyzer and Power Meter. It communicates with and controls the D.U.T. via Telnet. It was debugged here in Massachusetts under Windows 2000. Here the test takes ~ 43 seconds. In Thailand on an equivalent computer running Windows 2000 (Thai) the same test takes ~ 66 seconds. Time is measured by capturing start time and stop time from the O/S. Any clues to account for the difference? The time differential is the same in the development environment and the distribution environment.

"RMK at Netopia" wrote in message
news:[email protected]..
> I have written a Labview Program that uses GPIB to control an Agilent
> Spectrum Analyzer and Power Meter. It communicates with and controls
> the D.U.T. via Telnet. It was debugged here in Massachusetts under
> Windows 2000. Here the test takes ~ 43 seconds. In Thailand on an
> equivalent computer running Windows 2000 (Thai) the same test takes ~
> 66 seconds. Time is measured by capturing start time and stop time
> from the O/S. Any clues to account for the difference? The time
> differential is the same in the development environment and the
> distribution environment.
Suggest you break the test down to its individual steps to see which part o
f
the test is changed. You may even find that it is the test equipment that
is taking longer.

Similar Messages

Program execution time

Hi all,
i have created a report which inlclude posting dates. if i enter the period of 1 year it takes abt 3 mins. to execute it, as i tried the same in table from where the data comes , the table is aslo taking almost same time but it will not do, so just plzz tel me that is there any tips or trick so that i can reduce this execution time..??
thanx..

>
Vinod Reddy Vemuru wrote:
> Hi Nilesh,
> First send us your select query with out seeing which its very dificult to draw the solution. There might be many reasons for performance issues. Suppose a select in CDHDR/CDPOS table u can't improve much by what ever care u take.
>
> A select on BSEG can be improved by getting data from index tables BSAD/BSID/BSAK/BSIK table.
> So first post ur query.
>
> Thanks,
> Vinod.
thanx..
this is query..
select budat belnr into (itab-budat,itab-belnr) from bkpf
where budat between budat-low and budat-high and bukrs in bukrs

LabVIEW program will not run on Windows 2000

I need to run parts of a LabVIEW program on a PC which does not contain all the hardware required to run the full version. This used to work on Windows 95/98 but on Windows 2000 I get error message 'Capabilty not supported. VI was stopped at node 0x1BC of subvi "Out Port.vi"'. This program is very large and full of references of this type, is there an easy way around this problem?

Hi,
I might be barking up the wrong tree here, but Windows 2000 is built on top of the architecture of Windows NT. Win NT/2000 treats direct memory access differently to Win95/98.
Have a look at the following link and see if that helps - unfortunately it involves re-writing (well, re-linking) the .vi's that are calling the out port.vi. The link is in reference to writing to the parallel port through direct memory access, but the .vi's are based on writing to any memory location.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/c80752c53094c296862565f3007ac765?OpenDocument
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000110A0000&ECategory=LabVIEW.LabVIEW+General
As you don't say wh
at version of LV you're using, the following link might also prove useful (if you're using LV 6.0.2+)
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000102F0000&ECategory=LabVIEW.LabVIEW+General
Hope that helps
S.
// it takes almost no time to rate an answer

How to run labview program in debugging mode in windows 95 version

Respected all,
I am facing probelm while running probe.vi.
I received this command "connection to acquisition board was not found" when i run labview program.
I am using labview 5.1, fieldpoint FP 1000, NI-DAQ 6.5, Field point explorer version 1.6, Measurement and Automation Explorer 1.0.1.
I would kindly request you please help me how to run my program probe.vi in debugging mode in windows 95 version, so that i can locate where error occurs.
Thanking You
Yours faithfully
M.Vijay

Respected Norbert,
Thank you very much to for your help.
Norbert : Possible reasons are e.g. wrong IDs for measurement devices. If the error is connect to the FieldPoint, it is possible that it isn't configured correctly.
I am using Field point explorer 1.6, The Field point instrument FP 1000 and RS-232 port is using. It is confirmed that the field point instrument is working properly by LED light indication test.
Norbert: It sound like you are using DAQ devices (like PCI MIO 6952E) in the application. Are you sure that you select the correct device ID for this?
I am asking you to know, If i using Labview and Fieldpoint instrument FP 1000 to monitor my parameter interms of All, Channel 0, Channel 1, Channel 2, Channel 3, Channel 4, Channel 5, Channel 6, Channel 7 for my measurement.
But now i need to solve the command connection to acquisition board was not found, The expert say this command is due to there was no AT-AO-10 Analog Output board was present in CPU.
I do not find AT-AO-10 Analog Output board in my CPU, Previously the instrument was worked perfectly by other person who assembled everthing to measure temperature.
The only aswer know send by previous person is if my task does not imply the use of a DAQ you probably have to locate where the DAQ driver is called and exclude it from the program. try to run the program in debugging mode so that you can locate where the error occurs.
I do not know how to proceed his instruction. So i would kindly request you to please help me to solve my probelm.
I also removed AT-AO-10 software from device manager >> Data Acquisition system >> AT-AO-10 just now.
I also find GPIB version 1.30, when i remove in add or remove program, it say that Error removing the GPIB.
I am eagerly waiting for your help.
Thanking You
Yours faithfully
M.vijay

Execution time increase

hai guys,
Im currently developing a code that run 24 hours 7 days a week. My problem is the execution time increases as days pass by. As im tracing down the execution time ,the 1st day i start the to run the program execution time is 0.04 second but after 3 day it increases to 4.5 seconds .
then i indually tracked down the subvi that causing problem and find out that the problem is on writing to ini file.
The subvi function is to REPLACE the data (20 data )in a file every 10 second*not accumulating data just replace the old data . I open file replace data and close file every itteration and as day pass the execution time for this subvi increases.
Can any one help me to get a solution for the problem as time is a very important factor in my programming. the execution time is limited for less that 10 second.
thanks
regards
kokula

As David said, post the code.
Is there any reason why your are loggin to an .ini file? Does that mean you are using the LabVIEW config file functions?
I don't know if deallocating memory would help, or is even possible, without seeing your code. You either have a problem with resources continuously being created, but not being closed out. Or you have an ever growing array. This takes more memory over time, and slows down the code because LabVIEW has to move memory around to account for the ever larger array.
I bet if you let your program run long enough, it would eventually crash due to running out of memory.
By the way 47MB to 350 MB of memory consumption means the same thing as RAM usage increasing.

I have some software problems of running matlab script node in the LabVIEW program.

Hi there,
I wrote a simple matlab code, like x= 1, y = x*2. Then I tried to put them into matlab script node in LabVIEW.
However, when I ran the program, I couldn't run and Labiew show some error.
Then I tried the method talked before on this forum. Please see the following link.
http://forums.ni.com/ni/board/message?board.id=MathScript&thread.id=571
I followed the instruction and open the "command prompt," type some commands then I could run the program, and simultaneously, the LabVIEW program open "Matlab command line window" and run my labview code. However, if I didn't use the command prompt, the "matlab command window" will not be opened by running the labview program. It would just show some error. And even if I turn on the matlab program in advance, I still couldn't run the labview program.
Is there any effecient way to deal with this problem without using "command prompt?" Because I try another PC with both matlab and labview installed on it, I "can" run my simple matlab script node on it, and it will open the matlab command line window automatically by running my code. Therefore, I thought there might be some software linking problems in the previous PC I used . Do you have any ideas?
Thanks in advacne.

This board is for Mathscript, but you seem to have a matlab problem. You should probably post in the LabVIEW forum instead.
What is your LabVIEW version? What is you matlab version?
LabVIEW Champion . Do more with less code and in less time .

What is the difference in execution time between a program written in C language and the same program made with LabView?

what is the difference in execution time between a program written in C language and the same program made with LabView?

Hi Pepe
You cannot say which is faster, the LV or the C programm. The only way to be sure is to program in both environments and to check than. Check this for some benchmark examples:
http://zone.ni.com/devzone/conceptd.nsf/webmain/DC9B6DD177D91D6286256C9400733D7F?OpenDocument&node=200059
Luca
Regards,
Luca

Execution time of same program makes big difference

Hello all,
The execution time of same program in PRD system and QAS system makes big difference.
The difference of data is not much(as system copy was run on a regular time schedule. And the system enviroments are exactly the same. However, while the program only cost 2-3 seconds in QAS, it cost 7-8 minutes in PRD.
It only happens when trying to join some tables together.
I've checked the execution plans of same search, they are different:
QAS:
SQL Statement
SELECT
T_00.RANL , T_00.XALLB , T_00.REPKE , T_00.REWHR , T_00.HKONT ,   T_00.ZTMNAIBRX , T_00.GSART ,
T_00.ZTMHOYMNX , T_00.ZTMSBKBNX ,   T_00.ZTMSHDAYZ , T_00.ZTMMBHZKP , T_01.BAL_SH_CUR ,
T_01.ZTMSIHONP ,   T_02.SECURITY_ID , T_02.SECURITY_ACCOUNT
FROM
ZTM0108 T_00, ZTM0135 T_01, TRACV_POSCONTEXT T_02
WHERE
T_00.MANDT = '350' AND   T_00.BUKRS = 'MC51' AND   T_00.ZTMMCSNGX = '200806' AND
T_02.SECURITY_ACCOUNT = '0001' AND   T_01.MANDT = '350' AND   T_01.BUKRS = T_00.BUKRS AND
T_01.ZTMMCSNGX = T_00.ZTMMCSNGX AND   T_01.PARTNER = T_00.REPKE AND   T_02.MANDT = '350' AND
T_02.SECURITY_ID = T_00.RANL
Execution Plan
SELECT STATEMENT ( Estimated Costs = 666 , Estimated #Rows = 72 )
---   12 HASH JOIN
( Estim. Costs = 666 , Estim. #Rows = 72 )
Estim. CPU-Costs = 37,505,220 Estim. IO-Costs = 663
Access Predicates
--   9 HASH JOIN
( Estim. Costs = 268 , Estim. #Rows = 51 )
Estim. CPU-Costs = 18,679,663 Estim. IO-Costs = 267
Access Predicates
--   6 NESTED LOOPS
( Estim. Costs = 25 , Estim. #Rows = 38 )
Estim. CPU-Costs = 264,164 Estim. IO-Costs = 25
--   4 NESTED LOOPS
( Estim. Costs = 25 , Estim. #Rows = 27 )
Estim. CPU-Costs = 258,494 Estim. IO-Costs = 25
--   2 TABLE ACCESS BY INDEX ROWID DIFT_POS_IDENT
( Estim. Costs = 25 , Estim. #Rows = 24 )
Estim. CPU-Costs = 253,454 Estim. IO-Costs = 25
Filter Predicates
1 INDEX RANGE SCAN DIFT_POS_IDENT~SA
( Estim. Costs = 1 , Estim. #Rows = 554 )
Search Columns: 1
Estim. CPU-Costs = 29,801 Estim. IO-Costs = 1
Access Predicates
3 INDEX RANGE SCAN TRACT_POSCONTEXTID
Search Columns: 2
Estim. CPU-Costs = 210 Estim. IO-Costs = 0
Access Predicates
5 INDEX UNIQUE SCAN TZPA~0
Search Columns: 2
Estim. CPU-Costs = 210 Estim. IO-Costs = 0
Access Predicates
---   8 TABLE ACCESS BY INDEX ROWID ZTM0108
( Estim. Costs = 242 , Estim. #Rows = 2,540 )
Estim. CPU-Costs = 10,811,361 Estim. IO-Costs = 241
7 INDEX RANGE SCAN ZTM0108~0
( Estim. Costs = 207 , Estim. #Rows = 2,540 )
Search Columns: 3
Estim. CPU-Costs = 9,790,330 Estim. IO-Costs = 207
Access Predicates Filter Predicates
      ---   11 TABLE ACCESS BY INDEX ROWID ZTM0135
( Estim. Costs = 397 , Estim. #Rows = 2,380 )
Estim. CPU-Costs = 11,235,469 Estim. IO-Costs = 396
10 INDEX RANGE SCAN ZTM0135~0
                   ( Estim. Costs = 323 , Estim. #Rows = 2,380 )
                   Search Columns: 3
                   Estim. CPU-Costs = 10,288,477 Estim. IO-Costs = 323
                   Access Predicates Filter Predicates
PRD:
Execution Plan
SELECT STATEMENT ( Estimated Costs = 209 , Estimated #Rows = 1 )
---   12 NESTED LOOPS
( Estim. Costs = 208 , Estim. #Rows = 1 )
Estim. CPU-Costs = 18.996.864 Estim. IO-Costs = 207
--   9 NESTED LOOPS
( Estim. Costs = 120 , Estim. #Rows = 1 )
Estim. CPU-Costs = 10.171.528 Estim. IO-Costs = 119
--   6 NESTED LOOPS
Estim. CPU-Costs = 27.634 Estim. IO-Costs = 0
--   4 NESTED LOOPS
Estim. CPU-Costs = 27.424 Estim. IO-Costs = 0
1 INDEX RANGE SCAN TZPA~0
Search Columns: 1
Estim. CPU-Costs = 5.584 Estim. IO-Costs = 0
Access Predicates
---   3 TABLE ACCESS BY INDEX ROWID DIFT_POS_IDENT
Estim. CPU-Costs = 210 Estim. IO-Costs = 0
Filter Predicates
2 INDEX RANGE SCAN DIFT_POS_IDENT~PT
Search Columns: 1
Estim. CPU-Costs = 210 Estim. IO-Costs = 0
Access Predicates
5 INDEX RANGE SCAN TRACT_POSCONTEXTID
Search Columns: 2
Estim. CPU-Costs = 210 Estim. IO-Costs = 0
Access Predicates
---   8 TABLE ACCESS BY INDEX ROWID ZTM0108
( Estim. Costs = 120 , Estim. #Rows = 1 )
Estim. CPU-Costs = 10.143.893 Estim. IO-Costs = 119
7 INDEX RANGE SCAN ZTM0108~0
( Estim. Costs = 119 , Estim. #Rows = 1 )
Search Columns: 4
Estim. CPU-Costs = 10.142.167 Estim. IO-Costs = 119
Access Predicates Filter Predicates
      ---   11 TABLE ACCESS BY INDEX ROWID ZTM0135
( Estim. Costs = 89 , Estim. #Rows = 1 )
Estim. CPU-Costs = 8.825.337 Estim. IO-Costs = 88
10 INDEX RANGE SCAN ZTM0135~0
                   ( Estim. Costs = 88 , Estim. #Rows = 1 )
                   Search Columns: 4
                   Estim. CPU-Costs = 8.823.742 Estim. IO-Costs = 88
                   Access Predicates Filter Predicates
Could anyone tell me the reason? I've found note 724545 but not sure.
And, how to read the execution plan?(1 first or 12 first?)
Best Regards,
Robin

Hello Michael.
Thank you.
However, the sql statement is same:
QAS:
SQL Statement
SELECT
T_00.RANL , T_00.XALLB , T_00.REPKE , T_00.REWHR , T_00.HKONT ,   T_00.ZTMNAIBRX , T_00.GSART ,
T_00.ZTMHOYMNX , T_00.ZTMSBKBNX ,   T_00.ZTMSHDAYZ , T_00.ZTMMBHZKP , T_01.BAL_SH_CUR ,
T_01.ZTMSIHONP ,   T_02.SECURITY_ID , T_02.SECURITY_ACCOUNT
FROM
ZTM0108 T_00, ZTM0135 T_01, TRACV_POSCONTEXT T_02
WHERE
T_00.MANDT = '350' AND   T_00.BUKRS = 'MC51' AND   T_00.ZTMMCSNGX = '200806' AND
T_02.SECURITY_ACCOUNT = '0001' AND   T_01.MANDT = '350' AND   T_01.BUKRS = T_00.BUKRS AND
T_01.ZTMMCSNGX = T_00.ZTMMCSNGX AND   T_01.PARTNER = T_00.REPKE AND   T_02.MANDT = '350' AND
T_02.SECURITY_ID = T_00.RANL
Execution Plan
SELECT STATEMENT ( Estimated Costs = 666 , Estimated #Rows = 72 )
---   12 HASH JOIN
( Estim. Costs = 666 , Estim. #Rows = 72 )
Estim. CPU-Costs = 37,505,220 Estim. IO-Costs = 663
Access Predicates
--   9 HASH JOIN
( Estim. Costs = 268 , Estim. #Rows = 51 )
Estim. CPU-Costs = 18,679,663 Estim. IO-Costs = 267
Access Predicates
--   6 NESTED LOOPS
( Estim. Costs = 25 , Estim. #Rows = 38 )
Estim. CPU-Costs = 264,164 Estim. IO-Costs = 25
--   4 NESTED LOOPS
( Estim. Costs = 25 , Estim. #Rows = 27 )
Estim. CPU-Costs = 258,494 Estim. IO-Costs = 25
--   2 TABLE ACCESS BY INDEX ROWID DIFT_POS_IDENT
( Estim. Costs = 25 , Estim. #Rows = 24 )
Estim. CPU-Costs = 253,454 Estim. IO-Costs = 25
Filter Predicates
1 INDEX RANGE SCAN DIFT_POS_IDENT~SA
( Estim. Costs = 1 , Estim. #Rows = 554 )
Search Columns: 1
Estim. CPU-Costs = 29,801 Estim. IO-Costs = 1
Access Predicates
3 INDEX RANGE SCAN TRACT_POSCONTEXTID
Search Columns: 2
Estim. CPU-Costs = 210 Estim. IO-Costs = 0
Access Predicates
5 INDEX UNIQUE SCAN TZPA~0
Search Columns: 2
Estim. CPU-Costs = 210 Estim. IO-Costs = 0
Access Predicates
---   8 TABLE ACCESS BY INDEX ROWID ZTM0108
( Estim. Costs = 242 , Estim. #Rows = 2,540 )
Estim. CPU-Costs = 10,811,361 Estim. IO-Costs = 241
7 INDEX RANGE SCAN ZTM0108~0
( Estim. Costs = 207 , Estim. #Rows = 2,540 )
Search Columns: 3
Estim. CPU-Costs = 9,790,330 Estim. IO-Costs = 207
Access Predicates Filter Predicates
      ---   11 TABLE ACCESS BY INDEX ROWID ZTM0135
( Estim. Costs = 397 , Estim. #Rows = 2,380 )
Estim. CPU-Costs = 11,235,469 Estim. IO-Costs = 396
10 INDEX RANGE SCAN ZTM0135~0
                   ( Estim. Costs = 323 , Estim. #Rows = 2,380 )
                   Search Columns: 3
                   Estim. CPU-Costs = 10,288,477 Estim. IO-Costs = 323
                   Access Predicates Filter Predicates
PRD:
SQL Statement
SELECT
T_00.RANL , T_00.XALLB , T_00.REPKE , T_00.REWHR , T_00.HKONT ,   T_00.ZTMNAIBRX , T_00.GSART ,
T_00.ZTMHOYMNX , T_00.ZTMSBKBNX ,   T_00.ZTMSHDAYZ , T_00.ZTMMBHZKP , T_01.BAL_SH_CUR ,
T_01.ZTMSIHONP ,   T_02.SECURITY_ID , T_02.SECURITY_ACCOUNT
FROM
ZTM0108 T_00, ZTM0135 T_01, TRACV_POSCONTEXT T_02
WHERE
T_00.MANDT = '500' AND   T_00.BUKRS = 'MC51' AND   T_00.ZTMMCSNGX = '200806' AND
T_02.SECURITY_ACCOUNT = '0001' AND   T_01.MANDT = '500' AND   T_01.BUKRS = T_00.BUKRS AND
T_01.ZTMMCSNGX = T_00.ZTMMCSNGX AND   T_01.PARTNER = T_00.REPKE AND   T_02.MANDT = '500' AND
T_02.SECURITY_ID = T_00.RANL
Execution Plan
SELECT STATEMENT ( Estimated Costs = 209 , Estimated #Rows = 1 )
---   12 NESTED LOOPS
      |    ( Estim. Costs = 208 , Estim. #Rows = 1 )
      |    Estim. CPU-Costs = 18.996.864 Estim. IO-Costs = 207
      |--   9 NESTED LOOPS
      |   |   ( Estim. Costs = 120 , Estim. #Rows = 1 )
      |   |   Estim. CPU-Costs = 10.171.528 Estim. IO-Costs = 119
      |   |--   6 NESTED LOOPS
      |   |   |   Estim. CPU-Costs = 27.634 Estim. IO-Costs = 0
      |   |   |--   4 NESTED LOOPS
      |   |   |   |   Estim. CPU-Costs = 27.424 Estim. IO-Costs = 0
      |   |   |   |-----1 INDEX RANGE SCAN TZPA~0
      |   |   |   |       Search Columns: 1
      |   |   |   |       Estim. CPU-Costs = 5.584 Estim. IO-Costs = 0
      |   |   |   |       Access Predicates
      |   |   |   ---   3 TABLE ACCESS BY INDEX ROWID DIFT_POS_IDENT
      |   |   |       |   Estim. CPU-Costs = 210 Estim. IO-Costs = 0
      |   |   |       |   Filter Predicates
      |   |   |       -
2 INDEX RANGE SCAN DIFT_POS_IDENT~PT
      |   |   |               Search Columns: 1
      |   |   |               Estim. CPU-Costs = 210 Estim. IO-Costs = 0
      |   |   |               Access Predicates
      |   |   -
5 INDEX RANGE SCAN TRACT_POSCONTEXTID
      |   |           Search Columns: 2
      |   |           Estim. CPU-Costs = 210 Estim. IO-Costs = 0
      |   |           Access Predicates
      |   ---   8 TABLE ACCESS BY INDEX ROWID ZTM0108
      |       |   ( Estim. Costs = 120 , Estim. #Rows = 1 )
      |       |   Estim. CPU-Costs = 10.143.893 Estim. IO-Costs = 119
      |       -
7 INDEX RANGE SCAN ZTM0108~0
      |               ( Estim. Costs = 119 , Estim. #Rows = 1 )
      |               Search Columns: 4
      |               Estim. CPU-Costs = 10.142.167 Estim. IO-Costs = 119
      |               Access Predicates Filter Predicates
      ---   11 TABLE ACCESS BY INDEX ROWID ZTM0135
          |    ( Estim. Costs = 89 , Estim. #Rows = 1 )
          |    Estim. CPU-Costs = 8.825.337 Estim. IO-Costs = 88
10 INDEX RANGE SCAN ZTM0135~0
                   ( Estim. Costs = 88 , Estim. #Rows = 1 )
                   Search Columns: 4
                   Estim. CPU-Costs = 8.823.742 Estim. IO-Costs = 88
                   Access Predicates Filter Predicates
Only difference is the client.
I see that QAS use index SA on table DIFT_POS_IDENT first, while PRD deal with table TZPA first...Is it the reason?
Best Regards,
Robin

Labview Program will hang between 33% and 50% of the time.

I have a problem with a Labview program I made. I have two programs that do the same thing. One is in flat sequence form and the other is in state machine form.
As explained in the link below, I would like to make use of a microcontroller to make wiring connections for automating a measurement process. A separate current source and volt meter will be used.
https://forums.ni.com/t5/LabVIEW/Sequence-a-good-idea/td-p/2601333
I have since made some simple test programs which I have attached. The problem is when executing, the labview program will hang, but not every time the program is execute.
For example: Hall 1.2.vi will work properly twice with the third time it is executed it will hang. If you abort and try again, it will again run twice with no problems with the third hanging. This one is in flat sequence format (was in a flat sequence, but merged the windows because I thought that was the cause). From what I can tell, the program will hang when calling Keithley 6517 Single Read.vi. Both connected Keithley devices are connected to the computer via GPIB at 16 and 27. The way I verified if it was this vi causing it or contributing to it was that I removed it and the program never hung. I find it very strange that it will hang exactly on the third attempt every time.
Hall 1.3 simple.vi will work the first time and hang the second time. So it works 50% of the time. This one is in State Machine format. This one will hang at the case titled "Measure 1" which contains the Keithley 6517 Single Read.vi.
I've used the highlight execution button and watched the program run. Oddly, it doesn't hang when using this button. So I tried adding delays/wait in different places to no avail.
What could be causing this? As a side note, I say the program hangs for two reason. The main one is the program doesn't finish running so the run arrow is still black. The second thing is that if you notice at the end of the labview program, I have a block there that turns the current source off which doesn't happen when it hangs. I have to manually turn it off and then hit the abort program button to stop labview.
Solved!
Go to Solution.
Attachments:
Hall 1.2.vi ‏42 KB
Hall 1.3 simple.vi ‏81 KB

altenbach wrote:
SaintsFan wrote:
Also, I've tried placing wait/delays at various places with no improvement of the problem. My next thought is to just remove all the vi calls and have everything in one program.
How did you place the waits?
Why would placing everything in one program fix the problem. That makes no sense! What is your reasoning?
In the case of hall1.3, I placed a wait in the Measurement cases and CS On cases and there was no affect. In the hall 1.2 when the blocks were broken up similar to the state machine cases where each sequence window was identical to the cases, I placed a wait or delay in each window with no effect on the hanging.
My reasoning for placing everything in one program is the same as my reasoning for figuring delays would help, since the time of execution would be altered. If the execution time is faster and if the timing is the problem then I figured that the problem would happen more frequently or even every time.
Somehow I get the feeling this is not the case. The reason being the interval in which it succeeds or hangs is constant. I believe somewhere, a value is getting set. The 6517 Read vi runs fine if I run this vi by itself no matter how many or how fast I run it. Also, the same goes for both 1.2 and 1.3 if I remove the 6517 read vi they run fine no matter how fast or how many times I run them.
Somehow after the current source is set to operate and triggers labview will hang on a set interval when calling 6517 read vi.
Separately they work, together there is a problem. I tried placing a delay between these two by connecting the error out of the trigger vi to the error in of the delay block and the error out of the delay block to the error in terminal of the 6517 config block. I've also tried delays between other blocks connected the same way. From what I understand, a called vi can't execute until all inputs are present. Is this the correct way to wire the delays?

Execution time optimizing labview code

Hi,
I would like to optimize my labview program. Is there a way I can plot
the execution time of my program as a function of some parameter I am
changing in my program. I was thinking of placing the entire program in
a while loop and then changing the parameter during each loop iteration
and then outputting the time that the program takes to execute as a
function of the parameter. The problem is how would I obtain the
execution time.
Thank you,
-Tim

Here a re a few more tips:
Running on a typical multipurpose OS will will make things a bit unpredictable because you never know what else is running so you should always repeat each run many times (then take the fastest, not the average, of all corresponding times).
Make sure that each run takes a few hundred milliseconds to get accurate values.
For timing purposes, it might be worth to temporarily raise the execution priority. The results will be much more reproducible (at the expense of useablility).
LabVIEW Champion . Do more with less code and in less time .

Run-time error "5010": Labview: VI execution ...

I get Run-time error "5010": Labview: VI execution terminated by server. This error occurs sporatically. I am running Visual Basic 5.0 application that communicates to Labview 6.1 VIs. It is using NI-Imaq to do vision analysis of parts. I just need to know what to look for that may be causing this error. I am also running it on a PXI system with 64 MB of memory.

Hello,
I recommend you to do direct function calls to NI-IMAQ and NI Vision function libraries from Visual Basic as this will be a lot more efficient and improve rubustness of your application. During the installation of both software, you have the option to include support files for Visal Basic. Once these components are installed you should see the shipping examples in the following directories (if installed in the default path):
(NI-IMAQ) C:\Program Files\National Instruments\NI-IMAQ\Sample\VB
(NI Vision) C:\Program Files\National Instruments\MeasurementStudio\VB\Samples\IMAQ
There are additional examples that can be found in the Code Library (see the link on the left sidebar).
Let me know if you have further questions regarding this issue.
Regards,
Yusuf C.
Applications Engineering
National Instruments

I am trying to translate the labview program to a real time labview programming....i wan to know what te the main isse that i need to focus on

currently i am doing a lift monitoring system which made use of labview. Due to time constraint, i have decided to use the real time labview program. However i have no prior experience on the real time programmng, can i be enlighten on the main issue and what are the thing i ned to look out for. is thre any documentation that i can use?

Derek,
Programming for LabVIEW Real-Time is very similar to programming for LabVIEW for Windows. Many VIs do not need to be changed in order to run in LabVIEW Real-Time RT Engines. However, here are some issues to consider:
1) Drivers
2) File I/O
3) Dialog Boxes
4) Shared resources
1) Drivers. If you application was written in LabVIEW for Windows, and then ported to run on an RT Engine on RT Series Hardware, you need to be sure that the drivers you are using are supported on your platform. See KB 28G97MZ8: http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/aad11f924e5b5fd086256a310053a094?OpenDocument
2) File I/O: If you are running your programs on an RT Series DAQ Device, it has no storage device, so file I/O operations will crash. See KB 26FBO0KN:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/3c35f5e85476579d862569f50067462e?OpenDocument
File I/O on RT PXI Controllers is supported in 8.3 filename format (no spaces in the filename allowed).
3) When your application is deployed, (Operate>Download Application, Operate>Run, then File>Exit without closing RT Engine VIs), you VIs continue to run. However, the RT Engine runs headless with no keyboard, monitor (limited information displayed), or mouse, so any user interaction previously required by your VIs, such as Dialog boxes, will hang or crash your program. For user interaction with a deployed application, communicate to the Host PC using shared memory, VI Server, TCP/IP, DataSocket, or UDP. See ~\labview\examples\rt\rt communication.llb for examples.
4) Even though your programs now run in a real-time operating system, you need to follow good real-time programming techniques. These include: using multithreading with critical tasks set to time critical priority. One time critical VI with no parallel loops. Avoid accessing or using shared resources in time crital VI (shared resources cause jitter). Shared resources include the memory manager (preallocate arrays used in time critical loops), global variables for interthread communcation (use RT Queues). For more information, visit the LabVIEW Real-Time Resource Library in the Developer Zone: http://zone.ni.com/devzone/devzone.nsf/webproducts/c25f8c664230613a862567df006abb06?opendocument

Execution time difference between SELECT & UPDATE statement in JDBC Sender.

Hi Experts,
In my scenario, I have used the JDBC Sender Adapter with the SELECT and UPDATE statement.
Now the problem is in between the execution of Select and update statement, few more entries are coming in the same DB Table.
So result of this is updation take place for those entries which are not even picked up by the select statement.
Can we avoid this execution time difference between the SELECT & UPDATE statemet on JDBC Sender side???
Thanks & Regards
Jagesh

Hi
Use serializable option in additional parameters, now all new entries would also be updated.

How to extend the execution time of an ABAP Program using the Process chain

Hello Sapians,
Our Environment has got 600seconds = 10 mintues as the execution time.
My ABAP Program is taking more than this 600 seconds, to show the result, I found this when I tried to execute in debug mode, it shows the result.
If I execute in background also it shows the results succesfully.
Only issue is when I execute this report in foreground it has been taking ages and goes on Time OUT Error.
It has been decided that we can extend the execution time only for this report, and it will reset the time back to 10mintues once the report has been executed successfully or failed in between for any other reasons.
And we can achieve this by using the process chains.
Can any body help me please in this regard
Thanks,

Hi,,,,,,,,,,
Besides Process Chain There is another way out for this........
Resetting time counter of dialog process so that time-out does not
happen. Use this fm within your program at appropriate locations to
reset time counter.
"CALL FUNCTION 'TH_REDISPATCH'."
Thanks
Saurabh

Max execution time per pixel causing rendering differences between GPUs

Is there a maximum execution time different graphics cards
will process each pixel as part of the shader? When running the
Raytracing script (
http://www.adobe.com/cfusion/exchange/index.cfm?event=extensionDetail&loc=en_us&extid=1634 018
) on my Macbook Pro (256MB ATI Radeon X1600) then many pixels come
out grey or black as the loop per pixel that is tracing the ray
takes longer than some built in execution limit.
I first noticed this with a filter I've been working on which
looks fine on my alu iMac (512MB Nvidia GeForce 8800 GS) but
rubbish on the Macbook Pro or older iMacs.
Are there ways around this limit like splitting long for or
while loops into smaller chunks, or is it just a hardwired max
execution time per pixel?

I don't think you can time out on processing an individual
pixel, but I could be wrong. You could try reducing the number of
reflections in the filter and seeing if that fixes the problem. It
could be a math precision difference between the cards.
Shaders can (and will) time out, but individual pixels
shouldn't. It could also be a driver issue with the structure of
the filter. I have a x1600 mac book pro here and I'll try it out if
I get a chance.

Anybody experience difference in Labview program execution time on Asian Windows O/S?

Similar Messages

Maybe you are looking for