Compatible with labview thermostat

Goodmorning,

I'm looking for a thermostat (a device that can measure temperature and humidity) compatible with labview and if possible with a USB connector.

You never heard / use such a device? I did some research but I can't find it.

Thank you in advance.

Thank you! I found another that looks better, but thank you! (Your temperature is smaller)

Tags: NI Hardware

Similar Questions

  • Not compatible with Labview 2014 IMAQ?

    I try to work with a National Instruments / SuperDroid Robots SD6 ( https://decibel.ni.com/content/docs/DOC-18528 ) now... Everyting connects fine using LabVIEW 2014 with the module of Robotics with the exception of the functionality of the camera. When you use the solutions provided LabVIEW cannot find dependencies IMAQ.

    I checked to make sure that I have the module installed and I see IMAQ 4.9 and IMAQdx 4.3.5 MAX

    Check the newsletter below on the compatibility of the IMAQ, she only has not 2014 listed

    http://digital.NI.com/public.nsf/allkb/DB928F6D5E9D6B97862579A7006B2850

    Specifically, I need the 2014 Image processing module version in the link below. The download link says 2013 and during the installation process, I don't see an option for support for 2014.

    http://www.NI.com/gate/GB/GB_EVALTLKTSIGPROC/us

    Is there a trial version of this software that is compatible with LabVIEW 2014?

    I was able to get in touch with a sales engineer and I need to image processing module is not yet available for LabVIEW 2014. Where my question.

  • The Keithley 2612 is compatible with Labview 7.1?

    Hello

    I have a shiny new Keithley 2612 A two-channel sourcemeter and want to begin using this system of our laboratory.  We are currently using LabView 7.1.

    I found a driver for the 2612 has, but he says that it is only compatible with LabView 8 or later:

    http://www.Keithley.com/base_download?dassetid=51950

    Does anyone know of another driver, or another method that I could get this thing working in LabView 7.1?

    Thank you very much

    John

    Download and publish it on the thread Downconvert .

    Edit - this is a style of project pilot who introduced with LabVIEW 8. It might take a little longer.

  • Sorensen XEL power is compatible with labview

    What Sorensen XEL power compatible with labview? I'm in the automotive field of vehicle dashboard. I want to test and simulate different transient conditions that may generate noise in the pipe I needed of a programmable power supply. Currently I have a NIcompactRIO configuration. I needed voltage output cards higher simulation and test requirements and special conditions.

    I was told that the Sorensen XEL series is compatible with Labview. Is this fair? The other question I have is NIcompactRIO uses IP Ethernet, but Sorensen communication RS 232 communication. Can I have some possible parallel communication with Labview frontend Protocol, controlling all the two from the same unique computer.

    Third, what are the function blocks required in the VI for Sorensen.And programming last but least, where can I get a drivers Sorensen RS 232?

    Nothing in this VI with Ethernet communication so I don't understand what you're asking.

    Rather than add a \r\n with each entry, I recommend you set up VISA to automatically add and I would also recommend that you enable the character to stop playing as well. Then, there was no need for the VISA to the Serial Port bytes and these expectations. Look at the example of advanced series to learn how to set the VISA property to add a termination character.

  • CRIO-9073 is compatible with LabVIEW 8.5.1?

    I just got a cRIO-9073 and a cRIO-9074.

    When I set up, both of them appear correctly in MAX.

    When I add them to a project LabVIEW, the cRIO-9073 does not show the target FPGA. The cRIO-9074 shows.

    I'm using LabVIEW 8.5.1, is compatible with the cRIO-9073?

    Thanks for any help.

    Michel

    Hi Michel!

    According to this link, the interface FPGA and Scan of the cRIO 9073 are only supported in LV 8.6 using the NOR-RIO 3.0 driver.

    The link where you can check the compatibility is:

    FTP://FTP.NI.com/pub/DevZone/tut/crio_software_versions.htm

    Good day!

    Oswald Branford

  • Is DAQ Measurement Computing USB - 1608FS compatible with labview?

    I have DAQ USB-1608FS from Measurement Computing company, and I was trying to see if it is possible to use

    This data acquisition with labview 2012. I tried to download the drivers from their company http://www.mccdaq.com/usb-data-acquisition/USB-1608FS.aspx

    but when I tried to use labview in the DAQmx the DAQ tool is not detect it by LabView. So, if anybody out there knows if this data acquisition

    really can work with labview, please let me know.

    Their driver seems to be ULx http://www.mccdaq.com/daq-software/universal-library-extensions-lv.aspx

    and he said that he supports LabVIEW 2012. I suppose you open a sample and the device does not appear? The device is displayed in the Windows Device Manager? It seems that this driver/device will work, there may be just a few questions it initialize properly on your machine (either with Windows or Measurement Computing software). You must be to open a debate on their forums or call their support help line.

    Good luck! Let us know some of the above and, of course, let us know if find you the solution.

    -gavin

  • suggestion for soil moisture sensors that compatible with NI Labview?

    any suggestion for soil moisture sensors that compatible with NI Labview? Help me ~ ~!

    Fauzan says:

    any suggestion for soil moisture sensors that compatible with NI Labview? Help me ~ ~!

    Let me address your concerns about "compatible with NI LabVIEW" by asking you a question. Which soil moisture sensors are compatible with C++? Visual Basic? Visual C? JAVA?

    The sensors have a layer connection between himself and the computer. Sometimes, the sensor itself is directly connected to the computer via USB. Most of the time, there is a layer of connection which will interface to the computer - USB, RS-232, GPIB, PCI - and linking the layer is an acquisition of data, or simplified for your application, an analog input Module. It is up to you to set your software to interface with these devices.

    Now, I don't want to insult your intelligence. I bet you already know such things. But your question reads as if you have the same false ideas about LabVIEW with many people. That, LabVIEW is somehow a direct interface with the hardware, and you just bought sensors and LabVIEW magically presents the data. No matter what some people well planned would have you believe, this is not the case.

    OK, so take for example this soil moisture probe. It displays 0 to 3 volts and costs $30. So now we need a way to measure the voltage and send blood pressure data to a computer. We use USB. This thing right here will do the job and then some, for only $50, and is compatible with LabVIEW. My point is - LabVIEW is compatible with the device that ultimately connects to the computer - the sensor is simply a device of voltage output.

    I am not affiliated with or endorse I receommend or two devices, I've linked to, they were simply the result of a 10 second google search.

  • upgrade to labview 2013 problems now with labview 8.6

    Upgrade to Labview 2013 a few days ago and framework installation changed my MAX existing since version 5.1 to version 5.5 with CAN 2.7.5.

    Because all my previous software was written in version 8.6 and customer requirements, this can not be changed and if I need 'backward compatibility '.

    However check the supported versions in CAN it only seems to go back as far as Labview version 10.0?

    Worse still, when I try and load any program written in LabVIEW 8.6 8.6 I now get "cannot find file" for the DAQMX as

    DAQMX------Write.llb------DAQMX------Write.vi etc.

    Tried the navigation in the folder named "MAX."

    The questions are:

    What I have to remove and MAX and re - install the earler versions for compatibility with 8.6?

    If so this can be done without removing my 8.6 install/2013 installs?

    Yes, the new DAQmx versions are not compatible with LabVIEW 8.X.  You can just uninstall DAQmx and then install your previous version to restore your support 8.6, but you will have lost the support of DAQmx for 2013.

  • Is the DAQ Assistant compatible with LabView7?

    I am equipped with a LabView7 and a NI DAQ - 6015 Pad and am trying to monitor the temperature with two thermocouples. I searched some tutorials online, but most suggest using assistant DAQ, which is not listed in the section of my functions palette entry. I have downloaded the NOR-most recent DAQmx driver who is supposed to be compatible with LabView 7.x. I don't know if this means that it is compatible with LabView 7.0. I still do not see the DAQ assistant appear.

    Any help or suggestion (about DAQ assistant or how to program in LabView7 to solve my problem) is greatly appreciated!

    Thank you.

    It looks like the DAQmx latest version is 8.1 which will work with LV 7.0

    See here http://digital.ni.com/public.nsf/allkb/97D574BB1D1EEC918625708100596848

  • I need assistance with LabVIEW RT and dll

    Hello!

    I'm new to LabVIEW but I am facing something very difficult.

    I develop with LabVIEW 2012 on a cRIO-9082, and I would use a specific DLL in a VI. The DLL is called TcAdsDll.dll and it is used to communicate with a PLC. (This DLL is provided by Beckhoff, for more information: http://infosys.beckhoff.com/index_en.htm TwinCAT > TwinCAT system > TwinCAT connectivity > TwinCAT ADS).

    When I use the 'library of the call' function with the DLL, I get an error 7. I'm just trying to call a simple function of the DLL.

    I know that in LabVIEW RT (Pharlab) only certain DLLs are supported. I also checked the DLL with the tool of NEITHER, but after the 10th dependend DLL calling it just hangs.

    If someone is able to provide assistance, I would be very grateful!

    Does anyone know, what are the rules for the dll must be met to use in LabVIEW RT?

    Thanks in advance!

    A DLL must call only Win32 API supported by the Pharlap ETS system in question in the first place. Since NO guard updated the ETS with almost every new version of LabVIEW it depends actually. DLL checking tool is the only way I know to check this. If this DLL checking failures, or as in your case tool breaks down, the DLL is not justifiable on the RT system. The Beckhoff ADS DLL is a complex beast with many dependencies on any other DLLs Beckhoff and what else, and as such a bad candidate to run on NI RT systems.

    In addition to this fundamental questions, you have additional problems with the Microsoft c runtime library in his infinite wisdom, has decided to create a new C runtime library version with each new version of Visual C. It is already a problem for a developer when deploying to standard PC Windows, but gets a problem almost unmanagabel when targeting something as Pharlap ETS. NEITHER seems to have paid the MS C runtime for their version of the toolchain Visual C of choice for LabVIEW RT system, but this isn't an option for you. If the 3rd party DLL to be used has been compiled in a version of Visual different C that ANYTHING used for the RT version you want to use, then you almost certainly run into trouble, unless the DLL was created with Visual C 6.0 (now a very old version)!

    I've created in the past as a VI based entirely the LabVIEW ADS communication library. It is a tedious job to know the actual byte stream protocol. Unfortunately it is not something that I can share with the community.

    Your best bet would probably be to use the cRIO Ethercat solution and go with an Ethercat on your PLC interface. EtherCAT is sort of a superset of the ADS interface.

    Maybe you can also talk with these guys here. They have a few ADS LabVIEW library and Ethercat libraries too. Not sure if they are basic DLLS and if they would be compatible with LabVIEW RT well.

  • IMAQ PCI-1424 compatibility with Labview 8.6

    Hi, the computer that I used for image analysis had a broken motherboard issue, and I replaced it with a new one. I removed both the drives and the jury from the old computer to the new and then installed IMAQ Labview 8.6, but Labview 8.6 is not compatible with the software programmed with labview 5.0, so I uninstalled Labview 8.6 and re-installed Labview 6.0 image processing. I still have some problems to run the Analyzer software and image processing. After you have uninstalled the software or labview, the computer does not start correctly, poping up error as information "check your hard drive to ensure that it is properly configured and completed. Run CHKDSK /F to check for hard drive corruption, and then restart your computer."

    Some basic information on this computer and the image acquisition system (introduced in 2000) are as follows:

    • Windows 2000 operating system;
    • LabVIEW 5.0 basic package;
    • IMAQ vision for Labview advanced;
    • IMAQ PCI-1408, Cables IMAQ-BNC-1 and or-IMAQ for Windows NT / 95;
    • IMAQ-A2504-1 (1 m).
    • Sony XC - 55 1/3 "Interline transfer progressive scan CCD, 659 (H) X 494 (V), C-mount with JB - 77, SERVICES-12 p-02 and DKT503M;
    • Computar H1212FI 1/2 "mount C 12 mm w/focus and iris (10 inches FOV at 24 work dist.);
    • Extension tube Kit Computar VM100;
    • GRAFTEK high frequency fluorescent light 11 ";

    -What hardware IMAQ I use compatible with Labview 6.0 or 8.6? Should I install also drivers for the hardware of the IMAQ when I remove the card IMAQ? All the solutions for my problems? Thank you very much in advance!

    Hi simpra,.

    Here are two links to articles that list compatibility between Windows & LabVIEW and LabVIEW and IMAQ.   Why do you say that the image processign software was not compatible with the LV 8.6?  A message appear?  Or it simply did not work?  Also, are you talking about Module Vision Development, by chance?

    I'm afraid that I can't help hard drive corruption, if that's the case here.  Have you been able to go beyond that?

    My suggestion is to upgrade to the latest version possible.

    I hope this helps!

    Kristen H.

  • With the help of USB-6009 with LabView 8.0

    I try to use a USB-6009 with LabView 8.0 box.  I DAQmx 8.8 (that came with the unit) installed and verified that the 6009 works correctly through MAX I also read on this site that the 6009 is compatible with LabView 7 or more.  However, I am unable to get LabView to recognize the device.  Using LabView, to use a DAQ hardware I have to select "Input" in the palette 'Functions'  But there is no range "Input".  Actually I can't find the DAQ Assistant Express VI anywhere.

    Do I need to use a different version of the DAQmx?  If so, which and where can I find it?

    Thank you.

    LabVIEW 8.0 is not supported with DAQmx 8.8. I think that the last version with support for 8.0 is DAQmx 8.6.1. You can uninstall 8.8 and install 8.6.1. You should really consider upgrading your version of LabVIEW. NOR has decided to limit support for 7.1 8.0 just now. The latest version of DAQmx manages to only 8.2.x and higher.

  • LabVIEW 8.6 compatible with current products of National Instrument

    Based on the above title, I'm currently have software LabView version 8.6. If I choose not to upgrade to the current version, the software will always be compatible with all National Instruments products? I'm hoping to create a centralized thereby logging of data center.

    Thank you

    Hi chywn, that specific products OR do you use? Here are some links on the website to OR who can answer your question:

    Which are compatible with the Versions of LabVIEW with that OR drivers?

    NOR-DAQ and LabVIEW (for Windows) version compatibility

    Module LabVIEW and Toolkit compatibility information

  • NOR-RIO 4.0 is not compatible with 64-bit LabVIEW?

    Hello

    I have a 7841R multifunction RIO card.  I currently install the evaluation version of LabVIEW to test.  I've got 64-bit LabVIEW installed successfully and I had installed NOR-RIO 3.6 (which was on the disc that came with the card).  Trying to install other features (I think C to FPGA interface or something), I discovered that I needed NOR-RIO 4.0.  I uninstalled OR RIO 3.6, downloaded OR RIO 4.0 and now I try to install it.  I get the message a few steps in the process:

    Important note about NOR-RIO of LabVIEW support (64-bit Versions)
    A 64-bit version of LabVIEW has been detected on your system.  This version of the driver NOR-RIO support the 64-bit versions of LabVIEW.  However, this version of NOR-RIO is fully compatible with the 32-bit versions of LabVIEW installed on 64-bit operating systems.

    Is there a NEITHER-RIO 4.0 version that supports the 64-bit versions of LabVIEW?  If so, could you point me to it?

    Or do I have to install the 32-bit version of LabVIEW?

    Thanks for the help!

    See you soon,.

    Tom

    Hey Tom,

    Unfortunately, we do not have a RIO driver that is compatible with our 64-bit LabVIEW Development software.  If you need to use the RIO driver, you must install the 32-bit version of LabVIEW and build your applications in the development system.  Sorry for the confusion at the start during the installation process!

  • VeriStand 2015 will not deploy with Labview created model: error-307703

    I try to use a model of labview to resume a few calculated channels that are currently in one of my projects veristand. Without the LV model, it works fine. But after you import the model and connection of all inputs and outputs, he used to "deploy. Gives the error-307703 during the deployment. More information in the log below.

    I use Veristand 2015 and LabView 2015 also. I put the inputs and outputs correctly in the connector pane, and when you import the model into Veristand, the inputs and outputs appear correctly. "" When I use the "Tools" NI VeriStand "generate NI VeriStand model of VI ' there is no errors and it creates a LVmodel that I can import into veristand.

    Are there steps that I missed? Or troubleshooting tips for tweaking my design to accept a LVmodel?

    * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
    VeriStand gateway has encountered an error while deploying the system definition file.

    Details:
    307703 error occurred at Window.lvlib projectWindow.vi project > Project Window.lvlib:Command Loop.vi > NI_VS Workspace ExecutionAPI.lvlib: NI VeriStand - connect to System.vi

    Possible reasons:

    NEITHER VeriStand: The specified model is not compatible with NI VeriStand. If you try to deploy the model to an RT target, launch the Console Viewer tool to view the output of the console of the target, which includes information about the source of the error.
    =========================
    NEITHER VeriStand: .vi Wrapper (RT) of the NI VeriStand Engine.lvlib:VeriStand engine > Engine.vi Engine.lvlib:VeriStand NI VeriStand > NI VeriStand Engine.lvlib:VeriStand state motor Machine.vi > model model Execution.lvlib:Initialize loop Data.vi > SIT model API.lvlib:Initialize Model.vi
    =========================
    NEITHER VeriStand: Initialization error Code 1


Maybe you are looking for