Re: [Openbts-discuss] First installation problems

[Tom T. <tom...@et...>]

On Thu, Jan 21, 2016 at 6:14 AM, Balthasar Indermuehle <ba...@in...> wrote:
> The first problem I had is there seems to be no way to tell
> transceiver which B200 to use - I have two connected to this system.
> transceiver -h does nothing, nor is there any text in the book
> describing operation of this. Odd. I temporarily solved that by
> disconnecting one - then the transceiver loads and initialises the
> B200. But then nothing happens. No lights come on, nor does anything
> show up on the terminal after the standard messages it prints when
> starting up the B200. It stops on the "Performing timer loopback
> tests" and that's that.

Timer loopback test is a UHD function. What is the output of uhd_usrp_probe?

You can pass UHD arguments to the transceiver with the following syntax.

    ./transceiver <number of ARFCN's> <UHD device arguments>

The number of ARFCN's for USRP devices is always 1 - the syntax
mirrors from the RAD1 transceiver. Valid device arguments can be found
below.

    http://files.ettus.com/manual/page_identification.html

For multiple B200 devices, you would most likely want to identify by
serial number, so the something like the following for the USRP with
serial number 1234567.

    ./transceiver 1 "serial=1234567"

> Can anyone provide some help here? Can transceiver be run in verbose/debug mode?

The transceiver logging can be set to DEBUG, but the output is
primarily for GSM slot and framing level data collection; the
information is of limited use for debugging device issues. Critical
device information and errors are output all all logging levels.

  -TT