Test panel in NI DAQ/ Labview

Hi
I downloaded NI-DAQ and Labview 6i evaluation version to program my DAQ 6020E(BNC) . I clicked on MAX and in the "configuration tree" i see under "devices and interfaces" my DAQ device present, but when i right click on my device i see that the test panel is disabled .My O.S. is Windows Vista. Sometimes i get errors like" NI-Max" files stopped working or "shared" file stopped working etc. What should i do to enable "test panel" on Max? My aim is to program one analog output channel to generate 5.5Volt for which i need test panel. Without the test panel being active, is there an alternate way to do this? The green LED on DAQ board usually is on but occassionally it blinks but finally stabilizes to continuously on state.
Regards

duplicate post. Please don't ask the same question to multiple boards. Your question doesn't seem related to the student edition or Elvis either.

Similar Messages

NI-DAQmx task works in MAX or DAQ Assistant test panel but not in LabVIEW

I am attempting to read a single AI channel from a PCI-6024E card via an SCB-68. I have created a NI-DAQmx Analog Input Voltage Task in MAX for this channel, sampling in contiuous aquisition mode at 100 kHz, 10000 samples at a time, with RSE terminal config. If I use the Test feature from MAX, the channel acquires data as expected.
In LabVIEW, I call this task using an DAQmx Task Name Constant. If I right-click this constant and select "Edit Task", the Daq Assistant opens and I can use the Test feature from the DAQ Assistant to see that the data is still being acquired as expected.
However, when I try to programmatically read this channel in LabVIEW using the VI "DAQmx Read (Analog Wfm 1Chan NSamp).vi", the VI returns a constant DC value of 500 mV, which I know is incorrect (I can monitor the signal across the two terminals in the SCB-68 with a DMM to know that the signal coming in varies as expected, and as I read using the test panels). This erroneous reading occurs even if I make a new VI, drop the task name constant on the diagram, right-click the task name constant and select "Generate Code - Example" and let LabVIEW create its own acquisition loop (which is very similar to what I already set up, using the "DAQmx Read" VI).
Any ideas why the Test Panels work correctly but the LabVIEW code does not?

Hello bentnail,
I'm not sure why the test panels are readin the value correcly but the LabVIEW code does not, but there are a couple of things we can try.
1) What happens if you just use the DAQ Assistant and place it on the block diagram? Does it read out the correct values?
2) Try running a shipping example that comes with LabVIEW. "Acq&Graph Voltage-Int Clk.vi" should work well.
3) What kind of signal are you expecting to read (peak to peak voltage, freqeuncy, etc.)?
Thanks,
E.Lee
Eric
DE For Life!

My Labview 6i evaluation version getting bad/unusual readings(analog input/output) while when i use test panel of Ni-DAQ 6.9.0 i have good readings from my PCI-MIO-16E-1 board.

If i used Lavbview 5.0 on same PC i don`t have problems.Sorry with my english!
Attachments:
TestPanel.jpg ‏103 KB
Labview.jpg ‏62 KB

I tried running one of the DAQ example programs and i got the same data and i only use the version of NI-DQA that shipped with my 6i version evaluation. About hides drivers i reinstall and double click in all of folders and sub folders. About my program i don`t think i have problems because is very simple but i send it to you for you help me. About two weeks i am around this problem and i can`t see evolution...
PS.: Sorry with my english
Best regards,
Nelson Ferreira
Student of ISEP College in Portugal
Attachments:
LerEntrada.vi ‏43 KB

For a 3.33v input, DAQ & MAX Test panels read 018v. What is missing in set up?

Hi All:
I am resurrecting a Labview setup that has not been used for a few years.
The goal is to measure strain.
Software is:
Labview 6.0
DAQ V6.8.0f9
MAX 2.0.3.6.
Hardware is:
PCI-MIO-16E-1
SCXI-1000 Chassis
SCXI-1121 Module
SCXI-1320 Terminal Block
As a fist step I decided to test the hardware using MAX.
I reset all of the SCXI-1121 jumpers to factory settings except the Filter jumpers.
Filter jumpers were set at 10kHz and I left them at that setting.
In MAX I followed the software procedures for setting up the PCI-MIO-16E, SCXI-1000 Chassis,
and SCXI-1121 Module (Module was found using the auto detect). MAX verifies the PCI-MIO-16E
card, and the SCXI-1000 chassis.
I verified that EX 0 thru 3 were 3.33v using a digital meter.
I then wired EX 0 to CH 0 and using the MAX Test Panel and the set up string of
ob0!sc1!md1!0
in the channel box on the Analog Input tab.
I expected to see a 3.33v reading on the test panel, but got a reading of .0184v
(I assume this means zero or is noise). The result is the same on channels 1, 2, and 3.
As far as my bifocals can tell, all cables are connected properly, and there are no bent pins.
I have re-verified the jumper settings per the SCXI-1121 User Manual. I have printed the
“Knowledge Base”, “SCXI Trouble Shooting Resources” and walked through them step by step
to verify the set up of hardware and software.
I have set up a virtual channel for each channel and used the DAQ virtual test channel
test panel, and I get the same result .0184v.
Anybody have any suggestions or clues as to what I have missed?
Thank You
Peter Waltz

Hello Peter,
If you are reading 0.0184V on your analog input, then it probably means that you are reading nothing at all.
This seems like a driver issue more than anything else. Make sure that you are the latest possible driver installed for this setup. Traditional DAQ 7.0 or 7.1 are compatible with LabVIEW 6.0 and should work fine.
Once you have the right driver, try connecting your analog output to your analog input. Output a sinewave or a specific voltage and see what the AI reads.
Most likely the driver upgrade would solve your problem.
You can download the drivers from here.
Chetan K
Application Engineer
NI
Message Edited by CKap on 05-08-2006 02:57 PM

Correct termocouple reading by VI channel test panel but not by DAQ wizards.

1. I am getting correct termocouple readings when using the virtual channel test panel, but not when using labView software created by the DAQ wizards. why and how to solve it?
2. I am unable to switch on 6V relay using DAQ card's output voltage but able to do so using other voltage supply. How to solve this?

In answer to #2, the DAQ card's analog and digital outputs cannot drive
enough current to turn on a relay. What you need to do is use the output to
drive a MSOFET or transistor that will drive the relay. You can use the 5V
computer supply that is available on the DAQ card connector as the power
supply that the MOSFET or transistor use to turn the relay on.
Neal Pederson, President, VI Control Systems
1923 Mendius Lane, Los Alamos, NM 87544
TEL: (505) 662-1461, FAX: (603) 388-4969
[email protected], www.vicontrols.com
"DAQprojects" wrote in message
news:[email protected]..
> 1. I am getting correct termocouple readings when using the virtual
> channel test panel, but not when using labView software created by the
> DAQ
wizards. why and how to solve it?
>
> 2. I am unable to switch on 6V relay using DAQ card's output voltage
> but able to do so using other voltage supply. How to solve this?

DAQ card works with NIDAQ test panel but not with VB app/Component works

I am seeing this problem with 2 different DAQ cards. The card works fine with the NIDAQ test panel, but acts like the return lead is lifted with my VB app. The plotted signal appears to be little more than noise. Channel scan is internally triggered; that apparently works fine. The VB app is running in this configuration successfully in other areas, and I fixed this problem once by swapping cards. Currently, I lack a spare, as my "spare" is showing the same symptoms. Any helpful hints?
Card type: AT-AI-16XE-10
Configuration: Double-ended input, +/-10V range
Running: VB6, NIDAQ 6.1, ComponentWorks Std. 2.0.1, Windows NT 4.0 SP5

I upgraded to NI-DAQ 6.8.1 (with patch), but no joy. The upgrade went smoothly, the card was recognized and I was able to set the resources without a problem. The test panel works fine looking at the actual signal on the target system: slowly varying DC between 0-5 V or so. My app works fine also, except that it behaves as though the A/D is not connected to anything: noise between .05-.1 V or so. I swapped DAQ cards between the test system and my development system. The problem appears to be in the test system, not on the card. Another test system, identical except for (now) the version of NI-DAQ, works fine. I'm stumped!
BTW, why are there 3 DMA channels listed in the configuration for this DAQ? Do all 3 need to be assigned? I've run some systems
for years with only the first 2 assigned.

When measuring 6 voltage signals in labview I found that there was a difference in voltage signals in my program but not in the test panel. The test panel is correct. What is wrong with my program?

My labview program is not displaying equivelent voltages, but labview test panel is. So the computer is seeing the correct signals. My program is displaying a small difference in 3 out of 6 channels. All channels should be equal.

G'Day Pops,
You haven't really given us enough to go on - could you please post your VI so we can have a look at it?
cheers,
Christopher
Christopher G. Relf
Certified LabVIEW Developer
[email protected]
Int'l Voicemail & Fax: +61 2 8080 8132
Aust Voicemail & Fax: (02) 8080 8132
EULA
1) This is a private email, and although the views expressed within it may not be purely my own, unless specifically referenced I do not suggest they are necessarily associated with anyone else including, but not limited to, my employer(s).
2) This email has NOT been scanned for virii - attached file(s), if any, are provided as is. By copying, detaching and/or opening attached files, you agree to indemnify the sender of such responsibility.
3) B
ecause e-mail can be altered electronically, the integrity of this communication cannot be guaranteed.
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

Simulated device in MAX, self tests without error and has working Test Panels, but doesn't show up in DAQ assistant.

I'm trying to create a development machine where we can test new code without using our physical hardware. I've followed this guide in setting up a simulated device. I can get to step 3.2b, but the device does not show up in the DAQ assistant. In MAX, the device self tests and self calibrates successfully, and when I open the test panels, I see some sort of signal. I assume this is a default simulated input since I haven't told the device to look for anything? Note that the two devices I'm trying to create show up in the Devices and Interfaces section, but that even after running Self-Calibrate, the Self-Calibration date is still unspecified.
When I try to test the device and create a voltage input according to the guide, I am unable to see either device in the DAQ task creator.
Steps 1 and 2 of this guide are obviously satisfied. Step 3 is not, but this is unsurprising since a simulated device wouldn't be found in the Device Manager anyways. Also, I am not running RT, so step 4 is satisfied.
Does anyone have any ideas?
Solved!
Go to Solution.

That would be because the PXI 5124 is a digitizer not a analog input device. You need to use the NI SCOPE driver not NI DAQmx
Jeff

My daq card PCI6025e' digital ports PA,PB,PC are in high state and cannot be changed even in MAX 2.1 testing panel and continuously output 5 volts even set for output.

my digital ports PA,PB,PC are in high state and cannot be set low even if it is set for outputs.
Thanks

The MAX utility is the closest to the driver level and will eliminate software configuration as a possible issue. Please disconnect anything that you have connected to the DIO lines.
Use the MAX test panel for your DIO lines, configure them as outputs, and set them to a low state. Use a multimeter (DMM) to observe the line state. If it is still high then you may have a problem with your hardware. If this is the case, I advise calling National Instruments support and investigate a possible RMA (repair).
Best Regards,
Justin Britten
Applications Engineer
National Instruments

MAX 4.2.1.3001 Task Test Panel Button Missing

I just upgraded to LabView 8.2.1, along with the drivers, NI-DAQmx, MAX, etc., and now when I use MAX to view my existing tasks, they no longer have a "Test Panels" button. They appear to now have an integrated test graph. That is nice, but before I was able to press the "Test Panels" button, select a type of "Values" instead of a graph type, and this would allow me to see the raw values that each channel was returning. What happend to this functionality in 8.2.1.3001? I know that I can go to each individual channel and see its raw values, but that is not acceptable. I need to see all of the values of each of my task channels together in one place, the same way I was before "upgrading" to the new MAX. Am I missing something?
Thanks for listening!
Rick Howard
Exquadrum, Inc.

This post and also this post, which are the same, have been replied to on this DAQ forums post, on which you can continue posting. Please post only once on the most relevant forum.
Regards,
Raajit L
National Instruments

What determines TEST PANELS to show or not...

On any fresh install of NI-DAQ, the System Administrator and the first user logged in afterwards can use the Test Panels... button in the "Measurement & Automation Explorer" as well as run the Standalone programs made by Application Builder (LabView 7.1)...all other users can not use the Test Panels... or run the Built-vi's that shows up with plenty of error code 21, "an external subroutine required for execution could not be found", and it seems to be vi's that are called by the vi's we use, like one step away. I have set the permissions to all the related files to FULL as well as hacked the registry's HKeyLocalMachine->Software->NI... as well as the CurrentControlSet->...->DAQCARD... all to full control.
Since the Administrator and the frist user can run the programs it is definitely not a case of missing software, but just permission rights. Please help to get the other users productive as well!

Hi Nambabwe, if the test panels button is greyed out for a device, that means that MAX was unable to load the nidaq32.dll driver. I am interested in figuring out this problem, because it seems to be a commonly reported problem, yet I cannot reproduce it myself. Here are a few questions for you:
* Which version of NI-DAQ are you using?
* If this version is equal to or greater than 7.0, do you have both Traditional NI-DAQ and NI-DAQmx installed, or just Traditional NI-DAQ?
* Regarding the non-administrative users who are running into this problem: are they restricted users, power users, or guest users?
Here's one possible solution off the top of my head:
The "CurrentFile" value of the registry key "HKEY_LOCAL_MACHINE\Software\National Instruments\NI-DAQ\CurrentVersion\Configuration Manager" indicates the location of the current DAQ configuration file. Ensure that your normal users have at least read access to this file (and this registry key too, but it sounds like you've already done this).
Please check back with the answers to these questions, and I will help to come up with a solution to this problem.
Joe

Most users can not use TEST PANELS or run EXE built vi's?

On any fresh install of NI-DAQ, the System Administrator and the first user logged in afterwards can use the Test Panels... button in the "Measurement & Automation Explorer" as well as run the Standalone programs made by Application Builder (LabView 7.1)...all other users can not use the Test Panels... or run the Built-vi's that shows up with plenty of error code 21, "an external subroutine required for execution could not be found", and it seems to be vi's that are called by the vi's we use, like one step away. I have set the permissions to all the related files to FULL as well as hacked the registry's HKeyLocalMachine->Software->NI... as well as the CurrentControlSet->...->DAQCARD... all to full control.
Since the Administrator and the frist user can run the programs it is definitely not a case of missing software, but just permission rights. Please help to get the other users productive as well!

Hi, they have not got the application builder license here...

DIO won't work until I use the Test Panel

Here is some strangeness. A program that works fine all of a sudden has an issue on a clean install. I am using a DIO-24 and after the PC has been wiped and and the software including the OS and drivers are reinstalled I get an error trying to access the DIO. Once I open the MAX test panel for the device (DIO-24), wiggle some lines, and close it all is fine. The program will continue to function fine. What "Magic" is happening when I open the DIO-24 in MAX?
Matt
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

I am saying:
Are you saying that after installing the driver and your device you had to open MAX and use test panels before your device would work with your application, and now you can always use your application (even after restarting your computer) without opening MAX? - Yes
Does this behavior only occur with your software, or does it occur with a shipping example too? - I Have not tried to run example after a fresh install so don't know
Are you using LabVIEW to communicate with your device? - Yes LabVIEW 8.0
If so, what version and what driver have you installed. If not, what programming language are you using? - NI DAQmx 8.0 for Feb 2006 Disk
Is this driver version the same that you had installed when you developed your application? - No, previous version
What operating system are you working on? - XP
Do you need MAX open to run your application, or do you just need to run it before your application? - Just run once and close before running application
Any additional information you can provide about what you are experiencing would be helpful.
I spoke the the engineer who gave me the information and he said it happens only some of the time. Most systems come up fine but a few require that MAX before the app will run correclty.
Matt
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

Test Panel in VI format

I am looking for the Measurement & Automation Explorer (MAX) Test Panel in a VI format. It has the ability to write or read from all lines in the DAQ. Each line is modeled as an LED.
I know that the test panel is available in the nitpan32.exe. I need to make some slight modifications to the file and was looking for it in VI format.

Greetings,
I am not aware of the existence of the Test Panel as a VI, but the example "Dig Multi-line Direction (E).vi" does accomplish what you have described. You can assign each line's direction, and they are represented by an LED (input) and a switch (output). This example is installed with LabVIEW.
Good luck with your application.
Spencer S.

Test Panel for 6704 no examples?

I'm trying to find an example vi that support our PXI-6704 card. Doesn't seem Ni has any built in, I'm wondering if "Getting started with analog output.vi" will work.
I don't deal with the programming or with the electronics so I'm out of the loop here.
In MAX were using a Remotei-daq config so making a test panel isn't possible.
I need a vi that acts like a test panel and shows what properties can be changed.
Any help at is all is welcome.

Hi JR,
There are lots of examples for this board. The PXI-6704
will function the same way as any other analog output board. If
you are using LabVIEW, then you can easily find a wealth of examples
that can run on the PXI-6704 by opening LabVIEW and going to
Help > Find Examples > Browse > Hardware Input and Output > DAQmx > Analog Generation
Once there you should be able to run any of these examples.
Best of luck,
Otis
Training and Certification
Product Support Engineer
National Instruments

Test panel in NI DAQ/ Labview

Similar Messages

Maybe you are looking for