Physical channels node

Is there a way to get the IEPE or ICP power support and AC/DC coupling support information from a DAQmx Physical Channels Node.  If not can this be added to the next version of DAQmx? Some NI boards have different properties for different channels..  For example the NI 4432 has ICP power available for channels 0 through 3 but does not have ICP power for the last channel which is channe #4. 

Greetings ed Z!
I was able to programmatically obtain the information about the AC/DC coupling ability of various devices/channels but my efforts to do the same for IEPE support has failed.  If you're interested, my method was simply reading the AI.Excit.DCorAC DAQmx Channel property (found from Analog Input -> General Properties -> Signal Conditioning -> Excitation -> Advanced -> DC or AC) and then writing it back with two connected property nodes.  I then attached a case statement to the error wire running through the property nodes.  No error meant the feature was supported.  The error case handled if the feature wasn't supported.  
I know this is not an ideal setup and not exactly what you were really looking for.  As such, the best thing I can suggest is to head over to www.ni.com/ideas where you can submit this as a LabVIEW feature request.  
Hope this helps.
Michael G
Michael G.
Applications Engineer
National Instruments
Self-realization: I was thinking of the immortal words of Socrates, who said, "... I drank what?"

Similar Messages

  • How to get intimation about DAQmx Physical Channel invalid value encounter

    Can anybody tell me that if a DAQmx Control gets value from a configuration file( .ini file ) and the value is invalid (does not exist in the available physical channels list) than how I can be programatically intimated. I couldn't find any property node of DAQmx Physical channel Control which tells about that the current value feeded to the control is invalid.

    Thanks Alan, I have got a better soloution from you in another thread launched by me with title "How to get "Browse list of any DAQmx control in array form". In which u suggested of using DAQmx 8.0, which I have downloaded and used the property node DAQmx-Device>>DO.Lines to get an array of all Physical channels(DO category) of all devices. The value taken from that configuration file is searched in Physical channels array and if no match found than the value is invalid.

  • Filter the pull down menu of physical channels control

    Hello all,
    I need help, I'm desperate!
    I'm trying to create a software recording data from an accelerometer by using a NI USB-9234 device. So in order to do that, I linked a physical channels control to DAQmx create channel. The thing is, I want to display in the pull down menu, only the physical channels attached to the NI device specified above. And besides, I'd like this to be done automaticaly, meaning that no matter what is the name of the device (dev1, dev2, dev3...), the pull down menu will display the four physical channels attached to the specified device.
    Am I clear ?
    I know that by right-clicking on the physical channels control, I can filter it but I can't manage to figure it out how to filter by specifiying a device. Maybe by using property nodes...I don't know.
    If somebody has a solution, that would be much appreciated.
    Thanks a lot

    You can configure IO Name Filtering by choosing the following option in the context menu:
    But you cannot select a certain device type there, but only certain device names (which is a huge difference).
    So the easiest way to accomplish your task is to define a name for your USB-9234 (like MyDevice) and then limit the selection to "MyDevice".
    You have to make sure, that each PC using the application as aware of "MyDevice". This setting is done in MAX (Measurement and Automation Explorer) and can be distributed with your application using the Application Builder (or manual export/import within MAX).
    hope this helps,
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Mapping of line/port (Physical Channel constant) to pfi (Terminal Constant)

    Hello all,
    I am using "Dev1/port0/line4" (Physical channel constant) of my PXI-6602 as a digital input.
    Additionally I have set up a counter on that board. I need to arm this counter after the occurrence of an edge on
    "Dev1/port0/line4". But the property node only accepts "Dev1/PFIx" (Terminal Constants) as inputs.
    I try to avoid defining two constants within my program that practically map to the same physical pin.
    What is the best way of converting a "Physical channel" name to a "Terminal Name" ?
    Grüße
    Phili

    Having faced the same problem, I think I can say why there is no mapping.
    Channels are for data aquistion, so actually a DAC, ADC, DO-Driver ...
    Terminals are used for timing (trigger) and internally routed. So a diffrent concept, and a diffrent circuit.
    Actually the same goes if you use analog triggering, you will have a different ADC (I found out because I got only 10-bit on a 18-bit M Series Device).
    Felix
    www.aescusoft.de
    My latest community nugget on producer/consumer design
    My current blog: A journey through uml

  • Extract device from physical channel

    As always I want to do something absolutely trivial and am running into all sorts of issues
    I define (through a control) a physical channel that I want to take data on. I want to be able to programmatically reset the device the channel is on. i.e. i don't want someone to have to open up the code and change the device on the reset vi if necessary. Even if there is only one device physically connected, you can’t guarantee the device will be Dev1, because Labview keeps a history of devices that have been plugged in. The obvious solution – extract the device name from the physical channel control which contains the channel(s) you have selcted. Can I find a trivial way to do it, NO!  There is a property node called device but it does not (despite its name) return the device you have selected along with the physical channel.  There are convoluted ways of doing this, but i'm hoping there is some easy way. Suggestions
    Solved!
    Go to Solution.

    I think this might be the "trivial" way you're looking for: some string pattern matching and a simple
    regular expression to extract the device name prefix from a physical channel name.
    -Kevin P

  • PXI has no physical channels!!​! Please help!!!

    Hello.
    While using DAQ Assistant, when the window of selecting a physical channel appears, no physical channels appear. I try to use NI-5122 and I think everything is well configured in MAX (PXI-1002, External PC, MXI-3).
    Why doesn´t appear any physical channel???
    Is PXI-5122 supported by NI-DAQmx???
    I also have installed a PCI-5102, but as it works with Traditional NI-DAQ it shouldn't appear, should it??

    Hi Shawnyap, I have no clue what version of LabVIEW you have, so I'll send my 7.1 example.
    However, if your examples are corrupted, I'm going to highly recommend you upgrading to the latest driver at the link below and using the examples that come there.  If those are corrupted, there's a good chance something else is broken too.
    http://digital.ni.com/softlib.nsf/webcategories/85​256410006C055586256BE600709528?opendocument&node=1​...
    That link doesn't support LabVIEW 8 at the time of posting (NI-SCOPE 2.9.1) - let me know if you have LabVIEW 8 and I'll get you going.
    mike
    Attachments:
    niScope EX Configured Acquisition.vi ‏208 KB

  • How to create multiple physical channels using DAQmx?

    Hi, I am new to Labview.
    Can anyone please help me on how to create multiple physical channels? I am following the LabVIEW examples in the NI example finder but they are only for acquiring signals from one channel.
    Actually, I am using the channels of an SCXI 1520 to measure voltage signals. And one more thing, in the NI Example Finder, they are sample codes there for setting the filter in SCXI 114x.
    Will this example work with an SCXI 1520, too?
    Thanks!

    There are many ways to read multiple channels in LabVIEW. First, if you look at that example that lets you set the filter setting on the 114x and you click on the 'Physical Channel Listbox' then click 'Browse' you can see that you can select multiple channels. After you select the channels and hit 'Ok' it will build a multiple channel string. This is one way to read multiple channels.
    Next, you can create a 'Task' in Measurement and Automation Explorer(MAX). When you create this task select all the channels that you need to read then back in LabVIEW simply select a 'DAQmx Task Name Constant' Select the task you just created and wire that to an Input of your first DAQ VI. If you do this you do not need to have a 'DAQmx Create Physical Channel' VI or create
    Task because it is already created in MAX.
    When looking at example VIs you can tell if a multi-channel read is acceptable by looking at the 'DAQmx Read' and if it says NChan that means it will do a multichannel read. There are tons of example programs that will display the multichannel read capabilities.
    This example may not work for the 1520 because the properties that are set could possibly be specific to the 142x. When using the 1520 though it is very likely that the properties will be very similar if not exact. You will simply put a DAQmx Channel property node on your block diagram and then look for the Lowpass filter settings properties that will most likely be in the same location. Now another way todo this without using a property node would be in MAX when you create a task set the filter settings from the Device tab in the task configure window.
    Let me know if you need anymore help with reguards to this issue! Have a great day!
    Allan S.
    National Instrument
    s
    Applications Engineering

  • Discovering number of physical channels

    When setting up a DAQmx device in LabVIEW code, is there a simple way to discover and report the number of physical channels that have been selected?  I have looked for Property Nodes to do this using the "Physical Channels" control as well as the "task out" indicator, but I haven't found anything so far.  Any help would be greatly appreciated.
    Solved!
    Go to Solution.

    Found it!
    Measurement I/O -> NI-DAQmx -> Advanced -> Task Confi... -> Task Node -> NumChans (Number of Channels)

  • Physical channel choice .exe

    Hello,
    I have built a .exe (and it's setup) for a data acquisition system. My problem is that depending on the computer it is installed, the physicall channel to read may change (not the ai, but the Device number; that is, Dev1/ai7 to Dev2/ai7, depending if there are any previous devices installed).
    I want the user to be able to select the Physical channel, but, my problems come here: I cannot make the program 'wait' for the user to set the channel before starting the acquisition (it takes the default value, and gives an error since it won't match).
    I have tried looping the whole program and using a case structure so that when the physical channel is selected then the user should press a button to start the acquisition, but then I get an error (sorry can't rememeber the code), saying something like 'Attemped to read samples that are no longer available... try increasing fs...'.
    Any help?

    Hi usuario, 
    The other way of doing this is...
    - you need min 1 spare terminal on your device
    1) Scan your system for all H/W of type x (Product Type)
    2) Scan specified lines on all devices you have just filtered out - get line status
    3) Ensure that the H/W pull the input of the specified device up (out of default state) on selected channel.
    You can now detect which if the device is attached, and programatically determine it's name - very difficult to simulate though.
    Using boolean logic you can add more lines for more devices
    1 line = 1 devices
    2 lines = 3 devices
    3 lines = 7 devices
    etc...
    Try coding up Phil's example and see what it does when you add new devices - simulated or real. You'll learn lots and see it's not that complicated really.
    James
    P.S. - You have a race condition in your code between the input and the property node, just wire the output of the physical channel straight into the string stuff. You could do it simpler as well, like this:
    Edit: -correct spelling of a name
    Message Edited by James W on 05-20-2010 10:33 AM

  • DAQmx physical channel to string

    Hi Labview forum,
    I have a variable DAQmx physical channel variable.
    I would like to write the physical channel used to a file.
    Is there a way to convert the physical channel selected to a string for writing to file?
    Or to access a property node which stores the channel name in string format?
    Regards,
    Jamie
    Using Labview version 8.0

    LabVIEW1234 wrote:
    I am not sure how to use "Scan from String" for these unique data types. Where can I find the format codes for physical channels and enums. I guess ENUM is U32 or something like that but I have no idea what a physical channel is.
    You have to use the Scan From String to convert your string to the enum.  But as Dennis said, just wire your string straight into the Physical Channel input.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    String to Enum.png ‏11 KB

  • MAX: how to create a Calculated Channel based on two physical channels?

    Good morning,
    I need to configure some tasks in MAX with Virtual Channels that are calculations based on physical channels. I saw this article : http://digital.ni.com/public.nsf/allkb/1BFCE6FAD5B3944986256D67006DF7EC but cannot see the equivalent in the newest versions of MAX (V5.1).
    As an example I am already acquiring the physical channels Ch1 and Ch2 and I want to build a virtual channel Ch3=E+(A.Ch1+B)/(C.Ch2+D). A,B,C,D,E are constant values. I would then like to integrate Ch3 in a task together with other physical channels that I am acquiring.
    Could you direct me to this function?
    Thanks for your answer.
    Christophe

    Hello Christophe,
    With the newer versions of NI DAQmx and NI MAX there was a choice made to go from the relatively limited VI Logger options to a more extensive form of configurable applications.
    For this purpose (and others) NI Signal Express was created, which allows you to configure applications with a limited amount of programming.
    To do similar (and more things) then you were used to do with VI Logger you can use NI SignalExpress
    http://www.ni.com/white-paper/5825/en/
    http://www.ni.com/white-paper/5827/en/
    This specific VI logger functionality for the creation of ""virtual channels" (step 5 to 10) through VI Logger Tasks (directly from inside NI MAX) however does no longer exist.
    This also more clearly seperates your Configuration Tools (like NI MAX) from your actual applications made with LabVIEW or SignalExpress.
    Would using NI SignalExpress be an option for you?
    Kind Regards,
    Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
    CLD, CTA
    If someone helped you, let them know. Mark as solved and/or give a kudo.

  • Why can't I get a Physical Channel to show up?

    I have a USB-6008 and LabVIEW 7.0. When I try and use the provided examples I can't seem to change the Physical Channel. When I click on the drop down menu I get the Browse... option. Then when I click on Browse... I get a blank window. It looks like there should be some sort of a menu but there isn't.

    Check out this KB.
    -Alan A.

  • Problem with DAQmx Physical Channel control

    Dear LabVIEW community!
    I have installed LabVIEW, v13.0f02, 32-bit on my PC. The problem, which I face, is that DAQmx Physical Channel controls, which are used in VIs inside the LV projects, sometimes don't show me the list of DAQ devices - I can't expand the list at all. I push the button to expand the list, but nothing helps.
    But when I create VIs outside the project, and put there DAQmx Physical Channel control - everything works well.
    Note: devices are simulated via MAX.
    Is it some kind of bug in 2013 vesrion of LabVIEW? Because while using LV 2012 I didn't have such headache.
    The only thing that helps now - is to restart PC (laptop) several times; b/c restart of LV doesn't help.
    Can anyone suggest, what it can be, and how to fix this problem?
    Thank you very much in advance!

    Thank you for your answer!
    The point is, that this bug is independent from the code. DAQmx Physical Channel controls don't work even when I'm trying to use NI examples - for instance, Strain - Continuous Input.vi; Voltage - Continuous Input.vi, etc.
    I have such simulated via MAX devices: NI USB-9213, NI USB-9201, NI cDAQ-9172 with NI 9217, and 4 NI PXIe-4331 modules.
    Also, what I have noticed - front panel doesn't visualized fully (I send you the screenshot). When I'm moving mouse pointer over it, those part, which were under the mouse pointer, became clearly seen. And when I minimize, and then restor FP, it becomes fully clear visible.
    And also, this story happens when LV project is open. If I close opened projects, and open only single VIs, everything works smooth.
    Thank you very much, I hope, that this information will be useful to solve this problem.
    Attachments:
    Screen 1.PNG ‏87 KB
    Screen 2.PNG ‏107 KB
    Screen 3.PNG ‏129 KB

  • Save physical channel information in a configuration file and reuse it in another VI

    Dear all,
    I would like to do a pair of VIs. The first VI configures all psychical channels and store the task information (or physical channel name information) in a file and the second VIs can access this file and use the saved information.
    Can anybody show me a good example of this type of application? I've prepare a simple code, but it does not work now. I am not sure if I am using the right functions.
    Attachments:
    Configuration.vi ‏18 KB

    You can use Measurement I/O>>NI-DAQmx>>Advanced>>DAQmx Utilities>>DAQmx Flatten Channel String, and DAQmx Unflatten Channel String.

  • Deploying VIs to the RT causes the value in the Physical Channels of one of the VIs to change to an incorrect value. Why?

    Hi all.  I've been registered to the forum for a couple of years, but this my first post.  I'll try to give as much info as I can.
    NIPXIe-1082 chassis
    slot 1: PXIe-8133 Embedded Controller
    slot 2-3: PXIe-6363 X-Series Multifunction DAQ
    slot 4: TB-4353 32-Ch. Thermocouple
    slot 5: PXI-4496 Analog Inputs 16-ch
    (The second 6363 in slot 3 is a recent addition causing the others to move to higher slot numbers.)
    Windows 7
    LabVIEW 2011
    This code is still being developed to run a test stand, but its based on code from a previous test stand that is being modified for the new one.  There are three VIs that are opened and then deployed to the RT.  On the Front Panel of one of the VIs is a DAQmx Physical Channel control.  The control points to slot 5, but when I deploy the VIs, the control changes to point to slot 3.  None of the three VIs have been run yet.  I can manually "Reinitialize to Default Value" to get the control to point to slot 5 again, but I shouldn't have to.
    I realize that there is a lot I still don't know about NI hardware and LabVIEW.  This just seems like it should be a really simple solution and I'll probably have one of those DUH moments when I get told the answer.  I'll try to answer whatever questions for more information that I can.  Thanks in advance.
    -Psiber_Space

    Yes, it is defaulted to slot 5.  After it changes I can Reinitialize to Default to bring it back.
    Two things that I've tried during the week.  I've deleted the Physical Channel and then recreated it, but it continued to change upon deployment.  Then I simply disconnected the Physical Channel, moved it to an out-of-the-way location on the Block Diagram and then created a new Physical Channel.  The old Physical Channel is still changing upon deployment, but the new one stays intact.  It seems that as long as the old one isn't deleted, this workaround should work.  Except that the problem now seems to be spreading to the other controls on the same VI.
    Just today I upgraded from 2011 to 2011 SP1, but the problem is still there.  After the upgrade, I tried recreating the LabVIEW project from scratch, but that didn't seem to work either.
    I'm going to try contacting NI directly, but if anyone else has any ideas, feel free to continue posting.

Maybe you are looking for