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