attila

Technical Forum Moderator
  • Content Count

    3417
  • Joined

  • Last visited

About attila

  • Rank
    Prolific Poster

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

9553 profile views
  1. Hi @blipton In the latest beta version you can find "USART PS/2" interpreted for the Logic Analyzer. https://forum.digilentinc.com/topic/8908-waveforms-beta-download/ Could you provide more detail about the protocol ? it sounds similar to SPI without Select signal.
  2. Hi @reddish You have the updated manual in a private message. It will be included in the next software build. The deprecated undocumented ones at the end of the dwf.h have alternatives.
  3. Hi @reddish Thank you for the observation. I've started updating the manual.
  4. Hi @DanJP The 48kHz maximum signal with 192kHz rate is because to generate a signal it needs at least four samples like: 0, +1, 0, -1 With random, custom or play it can go up to 192kHz.
  5. Hi @sergiodorazio The -runscript should be without space after the minus sign. On normal "taskkill /IM WaveForms.exe" the application may ask if you want to save the changes in the workspace but you can use "taskkill /F /IM WaveForms.exe" to force close the app.
  6. Hi @alexpeck See latest beta version: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/
  7. Hi @DanJP The latest beta version is working for me with Linux/ALSA at up to 192kHz. https://forum.digilentinc.com/topic/8908-waveforms-beta-download/ Sorry but I don't what limitation do the various interfaces have.
  8. Hi @alexpeck Thank you for bringing this up. I've started working on this. It will be in the next version.
  9. Hi @Jared 1. Most probably something in the Linux driver/udev got messed up. 2. It should be no problem for the AD2 but it may be unsafe for the circuit connected to it and the operating/file system could get corrupt. 3. The Scope inputs are rated for +/-50V Higher voltages (inductor flyback, piezoelectricity...) could damage the first IC in the path a digital switch or other components, which leads to wrong scope reading. I've tried now to soft and hard reset the RPI while using the AD2 and after reboot it is working normally for me.
  10. Hi @DanJP Currently the software offers the preset frequencies provided by the audio libraries. Also on my Linux machines the maximum provided is 48kHz but it would be capable for more. I will add later higher flexibility in specifying the frequencies but this needs a bit more work in the low level interface. Thank you for the observation.
  11. Hi @THDplusN_bad You are right. The measurements can also be done with a custom setup on a breadboard using Wavegen and Scope XY view. The Curve Tracer instrument highly simplifies the software setup. You don't have to worry about the configuration of Wavegen channels, synchronization and triggering of Scope. The Tracer also takes in account the current sink of the probes, skips the samples at the step transitions, shows voltage drop, currents, hFE, Rds, offers cursors, export, 3D view... It can be use with and without adapter. In later case the circuit diagram shows the necessary
  12. Hi @CPP Yes, you were right. For digital import the sample rate is taken from the comments. The #samples overrides the rate. In case there is no #sample comment the rate is calculated from time column. It is fixed for the next version. Thank you for the observation.
  13. Hi @Will_SC The analog-in detector to analog-out latency is about 470ns. Like here specifying 100ns wait the delay will be 570ns. See a related post:
  14. Hi @RichSCorp See the following: # analog-in dwf.FDwfAnalogInFrequencySet(hdwf, c_double(1e6)) # 1MHz sampling rate dwf.FDwfAnalogOutNodeEnableSet(hdwf, c_int(0), c_int(0), c_int(1)) # channel 1 enable dwf.FDwfAnalogOutNodeOffsetSet(hdwf, c_int(0), c_int(0), c_double(0.0)) dwf.FDwfAnalogOutNodeAmplitudeSet(hdwf, c_int(0), c_int(0), c_double(5.0)) # 5 Vpk2pk range # trigger detector dwf.FDwfAnalogInTriggerChannelSet(hdwf, c_int(0)) # channel 1 dwf.FDwfAnalogInTriggerTypeSet(hdwf, trigtypeEdge) dwf.FDwfAnalogInTriggerLevelSet(hdwf, c_double(0.0)) dwf.FDwfAnalogInTriggerHysteres
  15. Hi @Chuankun The USB controller could be damaged by high USB voltage. Make sure to look for a faulty/unregulated USB hub supply to prevent further problems. You could try replacing the FT232H but likely other ICs on the board are damaged as well. The ADM1177 is probably fine, this is rated up to 30V