FPGA DEVICES · ENGINEERING · SOURCING Source-linked information. Clear project requirements.

Hard-to-find

QS3VH244QG EOL Sourcing: Check the Carrier, Enable Groups and Control Margin

Published · Updated

QS3VH244QG sourcing decision: establish whether the offered code, carrier and board requirement still describe the same purchase. Renesas PLC230018 explicitly names this order code. This dossier gives a buyer and an engineer a shared worksheet for a legacy board using a bidirectional bus switch, with a separate record for each enable group. It does not establish stock, price, lead time, authenticity or a qualified replacement.

Bring the released BOM line, board revision, supplier's complete proposed order code, carrier description and the circuit surrounding both enables. The useful output is a documented route: request the exact code, investigate a carrier proposal, or open a controlled board-change review. Keep those routes visible in the purchasing record so an unresolved electrical question cannot disappear inside a shortened supplier description.

Read the official QS3VH244 datasheet · Request QS3VH244QG, quantity 25

1. Establish the exact historical EOL record

Exact-code lifecycle recordThree dated notice events lead to a separate present-day offer review. The row names QS3VH244QG and gives no replacement. Follow the exact row 03 Jan 2024Notice issued 03 Jul 2024Last time buy 03 Jan 2025Last shipment QS3VH244QGReplacement field: NonePresent supply: unverifiedPLC230018, pages 1 and 37
Original timeline of the exact affected row. Historical deadlines do not establish present availability.

The source is Renesas PLC230018, issued 3 January 2024. PDF page 37 lists QS3VH244QG with last time buy 3 July 2024 (2024-07-03), last shipment 3 January 2025 (2025-01-03), and replacement field None. Its table heading limits the affected list to exact part numbers; other variations are not automatically included. The cover describes NCNR shipments between the deadlines and reserves order acceptance or cancellation when fulfillment is not commercially reasonable. Official notice, pages 1 and 37.

These dates answer a historical purchasing question: which manufacturer's withdrawal schedule applied to the named code? They do not answer whether a particular offer is deliverable today. In a present enquiry, preserve the notice identifier and the exact row alongside the supplier's proposed lot. Ask the supplier to state the offered quantity, carrier, lot identification, source route, traceability documents and any handling conditions. Request separate answers for each proposed lot rather than accepting one description for mixed material.

The word None is a boundary on this notice, not proof that no engineering alternative can ever exist. A buyer can accurately write that the notice names no replacement for this row. Choosing another switch requires a new comparison against the actual circuit. Conversely, the existence of another order code in an active family would not erase this exact-code withdrawal. Record lifecycle evidence at order-code level and avoid turning a family name into a purchase authorization.

For another affected line in the same BOM, use the hard-to-find component evidence directory to locate that line's own notice context. Do not transfer this row's dates to an unlisted switch. If a supplier refers to a later change or authorized continuation, retain the new primary record separately and reconcile its scope before changing the conclusion.

2. Resolve the package and carrier before comparing offers

Order code and carrier are separate fieldsThe code separates QS3VH244, QG package and a blank carrier suffix. A tube and reel are conceptual carrier drawings; PAG is a different package code. Read all code fieldsQS3VH244 | QG | blank DevicePackageCarrier Blank: tube or tray 8: tape and reelQG = QSOP; PAG = TSSOPConcept only. Not a package drawing.
Original order-field and carrier concept. Carrier drawings are illustrative, not photographs or handling specifications.

The May 2013 datasheet, DSC-5894/14, page 8 defines QG as QSOP - Green, PAG as TSSOP - Green, blank final carrier option as tube or tray, and 8 as tape and reel. The exact Renesas QS3VH244QG page identifies a 20-lead QSOP, PCG20, 0.64 mm pitch, tube carrier and marks this code obsolete at the recorded retrieval. Official exact-order-code package and status record.

This produces three useful comparisons. An offer written QS3VH244QG can be checked against the requested identity, while still requiring evidence about the physical lot. An offer written QS3VH244QG8 changes the carrier field and must be recorded as a proposal, with purchasing and assembly handling reviewed. An offer using PAG changes the package field and belongs in a package and board review. The shared device stem alone is insufficient to collapse those three descriptions into one BOM line.

Do not remove a suffix because a seller calls it packaging only. Carrier matters to incoming inspection, storage, feeder preparation, quantities supplied per carrier and the assembly house's process. Ask whether the proposed material is in its original carrier, has been repacked, or is being supplied as cut material. The answer does not establish authenticity, but it changes which label, lot and handling records are needed to evaluate the offer.

Use the following identity worksheet as a literal transcription exercise. Keep uncertainty visible; a blank field means unknown rather than an assumed match.

QS3VH244QG offer identity worksheet
RecordRequired entryReview output
Released demandQS3VH244QG; board and BOM revision; required quantityExact requested code retained
Supplier proposalComplete order code copied from written offerEvery literal difference recorded
Package evidenceManufacturer package code and controlled drawing revisionQG/PAG difference routed to board review
Carrier evidenceTube, tray or tape/reel; original or repacked; lot labelsHandling questions assigned before purchase
Unresolved factsMissing evidence and the next requested documentNo silent acceptance of an assumption

The complete-device-code lesson helps preserve the distinction between a purchase code and device marking. The Full MPN catalogue check can be run with QS3VH244QG as the input, but its output concerns the reviewed published catalogue. A missing catalogue match does not mean the manufacturer code is invalid; a match does not verify an offered lot. Save that output as a navigation aid, then return to the primary ordering record above.

Watch the shared complete-order-code comparison conceptShared original animation showing a complete-order-code transcription comparison with generic example codes, not QS3VH244QG electrical specifications or switch timing

This shared original animation uses example order codes to explain the comparison method. Its examples are not QS3VH244QG specifications, a switch-timing simulation or a physical inspection. Expand this section to view the concept.

Static transcript for this sourcing task: preserve the requested QS3VH244QG and the complete offered code as two separate strings. If the offer is QS3VH244QG8, record the added terminal 8 and consult the carrier definition on datasheet page 8. If an offer changes the QG package field to PAG, record that package-field change separately and consult the manufacturer's package definition. Keep the quotation, label and source definition together. A text difference identifies the next evidence question; matching text does not establish lot authenticity or board compatibility.

3. Map the two isolation groups onto the actual board

Two groups require two control recordsEight bidirectional channels form two four-channel groups. Each group has a separate enable. Diagram uses conceptual open switches and is not a pinout.Map both enable groupsGroup 1 / control 1GGroup 2 / control 2GA1Y1A2Y2A3Y3A4Y4A1Y1A2Y2A3Y3A4Y4xG HIGH: disconnectedxG LOW: joined, either directionConcept topology. Not a pinout.
Original topology map based on the datasheet function table. It is not a pinout, footprint or tested circuit.

The device contains eight bidirectional switch paths in two four-path groups. Each group has its own xG control: HIGH disconnects; LOW connects its A and Y terminals. The datasheet specifies operation at 2.3-3.6 V and -40 to +85 °C. Its pin configuration is on page 2. Use that primary drawing when assigning real pin numbers; the conceptual diagram here deliberately shows connectivity rather than physical placement.

Start with the board nets, not a generic eight-bit bus label. For each path, name both endpoints and state which endpoint can drive in each operating mode. Include reset, programming, normal transfer, standby, partial power and a disconnected external cable if those states exist in the product. A bus path that appears input-only during normal operation may be driven from the other side during factory test or recovery. Missing that mode can make an apparently sensible substitute unsafe for the circuit.

Next, create one control record for 1G and another for 2G. Record the controlling device, its rail, the active level, pull resistors, reset behavior and behavior while either supply is absent. Explain the intended default state in words. If the schematic ties the two controls together, preserve that fact rather than treating it as evidence that the two groups have identical load or timing requirements. Electrical symmetry in the switch does not prove symmetry in board routing or firmware ownership.

For each mode, the worksheet should output four decisions: who is permitted to drive, which group is connected, what receiver voltage range is required, and which event ends that permission. This is more useful than a single compatible checkbox. It exposes cases where a replacement would need a changed enable polarity, additional control logic, altered pull values or different initialization sequencing. Such changes can be evaluated, but they belong in a documented board change.

  1. Write the board revision and list all eight net pairs using the real schematic names.
  2. Assign each net pair to group 1 or group 2 from the manufacturer's pin configuration.
  3. For every power and operating mode, name the driver at each endpoint or explicitly mark it undriven.
  4. Record both enable levels and the source that guarantees them during that mode.
  5. Flag simultaneous drivers, unknown enable levels and unpowered endpoints for further circuit review.

A package count or a shared 244 name cannot resolve these entries. Retain the completed mode table with any alternate proposal so the comparison starts from the actual intended function. This worksheet is a planning method; no waveform, simulation or powered-board result is claimed.

4. Separate control-level margin from bus timing

A control level can fail before timing is reviewedA hypothetical controller high output of 1.62 volts is below the required 2.0 volt HIGH threshold at the specified upper supply range. The negative margin blocks this concept. Check control HIGH marginHypothetical controller output2.00 V required HIGH1.62 V assumed output0 V1.62 - 2.00 = -0.38 VNegative HIGH margin: stop.Use actual controller guarantees.Concept calculation. No hardware test.
Original hypothetical control-margin calculation. The controller output is an assumption, not a measured or product-specific value.

At VCC = 2.7-3.6 V, the datasheet's page 3 control limits are VIH minimum 2.0 V and VIL maximum 0.8 V. At VCC = 2.3-2.7 V, they are 1.7 V and 0.7 V. These control-input requirements must be checked against the source device's guaranteed outputs under the actual load and operating corners.

Consider an explicitly hypothetical board with a 3.3 V switch supply and a controller whose guaranteed HIGH output is assumed to be only 1.62 V. HIGH margin is controller VOH minimum minus switch VIH minimum: 1.62 - 2.00 = -0.38 V. The negative result blocks this control connection as described. Calling the source a 1.8 V GPIO is not a substitute for its guaranteed output specification. The designer must obtain the controller's actual limits and decide whether a different rail, permitted control source or a level-conversion circuit is needed.

For a second assumed value, controller VOL maximum of 0.20 V gives LOW margin of 0.80 - 0.20 = 0.60 V. A positive LOW calculation does not cancel a failing HIGH calculation. Keep both results, their assumed current and temperature conditions, and the supply tolerances in the same record. This small exercise prevents a data-path voltage feature from being mistaken for universal control compatibility.

Timing is a separate gate. At 3.3 ± 0.3 V, page 5 gives maximum turn-on 7.5 ns and turn-off 7 ns, with its test conditions on page 7. The data-path RC delay discussion is not an enable handover guarantee. Evaluate the interval between one endpoint ceasing to drive and another gaining permission to drive; include controller skew, clock relationships, interconnect and receiver requirements. Use the data sheet's conditions rather than treating the smallest published delay as the whole system budget.

For a conceptual budget only, suppose a reviewer allocates 7 ns for switch disconnection, 2 ns for control skew, 3 ns for an independently established scheduling uncertainty and 4 ns of project reserve. The sum is 16 ns. This is an arithmetic example, not a recommended dead time: the assumed terms may overlap, omit a driver-release delay, or be inappropriate for the actual topology. The useful output is a list of budget terms that can be replaced by evidence, with double-counting and missing terms explicitly reviewed.

The trace propagation estimate can help keep the interconnect term separate. As a declared example, enter 60 mm and 150 mm/ns to obtain 0.4 ns one-way propagation. Those numbers are assumptions, not measurements of this board or a property of the switch. Use a stackup-appropriate velocity, and retain the tool's exclusions for vias, discontinuities and driver/receiver timing. A scalar trace estimate cannot resolve the control margin or establish signal integrity.

5. Turn the worksheet into a reviewable purchase or board-change request

Declare five deliverables before board reviewFour declared present deliverables and one unconfirmed test plan create one unresolved item. This is a file-presence checklist, not a review of file contents. Make the handoff reviewableFabrication / drill: presentBOM: presentPlacement: presentAssembly: presentTest plan: not confirmed1 unresolved deliverableDeclared presence. Contents not checked.
Original file-presence example for a QS3VH244QG board review. One unknown remains unresolved.

Keep the sourcing route specific. For the released design, request QS3VH244QG with the required quantity and evidence conditions. If a different carrier is proposed, retain both the original demand and the proposal, and ask the assembly team what handling information it needs. If a different package or switch function is proposed, attach the mode map and margin worksheet to a board-change request. Preserve the unresolved items instead of rewriting the demand to resemble whatever is offered.

Use the existing Manufacturing file package check to organize a wider board review. In its Board and revision field, enter Legacy IO Rev C - QS3VH244QG review. In Declared file names, enter a real file list from that revision; for this example use RevC-fabrication.zip, RevC-bom.csv, RevC-placement.csv and RevC-assembly.pdf. The tool accepts declarations and names rather than uploading or inspecting the file contents.

For the worked example, select Declared present for fabrication/drill, BOM, placement and assembly, and Not confirmed for programming/test. Run the check. The expected output is one unresolved deliverable, the test plan. Review the individual lines, save the text report if useful, and pair it with the switch-specific worksheet. File presence alone cannot show that the enable groups, footprint, carrier handling or operating margins were reviewed. Keep the official drawing revision and the schematic mode table alongside the file list.

If the tool is unavailable, use this static fallback. Write the board revision; list the actual file names; give each of the five deliverables a present, missing or not-confirmed state; count every missing or not-confirmed entry once. Then add the following switch-specific questions: are QG package and carrier requirements preserved, are both control groups mapped, are HIGH and LOW margins supported, is the driver handover interval supported, and are partial-power states documented? The five-file count and these circuit questions answer different tasks and should remain separate.

For an offered legacy lot, the date-code and traceability evidence guide helps organize original labels, source documents and storage-history questions. Use it to define the evidence request; the guide does not authenticate this part. Keep material from different lots separate throughout the review, and ask for clarification when the paperwork, carrier description and proposed order code disagree.

Further evaluation is useful when the exact demand is preserved, the actual circuit is available and the reviewer can replace assumptions with controlled evidence. Resolve an unidentified package, an unexplained carrier change, a negative control margin or competing drivers before treating the proposal as suitable. Current stock, price, lead time, lot authenticity, physical inspection, simulation and board qualification remain unverified by this dossier.

Next action: prepare a homepage enquiry for QS3VH244QG, quantity 25. Review and change the quantity to your actual positive whole-number requirement before sending. Include requested delivery, destination, permitted carrier and traceability needs in the form; keep confidential board files out of the URL. For a board change, describe the scope and available revision-controlled files in the same enquiry. No form is submitted by this article.

Prepared with AI assistance and revised 10 November 2026. Manufacturer evidence was checked at the stated pages and exact order-code scope. Original diagrams and numerical examples are concepts. This preparation is not human engineering certification, device testing, a compatibility approval or a live supply check.

Back to Hard-to-find →

Source addresses and citation trail

Full source addresses are retained below. Read each citation with its document revision, page, table and applicability conditions above.

  1. https://www.renesas.com/en/document/dst/qs3vh244-datasheet
  2. https://www.renesas.com/en/document/eln/plc-230018-end-life-process-select-parts?r=13431
  3. https://www.renesas.com/en/products/qs3vh244/part-details/qs3vh244qg