Jump to content
  • Similar Content

    • By Gab
      Hello Everyone,
      Need some verification with daq program.
      I have one force sensor that connectd with my usb daq device. with this force sensor, unknown object is connected(hanging) and i want to find the mass of this object (F=ma) so i am taking continous sample and generate waveform graph. After the scaling, my waveform will be in Newton unit.
      my question is: if i take RMS of this waveform(1d Array data point) and divide by g (9.8 m/s2) then whatever value come is my correct mass? (F=ma).
      Thank you in advance
    • By Atron100
      hi
      i have a question in basic understanding of update rate sample rate samples per buffer and cycles per buffer.
      i have DAQ 6343 and electronic circuit. 
      i'm using AO0 for generation sine wave at these frequencies 10Hz, 100Hz, 500Hz, 1kHz, 3kHz this signal enters to electronic circuit.
      and after conversion i must to measure two outputs of this circuit by AI2 and AI3.
      from my understanding of tech spec of the daq analog output update rate is 900kS/s and analog input update rate is 500kS/s
      as i understand if i have freq = 3kHz the maximum sample rate per buffer is 300 samples
      and if i have freq = 10Hz i can generate this signal with 90000 samples per buffer?
      for analog input the formula is the same?
      that meaning of cycles per buffer?
      which sample rate of AI i need to setup to measure data fast and accurately? 
       
      thanks for answers
    • By _Y_
      I am trying to implement a simple DAQ Watchdog with single digital output but cannot find any logical way to reset the Watchdog timeout signal. One of obvious solutions is invoking DAQmx Reset Device.vi. Unfortunately, it does not work. The Watchdog goes to timeout state but the physical output signal does not turn to High.
       
      For some obscure reason (typical non-qualified guess:) I added bottom part of the code that is red-framed in the BD. The only difference between functional and non-functional code is using DAQmx Start Task.vi, that is located in “Solutionâ€-driven case structure. If Boolean control “Solution†is True, the code works; if False, it doesn’t.
       
      Please help to understand why launching conventional Digital Output task is necessary for normal functioning of the Watchdog?
       
      PS: Attempts to use clear expiration command instead of DAQmx Reset Device.vi were not successful.
       
      PSS: HW is PXIe-6358
       
      PSSS: Unfortunately, I cannot post any image here. Any image format results in "You are not allowed to use that image extension on this community" . The VI is attached.
      watchdogTest150817.vi
    • By pkeny
      Hello,
       
      I have created a vi that controls multiple writes (individually) by a switch. I have it so one individual switch controls one individual write (And is linked to individual clear, stop, error daqmx blocks). I do not think this is efficient as it takes about 4-6 seconds for the switch to actually write (True or False). 
       
      So, I was wondering if someone could help me make my code more efficient so it would run a bit faster.
       
      Thank you
      Digital Outs fine.vi
    • By CANewbie
      Hello,
       
      I think this topic is very important for everybody that are doing advanced DAQ. Because it you want to save an event, you need first to see it(real time analysis), and than to save the transition how the event happened(that means to have values, before the event happened). Using consumer producer structure.
       
      i'm trying to save data into some kind of buffer. my main goal is to delay values. I successfully created a delay using Delay values.vi, the problem is i think it makes the while loop slower. If anyone knows what is a good practice to create a delay for large amounts of samples 100k, 200k, 300k samples? Is a delay values.vi good practice, or is there another better way?
       
      Thank you
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.