Similar Questions

• Why did the counter works in MAX, but not of Labview?

  Please help, I've been away from Labview for more than 3 months and I'm pretty rusty...

  Last year, I configured successfully NI9401 to measure the period (in seconds) by counting the rising edges of my sensor signal.  Since then, I bought a new PC and loaded all my software inside, including the Labview VI that has worked successfully on the old computer.

  I can see the digital signal using MAX and test for the NI9401 Panel, then, I know that my son and my TTL signal is OK, but nothing except the below error when I try to run the attached VI, happens...  How can I say this VI to search for the signal on channel 14 and MOD3/CTR0?

  Thank you. I'm sure it's a small adjustment... it worked well a few months ago... do not know what the problem is now.

  Thank you

  Dave

  OK, now.  Solved the problem. The vi is fine, but some fragile son have been identified... worked in MAX but not in vi.  Now that the connections have been tightened, it works for both.  Sorry for the inconvenience.

  Dave

• Reading to the MAX but not of LabVIEW

  Hello

  I have a very difficult problem to read four counters of a NI 9401. In MAX, they read very well but in LabVIEW, they read zero. I scoured the internet and discussion boards and can't find anything on it. Please forgive me if this is a simple thing to fix. IM attaching two png which shows where I read meters and a picture of my task. I know that the VI everything would work better but I'm not posting my project as a whole.  I fixed it where some of the forum posts I found said have it better. Any help would be great. If you need a certain thing just let me know.

  Kind regards

  caleb1993

  I create now these tasks in LV I always not to read. I hope someone has assured this problem in the past and resolved. If yiu have a better idea then by testing each port call please let me know

  Thank you

  caleb1993

• Camera works to the MAX, but not in LabVIEW

  I struggled a lot with getting a camera DCC3240M of Thorlabs working in LabVIEW. The software supplied (Thorcam) works as it should. However, the LabVIEW SDK does not work as it should, it gives an error 155 "the operation is not supported.

  Instead of the SDK software, I tried the drivers for DirectShow and now the camera arrives in MAX and works as it should. He also appears with IMAQdx list Cameras.vi and in Vision Acquisition Express vi. BUT when I try to run IMAQdx open Camera.vi or the Express vi it does not work. Open device gives a DirectShow error code 0 x 80040275 "no capture hardware is available, or the hardware is not responding." And when I try to select the camera in the express vi, a red icon is displayed and I can only choose "Cancel":

  

  It's really very annoying that the camera obviously work with the drivers provided, but I can't use it in LabVIEW.

  I would be grateful for any ideas what is wrong. I'm running LabVIEW 32 bit on 64 bit Win8.1.

  Problem solved!

  I carefully removed all the drivers that came with the camera and then I installed the drivers from manufacturers (IDS) instead of Thorlabs drivers. And now it works, the camera always appears in MAX and it does not work. But now the supplied screw. I'm so happy. It took me a week to understand.

• communication serial port works to the max, but not in labview

  Hello

  I am trying to connect a regulator to oxygen flow (flow Bronkhorst EL) to a laptop through a USB using MAX and Labview series port adapter. After the MAX aperture, I see my instrument on port COM5 and need to change the baud rate to 9600 to 38400. After this I querry the command: 06030101217D00\r\n, I can turn the mass flow at maximum power regulator (looks a little weird order because of the syntax of the instrument, but it works very well). If I write a vi to do the same and send the same string through visa series, I get no results, it seems that the command is not send to the device. I tried to change all settings for the serial port, nothing seems to work.

  I've attached an example vi here, any suggestions?

  Hello

  just a simple misunderstanding, happy that you added the code.

  In MAX \r\n will be always interpreted as send a cr and line break.

  In LabVIEW only when you select \codes view by right-clicking on the channel.

  In your situation, it now sends a-a r another- and a n

• FireWire camera works to the MAX, but not in LabView

  Hello

  I use a 1394b (grey Grasshopper Point 14S5M-C) camera connected to a 1394 bus controller. In MAX, the camera works fine, but it will not work with all files of 1394-example LabView. These allways throw the error "NOR-IMAQ IEEE-1394: (Hex 0xBFF6800F) attribute not supported by the camera" even if some of these example like "grab.vi" files no attributes are defined at all. On the same computer, another device (Point Grey Scorpion 20SOM, 1394 (a) works without any problem.

  Can anyone help?

  Hi Christian,

  Thanks for this tip, this is the reason. I was unintentionally using the IMAQ instead of example IMAQdx files. With IMAQdx it works now.

  Best regards

  Karl

• Unit works fine with MAx but not with Labview visa series

  I have a RPM sensor connected to tachometer Monarch monarch, it gives error while coding in labview and works very well in Max if the sensor does not read 0. I wrote RS-232 simple programs never had an error, but this one's errors... not ablt remedy... Help, please

  Hello

  I solved it by using bytes to the port if there is anything in the port, I read it otherwise, he simply says no playback.

• What should I do when I can communicate with my instrument NI MAX through other programs, but not of LabVIEW?

  Hi all, this is a question that I had a few times before in one form or another.

  I use a Boxcar Integrator (245 SRS is the interface) for my experience. I connect to it via GPIB using my Agilent GPIB/USB interface. My program runs in LabVIEW, and I used it successfully in the (very recent) past.

  However, sometimes if I get LabVIEW or something, some weird stuff starts past trying to connect to it. For example, after the LV exit and go back to the top and any attempt to run my program, it throws the error:

  Error 1073807339 has occurred in the CITATION read in OR_Boxcar_ReadAnalogPort3.vi-> OR_Boxcar_SimpleTest.vi
  
  Possible reasons:
  VISA: (Hex 0xBFFF0015) timeout expired before the operation is complete.

  Which essentially means that he cannot connect for some reason or another (don't worry, I'm on the right GPIB address).

  So I go to equivalent NI MAX or Agilent (Keysight connection Expert), proceed to part communication from VISA to either and manually, connect with the machine. And it works! If clear my computer is communicating with the machine at this point, but not of LabVIEW.

  This could be the cause, and what I might try? Thank you!

  Oh shit, I forgot about it! I solved the problem, it was actually a 'me' problem is not a problem of LV. Even my solution would not be to help someone else who finds it. I was trying to read from my instrument, but it is in synchronous mode, so it generates an error if you try to read her when a data point has not been loaded in its buffer. I did something unusual, so it was not a point of data loaded into its buffer.

• USB thermometer works in Hyperterminal & MAX, but not in my VI

  I have USB (Omega TJ - USB) thermometer.  I contacted with her success in Hyperterminal.  When I try with MAX, it usually starts working after the second attempt to read/write.  But even if I put the termchar 0xD and termchar_en to True, I still have to type my writing as 'C' back ' 20.2 c ' (20.2 C being the temperature) any idea why this happens?

  In addition, I go ahead and make my VI, very similar to that found in the labview tutorial - image shown here: http://zone.ni.com/cms/images/devzone/tut/a/e09bfd41228.gif I put it for baud: 38400, 8n1.  and I also write 'c', but I get the error 1073807339.  I tried to change the buffer without change in the results.

  I thought it would be a relatively simple task, but it seems that I am bad, or overlooking something simple.

  Hi Chknrckd,

  Also what could be the problem, is that the way hyperterminal sends characters (when you type words). LabVIEW will send a string at the same time, while that hyperterminal sends each character at a time.

  More information can be found here:

  Why Test panels MAX works my Instrument Serial in Hyperterminal but not in LabVIEW or VISA work?

  http://digital.NI.com/public.nsf/allkb/171D2D70CFB66E74862571390062D12B

  I hope this helps!

• Instrument to appear in MAX, but not in the executable file

  Hello

  I use two HP34401A make some measurements, and I transfer the program to a laptop with complete labview at your desktop with only the runtime engine.  Instruments made their appearance in the Office MAX, but when I run the executable, they cannot be detected.  I expect some suggestions on how to possibly resolve this problem.

  Thank you

  Not to mention that MAX, what other driver is installed and necessary? Did you install NI-VISA, NI GPIB? At a minimum, you should include NI-VISA in the installer that you built.

• Serial via NIMAX okay but not through LabView

  I'm trying to communicate with a device via the serial port.  In MAX, I have configured the port (28800, 8, N-2, RTS/CTS).  In the test Panel, I can send a request for identification (ID? \r) and get an answer.  If I try this through a LabView VI, where I open a session VISA, set the COM port settings, and then try the request ID, I don't get a response.

  I have also noticed that if I try the query ID in MAX, but use a USB-serial adapter, I get no response.

  I don't know I'm missing a few simple nuace serial communication.  Any thoughts?

  Thank you.

  In LabVIEW, my guess is that you do not correctly send the \r. To do this, you must have the control/constant string defined for '-' code display. If you had posted your code, it would have helped to see if this or something else is wrong. Have you tried one of the sample programs before you try to write your own?

  I've never had a problem with an USB-RS232 adapter. The new port is actually in MAX and you can use Hyperterminal with it?

• My integrated Webcam is recognized by MAX but not as the IMAQ device

  Hello

  I use with 2014 LabVIEW IMAQ 14 and IMAQdx14.

  I am able to use my webcame MAX both in the Vision Assistant, but when I am trying to generate vi, in the wizard, IEEE1394 Imaging is grayed out.

  When I am using triggered image acquisition and select cam0 as the name of the interface (name of my camera to the MAX), I get the error code:-1074397163 (NOR-IMAQ: the session or the interface passed is not valid.)

  In MAX, I can see and use my camera, but it appears directly in the devices and Interfaces (and not under devices NOR-IMAQ)

  I can't find out if it is compatible live show... Is this to say that my camera is not supported by IMAQ? Is there a way to check whether LabVIEW?

  Thank you

  Karol

  Hi Karol,

  Since you are able to use the camera in MAX, it is DirectShow compatible. The reason why you get this error, it is that your device is not compatible with the IMAQ driver. Instead, you should be using the driver IMAQdx and corresponding IMAQdx live. Once you use those, you should be able to control in LabVIEW. It isn't an IEEE 1394 device either, so I think that it is expected that all options for this would be grayed out. Hopefully that should get you going in the right direction, but please post again if you have problems with the generation of VI you.

  Thank you

  Katie

• PXI-6682 shows Max, but not in DAQmx

  Hello

  I recently received a new chassis with some rare cards and I am relatively new to everything related to NEITHER.

  In any case, I also had a new PC (because they asked me to start from scratch)

  So I installed the following:

  1. NOR-Daqmx 9.0
  2. NOR-Sync 3.1
  3. MAX 4.6.1f0

  Later, I plugged my chassis and got all my cards to register automatically... except for the PXI-6682.

  Subsequently, I've traveled to find the pilot who has worked and myself (in the Setup OR Sync). MAX is now able to test it, read it and all that.

  Now the problem is that I need to know my C program run-time if the device is there or not...

  To achieve this effect, I used this: DAQmxGetSysDevNames

  It returns all devices except the PXI-6682.

  I can "cheat death" using the name provided in MAX ("Dev11") and use my calls OR Sync in this way... but it's terribly static.

  Y at - it no probable cause why a DAQmx call would not have recognized a device?

  Tips:

  1. http://forums.NI.com/NI/board/message?board.ID=80&message.ID=1257 : does not really give a solution
  2. The pilot seems weird... "Device Manager" name is "NI PXI-6682" instead of "PXI-6682" ' "."
  3. If I call DAQmxGetDevProductCategory it returns DAQmx_Val_Unknown (so that he knew the unit is plugged... but he can't read it)
  4. My NO-Sync calls are able to control the PXI-6682 very well

  Thanks in advance for any help,

  Sébastien Dupéré

  Hello Sebastian,.

  The NI PXI-6682 does not appear as a NOR-DAQmx device because it is not controlled by the driver OR DAQmx.  Instead, all commands and communication are through the NO-SYNC driver.  The "DAQmxGetSysDevNames" NOR-DAQmx function returns only the names of devices that can be controlled by the DAQmx driver.  To and from this device function calls will go through NOR-SYNC.  I'm not too familiar with this driver (I work with DAQmx) but they may have a function to return the names of similar to the DAQmx devices.

  (Incidentally, in the forum post you linked, the aircraft was a DMM which is controlled by the driver OR DMM and the explanation above also applies for him.)

  Kind regards

• NEITHER USB-9162 driver works for MAX and SignalExpress, but not for LabView

  Hello

  I looked for a solution for a while now. According to Web sites OR the NI USB-9162 is compatible with LabView 2012. I installed the last DAQmx. My hardware has been detected and is sensitive to MAX and works very well in LabView Signal Express. But it is not detected in LabView 2012. I searched the forum and not found any solution other then all uninstallation and reinstallation of any. It is quite conssuming time and would rather avoid if possible. Anyone have a solution? I wish I could appreciate.

  Tool:

  NEITHER USB-9162

  NEITHER RIO-9215

  Benjamin

  I reinstalled everything, and now I can work with it. I can't say that I was wrong on the first time, but now it works very well as well as other bugs that are now set.

  Thank you for your answers

• Camera detected in MAX, but not found in Labview

  Hello

  I have a camera Thorlabs USB (DCC1645C). I installed the drivers and MAX detects the camera, but when I try to open the camera with NOR-IMAQdx, it does not appear. I also tried to open with NOR-IMAQ camera, but I could not.

  If I try with Vision Express/Vision acquisition, the camera appears, I am able to select and configure the principle of the camera, but when I execute the program there a mistake: 'not found room '.

  It would be great help.

  Thank you

  Hi AurelioSilva,

  In fact, NI-IMAQ driver is used only for materials. For the hardware part 3 (such as your USB camera), I recommend the use of iMAQdx. You can find the difference between the iMAQ and iMAQdx here: http://digital.ni.com/public.nsf/allkb/0564022DAFF513D2862579490057D42E

  Now, back to your problem. When you talk about LabVIEW 2013 (64-bit), I think that it is perhaps the issue. You see, most of the drivers like iMAQdx and iMAQ are supported by LabVIEW 2013 (32-bit) only. Don't worry, you can install and run 32-bit LabVIEW 2013 in your 64-bit computer OS cause I do this all the time with 3rd party cameras. In short, not all drivers of OR are supported on a 64-bit version of LabVIEW. You can read about it here: http://digital.ni.com/public.nsf/allkb/E9B4EA0143514DCB8625725D0050680A

  Warm greetings,

  Lennard.C