FreeCalypso > hg > fc-rfcal-tools

comparison doc/Architecture @ 0:bd62be88259d

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
initial import of rfcal code and docs from freecalypso-tools repository
author Mychaela Falconia <falcon@freecalypso.org>
date Sat, 20 May 2017 18:49:35 +0000
parents
children
comparison
equal deleted inserted replaced
-1:000000000000 0:bd62be88259d
1 The RF calibration process fundamentally consists of 3 parts:
2
3 1: The FreeCalypso GSM MS device under test (DUT) to be calibrated;
4
5 2: An RF test station to which the DUT is connected via an RF coax cable,
6 performing the RF signal analyzer and signal generator functions required
7 for the calibration procedures;
8
9 3: A program that communicates with both the DUT and the RF test station and
10 orchestrates all of the signal generation, measurement and computation steps
11 to arrive at the final calibration results to be stored in the flash file
12 system of the DUT. The steps are too numerous, tedious and repetitive to be
13 performed manually, hence automation is required in order to make the process
14 practical.
15
16 The goal of the FreeCalypso RF calibration subproject is to produce a set of
17 tools for performing part 3 of the above breakdown. The current vision is that
18 our automated calibration software will be broken down into two interfacing
19 components:
20
21 1: There will be a Test System Interface Daemon (TSID) that encapsulates the
22 magic specific to a particular brand of RF test station, e.g., R&S CMU200.
23 The TSID will only talk to the CMU200 or other RF test station, but not to
24 the Calypso DUT, and the intent is that the TSID only needs to be started
25 once at the beginning of a calibration work shift and then stay running as a
26 hundred or more FreeCalypso GSM devices may be calibrated on the production
27 line. The TSID will present a local socket interface (can be changed to
28 TCP/IP if operation over a network is required) to which the other component
29 below will connect as a client.
30
31 2: There will be a set of 3 programs (fc-rfcal-vcxo, fc-rfcal-rxband and
32 fc-rfcal-txband) that perform the 3 required calibration groups for each
33 individual FreeCalypso device unit on the production line. The production
34 automation script will need to run fc-rfcal-vcxo first, then fc-rfcal-rxband
35 for each of the hardware-supported bands (e.g., 900, 1800 and 1900 on
36 FCDEV3B-900), then fc-rfcal-txband for each of the same bands. Each of these
37 programs will talk both to the DUT (via rvinterf) and to the RF test system
38 (via the TSID), i.e., will need to connect to an already-running rvinterf
39 process and to an already-running TSID via local sockets.
40
41 The programs in the second group above will contain no knowledge specific to
42 R&S CMU200 or any other particular brand of RF test station, instead this
43 knowledge is to be encapsulated in the TSID. The interface between the TSID
44 and its clients will be of a command-response nature, and will be defined from
45 the perspective of the needs of the FreeCalypso calibration process, rather than
46 from the perspective of the capabilities of the CMU200 - in other words, the
47 calibration automation program will command the TSID to the effect of "I need
48 this", and it will be the responsibility of the TSID to figure out how to
49 perform the required measurement or signal generation on the given type of test
50 equipment.
51
52 See the Test-system-interface document for the details of the TSID socket
53 interface.