Tonym

Members
  • Content Count

    6
  • Joined

  • Last visited

  1. Hello @attila, I am trying to generate signals around 500Hz with my AD2 and display these on a scope graph in LabVIEW. However, it seems as though time base is .0004 seconds, which is too small to see my signals. When I extend the time base, the scope graph still only displays .0004 seconds worth of data. If this is due to the sampling rate of the AD2, how can I change the default sampling rate so that when I run the AD2 in LabVIEW I am able to see more of my signal? Thank you.
  2. I have actually solved the issue above, but does anyone know if it is possible to extend the time base of the wavegen graph longer than 0.0004? I want to generate signals around 400Hz, but the sampling rate of the scope seems to be too high because it only displays a small section of the signal, and thus I cannot see the signal on the graph. Setting the time base to something longer does not fix the issue which makes me think that it may have to do with the sampling rate of the AD2? @JColvin @jpeyron
  3. Hello @JColvin, Thank you for the suggestion. I am using LabVIEW 2018. I have downloaded the LabForms VI, but it does not seem to be working properly. The first time I opened it, I was able to select how many channels for the wave generator, but after running it once, I was not able to change the wave generator as it seems to have disappeared. I am not sure why, but think it may be due to the newer version of LabVIEW I am using? This is what I see on the Wavegen tab.
  4. Yes, I have tried using the toolkit, but it has not helped with this issue. With the VIs provided in the toolkit, I am still unable to successfully use the AD2 with LabVIEW. I am trying to use the wavefunction VIs to send a signal out of one of the BNC outputs on the AD2 and back into one of its inputs, to then be displayed in LabVIEW. I am also trying to use the other BNC input for taking in another signal. I then want to display both the generated signal and the measured signal in LabVIEW. However, I am not able to Connect with the AD2 despite the correct device name. In addition, in the past in other VIs, I have been able to get a signal sent through the AD2 and displayed in LabVIEW, however there only seems to be 10 micro seconds worth of data to be displayed, which is too small of a window to see my signals. Extending the time base on the graph does not help, as it still only displays 10u of data. Do you or anyone know of how to fix these issues? Thank you for your help!
  5. Does anyone have a good overall understanding of the interaction between LabVIEW and the Digilent Analog Discovery 2? I am having some issues and would like some help. Thank you.
  6. Hello, I am working on a project that involves using the digilent analog discovery 2 to act as a an input and output for a VI in LabVIEW. I have downloaded the Adept and Waveforms software to communicate with the discovery 2 and LabVIEW. In this VI, I am getting an error number 1097, which has to do with the call library function. The error is in an attached photo. I have tried the suggested fixes online but have not found one to work for me. The error does seem to occur at the sub-VIs I downloaded from National Instruments, built to work for the discovery 2 in LabVIEW. When I open the call library function of the sub-VI that seems to raise the error, I see the attached images. Does anyone know if the set values are correct or if I need to change something? I am hoping that the error may be fixed by changing one of the parameters or options listed. The following links shed light on the 1097 error in LabVIEW: "Error 1097 Occurred at Call Library Function Node" https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000PAckSAG&l=en-US "Error 1097 While Calling DLL with Correct Calling Convention" https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9bHSAS&l=en-US Thank you!