Scope of voltage zero

Hello world

I'm new to labview.

I use a high precision load cell and signal conditioner that provide precise and exit excitation (10 V)

The problem when I use the DAQ (myDAQ) card to measure the output voltage

The tension reaches zero to time finished as in the picture, but it is very stable to zero (without load)

Also the same problem, I found earlier when measuring a battery of 9V DC

Any ideas?

I suspect that you have a grounding problem. The signal conditioner is probably connected to the Earth via the USB/RS-232 connection when you have connected. When it is not connected through USB, it can be based.

Try to connect the ALWAYS the MyDAQ connection 24 V DC or taking land on the signal conditioner.

Lynn

Tags: NI Software

Similar Questions

  • measurement of analog voltage tends to zero

    Hello, I'm new to the forum see lab and Labview FPGA. First of all I would like to describe my system: I measure the voltage of the voltage inverteres-three with LEM - LV 25-400. Three analog inputs (I + and HAVE-) are connected to the LEM. I run the analog measurement of Labview demo program and it can measure the voltage, but donot values remain constant. He goes to zero and after some time goes to the correct value. My blood pressure never goe to zero. One can derive a little but almost constant. If I add the filter with high sampling rate, I had an almost constant value but miss the ripple values. I wonder if anyone can help me would be greatly appreciated.

    with respect,

    Marco

    problem solved

  • Apart from the scope, is there an advantage between elements of application elements of page zero vs?

    It's the kind of best practices of the question type.

    I understand, the application parts are available throughout the app Page zero points will be available on the pages where page zero is used. But there are basically the same.

    So, outside of the scope, is there an advantage to using application elements vs zero page elements for items that will be used on most of the pages? My use is I have these reference values of almost all the pages and there are some pages that will change the value of this variable. They are not constant.

    Thank you!

    Do you need constants then?  IK them would define as page 0 items that are hidden and cannot be changed otherwise then I would use elements of application to a minimum.  For the most part, I also do not recommend 0 page elements, because they are not passed in and out of shape but are only accessible...

    In a perfect system, you pass in a page, what suits him and, according to the elements of the application and page elements 0 is dangerous in my mind...

    Thank you

    Tony Miller
    Software LuvMuffin
    Ruckersville, WILL

  • Issues of analog input DAQ-6008, voltage not zero to pin when you are offline

    I use the 6008 NOR-DAQ to produce a series of tensions and then read a sense resistor using the analog input (CSR). I noticed that my analog input gives me 1.3 V, when I probe it (compared to the mass of the device), when it is completely disconnected. This changes the reading to give me a different measure of sense than expected resistance.

    Why is my pin for analog input non-zero? Any help would be appreciated. Thank you!

    The 1.3 V is expected. The USB-6008-and-6009 case have the strangest input of the world circuit. The input impedance is approximately 144000 ohms terminated in 1.4 V. check the document User Guide and specifications.

    Lynn

  • FPGA/FPGA adapter creates 250 mV voltage offset

    I use a high-7971R FPGA in a chassis SMU-1073 with the adaptation Module 5782 (DC coupling) and 2016,08 device drivers. When I turn on the chassis and my computer, nothing strange happens. When I try to run something on the FPGA, however, things get weird. Each piece of code works exactly as it should, but as soon as that 'open FPGA reference' finishes running the adapter begins to produce a voltage mV to 0 to + 250 Ai and AI 1. It doesn't go to AO 0 or 1 AO. This shift of power disappears temporarily as long as 'Reference FPGA open' or "Close FPGA reference" are running, but the only way to get rid of the tension of offset entirely is to restart the chassis. Can someone explain to me why this is happening and how to fix it? The FPGA code, I am running can handle a small shift, but this shift seems to be to saturate the signal.

    To see the shift: branch I HAVE 0 and AI 1 directly in a 1 M complete oscilloscope.

    It is planned. CDA on this FAM (and more high-end a/d converters) have a range of sampling which is not centered around zero. The front end of the compenstates of the FAM for this by applying an offset from the signal which would appear to the user that the range of the ADC is centered around zero. What is different between this FAMILY and other instruments, is that it is not an additional circuit preventing that this lag observed a user of height of the output of the analog input.

    You see the shift happen to reference open FPGA is because that's when power to the GPA is activated. The shift should not have an effect on reading which provides the analog input. Just make sure you have impedance corresponding to the source of the signal at the analogue input and you should be good.

  • NEITHER 9234 with quasi static analog voltage

    Hello

    I have a NI 9234 (4 channels + / IEPE 24-bit 5V) attached to a chassis cRIO module. This module is ideal for accelerometers and microphones where the tension is in constant evolution (ie; measures of variation rates).

    I also have a module OR 9237 (4 channels 24-bit full-bridge module analog input) attached to the same cRIO. This module is ideal for measure variable voltages of strain gauges (quasi static and dynamic loads).

    The attached graph shows the two channels, collected synchronously, but as you can see the (red trace) cell breaks down (as it should), but then drifts back to zero on its own, when in fact it should remain low just like the extensometer is beam. After all, the two sensors are physically secured.

    Q1: Would that have something to do with AC/DC module 9234 internal coupling?

    Q2: Is it really possible to collect "quasi static" ongoing tensions by using a NI 9234 module?

    No explanation as to why this occurs, or if there is a way to remedy this would be appreciated.

    Kind regards

    Andreas

    Coupling AC/DC must do a lot with your question. In mode AC voltages static will be fitered outside and the 9234 measure indeed only change voltages. In DC mode, the voltage goes directly to the AD converter and you can also detect static tensions.

    A minute of Googling gave me the answer, this load cell electric piezo can measure dynamic changes, as any charge will escape the path the lowest resistance and the signal will go to zero after a certain time. I guess the other device you were using higher internal resistance (which is relatively low on the 9234), so it takes more time to what he flees, but he also took on the picture you attached your second try.

    Here you can find more example under the title

    "WHY ONLY DYNAMIC FORCE CAN BE MEASURED WITH SENSORS OF POWER PIEZOELECTRIC"

    http://www.PCB.com/techsupport/tech_force

    Andreas Jost

    Technical sales engineer

    National Instruments

  • Assistant OR-9234/Sound and Vibration: being reset to zero (crazy) automatically input signals

    Hi all

    I have a voltage source and a force as entries in a sensor module DAQ 9234.

    The software focuses both signals whenever they change. For example, if the voltage is read by data acquisition increases up to a constant value, the software will trace an increase in tension, followed by a slow return to zero. Similarly, if I increase the force applied to the force sensor and keep it at a constant value, the program will draw an increase in force, followed by a return to zero.

    Here is a graphical representation of the problem, which uses the sensor force for example:

    The sensors are passive. The sensor is a PCB 02 208, and the source of tension comes from a LDM-1000 signal conditioner, which receives a signal from a MHR 250 LVDT. By the LVDT core displacement changes are interpreted by the signal conditioner, which translates as the measure of a voltage value that can be read by data acquisition.

    Thank you in advance.

    I assume you have the rule 9234 on coupling AC mode, while you should use DC coupling.

    -AK2DM

  • Scope of digital storage of the homebrew: falling for the third time.

    I worked on an extended application of digital storage 5114 with most of the features of the NiScope

    Soft front and making little progress. The only approach I could think of was to start with an example provided

    and then modify it. I need to acquire several second waveform non-repetative @ 125ks/s, which is equivalent to 500 k

    samples. The Acquisition example configured to trigger dashboard will make me the waveform, but there over time. I need an application that will acquire the waveform, whenever it is triggered and hold until the next trigger. The applocation Soft Front Panel does well.

    As to why I'm just not using the S.F.P is twofold:

    1. I need to be able to isolate sections of the acquired waveform and calculate the effective as voltage peak to peak

    sections. I also want to make the integration of point by point to the area under the part of the envelope of the waveform.

    2. I tried to save the data of the S.F.P., but so far haven't had any success even open files.

    Koutcheens

    Attached is an example of NOR-SCOPE (which never shipped) that implements the exact algorithm used to extract data by the NO-SCOPE Soft Front Panel (SFP).  Essentially, it starts an acquisition and uses only an extraction when the acquisition is known to be complete.  It will never expire.

    By default, the SFP OR-SCOPE records in the format of hierarchical storage OR waveform (OR-HWS), a binary format.  "" "You can find OR HWS screws in the measure i/o" OR-SCOPE "Utility Functions" OR hierarchical waveform storage palette.  NOR-HWS is based on HDF5, so can be opened and read by all who reads HDF5.  The internal format is very similar to The SCPI-DIF, but put in a wrapper HDF5.  If you want more details, please ask.

    Example is saved in LabVIEW 7.0.

  • 3 voltage/current measurement channels, crosstalk between channels

    Hello

    I am running a NOR-USB-6211 is connected to an instrument that runs labview 8.5. What I want to do, it's current 1 and 2 channels of voltage measurement channel. All are separate physical channels. I use an express VI to separate the 3 channels on the box USB-6211 and trying to draw on maps of distinct waveform stacked in a way that it respond independently (as they should be physical separate circuits). I can ALMOST that it works. I can measure the current very well. The problem is with the tensions. If I change the voltage on channel 2, channel 3 meets both equally (eg. increase 5V on channel 2, channel 3 increases of 5V); However if I change the voltage on channel 3, channel 2 does very little (such as increase of 5V on channl 3, ~0.05V increase to channel 3). Not the best result, but better than the reverse. Channel 1 is not affected by changes in voltage, but it affects the Channels 2 and 3 (current increase, increase of tension of channel 2 and 3). I have no idea why this is happening. I saw the same thing when I used only 2 channels (current and voltage). When the current (channel 1) is changed, the (channel 2) voltage changes, but when the voltage, the current does not work. There must be a problem with the program because I get the same behavior when I physically disconnect channel 3 (for example, always responds when I change the voltage of channel 2). It seems like it should be a simple installation and a simple solution, but I can't understand it.

    I've included a snapshot of the program. I share the channels so I can selectively save some data in a file. I tried to simply connect the VI express to a graphic, and does not either (tensions influence each other). I also tried to replace the cluster with a table, but that did not work or the other. I tried to simulate the data with sine waves and I can get this to work without problem. I don't know what I can do.

    Thanks for your help.

    The f

    interference of signals of high-level signals at low level is normal with inputs high impedance of a multiplexer.

    put a short channel shorted inbetween and measure this also but throw the zero.

  • Tracing a position using two voltage on a graph signals in LabVIEW

    I am a new user with LabVIEW and I got 4 analog signals with a detector sensitive Position of duo-lateral (PSD) and then I made math on them and then reduce to two (coordinates X and Y). PSD will give the position of the signal in terms of tensions. If the position on the PSD is in the Center then X and there will be zero and the position of the signal on the signal changes the X and Y voltages are changing, so we get the new position. Now I want to do is draw the co-producers of the signal on the DSP on a graph in LabVIEW simultaneously. I'm simultaneously sampling at the speed of 1 kHz.

    Can someone help me with this application?

    Thank you


  • Blocking of blue screen with the analog voltage (WinXP, PCI-6251)

    Hello

    I'm looking to solve a problem of blue screen with my measure blocking
    application, which I am developing with C++. Blocking seems manifest
    a little random after a variable amount (500-50 000) of voltage analog
    measures. My application needs to make a huge amount of these digitally
    trigger voltage measures after a certain period of time, and I'm using a
    unique
    task to do. The task is stopped and started after a single measure
    is
    which is done around 10 000 - 100 000 times per second. For this
    because I do synchronized with the PCI-6251 map data acquisition and
    one
    Ztec oscilloscope card. It seems that the probability of blocking could be
    associated with
    the frequency of measurements of voltage that I perform.

    The
    the app itself is multithreaded, but I'm blocking concurrent access
    TO
    the card with lock - all access to the card are behind a single mutex

    lock, so simultaneous access is blocked. In any case, all data acquisition
    access
    o the map is initially a single thread, which is dedicated to the acquisition of data
    operations.

    I also did stress tests with Ztec scope map, which does not
    result
    in all the problems. I also disabled in order of acquisition of Ztec map data
    TO
    Make sure that it wasn't the card scope, the origin of the problems - the problem
    persistent, so this seems to point towards the direction of the nidaq map.

    The deadlock appeared when I used the original supplied with drivers
    the
    card. I installed the latest drivers (removed the device from)
    ' Windows
    Device Manager and your application Measurement & Automation, reinstalled), but the blue screen still appears.

    Blue screen gives me a few debug data, but it does not mention any

    files .dll or something that would be of course point to a specific file (driver). I enclose at least partially matching code snippets.

    Hello again! I've been in contact with a local support person, who suggested that I have use DAQmx_Val_FiniteSamps instead of DAQmx_Val_HWTimedSinglePoint. I don't have any other changes, but this (see below) and the problem disappeared, so this seems to be an acceptable solution, because I don't see at all why not do this way. (Thanks Henry!)

    DAQmxErrChk (DAQmxCfgSampClkTiming (task_reader, NULL, 100000.0, DAQmx_Val_Rising, DAQmx_Val_HWTimedSinglePoint, 1));
    DAQmxErrChk (DAQmxCfgSampClkTiming (task_reader, NULL, 100000.0, DAQmx_Val_Rising, DAQmx_Val_FiniteSamps, 2));

  • Card bad voltage outputs data acquisition / cut off voltage

    Hello

    I use a 6713 PCI and PCI MIO 16E1 and have a very strange problem: when I try out a voltage using LabView, I get instead of the voltage, a tension cut with a high unstable phase. Basically, all right, as long as my blood pressure is below 0.3V. All is well here, high level is stable, precise curve shape. But as soon as it exceeds 0.3 V, it is cut and the tension starts to drift. I have attached a drawing of the problem in this post.

    The system worked very well, but a week ago, the problem appeared. First he went again, but now he reappeared. The first attempt to define a certain tension might work, but already for the next pulse the problem occurs. Now she even work correctly once. Reboot etc did not help.

    The funny thing is, however, the same PC has two features listed above. I only and never used the PCI6713. When the problem occurred, I tried to move to the MIO 16E1 but it shows the same thing! Exactly the same problem here! I unplugged all the wires to the cards and it still does not work. Anyone here with an advisor?

    Thank you!

    Mike

    I was able the output voltage with a scope with 1 MOhm input impedance. But I found the problem by chance now! We got a whole batch of defective cables BNC! I already suspected the cable and tried different cables, about the same result. Then somehow, as I wrote, the problem disappeared once. Now, I used another type of cable to test the unit and it worked! So I checked the other BNC cables, and some of them seem to have a shortage between the mass and the Center, but in a way it produces sort of a junction diode (probably because of a layer of oxide somewhere). When I shook the cable suddenly I could measure a low impedance between the mass and the Center, but only for milliseconds, just like a bad contact.

    Really weired! But thanks for the help!

  • voltage

    I am in a position the output of a piezoelectric sensor.  It's just a generator of analog voltage with output to two pins.  Rated power rises almost a volts peak to peak, and when I have those two pins feed scope, I see exit in this neighborhood when I stimulate (type on) unit, at least rise above 400mV peak-to-peak.

    Now, I would like to read this same sensor via a USB-6009.  I had no luck in unbalanced mode (almost all the noise), but the signal seems correct in differential mode.  If I connect a sensor just to the AI0 + and AI0 - pines on the 6009.  I do all my tests in the "Test Panel" Max right now.  I have install the channel, generally defined entries max/min 1 and -1, respectively, than the configuration entry in the "differential", set the "continuous" mode and the rate to 1000 Hz and 'samples to read' to 1000 (so the screen is updated once per second).

    Here are the two questions I have:

    Output overall is a very low reading compared to what I'm used toseeing on the scope.  Instead of hundreds of millivolts, I see more as 60mV peak-to-peak.  Signal-to-noise isn't bad, but I feel it could be much better, and it's better when I read the same signal on other devices (a scope, for example).  Some advice on why I see this output low voltage when wiring in the differential analog inputs on the 6009?  Here is a picture of my capture window:

    * Second question: almost every time that I have to stop and reset on the device, I get the following error:

    I have to unplug the device and taking again to make it work again.  There is nothing particularly CPU happening on my machine, I am not anywhere near the limit of bandwidth of the device or bus and it feels not like it's really a matter of charge anyway since it works _always_ the first time I press 'start '.  Soft-reset the device does not help when this happens, I need to unplug the device and plug it in again.  Any ideas what might be happening here?

    Thank you!

    -Dan

    A piezoelectric sensor generates a charge and has a very high impedance. The correct way to fit your 6009 is a charge amplifier. It is possible to measure the power as a tension, however you need at least an amplifier with a very high impedance of entry AND short cables Hat!

    If your results are very reasonable take a look at the two devices input impedance.

    Depending on your skills to weld a simple (maybe not so linear) charge amplifier can be build with a high, low impedance input amp bias current op and a capacitor (poly) > resistance 10 M...

    Take a look at this LT1113 OP

    or the LMH6611.

  • Generator functions agilent modulated the amplitude of the voltage so that the signal

    Hello

    I'm new on the Labview.

    I need to provide a series of tensions with increases step on my device and it repeats again and again.

    For example, (5V 0V to 10V 0V 0V 15V) * 5 times

    In the past, I turned down on the generator Panel of Agilent 33220 functions by myself.

    It's stupid, so I will try to use the Labview to do the same.

    I have download the Agilent 33220 Vi function generator has and write a loop for to do this. It can work.

    But I found a problem. Each change of amplitude voltage, generator Agilent 33220 A functions will cease to exit and then output the new value.

    Because this short period of no output voltage, the dynamic behavior of my device will be destroyed.

    How can I do?

    You made a classic mistake. You have placed the Initialize and close inside the loop. The Initialize will, by default, perform a reset feature, which disables the output. Initialize outside a loop, do your stuff inside and close the loop.

    Regarding your code: I strongly recommend looking at the model of ramp function. It seems you want to increase the parameters of voltage to zero between the two. This can be easily done by creating your rising tensions ramp and then creating another matrix of the same size zeros and interlacing then the two tables. This will give you a complete range of voltage values, without to need two loops and determine what step you are on, etc. etc. For example, the following code will give you 5, 0, 0, 10, 15, 0 sequence fairly cleanly:

    In addition, never perform a comparison of equality on the floats. If not, you owe me nickel one another in my retirement fund.

  • scope and read the significant digits vi

    Hi all

    Let me start by giving you some background.

    I'm measuring a RMS (approximately 1.8V) voltage using NOR-Scope read Vi, which works very well, my problem is that I also try to calculate the current RMS within the same Vi, using a known resistance. With the voltage, I have only two significant digits using playback OR-Scope, which gives me too much a rounding error, when it comes to the current problem.

    So my question is this; is there another stock Vi that I could use to increase the number of significant digits to get or is it possible to increase the number of significant digits with the Vi? Other ideas are welcome and thank you for your help.

    I don't know what is this 'NO-Scope reading measure Vi', but how many significant digits you put your indicator (right click, properties)? If this does not help, please contact your VI.

    Cameron

Maybe you are looking for