Include sys/timeb.h functionality in a LabView application

I would like to use functionality made available by the header sys/timeb.h in a test application.  Does PharLap 13.1 support such functionality?  If so, how can it be exposed to a test application (not supported by standard #include); else, does PharLap support comparable functionality elsewhere?  If so, where?
Thanks.
KnechtDDC

Hey KnectDDC, 
I know of a few articles and sources that will be helpful. First PharLap 13.1 does support some DLL calls but, you need to make sure the DLL can work on a realtime system. You would need to compile the code into a DLL first. Here is an article that goes over making DLL from CVI for Real Time OSes:
http://www.ni.com/white-paper/4583/en#toc3
I would recommend section 8 because it provides an example of how to build a DLL in CVI for use in an RT system. There is a tool you can use to check to see if the DLL can run on the RT system as well:
http://digital.ni.com/public.nsf/websearch/0BF52E6FAC0BF9C286256EDB00015230?OpenDocument
Hopefully these documents are helpful and provide some insight into how the requirements for accessing code one real time systems. 
Best Regards,
-KP
Kurt P
Automated Test Software R&D

Similar Messages

  • What kind of function(s) (in dlls) have to be call by a Labview application to be able to manage the PC's power supply

    Assume that a Labview application is running on a PC. The PC has a DC battery. When a "power off" is detected on the AC line, data should be saved, Labview application and Windows should be closed.
    What kind of function(s) (of which dll) should be called by a Labview application to realize this data and system management in a safe manner ?

    UPS (Uninterrupted Power Supply) systems can send messages to the PC through the serial port when the AC is lost and when battery is low. I'm not sure how this message is sent but I suspect they use Windows Messaging. If you could find this out, you could write your vi to constantly look for this message and shutdown when it sees the message.
    - tbob
    Inventor of the WORM Global

  • Are LabVIEW VISA functions supported by LabVIEW Run Time Engine?

    I have an executable file that I created using LabVIEWS Application Builder. When I run the application on another computer that does not have LabVIEW installed, it crashes with a Windows message stateing the my application has generated erros and will be shut down by Windows. I have isolated the problem as having something to to with VISA Reasource Names.
    Does anyone know if there has been any issues regarding the use of VISA function in LabVIEW Run Time Engine? The version of LabVIEW that I have is 6.0.2. The version of Run Time Engine is 6.0 .
    Dan

    Yes there are issues with the RTE 6.0 and VISA. Use the RTE 6.0.2
    LabVIEW, C'est LabVIEW

  • Sun Studio cc includes unused static inline functions in object file

    While trying to compile some code originally compiled with GCC I run into a linking problem. My problem seems to be caused by that GCC does not include unused static inline functions in the object files while cc does. The following simple example can be used for illustrating this:
    void foo();
    static inline void bar()
      foo();
    int main()
    }This program compiles and links without any problems using GCC and Sun Studio 12 CC (the C++ compiler) but fails to link using Sun Studio 12 cc:
    khepri%> cc staticinline.c
    Undefined first referenced
    symbol in file
    foo staticinline.o
    ld: fatal: Symbol referencing errors. No output written to a.out
    It is probably fine of cc to include foo() in the object file (although not necessary?). My questions are:
    1. Are there any reasons for why cc includes unused static inline functions in the object file while CC does not?
    2. Are there any ways or options to tell cc to not include unused static inline functions in the object file?
    In the example above this is easy to fix by just removing or #ifdef away the code but the original code where I have this problem is not maintained by me and the static inline functions are in header files that get included in multiple C files and in some of these the functions are used.
    Thanks,
    Olav

    olavsa wrote:
    1. Are there any reasons for why cc includes unused static inline functions in the object file while CC does not?
    2. Are there any ways or options to tell cc to not include unused static inline functions in the object file?Removing dead code is an optimization, so you need at least -xO1 for that.

  • Couldn't include CNTN01 in z function group created at SE80

    Dear All,
             I am involved in workflow development for determining agent for a step.
             But I couldn't include <CNTN01> in z function group created at SE80?
             How to do so?I will be grateful for your help.
    Thanks,
    S.Suresh

    Hi Samson,
                   Thanks for your reply.
                   As you stated, <CNTN01> is found at the include file LSWEATOP under the function group SWEA.
                   It implies that I need not include ,<CNTN01> in my z function group?
    Thanks,
    S.Suresh

  • Article: Functional Globals in LabVIEW 8.5 - No Loop, No Joke

    Hello Everyone,
    I've written another article on my blog:
    Functional Globals in LabVIEW 8.5 - No Loop, No Joke
    I hope you find it interesting
    Thanks,
    -Jim
    Message Edited by Jim Kring on 09-07-2007 08:24 AM

    Thank you for your attention!
    I've opened the fixed vi and all seems to be ok, but in few mouse click all messed up again causing strange floating wire and a LV crash.
    If you are brave please try the following procedure (save and close all of your work..!):
    Open your fixed vi.
    CTRL-E to display the block diagram.
    Rigth click on the upper (DBL) feedback node and change it to "Globally Initialize".
    Right click again on the same feedback node and select "Move Initializer One Loop Out".
    Select the feedback node, the "+", the "+1" and the other (blue, INT32) feedback node.
    Then perform the "Horizontal Centers" alignement.
    (in my case) voila! Move one of the 2 feedback node and see what happen....
    Now try to close and save the vi.
    I run LV on a NI PXIe-8106 so I think that this kind of hw is fully compatible with NI software... :-)
    I suspect that in this case the problem is not at a graphic level but reflect a corruption of internal data LV data.
    Attachments:
    Broken wire.jpg ‏54 KB
    Error3.jpg ‏60 KB

  • What's the largest header file in /usr/include/sys?

    Just noticed this,
      $ ls -l /usr/include/sys | sort +4n | tail -3
      -rw-r--r--   1 root     bin        59151 Jul  4 03:39 dtrace_impl.h
      -rw-r--r--   1 root     bin        76941 Jul  4 03:39 sunddi.h
      -rw-r--r--   1 root     bin        83768 Jul  4 03:39 dtrace.hwhich is great because dtrace.h is so rich with comments, and dtrace_impl.h has plenty of ASCII art. Hooray!
    This more than makes up for the sins of /usr/include/sys/tnf_probe.h! ;-)
    .... now if you guys are ever bored, feel free to update /usr/include/sys/swap.h, /usr/include/vm/anon.h ... :-)
    Brendan

    Sorry I was really busy the last few days. Thank you for your answers!
    I probably should have left out all the specifics of what the software was that I was packaging, because I think what I was really asking did not come across clearly. What I really wanted to know is:
    Why do I have to provide the "-I /usr/include/headers_dir" compiler option for some libraries but not for others, although the header files for each lie in a level 1 subdir of /usr/include?
    I thought that maybe there was some kind of index of installed libraries that I didn't know about, which I could have updated from within PKGBUILD (so I guess that's why I included it originally). Seems to me now, though, that this is not the case.
    I did put in some google time (but not lots b/c 1. hard to google and 2. busy) to find an answer, but to no avail and it's not really top priority right now (and quite honestly never will be, since there is the -I option), so I guess it'll have to wait, unless someone knows...
    ---EDIT---
    So, right after I posted this (stupid me) I had a little think and I finally understand, whats happening.
    1. Headers are not found without specifying the directory they are in.
    2. I need the -I option because easykf headers are not well formed.
    Thanks a lot!
    Last edited by maximax (2013-09-27 00:26:03)

  • Getting syntax error in /usr/include/sys/ header files during Compilation

    Hi,
    I am migrating old PRO C code from Oracle 8 + Solaris 8 to Oracle 10 + Solaris 10 environment. While compiling the code it is giving error :*
    Syntax error at line 69, column 2, file /usr/include/sys/uio.h:
    Error at line 69, column 2 in file /usr/include/sys/uio.h
    lloff_t uiooffset; /* file offset */
    .1
    PCC-S-02201, Encountered the symbol "lloff_t" when expecting one of the followin
    g:
    } char, const, double, enum, float, int, long, ulong_varchar,
    OCIBFileLocator OCIBlobLocator, OCIClobLocator, OCIDateTime,
    OCIExtProcContext, OCIInterval, OCIRowid, OCIDate, OCINumber,
    OCIRaw, OCIString, short, signed, sql_context, sql_cursor,
    struct, union, unsigned, utext, uvarchar, varchar, void,
    volatile, a typedef name,
    The symbol "enum," was substituted for "lloff_t" to continue.
    Any guess why this is happening?

    Hi,
    Try using the PARSE=PARTIAL USERID=user/password[@SID] SQLCHECK=SEMANTICS precompiler options.
    All your hosts variables must be declared inside a Declare section.
    Reference: Pro C/C++ Programmers Guide, chapter 5
    Reguards,
    Rene Rivet

  • DataSocket Server will not start when the Launch DS Server if Local URL.VI is bundled into a LabVIEW application.

    I want to run a LabVIEW application on several machines remotely that do not have LabVIEW installed (licensing issues). Hence I have built a LabVIEW executable with the RunTime Engine to install on all of these remote machines.
    The VI has a bi-directional link, using Datasockets, to a machine with DAQ and Image acquisition functions. It primarily receives data items, but also the capability to change data items so it needs to run the "Launch DS Server if Local URL.VI" in order to publish data to the DataSocket server.
    When I run the pre-built VI on a machine that has LabVIEW Developers Edition installed, everything works fine - ie.
    the DataSocket server starts on the remote machine. However when I build the *.exe application and run it on a machine with and without LabVIEW Developers Edition installed the VI successfully subscribes to the DAQ and Image Acquisiton machine, but it does not start its own connection to the Data Socket server, and hence does not publish the data that the DAQ machine needs to suscribe to. IT seems that the Launch DS Server if Local URL.VI is bypassed? I have fiddled around with the Build settings but to no avail.
    In short, how do I get the DataSocket Server to run in a LabVIEW executable? Is it indeed possible? Any advice would be welcomed.
    When distributing a Labview Application (*.exe) with Data Socket Server Publish functionality, the DataSocket server does not start and hence no data can be sent by the Remote PC to the Server. The VI successfully retrieves data from the DS Server. I have used the "Launch DS Server if Local URL.vi" in the ditributed application but for some r
    eason this VI is not executed when I run the executable. How can you force the DataSocket Server to run with executable LabVIEW applications?

    Ryan,
    How to add Datasocket Server Control.vi?
    Source Files only show Project Files.
    So, I added Datasocket Server Control.vi file to the project first.
    Then I added it to Always Included < Source Files < Application Properties (Build Executable).
    Last, I built the Executable, but it didn't work.
    Can you help me.
    Thank you.
    Pedro Raposo

  • Porting a labview application from windows to linux

    Hello,
    I need to compile a labview application that has been created for windows under linux. It depends on calls to functions NBFifoCreate and NBFifoWrite. These are part of the nbfifo.dll library under windows. Could anyone point me in the right direction how to replace this dependency?
    Also I am trialing LabView Professional Linux. As I am reading along I gather that I might need LabView RT Module. Is that correct and does it come included with the Professional version.
    Thank you in advance.

    Hello Damien1979,
    It sounds like you have an application developed under the Windows OS which used features of the LabVIEW Real-time Module.  Now, however, you are trying to open the same VI or Project under Linux.  Is that correct? 
    What distribution of Linux are you using?
    Which version of LabVIEW are you using?
    The LabVIEW development system is supported under Linux, however, not all modules and toolkits are available for installation.  This link below contains the supported modules.
    Developing Linux Applications with NI LabVIEW or LabWindows/CVI
    I believe the NBFIFO.dll related files are associated with the LabVIEW Real-time module, but I haven not confirmed that yet.  The LabVIEW Real-time module is not featured in the link above.
    Regards,
    George T.
    Applications Engineering Specialist
    National Instruments UK and Ireland

  • Is there an easy way to know if a vi within a LLB not being use by a Labview Application

    To All,
    I have developed a Labview application over a year that contains a number of LLBs.  There are significant number of VIs within those LLB files that were written but have not been called  by the application.  I am trying to optimize all LLB files to exclude those unused VIs.  Because there are many of them, the task to find out which Vi is being used and which one is not become very tedious.  First question: Is there a way to automate the process?  Second question: Does a compiled Labview application include all used and unused Vis from the LLBs in the .exe file?  I am very appreciate any inputs from this community.
    A Labview User  

    Ben wrote:
    In pre-LV 8 you could do a "Save with options..." and choose development distribution, single prompt preserve hiarchy and LV will pick-up all of the used VI's and plomp them down in a new location leaving all of the used behind as well as fixing up a of the linkages to point at the new location.
    In LV 8 and beyond you can create a Source Distribution in the project and acoomplish the same thing.
    In LabVIEW 8+, you can get something similar to the first option by selecting "save for previous" and then pick the existing version (yes, it's there!).
    LabVIEW Champion . Do more with less code and in less time .

  • PID control in a windows CE Labview application

    Hi there,
    I want to build an application that will control the temperature in some ovens, using PID control. The application will be running in a controller (or a touch panel computer) with windows CE OS. I have Labview 8.6, PID control toolkit 8.6 and Touch panel module 8.6. The problem is that the PID vi's don't seem to work in touch panel module. 
    Is there any way to implement PID control in a windows CE Labview application?  
    Thanks in advance.
    Solved!
    Go to Solution.

    I think with a timed loop you can run reasonable good timing down to 1 mSecond. I think 1 mSecond is the lower limit for non realtime systems like Windows/windows CE. And if you have the PID toolkit this will supply you with the functions you need. You do not need an extra CE PID toolkit. This because  the touch panel module run under your standard Labview environment. But I do not know if all the functions in the PID tool like fuzzy logic are compatible with CE. Have you also considered Windows Embedded as OS for your module. With windows Embedded you can run standard Labview built exe files
    Both Windows Embedded, and XP Embedded can be trailed
    http://www.microsoft.com/windowsembedded/en-us/products/westandard/default.mspx
    Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
    (Sorry no Labview "brag list" so far)

  • LabView Application program crashses randomly

    Hi,
    I have developed an application for a monochromator system using LabView 2012 (32-bit version) as my programming language.
    My application performs calibrated scan using the Calibrated Photodiode from 300 nm to 1100 nm and then perform Device Under Test (DUT) scan from 300nm to 1100nm at an interval for 5nm.
    My application crashses randomly when inside a for loop that goes from 300 to 1100nm at an interval of 5nm, whether it is performing a Cal Scan or DUT scan.
    The one thing that is consistent is that it crashes whenever LabView executes my supplier’s .NET DLL/ function call. Once the application program goes into the monochromator function call, it does not give LabView the control back. The application is stuck inside the function call.
    On Good days I am able to scan up to 30 parts with no crashing, while some days it can barely scan 5 parts. It is very inconsistent.
    I am not sure if anybody have seen any problems using dll to interface with Labview 2012.
    I have attached an image of problem I am encountering, where the LabView application is stuck in the DLL and it does not give control back to LabView.
    I would appreciate any assistance on this subject.
    Thank you,
    Nirav
    Attachments:
    Cal Scan LabView Stuck.jpg ‏390 KB

    About the only thing I can determine from that jpeg is that you could benefit greatly from this and especially this.  Please upload the actual code, if possible, so we can help you decipher it.
    thanks!
    Bill
    (Mid-Level minion.)
    My support system ensures that I don't look totally incompetent.
    Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

  • Labview application very runs poorly on better PC hardware

    What could cause a Labview application to run extremely poorly when deployed to a new higher performance PC verus the 4 year old one at my desk?  I'm using an Intel Core Due 2 on my desktop (2 cores), whereas my application is being deployed to an Intel Xeon (4 cores).  I've tried running both the old LV8.6 version of the software and the newer LV2011 version, and both are crawling to the point the application cannot be used.  The GUI isn't updating at the 4x per second, the mouse pointer is extremely jumpy when moved around the screen, and tabs/menus take several seconds to a couple minutes to be responded by the application.  On my desktop PC, the application runs smooth using the same executable file.  Both have the same OS (32-bit XP SP3) and both are running the same anti-virus software.

    ExarK,
    - Can you supply additional information on what your application is doing?  
    - Do you have the source code available with the LabVIEW Development Environment?  It sounds like LabVIEW is either hogging your resources (insert Wait functions into any loops you are running to periodically free up your processor) or that there is a memory leak (make sure you are closing your references correctly).
    - Try building one of our shipping examples to run with your DAQ device (a simple analog input will do).  See if this runs slowly on the target PC as well.
    Andrew T.
    National Instruments

  • How can I get the measured data of a compiled LabView application via active X?

    I want use data measured by a compiled labview application in a visual basic program by the way of active x. i your knowledge base is only explained how to do this with a notcompiled vi
    or how to call a compiled vi but not how to get the properties.

    A. Rafiq's reply / answer is just exactly what I was looking for as well. I'm using it with VBA for an Excel application.
    Note that the differences between this and the "not compiled" VI is that the application is the compiled application name, versus LabVIEW.
    Additional information:
    Remember that when you build the application, it puts the VI(s) in a wrapper app, which requires the Run-Time Engine.
    In order to access the VI, you have to get a reference to it. Doing this starts the app.
    Now the VI's methods and properties are exposed.
    With the GetControlValue and SetControlValue
    methods of the VI you can access all of the controls on the front panel.
    Remember that the values returned from the GetControlValue method are of type Variant.
    If you find you h
    ave some trouble getting data in or out of your (LabVIEW) ActiveX server app, you can also easily write a VI to access the server.
    Remember that if you want to run these, the ActiveX server (LabVIEW) and the VB client app, on a remote machine you must:
    Install on the target machine the LabVIEW RTE (which you can include with Application Builder.
    Running the server app once on the remote machine before running the client is a way for the server app to register itself (at least in LV 5.1).

Maybe you are looking for