Jump to content

LarsB

Members
  • Posts

    30
  • Joined

  • Last visited

LarsB's Achievements

Frequent Visitor

Frequent Visitor (3/4)

4

Reputation

  1. Thanks, Attila, copying a part of the capture to a new tab is really helpful.
  2. Duh, just noticed the Cursor view, which answers my first question.
  3. Thanks for the explanation! I figured you really need to set a trigger to capture what you want.
  4. Is it possible to mark a point in time in the plot, e.g., by a (colored) vertical line? There are labels, but they don't move with the capture, so I'm not even sure what they're for. Alternatively, is it possible in the Event View (or anywhere else) to search for something after a given point in time, e.g., the previous search, or the current position in the capture on screen, or a numeric time value? I'm having a hard time analyzing the capture, and manually copying and comparing times such as "0.00211153" is quite cumbersome.
  5. What message do I have to wait for? If I wait for the box turn green and the message "Recording", then wait 1 seconds before I press stop, I only have captured a few ms. Do I have to wait for "Recording Trig'd ...", even though I don't have a trigger set? Or is there a limit to the sample rate when recording that WaveForms isn't aware of?
  6. When I try to record (16 bits, 128 Mi samples at 50 MHz), WaveForms doesn't capture anything if I start the recording and then press stop after a second. Why is there a delay before recording starts? WaveForms states it's "Recording Prefill"?! Can I avoid that? Trigger is set to None.
  7. Forgot to mention: It's version 3.18.1 on Linux.
  8. Great, I didn't know that! In my version, it says "swap event navigation", but it works. Very minor nitpick: It also reverses the arrow symbol, which is still confusing, so maybe keep the arrow's direction while swapping navigation? Or maybe it's already like that in your version?
  9. I have three signals in Logic: If I drag TRIG up below A0 then the dragged signal loses its name: Or is there a different way to reorder signals?
  10. Oh yes, I didn't notice that all data is shown if I leave the entry field blank. Perfect! And the bidirectional navigation will be really helpful, thanks!
  11. This is just a minor issue, and maybe my expectations are wrong, but: When I click on one of those little arrows at the side of the signal grid, e.g., I get the previous data segment, i.e., the signals scroll to the right (might makes the signal segment at the right edge disappear), which is consistent with the right-facing arrow. But my expectation is that clicking this arrow on the right side of the grid would show the data that follows after the edge, i.e., more. In other words, the grid should scroll left. Please compare this behavior with virtually any image gallery on the web, and you'll find that clicking the right arrow shows the next image, not the previous. Compared to this de-facto standard, Logic has it backwards. Am I the only one who thinks this way?
  12. With WaveForms Logic, it seems that I have to set the number of samples upfront. Is there a technical reason for this? Is it possible to start and stop the measurement with a click each instead? Also, why does the sample rate change when zooming in and out of the signal graph? Shouldn't it be fixed after the measurement?
  13. I'm using the logic analyzer of WaveForms to measure two buses. The buses are clocked by the same signal. WaveShows shows the bus value at each clock edge, like it should: Sometimes, however, I find it easier to work with a list, like in the Data view. Unfortunately, the Data view lists every measurement: (Also, while clicking on a row in the Data view positions the Signal Grid, why is the other way around not supported?) Is there a way to get a view of bus values only? Or in general a list of a protocol values?
  14. Oh, I just noticed that increasing the sample rate by a lot (that UI again ...) makes those slopes appear upright when zoomed appropriately. I guess that is what I'm seeing in the help sample diagram. I guess it's OK then in practice.
×
×
  • Create New...