attila

Hi @RichSCorp The C code looks good if the hdwf and outBNC1 are correct, but what is before and after this? By default on the device close it is stopped. - You can use wait in the application until it is needed. - Or call the following before opening to continue running after close, see the earlier script dwf.FDwfParamSet(DwfParamOnClose, c_int(0)) I just notice the following 3 mistakes but this is not a showstopper. # analog-in dwf.FDwfAnalogInFrequencySet(hdwf, c_double(1e6)) # 1MHz sampling rate dwf.FDwfAnalogOutNodeEnableSet(hdwf, c_int(0), c_int(0), c_int(1)) # channel 1 enable dwf.FDwfAnalogInChannelEnableSet(hdwf, c_int(0), c_int(1)) # channel 1 enable dwf.FDwfAnalogOutNodeOffsetSet(hdwf, c_int(0), c_int(0), c_double(0.0)) dwf.FDwfAnalogInChannelOffsetSet(hdwf, c_int(0), c_double(0.0)) dwf.FDwfAnalogOutNodeAmplitudeSet(hdwf, c_int(0), c_int(0), c_double(5.0)) # 5 Vpk2pk range dwf.FDwfAnalogInChannelRangeSet(hdwf, c_int(0), c_double(5.0)) # 5 Vpk2pk range

Hi @Will_SC The script is run on device 1 and it is monitored by device 2 with WF app. sonar.py D1 Sc1 <-> D2 Sc1 <-> D2 W1 trigger pulse D1 W1 <-> D2 Sc2

Hi @EdWall Due to high voltages usually the ADG612 gets damaged, resulting in positive or negative top of scale readings (like +/-25V, +/-2.5V) First you could verify the resistors and the signal propagation on in the input path.

Hi @sergiodorazio The -runscript should be without space after the minus sign. On normal "taskkill /IM WaveForms.exe" the application may ask if you want to save the changes in the workspace but you can use "taskkill /F /IM WaveForms.exe" to force close the app.

Hi @RichSCorp See the following: # analog-in dwf.FDwfAnalogInFrequencySet(hdwf, c_double(1e6)) # 1MHz sampling rate dwf.FDwfAnalogInChannelEnableSet(hdwf, c_int(0), c_int(1)) # channel 1 enable dwf.FDwfAnalogInChannelOffsetSet(hdwf, c_int(0), c_double(0.0)) dwf.FDwfAnalogInChannelRangeSet(hdwf, c_int(0), c_double(5.0)) # 5 Vpk2pk range # trigger detector dwf.FDwfAnalogInTriggerChannelSet(hdwf, c_int(0)) # channel 1 dwf.FDwfAnalogInTriggerTypeSet(hdwf, trigtypeEdge) dwf.FDwfAnalogInTriggerLevelSet(hdwf, c_double(0.0)) dwf.FDwfAnalogInTriggerHysteresisSet(hdwf, c_double(0.1)) dwf.FDwfAnalogInTriggerConditionSet(hdwf, trigcondRisingPositive) dwf.FDwfAnalogInTriggerFilterSet(hdwf, filterAverage) # use average samples in trigger detector # analog-out 1: trigger->wait->run->repeat from trigger, rearm dwf.FDwfAnalogOutNodeEnableSet(hdwf, c_int(0), AnalogOutNodeCarrier, c_int(1)) dwf.FDwfAnalogOutIdleSet(hdwf, c_int(0), DwfAnalogOutIdleOffset) dwf.FDwfAnalogOutNodeFunctionSet(hdwf, c_int(0), AnalogOutNodeCarrier, funcSine) dwf.FDwfAnalogOutNodeFrequencySet(hdwf, c_int(0), AnalogOutNodeCarrier, c_double(20e3)) dwf.FDwfAnalogOutNodeAmplitudeSet(hdwf, c_int(0), AnalogOutNodeCarrier, c_double(1.0)) dwf.FDwfAnalogOutNodeOffsetSet(hdwf, c_int(0), AnalogOutNodeCarrier, c_double(0)) dwf.FDwfAnalogOutTriggerSourceSet(hdwf, c_int(0), c_int(trigsrcDetectorAnalogIn)) dwf.FDwfAnalogOutWaitSet(hdwf, c_int(0), c_double(20e-3)) # wait length dwf.FDwfAnalogOutRunSet(hdwf, c_int(0), c_double(50e-3)) # pulse length dwf.FDwfAnalogOutRepeatSet(hdwf, c_int(0), c_int(0)) # repeat forever dwf.FDwfAnalogOutRepeatTriggerSet(hdwf, c_int(0), c_int(1)) # repeat waiting trigger dwf.FDwfAnalogInConfigure(hdwf, c_int(1), c_int(0)) # just configure analog-in dwf.FDwfAnalogOutConfigure(hdwf, c_int(0), c_int(1)) # start analog-out

Hi @Chuankun The USB controller could be damaged by high USB voltage. Make sure to look for a faulty/unregulated USB hub supply to prevent further problems. You could try replacing the FT232H but likely other ICs on the board are damaged as well. The ADM1177 is probably fine, this is rated up to 30V

Hi @Chuankun See the following posts:

Hi @sourdoughconquistador It could be an issue with the ftdi library or usb driver. You could try updating the libftdo.so In the adept.runtime2.20.1 1.4.8 is included and the latest is 1.4.22 https://ftdichip.com/drivers/d2xx-drivers/ For me both are working.

Hi @m72 It is fixed in the latest version: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/ You could reset/load the factory calibration or perform a new calibration.

Hi @m72 I will post an update fixing "AD2 blue" tomorrow. Thank you for the observation.

Hi @Light For warranty and replacement the support dot digilent at ni dot com specifying the Date of Purchase, Seller and Purchase Order/ Web order Number. They will need your name, when you purchased the device, whom you purchased it from (i.e. Digilent or a distributor), and the serial number on the underside of the device. If you purchased the board from a distributor, you will need to contact them about their warranty.

Hi @Egenco You could modify the FTDI driver INF to have the same VID/PID you have accidentally programmed, see in device manager/ details/ hardware IDs. The INF file lists the VID/PID/interfaces the driver is associated to. https://ftdichip.com/drivers/vcp-drivers/ This modification will break the certification of the Windows driver so you have to boot with disable driver signature enforcement in order to install the driver. Then you should be able to connect with FT_Prog to your device to change the VID/PID back. Uninstall the driver with delete checked and reboot. https://hassanulmakers.wordpress.com/2015/03/13/unbrick-bricked-ftdi-chip/comment-page-1/

Hi @Light Try using the original USB cable the device came with, other USB ports of the computer or powered USB hub. Let us know if this help.

Hi @MiaPka It looks like the PLL is not working but the analog circuitry is supplied since the ADC IC does not give error. For warranty and replacement please contact support dot digilent at ni dot com They will need your name, when you purchased the device, whom you purchased it from (i.e. Digilent or a distributor), and the serial number on the underside of the device. If you purchased the board from a distributor, you will need to contact them about their warranty.

Hi @MiaPka Try with a newer version of software: https://reference.digilentinc.com/reference/software/waveforms/start https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

Hi @chrisdoe In about on month ADP3450 see: https://fb.watch/36SpWxtyIn/

Hi @mmachtey See the following: default.dwf3work plot1.X.data = Impedance.Traces.Trace.getData("Rs") var rs = [] Impedance.Traces.Trace.getData("Xs").forEach( function(x){rs.push(-x)} ) plot1.Y1.data = rs

Hi @brha0386 Could you post a screenshot or saved workspace? During Patterns reconfiguration (0.4-1ms) the signals are hold with the last value.

Hi @Dilum Fernando I've moved you question to a more appropriate forum.

Hi @mmachtey In newer WaveForms version you can find in Impedance Analyzer Nyquist as well Custom plots. https://reference.digilentinc.com/reference/software/waveforms/start https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

Hi @EdWall In case of the first screenshot if you have used BNC adapter this was probably set to AC coupling. The scope inputs wires are differential. The scope channel reads the difference between 1+ and 1- or 2+ and 2-. This for instance to measure the voltage drop (current) on a shunt resistor. Using it in single ended mode the negative inputs should be connected to ground. Connecting the positive to ground and negative to signal you will have voltage reading with "opposite sign". And always make sure to have common ground connection between the devices and circuits!

Hi @brha0386 var rg = String(FileRead("~/Desktop/default.csv")).trim().split('\n') Patterns.Channels.DIO0.custom = rg

Hi @Sairy The AD1/2 have two scope input ranges 5 and 50Vpk2pk https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/reference-manual#scope_input_divider_and_gain_selection

Hi @dbm Thank you for the information.

Hi @kaamil1984 128Mi sample recording at 1 channel at 125MHz will be suffice ?