attila

Hi @adang Logger.Loggers.clear()

Hi @Wayne Contello It looks like in some places instead of the Digital color the Style is used. As a solution use the Dark Style option.

Hi @sergiodorazio At the time when these arguments where added the Script had no tabs, only one script could exist. The next WF version (3.16.31) will support selecting the tab, reusing the script argument to load a file, like: WaveForms mywork.dwf3work -script "tab 2"

Hi @kazu It could be done like this: for(var t = 0; t < 10 && wait(0.5); t++){ // wait 500ms Scope.single() Protocol.I2C.Write(0x2A) Scope.wait() // Scope trigger on Ch0-SDA falling, T0 var rg = Scope.Channel2.data // SCL var i0 = Scope.Channel2.IndexOfTime(0) // sample index at T0 var i1 = 0 // count SCL samples above 1.5V, dT SDA->SCL while(i1 < rg.length && rg[i1]>1.5) i1++ var dt = (i1-i0)/Scope.Time.Rate.value print(t, dt*1e6,"us") }

Hi @HILO Yes, it is broken. The next build will be out soon. Thank you for the observation.

Hi @sergiodorazio The selected script tab will be executed, as the workspace was saved. Save separate workspace with each script.

Hi @Brian Hall See the WF app Help.

Hi @oconn828 See the following post:

Hi @sergiodorazio Voltmeter.run() wait(0.1) for(var i = 0; i < 10 && wait(Voltmeter.State.Update.value); i++){ print(Voltmeter.Input.Channel1.DC.value) }

Hi @Lidong Master enable Off: Supplies.MasterEnable.setChecked(false) or Supplies.MasterEnable.value = 0 V+ Off: Supplies.Output.PositiveSupply.Enable.setChecked(false)

Hi @sergiodorazio Notice that you place the voltage reading to "vPtt1" and later used "vPtt" The Voltmeter already performs averaging. The DC is calculated based on average of the specified Update rate. If you want to average it further, use wait at least this amount of time, like: wait(Voltmeter.State.Update.value)

Hi @Lidong Set trigger to None to capture immediately. Use wait() function for pause in script, like settle.

Hi @logicmax if(!FDwfAnalogOutNodeEnableSet(hdwf, i, 0, 1)) return false; if(!FDwfAnalogOutIdleSet(hdwf, i, DwfAnalogOutIdleInitial)) return false; if(!FDwfAnalogOutTriggerSourceSet(hdwf, i, trigsrcExternal1)) return false; if(!FDwfAnalogOutTriggerSlopeSet(hdwf, i, DwfTriggerSlopeFall)) return false; if(!FDwfAnalogOutWaitSet(hdwf, i, 1e-6)) return false; if(!FDwfAnalogOutRunSet(hdwf, i, 2e-6)) return false; if(!FDwfAnalogOutRepeatSet(hdwf, i, 0)) return false; if(!FDwfAnalogOutRepeatTriggerSet(hdwf, i, 1)) return false; if(!FDwfAnalogOutNodeFunctionSet(hdwf,i, 0, funcPulse)) return false; if(!FDwfAnalogOutNodeFrequencySet(hdwf, i, 0, 500e3)) return false; if(!FDwfAnalogOutNodeAmplitudeSet(hdwf, i, 0, 1.0)) return false; if(!FDwfAnalogOutNodeOffsetSet(hdwf, i, 0, 0.0)) return false; if(!FDwfAnalogOutNodeSymmetrySet(hdwf, i, 0, 0.05)) return false; if(!FDwfAnalogOutNodePhaseSet(hdwf, i, 0, 0.0)) return false;

Hi @Popylala If you have no load or short on the V+, probably this is damaged. Do you have any idea how could this happen? What was the setup in the recent experiments? Did you connect high voltage to V+ ? For warranty and replacement contact the support.digilent at ni.com specifying the Date of Purchase, Seller and Purchase Order/ Web order Number

Hi @Popylala The voltage drop on the USB cable could be high, leading to lower device supply voltage and current increase. Try using other USB cable, socket, powered USB hub or 5 VDC AUX power supply for the device.

Hi @batesenergy 1. You could connect to the ADP over USB or Network. Currently the Network access is working in the same LAN. The connection is based on discovery which is probably not working over VPN. From the host computer it can be used in device mode with WF app or applications/scripts based on WF SDK. The next software version will add support for remote devices... 2. The ADP can also be used in embedded Linux boot mode. In this mode it can be used as well as device (like in step 1 over bridge-service) or any custom application can be run in the device. Applications/scripts based on WF SDK can access the ADP interfaces or other devices connected to the USB ports or over network. These apps/scripts can be developed-tested on computer then run/ported to embedded mode. 3. You could also install vncserver, a desktop and the amrhf build of WaveForms on the ADP-Linux. This way you can have remote access to ADP running WF app or other apps.

Hi @1988maciejt Sure, suggestions are welcome.

Hi @1988maciejt Drag the splitter from the right ? I've made this splitter non-collapsible for the next sw version.

Hi @edwardjs Do you have ground connection between the devices? Make sure the wiring is correct, which DIO is used for which signal. Use the Logic Analyzer or Oscilloscope to see the signal timings and levels.

Hi @1988maciejt This is the first time I hear such problem. I don't know what could be wrong... eventually some Windows security options. 1. Try running WF as Administrator. 2. Uninstall WF and make sure to delete the C:/Program Files (x86)/Digilent folder to remove any locked/remaining files-folders and reinstall. I've added for the next software version to show the url as placeholder text in case the page is no loaded.

Hi @enelson

Hi @James Aguirre I just notice this question. The THD and other measurements are available in the Spectrum interface.

Hi @enelson I see the problem now in XY at high offset/range ratios. It is fixed for the next version. Thank you for the observation.

Hi @1988maciejt Try reinstalling the WF application. The html files for help should be deployed to: C:\Program Files (x86)\Digilent\WaveForms3\doc\ Use Help/Browse to open in default browser.

Hi @blaugios The record length with (AD2,ADS...) is unlimited at lower rates (up to about 1-2MHz) that fits through the USB streaming. See the WF SDK/ samples/ py/ AnalogIn_Record.py AnalogIn_Record.py AnalogIn_Record_Wave_Mono.py .... 300M samples at 1MHz: AnalogIn_Record1.py The Analog Discovery Pro 3000 series will seamlessly use the internal DDRam for buffering to allow up to 128Mi samples and up to 125MHz.