summaryrefslogtreecommitdiff
path: root/RocketNames.mdwn
blob: 0ef0711492044ee848c676feb8ecd94cd8d6d454 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
# <a name="PSAS Naming Conventions"></a> PSAS Naming Conventions

(There are ANSI standards, Y1.1-1972, Y10.5-1968, Y10.19-1969, can't find them)

The purpose of this page is to document a framework for consistent usage within the project. The goal is to make the project easier. There are no enforcement mechanisms beyond infrequent whining.

- [[Designating Airframes|RocketNames#AirFrameNames]]
- [[Avionics Package Names|RocketNames#AvionicsPackageNames]]
- [[Component names|RocketNames#ComponentNames]]
  - [[Examples|RocketNames#ComponentExamples]]
  - [[Details|RocketNames#ComponentDetails]]
    - [[Component Type Codes|RocketNames#ComponentTypeCodes]]
    - [[Part Numbers by Function|RocketNames#ComponentNumberCodes]]
- [[Suggested Schematic Layer Numbers|RocketNames#SchematicLayerCodes]]

----

<a name="AirFrameNames"></a>

### <a name="Airframes"></a> Airframes

We have built a series of airframes of increasing size. The first was "LV0" for Launch Vehicle 0. The second "LV1", then "LV2". On occasion there have been multiple designs in the same size class, likewise there have occasionally been multiple copies of a single airframe design.

We encode this information as:

        <nop>VVNrC

Where VV is the vehicle identifier, "LV" or Launch Vehicle, in the case of the airframe, N is a single decimal digit identifying the design sequence. A single lowercase letter r identifies the design revision, and C is a digit identifying the particular copy of a design.

For example, after crunching an LV2a airframe in Aug. 2005 (LV2b was destroyed in an earlier flight), the next airframe design was designated LV2c, meaning the 3rd design revision of the LV2 airframe. The 1st incarnation of this design would be called LV2c1

Historical Note: We previously used a different naming system for the launch vehicle. LV2a was called LV2.1 and LV2b was called LV2.2.

----

<a name="AvionicsPackageNames"></a>

### <a name="Avionics Packages"></a> Avionics Packages

The avionics package is named in analogy to the airframe scheme.

        <nop>PPNrC

Here PP is the component group designator, "AV" for avionics. The NrC is just as explained in the [[Airframe|RocketNames#AirFrameNames]] section.

For example the avionics package designation in 2006 was AV2b. The "2" refers to the major design revision. In this case targeting the LV2 size airframe. We intend to keep the N-major revision of the avionics in sync with the N-major revision of the airframe. The "b" refers to the 2nd generational revision of the LV2-targeted avionics.

As a final example the 2nd copy to the "b" avionics targeting the LV2 airframe, and installed into the LV2c1 airframe would be LV2c1-AV2b2. Dropping the "AV2" is allowable LV2c1-b2.

----

<a name="ComponentNames"></a>

### <a name="Components"></a> Components

A very good feature to have is a unique designation for each part. Here is the basic form of a part number:

        TTTTNNNNFF

Where TTTT represents an alphanumeric type-code, and NNNN is a numeric part number. The FF field is the "extra" part number provided for special cases, normally this field is not used.

Sometimes a more elaborate scheme might be called for. Something like this:

        PPPPLL:BBBBB-VVVSS:TTTTNNNNFF.AA

This decodes as follows

[[!table data="""
Field | Type     | Length | Meaning                | Notes
[PPPP](#ComponentProjectCodes)     | alphanum | 1 - 4 | Project Code           | omit unless ambiguous
[LL](#ComponentLaunchNumber)       | alpha    | 0 - 2 | Launch Series          | use only if PPPP present
[BBBBB](#ComponentBoardDesignation)| alphanum | 1 - 5 | Board or Assembly Code | omit unless ambiguous
[VVV](#ComponentVersionNumber)     | numeric  | 0 - 3 | Integer Version Number | omit unless ambiguous
[SS](#ComponentSequenceCode)       | alpha    | 0 - 2 | Unit Build Sequence    | omit unless ambiguous
[TTTT](#ComponentTypeCodes)        | alpha    | 1 - 4 | Part Type Code         | see table
[NNNN](#ComponentNumberCodes)      | numeric  | 1 - 4 | Numeric Part Number    |
[FF](#ComponentExtraNumber)        | alpha    | 0 - 2 | Extra Part Number      | special circumstances only
[AA](#ComponentActualCode)         | numeric  | 0 - 2 | Actual Device Code     | special circumstances only
"""]]


<a name="ComponentExamples"></a>

**Examples**:

<dl>
  <dt> LV2:GPS1:D204.2</dt>
  <dd> Diode number 204 on GPS board revision #1 of Launch Vehicle #2. The suffix `.2&#39; refers to the 2nd part installed in this position. Normally a part is installed only once and no suffix is used. </dd>
</dl>

<dl>
  <dt> D204b</dt>
  <dd> Usually, the second component of a multi-part component called D204. Sometimes, undesirably, letter suffixes may be used to add distinct parts without re-numbering. </dd>
</dl>

<dl>
  <dt> LV2a:GPS03:VR204a.1</dt>
  <dd> Maximum--style part code. Launch Vehicle #2, flight `a&#39; (first flight), GPS board revision 3 (the `03&#39; is the same as 3). Variable resistor number 204a (Could be entirely unrelated to VR204!). The `.1&#39; refers to the 1st part installed on the board. Normally a part is only installed once, therefore most parts are implicitly designated `.1&#39;, the actual `.1&#39; is almost always omitted. Presumably a part labeled `.1&#39; has had a replacement contemplated at some point. </dd>
</dl>

<dl>
  <dt> Q101</dt>
  <dd> If there is no ambiguity, the simple form of the part number is used. In this case transistor number 101. </dd>
</dl>

<a name="ComponentDetails"></a>

**Details**:

The major field separator is the \`:' (colon), always used between major fields, such as between board designator and part designator. The \`.' (dot) is an optional subfield separator to disambiguate difficult cases, e.g. 802.1:R1100

<a name="ComponentProjectCodes"></a>

<dl>
  <dt> Project Code</dt>
  <dd> PPPP<br> For our purposes this will be of the form LV1, LV2, LV3, etc. This could be extended with a prefix like &quot;PSAS:&quot;. Ground support equipment might use another designator such as &quot;LTC&quot; for Launch Tower Computer. </dd>
</dl>

<a name="ComponentLaunchNumber"></a>

<dl>
  <dt> Launch Series</dt>
  <dd> LL<br> Flight sequence number. Follows the alphabetic sequence a, b, c,... z, aa, ab,... Note that this is a time sequence code as opposed to a serial number. Perhaps a date code could also be used here. </dd>
</dl>

<a name="ComponentBoardDesignation"></a>

<dl>
  <dt> Board or Assembly Code</dt>
  <dd> BBBBB<br> Board designation, alphanumeric, usually upper case. </dd>
</dl>

<a name="ComponentVersionNumber"></a>

<dl>
  <dt> Integer Version Number</dt>
  <dd> VVV<br> Board-level version number. Numeric starting from `1&#39;. Leading zeros are not significant. </dd>
</dl>

<a name="ComponentSequenceCode"></a>

<dl>
  <dt> Unit Build Sequence</dt>
  <dd> SS<br> Alphanumeric, lower case. a,... ab, ... Designates separate builds of the assembly. This is the serial &quot;number&quot; of the board. </dd>
</dl>

<a name="ComponentTypeCodes"></a>

<dl>
  <dt> Part Type Code</dt>
  <dd> TTTT<br> Designates what kind of part this is. For example `C&#39; is for a capacitor, `R&#39; for a resistor. The recommended codes are tabled below. </dd>
</dl>

<table border=1 cellpadding=0 cellspacing=0>
  <tr>
    <th bgcolor="#99CCCC"><strong> Component Type </strong></th>
    <th bgcolor="#99CCCC"><strong> Designation </strong></th>
    <th bgcolor="#99CCCC"><strong> Motivation </strong></th>
  </tr>
  <tr>
    <td> Power Diode </td>
    <td align="center"> CR </td>
    <td> Current Rectifier </td>
  </tr>
  <tr>
    <td> Signal Diode </td>
    <td align="center"> D </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Photo Diode, solar cell </td>
    <td align="center"> PD </td>
    <td> PhotoDiode </td>
  </tr>
  <tr>
    <td> Photo Diode, solar cell </td>
    <td align="center"> DL </td>
    <td> Diode `Lite&#39; </td>
  </tr>
  <tr>
    <td> PIN Diode </td>
    <td align="center"> PIN </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Zener Diode </td>
    <td align="center"> Z </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Transistor </td>
    <td align="center"> Q </td>
    <td> No idea </td>
  </tr>
  <tr>
    <td> Transistor Array </td>
    <td align="center"> QA </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Photo Transistor </td>
    <td align="center"> QL </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Resistor </td>
    <td align="center"> R </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Variable Resistor </td>
    <td align="center"> VR </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Resistor Array </td>
    <td align="center"> RA </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Thermistor </td>
    <td align="center"> RT </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> PhotoResistor </td>
    <td align="center"> RL </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Capacitor </td>
    <td align="center"> C </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Variable Capacitor </td>
    <td align="center"> VC </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Variable Capacitor Diode </td>
    <td align="center"> VCD </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Capacitor Array </td>
    <td align="center"> CA </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Crystal / Resonator </td>
    <td align="center"> X </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Inductor </td>
    <td align="center"> L </td>
    <td> No idea </td>
  </tr>
  <tr>
    <td> Variable Inductor </td>
    <td align="center"> LV </td>
    <td> VL sucks </td>
  </tr>
  <tr>
    <td> Inductor Array </td>
    <td align="center"> LA </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Strain Gage </td>
    <td align="center"> SG </td>
    <td> less generic </td>
  </tr>
  <tr>
    <td> Switch </td>
    <td align="center"> SW </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Integrated Circuit </td>
    <td align="center"> U </td>
    <td> Convention? </td>
  </tr>
  <tr>
    <td> Light Emitting Diode </td>
    <td align="center"> LED </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Transformer </td>
    <td align="center"> T </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Test Point </td>
    <td align="center"> TP </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Removable Jumper </td>
    <td align="center"> J </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Male Connector </td>
    <td align="center"> CM </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Female Connector </td>
    <td align="center"> CF </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Generic Connector </td>
    <td align="center"> CN </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Fuse </td>
    <td align="center"> F </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Ferrite Bead </td>
    <td align="center"> E </td>
    <td> Convention? </td>
  </tr>
  <tr>
    <td> Wire (also fixed jumper) </td>
    <td align="center"> W </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Wire Bundle </td>
    <td align="center"> WB </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Transient Voltage Suppressor </td>
    <td align="center"> TVS </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> EM Shield </td>
    <td align="center"> EMS </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> SCR </td>
    <td align="center"> K </td>
    <td> ??? </td>
  </tr>
  <tr>
    <td> other Thyristor </td>
    <td align="center"> Y </td>
    <td> ??? </td>
  </tr>
  <tr>
    <td> Motor, actuator </td>
    <td align="center"> M </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Piezo element </td>
    <td align="center"> PZ </td>
    <td>
    </td>
  </tr>
  <tr>
    <td> Battery </td>
    <td align="center"> B </td>
    <td>
    </td>
  </tr>
</table>

<a name="ComponentNumberCodes"></a>

Part Number NNNN
----------------

Never zero. Leading zeros are not significant. Part numbers need only be unique within a given board and revision, however, it is desirable that part numbers convey as much information as possible. We therefore try to keep them unique across a project, and to keep part numbers grouped by functional section.

Major subsystems have a common 4th digit, as in the case of the flight computer using 1xxx numbers, the GPS using 5xxx, etc. Current Nxxx subsystems are:

> [[!table data="""
Function              | TLA | numbers
Flight Computer       | FC  | 1xxx
Generic Node          | GFE | 2xxx
Avionics Power System | APS | 3xxx
Inertial measurment   | IMU | 4xxx
GPS                   | GPS | 5xxx
Telemetry (ATV, WiFI) | TLM | 6xxx
Pyro/Recovery         | PYR | 7xxx
Fin Control           | FIN | 8xxx
"""]]

Future Nxxx series systems are proposed to be:

> [[!table data="""
Function              | TLA | numbers
Magnetometer          | MAG | 9xxx
Pressure              | PRS | 10xxx
Propulsion control    | PRP | 11xxx
Backup uplink radio   | UPL | 12xxx
"""]]

Each major subsystem (Nxxxx) have application sections which have a common 3rd digit (xNxx). These are defined per major subsystem, but since some of the boards have commone components, some of the number range is reserved:

> [[!table data="""
Function                       | TLA | numbers
Switching Power Supply         | SPS | 000 - 099
High Availability Power Supply | HAP | 100 - 199
Microprocessor & Misc.         | UC  | 200 - 299
Application specific sections  | ??? | 300 - 999
"""]]

... which leaves 7 possible application section left per major subsystem.

<a name="ComponentExtraNumber"></a>

<dl>
  <dt> Extra Part Number</dt>
  <dd> FF<br> This field is legitimately used when a single logical part has multiple physical components. For example when two resistors are placed in series to increase power handling capability or precision, each resistor might be designated R101a, R101b, etc. A less legitimate use for this field is as a quick and dirty way to wedge part numbers into a previous scheme without having to re-number everything. </dd>
</dl>

<a name="ComponentActualCode"></a>

<dl>
  <dt> Actual Device Code</dt>
  <dd> AA<br> This field distinguishes between parts installed on the same board in the same place at different times. The field should always be separated from the part number by a `.&#39; dot. When a board is first assembled the parts are implicitly `.1&#39; coded. If a part fails or is otherwise replaced, the replacement becomes a `.2&#39; part. If the original part is reinstalled, it would again be the `.1&#39; part. </dd>
</dl>

----

<a name="SchematicLayerCodes"></a>

### <a name="Suggested schematic layer usage"></a> Suggested schematic layer usage

This is mostly for xfigs, but may apply more broadly.

<table border=1 cellpadding=0 cellspacing=0>
  <tr>
    <td> Components </td>
    <td> 100 </td>
  </tr>
  <tr>
    <td> Component Marks </td>
    <td> 90 </td>
  </tr>
  <tr>
    <td> Interface + Power </td>
    <td> 80 </td>
  </tr>
  <tr>
    <td> Labels </td>
    <td> 60 </td>
  </tr>
  <tr>
    <td> Values </td>
    <td> 40 </td>
  </tr>
  <tr>
    <td> Signals </td>
    <td> 0 </td>
  </tr>
</table>