17 Jun
2012
17 Jun
'12
9:32 p.m.
On Mon, Jun 11, 2012 at 7:12 AM, Alexander Chemeris
<alexander.chemeris(a)gmail.com> wrote:
On Mon, Jun 11, 2012 at 4:08 AM, Thomas Tsou
<thomastsou(a)gmail.com> wrote:
I'm running into this issue now, which was the reason I wasn't always
seeing transmit output. Workaround patch is attached along with the
corrected 'normal' rate GSM signal.
Thomas
If the load drops down and the signal transmits,
I wouldn't worry
about it for now. The likely condition is that there is a offset
between the initial arriving timestamp and the expected timestamp.
Because the receive timestamps drive the transceiver, the receiver may
run at 100% until the timestamp and expected value align. If OpenBTS
transmits consistently, then the system is in sync.
Aah! Yes, we have some issue with setting the timestamp with UmTRX.
E.g. I had to modify UHD examples which set timestamp to 0 on startup
and rely on this later on. With my change they read the actual value
of the timestamp and start from that. Could we do the same for
OpenBTS? 