JZNC-YIU02-E Output Transistor Failure: Identifying FR28-Marking

1. Problem Overview

The Motoman YRC1000 robot controller family uses the JZNC-YIU02-E board as an I/O expansion module for European-standard installations. The board provides additional digital input and output channels beyond the controller's onboard I/O. In a typical field failure, one discrete output — for example, a PLC handshake, a gripper solenoid driver, or a status annunciator — suddenly stops responding while the rest of the I/O group continues to function. Inspection finds that one output stage has failed open or shorted, and the surface-mount transistor that drives the load is labelled with the SMD code FR28.

Because the original part number is not printed on the device envelope, the technician is left with three realistic options: identify and substitute the transistor at the board level, replace the entire board, or re-map the failed output to a spare channel through the controller's concurrent I/O and ladder logic. This reference covers all three paths, the electrical context needed to interpret the FR28 code, and the verification steps required to bring the cell back to production.

2. Board Identification and Documentation Trail

The JZNC-YIU02-E is listed in the Motoman product documentation library as an I/O expansion board for European standards, in the PNP (source) signal assignment variant. The relevant documentation entry belongs to the YRC1000 controller family documentation set.

For documentation requests, the official Motoman service and support portal (Motoman Product Documentation) lists the YRC1000 manuals by part number, including the I/O signal assignment table for the JZNC-YIU02-E PNP variant. Cross-referencing the board's catalog number against the documentation portal is the first step before any repair attempt, because the surrounding manuals specify the wiring pinout, ladder tag ranges, and concurrent I/O addresses that you will need for re-mapping if you decide to free up the failed output.

3. Symptoms and Pre-Diagnosis

A typical ticket for this failure includes one or more of the following:

• A single discrete output that never turns on, even though the controller's output monitor shows the corresponding tag in the ON state.
• A single discrete output that is permanently ON and cannot be cleared from the program.
• A PLC or field device reporting loss of a specific input or handshake that lines up with one YRC1000 I/O tag.
• No communication errors, no servo faults, no E-stop — only the indicated output is misbehaving.

Before assuming a failed output transistor, confirm three things:

1. The output tag is being driven correctly from the ladder and concurrent I/O. Use the I/O monitor screen on the YRC1000 teach pendant.
2. The receiving device (PLC, solenoid, relay, indicator) is not at fault. Swap the load, or temporarily re-wire the affected wire to an adjacent spare output.
3. The 24 V user supply to the board is healthy. PNP source outputs pull the load up to the user supply through the output transistor; if the supply is missing or sagging, every output on the affected group will appear dead.

Once those are ruled out, the failure is inside the JZNC-YIU02-E output stage, almost always on the discrete transistor that drives the affected line.

4. Where the FR28 Transistor Sits in the Circuit

The JZNC-YIU02-E PNP source outputs are typically implemented as:

• An optocoupler or galvanic isolation stage on the controller side of the boundary.
• A driver transistor on the field side that sources 24 V DC out to the load.
• A flyback / protection network (typically a TVS diode or Zener clamp plus a freewheeling diode for inductive loads).
• An indicator LED and its series resistor on the field side.

For a PNP (sourcing) board, the output transistor is the device that connects the 24 V user supply rail to the output pin when the controller commands it ON. When the transistor fails it most commonly goes shorted collector-to-emitter (output stuck ON, possibly with the user supply rail pulled down by the shorted output device) or open (output never turns on, with the controller still commanding it from the ladder). The FR28 marking on the package indicates the device is a small-outline SMD active component, most likely in a SOT-23 / SOT-323 / SOT-363 or similar three- or four-terminal package. Without access to the factory BOM for the JZNC-YIU02-E the exact manufacturer part number cannot be named from the marking alone; this is normal for industrial OEM designs where the marking is internal to the supplier.

5. Decoding the FR28 Marking

Surface-mount component marking is a known engineering headache. A four-character alphanumeric code on a small-outline package is rarely the full part number — it is a shortened manufacturer code, sometimes combined with a date or factory code. Some interpretations to evaluate:

5.1 Possible family: small-signal PNP or NPN transistor in SOT-23

The most common interpretation of FR28 on a SOT-23-sized device in an industrial output stage is a small-signal bipolar transistor in the MMBT / BC / 2SA / DTA families, used either as the main output switch (less common at full load) or as a driver in front of a larger pass element. The FR prefix appears in several industry-standard SMD coding schemes, but no single cross-reference is authoritative without removing the part and probing it on a curve tracer.

5.2 Possible family: dual/complementary pair

The board's output section frequently uses matched pair transistors (for example, a pre-driver plus a main switch). A FR28-marked device could be one half of a complementary NPN+PNP pair. If the same marking appears on multiple positions on the board, you have a part that is still available on the other output stages and can be pulled as a known-good donor.

5.3 Verification by signature

The fastest field check:

1. Identify which leads are tied to ground, which to the 24 V rail, and which to the optocoupler output or gate drive.
2. With the board unpowered and isolated from the backplane, use a diode-test multimeter on the suspect device.
3. A healthy small-signal BJT will show 0.5–0.7 V between base and emitter in one direction only, and a higher reading between base and collector. A shorted device will read near zero in both directions; an open device will read open in both directions.

Document which of the two failed states you have — shorted (output stuck ON, possible supply sag) or open (output never turns ON) — because the verification procedure and the re-mapping strategy differ slightly between them.

6. Practical Engineering Decisions

The decision tree is driven by three constraints: how critical the affected output is, how long the line can be down, and whether any spare channels exist on the board.

Most field engineers reach for option 3 first, because the controller's concurrent I/O and ladder logic both support re-mapping with no physical rework. Options 1 and 2 are used when the failed output simply cannot be freed up or the channel is wired in a way that makes it impossible to share with another output.

7. Re-Mapping a Failed Output via Concurrent I/O

Concurrent I/O is the YRC1000 mechanism that lets a user-defined set of internal I/O tags mirror real physical I/O pins on the I/O expansion boards. To free up a failed output, you assign that user tag to a different physical pin on the same board or another board.

7.1 Identify an unused physical output

Choose an output that is not wired in this cell. Common candidates:

• The "battery alarm" output group, which is usually left unwired in cells with a separately-monitored UPS or DC bus.
• A spare output reserved for a cell that was deleted during integration.
• An output on a second JZNC-YIU02-E (or sibling) board in the rack that still has free lines.

7.2 Confirm the spare output is healthy

Move the field wire temporarily to the spare pin, command it ON from the I/O monitor, and verify the connected device responds. If it does, the spare is good.

7.3 Re-assign the concurrent I/O tag

In the YRC1000 maintenance console:

1. Navigate to Setup → Function → Concurrent I/O.
2. Locate the user I/O tag number that drives the failed output (this is the tag your ladder or INFORM program uses; the exact numbering is documented in your release's I/O table — refer to the YRC1000 operator's manual and the PNP signal assignment table for your software revision).
3. Edit the assignment to point at the new physical output.
4. Save and reboot the controller to load the change.

7.4 Move the field wire

Physically move the wire from the failed pin to the spare pin on the CN308-style header.

7.5 Document the change

Update the as-built wiring diagram, the cell schematic, and the I/O assignment table to reflect the new physical pin. This is the step that is most often skipped, and is the cause of every subsequent "mystery dead output" troubleshooting visit.

8. Re-Addressing the Output in a Ladder Program

If the failed output is driven by a ladder program rather than concurrent I/O, the re-mapping workflow is in the Ladder Editor on the YRC1000 maintenance PC.

8.1 Find the coil

Locate the output coil that drives the physical pin. In most YRC1000 ladders, the physical output is referenced by an output relay address such as OUT 20007 (the exact address depends on the slot configuration; consult the I/O assignment table from the Motoman documentation portal).

8.2 Pick a new relay address

Choose an unused output relay on the spare board. The slot assignment defines the address range; the standard 16 outputs per slot give a clean block.

8.3 Edit the ladder

Change the relay operand from the old address to the new one. Save and download the program.

8.4 Verify

From the I/O monitor, force the new output relay ON and confirm the field device responds. Then run the cell in manual at low speed to confirm the original sequence still works correctly.

9. Component-Level Repair Procedure

If you have decided to attempt the transistor replacement, follow this sequence.

9.1 Prerequisites

• A copy of the JZNC-YIU02-E board schematic or at least an understanding of the PNP source output topology from the Motoman documentation library.
• A hot-air rework station or fine-tip soldering iron suitable for SOT-23 class packages.
• Anti-static precautions.
• A donor device: pull a known-good equivalent from an unused output position on the same board or a retired board of the same catalog number. This is far safer than guessing at a substitute from a generic SMD code book.

9.2 Substitution logic

If you cannot obtain a verified donor, the next step is to characterize the failed device:

• Package style (number of pads, pinout).
• BJT vs MOSFET.
• PNP vs NPN polarity.
• Approximate current and voltage rating when ON (estimate from the load the output was driving).
• Voltage rating when OFF (estimate from the user supply rail, typically 24 V DC).

Match an equivalent from a major-line SMD catalog that meets or exceeds all of the above. As a rule of thumb:

9.3 Removal

Apply flux, heat all three pads of the failed device evenly with hot air, and lift it with tweezers. Clean the pads with wick and isopropyl. Inspect for lifted pads — multilayer boards can lose inner connections if the rework is too aggressive.

9.4 Placement and reflow

Place the donor or substitute, align the leads to the pads, and reflow with hot air or a fine-tip iron. Confirm orientation (pin 1, base/gate, collector/drain, emitter/source) against the pad pattern before applying heat.

9.5 Post-repair inspection

• Visual inspection under 10× magnification for solder bridges, insufficient solder, tombstoning.
• Continuity check from the user supply rail to the output pin (should be open with the controller output OFF; should pull up to ~24 V when commanded ON, with the load connected).
• Verify the LED indicator on the affected output (if present) responds to commands.

10. Board Replacement Procedure

When a spare JZNC-YIU02-E is available, board replacement is straightforward but the re-addressing must be planned.

1. Power down the controller and lock out the cell.
2. Label and photograph every wire on CN308 and any other I/O connectors on the board.
3. Remove the board and install the spare.
4. Reconnect the wiring exactly as documented in the cell schematic.
5. Apply power and verify the I/O monitor shows every input and output in its expected state.
6. Run a manual jog of the cell to confirm operation before releasing the line.

If the spare board has a different I/O assignment default, you may need to reload the configuration. Always store a backup of the controller's job files and I/O configuration before swapping a board.

11. Verification and Commissioning

After any of the three repair paths, the same verification set applies.

11.1 Static verification

• For every input on the board: force the field device ON and OFF, confirm the I/O monitor tracks correctly.
• For every output on the board: command the output from the monitor or ladder, confirm the field device responds.

11.2 Dynamic verification

• Run the cell in manual mode at reduced override (typically 10 percent) and exercise the full sequence that uses the affected output.
• Run a single automatic cycle with a safety observer present.
• Run a full automatic cycle and confirm the cell returns to its home state cleanly.

11.3 Documentation closeout

• Update the wiring diagram with any re-mapping performed in step 7 or 8.
• Update the I/O assignment table for the cell.
• File a deviation report if the FR28-marked device was substituted with a non-OEM part; this is important for any future warranty support.

12. Common Pitfalls

12.1 Re-mapping without updating documentation

This is the single most common cause of "the I/O is wrong again" tickets after a repair. If the re-mapping is not reflected in the cell documentation, the next technician who services the cell will spend hours re-tracing the wiring.

12.2 Confusing a shorted output with a PLC failure

A shorted PNP source output can pull the user supply rail down, which may cause other outputs on the same board to misbehave or the PLC to see what looks like a noisy input. Always verify the supply rail before chasing phantom PLC problems.

12.3 Assuming the FR28 code is universal

There is no single manufacturer-mark cross-reference table that is authoritative for industrial OEM SMD codes. The same FR28 marking can refer to different devices in different product lines. Verify by signature, not by code alone.

12.4 Disturbing warranty coverage

If the cell is under warranty, board-level repair may void coverage. Confirm the warranty status with the local Yaskawa/Motoman service channel before substituting components.

13. Frequently Asked Questions