Data Acquisition Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

Based on this question, I would like to add a new category of events to LabVIEW: Max-events.

 

This category could contain the following events:

-Hardware Added

-Hardware removed

-Configuration changed

    -Scales

    -Channels

    -Tasks

 

If you know other events, please post them.

I'm not sure who reads this, but I'm not seeing any feedback in the forum so I thought I'd post up here.   This may seem like a simple thing, but hopefully my pain will be someone else gain.  I messed with this off and on for two months before I finally figured it out.  It's probably obvious to those who work with this equipment every day and have EE degrees, but not so much to those of us who do not. 

 

Please see http://forums.ni.com/t5/Multifunction-DAQ/Measuring-220VAC-with-CompactDAQ/td-p/1145956 for a description of the issues I was having. 

 

Some will tell me to "search"... well, I did.  ...and everywhere I looked all I found was that I needed to measure from the power leg to ground.  All of the examples either were only measuring 120 which is fine since what you have is one power leg and neutral... which is basically ground!  So those numbers come out fine.  Or they were for 3 phase, which I don't use currently.  BUT when you try and measure anything with two power legs (basically anything between 208VAC to 240 VAC) the numbers don't work out right if you try to measure between each power leg to ground and then try to recombine them and plug them into the Power VI's.  Not one place that I looked did it tell me that I need to measure both power legs across a single channel.  I only finally tried it because I'd done pretty much everything else.  I know this is pretty basic stuff, but when all you give me says one thing... that's what we do.  Just trying to help others.

Thanks,

Chad

I am learning how to use the scripting feature of NI-RFSG and the script editor is an incredible frustrating tool.

 

Why do you show text if you can't type? Show a diagram if you don't want people typing.

 

I am using Notepad to type my scripts and then moving the text over.

 

There should be a way to allow people to type in the script editor and do on the fly syntax checking... or even do it after. I can export my script to the clipboard, but why can't I paste into it?

 

Just let people type.

I would really like to see a user configurable hardware front panel that integrates with LabVIEW. The panel would connect to a computer via USB. National Instruments could sell different hardware controls such as pushbuttons, LED's, switches, LCD panels for graphs, rotory encoded switches, slide switches and potentiometers, LCD indicators for text and numbers, etc.

 

LabVIEW would discover which panels are connected and which hardware controls are available in those panels. The user could then drop them as terminals on the block diagram and use them as normal.

 

Another option for the panel could be an embedded computer running LabVIEW so that the whole thing can be stand alone.

Hey all,

 

Just passing an idea for some new HW and SW for the PXI and LV. I think a touch panel PC monitor would be an ideal O/P for a PXI as you could plug it in the back and eliminate the use for a mouse and keyboard whilst using the PXI chassis. This also leads onto my second idea, the creation of a front panel customization tool kit. This tool kit will enable users to easily customize the front panels of their VI's much in the way a function pallet would work. This way you are able to quickly customize your front panel to suit the end users needs.

As a user of the SCXI 1000 with a 1302 board, I had a lot of difficulty finding information on the pinout of my board. The 1302 is a direct link to the 6220 DAQ card on my computer. When I first looked for the 1302, I could find very little information on it. By adding a few windows and commands to the M&AE, I probably would have been able to solve my problem in minutes instead of days.

 

Solution

A. Being able to add boards which link to pinouts of the computer's DAQ and treat them as a board.

B. Have a list of pinout boards which can link to the DAQ. Since I was dealing with a 1302 which has 34 pins instead of 64 (or something close to that) I had difficulty finding the information on the pinouts. It was far easier to find the pinout of the 6220.

 

It could be I was a little annoyed at the amount of time that I spent on finding information on the 1302, but it took me far longer to find the information than it should have. This data should be built in.

As far as I know, the DAQ-mx has provicion to generate the COUNTER output or to read digital input triggered by the change detection event.


It would be nice if one is capable of generating the DIGITAL output on accurance of change detection event.(i.e. it can be triggered):smileytongue:

 

Also digital output must be allowed to generate the waveforms which are triggered by any of the digital input lines.

 

If possible then COUNTER counts should be available to user in LABVIEW after triggering, to synchronise the various digital input/output to counter state/count.Since some of the actions are COUNT dependent.

In addition to USB-TC01 one thermocouple channel, the device should be able to log ambient temperature. Most temperature data needs to be referenced to something.

I would like to have an programmable gain amplifier in the analog output path that I can use to adjust the amplitude of an output signal.  In control applications, this would be much better than having to stop a continuous task, reload the data with a new amplitude, and start the task again.

 

Ideally, for some of my applications, it would be nice to be able to generate a basic waveform scaled to +/- 1V and then have a property that I can write to while the task is running to set the gain.

It would be great if NI offered a simple 4 Counter bus-powered USB device, like a USB-6601, but with the counter capabilities of the new X Series DAQ devices. This would give people who only need to perform counter operations a low-cost alternative to the bus-powered M Series, with double the counters.

I often use one DAQ device to test the basic functionality of another device and like to be able to quickly do this through test panels.  Unfortunately, MAX does not allow the user to open more than a single test panel at once.  The current workaround for this is to launch the test panels outside of MAX (see this KB).

 

It would be nice to have the same functionality when opening test panels in MAX.  Specifically, I would like to be able to do the following with a Test Panel open:

1.  Be able to navigate through MAX to do things like check device pinouts, calibration date, etc.

 

2.  Be able to move and/or resize the original MAX Window (it always seems to be blocking other applications that I want to view alongside the Test Panel)

 

3.  Open a test panel for a second (or third...) device.

 

It is nice that there is a workaround in place already but I think it would be nice if MAX had this behavior to begin with.

Hi all,

 

Any series card should have a feature listing different  parameters like voltage, temperature etc it supports(May be a property node should be used). so that user can configure the required parameter among the supported.

Ex: SCXI -1520 module can be configured as Strain, Pressure or voltage but this information will be known only by seeing its manual or when a task is created in MAX. But in LabVIEW               Software i cant get this information directly. Because it allows me to configure 1520 as temperature also and we will come to known that 1520 module doesn't support for temperature       parameters only when once tried to acquire.

 

So what you people think about you.Share your ideas on this please. 

 

Regards,

geeta 

Hello,

 

How often you have build Labview applications using simulated DaqMx boards ...

And how often you were limited by the default behaviour of simulated boards ... ( Sinewave for analogic inputs, Counter square signal for digital inputs ... )

 

It would be nice to integrate in DaqMx simulated boards, the abilty to modify the default behaviour of simulated inputs ... thru dedicated popups

 

It would be nice, for each task linked to a simulated daqMx board, to launch a popup window ...

 

  • For digital input, give the abilty to modify for each configured channel , the current binary value.
  • For analog input, give the ability to choose between a fixed value, a sine wave, a square signal ... white noise ...
  • For digital output, give the ability to view the current setted values
  • For analog output, give the ability to view the current simulated output value on a waveform chart ...

 

A more powerfull tool could also integrate a simulated channels switching mechanism ... A simulated output could be linked to a simulated input 

 

This feature could be a good way to create an application which could simulate a complete process ... this application could be used to validate a complete system

(such a kind of SIL architecture)

 

Other idea .... A complete daqMx simulation API ...

 

  • Creation of an API which could instanciate a simulated daqMx board (Wich could be seen via MAX)
    • Takes place of the actual limited daqMx simulated board
  • This device could then be accessed by other application thru daqMx
  • This API could have access to all channels of this simulated device.
  • This API could force, programmatically, the value of the simulated input channels according to a realistic process model

 

Something like this ...

 

 

 DaqMxSimulatedAPI.PNG

 

Just as a better integration of the poor mans DAQ, I see it as an door opener for serious DAQ hardware. 

It matters less to me right now because I am about to change jobs but instead of a frame grabber to connect to cameras, we could use frame grabbers that acquire both Hi-Def and standard-def video. We've found some that usually work but get a bit flaky when we are using two simultaneously. Having robust LabVIEW drivers from NI instead of writing our own would save a lot of time.

Since NI already has the hardware interface devloped to USB and the PCI bus and its variants, why not leverage on that and create a line of hardware dongles that are compatible with MAX, LabVIEW and LabWindows IDE's. The volume may be low but it would be an integrated solution for ease of hardware/software interaction. Each dongle would have a unique serial number that the programmer's application  can check and verify before allowing software operation.

 

-AK2DM

When I want to do an installation build of my project, I have to include the whole NI-daqmx into my build in order to insert my (in this case) USB-6251-driver. Thus my install package expands from about 150 MB to more than 1 GB. This is way to much!

 

It would be nice to be able to choose only the wanted driver (in my example the NI-6251 and the SCC68) in the "adding additional driver's" menu and just add this one to the distribution instead of "adding them all".

TO

 

R&D , LABVIEW,

NATIONAL INSTRUMENTS.

 

FROM

 

Mithun Raj .T,

Pranavam, Kalluvilla , Kariyam,

Sreekaryam P.O, Trivandrum- 17,

Kerala, India.

 

We are a group of B.tech project students from SIST , Kerala ,India. We are doing a project on ICU using LABVIEW in Indian Space Research Organisation.

While we doing our project we found the nessecity of following :

 

> A functions that provides range or specification of the addressed device so that the programmer has an overall knowledge of the addressed device & its range of operation.

> A suggestion window at the top left when some error occurs.

 

So if our suggestions are good please kindly provide us a good idea certificate from NATIONAL INSTRUMENTS,that will help us a lot. So kindly consider our request.

 

Your's affectionatly,

 

Ahammed Shiraz A.R

Anish .S

Dileesh .S

Mithun Raj .T

 

Proposal : If left unwired, the DAQmx Create Channel Minimum and Maximum Value inputs would default to the maximum value for whatever physical channel was wiredCurrently for example, AO Voltage defaults to +/- 10 VSome devices such as the USB 6008 are limited to 0 to +5 VFor programs that allow for different daq devices to be used and changed at run time, one does not know ahead of time what the allowable input limits will be and cannot be assignedIs it possible to use the DAQmx Device property I/O Type:Analog Output:Voltage:Ranges to obtain the limits and then wire that result however this involves extra coding to make use of themIf the DAQmx Create Channel is used at many places in a vi it becomes cumbersome to have to extract the property for every instance of usei.e. even if DAQmx Create Channel is done once, another call to it does not retain the values previously setA solution would be for DAQmx Create Channel to simply obtain the minimum and maximum values based on whatever physical channel was wired to it and use them.

In the DAQmx Physical Channel Control if Analog Input is selected I would like to filter on the type of module i.e. Thermocouple, strain, Current, etc.

Filter Analog Input Measurement Type.jpg