Jump to content

sintech

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by sintech

  1. Hello @attila, thank you. As I can see position is saved separately for each decoder.
  2. Thank you @attila, looking forward to new versions.
  3. Hello Digilent, It is nice to see that Waveforms is constantly improving with new features and fixes. Could you please consider the following changes to Logic instrument to make it even better: 1. Move "Add signal (bus, etc.)" window to the right. Because currently it overlaps current signal names and types. 2. Custom decoder. Is it possible to make it start decoding on demand? Custom decoder is a very powerful feature but pretty slow on large captures. It is a common approach to make one long capture and cut interesting parts to the new tabs using scissors tool. And then it makes sense to run custom decoder in each of these new tabs while it is disabled in main Buffers tab by default. BR, Konstantin
  4. Thank you for the new 40-bit mode on DD, it is even better than possible dual-mode.
  5. Hello @attila, can you please shed some light on dual device mode? Am I understanding right that it is a way to capture samples synchronously on both devices as if it is a single device with 2x channels? How will it work in case of DDiscovery which does not have dedicated trigger pins? Maybe repurpose one DIO to trigger In/Out on both devices? 31+31 channels is a dream setup for me, even 24+24 will be a considerable enhancement over current 32ch. Is there any plan to support mixed device setup like DD+AD2 (which I have)? In live streaming mode at least? Thank you for new features.
  6. I meant the following: Press "Fit selection to window" icon Click left mouse button somewhere in waveform display then drag mouse to some other point then release the button Waveform area between mouse press and release should be scaled to current window visible area. Repeat if needed.
  7. Thank you very much @attila. I will try this approach. I really overlooked this setting, will try it for my data. Nice and elegant solution. If you allow, I have one little suggestion, a new button next to the "Show entire capture" called "Fit selection to window" which can be used to select a precise amount of samples to display.
  8. Hello @attila, thank you again for all the fixes. Let me continue this thread based on a new experience. I spent a lot of time working with DD and realized that I'm really missing one specific feature. Ability to extract part of the capture to file. Like for example I made one long capture and I want to split it to a number of semantically meaningful short pieces. Short captures could improve custom decoder performance and make 'All events' export filter useful, because currently it just freezes WF on large captures. From UI point of view it could be made using Vertical Quick Measure selection + new "file type" option in "Save Acquisition" dialog (like it was done for project with or without acquisition). Other: The name of the current opened project is not displayed anywhere in WF. Cursor position precision is not enough for high-speed captures. If you reopen saved project, all cursors are shifted left. Endianness in multi-byte bus. Is it possible to change byte order? Delayed trigger feature. Wait for some specific amount of time after trigger before starting capture. Could a negative trigger value in Record dialog be used for that? Did you consider adding complex triggers: protocol + simple? For example I would like to trigger when my bus has value 0x55 and "WR" signal is rising. I know it is possible to manually set all needed Bus bits to level condition and set separate signal to edge but anyway it would be good from UX point. The same for Events View, ability to multiple match: bus equals 0x55 and WR equals 1. I thought about your idea of describing cursors in notes and maybe it is possible to make some sort of hyperlink to specific point in capture, like "[time]". Because notes are stored in separate file from project/capture while cursors are bound to project which is not always convenient.
  9. @attila, thank you for your quick reply and fixes. Yes, name column in Cursor View will do the job. And please make it scroll to the cursor timestamp when cursor is clicked in the Cursor view.
  10. I have been a DDiscovery user for almost half a year. It is a great tool for signal capture and analysis and it is bundled with WaveForms software which is also very good and stable. I could not resist buying AD2 for analog projects since I saw the potential of WF+AD2. Based on my experience I have a few issues and new feature suggestions for WaveForms (latest beta). Issues: Logic: While clicking thru events, "Base" value changes from event to event, while it could be more convenient if it stays the same (to compare relative length of pulses). Logic: When "Base" is low, the value of Bus could be hidden at the left side of display. It depends on horizontal scroll position. Screenshot attached Protocol: SPI Spy becomes very slow and even freezes WF when large portion of data is received (>2k). Latest WF hangs on Mac OS X 10.14 from time to time. How can I report it to investigate? Suggestions for Logic: Play mode. Great feature but completely undocumented. It is worth mentioning in WaveForms Help and DD Wiki. Important point: "Start: 0" means beginning of the file, not 0 mark on X-axis. It would be nice if "Start" and "Samples" could be configured in time units in addition to samples. It would be nice to have "ROM Logic" feature among analyzers even as software implementation, because sometimes even simple logic equations are enough to better understand the behavior of signals while "Custom" analyzer tends to be very slow on large captures. It would be nice if "Export" has a feature to export unique events of all channels like "Raw Events" but with Data column for each logical channel or bus. Currently I have to export "Raw events" and then parse them using a python script to do the same. "Add Signal" dialog does not have a Name field, so I have to click edit for every single signal to set its name. Last but not least: Signal annotation. Currently we have: "Notes" - global for capture, "Labels" - just a text bound to screen coordinates (changes position on different WF window size), "Cursors" - bound to exact waveform position but you can't assign a name to cursor. So we have no option to mark events on waveform and assign a name to them. Please make some sort of bound (to waveform) labels or named cursors to mark start and end of the event.
×
×
  • Create New...