1. Identify the Actual Transceiver Variant

Start with the actual item being offered: a loose transceiver IC, a module or a populated board. Keep the component manufacturer code separate from the assembly reference. A warehouse label reading CAN board may describe the larger deliverable without identifying the transceiver variant that a component reviewer would need.

Preserve the full supported code and observed marking together with original packing or purchase references. An internal programme number and a semiconductor ordering code have different roles. If a suffix is missing, retain the incomplete reading rather than filling it from another board that used a familiar member of the same family.

Keep a controller's configuration or firmware reference outside the transceiver identity field. Such records may describe the previous system, but they should not supply a hardware feature description for an unidentified physical-layer device. The existing programmed-MCU guide addresses programming state; this enquiry concerns the product capability documented for the transceiver itself.

Where a module contains several unidentified devices, state the identification level reached. Do not promise loose transceiver stock when only complete modules are available for release. The recipient should be able to distinguish a supported component variant from a board description whose internal product evidence remains incomplete.

2. Preserve the Manufacturer's Mode-Capability Description

TI's TCAN1042H page describes its family as having a low-power standby mode with a remote-wake-request feature. TI's TCAN1051H page describes its family as providing silent mode, also commonly called listen-only mode. Keep these statements with their named source context rather than reducing both examples to an unexplained low-power or inactive-mode field.

For the actual offered code, retain the mode wording supported by the applicable manufacturer reference. The examples show different documentation questions, not a decoding rule for every CAN transceiver. Do not assign standby, wake or silent capability to another family simply because its short description also contains CAN.

Keep capability separate from operating state. A product description can explain a documented feature, while saying nothing about the mode currently selected in a loose surplus unit or an old board. An inventory row should not describe a device as presently listening, asleep or waking solely because those words appear in its catalogue.

If owner records use silent and standby interchangeably, preserve the original annotation and seek the exact product reference needed to clarify it. Do not resolve the ambiguity from a control-terminal photograph or a recollection of software settings. This article supplies no truth-table interpretation, control level, wake timing or network operating instruction.

3. Keep Interface Options and Reports Separate

Retain other variant information only where the exact code's documentation supports it. A broad family reference should not complete every interface-option field in a seller's list. If the available record is an overview rather than an exact variant document, state that limitation and identify the missing suffix or reference as a separate question.

Distinguish semiconductor capability from module-level claims. A board's connector, supply annotation or software label does not independently establish all of the loose transceiver's features. Likewise, a named transceiver example does not establish the operating configuration of every assembled board that resembles an evaluation product.

If the stock has an existing report, record its identified units, date and declared test scope separately from the manufacturer's feature description. A former installation shows a history reference, not a fresh result for standby, remote wake or silent behaviour. Keep sample coverage and unresolved connections to the offered material explicit.

This guide does not reproduce voltage, bitrate or timing figures from the product pages and does not borrow unread truth-table details from linked datasheets. It performs no CAN traffic, wake or standby test. Missing operating evidence should remain missing rather than being replaced with a family feature or an old equipment statement.

4. Offer Capability-Identified Groups Without Network Promises

Organise supported stock by exact identity and retain the referenced mode-capability descriptions beside that identity. Keep unknown variants distinguishable from identified groups. A combined heading such as silent standby parts can obscure the very feature difference the reviewer needs, even when all the items came from equipment associated with CAN.

Within each supported group, retain physical condition and source-history differences. Identify which component or module the owner has authorised for release and which non-sensitive records may be shared. For unresolved items, name the missing code, variant reference or report coverage rather than declaring the whole group compatible with another network.

For an ICULTRA CAN-stock enquiry, provide complete supported identifiers, the actual sale-item quantities and the applicable standby/wake or silent/listen-only references. Request review of that disclosed material. Mode classification does not establish present network behaviour, engineering compatibility, purchase eligibility or a commercial offer; those matters require further evidence and agreement for the particular scope.

Sources and further reading

TI's TCAN1042H and TCAN1051H product descriptions support the family-specific mode examples. No mode truth table, control level, timing, bitrate or current network test is inferred from these overview pages.