attila

Hi @dave slagle Could it be a USB connection issue so the device gets occasionally disconnected? In this case a disconnect error should pop up quickly. It could also be an under-voltage or over-current problem so part of the device gets reset. In this case it could take longer for the error to show up. See the system monitor on the right of the status bar. The USB voltage should be above 4.5V and the current in idle ~350mA. You could try to use 5V DC aux power supply.

Hi @Fonso It may be useful to have such complex qualifiers as math channel.

Szia @Andras You could try to run the WF SDK/ sample/ py/ Enumerate.py to see if the lower level libs detect the device but I don't see too much chance to make it working soon.

Hi @eivind_k The record should be continued until it returns done then the buffer realigned to the last received sample. I would recommend using the latest software version. https://forum.digilentinc.com/topic/8908-waveforms-beta-download/ See: AnalogIn_Record_Trigger.py AnalogIn_Record_Trigger_int16.py

Szia @Andras There is no official FTDI driver for Windows ARM64: https://ftdichip.com/drivers/d2xx-drivers/ Here is some unsigned beta driver mentioned: https://answers.microsoft.com/en-us/surface/forum/all/surface-pro-x-usb-c-to-rs232-issues/3bc380dc-b018-4ad2-958a-e66c438c6b94?page=3

Hi @Sagi If you only want to read then leave the sub-address field empty.

Hi @Fonso No. Only edge (rise/fall/either), pulse length and transition (positive/negative less/more/timeout), window (entering/exiting); with hysteresis and holdoff are supported for analog inputs; and edge (rise/fall/either) for external or internal trigger signals. Happy New Year

Hi @Sagi The WF app supports all/the mentioned I2C specs. For devices with registers the first written byte(s) represent the register address. For 8bit regs the first bytes, for 16bit the first 2 bytes... To read from a register the direction needs to be changed with repeated start: [Start, I2CADR-WR, REGADDR, Sr, I2CADR-RD, DATA1, 2..., stoP] or [Start, I2CADR-WR, REGADDR1, 2..., Sr, I2CADR-RD, DATA1, 2..., stoP] Some devices require such restart other work fine with stop/start (separate write-register-address and read-data transfers). To write to a register the direction does not need to be changed: [S, I2CADR-WR, REGADDR, DATA1, 2..., stoP] or [S, I2CADR-WR, REGADDR1, 2..., DATA1, 2..., stoP]

Hi @Mario875 Yes. The pattern generator and logic analyzer can run independently or in parallel in the device.

Hi @ssm Use FDwfAnalogInBufferSizeSet(hdwf, 605)

Hi @suktan Unfortunately it is not supported. Happy New Year

Hi @Sagi In I2C the standard procedure to read a sub-address is [S, ADR-WR, SUBADDR1, 2..., RS, ADR-RD, DATA1, 2..., P] The RD/WR bit after Start/Re-Start Address specifies the direction of the following bytes. With WR only the master is allowed to send, slave acknowledges and with RD the slave sends bytes, master acknowledges. The [S, ADR-WR, master-byte, slave-byte...] would violate the I2C specs.

Hi @dave slagle Sorry to hear this. Could you post or send me the crash report ?

Hi @COMPACT In the software the maximum number of digital in/output lines is still 32.

Hi @kazu You could use a configuration like this:

Hi @bryan78 Thank you for the observation. Here you can find the specifications: https://digilent.com/reference/test-and-measurement/analog-discovery-pro-5250/specifications

Hi @Resul The steps are the following: Amplitude = 0 RepeatAmplitude = 0 theAmplitudeScript() // initialize Amplitude = 0 for the frequency range: measure(at freq step) theAmplitudeScript() if(RepeatAmplitude==0) next frequency step

Hi @Fortune It looks like the data read from the flash is corrupt (SN, name...) and reprogramming fails at verification... Do you happen to know how did it get it to this state ? Have you eventually used the "Linux USB Recovery" and accidentally overwrite or set flash fuses ? Try to reset the device by removing and reconnecting the power supply after a few seconds. To see the boot log please connect with a terminal app to the ADP and press "Apply & Reboot" in WaveForms/ Device Manager/ Boot

Hi @leonvs The system clock frequency could be wrong after software reboot. It will be fixed for the next version. Thank you again for the observation.

Hi @leonvs Unfortunately I don't think such trigger capabilities will be added soon.

Hi @cprosser I've managed to reproduce and fix it. With the current software version uncheck the Options/"Acquire Noise" (or Noise under Config) to prevent this error. Thank you for the observation.

Hi @AlanB You could use the 4th device configuration with 16Ki digital-io/out sample buffer. FDwfDeviceConfigOpen(#, 3, &hdwf) There is no digital play mode with AD2 but only with Digital Discovery.

Hi @jacobc There is no alternate cable with lock. The 30pin connection should provide sufficient support.

Hi @Blue21 In the next software version: The SDK Impedance function (FDwfAnalogImpedanceReferenceSet) will only control the DIOs used by Adapter, leaving the others unchanged configured by FDwfDigitalIO functions. In the WF application the unused DIOs with Adapter can be controlled under Options/DIOs or with Script.

Hi @Sagi Sure, you can add other channels/interpreters to Logic. You can also change the trigger source. The Help describes the useful features but you can use Ctrl+Space to list all the objects/functions.