• Content Count

  • Joined

  • Last visited

About m72

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello! WaveForms 3.15.5, Windows 7, x64 After auto reconnection Scope base changes from 100 ns/div to 100 ms/div. With best regards, Mikhail.
  2. Hello! Sorry for stupid question. How I can choose a few words for filter? For example if I need to remove or show "ACK" and "NAK"? With best regards, Mikhail.
  3. Hello! WF 3.13.18, Windows 7, x64 Under some conditions, the pattern generator produces glitches at the end of the sequence. I think that in the "Auto" mode the field "Run" should be rounded down. An example with this effect in attachment. The DIO0 pin is connected to the first channel of the oscilloscope. With best regards, Mikhail. glitch.dwf3work
  4. Hello! WaveForms 3.13.16, Windows 7, x64. Speed test with Digital Discovery fails. 😞 With Analog Discovery works fine. Latency 0.15...0.20 ms, to device 20...25 MBps, from device 29...41 MBps. Some problems with 125 MHz base frequency in Digital Dicovery after reconnection (for example after failed "speed test") found. The kernel frequency is set to 125 MHz. Ok! The "Patterns" tab generates *1.25 faster than required. Clock 1MHz -> 1.25 MHz. In the "Logic" tab maximum sampling frequency in the list is "800 MHz", but the measurements are right "1.25MHz". Work aroun
  5. Hello! WF 3.11.24, AD2, Windows 7, x64 On save/load or when I clone the scope relative cursors go wrong. It happens if reference cursor number is greater than current. With best regards, Mikhail. scope_clone.dwf3work
  6. Hello! Yes of course. I have used it. With best regards, Mikhail.
  7. Hello! Digital Discovery, WaveForms from 3.11.18, Windows 7 x64. When allow "Logic Analyzer" from "Protocol" by default it change DIO24 -> DIN0 (mode 800 MHZ, DIO0..7). If start "Logic Analyzer" at "200 MHz, DIN0...DIN23, DIO24...DIO31" it change sample rate "100...400MHz" -> "800 MHz" and change DIO24 -> DIN0. If start "Logic Analyzer" at "400 MHz, DIO24...DIO39" it change sample rate "100...400MHz" -> "800 MHz" and make DIO >= 32 "not available". And after that "800 MHz" -> "400 MHz" moves DIO32 -> DIO24 and DIO33 also to DIO24. With best regards,
  8. Hello! Just tested it with simplest settings (attenuation 1X, 50 ns/div, zero signal). Only offset on the screen is changed. Scope1 ... Scope3. 1. It happens only with second channel. 2. When offset is [-2.34V ... -1.76V]. 3. At the borders noise is like a rare peaks. At the center like as an ADC input is overloaded. 4. Peaks values are -7.6V & +7.6V. Scope4. 1. Offset -4V 2. But signal is not zero, it is +2V. So it became to the same "- div from the center". Peaks are -5.6V & + 9.6V -> shifted +2.0V. 1V/div, 2V/div, 5V/div - the same situation. Why I am
  9. Hello! Very very strange. It occurs without any scheme and on different PCs. Only shift level on the screen changes. Conditions: Attenuation 9X...100X & offset -16V ...-24V May be this is an calibration effect? Or it is damaged by high voltage impulse... At zero state second channel on this AD2 is more noisy than first. With best regards, Mikhail. P.S. I often find bugs. Even in such things as TV set, PLC (in Siemens LOGO! One is definitely there), Atmega, etc. 210321ABEEA0.dwf3calib
  10. Hello! Oscilloscope problem. When I shift second channel down - some glitches on the screen occurs. It happens on "two lines down from center" and does not affected by the shift level. With best regards, Mikhail. default.dwf3work
  11. Hello! The initial clock signal level depends on the frequency and phase. With phase == 0 - it works well. With phase = 180 degrees - so-so. (This signal is like a preview). As far as I understand, these are rounding issues. But you must admit that it looks strange: I change the frequency slider - the initial signal level changes. The delay parameter for signals is very useful. But in the general case, it would be nice to set the line state separately. It may have to separately process for each type of signal and even its value. I will try to systematize my experience a bit late
  12. Ok. But problem with pulses that start at "High" is present. Line goes High on start ignoring delay settings. And falling down at expected time. P.S. May be it is better to fill delay before pulse with "Idle" value? EMU_2CH_EACH_V10.dwf3work