attila

Hi @Mesh_Houston Set the jumpers behind the BNC connector to DC.

Hi @Rohan16 Yes, add manually, use workspace Use Ctrl+Space or check Edit/'Code completion' but too many suggestion can be disturbing in writing, see the Help tab

Hi @Rohan16 Probably you have no signal added with name DIO24 See the following:

Hi @aminoh If the libqt5 multimedia, script and serialport are installed the 'base' is already installed. (All these dependencies should be installed automatically when installing waveforms, but it looks like suse would need different requisite naming.) Try to install waveforms with force, option 2

Hi @JAlaj If you are listening on signal use Protocol/SPI/Spy 'Receive to File' or for SPI master write a Custom script or Sensor for precise hardware timer.

Hi @bryan78 Which software version are you using ? Could you provide more detail about the issue ? It seems to me working correctly. I notices some delay with Protocol/UART/Spy at lower rates, which needs improvement in the 'firmware'.

Hi @Ostin Flores It is linear average of Vrms values. The latest version adds "RMS average" option.

Hi @sintech 1.

Hi @Fonso

Hi @Marcus Watson If you are capturing up to device buffer size of samples you can use acqmodeSingle, see WF SDK/ samples/ py/ AnalogIn_Acquisition.py, AnalogIn_Trigger.py.... This does not need loop, but you should verify if the capture is done with FDwfAnalogInStatus before reading the data. The record mode is for capturing more samples at lower rate, using data streaming and this requires loop to transfer the chunks of data.

Hi @Al B. The 4 USB host ports are only available with Linux boot mode.

Hi @erikderuijter I'm not familiar with this unmaintained 'WF_SDK' wrapper. See the WaveForms SDK manual and examples. The indexing in code is base 0, 4th is 3

Hi @game890921 Cut, 'Add tab with visible data', select Tab, Export

Hi @aminoh It looks likes the following dependencies need to be installed manually: sudo zypper install libQt5Multimedia5 libQt5Script5 libQt5SerialPort5

Hi @Kenji_T The Probe option in the application is a software feature, it cannot have specifications. This scales the oscilloscope input, voltage reading in the specified way and displays the units you want, similar to a math channel. The used hardware probe should match the oscilloscope specifications.

Hi @Ostin Flores For averaging calculate the average of multiple frequency domain results. For triggered repetitive patterns/signals time domain averaging may provide better result.

Hi @mrb-bt Amplitude setting and Channel# reading unit is V, peak to peak voltage / 2 if(Channel2 == 0) return Target; // return initial amplitude This is the amplitude very first amplitude setting for initial value. The readings are never going to be 0.0000000, always above 0. You can also use if(Frequency==0)... Repeat = abs(Channel2 - Target) > 0.1; // repeat step if needed Yes. The earlier will force the step to be repeated if the difference between the target and channel reading is above 100mV. For dB use 20*log10(Channel#/Amplitude)

Hi @Shalin I spent a few days with this and then realized the approach I had chosen would not work. Please don't wait for this, I don't know when I will have time to try to make it happen again.

Hi @sintech 1. The next version will remember the last dialog positions. 2. I'll try to implement such option later.

Hi @aminoh The waveforms rpm is signed in the latest version: The adept runtime release should be updated soon. In the future the Linux packages will be signed automatically by the build script. Thank you for the observation.

Hi @PhilipJ Isn't the Events view helpful ? The 'blue arrows' on signal row moves to the next/previous edge and on the protocol row to the protocol specific event/value.

Hi @fractalbrain I'm glad it works. Thank you for the advice.

Hi @clb The latest version adds auto leveling possibility for Network Analyzer.

Hi @liu The phase adjustment for different number of custom samples than the device buffer size if fixed in the latest version.

Hi @HasNoCreek See the examples and manual: FDwfDigitalInTriggerSet(hdwf, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF) is not a valid trigger, DIN15:0 to be high and low at the same time and also to be either edge, rising or falling. FDwfDigitalInStatus with false (0) instructs to not fetch capture data from the device.