Search the Community

Showing results for tags 'bug'.



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
    • 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 12 results

  1. gasstationwithoutpumps

    Impedance Analyzer offset bug

    In Waveforms 3.8.17 (beta), I have encountered a bug in the impedance analyzer when the offset voltage is not zero. I was measuring the impedance of 10µF capacitors with the adapter board at 100Ω, and I got perfectly fine readings when I used amplitude=1V, offset=0V. But when I switched to using amplitude=1V, offset=4V, the impedance was reported as essentially infinite (dropping down to maybe 100MΩ around 100kHz). I got this result with several different capacitors, so it is unlikely that poor connections were responsible. The short and open compensations were redone for the new offset, and seemed to be reasonable. Providing a DC offset when testing electrolytic capacitors is essential, and a DC offset is also useful for determining the voltage dependance of ceramic capacitors, so fixing this bug seems to be fairly important.
  2. maximb

    Nexys 4 DDR Keyboard: Wrong scancodes

    Hi, I recently discovered that the wrong scan codes are sent for certain keys. This is tested with my own PS2 keyboard controller, and the same behaviour is present with the official demo: https://reference.digilentinc.com/learn/programmable-logic/tutorials/nexys-4-ddr-keyboard-demo/start I have tested two keyboards: One Logitech K120, and one Microsoft comfort curve 3000. The following behaviour is exhibited: Left arrow set 2 scancode should be: E0 6B / E0 F0 6B. Actual: 6B / F0 6B Up arrow set 2 scancode should be: E0 75 / E0 F0 75. Actual: 75 / F0 75 Down arrow set 2 scancode should be: E0 72 / E0 F0 72. Actual: 72 / F0 72 Curiously, the right arrow scancode is correct. Numpad division set 2 scancode should be: E0 4A / E0 F0 4A. Actual: 4A / F0 4A Can anyone confirm? Online Documentation for Altium Products - PS2 Keyboard Scan Codes - 2017-09-13.pdf
  3. Hi, I just added a function generator amplifier to my AD2, and i recognized the following: - When everything is hooked up (function gen + 21W lamp for testing) and i start waveforms, it seems that the output of the AD2 goes unwanted high. (There is some current drawn from the power supply at the same time) - The same thing happens: -when you click in the close window button on the top rigth corner when the window pops up that asks you to save the current workspace. but in this case the current drops much slower. (as seen on the power supply) Waveforms Version 3.8.2 64-bit Windows 10
  4. gasstationwithoutpumps

    Minor bug in Waveforms 3.8.2

    There is a minor bug in Waveforms 3.8.2 in the Impedance Analyzer: the metadata for probe resistance and capacitance seem to be swapped: #ProbeCapacitance: 1.04e+06 Ω #ProbeResistance: 4.3e-11 F Also, the metadata does not include the excitation (amplitude and offset). I would check the beta release of newer versions, but there doesn't seem to be a beta for the Mac OS X, just Windows and Linux.
  5. gasstationwithoutpumps

    Bug: AD2 Impedance Meter export

    There is a bug in the export of data from the impedance analyzer from Waveforms (specifically from Waveforms 3.8.2 using the Analog Discovery 2, but I have seen it with earlier releases of Waveforms 3 also). The problem is that the frequencies are reported as if they were from a linear sweep, even though a logarithmic frequency sweep was done: #Date Time: 2018-07-01 16:50:47.258 #Trace: Trace #Start: 100 Hz #Stop: 1e+06 Hz #Steps: 101 #Resistor: 10000 Ω #Average: 10 #ProbeCapacitance: 1.04e+06 Ω #ProbeResistance: 4.3e-11 F #Compensation: Open Short #Wavegen: Wavegen1 #Amplification: 1 X #Settle: 20 ms #MinPeriods: 32 #Channel: Channel 1 #Range: 5.49577 V #Offset: -0.000318847 V #Attenuation: 1 X #Channel: Channel 2 #Range: 5.51181 V #Offset: -0.000280998 V #Attenuation: 1 X Frequency (Hz) Trace θ (°) Trace |Z| (Ω) Trace Ls (H) Trace Cs (F) 100 0.00067832392258167652 9971.9407134030535 0.00018789460945304077 -0.013481119008321029 10099 0.0018260127183053441 9972.4554790954317 0.00046132118972998595 -0.0045670615004842902 20098 0.0026165423173400044 9972.2098918719494 0.00060286028271848858 -0.0029068564833067186 Many of my students had problems with this bug last quarter, and we had to create a work-around in our gnuplot plotting scripts: #if the frequencies in your data file don't follow log increments use the code below # Written by Ali Fallahi #example: use plot 'data' u (correct($1)):3 instead of plot 'data' u 1:3 freq_u=1e6 #last frequency freq_l=10 #first frequency NoOfSamples=101 #number of samples indexno(f)=(NoOfSamples-1)*(f-freq_l)/(freq_u-freq_l) correct(f)=10**(log10(freq_l)+indexno(f)/(NoOfSamples-1)*log10(freq_u/freq_l)) ## plot 'measuring-10kohm-buggy-freq.txt' u (correct($1)):3 title '10k{/Symbol W}±0.1%' It would be nice not to need to correct the data files.
  6. There appears to be a mistake in the WaveForms SDK Reference Manual supplied with the SDK. The document says: But the function actually requires the idxChannel AND idxNode, like this: I'm running the following code segment to get the different node options: num_channels = c_int() dwf.FDwfAnalogIOChannelCount(hdwf, byref(num_channels)) print(num_channels.value, "channels") for i in range(0, num_channels.value): print("Channel", i) channel_name = create_string_buffer(32) channel_label = create_string_buffer(16) dwf.FDwfAnalogIOChannelName(hdwf, c_int(i), channel_name, channel_label) print(str(channel_name.value), str(channel_label.value)) num_nodes = c_int() dwf.FDwfAnalogIOChannelInfo(hdwf, c_int(i), byref(num_nodes)) for n in range(0, num_nodes.value): node_name = create_string_buffer(32) node_label = create_string_buffer(16) dwf.FDwfAnalogIOChannelNodeName(hdwf, c_int(i), c_int(n), node_name, node_label) print(" ", str(node_name.value), str(node_label.value))
  7. gasstationwithoutpumps

    Measurement information not saved with workspace

    When I save a workspace and restore it in Waveforms 3.6.8, the measurement list in the Scope interface keeps the peak-to-peak, DC RMS, … setting, but loses the channel information, so that the measurement list has to be cleared and re-created each time I load the workspace. Note: I had renamed the channels (so they had names like Voltage with label "V" and Current with label "I", instead of C1 and M1).
  8. gasstationwithoutpumps

    SPI sensor script ReadWrite not working (3.6.8)

    In Waveforms 2015 3.6.8 on a Mac OS 10.11.6 with an Analog Discovery 2, I am not able to get the SPI sensor scripts to work. I'm having no trouble with Master or Custom scripts, but with the Sensor scripts the ReadWrite() commands always return an array of zeros, even if I'm not in Debug mode. (I tried starting from a fresh run of Waveforms, to make sure that the debug setting was not just being excessively sticky.) Can anyone else duplicate this behavior? Or is it just me? Incidentally, the documentation for the protocol instrument and the scripts is woefully inadequate—I had to figure out how things worked by trial and error, because of the extreme lack of information in the documentation.
  9. I'm running waveforms 2015 3.5.4 and got a bug/request. When changing the timebase, the position should not change. When I use the scroll the wheel or the timebase pop-up the actual position of the trigger point moves around in the scope graph window, this is very frustrating. Once you set the trigger x position, it should never move. Thanks.
  10. akshata@94

    simulation error

    hello guys, I am new to this forum . I am implementing md5 in Verilog. I am almost done with it somehow but still stuck half in a way.. can someone can help me in finding the bug in the rtl. I have referred pancham md5 source code for it and have modified a little bit as per my application. here, are the two attached files kindly help me in solving these issues. have been trying since long. I have to calculate the hash value of about 512 bytes but first of all trying from smaller input values md5.txt1.txt pancham_round.txt
  11. gasstationwithoutpumps

    Network analyzer bug in saving files

    I think that I have tickled a bug in Waveforms 2015 (version 3.5.4 and at least one earlier version) when outputting Network data files. The Network tool allows you to sweep the frequency down instead of up, which is very handy when using very low frequencies, as the auto setup does an extra two runs at the first frequency, which can take a lot of extra time if the low frequency is 100mHz. Everything works great, until you save the data. The frequencies in the file are not properly paired with the other columns—it looks like the frequencies are being regenerated sweeping upward, even though all the data in the other columns is for the frequency sweeping downward.
  12. I have installed Adept 2 and Waveforms 3.3.7 from the Digilent website. I can open the Waveforms software and use it in demo mode with no issues, but the moment I plug in my Analog Discovery 2, the application crashes. The .crash file is too big to upload directly, so I have uploaded it here: https://dl.dropboxusercontent.com/u/971295/_usr_lib_digilent_waveforms_waveforms.1000.crash This issue is entirely deterministic with my setup, so please let me know if any additional information would help.