Timer( ) resolution in CVI 2009 SP1

In the CVI 2009 SP1 Contents Help for Timer() function I find
The resolution is normally 1 microsecond. However, if you set the useDefaultTimer configuration option to True, the resolution is 55 milliseconds.
But if you click on the useDefaultTimer hyperlink, a new page is opened, where you can read that the resolution is 1 millisecond if you set useDefaultTimer to False.
Which is the right resolution?
I wrote my application considering 1 microsecond, but I found strange problems, and I think it is 1 ms.
Vix
In claris non fit interpretatio
Using LV 2013 SP1 on Win 7 64bit
Using LV 8.2.1 on WinXP SP3
Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

Hi vix,
Thanks for bringing those documentation problems to our attention.
1. There does seem to be a problem with a lot of the function prototypes in the .chm help in the CVI 2009 SP1 and 2010 versions, where an extra asterisk seems to have been added to a number of output parameters. We'll fix this and post a corrected version of the affected .chm files as soon as possible. In all these cases, the parameter data type as it appears in the Parameters section of the help topic is correct, as is the prototype in the corresponding function panel.
2. Concerning the timer resolution issues, the async timer resolution is in fact 1 millisecond, as confirmed by the GetAsyncTimerResolution function. But note that asynchronous timers are a library in and of themselves, and are not covered by what is discussed in the documentation of the Timer() function or the useDefaultTimer option.
The resolution of the Timer() function should be 1 microsecond, as of CVI 9.0 and later. The function documentation is correct. When that change was made, however, the documentation of the useDefaultTimer option was incorrectly not updated. It should say that "the performance counter timer provides a resolution of 1 microsecond".
You mentioned that you didn't think that the resolution of the Timer() function was 1 microsecond. If you run the following code, what do you see?
int     i;
double  time[10];
for (i = 0; i < 10; i++)
    time[i] = Timer();
for (i = 0; i < 10; i++)
    DebugPrintf ("timer = %f\n", time[i]);

Similar Messages

  • LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows - Supported Features

    Hi,
    Can some one please point out what features are supported by the LV RTE (Minimum ) [LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows]
    1) Is there a limit on the size of the exe which can be run on it?
    2) Will this support additional modules like DAQ etc.,? Or do we have to chose the regular installer ( 170 Mb ) for that purpose?
    3) If a list of what it does or does not support is available, it would be extremely helpful.
    Thanks In advance.
    Regards,
    Vijay

    Anand, 
    I did go through both the links that you had sent earlier before posting on the forum. For eaxample refer the following link where it says,
    http://joule.ni.com/nidu/cds/view/p/lang/en/id/1599
    It does not contain the full run-time engine, but will allow some executables to run.
    1) What do they mean by 'some' executables. Is there a list of yay's and no's available?
    2) Can someone from NI reply to this and shed more knowledge?
    Regards,
    Vijay 

  • Announcement: LabWindows/CVI 2010 SP1 Run-Time Engine Updated

    A new version of the LabWindows/CVI 2010 SP1 Run-Time Engine (10.0.1.434) is now available for download. The new version includes Security Update 5Q5FJ4QW which resolves security vulnerabilities in components installed with LabWindows/CVI 2010 SP1 and earlier and LabVIEW 2011 and earlier. Further details can be found at KnowledgeBase Article 5Q5FJ4QW: How Does National Instruments Security Update 5Q5FJ4QW Affect Me? Installing the security update will have the same effect as installing the new version of the Run-Time Engine.
    The update can be downloaded from the Drivers and Updates page. The LabWindows/CVIRun-Time Engine is a free download.
    National Instruments
    Product Support Engineer

    The correct link should be this one
    Proud to use LW/CVI from 3.1 on.
    My contributions to the Developer Zone Community
    If I have helped you, why not giving me a kudos?

  • LabVIEW Run-time 2009 SP1

    When I try to install LabVIEW Run-time Engine 2009 SP1 on a Windows 2000 machine I get an error message that states "Windows XP SP2 or greater required" 
    The compatability chart http://www.ni.com/labview/os-support/f/ states that LV 2009 is supported on Windows 2000. What gives?

    Do you have administrator privileges?  Also, do you have any security programs installed on your computer that could hinder the installation?
    Applications Engineer
    National Instruments

  • Is Labview Run-Time engine 2009 SP1 compatible with Windows 8

    I potentially need to install a Labview executable and Run-time engine 2009 on a Windows 8 OS.  From looking at the run-time engine support, it only looks like it only shows windows 7 down to XP.  Does anyone have any experience using Runtime 2009 on Windows 8?

    Hi Awhite144,
    The first version of LabVIEW to officially support Windows 8 is LabVIEW 2012 SP1. That being said, I would expect LabVIEW 2009 to work fine on Windows 8, and if you run into any trouble, feel free to post it here. LabVIEW 2012 SP1 installs a number of older LabVIEW run-time engines (including LabVIEW 2009), so it will install on Windows 8.
    I have not personally used LabVIEW 2009 on Windows 8, maybe if someone else has experience with it they can weigh in, but I expect it to work.
    As an important consideration, I assume you are talking about the full version of Windows 8, not Windows 8 RT. 
    Regards,
    Jeff Peacock 
    Product Support Engineer | LabVIEW R&D | National Instruments 

  • LabWindows/CVI 2009 Run-Time Engine update

    I wanted to let everyone know that NI has released an udpated CVI 2009 Run-Time Engine. Information on what bug(s) this update fixes can be found here. If you are currently not using the CVI 2009 Run-Time Engine, you do not need to install this update.
    This is an updated installation of the CVI Run-Time Engine, not a patch. If you download and install this update it will upgrade whichever version of the CVI Run-Time Engine you currently have to version 9.1.0.428 (CVI 2009 released with version 9.1.0.427). One way to find out which version of the CVI Run-Time Engine you have installed is to view the version number of c:\windows\system32\cvirte.dll. If you install version 9.1.0.428, any installer distributions that you create from any version of the CVI ADE will include version 9.1.0.428.
    If you have not yet installed LabWindows/CVI 2009, it's recommended that you install this update, either before or after you install CVI 2009.
    Luis

    To be clear, the original problem that you reported ("Attempt to free pointer to memory not allocated by malloc() or calloc()") might very have been the problem that this patch fixed, which was in fact new to 2009. But that problem only happens if there were actual plots in the graph.
    However, after looking at the "dynamic memory is corrupt" isse some more, it turns out that it is actually expected behavior, believe it or not. This is a limitation of easytab controls, caused by how they use callback chaining in their implementation. Whenever a panel or a control has its callback chained, you cannot change the callback, or make a copy of it after the chaining takes place. This is described in the EasyTab_ConvertFromCanvas function help ("...For the same reasons, do not call DuplicatePanel or DuplicateCtrl on any of these panels or controls after the Easy Tab control has been created.").
    As you probably have read elsewhere, easytab controls are quite obsolete. They were a stopgap "solution" to the problem of there not being a native tab control in the CVI user interface library. Native tab controls were finally added in CVI 8.0, and so we recommend that, if possible, users update their code to use these instead.
    Luis

  • CVI 2010 SP1 Crash

    Hallo,
    ich habe ein Update von CVI 2009 auf CVI 2010 durchgeführt und habe jetzt ein Problem.
    Eine meiner Applikationen lässt sich nicht mehr im Debugmodus starten,
    Noch vor dem Eintritt in die main()-Routine stürtzt die Applikation ab (siehe Screenshot im Anhang).
    Im Releasemodus läuft alles normal.
    Danke für Ihre Hilfe im vorraus.
    MFG,
    Christoph Pierednik.
    Solved!
    Go to Solution.

    In the past I had the same problem and thanks to NI support I solved it.
    As explained here I had to remove some of the listed import library I had previously included.
    As a matter of fact in the document I linked there is
    The base version of LabWindows/CVI includes these import libraries, and LabWindows/CVI automatically loads these libraries when it starts up and searches them to resolve references at link time. Thus, you do not have to include these libraries in your project.
    Vix
    In claris non fit interpretatio
    Using LV 2013 SP1 on Win 7 64bit
    Using LV 8.2.1 on WinXP SP3
    Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
    Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

  • Labview 2009 SP1 Installer build help needed

    Hello,
    First time posting here.  I have a rather large project that I recently converted from Labview 7.0 to 9.0.  I am able to build an executable and it starts up Ok but I don't know for sure if it works.  Since I couldn't build an installer, I copied the folder containing the .exe onto the targeted machine and installed Labview Run-time Engine 2009 SP1.  The executable then complains that it needs the full development version to work.  I am not too worry about this part at the moment, but if you have any pointers, please go ahead and post them.
    Ok, I have gone through a lot of posts on building and installer but it seems the one post that has something similar to what I experienced didn't get an answer.  Here's the Build Errors from the pop-up dialog:
    CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_BuildDevPart.vi >> NI_MDF.lvlib:MDFBuildDevPart_SetOtherProperties.vi
    Loading product deployment information
    Loading product deployment information
    Loading product deployment information
    Loading product deployment information
    Adding files to installer
    *** Error: An internal tool or library returned an error. (Error code -21)
    *** End Error Report
    *** Error: Windows SDK function returned an error. (Error code -12)
    *** End Error Report
    The build log file has slightly more info:
        [LOG ON]  Mon May 31 20:55:07 2010
    <<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
    <<<MDFConfig_SetDistributionLanguage>>> Language id: 9
    <<<MDFConfig_SetBuildDir>>> Build directory: C:\HardwareTest\XXX\Release\Installers\Lab Test Suite 4.2.9 Installer - XXX
    <<<MDFConfig_SetBuildMode>>> Build mode: 1
        [NMDK BEGIN]  Mon May 31 20:55:07 2010
         Building developer part
    > Adding files to installer
    <<<MDFBuildDevPart_SetFileNames>>>
    <<<MDFBuildDevPart_SetDefaultInstallDir>>>
    <<<MDFBuildDevPart_SetUpgradeInfo>>>
    <<<MDFBuildDevPart_SetOtherProperties>>>

    > **************
    > *** Error: An internal tool or library returned an error. (Error code -21)
    Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
    nmdkSetInformationalProperties returned error code 26024
    > *** End Error Report
    > **************

    Adding product dependencies to developer part

    > **************
    > *** Error: Windows SDK function returned an error. (Error code -12)
    Closing dist kit
    ***** About to begin MAXImportConfig:oMAXPartModifications...
    No MAX import files specified - nothing to do - returning.
    Error in MDF API function: _MDFBuildDevPart_Close
    Error in MDF::BuildDeveloperPart::Close.
    ERROR: Caught MSI Exception:
    <Unable to format error record.>
    MSI error code: 6
    > *** End Error Report
    > **************

        [LOG OFF]  Mon May 31 20:55:07 2010
        [MDF END]  Mon May 31 20:55:07 2010
         Closing MDF.
    I realize that I should post my project file but I can't do that until tomorrow.  From those 2 errors, can you tell me what the installer builder is looking for?  I have gone through all my dependencies and they look Ok at the moment.
    Thanks for you time.

    Hi Celeb,
    I had to help out on another project and finally only getting back to looking at this issue yesterday.  As you suggested, I went ahead and created a new project and created new build specifications (exe and installer).  I was able to properly build both items but won't be able to check out the executable til later this week.
    I noticed one thing about the project that Labview produced after converting the old *.bld file to a project file.  With the converted project, Labview adds unexpected installer destination folders into WindowsFolder in the Installer/Source Files/Destination View.  I thought I deleted them before but they seem to make it back (kinda hazy about this at this point).  My actual installer folder should only go into the WindowsVolume folder.  Anyway, on the new build spec, since I don't manually add the installer folder into the WindowsFolder, nothing get populated there and the installer is able to build properly.  This might have been the cause of my inability to build an installer with the converted project/build specs.
    I hope NI could add in more details into the build error messages.  As it is, it's really difficult to know why a build failed because there's no details in those messages.
    Thanks again,
    T.

  • Labview 2009 SP1 - Create exe option does not appear

    Hello everyone,
    I'm using Labview 2009 SP1 and I want to create a simple exe file (to run in the same computer that has labview or in any other  computer with the appropiate labview run time engine).
    I create a project with project explorer with the appropiate VI, everything OK for the moment, but when I right click on the menu "Build Specifications" of the project explorer I only have the options New and Help. If I click on New I only have "Source Distribution" and "Web Service (RESTful)" I would like to see the option Application and be able to create the EXE file.
    Anyone knows how can i create simple EXE files or make the option "Application" to be visible?
    Thanks for advance!
    Much thanks for your time and dedication!

    I guess you did not install the LabVIEW Application builder when you installed LabVIEW. When you do, it will allow you to create the exe and installer (You must be having a valid licence also).
    The best solution is the one you find it by yourself

  • Application builder for Lab View 8.6.1 , 2009 SP1 and 2010 SP1

    All 3 Versions seem to have huge flaws. With 8.6.1 When trying to build and application I get a duplicate name error and the application won't work. With 2009 SP1 I get Error 1003 broken VI when I have no broken VI's. Again Application won't work! With 2010 SP1 After the application is built for some reason lab view can no longer find the Excel sub VI's no matter how I place them in the build. And again application doesn't work. With all 3 versions the Vi's and over all programs work perfectly in the development environment. The application builder seems extremely flawed.
    I would currently like assistance with 2009 SP1 problem the Error 1003 broken VI. I have reinstalled and rebooted my machine several times , tried including as much as possible in the build and still get the error about a broken VI. That works perfectly in the development environment. Please HELP?
    Thank You
    Attachments:
    Broken VI.gif ‏8 KB

    Scott,
    Good afternoon, I'm sorry to hear you are having problems working with the application builder, hopefully I can help you get to the root of this problem.
    What steps have you taken to try and resolve the error? This error can be caused by a variety of things. The link below details 8 potential solutions that may help resolve your error.
    http://digital.ni.com/public.nsf/allkb/705C2ECA081F3C7986256C0F00559B02?OpenDocument
    I would recommend starting with these steps. Let me know if any of these solutions work for you.
    -Nick-
    Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

  • 2009 sp1 slow build

    Trying to build my application after I just upgraded to sp1 on LabVIEw 2009.
    It seems to take a long time, while using a lot of cpu power.
    Progress is very slow. Hard drive is not being used intensly.
    Running the same on the 2009 f2 version. Building from the same sources.
    Very slow as well.
    I'm new to the performance of the build feature in 2009. Coming from version 7.1.1
    And I'm very surprised on the difference. Why does the build take sooooo looooonnnnggg on the 2009 version(s)??
    We build smaller apps before on 2009, and did not seem a big deal. But this bigger application. 
    And then after about 15 minutes, I get an error message:
    Error 8 occurred at AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller 
    So this is running with the 2009 f2 version on XP pro with 1Gb of ram. And for the 2009 sp1 version on windows 7, with 8Gb of ram....
    So do not expect any memory issues with the SP1. Could this be a windows 7 x64 issue?
    Anyone any experience with building larger applications?

    Hello Everyone,
    We have observed that building executables in LabVIEW 2009 is slower than in 8.6.  In most cases it was about 10 to 20%.  However, in some larger builds we have seen almost a 3x or 4x slow down.  This large slow down has been reported to R&D for further investigation (CAR 205343).  In the case that was reported to us the build was about 8000 VIs and took 2GB of memory to complete.
    There wasn't a difference between LabVIEW 2009 and 2009 SP1.  The slow down occurred between 8.6.1 and 2009.  Does your slow down occur between 2009 and 2009 SP1?
    Message Edited by Jon S. on 03-09-2010 08:42 AM
    Regards,
    Jon S.
    National Instruments
    LabVIEW R&D

  • Can't open .prj files CVI 2009

    Running CVI 2009 and everything had been running fine for weeks.  Shut down test program that was running.  Installed my license device and went to my .prj file to open it up in debug mode.  When I double clicked on it, Windows says it can't find the file, even though it is sitting right there in explorer, it will not open it.  Tried several other .prj files and it does the same thing.  Tried opening CVI by itself and then loading the .prj file, but the splash screen comes up and then it never does anything else.  Rebooted several times (running XP SP3), then finally tried to do a repair of the CVI install.  This didn't help and it did the same thing.  Then deleted everything and did a fresh install...it still says it can't find the .prj file.  It seems like something has gotten corrupted in my Windows install maybe??  Probably going to try and re-image the machine, but trying to figure out what happened.  Anyone seen anything like this ever before???
    Thanks for any info...
    EDGE

    Hi EDGE,
    I haven't run into a similar error in the past but keep us posted on if reimaging the machine resolves the issue.
    Best Regards,
    Swathi B

  • CVI 2009 Very slow installation of distribution kits

    I'm having an issue with distribution kits built with CVI 2009 taking a long time to install on some PCs.  In the installer, the progress bars will both be completely full, with the top one displaying "Overall Progress" "Currently Installing [application name].  Part 1 of 1."  The bottom bar displays nothing.  During this time, there is usually a few instances of msiexec.exe sucking up considerable CPU time according to Task Manager, and the disk does not appear busy.  If I wait several minutes (sometimes 10 minutes or more), it will eventually move on, with the next step displaying "Validating Install..." on the bottom progress bar.  This only happens on some PCs, other ones install in a reasonable amount of time (less than a minute).  Once the installation is complete, everything appears to have worked and the installed software runs fine.  The only pattern I've noticed that the PCs that show this problem tend to be older models.  One is a P4 3.2Ghz desktop with 1.5GB of ram, and the other is a Core Duo (not sure about speed at the moment) Dell laptop with 2GB of ram.  Both are running Windows XP SP3.  
    Any insight into this would be appreciated, as some of the PCs that show this are ones used for testing software packages and often having things installed onto them.  Thanks.

    Hi tstanley,
    I was wondering what you were running distribution kits from - hard drive, CD, network or USB stick?
    Charlie Rodway
    Test Design Engineer
    Rolls-Royce Controls and Data Services Ltd

  • Image ROI ID number in LabVIEW 2009 SP1?

    In LV 8.5 (Vision), multiple ROIs had ID numbers displayed next to them:
    Apparently not so anymore in 2009 SP1:
    The only difference between the two VIs is that I was using a classic image object and I am now using the modern version;and the image tools window is replaced by the image tools palette associated with the image. There is no image property that I can find to turn the ROI "legends" on or off.
    How is the user supposed to know which ROI is which?
    Solved!
    Go to Solution.

    Ooops...: Indeed. I checked my LV 8.5 code (in fact written in LV 6 or whenever the first Image control was released) and I did overlay the ROI numbers myself at that time! 
    Since I had meanwhile used overlay to get ROI numbers, I just reinvented the wheel...twice.
    I still think that would make sense to have this feature by default in the Vision toolkit.
    X.

  • I'm trying to read some XML data from temperature logger over my network. I'm using LabView version 2009 sp1. I'm using the URL Get Document Vi. It works fine when using Internet sites like google or foxnews etc...

    I'm trying to read some XML data from temperature logger over my network.  I'm using LabView version 2009 sp1.  I'm using the URL Get Document Vi.  It works fine when using Internet sites like google or foxnews etc...
    When I use it with my temperature logger most of the time I get an Error 66...but some times it does work and actually retrieves the document. 
    I can use the same address "http://172.22.21.68/XMLfeed.rb" (Internet Explorer or Google Chrome) in my browser and get a response every time.  When accessing from my browser the server in the temperature logger does take around 6 seconds to respond, but it does respond every time. 
    Is the URL Get Document Vi exceeding a timeout?  If so, where can I set it to wait longer?
    Attachments:
    Error 66.jpg ‏183 KB

    It looks like the TCP Buffered Read has a 2.5 sec timeout, I believe that is where I had trouble as well.  Try creating your own URL Get HTTP Doc vi in which you call URL Get Document in normal mode, with an appropriate number of characters to fetch (enough characters so that you capture all the important data in the XML file).
    Attachments:
    ex1.PNG ‏33 KB

Maybe you are looking for

  • Utilizing Multimedia Links - Links to Media Using Adobe Acrobat 9

    Embedding multimedia such as videos makes PDFs too large to e-mail and large to store, and each distributed PDF has to contain the video instead of the video residing in just a single location. I wanted to know whether one can embed links in the PDF

  • Logical Standby Data Consistency issues

    Hi all, We have been running a logical standby instance for about three weeks now. Both our primary and logical are 11g (11.1.0.7) databases running on Sun Solaris. We have off-loaded our Discoverer reporting to the logical standby. About three days

  • Lightroom 3 Trial is the same in quality as Final Version?

    I have here the option to buy Lightroom 3 as my first choice in application for Adobe Software in environment desktop for 32 Bits acknowledge. I'm seeing here posterior versions have it 32 Bits as secondary standard option in 64 Bits version. I'm ent

  • Creating View for an extractor with reference field

    Hi All,          Here is my requirement. I need to create a DB view for an extractor. I need to join 3 tables : AUFK,AFIK & AFKO. Table Join Conditions: AUFK     MANDT     =     AFIH     MANDT AUFK     MANDT     =     AFKO     MANDT AUFK     AUFNR   

  • How to create an Alert Service using Oracle9i wireless?

    Hi All, I wanted to create an alert based service on oracle9i...but i am unable to figure out from where should i start doing..i am under basic confusion of how this whole system actually works..how to configure my service..can any body suggest me...