attila

Hi @Oscar A There is no interpreter in the application for this protocol, but it could be implemented with Custom interpreter.

Hi @Ayesha Zaman Make sure the acquisition time / sample rate is not more than the device buffer size, 8192 for AD2, otherwise it will try to use record/data streaming which is limited to a few MHz for AD2. Time (s) - mso/1 Amplitude (V) - mso/1 0 3.97984m 10n 3.97984m 20n 3.97984m 30n -10.8283m 40n 7.68187m 50n -14.5303m 60n 3.97984m

Hi @David Aurora Corrected in the latest:

Hi @fr.bernardo It should be something like this: var reg = Read0(8,4); // read 4 bytes from DQ0, SISO, var ss = reg[0]>>6; var bd = ((reg[0]&0x3F)<<8) | reg[1]; var tp = (reg[1]<<3) | (reg[2]>>5); if(ss!=0) return "SS"+ss; return bd; // or scale it to unit

Hi @Kodeeswaran S

Hi @David Aurora

Hi @DaniS Feel free to use the beta version. As you can see in the logs, in addition to new features, bugs are fixed.

Hi @Kodeeswaran S I run the following code on Windows and Linux, and got the same result: DigitalIn_Trigger2.py record.windows.csvrecord.linux.csv

Hi @KTP Yes, all functions are thread safe.

Hi @Kodeeswaran S Looking at you csv files: in window the first period is 206 samples long, according the column1 0.201, and in linux 409, 0.400 The sample step of column1 is both files is 0.000979 but you mention different frequencies in windows and linux I don't recommend using this 'WF SDK'. The logic.record performs simple separate captures than should not be concatenated... See the real WaveForms SDK manual and examples here: The AD3 first/default configuration has 16ki samples allocated for Logic Analyzer so you can use acqmodeSingle, you don't have to use acqmodeRecord, to capture up to this number of samples.

Hi @gcb The Play mode with Digital Discovery lets you generate 1-16 bit wide digital signals from tabs. The tab data can be an earlier capture or imported csv, txt or binary file, or generate with the embedded Script interface. This Play mode is not 'infinitely' continuous, but up to 256MB. For 'infinite' length AWG can be used on other T&M devices. These are intended for analog signals, but can also output 1 digital signal.

Hi @DaniS The workspace opens with the latest software version:

Hi @Aurelien Yes, that rom logic but using from SDK, see samples/py/DigitalOut_ROM_Mux.py https://digilent.com/reference/waveforms_-_rom_logic Again, this can be very complicated to code it for state machine. You can use the Scrip tool to automate tasks in WaveForms application.

The Network Analyzer in this has spectral measurements, see:

Hi @Eugene101 Ideally it should be flat but nothing is perfect. I think such 0.2dB deviation is acceptable, unnoticeable with common usage. https://www.ni.com/en/shop/electronic-test-instrumentation/oscilloscopes/what-are-oscilloscopes/3-hidden-oscilloscope-specs-that-really-matter.html If you take relative measurement, like it is done by default in Network Analyzer, the different between channels is lower 0.002-0.05dB, see C2 is relative to C1 For more accurate measurement a close compensation can be used, an initial close loop reference curve R1, see M1 is C1 relative to R1 (earlier saved C1 curve)

Hi @fr.bernardo First see the examples in Custom and Help tab. If this is working with your sensor and you need precise ~10 nanosecond level timing you can turn to Sensor mode. Otherwise you can use Custom mode or Script tool for ~10 millisecond precision software timing.

Hi @David Aurora It will be in the next build.

Hi @Aurelien SPI Slave feature is not yet available with SDK. I'll port it from the application to the library later. It could be implemented using state machine with ROM logic but this is very complicated to do.

Hi @David Aurora Thank you. I'll tell my boss 🙂

Hi @Eugene101 Is the wiring to the two scope channels completely identical and symmetric, splitter in middle and identical cables ? If you are using probes at 10X you could try adjusting the trimmers. The device has two trimmers for each channel for positive and negative inputs. These may need a bit of adjustment for high range, above 5Vpk2pk, 500mV/div. The 2nd and 3rd trimmers are for +, and 1st and 4th for - input. With short BNC cables + T splitter I see ~0.005dB difference at low and ~0.02dB high range between the channel readings. This may also come from the BNC adapter capacitance difference.

Hi @AHT The WaveForms application is available for Windows, MacOS and Linux. The "USB Device" should be 'software attached' to the Virtual Machine if you want to control it from this. Which VM are you using ?

Hi @Abdullah1 Which device are you using? With Analog Discovery 3, ADP2230, ADP3X50... notice the high precision hardware trigger datetime stamp in top of the plot. With WaveForms app to improve the capture rate set: Update: Fastest, uncheck Noise, specify Samples, Edge Hist: Off (may work even with On), specify Buffers and Run: Buffer Stop For Buffers you can specify +1 since the first capture(s) seems to have a bit more delay, probably due to initial memory allocations. Make sure the Scope is not visible, like select Welcome tab, press Run button in Scope tab. Then export data using Script tool, looping through Scope.Buffer.value, like from 2 to 101 The ADP2230, ADP3X50 have device buffering which provides ~1us capture latency. This can be enabled under the dropdown before Buffer option. Since transfer does not influence capture latency, the View/Logging can be used to auto export captures sequentially. Custom app/script can perform better than WF app if less processing is performed between captures, like 4096 samples @ 100MHz on 2 channels at 1ms See the following example: AnalogIn_Triggers.py

Hi @David Aurora Thank you for your feedback. I will try to add such a feature asap.

Hi @HasNoCreek Use Counter Init and long Low

Hi @AHT Did you attach the 'Digilent USB Device' to the virtual machine ?