Hi, I'm new to LabView and I experience a strange problem: The DAQ-Assistent stops working correctly some times. It is running correctly till all configuration is finished and the sub-vi should be created. After that I have this sub-vi but with no input or output connections, just the symbol of the vi. By double clicking it, the configuration is running normal, but after clicking OK there is still no in- or output by the vi. My steps are:1. open a new vi in labview2. clicking the express --> input --> DAQ-Assistent 3. configuring by my means (analog input, voltage, channel ai0)4. testing the input (all is working)5. clicking OK, so the vi is created I had this problem before and solved it by reinstall (repair the installation) labview and DAQmx. After that it worked. But I haven't made any changes to the computer since the last time it worked and now, after the weekend, it isn't possible to create a running vi again. I can use my old vi which I saved, but it isn't possible to alter the configuration made by the DAQ-Assistent. I don't know how this is possible or how to solve it, so I hope you can help me. I can provide some picture with my steps and showing that the hardware is running (as I see some output in the MAX testpanels as well as in the DAQ-Assistent) and only getting a vi with no connections and my saved vi where it is still running as long as I don't change anything by the DAQ-Assistent. Thanks for any advice. Hardware: PCIe-6251BNC 2110cable: SHC68-68-EPM Software (german):Windows XP SP3LabView 8.6DAQmx 8.9MAX 4.5.0f0 EDIT:Now after waiting and trying it several times, it works again. I can't explain it . Even after several reboots and starting and closing the program it wasn't working and now all of a sudden it's OK... I welcome any explanation, why this happens from time to time... Message Edited by mh_51 on 05-11-2009 07:54 AM

LabVIEW

daq-assistent not working sometimes

Author

Hello MarianMO,

I'm using kubuntu gutsy (7.10), so I'm using kde as window manager. One part of kde is a program called klipper which handles the clipboard. There is a menu item to delete all contents of the clipboard as you can see in the following pictures. The left one (or the upper one) has one entry, at the other one you can see that the clipboard was deleted (Zwischenablage leer):

For the connection to the windows machine I'm using a program called tsclient. It comes with the main ubuntu repository and the version is 0.148-3ubuntu1. You can find the description at the end of this post. At the remote side I have allowed machines to connect from outside per RemoteDesktop function built-in in windows XP.

Have a nice evening,

Description of tsclient:

Description: front-end for viewing of remote desktops in GNOME
tsclient is a GNOME program for remotely accessing Microsoft Windows NT/2000
Terminal Services and XP Remote Desktop Sharing as implemented by the Remote
Desktop Protocol (RDP). Using the rdesktop program as a backend, tsclient
allows users to access and view their desktops as stored on remote Windows
NT/2000/XP servers.
.
Some of tsclient's features include:
   * A GNOME panel applet to quickly launch saved RDP files
   * Support for RDPv5 and rdesktop-1.3 arguments
   * Reading .rdp files in the MS Unicode format
   * Writing .rdp files in ASCII (for compatibility with the MS client)
   * A "RDP picker" which lists .rdp files in ~/.tsclient/ and launches
     rdesktop from the rdp file when selected
.
tsclient also supports:
   * VNC clients (*vncviewer)
   * Citrix ICA client
   * X via Xnest
.
Author:   Erick Woods <erick@gnomepro.com>
Homepage: http://www.gnomepro.com/tsclient/