Someone

I'm using the newest 3.19.29 on Linux. The segfault is reliable either with the Python demo or my own code. I could give a more useful backtrace if you happen to have a library with debug symbols.

Hello, I want to read UART data with a Digital Discovery. When I change the Digital_Uart_RX.py demo to use a rate of 8 MHz (or 10 MHz) it segfaults: #0 0x00007f7a3a5558e9 in iFDwfDigitalInStatusData2(DINSTDVC*, void*, int, int) () from /lib/libdwf.so #1 0x00007f7a3a563c4e in FDwfDigitalUartRx () from /lib/libdwf.so I can't say if this is dependent on the data on the line or not. Is there a limitation on UART rates? I hope this can be reproduced.

When I do a loop using FDwfDigitalInDividerSet() and FDwfDigitalInDividerGet() I can see that dividers 1, 2, 4, 8 and up are accepted by the hardware (or your library). When doing a measurement with divider 10 I get results which seem to be measured by 80 MHz. But that's not the main point here. When I execute the above example with a wantedDivider of 16 it reads data. When I use a value of 8 FDwfDigitalInStatus() stays in DwfStateWait. That's the problem I need to be solved: Using the record feature with higher frequencies.

Hello, I have a Digital Discovery here with which I want to record some data. First question: I tried to query the valid dividers and found that fractal frequencies are possible with the valid dividers being 1, 2, 4, 8 and up. Is that right? Second question: The DwfState type in the SDK header has state 3 defined twice and state 6 missing. Is this a type or intentionally? Now my issue: The following code works with a divider of 10 but not with 9 or lower. In the latter case the state stays at DwfStateWait and does not change. Maybe I'm handling the wait state wrong here? I found no sample code that handles this case. #include <iostream> using namespace std; #include <dwf.h> static const int bufferSize = 2 * 1024 * 1024; static const unsigned int wantedDivider = 9; // valid Dividers ok? // DwfState 3 double and 6 missing? int main() { HDWF hdwf; DwfState sts; uint8_t *buffer = new uint8_t[bufferSize]; int availableBytes; int lostBytes; int corruptedBytes; // Open device FDwfDeviceOpen(-1, &hdwf); // Configure device FDwfDigitalInInputOrderSet(hdwf, false); FDwfDigitalInSampleFormatSet(hdwf, 8); FDwfDigitalInBufferSizeSet(hdwf, bufferSize); double hzSys; // Clock should be 800 MHz with 8bit sample format FDwfDigitalInInternalClockInfo(hdwf, &hzSys); // Valid dividers are: 1, 2, 4, 8- FDwfDigitalInDividerSet(hdwf, wantedDivider); FDwfDigitalInAcquisitionModeSet(hdwf, acqmodeRecord); // Start aquisition FDwfDigitalInConfigure(hdwf, false, true); // Wait for data do { FDwfDigitalInStatus(hdwf, 1, &sts); } while (sts == DwfStateWait); // Read data if (sts == DwfStateRunning) { FDwfDigitalInStatusRecord(hdwf, &availableBytes, &lostBytes, &corruptedBytes); int bytesToRead = min(bufferSize, availableBytes); FDwfDigitalInStatusData(hdwf, buffer, bytesToRead); cout << "read " << bytesToRead << " bytes." << endl; } // Stop aquisition FDwfDigitalInConfigure(hdwf, false, false); // Close device FDwfDeviceClose(hdwf); delete[] buffer; return 0; }

When I use the whole memory capacity of my Digital Discovery it takes quite some time to download the data via USB2. Would the hardware be capable to reduce/compress the data on the fly while downloading? Sending not every single byte but only levelchanges and length information for longer runs to speed up this process for data with suitable properties?

I'm using Waveforms 3.18.41 on Fedora 34. How to reproduce: Load a Workspace with data in Logic tab and events view open. Zoom into some data, while the first event stays selected. Activate one of the quick measure features. As soon as the mousepointer hovers over the plot the event view moves along its list and the plot flickers. If the mouse moved long enough the end of the event view is reached and the plot changes zoom. When I try to zoom in again with the mouse wheel the zoom eventually gets reset and other things happen. Sometimes it works for a moment but then the eventlist wandering eventually happens again. It works again if the quick measure gets deactivated. If the event view is closed measurement works. Can you reproduce this?

I tried Waveforms beta 3.18.13 on Linux and found issue 2 fixed.

Knowing this variables name I see it in the debugger and that it is used in the uart example, but no documentation led me there. Thanks for the hint.

This is no important issue, I'm just doing some finger exercises with Waveforms. The thought behind my actual problem: When signals enter the analyzer through different ways like isolators and such, they gather different time offsets. As the Waveforms logic analyzer provides no timeshift functionality out of the box I came to think about a custom logic script to move the data of one channels rgData array to rgValue with an offset index. But to calculate the array offset from the expected time offset I would need to know the actual sample rate of the data. This data I don't have because custom logic scripts don't have access to the Device information. Would it make sense, or be feasible, to provide a time offset functionality for each channel? Would it make sense to provide access to the device settings in a custom logic script?

If I only copy the files to their destinations stated in the spec file, LabVIEW segfaults due to a nullpointer deref when using any of the Digilent VIs. There's a postinstall VI in the package, but this wants to use the registry functions, which are only available under Windows. What I have seen so far LabVIEW is best supported and works best on Windows and with its current issues I will not try and use it under Linux anymore. But thanks for helping.

I installed Labview 2021 on my Linux box and it worked. Then I wanted to install the Waveforms packet for it. Documentation states that VIPM is needed to download and install it. VIPM on Linux is only available in a 2017 version which needs a lot of old libraries to be installed alongside. After installation of VIPM I wanted to install the Waveforms packet with it but failed because Labview didn't start anymore. So before attempting a reinstallation: Is there a way to install the Waveforms packet without VIPM?

Record mode is limited to around 1MHz. The software does a good job setting the right parameters when zooming in and out of the diagram to ensure maximum resolution on repeated capturings. When limiting the inputs to 8 the memory allows 256Mi samples instead of only 64Mi in other modes. So one can have higher resolution for a 4 times stretched time period. But when the setup doesn't allow signal integrity at 800MHz I want to limit the maximum rate used. That's something I have to do manually now by limiting the rate when it gets set too high and adjusting the viewport. This would be easier if the software could do this automatically. At the moment life is easier with like the 100/200MHz modes and 64Mi samples, but with software support one could have up to 4 times the sample rate (up to a point) for a given time period - without hassle.

Hello, I'm using a Digital Discovery with Waveforms 2.16.40 in Logic mode and I want to make a longer scan at a low rate using the full 256 Mi sample space by limiting the inputs to 8. But when I zoom in to reaquire a higher resolution detail view the sample rate goes up to 800 MHz. Maybe it makes sense to add an option to limit the maximum rate. From your company view this could be a checkbutton in device configuration "High speed adapter" yes/no. With which you set the maximum to 200 MHz when no, even in "800MHzx8" mode. From a user point of view this could be a number entry or selector where the user can say "That's the maximum rate I get valid results for in my current setup".

Hello, I read the following lines in the documentation of some other USB DAQ: As I have no real electronics background I'm asking myself if such a statement is also valid for Digital Discovery or Analog Discovery 2 input pins and what state do these pins have in powered off state?

Hi @attila, I see that me looking stupid comes from the fact that the help included in the software differs significantly from the one referenced on the web. See here: https://digilent.com/reference/software/waveforms/waveforms-3/reference-manual#the_workspace_and_project The online version now seems way outdated in comparison and I will use the included help from now on.