Configuring individual channels on the PXI-4472B

Hi, I am using the PXI-4472B card to acquire vibration data using transducers with different frequency ranges. The problem I am having is that some of the transducers require being powered from the board (via IEPE) and some don't and I cannot find a way to turn the excitation on and off for individual channels, only all of them.
I am using LabVIEW 8.6 and have configured all the channels using the property nodes to enable the excitation and specify the current, but not all the channels require this.
It clearly states in the data sheet for the 4472 card that the channels are individually configurable for the IEPE, can someone please tell me how to do this?
Thanks in advance,
Darren.
Solved!
Go to Solution.

Hello Darren,
Thank you so much for your post on our webforum. I don't have this device on hand (at this moment), but did a test with a simulated device, and this worked well. I created two channels within one task; so use two create channel.vi after each other with their own channel properties. The task out and in are connected to each other, so they have the same task reference.
PLease find a picture of the test I did, based on example \Programs\examples\DAQmx\Analog In\Measure Sound Pressure.llb\Cont Acq Snd Pressure Samples-Int Clk.vi
Please let me know if you have any further questions,
best regards,
Martijn S
Applications Engineer
NI Netherlands
Attachments:
example4472.jpg ‏151 KB

Similar Messages

I would like to configure physical channel in the following VI

i would like to configure Physical channel in the fillowing Vi. when i set 0 as physical channel input i get error 200170(physical channel specified does not exist on thi device. I am using board AT-MIO-16XE-50 for signal generation. if i use other conventional DAQ Ao config, there i can set channel 0 as input. why not here? please explain? i attached my VI. thanks
Attachments:
041015_simple.vi ‏41 KB

The AT-MIO-16XE-50 is not supported with DAQmx. (The PCI version of the card is, but not the AT version.) The AT card is supported with Traditional DAQ however. This is why you got the error using the DAQmx VIs but not with the traditional daq VIs.

What is best way of configuring the channels for the PXI box

Hi,
All these days I was using a SC-2345 box and a PCMCIA card and I created all my virtual channels as traditional NI-DAQ channels. Now I am using the PXI box, I am wondering whether I still use same traditional NI-DAQ channels or shall I use NI-DAQmx channels. I would like to know what are the advantages of using the NI-DAQmx channels and also using the DAQmx VI's in the labview programming.
Thanks,
Mudda.

Hi Mudda,
I think it depends on what PXI measurement modules you are using. I'm using PXI4461 for audio measurement and the card supports DAQmx only. I also have PXI5112 digitizer card and it uses the NI-Scope driver. So you need to check which driver your module supports.
You can find advantage of DAQmx here. http://zone.ni.com/devzone/conceptd.nsf/webmain/B1C2A3BC3228AEA186256D2500640D52?opendocument
Bill

Why do I get an error when I try to configure a channel with the tktds7x4 driver?

I use the TDS754D scope. My complete function call is:
errStatus = tktds7x4_ConfigureChannel( ScopeHandle, "CH1", 5.0, 2.0, TKTDS7X4_VAL_DC, 1.0, VI_TRUE);
When I step through it, I see that I get an error on the driver line
viCheckParm(Ivi_SetAttributeReal64 (vi, channel, TKTDS7X4_ATTR_VERTICAL_RANGE, 0, range), 3, "Range");
I'm also getting an error with tktds7x4_ConfigureEdgeTriggerSource
I just downloaded and installed this driver, and it is the first time I have tried to use it. I'm running it in Microsoft Visual C++ 6.0, but it is a C program.

I hadn't done too much debugging when I wrote the question. All I knew was that I got a timeout error when I used that call. Over the weekend I tracked it down to a problem in the function tktds7x4_InvalidateTriggerAttributes, and specifically, the line
checkErr( Ivi_GetAttributeViString (vi, VI_NULL, TKTDS7X4_ATTR_INSTR_COMM_TRIGGER_SOURCE, 0, BUFFER_SIZE, triggerSource));
My scope does not have the 2C option, so there is no communication trigger function. When the driver queries the communication trigger source, the scope apparently does not return anything because it does not understand. I added the lines
if (!strcmp(triggerSource, channelName))
checkErr (Ivi_InvalidateAttribute (vi, VI_NULL, TKTDS7X4_ATTR_TRIGGER_LEVEL));
checkErr(
Ivi_GetAttributeViInt32(vi, VI_NULL, TKTDS7X4_ATTR_INSTR_OPTIONS, 0, &options));
if (isOpt2C)
before that line of code (at line 7360), along with a closing brace before the label "Error:"
Also, at line 399, I added the following 3 lines:
{ "CH1" , "CH1" },
{ "CH2" , "CH2" },
{ "CH3" , "CH3" },
{ "CH4" , "CH4" },
even though the comment for triggerSourceStringTableEntries says that it is for non-channel sources only. I am not positive that it was necessary, but I think it was.
With those changes, the driver now works correctly for me. I have attached my updated driver source code. I am never happy to change a commercial driver, though. If someone were to re-download this driver and re-install it, all my changes would be lost, and the driver would no longer work.
Attachments:
tktds7x4.c ‏664 KB

What is the device_type_number for a PXI-4472B?

What is the device_type_number for a PXI-4472B?

I mispoke on device_type_number as the variable is labeled as device_type_code, if memory serves correctly, in your older NIDAQ examples. It is the parameter found by using:
Get_DAQ_Device_Info (iDevice,ND_DEVICE_TYPE_CODE,&device_type_code);
where iDevice is the device number set in MAX. For example, this number for a PCI-6052 = 273 and for a PXI-4472 = 335. Does the PXI-4472B have the same device type code as the PXI-4472 or is it different?

ASA 5505 8.4. How to configure the switch to the backup channel to the primary with a delay (ex., 5 min) using the SLA?

I have ASA 5505 8.4. How to configure the switch to the backup channel to the primary with a delay (for example 5 min.) using the SLA monitor?
Or as something else to implement it?
My configuration for SLA monitor:
sla monitor 123
type echo protocol ipIcmpEcho IP_GATEWAY_MAIN interface outside_cifra
num-packets 3
timeout 3000
frequency 10
sla monitor schedule 123 life forever start-time now
track 1 rtr 123 reachability

Hey cadet alain,
thank you for your answer :-)
I have deleted all such attempts not working, so a packet-trace will be not very useful conent...
Here is the LogLine when i try to browse port 80 from outside (80.xxx.xxx.180:80) without VPN connection:
3
Nov 21 2011
18:29:56
77.xxx.xxx.99
59068
80.xxx.xxx.180
80
TCP access denied by ACL from 77.xxx.xxx.99/59068 to outside:80.xxx.xxx.180/80
The attached file is only the show running-config
Now i can with my AnyConnect Clients, too, but after connection is up, my vpnclients can't surf the web any longer because anyconnect serves as default route on 0.0.0.0 ... that's bad, too
Actually the AnyConnect and Nat/ACL Problem are my last two open Problems until i setup the second ASA on the right ;-)
Regards.
Chris

I have a DAQ Assistant configured to read multiple channels at the same time. When I wire a graph indicator to the output, I see all of my signals jumbled together. How do I split them up into seperate signals?

I have a DAQ Assistant configured to read 2 channels at the same
time. When I wire a graph indicator to the output, I see the 2
signals jumbled together. How do I split them up into seperate signals?
When I wire any type of indicator it is showing just one output of a single channel.
I want 2 indicators showing 2 different signals as expected from the 2 channels configured. How to do this?
I have tried using split signal but it end up showing only 1 output from 1 signal in both the indicators.
thanks in advance.
Solved!
Go to Solution.

Yes you are right. I tried that but I did not get the result.
I just found the way. When we launch split signal, we should expand it (split signal icon) from above and not from below. It took me a while to figure out this.
thanks

Can I close multiple output channels in parallel on one COM line using the PXI-2503

I want to fan out a power supply to four DUTS. During current testing, I will want to turn on one DUT at a time. During other tests, I want to power all four DUTS in parallel. This will require turning on four output channels at once in each mux bank. Can this be done using the PXI-2503?

Bob,
4x6 2-wire mode should work fine. You can connect the power supply to one column, and the DUTs to each row. The rows can be connected to the column one at a time or all at once.
Regards,
Jessica Kinnevan
Applications Engineering

[svn] 1743: In the process of changing the messaging authentication tests to run over individual channels .

Revision: 1743
Author: [email protected]
Date: 2008-05-15 12:26:11 -0700 (Thu, 15 May 2008)
Log Message:
In the process of changing the messaging authentication tests to run over individual channels. Before the tests were just running over the first/default channel in the destination. Now the tests will be hardcoded to run over a particular channel. In this checkin I am removing the existing authentication tests and checking in tests that run over a polling amf channel. Tests for other channels are coming soon.
Modified Paths:
blazeds/branches/3.0.x/qa/apps/qa-regress/WEB-INF/flex/messaging-config.mods.xml
Added Paths:
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-amf/
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-amf/JMSAuthConSubscribeTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-amf/JMSAuthProSendTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-amf/JMSAuthSendSubscribeConstraintTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-amf/MessagingAuthConSubscribeTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-amf/MessagingAuthProSendTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-amf/MessagingAuthSendSubscribeConstraintTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-amf/MessagingAuthenticationTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-amf/MessagingAuthenticationTest2.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-amf/MultiTopicMessagingAuthConSubscribeTest.mxml
Removed Paths:
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/JMSAuthConSubscribeTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/JMSAuthProSendTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/JMSAuthSendSubscribeConstraintTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/JMSAuthSendSubscribeConstraintTest_Streaming.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/MessagingAuthConSubscribeTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/MessagingAuthProSendTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/MessagingAuthSendSubscribeConstraintTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/MessagingAuthenticationTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/MessagingAuthenticationTest2.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/MultiTopicMessagingAuthConSubscribeTest.mxml

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

Possible to configure several communication channels for the same receiver?

Hi,
is it possible to configure several communication channels for one (the same) receiver?
The problem is as follows: I would like to switch between the RFC-channel and the XI-channel, if the RFC-Adapter doesn't work for some reason.
The situation: Our XI3.0 posts messages to several receivers and the switch should be done by changing one table entry which is selected and analysed in an ABAP-Proxy and which could enrich the XML-message. By now, the only chance I see is to change the respective entries in the Integration Directory for each receiver separately.
Thanks for your help, Peter.

Hi,
>>>>But to be honest: Is it elegant to double the receivers?
of course not:)
but this is the only way I believe
(cause you cannot assign conditions to receiver agreements)
you could also create two messages (practically two flows)
but would it be more elegant?
BTW
in my opinion you should try restarting RFC channel
and not create two - just in case...
if RFC doesn't always work why don't you use another one only?
this would just simplify your scenario (maintanance of just a number of communication channels and not 2 x number of communication channels)
Regards,
michal
Message was edited by: Michal Krawczyk

I Am Getting Inaccurate Readings When Some Channels of the SCXI-1520/SCXI-1314 Are Open Circuits

Am Getting Inaccurate Readings When Some Channels of the SCXI-1520/SCXI-1314 Are Open Circuits
My hardware is :-
PCI MIO 16E-1 - 1 no.
SCXI-1000 chassis - 1 no.
SCXI-1520 - 4 nos.
SCXI-1314 - 4 nos.
MAX is showing all hardware ( DAQ card + Chassis + SCXIs), set in Multiplexer mode.
I am using MAX task to configure channels ( as per requirement ) and then use the same task in Labview 7.1
When I am trying to generate task only for connected channels then reading are coming some times....... but when i generate task for all channels including (not connected channels) then the reading are either on - side or on + side (max or min).
I have tried to ground the +S but not work
tell me some solution
Thanks
Surender Kumar

No, DAQmx is superior and I strongly recommend you used DAQmx
Elijah, I guess I understood the problem that Sunder is facing, coz even I had experienced it 2 years back
What happens is if you scan only the channels to which sensors/strain gauges are connected, all is fine and you get good strain readings.
But if you happen to include an unconnected channel into the scan list, all the subsequent channels after the open channel will show saturated readings.
Right, Surender??
The problem we found, lies in the settling time of the E series DAQ card's ADC. Even we were using PXI 6071 E
Once the ADC saturates on reading an open channel, it cannot settle fast enough to read the next channel.Hence, the next channel also reads saturated value, instead of the correct value.
This is irrespective of the sampling rate because, this happened even when we did continuous sampling at low scan rates of 10 to 100 samples /sec
We found 2 solutions to this problem
Disable Simultaneous sampling and hold for the SCXI 1520 module ( using a DAQmx property node)
Use a M series DAQcard, which did not have this settling time problem
Hope this helps,
Regards,
Dev

How do I get NIDAQ to allow 8 differential channels on a PXI 6031E card?

The PXI 6031E card contains 32 differential analog inputs (64 SE). However, in MAX, it is not possible to select Differential mode for any channels past the first 8. If you run the Test panels for the 6031E card (configured for differential input), selecting channels 8-31 results in an error. (0-7 operate correctly).

Yep! The URL has the answer. My problem statement wasn't quite accurate in that I claimed that I had errors on channels 8-31...Actually 8-15 and 24-31 were invalid and caused errors. What is/was confusing is that when editing an analog channel in MAX, and differential mode is selected, MAX allows the user to select invalid channel numbers(e.g. 8-15). The MAX editor requires the user to somehow "know" (or access the above URL) to skip 8 points to get to the next group of valid differential analog channels (16-23). It would be better if the channel number selector only displayed valid selections - based on the selected mode.

How to control individual channel of signal generated from digital waveform generator?

Digital waveform generator has 8 channels. I need to generate two different signals to HSDIO. How to modify and control two different channels? Also, how to translate pin outs from PXI-6541 to channels? I need to control signal into pin 1,3,29,and 31 individually.
Thank you!!
Solved!
Go to Solution.

You must combine your individual data into an array. The digital waveform is simply a digital representation of the binary array. It still boils down to bit 0 of each array element going to channel 0 (or the first channel you specify in Create Dynamic Channels). The next bit goes to the next channel. My last post is quite clear. To display the array in binary, right click on an array element, then select Display Format, then select Binary. You can also right click on the element, select Visible, then select Show Radix to display the small b before the number. One more thing, in the Display Format window, uncheck the box next to Use minimum field width. Then set the numeric just under the box to 8. Then select Pad with zeros on left in the box below.
You should not use waveforms until you learn more about how the HSDIO operates on input data. It isn't hard to combine waveforms, but it also isn't as clear as using an array of U8 or U16 or U32.
Trying to explain further. The first number to be writen to the HSDIO will have this effect: Bit 0 (LSB) of the number gets written to the first HSDIO channel you specify. Bit 7 goes to the 8th channel you specify. If you don't specify 8 channels, the bits get ignored. So wiring in one number will produce only one bit on each channel. In other words, the number already combines the bits of all the channels you specify. You don't combine anything yourself. Look again at my picture on my last post. By wiring in an array, you cause a bit pattern to be generated.
I hope this is more clear.
- tbob
Inventor of the WORM Global

Configuring DAQ channels through LabView program

Hi,
I want to scan one analog input of PCI 6025E every 250 msec and I scan 8 such channels. I am using AI Sample Channel VI to do this and for its channel input I am feeding a string (with channel name) that is typecasted using a Traditional DAQ channel constant. All the required channels are configured using this constant. However this VI doesn't seem to be portable. When I use it on a different machine, the constant shows no channels defined.
Is there a way to configure DAQ channels through my program such as to make the program portable? I came across notes that mentioned DAQ global channel but I don't know how to use it.
Thank you in advance,
Sharmila

One of the great things about DAQmx is that there are only 4 basic VI's to learn to use. The Configure, Read, Write and Stop. The same Configure VI that was used to setup the analog input channels can be used to setup analog output, digital in/out and counter in/out.
The small menu on the bottom of the VI is actually a listing of all the different operations that this single polymorphic VI can do. Click on the down arrow and you'll see what I mean.
I've modified the example to read DIO lines 0-3 and write to lines 4-7 on Port 0. Again it programatically builds the channel list so it will always refer to the correct device. To create individual channels for a digital line, you first specify the device, then the port, then the line or lines. Example, to create a task for lines 4-7 on port 0, you would use "Dev1/port0/line4:7".
Notice that the "DAQmx Create Channel.vi" is the same one used in the analog input configuration, but with different polymorphic selections. Also note the "DAQmx Read.vi" is the same except for the selector.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
Attachments:
Build Task and Scan Channels with DIO.vi ‏127 KB

Why does it take so long to clear a task (with DMA transfer) using the PXI bus?

I am migrating a system which used to use a PCI-6133 (8 channel simultaneous AI) and PCI-6733 (8 channel AO) to one that uses a PXI-6133 and PXI-6733 mounted in a PXI-1033 chassis.
In general, things seem to work (synchronized AI/AO running near the maximum rate on both devices), with the one exception that clearing an AO task on the PXI-6733 takes forever (on the order of 20-30 seconds).
Even when I try the sinewave generation for the PXI-6733 in the MAX test panel it takes the same amount of time to stop the task. If I switch to using interrupts as the transfer mechanism, it stops immediately.
I tried using the interrupt transfer mechanism on my more demanding set of synchronized tasks, but that does not produce the right behavior (even though it does not give any errors).
Is there any trick (or better diagnostic) to help get my tasks working with DMA under PXI that used to work fine on PCI?
Thanks in advance!
Solved!
Go to Solution.

Hi Patrick,
I'm using a PCIe-8361 controller. The computer is a Dell T5500 workstation running Windows 7 x64. I see the problem every single time I try to clear a task running on the PXI-6733, including my example using the Measurement & Automation test panel (from the very first time I try the Sinewave Generation onward). I can try other parameters in the test panel, but I don't need to adjust anything from the defaults (e.g., Rate = 1000) to get the behavior. I will also try installing the PXI chassis in a few other computers we have here just to confirm that it's not computer specific. From your line of questions I can at least gather that there's nothing obvious (like a known bug with the PXI-6733) and that I should expect this configuration to work.
Thanks for your help and I'll post any other findings I obtain.

Configuring individual channels on the PXI-4472B

Similar Messages

Maybe you are looking for