Hi Tom,
On 14/06/2021 20.23, Tom McDermott wrote:
> But it is also generating:
> libgnuradio.grhpsdr.so.1.0.0git
> libgnuradio.grhpsdr.so.e487bf33
> Is the way my OOT's .so files (and no soft links) being generated a
> problem?
This should not be a problem for packages. One small problem when i
Hi again
I would like to ask you the following and I am also attaching the code for
clarity:
self.sink = uhd.usrp_sink(
",".join(("addr0=192.168.10.2,addr1=192.168.10.3", "")),
uhd.stream_args(
cpu_format="fc32",
channels=range(2),
),
)
self.source = uhd.usrp_s
I just thought, that the time difference I observed might be because of the
time difference in the execution of my python commands.
So, is there a way to validate my time synchronization between the 2 devices?
Thanks.
From: Discuss-gnuradio
on behalf of
Sky
On 06/15/2021 09:19 AM, Skyvalakis Konstantinos wrote:
t1 = self.sink.get_time_now(0)
t2 = self.sink.get_time_now(1)
t3 = self.source.get_time_now(0)
t4 = self.source.get_time_now(1)
print(uhd.time_spec_t.get_real_secs(t1))
print(uhd.time_spec_t.get_real_secs(t2))
pr
On 06/15/2021 09:34 AM, Skyvalakis Konstantinos wrote:
I just thought, that the time difference I observed might be because
of the time difference in the execution of my python commands.
So, is there a way to validate my time synchronization between the 2
devices?
Thanks.
You could do
I am so baffled as to why I am observing these 4 phase offsets.
I checked and the 2 devices are indeed successfully time synchronized.
I literally have no clue why this is happening.
You're sure there is no other workaround?
Many thanks.
From: Marcus D. Le
On 06/15/2021 11:43 AM, Skyvalakis Konstantinos wrote:
I am so baffled as to why I am observing these 4 phase offsets.
I checked and the 2 devices are indeed successfully time synchronized.
I literally have no clue why this is happening.
You're sure there is no other workaround?
Many tha
