I am unsure how to connect the LDAC (pin 4) and CLR (pin 5) pins. I want to have an immediate output without buffering and assume that I can tie LDAC low and leave CLR unconnected. Am I correct in connecting the DAC in this manner?
# Use the first detected context
contexts = iio.scan_contexts()uri = next(iter(contexts), None)ctx = iio.Context(uri)
# Find the ad5627 devicead5627 = ctx.find_device("ad5627")
# Find the voltage0/1 channels
chn1 = ad5627.find_channel…
AD5627 is actually present in your setup (iio:device0: ad5627). For AD7091, we found an issue that was preventing the driver to be probed (https://github.com/analogdevicesinc/linux/pull/923/commits/1cfe1f302f268de731ad8b9631913024868b88f7).
Do you have libiio installed ? You can verify this by running
adi@spandauhome:~$ iio_infoLibrary version: 0.21 (git tag: 359305c)Compiled with backends: local xml ip usb serialUnable to create Local IIO context : No such file or directory…
By the way, we have fixed another issue - the AD5627 I2C interface was not properly configured. I've updated: https://wiki.analog.com/_media/resources/eval/user-guides/ad-fmclidar1-ebz/socfpga_arria10_socdk_fmclidar1_2019_r1.zip - make sure to update…
//AD5627//DAC #define AD5627_VOUTA 0x00 //A A2 A1 A0(000) #define AD5627_VOUTB 0x01 //B A2 A1 A0(001)#define AD5627_BOTH 0x07 //AÇÒB A2 A1 A0(111)
//配置指令#define RESET_COM 0x28 //复位#define…
I followed what you provide and the result was:
root@analog:~# iio_info | grep device
IIO context has 5 devices:
iio:device0: ams …
I'm trying to access a ADRV9002 board through pyadi-iio library and libiio with the current (and hopefully newest) versions:
>>> iio.version(0, 21, 'b23a03b')>>> adi.__version__'0.0.5'
But I get this error when…
nanoDACs are a portfolio of products which combine small package, low power and low cost digital to analog conversion.
nanoDACs are monotonic DACs which can be powered off a single 3V or 5V supply and are available in the industries smallest packages…