Jump to content


  • Content Count

  • Joined

  • Last visited


Community Reputation


About fungiscience

  • Rank
    LAVA groupie
  1. Hello, I want to distribute a LV 7.0 Express application for a customer. It uses a PCI-6036E card for Data Acquisition together with MAX on some computers and MAX 3.2 on others. All target computers uses Windows 2000. I need to install the customer application, together with LabVIEW Runtime, NI-DAQ (supporting Traditional DAQ), the PCI-6036E drivers and import Traditional DAQ virtual Channels in MAX. The customer want the installation to be automatic, so he would like a single installer wrapping all those functions. I looked at many tutorial and stuff on www.ni.com and tried some tricks, but doesn't seem to work well. The last installer I manage to build (with LabVIEW 7.1 Development Build Application and Shared Library) could : 1) Install the customer application 2) Install LabVIEW Run Time 3) Launch the NI-DAQ 7.4 installer (but the installer couldn't function : either I had a Windows error telling me that the installer couldn't load everything or either It started sucessfully, but the progress bar was coming back and forth, with no progression...but no particular failure) My last application build is attached to this message. I used a batch file to launch the NI-DAQ installer. I included all NI-DAQ 7.4 installer files in /drivers directory under the main installer directory. Is it possible to build a complete installer wrapping al of those function with LabVIEW 7.1. Can I define Traditional DAQ Virtual Channel with MAX 4.2 on my computer even if I don't have the proper hardware and export it to target computers with the real thing (MAX 3.0.2 or 3.2 with the real PCI device)! And can I export those channels automatically within the installer itself. Thank you, Sebastien Gelinas
  2. Hello, I'm trying to write one sample to one virtual channel programmatically with LabVIEW 8.2 in a task configured in MAX (DAQmx simulated device PXI-6225). This task contains 30 different outputs. I don't want necessarily to write all 30 outputs all the time. Is there a way to do that? I tried with the Task Property Node, with Channels property wired to the Task/virtual channel input of Start/Write/Stop DAQmx VIs, but I get invalid task/virtual channel error (see image 1). With DAQmx Read Property node, there is a property called Channels to read, which permits to read only certain channel in a task (see image 2). This property doesn't exist in the DAQmx Write Property node...is there is reason for this? Is there another to write only one specific channel in a task? Thank you!
  3. QUOTE(yen @ Feb 21 2007, 12:45 PM) Yes the DB is originally on another computer, but i copied the DBF file on the local computer. It<s not corrupted, I can open it with Microsoft Access. The connection is defined correctly as well! QUOTE(fungiscience @ Feb 21 2007, 01:30 PM) Yes the DB is originally on another computer, but i copied the DBF file on the local computer. It<s not corrupted, I can open it with Microsoft Access. The connection is defined correctly as well! Actually, it just seems to me that LabVIEW Database Connectivity Toolkit doesn't provide access to dBase DBF files. First, when you browse for database file, using the dialog prompt from the Open Connection VI, only Microsoft Access database files (.mdb) is defined in the dropdown list. Second, my database file is consistent and working : I can access it from Microsoft Access easily. And the Test connection button tells me : Unrecognised database format...which brings me to the conclusion that this file type isn't supported!
  4. Hello, I try to connect to a DBF File (a dBase file which is supposed to be supported by the LabVIEW Database Connectivity Toolkit) using the LabVIEW Database Connectivity Toolkit. I always get an error when I supply the Open Connection VI with the DSN, or the file path or when I configure manually the dialog with Microsoft JET 4.0 OLE DB Provider and the file path to the dbf file (The test connection doesn't work either). Here is the error from the dialog Test connection button : Test connection failed because of an error in initializing provider. Unrecognised database format Here is the error when a supply the file path in input : Error 1 occurred at DB Tools Open Connec (Path).vi->MEPR-Query Database-Get data.vi Possible reason(s): The file provided is not a data link (UDL) or a file DSN. Any tips?
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.