• Home
• RFQ/EI
• Products
• Categories
• Manufacturers
• Tools
• Blog
• About Us
• Contact Us

THVD1420DR: RS-485 BOM Planning for Volume Production

Not on the evidence of the shared family alone. Its 500 kbps maximum rules it out for faster links, and compatible slower applications still need a timing and circuit review before AVL approval.

Table 1. Identity fields to freeze before requesting volume quotations

Source: TI datasheet, device information, package option addendum, and SOIC D0008A drawing; exact-part page checked September 20, 2026. Compiled by YG Group.

Keep the engineering revision of the circuit separate from the manufacturer's document revision. If a protection resistor or termination option changes, the assembly BOM must show that change even when the transceiver MPN stays the same. Conversely, an updated manufacturer datasheet should trigger a review of the affected requirements, not an unexplained change to the released circuit.

Define the interface before choosing the surrounding parts

The transceiver has one differential pair, A and B, shared between transmit and receive. It does not provide galvanic isolation, a communications protocol, or a guaranteed cable length at the maximum data rate. Those are system decisions.

Begin the design record with the actual bus: point-to-point or multipoint, intended signaling rate, cable characteristic impedance, longest cable, stub arrangement, connectors, ground reference, and the electrical environment at each port. Then identify which boards sit at the two cable ends. This determines where termination is fitted and avoids giving every node an unconditional termination resistor.

The datasheet recommends termination at the two ends of the bus, with resistor values matched to cable impedance. Intermediate nodes normally should not create additional full terminations. Its one-eighth-unit-load input specification describes receiver loading; the advertised node count does not establish that a particular 256-node cable layout will work at 12 Mbps. Stub capacitance, edge reflections, cable loss, and termination all remain relevant. TI datasheet, Sections 8.2.1–8.2.2, pp. 15–16.

For a product offered in several installation roles, make the termination a controlled assembly option or a clearly documented user setting. An unlabelled resistor marked “DNP if not required” transfers a circuit decision to manufacturing. The release package should name the board variant, fitted state, and installation role.

Bus polarity also belongs in the drawing. In TI's truth table, a high driver input produces A high and B low, with differential voltage defined as VA minus VB. Map that behavior to the connector's actual pin labels and the remote equipment's convention. Copying “A” and “B” names between unrelated equipment is insufficient evidence that the physical wiring is correct. TI datasheet, Section 7.4, p. 13.

Close both directions of the MCU voltage check

The THVD1420 recommended supply range is 3.0–5.5 V. Its driver-input and enable-input high threshold is 2 V minimum, while the permitted high input range extends to 5.5 V. This helps a 3.3 V MCU control a transceiver powered from 5 V. It does not, by itself, establish that the return path from the receiver output to that MCU is safe.

The receiver output R follows the transceiver's supply domain. TI specifies a high output of at least VCC minus 0.4 V under its stated load condition. With a 5 V transceiver supply, the MCU receive input therefore needs suitable voltage tolerance or a properly designed interface. Check the MCU's allowed input voltage, powered-off behavior, and input thresholds. A schematic note that says “3.3 V logic compatible” can hide this direction-dependent problem. TI datasheet, recommended operating conditions and electrical characteristics, pp. 5–6.

Table 2. Electrical boundaries that should appear in the design review

Source: TI datasheet, pp. 4–6. Compiled by YG Group. Absolute maximum ratings are stress limits; they are not extended operating specifications.

If the ground-offset requirement exceeds the available operating margin, changing the TVS alone does not solve the architecture. The design may require isolation and an appropriate isolated supply, together with a fresh system-level protection review. Those additions change the BOM, board space, and qualification plan substantially. Decide this before treating the interface as a routine eight-pin component purchase.

Make driver control part of the production specification

DE is active high; RE is active low. The device includes weak internal biasing that disables the driver and receiver when the respective enable inputs are left open. A production design should nevertheless document the MCU reset state and the intended bus behavior during boot, firmware update, watchdog reset, and power loss. External pull resistors may be appropriate when a deterministic state must hold against board leakage, noise, or another connected circuit. Their values should be chosen for that circuit, not copied without checking.

A particularly important timing distinction is whether the device is waking from shutdown. With the receiver already enabled, the driver's enable timing is specified on a nanosecond scale. When the receiver is disabled and the device must wake, the driver-enable maximum is 10 microseconds under the specified test conditions. Receiver wake-up also depends on the driver's state. At 12 Mbps, one bit is about 83 ns, so enabling the device and immediately transmitting can lose the start of a frame. TI datasheet, switching characteristics and measurement circuits, pp. 7–8 and 11–12.

The firmware release requirements should distinguish three events: waking the transceiver, enabling the transmitter, and releasing the bus after the final bit. Use the relevant maximum timing for each event, add the controller's actual timing uncertainty, and validate with an oscilloscope at the intended operating conditions. A UART transmit-complete event may be useful, but its precise meaning must be checked in the controller documentation; a buffer-empty event is not necessarily the end of the last stop bit.

These are manufacturing concerns as well as firmware concerns. A board may pass a slow bench demonstration and still fail an automated test that starts a transaction immediately after applying power. Define the startup wait and the test fixture's bus state in the production test specification.

Select protection for the required disturbance and data rate

TI specifies bus-pin IEC contact ESD, air-discharge ESD, and fast-transient performance. These are useful component-level capabilities. They do not certify the completed enclosure, connector, PCB, and power system against every disturbance. Surge energy, discharge location, return paths, and the applicable equipment test setup still determine the protection network.

The family datasheet contains a useful example with series pulse-proof resistors and a TVS. However, its illustrated 1 kV surge application is a THVD1400 circuit. The example uses a slower, 500 kbps member of the family; the accompanying waveform is not a THVD1420 12 Mbps validation. Treat the listed Bourns CDSOT23-SM712 and Vishay CRCW0603010RJNEAHP parts as components in that stated example, not as a universally approved THVD1420DR protection BOM. TI datasheet, surge protection example and component table, pp. 18–19.

For a THVD1420DR design, qualify candidate protection parts against both the disturbance and the signal:

• Check the TVS standoff and clamping behavior against legitimate bus voltages and the transceiver's stress limits, including tolerances and the relevant pulse current.
• Check capacitance and series resistance against signal amplitude, edge shape, and the actual cable load at the intended data rate.
• Check pulse energy and repetitive exposure for series resistors; a resistance value and package size alone do not establish a pulse rating.
• Place the protection path near the connector and provide a short, controlled return path so the PCB does not defeat the chosen component.

These checks may lead to an approved set of protection alternatives, but each alternative needs the relevant electrical and layout evidence. A purchasing substitution based only on “same voltage, same package” can change clamping or capacitance enough to invalidate prior tests.

Release a complete BOM, including optional parts

A useful interface BOM is a short set of controlled functions. It need not overpopulate the PCB; it must explain why each fitted or optional position exists.

Table 3. Recommended release fields for the interface BOM

Source: design-release framework compiled by YG Group from TI datasheet, application, supply, and layout guidance, pp. 15–21. Project-specific choices require project validation; this is not a tested reference design.

The on-chip failsafe behavior makes the receiver output high for specified open, shorted, and idle conditions. It does not tell application software which condition occurred. A product that must detect a broken cable still needs protocol-level diagnostics or a separate diagnostic strategy. Likewise, a failsafe receiver does not automatically justify removing external bias from a bus containing other receiver types. Evaluate the whole network. TI datasheet, receiver function table, p. 14.

Qualify THVD1400DR as a separate configuration

THVD1400DR is a useful related part because it shares the SOIC package option and the family interface arrangement. Its maximum signaling rate is 500 kbps, compared with 12 Mbps for THVD1420DR. It cannot replace the faster part in a design that needs more than 500 kbps.

Even below that limit, qualification should cover timing, edges, the protection network, and the intended cable topology. Slower edges can alter reflections and emissions, but this does not establish that every THVD1400 implementation is interchangeable with a THVD1420 implementation. The respective switching-characteristic tables must govern the review. TI datasheet, pp. 7–8.

Keep THVD1400DR as an engineering alternative under evaluation until the project has approved its configuration. If it is eventually accepted, record any restrictions in the AVL: maximum firmware baud rate, compatible product variants, and required test coverage. A procurement system should not silently substitute it solely because the family names differ by two digits.

Connect purchasing, assembly, and verification

Request quotations against the full MPN and an agreed delivery configuration. Include quantity, required delivery schedule, packaging condition, traceability documentation, and any approved lot or date-code constraints. Confirm the offered manufacturer identity and part marking against the manufacturer's information, while recognizing that marking alone is not a complete authenticity assessment. Avoid turning an unverified “equivalent” into a production line item.

For the assembly handoff, attach the SOIC D0008A package and land-pattern reference. The datasheet also contains DRL drawings, so the assembler should not select the first eight-pin drawing it encounters. Check feeder orientation and pin 1, solder-mask and paste choices, the actual shipment label, and the assembly site's qualified reflow profile. TI's example land and stencil drawings are starting points, not proof that every PCB process has identical tolerances.

A practical release test should answer four questions. First, does the device communicate correctly at the required supply and temperature limits on the intended cable? Second, does startup and transmitter turnaround remain reliable through the actual firmware sequence? Third, do the chosen protection parts preserve the signal while meeting the project's disturbance tests? Fourth, can manufacturing reproduce those results using the released board variant, assembly process, and test fixture?

Keep the answers attached to a configuration: PCB revision, firmware revision, transceiver MPN, protection MPNs, cable, termination state, and test conditions. Without that record, a passing result is difficult to reuse after an engineering change. Do not label a calculated margin or a planned test as a measured result.

Make the release package reproducible

A THVD1420DR volume BOM is ready when it identifies the exact orderable device and the circuit conditions that make it usable. Freeze the termination options, close the MCU voltage check in both directions, specify wake-up timing, and qualify the protection network at the real data rate. Give purchasing and manufacturing the resulting configuration and evidence, including the limits on any alternative. That is what allows repeat builds to reproduce an approved RS-485 interface.

References

1. Texas Instruments, THVD1400, THVD1420: 3.3-V to 5-V RS-485 Transceivers in Small Package with ±12-kV IEC ESD Protection, SLLSF78B, revised October 2021. Includes application examples, the package option addendum dated October 31, 2025, and mechanical drawings.
2. Texas Instruments, THVD1420DR exact-part ordering and packaging information, checked September 20, 2026. Dynamic status and packaging fields do not establish a committed delivery date.