Data Acquisition Idea Exchange

Top Authors

User

Kudos

Post an idea

INSTRUMENT SPECIFICATIONS

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 wired. Currently for example, AO Voltage defaults to +/- 10 V. Some devices such as the USB 6008 are limited to 0 to +5 V. For 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 assigned. Is 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 them. If 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 use. i.e. even if DAQmx Create Channel is done once, another call to it does not retain the values previously set. A 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.

Bring DAQmx to Mac and Linux

For some time a few Mac and Linux users are complaining to me that they want DAQmx on the Mac and Linux. This makes LabVIEW more cross platform compatible and enables the users to use their measurement equipment to it's full potential. The Mac market share hits about 10% and Linux about 2% this seems to be a growing market. And mosth netbooks use linux as an os, therefore this will make excelent portable measurement station. This will open a new market for National Instruments and for LabVIEW programmers.

I have a USB-6509 and a USB-8951 connected to a computer through an external USB Hub. MAX locks-up hard when I disconnect the External USB Hub from the computer, always requiring a reboot. When I connect/disconnect the individual devices on the other side of the External Hub, leaving the External Hub connected and powered, I do not get any problem.

Should there be problems when the External Hub is connected/disconnected, instead of the individual devices??? I'm thinking this is a "USB Problem", but the Windows Device Manager seems to roll smoothly with all the connection/disconnection variations. It is MAX (and any subsequent LV prog) that has the hangup.

Any ideas? Thanks!

DAQmx Device events

While running a test I developed I noticed an odd DAQmx behavior. After a USB 6212 connection was momentarilly interupted all read and write tasks associated with the device hung until the USB cable was disconnected. It would have been easy to code around if there was a Dev connection event and a Dev disconnection event that I could use to pause operations and trigger a Device reset. Since the devices are PnP couldn't the DAQmx API simply make the system hardware connect/disconnect events visable?

View All (2)

Take advantage of open-source hardware

View All (2)

Lightweight daqmx installer

I have a hard time explaning to clients that the little application that just monitors a few AI channels requires a huge (several 100'sMB) installer to run. It would be nice to allow for a small subset of daqmx to work. Maybe there is a way of doing this or maybe it is way too hard, but it would be nice to have the ability to filter support for devices and daq type on the drivers installation.

IE:

install only 6609 or 6008 AI only support where the installer would be a small fraction of the current size.

Improve interaction with MAX

I configure DAQmx channels, tasks, and scales as well as CAN messages and channels in MAX. It would be nice, if I could change the ordering of these elements after creation. It would also be nice to have an option to remove all configured channels (and tasks and scales) as well as CAN messages and channels, if I want to load the configuration of another project. Now I have to go to every section and delete the configuration by hand.

It would also be cool, if I could configure DAQmx variables in MAX, which I can use (write and read) in LabVIEW, too. E.g. I have a lot of tasks, which all use the same aquisition rate. If I have to change the rate, I have to change every task by hand. If I could use a variable, I just would change the variable. This would save a LOT OF WORK with huge DAQmx configurations.

Hello everybody,

I use always MAX to configure my DAQ cards to remove the burden of writing every time the same code just to create a DAQ task. MAX is part of my LabVIEW tool base and every project where I use a DAQ card does have a MAX config file.

Everything is nice, until I have to add some third party hardware! Then I have either use the driver provided with the hardware or write my own driver. I cannot use MAX to configure it, therefore I have to write VIs to allow online configuration. I also have to write VIs to load and save the configuration of the hardware. It would be much simpler, if the supplier of the third-party hardware or I could write plug-ins for MAX (and DAQmx) to incorporate the hardware in LabVIEW (and of course other software, which uses MAX). I could use the same API for nearly all of my hardware. One example from a competitor for this kind of hardware integration is Ipemotion of Ipetronik. There is even a plug-in for DAQmx in Ipemotion!

Regrads,

Marc

Specify source of simulated device data

I love simulated devices, but one major drawback is the static nature of the simulated data. It would be awsome to have the ability to import real world data for playback in the simulated devices. Essentially analog input channels could take a waveform in or waveform file, digital in could take a digital file or even a popup probe for the input where the user can turn on/off digital lines or turn a nob on an analog line would be very nice to have. This would allow the programmer to capture real data that a system might expect to recieve and then run the daq application in simulation using daqmx simulated devices with the exact real-world data.

Data Acquisition Idea Exchange

INSTRUMENT SPECIFICATIONS

DAQmx Create Channel Minimum and Maximum Value default to largest possible for the wired physical channel

DAQmx Physical Channel Analog Input Filter by Measurement Type

call PFI DAQ terminals something else or add a delimiter before the number