LabVIEW & WinNT

Hello,
Can anyone tell me if I can use the memory VI's In Port.vi and Out
port.vi with Windows NT 4.0 (Or with Windows 2000)? I am
using LabVIEW 5.1.1
The manual says that it can be used with Win 3.11/95/98.
Thanks,
Patrick Pol
The Netherlands
[See first answer for additional information]

Hi Patrick,
The hardware layers are much better protected under WindowsNT. Any request
for access to the system has to go though the operating system. Because of
this
difference in architecture you cannot use the standard InPort and OutPort
vi's as
supplied by National Instruments. However they do have a fix for it but for
some
reason.... Anyway if you call NI support they will say they are aware of the
problem
and will send you the WinNT VI's. But I can cut the process short and just
attach it.
(private mail)
RB.
From: [email protected]
Subject: inport and outport
Classification: Restricted
|---------------------------------------------------------------------------
---|
|Title*: Port and Memory Utilities for Windows
|
|---------------------------------------------------------------------------
---|
|Description*:
|
|These files allow a user to call In Port and Out Port from Windows
98/95/NT. |
|There are also functions to read or write physical memory. The zip file
below|
|contains an installer that installs two LabVIEW libraries of 12 VIs each, a
|
|CVI DLL, the CVI run-time engine (with the low level system driver), and
the |
|source file. There are separate libraries for LabVIEW 4.x and 5.x. The
5.x |
|VIs are marked as thread-safe.
|
|In Port.vi and Out Port.vi are direct replacements for the standard LabVIEW
In|
|Port and Out Port. There are also VIs for reading and writing physical
|
|memory. However, these use an intermediate DLL, AccessHW.DLL, which in
turn |
|calls the CVI RTE. Consequently, this DLL must be in the same directory as
|
|the VIs.
|
|
|
|Also attached is a C example that uses these functions.
|
|---------------------------------------------------------------------------
---|
(See attached file: accessHW.zip)
Patrick Pol wrote in message <[email protected]>...
>
>Hello,
>
>Can anyone tell me if I can use the memory VI's In Port.vi and Out
>port.vi with Windows NT 4.0 (Or with Windows 2000)? I am
>using LabVIEW 5.1.1
>
>The manual says that it can be used with Win 3.11/95/98.
>
>Thanks,
>
>Patrick Pol
>The Netherlands
>

Similar Messages

  • LabVIEW / WINNT Keyboard scan?

    Hi,
    I am using LabVIEW 5.1.1 with WINNT 4.0 and need a "good" routine or
    pointer to a keyboard scan that can be fine tuned so PC resources are
    not strangled. I appreciate any help with this one!
    Karl Hanke
    [email protected]
    Sent via Deja.com http://www.deja.com/
    Before you buy.

    > I am using LabVIEW 5.1.1 with WINNT 4.0 and need a "good" routine or
    > pointer to a keyboard scan that can be fine tuned so PC resources are
    > not strangled. I appreciate any help with this one!
    >
    I'm not 100% sure I know what you are looking for, but the NI ftp site
    contains some VIs that give you access to key events in LV. They return
    a cluster of keys and modifier info like shift and ctl. They will give
    you key down events only, not key up, and they exist for all platforms.
    I believe you will find them in the LV31 directory, but they will load up
    into LV5 or 5.1 just fine. There are probably similar VIs at other sites
    on the LV web ring. You should be able to jump on the web ring at the NI
    site or at the umass site.
    Greg McKaskle

  • Installation Labview-- WinNT Embedded

    can I run a LabView runtime application on my PC-104 Computer where I
    have Installed the Win NT embedded?

    Yes, I have run LV apps on a SBC with NTE. Just be sure you have enough resources, RAM and disk
    space, to load the app and the run time engine.
    "Dario Jossen" wrote in message
    > can I run a LabView runtime application on my PC-104 Computer where I
    > have Installed the Win NT embedded?

  • Logoff in Winnt with command in labview

    Hello,
    some time ago somebody posted a message to ask about logoff menu when a
    button is pushed in labview. I read it but didn't need it so I removed
    it. It turns out that I do need it. Can somebody tell me how it was
    done ?
    ==> Push a button in LabVIEW, get the WinNT logoff menu.
    Thanks
    nlrme
    Sent via Deja.com http://www.deja.com/
    Share what you know. Learn what you don't.

    Thanks that worked.
    The python script however doesn't support my weather code ((CXTO)It's out of range).
    Anyone know one that does support Canada so I don't have to a bunch of them?
    Last edited by cryticfarm (2009-08-07 03:50:39)

  • Can LabVIEW run as a service on WinNT kernels [without a user logon]?

    Is it possible to run LabVIEW as a service on a WinNT kernel [NT 4.0, 2000, or 2003]?
    I.e. is it possible to run LabVIEW without a user logging on?
    Or must there always be a user logged on before LabVIEW can be run?
    Also, if standard-issue National Instruments LabVIEW cannot run as a service, then are there any third party products [maybe from Endevo, or Vogel Automatisierungstechnik] that have the ability to create something like a "LabVIEW-lite" that can run as a service [without a user logon]?
    Thanks!

    Windows
    =======
    LabVIEW code can run within a service, but LV does not support being built as a service.
    What is the difference? An NT Service requires a special exported API and integration with the NT Service Manager. We do not build that kind of EXE, just the regular EXE. However, you can build your LV application into a DLL and then load that up from your own service host EXE.
    However, there are a couple of gotcha's that happen when running as a service. First remember that you cannot have any UI - so if any of your VI's attempt to open their front panel, you are going to be in trouble. Second, there is an issue with pumping Windows messages in LV right now. See my blog article on ASP.NET and LV (which is LV running in a service - the aspnet_wp.exe service). My blog link is in my signature.
    Also remember that while a service doesn't need a user to log in, it itself is going to log into Windows to get the security credentials. You'll need to think about what credentials you want the application running under when you configure the NT service. Remember, Local System, which is the default, means that you have super user priv. on the local machine, but no NT Network permissions. It is generally a good idea to create an NT Workgroup or Domain account specifically for the service so that you can control what permissions it has.
    Other Platforms
    ===============
    Linux and Solaris daemons are a bit more straightforward and so, I think, both the EXE and DLL should work. However, I haven't done daemon work in over 10 years so I won't promise anything
    I have never worked on a Mac so I have no idea. But X is really a Unix OS so I imagine it would be the same as Linux. However, for all platforms supported by LV, building into a library and then calling the library from the OS's service host *should* work. Just the same rules about the UI.
    Brian Tyler
    http://detritus.blogs.com/lycangeek

  • Problem on WinXP / Labview 6.1 with VISA (serial port)

    There is a problem on WinXP / Labview 6.1 with VISA which i use to poll the state lines of the serial port. The only functions that i use are "VISA Open", "Find Resource", line state properties and "VISA close".
    On my own machine (WinME) it works fine as a standalone application (with runtime engine in the same direction), even if i rename the Labview directory so that Labview is not found.
    From my VXIpnp directory i deleted all but these files:
    directory "Win95",
    subdirectory "Bin" containing "NiViAsrl.dll",
    subdirectory "NIvisa" containing "visaconf.dll".
    When shipping this to WinXP (and copying "VXIpnp" to the root directory), the serial port was not found, so i renamed the direction "Win95" to "
    WinNT", but this did not work also.
    I installed the VISA server, although it seems not to be required -- no result.
    Final question:
    What must i do for distributing the program as a standalone application for all windows platforms?

    Hey Joachim,
    In order to create an installer that includes the VISA Run-time engine for serial IO you will have to purchase LabVIEW 7.x. See screen shot. This packages a small compact version of the run-time that can only be used for serial, but it takes up much less space. The installer that I created has my application, the LV Run-time, and the VISA run-time and it is about 26 MB.
    That is much smaller than if I had to include the 32 MB LV 7.1 run-time and the 14 MB VISA run-time separately. It would have been even smaller if I would have uncheck some of the items that I wasn't using.
    -Josh
    Attachments:
    advanced.JPG ‏31 KB

  • Activex question in labview

    Hello,
    I am trying to controll an 8753ES with the agilent intulink through labview using activex.  I have read about activex in labview, and and help file for intulink, which says:
    In order to use the Agilent IntuiLink VNA Automation Server, a Visual Basic program must reference two servers.  Under the Visual Basic Project | References… menu item, include the following two references:
    · BLXL Servers:  Check the box for  Agilent IntuLink Servers Common Interfaces.  As the description suggests, this library contains definitions of common interfaces.  In particular, this library defines some enumerated types, used by Agilent IntuiLink Automation Servers.
    · AgtServer8714:  Check the box for Agilent VNA Network Analyzer Automation Server.  This library contains definitions specific to the supported network analyzer products.
    Object Hierarchy
    AgtServer8714 Object
    Provides methods to obtain data, obtain graphics, save and restore calibration and state, and to establish and close a connection to a network analyzer.
    AgtMeasure8714 Object
    Provides methods to obtain scalar parameters from the network analyzer.  Most of these are setup parameters.
    AgtUtilities8714 Object
    Use the AgtUtilities8714 Object to:
    · Work with the network analyzer connection to the PC.
    · Work with the network analyzer descriptions and identity.
    Now, I have constructed what I think is the correct implementation in labview (see atachment), but when I run it I get an error that makes it seem like an i/o refernce is not included:
    Exception occured in AgtServer8714.AgtServer8714.1: CAgtServer8714::Connect method failed. CAgtCore8714::Connect method failed. CAgtConnectObject::CreateIO method failed. in vna_activex.vi
    What I really want to know is, how do the references that are required for a program in vb work in labview?  I looked up a vb sample for intulink, and they include four references:
    Reference=*\G{00020430-0000-0000-C000-000000000046}#2.0#0#..\..\..\..\..\..\WINNT\System32\STDOLE2.TLB#OLE Automation
    Reference=*\G{06EB23A2-C6C1-8714-98B5-080009C12B46}#1.0#0#..\..\..\..\..\..\Program Files\Agilent\IntuiLink\VNA\AgtServer8714.dll#AgtServer8714Lib
    Reference=*\G{D753C10E-EF9A-11D3-98B9-080009C12B46}#1.0#0#..\..\..\..\..\..\Program Files\Common Files\Agilent\IntuiLink\BLXLServers.dll#Agilent IntuiLink Servers Common Interfaces
    Reference=*\G{6B263850-900B-11D0-9484-00A0C91110ED}#1.0#0#..\..\..\..\..\..\WINNT\System32\msstdfmt.dll#Microsoft Data Formatting Object Library 6.0 (SP4)
    It seems like in labview, there is nothing else that is reading the reference when I do an automation open.  Any help at all is welcome.  Also, if you know of any labview examples that use intulink, that would be great.
    Thanks,
    Eric
    Attachments:
    vna_activex.vi ‏11 KB

    Here is a link to the Agilent8753ES instrument drivers from www.ni.com/idnet:
    http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=1625
    Brian
    Brian G.

  • How can I design my LabVIEW app to behave differently based on installed components?

    Howdy all,
    I've got a program that is complete, and offers some basic service. Advanced users will have the option of additional functionality. When users decide to use this program, they decide what capabilities they want - whether it provides just the base functionality, or if it has the advanced functionalities. The additional functionality relies on the installation of an additional LabVIEW component. In this case, the base package requires simply the LabVIEW(7) runtime engine. However the additional functionalities are vision related and require the installation of the IMAQ Vision 7 Development Module. I would like my program to detect the installation of the vision module
    on the user's computer, and give the user access to these vision functions ONLY if the vision pack is installed. (ie, I don't want to have two versions of the program - the user only installs one complete version, but some components will be hidden if they don't have the vision module)
    Currently, this program checks the Window's system32 directory for the presence of the imaq.dll and the nivision.dll. Right now, this system *sort of* works on most computers, but if the user has their windows installed in a non-standard windows directory (say they installed windows to "windoze" or something other than the standards like "Windows" and "Winnt")
    Does anyone know of a way to programmatically detect the installation of the Vision module? What I'm doing right now would work in 95% of the cases (I think) if I could nail down the root windows directory (which I'm pretty sure is stored in the registry for all Windows versions, but the name of the key depends on the version of windows, a
    nd I would rather not go down that road)
    Any help, stories about similar situations, etc., would be appreciated.

    Vitrick and Andre -
    Even better might be to use one of the Windows API calls
    "GetSystemDirectory" or "GetWindowsDirectory" located in the KERNEL32.DLL.
    See MSDN for documentation of the calls.
    Regards,
    James
    "andre@carya" wrote in message
    news:4059b191@newsgroups....
    > Hello Vitrick,
    >
    > With just a quick look at your problem I think you are looking for the
    > windows system variables found in the "My computer>settings>enviromental
    > variables", mine is called windir. Sometimes It's called %WINDOWS% I
    think.
    >
    > I don't know exactly how to implement these variables.
    >
    > Greetz,
    >
    > Andr�
    > "Victrick" schreef in bericht
    > news:[email protected]...
    > > Howdy all,
    > >
    > > I've got a program that is complete, and offers some basic service.
    > > Advanced users will have the option of additional functionality. When
    > > users decide to use this program, they decide what capabilities they
    > > want - whether it provides just the base functionality, or if it has
    > > the advanced functionalities. The additional functionality relies on
    > > the installation of an additional LabVIEW component. In this case,
    > > the base package requires simply the LabVIEW(7) runtime engine.
    > > However the additional functionalities are vision related and require
    > > the installation of the IMAQ Vision 7 Development Module. I would
    > > like my program to detect the installation of the vision module on the
    > > user's computer, and give the user access to these vision functions
    > > ONLY if the vision pack is installed. (ie, I don't want to have two
    > > versions of the program - the user only installs one complete version,
    > > but some components will be hidden if they don't have the vision
    > > module)
    > >
    > > Currently, this program checks the Window's system32 directory for the
    > > presence of the imaq.dll and the nivision.dll. Right now, this system
    > > *sort of* works on most computers, but if the user has their windows
    > > installed in a non-standard windows directory (say they installed
    > > windows to "windoze" or something other than the standards like
    > > "Windows" and "Winnt")
    > >
    > > Does anyone know of a way to programmatically detect the installation
    > > of the Vision module? What I'm doing right now would work in 95% of
    > > the cases (I think) if I could nail down the root windows directory
    > > (which I'm pretty sure is stored in the registry for all Windows
    > > versions, but the name of the key depends on the version of windows,
    > > and I would rather not go down that road)
    > >
    > > Any help, stories about similar situations, etc., would be
    > > appreciated.
    >
    >

  • What are the Dynamic Events avaliable in the LabView 6.1 Event Structure?

    I recieved LabView 6.1 recently and I am working with the Event Structure, and I'm trying to figure out what Dynamic Events are avaliable in the event structure, and how to access them. If you don't understand what I'm talking about, open a new VI in LabView 6.1 and drop an event structure on the diagram. Add an event and look at the dialog box that appears on the screen, specifically the Event Sources section. The third option in this area of the screen is "grayed out" but reads "Dynamic". I'm curious what these events are, and how I access them. I'm running WinNT 4 SP6.
    Thanks,
    Chris Davis

    I believe this is part of a feature which is not yet present in LabVIEW 6.1, but may be present in a future release.

  • Help convert from 7 to labview 6.1

    Hi,
    Could anyone help me to convert the code to labview 6.1
    Thankyou very much
    Attachments:
    ag663xxa.zip ‏503 KB

    You can try creating a 6.1 driver yourself. All the IVI drivers are simple wappers around a Call Library Node Function into the DLL created in LabWindows/CVI. The LabVIEW driver is created from the Tools>Instrumentation>Import CVI Instrument Driver selection. Download the CVI driver and install it. The converter will require some files installed in the \VXIpnp\WinNT (.fp) and \VXIpnpWinNT\bin (.dll) folders.

  • MAX shows my GBIP-USB Interface, but no communicatin with Labview

    I'm using a GPIB-USB(Agilent) Inferface to communicate with my devices.I Install the drivers form agilent and Labview 6.0.2. MAX 2.0 does not show me my USB-GBIP Interface and no devices. So i have download MAX 2.2 and now i can communicate with my devices. The problem ist, that i can't open the VISA session in LABVIEW, so that i can't communicate with my devices. I try to open the NI-Spy, but it show me an error. Have erverybody a idea how can i solve this problem. THX

    Adi wrote in message news:<[email protected]>...
    > I'm using a GPIB-USB(Agilent) Inferface to communicate with my
    > devices.I Install the drivers form agilent and Labview 6.0.2. MAX 2.0
    > does not show me my USB-GBIP Interface and no devices. So i have
    > download MAX 2.2 and now i can communicate with my devices. The
    > problem ist, that i can't open the VISA session in LABVIEW, so that i
    > can't communicate with my devices. I try to open the NI-Spy, but it
    > show me an error. Have erverybody a idea how can i solve this problem.
    > THX
    My friend at Agilent supplied the following answer. There are suppose
    to be two pictures at the end of this note, but my news group
    interface
    does not allow them to be added.
    Les Hammer
    [email protected]
    Complete Test
    PO Box 6
    Loveland, CO. 80539
    ===========================================================
    I understand you want to control GPIB instruments using NI LabVIEW, NI
    VISA, and the Agilent 82357A USB/GPIB Interface.
    This method works for me. Perhaps you can compare your results to
    this procedure, and then make progress.
    1. Starting Conditions:
    I start with my HP Kayak XU800 PC (single 800 MHz CPU), with an NI
    PCI-GPIB+ card installed.
    My Agilent 82357A USB/GPIB Interface is not connected to PC nor
    instrument.
    The attached Visagpib01.vi LabVIEW program is on an uninstalled floppy
    disk: A:\Visagpib01.vi
    I format the C: hard disk and install Windows 2000 Professional. I
    reboot.
    Windows runs a Found New Hardware Wizard (for a PCI Simple
    Communications Controller). I assume that is for the NI PCI-GPIB+
    card. I click the Cancel button. I'll run a similar wizard AFTER I
    install the NI software.
    2. Install NI-488.2 for Windows:
    I put in my NI-488.2 for Windows CD (July 2000, 500739E-00) and let it
    autorun. I click on "Install NI-488.2 Software for Windows". I use
    the default Destination Directory: C:\Program Files\National
    Instruments\NI-488.2\ .
    I choose the default "Typical" installation, and complete the
    installation.
    Now I click on "Explore CD" and run the "SetupVisa" icon to install
    NI-VISA 2.5 . I use the default NI-VISA Folder: C:\VXIpnp\ . I
    choose the default "Complete" installation, and complete the
    installation.
    I click the Yes button to reboot my PC.
    Now that I have installed the NI software, the NI-488.2 Getting
    Started Wizard runs. I click on "Verify your hardware and software
    installation". It found my NI PCI-GPIB+ card as GPIB0. The Agilent
    82357A will not be visible yet. I click the Exit button. I'm done
    with this NI-488.2 Getting Started Wizard, so I click the x in the top
    right of the window.
    3. Install Agilent I/O Libraries for Windows:
    I put in my Agilent I/O Libraries for Instrument Control for Windows
    CD (L.01.00) and let it autorun. I click the Next button a few times
    until I see 2 big buttons: Full Installation & Custom Installation.
    Because this is the L.01.00 release and I installed the NI VISA first,
    either button would work. But I'll be precise and click the Custom
    Installation button. I use the default Destination Folder: C:\Program
    Files\Agilent\IO Libraries . I choose "SICL and side-by-side Agilent
    VISA Installation". This will leave the NI VISA as the primary VISA,
    and install the Agilent VISA as secondary VISA. After a few clicks on
    the Next button, it says the Agilent IO Libraries have been
    successfully installed. I choose neither View Readme nor Run IO
    Config. I click the Finish button.
    Some Operating Systems may require a reboot here. My Windows 2000
    does not.
    4. Prove NI VISA is Primary VISA:
    Start button - Programs - Accessories - Windows Explorer. Browse over
    to and highlight My Computer\C:\WINNT\system32\visa32.dll . File
    pulldown menu - Properties - Version tab. My file is National
    Instrument's VISA Library 2.5.0.0 .
    I click the Cancel button. File pulldown menu - Close.
    5. Plug the 82357A into the PC:
    I finally plug the 82357A into my PC's USB port (any USB port). The
    standard 82357A live configure window pops up: "Agilent 82357A
    USB/GPIB Interface Detected". Because Agilent VISA is installed, the
    VISA Interface Name defaults to "GPIB0". Because I know I already
    have a GPIB0 (my NI PCI-GPIB+ card), I click the Edit button and
    change the VISA Interface Name to GPIB1, by clicking the nearby little
    up arrow. I click the OK button.
    6. Configure NI Software to Recognize Agilent Interfaces:
    Start button - Programs - National Instruments - Measurement and
    Automation Explorer. I click the OK button because I don't care when
    MAX searches for new devices. Tools pulldown menu - NI-VISA -
    Passport Editor. I put a checkmark in the "NIVisaTulip.dll - VISA
    Library Passport for Tulip" line. I click the OK button. Because I
    changed a setting, I need to click the OK button again. File pulldown
    menu - Exit to exit MAX.
    7. Access an Instrument through the 82357A:
    The Agilent 82357A USB/GPIB Interface should now be accessible from
    NI-VISA. With my 82357A plugged onto my HP 34401A Multimeter, Start
    button - Programs - National Instruments - VISA - VISA Interactive
    Control. Below the "GPIB1 (hpib7, 82357)" line, is a line for my
    instrument, "GPIB1::23::INSTR". I double click on that "INSTR" line
    to pop up a session window. Basic I/O tab - viWrite tab, I click the
    Execute button to write the default "*IDN?\n" string. viRead tab, I
    click the Execute button to read the expected
    "HEWLETT-PACKARD,34401A,0,5-1-1\n" string. I'm done, so I click the x
    in the top right of the window. File pulldown menu - Exit to exit the
    VISA Interactive Control window.
    8. Install NI LabVIEW Evaluation 6i:
    I put in my NI LabVIEW Evaluation Software for Windows 2000/NT/Me/9x
    CD (version 6i, 350778A-01) and let it autorun. I click the Install
    button. Eventually I choose the Complete installation. It says
    LabVIEW 6i Evaluation has been successfully installed. I click the
    Finish button. Eventually I click the OK button.
    9. Run the attached Visagpib01.vi LabVIEW program:
    Start button - Programs - National Instruments LabVIEW 6i. I click
    the lower left RED Start using LabVIEW button. I click the Open VI
    button and enter the File name as A:\Visagpib01 . I close the
    Controls and Tools palettes by clicking the x in the top right
    corners. Notice the resource name field of "GPIB1::23::INSTR" to use
    my GPIB1 82357A connected to my 34401A at GPIB address 23. Operate
    pulldown menu - Run, and the read buffer field now says this expected
    string: "HEWLETT-PACKARD,34401A,0,5-1-1". Running the example again
    simply writes over the earlier string, and so does not appear to
    change the display. The attached Visagpib01.vi LabVIEW program is
    simplified from the "C:\Program Files\National Instruments\LabVIEW 6
    Eval\Examples\instr\visa\SRQ Event Handling.vi" NI example program.
    I attach 2 GIF files to describe the attached Visagpib01.vi program:
    Visagpib01_panel.gif
    Visagpib01_diag.gif
    I hope this helps!
    | Ted Cline
    | IO Support
    | Basic, Emerging and Systems Technologies (BEST) PGU
    | Agilent Technologies
    | CU-326, 815 14th Street SW, Loveland, CO 80537-6390 USA
    | 800-452-4844 Customer Support (United States)
    | 877-894-4414 Customer Support (Canada)
    | 970-679-5260 FAX
    | [email protected]
    | ftp://ftp.agilent.com/pub/mpusup/index.html Postsales Support
    GPIB and Connectivity Solutions:
    http://www.agilent.com/find/xbv_pgr_gpib
    IO Libraries:
    http://www.agilent.com/find/iolib
    http://www.agilent.com/find/iolibux
    VEE:
    http://www.agilent.com/find/vee
    Instrument Drivers:
    http://www.agilent.com/find/inst_drivers
    http://www.agilent.com/find/inst_drivers_pnp

  • "how to read parallel port using labview"

    "i am doing a bio medical project and need to read data from parallel port using labview. can anyone help me"

    Hi
    in most cases a simple example helps best.......see attachment. Find in addition in Word document a helpful picture of LPT - Pins.
    In case you work with WinNT, W2k, XP - you need to install accesshw.
    Regards
    Werner
    Attachments:
    printer_port_test.zip ‏41 KB
    dsub_25_parallel_port.doc ‏29 KB

  • Password for labview program

    Hi all,
    I am developing a labview program for a high
    power microwave device. The final program will
    be running stand alone on a pc attached to the
    microwave device in a laboratory. To ensure
    safety, I am wondering if I can set up a password
    to the labview program at start up so only
    authorised people can use it? Or if there is
    other way to do that. Any comment will be
    greatly appreciated.
    Thanks.
    Regards
    Hank
    Sent via Deja.com
    http://www.deja.com/

    In article <[email protected]>,
    [email protected] wrote:
    > Hi all,
    >
    > I am developing a labview program for a high
    > power microwave device. The final program will
    > be running stand alone on a pc attached to the
    > microwave device in a laboratory. To ensure
    > safety, I am wondering if I can set up a password
    > to the labview program at start up so only
    > authorised people can use it? Or if there is
    > other way to do that. Any comment will be
    > greatly appreciated.
    >
    > Thanks.
    >
    > Regards
    >
    > Hank
    >
    > Sent via Deja.com
    > http://www.deja.com/
    I am pretty sure that you can do that by using a case loop outside of
    your main program. You can set it up so that user(s) will have to
    enter a string (which would be password) before he/she can get to the
    front panel of the main program.
    Within this vi, you can have an array of strings such that users can be
    given different passwords (or level of authority) for more security.
    After the user enters the password, you can compare the user input by
    using equal function in the comparison palette (make sure the password
    list is case sensitive or stuff like that or you'll have to convert all
    the user input string to either upper or lower case if you want to save
    some trouble). If the result of comparison is true, then they can get
    into the main program, or else the program will quit.
    You can also put in looping structure to make it more fancy such that
    each user can be given say 3 chances to enter the correct password...
    If you want to go really fancy, you could also try to put in a data
    file that stores all the passwords in binary format (requires a little
    conversion, of course) in a directory of the target machine that you
    know exist (say WINDOWS or WINNT), and include the data file as part of
    your instalation disk content, point the installation destination to
    that directory. In your password program, find the target machine
    operating system and then look for the file from there.
    Hope it helps. If you have any questions, please e-mail me at
    [email protected], and I'll try to e-mail you a copy of my code.
    Sent via Deja.com
    http://www.deja.com/

  • Error in LabView.exe after each start

    I installed LabView 7.0 in an older computer (Pentium III, 500 MHz, 512M RAM, Windows 2k sp4) along with GPIB and E-series PCI cards. Each time I open LabView it crashes and says "LabView.exe has generated errors and will be closed by Windows. An error log is being generated." The error log is attached, but means nothing to me. It crashes with regularity within 30 sec of opening LabView but I seem to be able to run .vi's during that time. I've tried:
    1) Reinstalling
    2) updating video card driver and ActiveX
    3) installing on a different drive
    none of these help.
    Any help you may have would be appreciated.
    Attachments:
    LabVIEWlog.txt ‏1 KB

    Hello,
    The file you attached is a LabVIEW.ini file, where the configuration settings are stored. Please find the error log file, and this should give you a better idea what might have caused the error.
    There are two types of log files. There are those created by LabVIEW and those created by Windows.
    The log file created after internal LabVIEW errors is called LabVIEW_Failure_Log.txt and it is stored in your temporary LabVIEW directory. By default, this directory is located at C:\Documents and Settings\(User Name)\Local Settings\Temp (Windows 2000).
    NOTE: By default, the Local Settings folder is a hidden folder. In order to view hidden files and folders in Windows Explorer, select Tools » Folder Options » View. In the Advanced Settings field, select Show
    hidden files and folders.
    If you have modified the location of you temporary directory, the log file will be located there. To view or change LabVIEW's temporary directory path, go to Tools » Options » Paths » Temporary Directory. For more information on the error information contained in the LabVIEW_Failure_Log.txt file, visit the LabVIEW Internal Error Support Page linked below.
    If you receive an error message saying that LabVIEW has generated errors and will be closed by Windows, there will be a different log file created. This is a log file created by Windows, and by default it is a Dr. Watson's error log file. These log files are saved as .log file under ...\WINNT folder for NT based systems, and as .wlg under ...\Windows\Drwatson folder for Windows 9.x systems.
    If you open just LabVIEW, without trying to open a VI, will you still receive the crash? If so, can you create a new simple VI similar to the VIs that crash LabVIEW and run it? Do you call any hardware driver or o
    ther dlls with the VIs that cause LabVIEW to crash?
    Zvezdana S.
    National Instruments

  • XP/LabVIEW 4.0.1 Compatibility

    Hi, I am currently doing research at the local University using LabVIEW 4.0.1, PC 1200 DAQ board, and a Pentium 2 computer running WinNT. I am thinking about upgrading my computer in order to handle greater DAQ speeds. My question is concerning the compatibility issue between Windows Xp and LabVIEW 4.0.1. Has anyone tried LabVIEW 4.0.1 with XP; any success? or do I have to upgrade to a newer version of LabVIEW.
    Thank you for your help,
    Regards,
    RTsen

    Windows XP was first supported with LabVIEW 6.1. Now, it's always possible that it could work with 4.0.1, but it's very likely that you'll run into some problems. I would suggest upgrading to LabVIEW 6.1. Not only are you likely to experience less problems with the new OS, but you will always gain a lot of new tools in the upgrade from 4.0.1 to 6.1.
    J.R. Allen

Maybe you are looking for

  • " Screen Tearing" with EVGA GTX 970

    Hi everyone, when watching clips with movement or moving windows on windows somewhere else I get the "tearing effect" on my monitor. Meaning I see vertical lines while movement on my monitors, mainly in the middle. I do not see this line in PP CC 201

  • 2x LabVIEW Systems Engineer Full Time Positions – Sheffield and Bristol, UK

    2x LabVIEW Systems Engineer - Full Time Positions – Sheffield and Bristol, UK 1.0      Description: As a Systems Engineer, you'll be part of a team that is responsible for developing both hardware and software applications based on Object Oriented Te

  • I can't import keyword list into Aperture

    I want to import a big keyword list from last years photo library into this years, but when I export the keyword list from my 2012 library it's greyed out and won't import into my 2013 library. The Aperture help says it should work just fine, any tip

  • How to execute Sql command behind the submit button?

    Hello Dear, i design a Visual JFS page with 1 text box, 1 dropdown list, 1 date picker and 1 submit button. i have a database connected to my project with hibernate framework. now i want that whatever i change to textbox, dropdown list & date picker,

  • Urgent: MacBook Backlight Off

    I seem to have pressed some kind of deadly key combination that has completely disabled my display's backlight. The screen is barely readable and none of the normal brightness buttons or sliders are having any effect. Any ideas on how to get things b