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