attila

Hi @m72 Thanks for the photos of the ancient equipment 😃 The record with analog only will be fixed in the next version, after the holidays, after January 8th.

Hi @jruff See the digital-io functions.

Hi @Ronnie In your project you are using the two AWG channels independently. The generates signals phase is given by the software start timing (FDwfAnalogOutConfigure) If you want these to be perfectly phased, see the AnalogOut_Sync.py AnalogOut_Phase.py examples.

Hi @Matty333 The impedance of coaxial cable is measured between the core and shield. The BNC adapter cannot be used directly since this connects shields to common ground. The impedance analyzer implementation has option for differential measurement but by default and also on the IA Adapter single-ended setup is used.

Hi @nakajii The oscilloscope inputs on ADP3X50 have 50 and 2V pk2pk rage. At low range the resolution and precision are better.

Hi @gabagool I don't know what could be wrong, it is working for me. Is the Digital Voltage set correctly ?

Hi @Ronnie For better performance turn off AutoConfigure, as it is in the earlier sample_bb2.py Is the "wait" causing you 'much latency' ? This is only needed for the first capture, after device connection, offset, range adjustment. For the following captures you only have to restart the generator. dwf.FDwfAnalogOutConfigure(hdwf, channel, c_int(1)) The analog-in rearms itself so you only have to wait for the capture to finish. There is no need for FDwfAnalogOutConfigure. while True: if dwf.FDwfAnalogInStatus(hdwf, c_int(1), byref(sts)) != 1: (For other use cases the analog-out can also be configured to restart itself.)

There is no need to uninstall since it will upgrade sections which are needed.

Hi @Ronnie See the following: simple_bb2.py - FDwfAnalogOutNodeDataSet expects data +/-1 normalized samples, this is multiplied by specified amplitude and offset added in the device - adding AnalogIn capture configuration - wait/sleep/delay should be used after offset/range adjustment for the levels to settle

Hi @m72

Hi @BigBob

Hi @linear_guy

Hi @amahpour For me it is working normally on RPI. Could you try the latest version ?

Hi @Ronnie There is nothing wrong with this piece of code, but it could be somewhere else. If you don't want to publicly post more script you could send it in private message. Edit: There is not function to return the data.

Hi @linear_guy The scroll will be corrected in the next version. The problem was that when switching between PNP and NPN (without adapter, ground reference level), the order in the preset list was not changed, but the scroll took it as if it had been changed. Fixed will be like this:

Hi @BigBob For path separator slash "/" should be used, eventually "\\" but not recommended. Backslash "\" is for special characters like "\t" tab, "\n" new line. Similarly "\\" denotes backslash and is used for paths on Windows. In WaveForms scripts you can use slash "/" for all OSs as path separator. It looks like when importing multiple files it may load the same file several times. It will be fixed in the next version today or tomorrow.

Hi @gabagool Which device are you using ? Please attach screenshots with the Logic Analyzer capture and Protocol.

Hi @Loic VINET For Digital Discovery, Analog Discovery 3, ADP3X50 and newer devices, on software connection the computer time is synchronized with the device. The time stamp for each capture is given by the device timer. The trigger time resolution is given by sampling rate (8/10ns) and for Digital Discovery at 100MHz or higher is 1.25ns The accuracy of the device timer is given by the device's crystal oscillator, but AD3, ADP3X50... can also use external reference clock. See the following example: DigitalIn_TriggerTime.py With 1Hz pulses generated by the same device the trigger time is precisely 1s step: By triggering on pulses from another device you can see the frequency difference between crystal oscillators, here ~4us/sec:

Hi @Ronnie Does the device work against the messages? -121 EREMOTEIO can be caused by short packets URB_SHORT_NOT_OK. I don't understand why something so standard and commonly used is being logged. I don't yet know at which location/level is this message enabled.

Hi @Ronnie Probably the BB USB port can't provide sufficient power. Try using powered USB hub or 5VDC supply for AD2.

Hi @Duh The next software version will improve/fix the mentioned custom signal preview in Patterns, taking in account delay and repetition parameters.

Hi @Mohammad Alsmadi 0.1X attenuation would require amplifying the input signal by 10. 10X attenuation is for 10X probe (1:10 probe in 10X position) which reduces the input signal from probe to the device by 10 and the software scales is back by 10 to represent how it is on the tip of the probe. With 10X the low range is up to 2V/div (1X=0.2V/div) and the ADC resolution ~1.3mV (1X=0.13mV). The 10X probe needs to be tuned. The 10 reduces the probe capacitance, increases the bandwidth. Depending on your requirements you could use AC coupling. For repetitive signals you could use the Time/Average.

Hi @Mohammad Alsmadi For 1X input set the channel Range to 200mV/div or lower, for 10X 2V/div or lower...

Hi @Anthocyanina To be coupled select 'copy from' for both channels, Channel 1 / Copy from: Channel2 and Channel 2 / Copy from: Channel1 This way, whichever you modify it will applied to the other channel. For 'sweeping modulation' you could use a custom waveform or play more samples from file or for AD3, ADP3X50 AM/FM source can be a Scope input. For AD3 the first/default device configuration provides 2048 modulation buffer. Select the 6th device configuration to have 8192 AM/FM buffer.

Hi @linear_guy The sweep/step can be changed with the following buttons: