Skip to main content
Explore ERDILRF

Press ↑↓ to move, Enter to open, Esc to close.

Rangefinder UART Logic: Supply Is Not Signal Level

A rangefinder’s supply voltage is not its UART logic level. Before connecting a host, check the power input separately from the transmit and receive signal limits in both directions. If the electrical limits are missing, leave the data lines disconnected and request the applicable specifications for the delivered unit; neither a supply range nor the label “UART-TTL” proves that a particular host is compatible.

Separate the power rail from the signal domain

The supply specification describes the voltage presented to the module’s power input. UART signal specifications describe what each transmitter produces and what each receiver accepts. Those are different electrical interfaces, even when they share a reference ground. A module can have a supply range that tells you nothing about the safe voltage on its receive input.

There are two independent signal paths: module TX to host RX, and host TX to module RX. For each path, the receiver must recognize both the transmitter’s low and high output levels, and its input must remain within its allowed limits. Nominal logic labels alone do not establish those conditions. The comparison should cover the operating voltage and conditions of both devices, not just a typical value at room temperature.

Do not connect a signal pin to a power rail as a substitute for data wiring. Likewise, matching the UART baud rate is not evidence of electrical compatibility: a serial port may be configured correctly in software while its input is being driven outside its permitted limits.

What the two model records actually say

The LRF50H model record specifies a 9–36 V DC supply and a UART interface. Its source does not specify the UART logic level. The supply range must therefore not be used as the signal voltage, an input-tolerance limit, or a reason to select a particular adapter. Request the missing TX and RX electrical limits for the delivered configuration before completing the signal connection.

The LR1000E2 model record lists a 3.3–5 V supply and a UART-TTL interface. It also records a 3.3 V TXD/RXD logic level from an oral confirmation; that is not a written signal-level specification in the manual or product page. Even that confirmation does not establish the receive pin’s absolute maximum, threshold limits, output drive, or behavior when either device is off. Request written, batch-applicable limits before deciding whether the host can connect directly.

For LR1000E2, connector numbering and enable polarity are confirmed per delivered configuration. Confirm the connector view, harness and enable requirements for the actual unit; do not assume a wire color or a connector viewing direction.

A decision tree for each UART direction

  1. Identify the transmitter and receiver. Label module TX to host RX and host TX to module RX as separate paths. Obtain the host board’s own pin documentation; a processor family name is not enough to identify a board’s interface.
  2. Collect the limits. For each transmitter, obtain guaranteed output-high and output-low levels at the relevant load and supply conditions. For each receiver, obtain its high and low thresholds and permitted input range, including absolute maximum ratings.
  3. Compare both logic states. The minimum guaranteed output high must meet the receiver’s required input high, and the maximum guaranteed output low must meet its input-low requirement. Check the entire possible input voltage against the receiver’s allowable range, including relevant transients. Threshold compatibility alone is not an input-tolerance check.
  4. Decide separately for both paths. If the documented limits are compatible in both directions and the remaining interface requirements are satisfied, a direct signal connection may be considered. If they are incompatible, evaluate a suitable translator. If any required limit is unknown, keep that path unconnected and obtain the missing information rather than guessing.
  5. Review power states. Ask what happens when the transmitter is powered and the receiver is not, and when the supply rails rise or fall in different orders. Check whether the chosen interface and translator explicitly support those states; otherwise resolve the issue before wiring.

A level translator is not a universal remedy. Select one only after the limits on both sides are known. Its input thresholds, output levels and absolute ratings must fit the corresponding devices; its supply range, direction, data-rate capability, loading and power-off behavior must also fit the design. A bidirectional part is not automatically suitable merely because UART has two wires: each UART line normally carries data in one direction. Confirm that the chosen device supports the actual arrangement.

A worked decision without invented limits

Suppose a host board is described as having a nominal 3.3 V UART, and its designer wants to use it with the LRF50H. The module’s 9–36 V DC supply is relevant to the power input, but it does not supply the missing module TX output limits or module RX input limits. The result is hold the signal connection, not “direct connect” and not a recommendation for a specific translator.

With the LR1000E2, the oral 3.3 V logic-level record is useful context for the question to ask, but it is not a complete compatibility calculation. Even if the host also says “3.3 V,” obtain the guaranteed thresholds, output levels and input limits for both sides. A matching nominal label does not establish electrical margin or safe operation across all power states.

Powered-off wiring review

Before energizing either device, prepare a connection record and check it against the delivered hardware. This is a design review, not evidence that the assembly has been tested.

  • Record the exact module, host board, document revisions and intended supply conditions; flag missing or conflicting documentation.
  • Identify the module power input and return separately from every signal pin. Confirm the supply design against the module and power-source specifications.
  • Confirm pin numbering from the correct mating side and viewing direction, then match the actual harness to that definition. Do not infer connections from color alone.
  • Trace module TX to host RX and host TX to module RX; verify each receiving input’s limits before making the connection.
  • Verify the reference-ground arrangement and review any isolation requirements for the installation.
  • Document the behavior of both signal paths when either side is unpowered, including the translator if one is used.
  • Leave reserved or uncertain connections unresolved until the applicable documentation identifies their function and permitted state.
  • Record who supplied each missing limit and the unit or revision it applies to. Recheck the decision if the host, harness or module configuration changes.

Use the UART module integration overview to explore the category, then contact ERDI with the model, host interface, power arrangement and unresolved electrical questions. Ask for limits for both signal directions, not simply whether the module is “TTL.”

FAQ

Is supply voltage the same as UART logic voltage?

No. Supply voltage applies to the power input; UART levels and input limits apply to the data pins. They must be checked separately.

What if the source omits signal levels?

Leave the signal connection open and request the applicable transmitter output levels, receiver thresholds, absolute input limits and power-state behavior for the delivered unit.

When can a level translator be selected?

After both sides’ electrical limits and operating conditions are known. Check each direction, translator power supplies, speed, loading and behavior when either side is unpowered before selecting a part.

Models mentioned in this article