Search the Community

Showing results for tags 'discovery'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 16 results

  1. Tonym

    LabVIEW issue with Discovery 2

    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!
  2. Hello, I'am writting my own software to setup an Analog Discovery 2 device and conduct some mesurements in C# using SDK library and wraper. I can connect with the device, disconnect and even retrieve some information such as serial no. I would like to have some sort of protection in case if device is rapidly unplugged from computer. In this particular circumstances in Waveforms software an error will occur. I have tried some sort of checking with use of enumerators but enumerators works poperly when device is connected. When device is disconnected last status is remaining and no error messages are visible. What I hve to do to solve this problem? Connecting with device: public bool AD2_Connect(ref int AErrorCode, ref int ANoOfAD2Devices) { bool AIsConnected = false; string AVersion = null; string ADeviceName = null; string ADeviceSn = null; // detect number of all connected supported devices dwf.FDwfEnum(dwf.enumfilterAll, ref ANoOfAD2Devices); // open automatically the first available device if (dwf.FDwfDeviceOpen(-1, ref hdwf)==0) { AIsConnected = false; } else { dwf.FDwfGetVersion(out AVersion); //get veriosn dwf.FDwfEnumDeviceName(0, out ADeviceName); //get device name dwf.FDwfEnumSN(0, out ADeviceSn); //get serial no AIsConnected = true; //set flag } dwf.FDwfGetLastError(ref AErrorCode); //get last error code string AErrorMsg = null; dwf.FDwfGetLastErrorMsg(out AErrorMsg); //get last error message return AIsConnected; //return flag } Then I need to check if device is still connected. My version of chceckig if device is disconnected or connected, but it doesn't work. int AIsUsed = -1; int ADevicesNo = -1; dwf.FDwfEnum(dwf.enumfilterAll, ref ADevicesNo); dwf.FDwfEnumDeviceIsOpened(0, ref AIsUsed);
  3. agnichatian

    Waveforms Script Printing

    Hello, I have an Analog Discovery (legacy) and the latest Waveforms app. I am trying to write a script that makes the protocol module write to a 24C16 eeprom, read it back, and print to the screen or window. I can access th I2C (can see on my scope), but I can't print anything. The print() function does nothing unless in debug mode, but then the app seems to hang. I tried Custom mode and Sensor mode. And I tried the ADXL345 example, with a known good breakout board, and it always returns the same thing, doesn't change with orientation of the chip (but my main concern is the eeproms) Why is the output window at the bottom of the script area only one line long. The only thing that shows up there is the results of return statements. How can I see the I2C and run the script at the same time ? The logic analyzer only shows the first two I2C bytes, so I'm using an external scope. What does the manual mean when it says the the I2C can only send when in debug ? Isn't that a show-stopper ? Am I missing some key piece of documentation ? The manual does not say much about how all of this stuff works. - Thanks
  4. Hello I am a user of Analog Discovery2 and I believe it is missing one very important (for me at leas) function. I basically want to monitor and register the communication between two devices which use UART to do so. The Protocol panel looks great but I am able to register only one of the devices at the same time. Logic panel is very unfeasible in my case because I want to register many lines of the communication (like 5 min). Is there any way I can achieve that? Maybe there is a custom script which would help in my case?
  5. Hi Folks Although the Analog Discovery has fully differential analog (scope) inputs, the Discovery BNC adapter board does NOT! For some reason the negative inputs of both analog channels have been connected to the Analog Discovery ground. Therefore, they form a short circuit between any conductors they are connected to. Why is this important? I just found out the hard way, when I connected the scope leads from the Discovery BNC adapter board to parts of a circuit at very different voltages. I was expecting each channel to measure the differential voltage across each probe. Instead, there was a crack, a flash, and a little jet of molten metal, as the clip on one of my scope probes vaporised! IMO this is a safety hazard, because adding the Discovery BNC adapter board to the Analog Discovery changes its electrical behaviour in a significant way (from differential to single ended) but there is no mention of this in the Discovery BNC adapter board reference manual. Users should be warned in BIG LETTERS about this change in behaviour, perhaps printed on the PCB as well. I was lucky, but providing users with a warning about this could save somebody's life one day. I can see that grounding the negative inputs could make sense, in that it makes the analog inputs behave more like a conventional oscilloscope, where the probe shields are usually returned to Earth. However, if you're going to do this you should at least warn users about what you've done. IMO it would be better to provide 4 sockets for scope probes, with each connected to one of the differential inputs, and all the scope shields returned to Analog Discovery ground. Then the Discovery BNC adapter board could be used for fully differential measurements. You could also provide jumpers to select single ended behaviour instead, by shorting the negative inputs to ground. At least that would give the user a choice about whether to operate as differential or single ended inputs.
  6. Hello all. New to WaveForms, so excuse me if this is too easy. I'd like to capture an analog channel, and two digital ones - where information is encoded into the width of the pulses. Sure enough, I can do this. But of the digital, one is PWM, which I'd like to manipulate into the corresponding stream of percentages (or 8-bit values, does not matter); the other one encodes the duration of something - therefore I'd like to measure their positive duration, as in a timer/counter... Can this be done in WaveForms with the AD2?
  7. Hi, so I am trying to complete a project for one of my classes and I decided to us the script part of the analog discovery; however, there is not enough comments on the code to explain what it is specifically doing. I found an example code that is titled "Wavegenpiano". I would like to know if someone can explain what that code is doing., ie, what each part of the code is doing. I would like to use that code associated with a buzzer to output a song. TL;DR How can I use the script part of the analog discovery to have a buzzer output out a sound?
  8. """ DWF Python Example Author: Digilent, Inc. Revision: 2015/02/05 Requires: Python 2.7 Start synchronized the AWG outputs of multiple Analog Discovery devices. Connect the Trigger-1 pin of each device together. """ from ctypes import * import time import sys if sys.platform.startswith("win"): dwf = cdll.dwf elif sys.platform.startswith("darwin"): dwf = cdll.LoadLibrary("libdwf.dylib") else: dwf = cdll.LoadLibrary("libdwf.so") #print DWF version version = create_string_buffer(16) dwf.FDwfGetVersion(version) print "DWF Version: "+version.value cDevice = c_int() dwf.FDwfEnum(c_int(2), byref(cDevice)) # 2 = enumfilterDiscovery print "Found "+str(cDevice.value)+" devices" cChannel = 2 cOutput = cDevice.value*cChannel hdwf = c_int() #open device for iDevice in range (0, cDevice.value): dwf.FDwfDeviceOpen(c_int(iDevice), byref(hdwf)) if hdwf.value == 0: print "failed to open" quit() for iChannel in range (0, cChannel): print "Configure "+str(iDevice+1)+"/"+str(iChannel+1) # enable channel dwf.FDwfAnalogOutNodeEnableSet(hdwf, c_int(iChannel), c_int(0), c_int(True)) # 0 = AnalogOutNodeCarrier # configure dwf.FDwfAnalogOutNodeFunctionSet(hdwf, c_int(iChannel), c_int(0), c_int(1)) # 1 = funcSine dwf.FDwfAnalogOutNodeFrequencySet(hdwf, c_int(iChannel), c_int(0), c_double(1000.0)) dwf.FDwfAnalogOutNodeAmplitudeSet(hdwf, c_int(iChannel), c_int(0), c_double(1.0)) # set trigger source to external trigger 1 dwf.FDwfAnalogOutTriggerSourceSet(hdwf, c_int(iChannel), c_byte(11)); # 11 = trigsrcExternal1 #set different phase iOutput = iDevice*cChannel+iChannel dwf.FDwfAnalogOutNodePhaseSet(hdwf, c_int(iChannel), c_int(0), c_double(360.0*iOutput/cOutput)) # start the channel, this will wait for the trigger dwf.FDwfAnalogOutConfigure(hdwf, c_int(iChannel), c_bool(True)) # configure Trigger-1 pin to output the triggerPC signal for the last device dwf.FDwfDeviceTriggerSet(hdwf, c_int(0), c_byte(1)) # 1 = trigsrcPC # after open, before the first run wait a bit for the offsets to stabilize time.sleep(5) print "Pulse trigger to start generation..." dwf.FDwfDeviceTriggerPC(hdwf); time.sleep(60) print "done." dwf.FDwfDeviceCloseAll()
  9. I'm trying to take accurate readings using the "Logger" module in Waveforms 2015. When I power up a simple DC circuit with +5V, and use a DMM I get readings of ~4.44 volts. However when I run the data logger module, all of the readings are <100 mV. Shouldn't the logger be reading ~4.44 volts, or is there some configuration I am missing Thanks in advance!
  10. Hello, I'm a newbie using the Analog Discovery (Legacy), and attempting to run through a few experiments. When using the Power Source or "Supplies" tool in Waveforms 2015, all the directions and manuals show a dropdown menu where you can adjust the voltage (0-5V). The manual from Digilent's own website SPECIFICALLY regarding the Analog Discovery Legacy shows this as an option as well. I can't find any such option however in my program, it just isn't there. I should mention that I am powering the AD itself via USB from my laptop, but I don't think that is the issue as according to the status I am outputting ~5V via USB just fine, and the manual also shows the dropdown while being powered by USB. I also don't know what the little green bar underneath is supposed to represent, as it moves up only partially seemingly to random places when I turn on the "Master" enable, in case that it something to be concerned about. Any help is appreciated. Thanks!! P.S. Sorry for the re-post I realized I put this question outside the "Waveforms" Forum.
  11. Hello folks, I'm a newbie using the Analog Discovery (Legacy), and attempting to run through a few experiments. When using the power source tool via Waveforms 2015, all the directions and manuals show a dropdown menu where you can adjust the voltage (0-5V). The manual from Digilent's own website SPECIFICALLY regarding the Analog Discovery Legacy shows this as an option as well. I can't find any such option however in my program. I should mention that I am powering the AD itself via USB from my laptop, but I don't think that is the issue as according to the status I am outputting ~5V via USB just fine. I also don't know what the little green bar underneath is supposed to represent, as it moves up only partially seemingly to random places when I turn on the "Master" enable. Any help is appreciated. Thanks!
  12. mschambe

    Digital Discovery

    Can the Digital Discovery logic analyzer be configured for state analysis? Specifically, can you designate one of the IO's as an input clock source and choose the appropriate edge for capturing data?
  13. Hello, I have an Analog Discovery and I recently installed WaveForms version 3.3.5 (I actually found it a bit ambiguous how to install WaveForms. I attached an image below of the files I downloaded from Digilent. All I did was click and drag the framework into the corresponding directory and likewise for the application. Then I ran the driver installer). I am running Mac OS X El Capitan 10.11.5 on my Mac laptop. When I look under the USB device tree in System Information I can see "Digilent USB Device" but when I open up WaveForms it alerts "No device detected". Would anyone know how to solve my issue by chance? Any help is very much appreciated.
  14. dgwalsh

    BNC Adapter

    What advantages does the BNC adapter offer to the first generation Analog Discovery?
  15. attila

    Waveforms-3 On Zybo

    Here you can find instructions on how to set up Linux and WaveForms 3 for Zybo: http://www.instructables.com/id/WaveForms-Analog-Discovery-on-Zybo/
  16. BlacKnight

    Anaolg Discovery USB isolation

    Hi Folks I'm using an Analog Discovery. For my current project I need to isolate it, but it doesn't work when I try to connect it with a USB isolator. According to the manual... I've tried USB isolators from 2 different manufacturers. The Analog Discovery doesn't work with either of them. When the device connects I get an error message during device configuration (image attached). Is it possible that the software has changed so that it now doesn't work correctly with a USB isolator? It may be a timing issue during configuration, since the isolator only runs at 12Mbps. If so, is it possible to download an old version of the software that does work with a USB isolator? Any help would be appreciated.