Search the Community

Showing results for tags 'analogdiscovery2'.



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 8 results

  1. Hello For a project I have to analyze two analog signals at a frequency of 78.4 kHz. Sampling rate must be at least 1 MHz. I have a Analog Discovery 2, I generate for now a signal square of 100kHz. I can observe this signal but only on a few periods. I wish I could get them back on a spreadsheet excel in order to treat them with Matlab. I can get a spreadsheet excel, but only with 8000 values, or I would need 1M values. Is it possible with a Analog Discovery 2 ?
  2. Hi all i am using Analog discovery 2 for communication purpose.(CAN) I tried using the sample code given same as attached. I am using PCAN to send/receive frames to analog discovery 2 , I am sending only one frame with Standard ID : 0x011 and Data: 0xaa 0xbb 0xcc 0xdd 0xee 0xff but i am receiving lot of Frames with the same ID sent, lot of extended remote frames with CRC errors ,etc. I have attached the console output for reference. Can I know why i am facing the issue? I tried same experiment with waveforms still having similar issue. I have attached the screen shot of it. Digital_Can.py CAN_Console.txt
  3. I am using analog discovery 2 to send/Receive signals with PCAN using python. Do i need to have a CAN transceiver IC to convert from CAN-H/L to CAN-Rx/Tx? Also wanted to know if i use Waveforms software, what is the hardware connection?
  4. Hello all, I am trying to read data from an Analog Discovery 2, but I am a bit confused by the FDwfAnalogInStatusData16() function. I would prefer to have the raw integer data from the AD2, as I want to histogram them and I would have to convert back the doubles to integers. On the include file of the C API it is written DWFAPI BOOL FDwfAnalogInStatusData16(HDWF hdwf, int idxChannel, short *rgu16Data, int idxData, int cdData); and I do not understand the difference between idxData and cdData. I tried to guess from the buffer sizes with no success. Reading from the AD2 I know that the maximum buffer size is 8196 (is this per channel?), so I thought that the idxData parameter is an index of the waveform and that the available samples (that I read with FDwfAnalogInStatusRecord) are a multiple of the buffer size (that I set with FDwfAnalogInBufferSizeSet), but it is not the case. May I ask for a quick example on how to use FDwfAnalogInStatusData16 to read both channels? Thanks
  5. It appears that the AD2 power supply selection does not automatically switch to external power when plugging it in after it has already been connected via USB. 1. Connect the AD2 via USB cable 2. Start waveforms2015 3. Connect external power supply(5V -3.5A) From time to time a failure appears like DptiIO failed ERC: 0xA. On Linux this issue is made worst by the fact that it appears a lot more often than on Windows even in the middle of operation of the device. This appears even without the external power supply. Something similar appears on Linux saying that the USB port did not provide sufficient power. Even if the power supply is connected later on, the issue still appears. The only way to solve this is completely disconnect the USB cable, plug in the power supply cable, then plug in the USB cable. The version of Waveforms2015 used is 3.5.4 64bit. On both Windows 7 and Linux the same version is present.(with the latest ADAPT software installed on Linux). The device is put in mode 4 with only Logic and Patterns enabled and memory allocated for them. Is there any way to solve this? Thanks
  6. We are currently using an AD2 as a data acquisition device in a configuration in which an external trigger is delayed by the DigitalOut device and then routed to one of the AnalogIn channels to trigger the latter. The DigitalOut generates its trigger on digital i/o line 0. We now wish to use some of the other digital i/o lines for simple i/o. The question is can we do both things at once: namely, trigger digital i/o channel 0 with the DigitalOut device while using digital i/o lines 1-15 as simple Digital I/O devices? Our guess is that we can use lines 1-15 for digital input but not digital output. We'd very much appreciate any insight into this issue.
  7. Working on Debian 8.6 in python 2.7, trying to figure out what the 'ready' state of the AD2 means and how I can get back to running mode. We configure the AD2 to run continuously, collecting multiple subtraces and combining them into a larger trace. The system happily runs, sometimes for hours or days, reporting states of 'arm', 'triggered', and 'done' repeatedly. But at some point with an unknown-to-me cause, it flips to a 'ready' state and our data collection stops. I don't know what FDwf python command to issue to get it back to triggering and taking data. As it is, I close and delete the python AnalogDiscovery object and create a new object, thus re-initializing our AD2 connection. But my guess is that I shouldn't have to do this to start up again. Can someone tell me to proper way to get back to taking data after getting bumped out to 'ready' state? Thanks.
  8. We're using the 64 bit packages for Debian, writing our own python 2.7 code to access the provided AD2 library using 'ctypes' module. I'm trying to track down a tricky bug and wondering what the library was compiled with: C or C++ ? Is the dwf.h definition file exactly correct with regards to parameter types (char vs unsigned char Trying to see if the size of the parameters, ctypes.c_bool() vs ctypes.c_int(), e.g., matters. Or c_byte() vs c_ubyte(). Since afaik C doesn't have 'bool' type, knowing if this is a C++ library would help me decide. Similar inconsistencies: Example code snippet: /usr/share/digilent/waveforms/samples/py/dwfconstants.py #TRIGSRC trigsrcNone = c_byte(0) trigsrcPC = c_byte(1) But dwf.h, that presumaly the library was compiled with: typedef unsigned char BYTE; typedef BYTE TRIGSRC; const TRIGSRC trigsrcNone = 0; const TRIGSRC trigsrcPC = 1; where my reference tells me 'c_ubyte' is what we should be using for 'unsigned char', not c_byte(). Going by the dwf.h file, I would not use the definition examples provided in dwfconstants.py, but change to c_ubyte(), for example. In the end, most of these probably won't matter, but the bug I'm chasing seems to involve corruption of the runtime stack (moving a FDwf call into a subroutine gives different behavior than calling it from one up), so I'm being paranoid about the ctypes interface since it's easy to make a mistake there. This on Debian 8.6 with installed: +++-=======================-================-================-=================================================== ii digilent.adept.runtime 2.16.5 amd64 Digilent Adept Runtime ii digilent.adept.utilitie 2.2.1 amd64 Digilent Adept Utilities ii digilent.waveforms 3.3.7 amd64 Digilent WaveForms Thanks much.