attila

Hi @suke The trigsrcAnalogOut outputs high while the instrument is running. The AnalogIn will trigger on rising edge (falling, either if configured), so the AnalogIn should be started before AnalogOut, or wait-run-repeat configured for AnalogOut.

Hi @suke The above approach should work but you have to process the data to look for transition in the sample array(s). For higher precision measurement you can use the Network Analyzer feature. First you could experiment with the WF app NA instrument then see the WF SDK/ samples/ py/ AnalogNetwork_Analyzer.py example. To use it at fixed frequency: ... for i in range(steps): while True: if dwf.FDwfAnalogImpedanceStatus(hdwf, byref(sts)) == 0: ...

Hi @dsula You can use: A: disable auto configure and apply after setting/adjusting one or multiple parameters without changing instrument state open device... FDwfDeviceAutoConfigureSet(hdwf, 0) ... other settings FDwfAnalogOutConfigure(hdwf, -1, 1) # 1=start enabled channels FDwfAnalogOut*Set(hdwf, ...) ... other settings if needed FDwfAnalogOutConfigure(hdwf, X, 3) # 3=apply X -1, 0, 1 B: use dynamic configuration, each setting will be applied immediately without changing instrument state open device... FDwfDeviceAutoConfigureSet(hdwf, 3) ... other settings FDwfAnalogOutConfigure(hdwf, -1, 1) # 1=start enabled channels FDwfAnalogOut*Set(hdwf, ...) # will apply See SDK manual and the following posts.

Hi @mmachtey The MaxAmplitude is 2.5V with the Analog Discovery.

Hi @szhbchr The WF is not yet available as MacOS ARM64 built. The WF app is working on M1 with Rosetta emulator. The WF SDK should also work with Python x86-64.

Hi @JoLe It looks like the device is damaged. For warranty and replacement contact the support.digilent at ni.com specifying the Date of Purchase, Seller and Purchase Order/ Web order Number. I suspect the AD2/TDI_USB signal is constantly driven low by IC35. Probably this NC7SZ126 is damaged. The version should be 0xE but it is masked to 0xA and reading 28Bytes passes (sending 0x1B) but reading 8Bytes fails (sending 0x7)

Hi @suke Use: FDwfAnalogInTriggerSourceSet(hdwf, trigsrcAnalogOut1)

Hi @chuckB Try using the original USB cable or other you have at hand. See in System Report or lsbusb if the device is detected, look for FTDI device. The LED in the AD2 only lights up after software connection.

Hi @Resul In the application the values can be accessed from Script, stored separately for various setups DutFirst(Adapter), ResFirst, Differential and analyzer or meter mode (Mtr) The compensation values are stored in workspaces/projects. In custom app/script you can use loops to measure open/short comp values for multiple frequency steps (like it is in AnalogImpedance_Analyzer.py), store these values and use later for normal measurements.

Hi @johnsomu The next software version will allow multiple enables/clocks for Sync.

Hi @cprosser See the Gray style in the latest WF beta version.

Hi @JoLe Which WF version and operating system are you using? Please try the "Force Programming", under Options or right-click. This will bypass the "Communication error" and tries to continue with the device initialization. You could also try to reprogram the USB EEPROM. In Device Manager hold down the Ctrl key until "My device is not listed" shows up and with this: press Find Device, make sure the proper device is selected and Program Device. Let me know if these help. If not, the device may be damaged.

Hi @triboguy See the application Help, press F1

Hi @Tood Use data compression by specify the interested DIOs, like for DIO 7 only: FDwfDigitalInSampleSensibleSet(hdwf, 1<<7) See DigitalIn_Record_Compress.py You can also set the FDwfDigitalInTriggerPrefillSet 0 to start streaming data only after trigger and specify samples after trigger with FDwfDigitalInTriggerPositionSet.

Hi @Josh Woods If millisecond precision is suffice the easies would be using software control, delay... For nanosecond level timing or device automated tasks you can use cross-triggering, wait, repeat... Sure, you can also start Wavegen and Patterns at the same time and use delay (Wait) in Patterns (FDwfDigitalOutWaitSet) Use trigsrcPC for both or trigger one by the other instrument.

Hi @vsethia Only the digital supply.

Hi @Josh Woods It can be done with Script or automatically if you are using one Wavegen run cycle. The Pattern could trigger on the falling edge of the Wavegen trigger, when its run cycle ends. Here I've only used Script to start the instruments in sequence.

Hi @bryan78 Unfortunately the ADP5250 will never support Pattern Generator or Protocols. The Logger for ADP5250 performs untriggered captures and the application measures DC and RMS values from these. For other devices the Logger uses scan sift acquisition. The following are not supported: - AnalogIn: acquisition modes: shift, screen, record; noise buffer, average filter, trigger holdoff, trigger types: pulse, transition, window - AnalogOut: play mode, device noise, AM/FM, wait, run, repeat - DigitalIn: acquisition modes: shift, screen, record, sync; noise buffer, timeout trigger, protocol trigger, - DigitalOut and Protocols

@malexandercould you help in this problem?

Hi @mmachtey The switching thresholds for "CV/CC Resistor" modes are the same as in the custom script examples. I've tested/tuned the method in script then added as C code for measurement mode. Based on the DUT VRMS measurement and desired value the generated signal amplitude is adjusted. If the target amplitude is above 2.5V (5Vpk2pk) it switches to lower resistor. The maximum would be 5V (10Vpk2pk) for Analog Discovery Wavegen but with 2.5V the Scope input can stay in low range 5Vpk2pk to have better measurement resolution. If the target is below 0.2V (2.5/12.5) it switches to higher resistor value. After a resistor change the measurement is repeated to fine adjust the amplitude for the new resistor value. const Voltage = 0.1 // desired VRMS const MaxAmplitude = 2.5 // maximum AWG amplitude if(Amplitude==0) { // first step, initialize Resistor = 1e6 Amplitude = Voltage*Math.SQRT2 Repeat = 2 // repeat step twice }else{ // adjust amplitude based on VRMS Amplitude *= Voltage/VRMS if(Amplitude>MaxAmplitude && Resistor>10){ // amplitude top limit, change resistor Resistor /= 10 Amplitude /= 10 Repeat = 2 // repeat step twice }else if(Amplitude<MaxAmplitude/12.5 && Resistor<1e6){ // amplitude low limit, change resistor Resistor *= 10 Amplitude *= 10 Repeat = 2 // repeat step twice }else if(Repeat){ Repeat-- }else{ Repeat = 1 // do each step twice, to adjust and measure } }

Hi @Mathias.SICK The AD has two input gain steps 5 and 50 Vpk2pk. The accuracies are for 0V common mode inputs (VinCM). The mV stands for max offset error and % for max gain error.

Hi @mmachtey The CV/CC modes works similar to the CV/CC script examples. Based on your request I've added to the latest software separate CV/CC options without and with resistor switching for IA Adapter.

Hi @cprosser The next sw version will have Gray/soft style option. I'm working on the qstyle of the remaining UI elements and adding Gray mode support the other various graphical elements. Than you for your post.

Hi @bryan78 If you are looking for the power supply voltage/current/power logging this is available in the Supplies tool. The support for Logger tool (using Oscilloscope channels) will be in the next software version.

Hi @tmk2z