Project

General

Profile

PostProductionTesting » History » Version 3

9600, 02/19/2016 10:52 PM

1 2 9600
= Post-production testing =
2 1 9600
3 1 9600
Basic checks to perform after production to make sure there are no critical issues with manufacturing.
4 1 9600
5 1 9600
== Required instruments: ==
6 1 9600
7 1 9600
1. Laboratory Power Supply Unit (PSU) 3-15V/0-2A with DC current indication or external ammeter.
8 1 9600
2. Voltmeter or multimeter with good accuracy.
9 1 9600
3. Spectrum analyzer, at least as good as Signal Hound.
10 1 9600
4. PC with 1GbE port, configured with IP 192.168.10.1/24.
11 1 9600
5. 1GbE capable cable, plugged into the PC port described above.
12 1 9600
6. RF cables, adapters, attenuators etc.
13 1 9600
14 1 9600
== UHD ==
15 1 9600
16 1 9600
You should download and [wiki:Building_firmware build] the Fairwaves version of UHD.
17 1 9600
18 1 9600
Then follow [http://files.ettus.com/uhd_docs/manual/html/build.html normal UHD build instructions]. You only need to build 'host' part of UHD.
19 1 9600
20 1 9600
== Testing ==
21 1 9600
22 1 9600
=== 1. Critical issues ===
23 1 9600
24 1 9600
Check that all [https://code.google.com/p/umtrx/issues/list?can=2&q=Priority%3DCritical critical issues] are fixed or worked around for the unit under the test.
25 1 9600
26 1 9600
=== 2. Short circuit ===
27 1 9600
28 1 9600
Adjust PSU current limit to 1-1.5A, set voltage to 3-4V and double check polarity. Apply power to UmTRX and check UmTRX current consumption with the PSU:
29 1 9600
30 1 9600
* If the current consumption of UmTRX is limited by the PSU, check the power polarity. If the polarity is correct, mark this UmTRX unit as defective with the "over-current" label.
31 1 9600
* If the current consumption is below the limit, slowly increase PSU output voltage to 12V. Current consumption should be less then 0.5A at 12V - probably around 0.3A (without Ethernet cable connected and without firmware loaded).
32 1 9600
33 1 9600
=== 3. DC-DC converters ===
34 1 9600
35 1 9600
Test voltages of all the following test points:
36 1 9600
|| C140 || 2.5V ||
37 1 9600
|| C138 || 1.2V ||
38 1 9600
|| C141 || 3.3V ||
39 1 9600
|| C131 || 6V ||
40 1 9600
|| U18 || 5V ||
41 1 9600
|| U28 || 3.3V ||
42 1 9600
|| U29-1, U29-2 || 3.3V ||
43 1 9600
|| U30-1, U30-2 || 2.5V ||
44 1 9600
|| U31-1, U31-2,[[br]]U32-1, U32-2 || 1.8V ||
45 1 9600
|| Collector Q3[[br]] near GBEth || 1.0V ||
46 1 9600
47 1 9600
=== 4. Clock source ===
48 1 9600
49 1 9600
Check that both switches of the S3 dip-switch are turned down (position "master"). Check that LED-I lights constantly (indicates that clock is OK) and LED-G lights constantly (indicates that GPS is powered on).
50 1 9600
51 1 9600
=== 5. Ethernet PHY ===
52 1 9600
53 1 9600
Plug in an Ethernet cable, connected to a 1GbE network.
54 1 9600
55 1 9600
* Current draw should increase by about 100-150mA.
56 1 9600
* LED6 and the right LED on the Ethernet connector should light constantly, LED5 and the left LED on the Ethernet connector might blink.
57 1 9600
58 1 9600
59 1 9600
=== 6. FPGA firmware ===
60 1 9600
61 1 9600
1. Switch off power.
62 1 9600
2. Connect JTAG adapter. 
63 1 9600
3. Switch on power back. 
64 1 9600
4. [http://umtrx.org/hardware/flashing/ Load firmware]. 
65 1 9600
66 1 9600
Firmware images:
67 1 9600
68 1 9600
* [http://people.osmocom.org/ipse/umtrx-v2/current/ UmTRXv2]
69 1 9600
70 1 9600
[[span(style=color: #FF0000, Describe LED status and debug port output.)]]
71 1 9600
72 1 9600
=== 7. GPS sync ===
73 1 9600
74 1 9600
Connect GPS antenna and wait for ~1 min for LED G to start blinking - this means that GPS sync is acquired.
75 1 9600
76 1 9600
=== 8. LEDs status ===
77 1 9600
78 1 9600
Check all LED's in according to functionality as described in [FeaturesAndTechnicalSpecification].
79 1 9600
80 1 9600
=== 9. LMS init ===
81 1 9600
82 1 9600
[[span(style=color: #FF0000, Describe for both LMS chips.)]]
83 1 9600
84 1 9600
Connect the spectrum analyzer (SA) to the TX1 port and set the SA and TX to the same frequency, e.g. 960MHz. Find the TxLO leakage level.
85 1 9600
86 1 9600
To check LMS control lines adjust its configuration.
87 1 9600
88 1 9600
Usual contents of *.bat* file to init basic functions:
89 1 9600
{{{
90 1 9600
set lms=%C:\Python32\UmTRX\umtrx_lms.py --umtrx-addr 192.168.10.2 --lms 1%
91 1 9600
%LMS% --lms-init
92 1 9600
%LMS% --lms-tx-enable 1
93 1 9600
%LMS% --lms-rx-enable 1
94 1 9600
%LMS% --lms-set-tx-vga1-gain -10
95 1 9600
%LMS%  --pll-ref-clock 26e6 --lpf-bandwidth-code 0x0f --lms-auto-calibration
96 1 9600
%LMS% --lms-tx-pll-tune 960000000
97 1 9600
%LMS% --lms-set-tx-pa 2
98 1 9600
%LMS% --lms-set-tx-vga2-gain 20
99 1 9600
%LMS%  --lms-rx-pll-tune 915000000
100 1 9600
%LMS% --lms-set-rx-vga2-gain 9
101 1 9600
%LMS% --lms-set-rx-lna 3
102 1 9600
}}}
103 1 9600
104 1 9600
=== 10. Modulated Tx ===
105 1 9600
106 1 9600
Generate a modulated signal and check power consumption by functionality as described in [wiki:PowerConsumption].
107 1 9600
108 1 9600
Exercise case as the modulated signal of UmTRX will be much higher than TxLO leakage and could damage your SA!
109 1 9600
110 1 9600
To get ideal GMSK modulation might be used the next example:
111 1 9600
{{{
112 1 9600
tx_samples_from_file.exe --rate 1083333 --freq 9478e5 --file gmsk.cfile --loop
113 1 9600
}}}
114 3 9600
To make measurements of phase error etc, better to [http://umtrx.org/applications/openbts/ run OpenBTS] after [wiki:LMS6002DCalibration].
Add picture from clipboard (Maximum size: 48.8 MB)