AD4134
Recommended for New Designs
The AD4134 is a quad channel, low noise, simultaneous sampling, precision analog-to-digital converter (ADC) that delivers on functionality, performance...
Datasheet
AD4134 on Analog.com
AD7134
Not Recommended for New Designs
The AD7134 is a quad channel, low noise, simultaneous sampling, precision analog-to-digital converter (ADC) that delivers on functionality, performance...
Datasheet
AD7134 on Analog.com
I am trying to configure the AD4134 in 4-Wire SPI Control Mode with an ESP32-S3. After studying the documentation in detail there are still some questions left open especially regarding SPI timings. The "Virtual Eval" tool also did not provide the necessary information, eventhough it's a great help.
Setup:
Questions:
I attached two screenshots trying to write and subsequently read the INTERFACE_CONFIG_A register. I get the following results, which do not seem right to me. After writing 00010000 I would expect reading 00010000 (or 00011000 with mirror bit). Furthermore the STATUS byte changed from 00000000 to 10000000 (or 11000000 depending on the correct CPHA setting).


Could you comment on possible reasons for this behaviour?
I hope some expert from Analog can help out with those questions. Thanks in advance.
Kind regards,
Patrick
Hi,
Apologies for the delayed response. We will look into this. I will contact the product owner and get back to you.
Regards,
JC
hi Patrick
my replies according to the Question numbers
1. Figure 4 describes the SPI timing which is supported by most uC's
2. it is a 1 bit status sent by the AD4134 which is the error bit, which indicates that the previous frame had a read, write, or CRC error.
3. No, Only in PIN control mode
4. See Table 5 in Datasheet
5. See Table 5 in Datasheet
6. No
Lastly for Reading a register your Command should be 0x80 (R+7 bit address), which is not being followed as per my understanding. so if you write 0x81 (R + address 0x01 ), 0x00 on SDI line you should read back 0x80 or 0xc0
thanks
Hi Wa$iM,
thanks a lot for your reply. The hint with Table 5 and Figure 4 helps a lot. Those are not referenced anywhere else in the documentation. For me it seems the ESP32-S3 fullfills all timing requirements, but i am still getting responses that make no sense to me. Thus i will assemble another prototype to exclude that hardware issues are causing this problem.
In the meantime could you maybe confirm (in regards to question 2), that the error bit is 1, if an error occured and 0 if not?
Thanks a lot!
Greetings,
Patrick
Hi pre ,
This error bit is the NO_CHIP_ERR bit. This bit is cleared if any of the other status error bits are set. This bit sets back to 1 when all the status bits are cleared, indicating no chip error.
Thanks,
Janine