Jump to content

attila

Technical Forum Moderator
 View Profile  See their activity

  • Posts

    6,454

  • Joined

  • Last visited

 Content Type 

Everything posted by attila

  1. attila
    Hi @dave slagle What temperature are you reading? In this device without active cooling, around 50*C is normal or more if you have loads.
  2. attila
    Hi @RAJEEVA dwf.FDwfDigitalIOOutputEnableSet(hdwf, c_int(1<<1)) # OE DIO-1 / DIO-25 dwf.FDwfDigitalIOOutputSet(hdwf, c_int(1<<1)) # drive high DIO-1 / DIO-25
  3. attila
    Hi @dave slagle The USB connector in the AD2 is strong and reliable. I'm using some since many years and never had any problem with it. Except some cables are not making good contact with one device or the other kind of devices. On your device some USB cable or try to reversely plug could have damaged the socket. I don't think the two year old device is in warranty... You should try to replace the USB connector.
  4. attila
    Hi @dclock Thank you for the feedback.
  5. attila
    Hi @dave slagle This is likely a connection-contact issue. The error indicates loss of USB communication. Try using other cables eventually powered USB hub.
  6. attila
    Hi @RAJEEVA
  7. attila
    Hi @dclock Did you try installing the driver from the installer DMG? Could you try the latest beta version? https://forum.digilentinc.com/topic/8908-waveforms-beta-download/ This updates the USB libraries for macOS. Install the dwf.framework form the DMG and try running the following: $ python /Application/WaveForms.app/Contents/Resources/SDK/samples/py/Enumerate.py
  8. attila
    Hi @sib Thank you for sharing your code. I will test the example and your code as soon I find the ACL2, or get a new one... You may need a Protocol.SPI.Stop/Start() between "SPI RESET" and "Read Device ID".
  9. attila
    Hi @sib You can find the example for ACL2 (as 3) ADXL362 under Custom, not Sensor tab.
  10. attila
    Hi @sib Thank you for the photo and screenshot. The wiring looks good. At the moment I can't find ACL2, only ~20 other PMods, but the last time I've checked it was working. You have selected the example for ACL with ADXL345. This has different command set than the ACL2 with ADXL362 IC. Probably you wanted to say ACL2 and not ACL5. Under the Custom tab select the ACL3/2 with ADXL362 and Run. These is a typo mistake, it should be ACL2 instead ACL3. In case you use the Logic Analyzer, the Protocol tool won't be able to read data, so the uncheck this option otherwise you will get "Device ID mismatch". You can also use the Master tab
  11. attila
    Hi @sib The used DIO signals for different purpose can be selected to ease wiring.
  12. attila
    Hi @RAJEEVA The AD2 samping rate is 100MHz bandwidth about 50MHz. The DD sampling rate is 800MHz on the DIN lines and bandwidth about 100MHz. The bandwidth highly depends on the driver circuit, wiring... For IR signal you probably need much lower frequency. This typically uses 30-60kHz carrier signal and kbps data rate.
  13. attila
    Hi @sib You should have: CS to Select, SCLK to Clock, MOSI to DQ0, MISO to DQ1 Pin-5 or 11 to GND and Pin-6 or 12 to V+ 3.3V The other interrupt pins and DQ2-3 are not required. You can find info about the Pmods at: https://reference.digilentinc.com/reference/pmod/pmodacl/start https://reference.digilentinc.com/reference/pmod/pmodacl2/start
  14. attila
    On Digital Discovery the index for DIO-24 is 0, 25 is 1,... dwf.FDwfDigitalIOOutputEnableSet(hdwf, c_int(1<<0)) # DIO-0 / DIO-24 dwf.FDwfDigitalIOOutputEnableSet(hdwf, c_int(1<<1)) # DIO-1 / DIO-25 dwf.FDwfDigitalIOOutputEnableSet(hdwf, c_int(1<<2)) # DIO-2 / DIO-26 dwf.FDwfDigitalIOOutputEnableSet(hdwf, c_int(1<<3)) # DIO-3 / DIO-27 dwf.FDwfDigitalIOOutputEnableSet(hdwf, c_int((1<<0) | (1<<1) | (1<<2))) # DIO-0:2 / DIO-24:26
  15. attila
    Hi @RAJEEVA You can find the examples and manual in the SDK folder: DigitalIO.py # enable output/mask on 8 LSB IO pins, from DIO 0 to 7, DIO 24 to 31 for Digital Discovery dwf.FDwfDigitalIOOutputEnableSet(hdwf, c_int(0x00FF)) # set value on enabled IO pins dwf.FDwfDigitalIOOutputSet(hdwf, c_int(0x0012))
  16. attila
    Hi @sib You can find script examples in Protocol tool/ SPI-I2C Custom and Sensor tabs. You can also find SPI/I2C examples in the SDK:
  17. attila
    Hi @caesun For such purpose you could use the OpenScope or OpenLogger: https://store.digilentinc.com/usb-scopes-instruments-circuits/
  18. attila
    Hi @m72 Thank you for the observation. I managed to reproduce the issue. Until this gets solved, please use lower cursor numbers as reference.
  19. attila
    Hi @juliosilva The devices can be used with single board computers (BeagleBone, RaspberryPi4...) using the ARM build of WaveForms. https://blog.digilentinc.com/analog-discovery-2-is-now-compatible-with-raspberry-pi-4/ The phones and table are not supported due to USB device driver.
  20. attila
    Hi @PBritten The custom waveforms in Wavegen are stored in a the .Custom container to be able to reuse them in multiple Channels and different modes. Wavegen1.Custom.set("MyWave", arr) Wavegen1.Channel1.Custom.Type.text = "MyWave" Related posts: https://forum.digilentinc.com/search/?q=wavegen custom script&type=forums_topic&nodes=8
  21. attila
    Hi @m72 After adding the Order option in Logic Analyzer (splitting the Input selection in two) I have forgotten to update the Protocol/Logic Analyzer to set the Order option automatically. Thank you for the observation, it is fixed for the next release.
  22. attila
    Hi @m72 This looks like a digital issue in the ADC. Have you used for this tests the WF v3.11.23 I sent you in private message?
  23. attila
    Hi @m72 You have in private message a software version which changes a bit the digital timings. Please install this, reconnect the device to make sure it will get reconfigured and start the application. Let me know if this solves the issue. The scope inputs are rated for up to +/-50V, but it should survive higher voltages due the 820k series resistor before the 7.5-20mA protection. High voltages (with energy) usually damage the gain selector analog switch, which leads to DC reading. https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/reference-manual#scope_input_divider_and_gain_selection The attenuation option is intended to scale the scope readings, it is not a device feature. For instance when you use a 10x scope probe (9M series), the scope input will actually get 1/10 of voltage. Specifying 10x attenuation the software will multiply the readings by 10, to compensate this. You can also use this to reflect external voltage dividers, amplifiers... Edit: The calibration adjust the amplitude and offset.
  24. attila
    Hi @m72 This may look like a digital issue, from ADC to FPGA... but i don't it is since we should see similar glitch on the upper side too. Could you provide detail about the experiment? I see you have set 10x probe... Are you using (single ended) BNC probe at 10x ? In case you are using differential input with high common mode voltage, the signal might enter in limitation or clamping starts to act, which also depends on the offset: https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/reference-manual?redirect=1#scope_driver https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/reference-manual?redirect=1#scope_signal_scaling The highlighted "noise band" indicates high frequency signals (noise, glitch), above current sampling rate, which indicates some analog issue:
  25. attila
    Hi @eos33 I have added HDMI CEC interpreter to the latest WF beta build: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/
×
×
  • Create New...