Hi Andreas,
When you set the subdev spec to "A:0 B:0" for both devices as you do in
this case, UHD now has 4 channels where channels 0/1 are on device 1 and
2/3 are o{n device 2. So, your streaming command is correct in choosing
{0,2} as the desired stream channels. But other parts of your code are not
because you have "num_chan" set to 2 and so you are only manipulating
channels 0/1 with your other commands. Perhaps you could set a vector at
the top such as:
std::vector<size_t> my_chan = {0,2};
and then you could have num_chan=2 (as is now) but then you always need to
use "my_chan[chan_index]" when providing a channel index to UHD (such as
tune commands or gain commands). This "my_chan" vector could be used
directly also in the stream args.
I don't know if this will fix your overall issue, but the channel indexing
needs to be modified to match what UHD is expecting.
Rob
On Fri, Aug 21, 2020 at 5:39 AM <andreas.bertheus...@kongsberg.com> wrote:
> > Can you resend the source code for the first case you describe below
> along with command line?
>
> I have attached the code for a channel mapping of (0,2) in siggen.cc. I
> also include my CMakeLists file.
>
> Program is run without arguments; ./siggen
>
> Attached output_case_1.txt shows the program output when outputs A and B
> on first X310 get enabled, and I do observe signals on those outputs.
> Attached output_case_2.txt shows the program output when outputs A and B
> on second X310 get enabled, but I _do not_ observe signals on those outputs.
>
> Looking back on the mailing list this also seems similar to the "issue
> about subdev spec" posted by Damon qi, earlier this month.
>
> Regards,
> Andreas.
>
> ________________________________
>
> CONFIDENTIALITY
> This e-mail and any attachment contain KONGSBERG information which may be
> proprietary, confidential or subject to export regulations, and is only
> meant for the intended recipient(s). Any disclosure, copying, distribution
> or use is prohibited, if not otherwise explicitly agreed with KONGSBERG. If
> received in error, please delete it immediately from your system and notify
> the sender properly.
>
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
