gap

This looks like a good tool. I was wondering if (without opening and viewing the Zip file,...) Does this demo let you use a twain device as a webcam (slow motion) with Labview? Cheers!

This is an issue that I reported to the Realtime PXI team about two weeks ago. I have written many applications that use the installer deploy the executable to a headless PXI system. The NI web site still has application links touting this as a great feature (launching target code from installer) I have an open issue on it at NI. The applications people said that someone there (no name dropping but they know who they are) is working on it. My request has been taken and no status update(in two weeks) has been to me on NI's application team progress. The work around has been to go back to LV 7.1!!!

How about powing a skateboard with labview.

Here is a document that my local NI rep sent. Author: Gerardo Garcia x32773 Last updated: 10/10/05 Note: this document is a work in progress. You can find a link to the latest version of this document here. General Questions 1. What is a LabVIEW Shared Variable?The LabVIEW shared variable is a new feature in LabVIEW 8 for sharing data between VIs and networked computers. The API is similar to a local or global variable; however it has many additional features such as network buffering. 2. When should I recommend using shared variables to customers? NI recommends using shared variables for most applications that need to share and monitor data across the network. As a general rule of thumb, we will recommend shared variables for most applications. Shared variables are not recommended in medium to fast streaming applications, such as vibration monitoring, etc. In these cases, low-level TCP or UDP functions will provide faster communication. See the performance section of the FAQ for more information. 3. How does the shared variable work? The shared variable uses different methods to communicate depending on the shared variable configuration settings. When a shared variable node is placed on the block diagram, LabVIEW scripts the corresponding communication code in the background. 4. Can users see the code behind the shared variable? No.5. What are the different types of shared variables? There are three types of shared variables: 1. Single-process 2. Network-published 3. Time-triggered The type of variable is designated through a setting in variable properties dialog. 6. What is a single-process shared variable and how does it work?Single-process shared variables behave much like global variables and will have similar performance. They are used to transfer data between VIs or loops on a single computing device. There are two advantages that single-process shared variables have over global variables:

The exam was OK. I had a few interuptions while taking it and still had plenty of time to finish.

Part of the problem with upgrading would be that the test stand is a UNIX SUN station. I have very limited or no support to upgrade the UNIX station. It took several weeks to get a new monitor (special connector) for it. Upgrading may just cause a problem that our very limited It group could not fix. Then testing would not be able to start. Labview 4 may not be so bad to use afterall. "If it is not broken do not fix it." So like I said before, I agree that the best solution at this time is to work in the native LV4 and just live with it.

Does example code exist for the LV8 real time module? NI decided to change the real time code programing style by adding a shared variable. What is it and how does it survive? Examples of the new coding style would be helpful. If they "really do exist"(just like talking M&M's which are tasty by the way) , where can the elusive code snipits reside. Any help in linking or posting would great thanks in advance.

Everything you mention sounds true. It makes sense. I am stuck using LV4. Thanks for the comments.

This month I have been tasked with testing a new custom ASIC. We are using an old IMS Logic Master XL 60 to automate the testing. The thing uses UNIX and Labview 4. The driver will not be updated for any newer versions of LABView. Any ideas on how to roll back LabView 7 code back to Labview 4? There is no "undo" for pete sake.

Does anyone have experience using the PXI 6120 DAQ card with LV real time? I have been plagued by problems for over a year. (Using Traditional Daq) I use the analog output for continuously generating a sine wave. Then I set up the analog input to capture fininte data for a set number of hardware triggers. 10% of the time, when the analog input re-arms for the next trigger, the analog output stops updating. No error code is ever created by the sofware driver. The short term fix has been to monitor the analog output with a portable scope and reboot the PXI to reset the hardware. The NI support network came up with the solution of using "DAQmx" a major code rewrite. I finally rewrote the code only to find a new set of "buggy boos". These new hurdles are the result of using LV8. To get over the new hurdles, I am hoping that a good example program exists for LV8 RT that shows how to remotely control a PXI chassis with 3 DAQ cards.