06-20-2015 10:22 AM
06-20-2015 10:30 AM
06-21-2015 10:02 AM
You've posted no code, given none of the technical details (like a full description of the signal), talked about none of the hardware (I'm assuming a fast D/A converter), and not given any indication of your level of familiarity with LabVIEW.
I'd never used the Simulate Arbitrary Signal Express VI until Altenbach suggested it, but it took about 3 minutes to get a set of pulses of varying widths and heights appearing on a Chart on my PC. While I don't particular love the Dynamic Data wire, it does plug into a Chart nicely, and there are functions to convert it to other "more traditional" LabVIEW data types.
Provide us with more information (especially code!!!) and we can be more specific (and thus helpful) for you.
Bob Schor
06-25-2015 12:37 AM
Thank you all. I have been successful in developing the signal using ARBITRARY signal generation.
07-14-2015 06:36 AM
Respected Sir altenbach ,
I need to send the signal to Agilent 6642A dc power supply(0-20V, 0-10A) having gain of 4, for ampilfication and it will be used for my experiment. I am facing problem here.
I am using GPIB USB HS for sending the signal and when I am sending commands *IDN , it is successfully reading and writing, which means I have all my softwares and drivers installed perfectly. I have NI MAX and command expert installed in my pc.
I have made a program (which is attached) in labview and the GPIB seems to read it ( ACTIVE/Green signal is showing when it is run) .
But I cannot see it in oscilloscope (Tektronix TDS 2024B) which means something is wrong here. I need the see the signal as shown in the image attached.
I want to see the signal in the oscilloscope as well.
Can anyone tell me what is wrong in the program attached? The voltage seems to go upto 1v but suddenly drops at 0.37v and remains constant no matter what I do.
I want to control the DC thorough labview.
Thanks.
07-14-2015 06:39 AM
Screenshots.
07-14-2015 08:22 AM
It would really help us to help you if you posted code, not pictures of code. Not only are the pictures difficult to see, sometimes, but if we want to test part of your code, we have to "do all of the work" of manually re-creating your code ourselves. We are willing to help you, but the least you can do is to save us some manual labor (think about our poor, tired fingers).
If your code involves important sub-VIs (such as the one called "Configure.vi" that I notice), you can include it, as well, by attaching a ZIP file of the relevant VIs that you use.
Bob Schor