I was wandering if there was an existing way to access the AD9361 auxiliary ADC/DAC from inside grc.
Yes, you can use the IIO Device Source/Sink blocks to do this.
Thanks for your help so far.
Now, to use these blocks I need info for the Device Name, PHY Device Name, Channels, and Parameters fields. I've poked around in this site for information regarding this task, but the best I could come up with is a suggestion to use iio_info to find the contents for these parameter strings. I have have run iio_info on the platform (ZedBoard+AD-FMCOMMS-EBZ) however the extensive results returned have an indecipherable correspondence to the physical hardware, at least to me, maybe others are sharper Are there clearer instructions to configure these blocks to read/write from/to the AUXADC/AUXDAC1,2 physical device pins?
As a 'hello world' exercise, I'd like to connect a sine signal source block to a correctly configured IIO Device Sink block and then connect my scope probe to the appropriate AUXDAC test-point pad on the AD-FMCOMMS-EBZ and watch a sine-wave on the scope screen.
I look forward to a breakthrough.
aux adc and sac are not iio triggered buffer channels. They are simple device attributes, which you can only access asynchronous.
Details on the necessary IIO attributes: AD9361 high performance, highly integrated RF Agile Transceiver™ Linux device driver [Analog Devices Wiki]
What information do I need to insert into the; Device Name/ID, PHY Device Name/ID, Channels and Parameters fields, (the fields shown in the dialog below) to be able to output a signal from either of the AUXDAC test pads on the AD-FMCOMMS3-EBZ eval PCB?
Sorry for the delay, I've been on travel.
Anyway, I was incorrect in my original response I thought the aux was a streamable device. However, they are just simple device attributes as Michael mentioned.
There isn't a standard way of doing this with the current GNURadio blocks since they are built for streams. To do this you will need to create a block that performs a C call to libiio: Device or utilize the libiio python binds to do the same.
Thanks, I saw that other post and it was a little mysterious - I'm an old RF guy and completely new to Gnu radio, libiio etc. However I did get the idea that to get things to work I'd have to do some digging on my own, which is as you can imagine is painful but nevertheless is progressing. quite well, but it's quite likely that I will have more questions later on.
I will probably end up making blocks that do this since they are very useful. Just need to find some time
Retrieving data ...