Project

General

Profile

Feature #3628

document nanoBTS calibration procedure using ipaccess-config tool

Added by laforge 3 months ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
10/04/2018
Due date:
% Done:

0%

Spec Reference:

Description

The nanoBTS has the capability to OCXO calibration against another (macro) BTS. We had implemented this in ipaccess-config, but we apparently never documented how it works.

Let's add it somewhere to the nanoBTS related wiki pages.

Without trying, I remember that it was part of the "Tests" that can be triggered via OML.

static const struct value_string test_names[] = {
»·······{ NM_IPACC_TESTNO_CHAN_USAGE, "Channel Usage" },
»·······{ NM_IPACC_TESTNO_BCCH_CHAN_USAGE, "BCCH Channel Usage" },
»·······{ NM_IPACC_TESTNO_FREQ_SYNC, "Frequency Synchronization" },
»·······{ NM_IPACC_TESTNO_BCCH_INFO, "BCCH Info" },
»·······{ NM_IPACC_TESTNO_TX_BEACON, "Transmit Beacon" },
»·······{ NM_IPACC_TESTNO_SYSINFO_MONITOR, "System Info Monitor" },
»·······{ NM_IPACC_TESTNO_BCCCH_MONITOR, "BCCH Monitor" },

I think you start with a CHAN_USAGE to see the receive level per ARFCN. You then proceed to a FREQ_SYNC to see which of those have a FCCH (and hence are BCCH/CCCH carrying).


Related issues

Related to OsmoGSMTester - Bug #3560: nanoBTS multiTRX tests in osmo-gsm-tester Prod setup failingIn Progress2018-09-17

History

#1 Updated by pespin 3 months ago

  • Related to Bug #3560: nanoBTS multiTRX tests in osmo-gsm-tester Prod setup failing added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)