Shenzhen Link-Card Tech Co., LTDMenu

Classic Detector Deep Dive: RTD6122CH Digital Output Timing and Configuration Word Fully Analyzed

Tech Blog · Classic Detector Deep Dive

Classic Detector Deep Dive: RTD6122CH Digital Output Timing and Configuration Word Fully Analyzed

Published 2026-09-12 · Link-Card Technology

The RTD6122CH is one of the main volume-production models among domestic 12 μm uncooled infrared detectors: a 640×512 active array, 14-bit digital output, on-chip 6-bit non-uniformity correction, and all control carried over a single SD0 serial line using in-band coding. Written for electronics engineers, this article consolidates the electrical parameters, the 408-bit configuration word, the output timing, and the debugging flow scattered across the datasheet into a single hands-on reference.

1. Device overview and array definition

The RTD6122CH is built on a vanadium oxide (VOx) microbolometer focal plane array (FPA); the readout integrated circuit (ROIC) is fabricated in CMOS and vacuum-packaged together with the sensing elements, making it a long-wave infrared (8–14 μm) uncooled detector. The output is 14-bit raw digital video: the detector performs only pixel readout and A/D conversion, while two-point NUC, defective-pixel replacement, image enhancement, and all other processing are left to the back end. The main imaging-related specifications are summarized in Table 1.

Table 1. RTD6122CH main specifications (imaging-related items)
ItemSpecification (conditions)
Array sizeActive array 640×512; full array 656×522
Pixel pitch12 μm
Sensing element technologyVOx microbolometer
Spectral response8–14 μm long-wave infrared
Digital output14-bit, row-by-row readout, white-hot polarity
Frame rate≤60 Hz (50/30/25 Hz commonly used)
Thermal sensitivityNETD <40 mK (f/1.0, 50 Hz, 300 K)
Thermal time constant<12 ms
Power consumption<170 mW (50 Hz, 25 °C, TEC excluded)
On-chip correction6-bit non-uniformity correction (OOC), per-pixel adjustment, effective in the current frame
Mirror functionIndependent X- and Y-direction mirroring (configuration-word control)
Operability≥99.5%
Operating temperature-40 to +85 °C
Package32-pin ceramic, 22×22×4.58 mm, weight ≤6 g

The array definition directly determines how the acquisition logic addresses the pixel stream, so an accurate spatial picture is needed first: the detector outputs 522 rows × 656 columns, of which rows 8–519 and columns 10–649 form the active array; column 654 is the on-chip temperature-sensor output (the DTEMP column) and column 655 is the test column (the TEST column), and all 656 columns are streamed out together with the pixel data. The coordinate origin is at the top left, with row numbers increasing downward and column numbers increasing to the right, as shown in Figure 1.

Output array diagram: positional relationship of the 656×522 full array, the 640×512 active array, the invalid regions, the DTEMP column, and the TEST column
Figure 1. Output array diagram (from Figure 1 of the RTD6122 Uncooled Infrared Focal Plane Detector User Manual V2.0, converted to grayscale)

The invalid regions are not meaningless: frame-structure and reference-signal identification, as well as dark-level observation, all rely on fixed column positions; the back end likewise computes column-address mapping and defective-column replacement in full-array coordinates (see Section 7).

2. Pins and power-supply design essentials

The detector pins fall into five functional groups, as listed in Table 2. The digital I/O is powered from DVDD (1.8 V), and the interface level is LVCMOS18.

Table 2. Pin functions by group (32-pin ceramic package)
GroupPinFunction
Digital outputDO3–DO0Pixel data, 4-bit multiplexed, LVCMOS18
Digital inputMCKMaster clock, LVCMOS18, 45–55% duty cycle
Digital inputSD0Configuration / reset / frame- and line-sync coded input, and OOC even-column data input; must be held high during power-on
Digital inputSD1OOC odd-column data input, LVCMOS18
PowerVDETSensor bias, 11 V
PowerAVDDAnalog supply, 3.3 V
PowerDVDDHDigital I/O supply, 3.3 V (may share a rail with AVDD, with ferrite-bead isolation)
PowerDVDDDigital core supply, 1.8 V
Analog filteringCAP1 / CAP2 / CAP3CAP1 and CAP3 each connect 1 μF to AGND; CAP2 (about 2.7 V) connects 1–10 μF (0805 package recommended) to VDET
Analog outputVTEMPOff-chip temperature-sensor output, sampled by the TEC temperature-control loop
Temperature controlTEC+ / TEC-Thermoelectric cooler drive
GroundDGND / AGND / DETCOMDigital ground / analog ground / sensor reference ground
OthersRESERVED / GETTERLeave unconnected

Power supply is the first pitfall in designing with this class of detector: the device is sensitive to supply noise, and noise on the analog section shows up directly in the image. The voltage windows, typical currents, and maximum allowed noise of the four supply rails are given in Table 3. Every supply pin needs 10 μF and 0.1 μF decoupling in parallel, with the 0.1 μF capacitor placed immediately next to the pin; VDET (11 V) is generated in two stages — a DC/DC boost followed by a low-noise LDO; low-noise LDOs are recommended for AVDD and DVDD (the reference design uses the ADP7102); and when DVDDH shares a rail with AVDD, it must be isolated by a ferrite bead.

Table 3. Power-supply requirements (currents are typical values; noise limits are RMS over a 1 Hz–50 kHz bandwidth)
PinVoltage/V (min–typ–max)Typical current/mAMaximum noise
VDET10.8 – 11.0 – 11.24.8930 μV
AVDD3.2 – 3.3 – 3.418.3250 μV
DVDDH3.2 – 3.3 – 3.41.181 mV
DVDD1.75 – 1.8 – 1.8511.691 mV

The maximum-current figures for Table 3 are the possible maxima at 85 °C (VDET 25 mA, AVDD 25 mA, DVDDH 5 mA, DVDD 25 mA); size the supplies with margin against these values. The digital-signal levels and the interface timing constraints are given in Table 4.

Table 4. Digital-signal levels and interface timing constraints (conditions: LVCMOS18, 5 pF output load)
ParameterConditionMinTypMax
Input high level VIHMCK / SD0 / SD11.5 V—DVDD+0.3 V
Input low level VILMCK / SD0 / SD1-0.3 V—0.3 V
Input leakage current—±10 μA
Input capacitance—2 pF
Clock duty cycleMCK45%50%55%
Input setup time T_setupSD relative to MCK1.5 ns
Input hold time T_holdSD relative to MCK1.2 ns
Output rising edge Tr10%–90%0.48 ns0.7 ns1.07 ns
Output falling edge Tf10%–90%0.36 ns0.53 ns0.86 ns
Output delay TdrRising edge relative to MCK3 ns4.4 ns6.4 ns
Output delay TdfFalling edge relative to MCK2.9 ns4.3 ns6.1 ns
Interface timing constraints: MCK clock, SD input setup/hold times, and DO output-edge delays relative to the clock
Figure 2. Interface timing constraints (from Figure 7 of the user manual, converted to grayscale)

The maximum output delay of 6.4 ns is already close to the half-cycle limit (6.6 ns) at 76 MHz (13.2 ns period) — although ordinary FPGA I/O needs no dedicated source-synchronous circuitry, the sampling point must land inside the data-valid window with margin to spare (see sampling-point adjustment in Section 7). The 5 pF load condition also means the DO traces on the PCB should be kept short: the larger the load capacitance, the tighter the timing.

3. The 408-bit configuration word, field by field

All operating parameters of the detector are packed into a single 408-bit configuration word (SmartData), written once over SD0, taking effect on the next frame, and held until reset or power-down. Thirteen groups of fields in the configuration word are directly adjustable; by function they fall into four classes — operating configuration, gain adjustment, operating mode, and output adjustment — as listed in Table 5.

Table 5. Complete list of adjustable configuration-word fields (default values from the factory configuration-word table; actual operating values are governed by the factory TestReport)
ClassFieldBit fieldDefaultMeaning and role in imaging mode
Operating configurationXMIRD1840Row-direction mirror: 0 = left to right, 1 = right to left
YMIRD1850Column-direction mirror: 0 = bottom to top, 1 = top to bottom
IRG<5:0>D328–D32339Frame rate: 39(d) = 50 Hz, 23(d) = 30 Hz, 19(d) = 25 Hz; MCK must simultaneously satisfy the line-period constraint
ADDR_A<9:0>D304–D2951023Defective-column replacement coordinate A (0–653, full-array columns; 1023 = disabled)
ADDR_B<9:0>D314–D3051023Defective-column replacement coordinate B; the two channels have no priority and should not be written with the same coordinate
Gain adjustmentINT_CAP<2:0>D188–D1863Integration capacitor, 3–10 pF (000–111); sets the CTIA equivalent gain (see Table 7)
INT_TIME<6:0>D175–D16970Integration time: Tint = (INT_TIME×32+16) × TMCK
RST_TIME<6:0>D182–D1767Analog reset time: Trst = (RST_TIME×32+16) × TMCK; constraint Trst ≥ 3 μs (50 Hz)
Operating modeSAB_END36210 = TCC mode, 1 = SAB (self-bias) mode; factory default is SAB
Output adjustmentGOF<6:0>D202–D19677Global offset configuration bits (positive correlation)
SFB_GOF<6:0>D209–D20377Self-bias global offset; in SAB mode this should be set the same as GOF
ADC_GAIN<6:0>D335–D32955ADC gain adjustment (positive correlation); works with GOF to calibrate the dynamic range
SFB_OOC<5:0>D195–D19032Array output mean adjustment in SAB mode (positive correlation); negatively correlated in TCC mode
NTCC<12:0>D223–D2117686Array mean adjustment in TCC mode, ineffective in SAB mode; bit weights <12:5> = 1, <4> = 1/2, <3> = 1/4, <2> = 1/8, <1> = 1/16, <0> = 1/32

Three constraints run through every configuration combination and should be checked before writing a configuration:

The factory provides complete default configurations for both SAB and TCC modes at 50/25/30 Hz (for imaging use). Table 6 analyzes the three SAB-mode default configurations field by field, showing how the fields track the frame rate.

Table 6. Field-by-field analysis of the three SAB-mode frame-rate default configurations (MCK taken as the smallest usable integer MHz)
Field50 Hz @ MCK=76 MHz25 Hz @ MCK=50 MHz30 Hz @ MCK=50 MHz
IRG (frame rate)39 (50.0 Hz)19 (25.0 Hz)23 (30.0 Hz)
XMIR / YMIR0 / 00 / 00 / 0
ADDR_A / ADDR_B1023 / 1023 (disabled)1023 / 10231023 / 1023
INT_CAP (integration capacitor)3 (6 pF)5 (8 pF)3 (6 pF)
INT_TIME707070
RST_TIME777
INT+RST constant-sum check77 ✓77 ✓77 ✓
Tint (actual integration time)29.68 μs45.12 μs45.12 μs
Trst (actual reset time)3.16 μs4.80 μs4.80 μs
SAB_EN1 (SAB)1 (SAB)1 (SAB)
GOF757572
SFB_GOF757595
ADC_GAIN576264
SFB_OOC333732
NTCC (ineffective under SAB)768671887686

The three configurations show a clear linkage: IRG sets the frame rate, MCK shifts gear with the frame rate, the integration capacitor sets the gain tier, and the output-adjustment fields pull the operating point back into the target window. The MCK choices — 76 MHz for 50 Hz and 50 MHz for 25/30 Hz — are the direct result of "the smallest integer MHz above the constraint minimum": at 50 Hz the minimum is 72.3 MHz, so 76 is chosen; at 25 Hz the minimum is 36.15 MHz and at 30 Hz it is 43.38 MHz, both rounded up to 50 MHz so that one clock source can be reused across the two frame rates. One caution: in the factory configuration of the 30 Hz tier, SFB_GOF (95) differs from GOF (72), whereas the manual requires the two to be identical in SAB mode; this tier is a legacy configuration, so when using it as a tuning baseline, re-check both fields first.

The choice of integration capacitor is a classic gain–dynamic-range trade-off; Table 7 gives the measured trends for the RTD6122CH at f/1, 50 Hz, 300 K (typical values).

Table 7. Integration-capacitor tiers versus typical responsivity, noise, and NETD (RTD6122CH, f/1, 50 Hz, 300 K)
INT_CAP<2:0>Integration capacitorRMS temporal noiseResponsivity SiTFNETD
0003 pF7.571 cnt285.462 cnt/K26.535 mK
0014 pF5.729 cnt212.251 cnt/K26.974 mK
0105 pF4.642 cnt169.172 cnt/K27.452 mK
0116 pF3.922 cnt140.665 cnt/K27.903 mK
1007 pF3.418 cnt120.669 cnt/K28.434 mK
1018 pF3.070 cnt104.647 cnt/K29.308 mK
1109 pF3.454 cnt92.952 cnt/K37.089 mK
11110 pF2.530 cnt83.477 cnt/K33.041 mK

The larger the integration capacitor, the lower the CTIA equivalent gain and output swing; the RMS noise count falls accordingly, but NETD does not improve — it degrades, because sensitivity is set by NETD = RMS/SiTF and SiTF falls faster than RMS. The correct use of a larger INT_CAP is to compress the output swing and expand the unsaturated headroom and dynamic range (the 8 pF choice in the 25 Hz default configuration is exactly this trade-off), not to raise thermal sensitivity.

4. SD0 in-band serial timing

The RTD6122CH has no dedicated frame-sync or line-sync pins: all control functions are carried as specific serial codes on the SD0 line, and SD1 serves only as the odd-column data channel during OOC write-back. The four SD0 function codes and their priorities are listed in Table 8.

Table 8. SD0 function codes (function priority: reset > configuration > frame sync > line sync)
FunctionCode
Reset (RST)27 consecutive "1"s followed by one "0" (27×'1' + '0')
Configuration (CONFIG)1111111_1010101, followed by the continuous write of the 408-bit configuration word
Frame sync (FS)1111111_1010011
Line sync (LS)1111111_1010111

After power-on, a reset code is sent first to return the internal state to a known starting point, then the configuration word is written; afterwards the detector enters steady state — one FS per frame period and one LS per line, with at least 2770 MCK cycles between the frame flag and a line flag and between adjacent line flags. The code patterns for reset and for configuration write are shown in Figures 3 and 4 respectively, and the complete frame/line sync timing in Figure 5.

Reset timing: 27 consecutive 1s followed by a 0 on SD0; the circuit enters and exits the reset state
Figure 3. Reset timing: 27 consecutive "1"s followed by a "0" on SD0 (from Figure 8 of the user manual, converted to grayscale)
Configuration data write timing: seven leading 1s, then the CONFIG header and the 408-bit configuration word written MSB first
Figure 4. Configuration data write timing: 408 bits written continuously after the configuration header, MSB first (from Figure 9 of the user manual, converted to grayscale)
Frame sync and line sync timing: FS and LS codes sent on SD0, adjacent codes separated by no less than 2770 MCK cycles
Figure 5. Frame sync and line sync timing: FS once per frame, LS once per line (from Figure 10 of the user manual, converted to grayscale)

In-band coding means the back end must generate the sync sequences bit by bit: on the FPGA side, a small pattern state machine typically drives SD0, inserting FS at the start of each frame and LS at the start of each line while guaranteeing the setup/hold relationship to MCK (Table 4). A fully written configuration word takes effect on the next frame; until then the detector keeps operating on the previous configuration.

5. Pixel data output format

Pixel data is multiplexed out over the four lines DO3–DO0, with the basic cadence: every 7 MCK cycles deliver 2 columns of 14-bit data — DO3 and DO2 always carry the odd columns, DO1 and DO0 the even columns; within a column the 14 bits are split between the two data lines, with DO3 (DO1) outputting D13, D11, D9, D7, D5, D3, D1 in sequence over the 7 cycles and DO2 (DO0) outputting D12, D10, D8, D6, D4, D2, D0 — that is, 1 bit per line per MCK cycle, 2 bits per line pair, bit-interleaved as shown in Figure 6. The DO signals change on the falling edge of MCK; the acquisition side is advised to sample on the rising edge of MCK (see Section 7 for sampling-point optimization).

Data combination format: the bit-interleaved output order of two columns of 14-bit pixel data within 7 MCK cycles
Figure 6. Data combination format: 7 MCK cycles output 2 columns — DO3&DO2 odd columns, DO1&DO0 even columns (from Figure 11 of the user manual, converted to grayscale)

Between the frame sync / line sync and the pixel data, the output stream embeds fixed reference data: after the frame sync, 8 flag words and 14 binary-weighted reference signals repeat until the next line sync; after a line sync, the reference data is output only once, followed by the 656 columns of pixel data for that line, with the DTEMP and TEST columns embedded at the end of the data stream, as shown in Figures 7 and 8 respectively.

Reference data timing after frame sync: 8 flag words and 14 binary-weighted reference signals output repeatedly
Figure 7. Reference data timing after frame sync (from Figure 12 of the user manual, converted to grayscale)
Reference data and pixel data timing after line sync: 22 reference words followed by the line's 656 columns of pixel data, with the DTEMP and TEST columns at the end
Figure 8. Reference data and pixel data timing after line sync: DTEMP (column 654) and TEST (column 655) embedded at the end of the data stream (from Figure 13 of the user manual, converted to grayscale)

Column 654, DTEMP, is the digital output of the on-chip temperature sensor: sensitivity about -33.8 cnt/K (fitted slope -33.756, R²=0.9998), with a typical output of 6867 cnts at 20 °C; part-to-part variation is corrected per the factory TestReport. The back end should retain the DTEMP column for real-time temperature monitoring, feeding temperature-dependent compensation and the TEC control loop.

The reference signals serve to calibrate the data channel: the 14 binary-weighted references (1–8192) span the full ADC range, and the 8 full-scale/zero flag words are used to identify the frame header and channel validity. The back-end acquisition logic should verify bit order and code values in the reference-signal segment first (see first-time bring-up in Section 7) before unpacking pixel data; the invalid-region data on DO (invalid columns, DTEMP, TEST) does not participate in imaging, but the DTEMP column should be retained for temperature monitoring.

6. OOC on-chip correction and write-back

The RTD6122CH's on-chip non-uniformity correction (OOC) applies a 6-bit offset adjustment to each pixel's output: the back end computes an OOC value for every pixel and writes it back continuously over SD1 (odd columns) and SD0 (even columns) — it takes effect in the current frame and must be sent every frame. The write format is 6 bits per pixel, with adjacent data separated by a "0" bit; starting 7 MCK cycles after the line sync, the OOC data for Pixel 0–653 is written in order. While row N is being output, the correction values for row N+3 are written; after the row-521 data has been written, rows 0–2 are written back, with the timing relationship shown in Figure 9.

OOC data write timing: starting 7 MCK cycles after the line sync, each pixel's 6-bit data is written over SD1 and SD0; row N+3 is written and takes effect in the current frame
Figure 9. OOC data write timing: SD1 for odd columns, SD0 for even columns; writing row N+3, effective in the current frame (from Figure 14 of the user manual, converted to grayscale)

The adjustment direction and quantization step of the OOC are set by device characteristics: the measured OOC–DOUT curve has a linear-region slope of about -871.99 cnt/LSB (R²=0.9999) — each +1 in the OOC value lowers the pixel output by about 872 cnt. The factory calibration goal is to sweep the OOC pixel by pixel and converge the full-array output within 8000±450 cnt; the correction values are designed around "a 900-cnt target window with a step effect of about 872 cnt", which guarantees a unique feasible OOC value for every pixel.

7. Bring-up and debugging flow

The user manual divides debugging into two phases: first-time and routine. In first-time bring-up, verify each item in sequence and do not move to the next until the current one passes:

  1. Power-supply check: with no load (detector not connected), measure the voltage at each POWER pin with a multimeter and confirm it falls within the Table 3 windows;
  2. Input-signal quality confirmation: capture the MCK and SD pin waveforms on an oscilloscope, check the transmitted data for correctness, and verify that levels and setup/hold satisfy Table 4;
  3. Output-signal quality confirmation: with the detector connected, re-measure each supply rail, then capture the reference data after FS and LS and compare it against the reference-signal sequences in Figures 7 and 8;
  4. Data-acquisition confirmation: read the reference data in the acquisition logic and verify the data combination format (Figure 6) and bit order.

If the reference data is wrong at step 3, go back over steps 1–2 and confirm probe contact; if the data combination is wrong at step 4, check the bit-interleaving in the program. Keep the no-load state throughout steps 1–2 to avoid damaging the detector.

Routine debugging starts from the factory TestReport and works through four stages in order (with the lens cap on, or facing a uniform surface/blackbody, throughout):

  1. Configuration write: write the TestReport configuration; set the OOC of the whole array to 32(d); acquire and check the reference data and the two monitoring columns — the DTEMP column mean should fall in 6000–7000 cnt and the TEST column mean in 14000–15000 cnt;
  2. ADC adjustment: increase GOF by 22 LSB and write it, adjust ADC_GAIN until the TEST column mean is as close to — and below — 16383 cnt as possible, then decrease GOF by 22 LSB and write it back — the ADC input range is 0–2.4 V and the output 0–16383 cnt; this step aligns the analog swing to the ADC full scale and maximizes dynamic range;
  3. DC adjustment: adjust SFB_OOC so the active-array output mean falls in 7000–9000 cnt (the target operating point); this step must be redone after the operating temperature range changes;
  4. OOC calibration: sweep the OOC value pixel by pixel so every pixel's output enters 8000±450 cnt; calibration is complete when the peak-to-peak of the full-array output mean falls within the threshold.

Sampling-point selection is the last step and the most easily overlooked: the DO signals change on the falling edge of MCK, so start by sampling on the rising edge of MCK, then move the sampling point step by step within the valid window and pick the best setting by image quality and array RMS — the typical symptoms of a poorly chosen sampling point are sparkling pixels in the image and RMS degrading from the normal ~4 cnt to ~6 cnt.

Two further usage notes: SD0 must be held high during power-on; and pointing the lens at direct sunlight causes permanent damage to the detector — avoid it both in debugging and in use.

8. Defective column replacement

If an electrically defective column appears in the output array (an entire column stuck at 0 or 16383), it can be replaced using the 2 spare columns at the end of the full array: write the defective column's full-array coordinate (0–653, including the left-side invalid offset) into ADDR_A or ADDR_B; after replacement, the columns following the defective one automatically shift forward by 1–2 columns and the spare columns fill in at the end. The two channels have no priority and must not be written with the same coordinate; when there is no more than one defective column, keep the other channel at the default 1023. Defective-column replacement should be done after power-on, before operating-point adjustment and OOC calibration; the factory TestReport configuration already includes defective-column replacement, but you must handle it yourself in a self-developed configuration.

Conclusion

The bring-up path for the RTD6122CH can be summed up as one main line: design the supplies and interface levels per Tables 3 and 4; work out MCK and the configuration word per Section 3 (IRG sets the frame rate, MCK is the integer MHz above the constraint minimum, INT+RST sums to a constant 77); generate the SD0 in-band codes and FS/LS sequences with an FPGA state machine; unpack the DO data with the 7-MCK/2-column bit interleaving and validate the channel on the reference-signal segment; and finally run the debug chain of TestReport configuration → ADC/DC adjustment → OOC calibration → sampling-point selection. Once this timing and configuration system is understood, integrating similar detectors with custom timing is just a matter of different code patterns and configuration fields.

References

  1. RTD6122 Uncooled Infrared Focal Plane Detector User Manual V2.0, Raytron Technology Co., Ltd., June 2025.
Back to Tech Blog

Need selection advice or a custom solution?

Link-Card provides thermal module selection, secondary development and full-system solution support.

Our sales team will reply to the email or phone number you leave. You can also email sales@link-card.com directly.