Re: [USRP-users] B210 initial tickcount offset

2018-05-23 Thread Thomas via USRP-users
--Oprindelig meddelelse- Fra: USRP-users På vegne af Thomas via USRP-users Sendt: Wednesday, 23 May 2018 20.54 Til: 'Ian Buckley' ; 'kf' Cc: usrp-users@lists.ettus.com Emne: Re: [USRP-users] B210 initial tickcount offset Hi Ian: that was also partly what we figur

Re: [USRP-users] B210 initial tickcount offset

2018-05-23 Thread Thomas via USRP-users
te <= RC_RESP_HEAD; else if(go) rc_state <= RC_DATA; _____ /fabric -Oprindelig meddelelse- Fra: USRP-users På vegne af Ian Buckley via USRP-users Sendt: Wednesday, 23 May 2018 20.11 Til: kf Cc:

Re: [USRP-users] B210 initial tickcount offset

2018-05-23 Thread Ian Buckley via USRP-users
There is a certain amount of (deterministic) latency incurred in the pipelining of H/W signals, both data and control. The tick count applied to the data will be accurate w.r.t the instant the data left the DDC and was packetized. -Ian > On May 23, 2018, at 2:26 AM, kf via USRP-users > wrote

[USRP-users] B210 initial tickcount offset

2018-05-23 Thread kf via USRP-users
Hi. I am having trouble understanding why the first samples I receive have a tick count offset of 7. My setup is:  - B210 with gpsdo  - Time source and reference set to 'gspdo'  - Two-channel RX  - Sample rate set to 16Mhz The procedure is then to  - Reset to time to 0 using the PPS signal  - Re