Creating PCB from Diagram

Yes — I can work from this image, but not as a one-click PCB conversion.
From the diagram, I can already tell it is a 3-channel interface board between a Beckhoff PLC and an XRD 4343 / XRD-FGe Opto LVDS interface, with:
  • CH1: PLC output to LVDS trigger
  • CH2: LVDS frame enable back to PLC input
  • CH3: LVDS frame sync back to PLC input
  • a DB9 interface
  • selectable 5 V / 24 V input conditioning
  • isolation, LVDS drivers/receivers, protection, and power blocks
The attachment workflow for schematic images says the right approach is to:
  • identify the topology
  • read visible labels/values
  • connect the findings to your current project
  • then offer to recreate the circuit in Flux rather than pretend the image can be imported directly
So the practical answer is:

Table


What I can do from this imageWhat I cannot do directly
Recreate the schematic in Flux based on the blocks and labels shownAuto-import this image as a finished PCB
Help choose actual parts for the isolators, LVDS transceivers, connectors, protection, and power stageInfer exact component part numbers if they are not specified in the diagram
Build the PCB after the schematic is capturedGuarantee correctness of hidden details not shown in the image
The main missing piece is that this image is a block/functional diagram, not a full electrical schematic. It shows functions like “high-speed optocoupler / digital isolator,” “LVDS driver DS90LV011A or SN65LVDS31,” “LVDS receiver SN65LVDS32 or DS90LV032,” “100 Ω differential termination,” polarity select, fuse/polyfuse, TVS/ESD, and optional isolated DC/DC + LDO, but it does not show the exact pin-level wiring for every device or the full power implementation
If you want, I can recreate this board in your current Flux project. The next step would be for me to build a plan for:
  • the connectors and I/O mapping
  • channel-by-channel schematic capture
  • power/protection section
  • then PCB layout
Before I do that, I need one clarification:
Do you want me to build
  1. a functional equivalent of this interface board from the diagram, or
  2. a close reproduction using the exact device families named in the image, like DS90LV011A, SN65LVDS31, SN65LVDS32, and DS90LV032?
build a functional equivalent of this interface board from the diagram
I've made a plan, and started work on it.

Started implementing a plan

# Goal

- Design and implement a functional equivalent of the Beckhoff PLC to XRD 4343 / XRD-FGe Opto LVDS interface board. The board will provide one PLC output to an LVDS trigger channel, two LVDS-to-PLC return status channels, a DB9 field interface, and selectable 5 V or 24 V trigger input conditioning with built-in isolation, protection, and basic power handling. The design will be developed in Flux following schematic capture and PCB layout implementation.

# Implementation plan

1. **Schematic Design and Functional Block Capture**

1. Capture the functional requirements and signal mapping from the reference interface including:

- PLC output to LVDS trigger channel

- Two LVDS-to-PLC status channels

- DB9 interface for field connections

- Selectable 5 V / 24 V trigger input conditioning

- Isolation and protection mechanisms

2. Define power handling and conditioning blocks, ensuring selectability and proper isolation across domains.

2. **Component Selection and Schematic Build**

1. Select and add components to implement the three channels:

- Add a PLC output driver circuit interfaced to an LVDS trigger driver circuit

- Add LVDS receiver circuits for the two return channels routed to PLC inputs

2. Add a DB9 connector and connect it to the field interface circuits correctly.

3. Integrate a selector (or circuitry) to choose between 5 V and 24 V trigger input, and add isolation, protection components (e.g., TVS diodes, optocouplers) in both trigger and return paths.

3. **Schematic Verification and Footprint Assignment**

1. Review the schematic to ensure all functional blocks and signal connections are properly captured.

2. Assign PCB-ready parts and configure footprints for critical components.

4. **PCB Layout Preparation**

1. Define board outline and layout constraints.

2. Group components by functional blocks (trigger channels, status channels, power conditioning, and DB9 interface) and place them accordingly on the board.

3. Configure layout design rules including isolation clearances and trace width for signal integrity.

5. **Layout Finalization and Review**

1. Route all nets using automatic and manual methods where necessary, ensuring proper connections between blocks.

2. Perform layout and manufacturability review to confirm that all components are properly placed and all wiring is correct.

# Success criteria

- The schematic accurately captures the required channels and interfaces including PLC to LVDS trigger, two LVDS-to-PLC status channels, DB9 field interface, selectable trigger input conditioning, isolation, protection, and power handling.

- Components are selected, placed, and assigned PCB footprints, and the board layout meets functional, isolation, and manufacturability requirements.

- The project is ready for further detailed verification and production-level testing.

Working on your request...

17:50

Continue
I've made a plan, and started work on it.
Add USB-C details
Run schematic checks
Pick USB footprint

Started implementing a plan

# Goal

- Implement a functional equivalent of the Beckhoff PLC to XRD 4343 / XRD-FGe Opto LVDS interface board. This design will include one PLC-output-to-LVDS trigger channel, two LVDS-to-PLC status return channels, a DB9 field interface, selectable 5 V or 24 V trigger input conditioning, isolation, protection, and basic 24 V power handling, all based on the uploaded reference diagram.

# Implementation plan

1. Schematic Capture

1. Capture the overall interface architecture including the three channels and DB9 field connector mapping.

2. Add a selectable input conditioning block for 5 V or 24 V triggers, ensuring proper switching, isolation, and conditioning based on reference design.

3. Incorporate isolation and protection circuits (e.g., opto-isolators, TVS diodes) for both trigger and status lines, as well as for the power input.

4. Define power handling and regulation circuitry for the 24 V supply.

2. Component Selection and Placement

1. Select and add suitable LVDS transceivers and isolation components from the Flux parts library.

2. Add necessary passive components (resistors, capacitors) and protection elements into the schematic.

3. Map the DB9 connector signals to the appropriate channels in the design.

3. Schematic Wiring and Connectivity

1. Connect the PLC-output-to-LVDS trigger channel with its dedicated conditioning, isolation, and protection circuitry.

2. Connect two LVDS-to-PLC status return channels to their respective protection circuits, ensuring correct signal routing back to the PLC.

3. Wire the DB9 field interface to correctly interface with external hardware, replicating signal paths from the reference design.

4. PCB Setup and Layout

1. Assign footprints to all selected components and define the board outline with constraints matching project requirements.

2. Place components by functional block: one for the trigger channel, one for the status channels, and one for the DB9 connector and power conditioning.

3. Use auto-placement and auto-routing tools to route nets, ensuring proper clearance and manufacturability.

5. Verification and Review

1. Review the schematic to ensure all signal paths, isolation, and protection measures are consistent with the reference board behavior.

2. Verify PCB layout for routing completeness, manufacturability, and adherence to design rules and isolation requirements.

# Success criteria

- A complete and functional schematic capturing all required channels, DB9 mapping, and selectable input conditioning is created.

- Essential components for LVDS conversion, isolation, and protection are selected and correctly placed.

- PCB layout with correct footprints, board outline, and routed nets is generated and verified for manufacturability.

- The design functions as a functional equivalent of the reference Beckhoff PLC interface board.

Working on your request...

16:44:59

Q1 C - R8 P2
JP3 1 - R1 P1
J2 3 - JP3 2
U2 RO2 - R10 P1
Q3 C - J2 5
IC1 OUT- - U5 I/O 6
PS1 -VOUT - C5 P2
J2 2 - D2 A
R14 P2 - Q3 B
PS1 -VOUT - C5 P2
J2 2 - D2 A
J1 1 - U5 I/O 1
JP3 3 - R5 P1
PS1 +VOUT - C5 P1
R7 P2 - Q1 B
PS1 -VOUT - C5 P2
U1 VO - C8 P1
IC2 VO1 - R6 P2
U1 VO - C8 P1
U4 COL - R14 P1
U2 RO1 - R9 P1
PS1 -VOUT - C5 P2
J1 1 - U5 I/O 1
R1 P2 - R5 P2
J1 2 - U5 I/O 3
J1 6 - U5 I/O 2
U4 COL - R14 P1
R7 P2 - Q1 B
R14 P2 - Q3 B
D1 CATHODE - D2 K
PS1 +VOUT - C5 P1
D1 CATHODE - D2 K
J1 1 - U5 I/O 1
JP2 2 - IC1 IN
J1 2 - U5 I/O 3
IC1 OUT- - U5 I/O 6
PS1 -VOUT - C5 P2
R14 P2 - Q3 B
IC1 OUT+ - U5 I/O 5
PS1 +VOUT - C5 P1
PS1 -VOUT - C5 P2
IC1 OUT+ - U5 I/O 5
U2 RO2 - R10 P1
PS1 +VOUT - C5 P1
IC1 OUT- - U5 I/O 6
J1 6 - U5 I/O 2
J1 7 - U5 I/O 4
J2 2 - D2 A
D1 CATHODE - D2 K
J2 3 - JP3 2
J1 SHIELD__1 - U3 CAT
IC2 VO1 - R6 P2
J1 6 - U5 I/O 2
IC1 OUT- - U5 I/O 6
D1 CATHODE - D2 K
J2 2 - D2 A
R1 P2 - R5 P2
F1 ~ - D1 ANODE
Q1 C - R8 P2
R9 P2 - U3 AN
U3 COL - R13 P1
IC1 OUT+ - U5 I/O 5
J1 2 - U5 I/O 3
PS1 +VOUT - C5 P1
U1 VO - C8 P1
Q3 C - J2 5
PS1 -VOUT - C5 P2
D1 CATHODE - D2 K
PS1 -VOUT - C5 P2
JP3 3 - R5 P1
PS1 +VOUT - C5 P1
PS1 +VOUT - C5 P1
PS1 +VOUT - C5 P1
J1 SHIELD__1 - U3 CAT
J2 2 - D2 A
R1 P2 - R5 P2
IC2 VO1 - R6 P2
J1 SHIELD__1 - U3 CAT
J2 2 - D2 A
PS1 +VOUT - C5 P1
J1 6 - U5 I/O 2
R10 P2 - U4 AN
D1 CATHODE - D2 K
J1 SHIELD__1 - U3 CAT
J2 1 - F1 ~
D1 CATHODE - D2 K
PS1 +VOUT - C5 P1
J2 2 - D2 A
PS1 +VOUT - C5 P1
U1 VO - C8 P1
Q1 C - R8 P2
PS1 -VOUT - C5 P2
J1 2 - U5 I/O 3
J2 2 - D2 A
J1 7 - U5 I/O 4
D1 CATHODE - D2 K
PS1 -VOUT - C5 P2
PS1 -VOUT - C5 P2
Q2 C - J2 4
J1 7 - U5 I/O 4
J1 7 - U5 I/O 4
R13 P2 - Q2 B
J2 1 - F1 ~
R13 P2 - Q2 B
PS1 +VOUT - C5 P1
IC1 OUT+ - U5 I/O 5
J1 1 - U5 I/O 1
R9 P2 - U3 AN
IC2 VO1 - R6 P2
U3 COL - R13 P1
R10 P2 - U4 AN
JP2 2 - IC1 IN
JP3 1 - R1 P1
PS1 -VOUT - C5 P2
Q2 C - J2 4
F1 ~ - D1 ANODE
J1 SHIELD__1 - U3 CAT
D1 CATHODE - D2 K
U2 RO1 - R9 P1
R13 P2 - Q2 B
PS1 -VOUT - C5 P2
C11
Capacitance
100nF
C8
Capacitance
1uF
U1
Q1
J2
R3
Resistance
100R Ω
C5
Capacitance
10uF
C9
Capacitance
100nF
R13
Resistance
4.7kΩ
R11
Resistance
10kΩ
R8
Resistance
10kΩ
R1
Resistance
820R Ω
R10
Resistance
330R Ω
C6
Capacitance
100nF
R9
Resistance
330R Ω
R12
Resistance
10kΩ
R5
Resistance
4.7kΩ
R2
Resistance
100R Ω
C7
Capacitance
1uF
C4
Capacitance
100nF
C3
Capacitance
10uF
C10
Capacitance
100nF
R6
Resistance
10kΩ
R7
Resistance
10kΩ
R4
Resistance
100R Ω
R14
Resistance
4.7kΩ
IC2
D2
JP3
JP2
IC1
D1
U4
U5
PS1
F1
J1
Q2
U3
Q3
U2

Refine this doc
Ask about this doc
PLC-to-LVDS Isolated Interface Board — High-Level Implementation Plan
Objective
Create a functional equivalent of the attached 3-channel isolated PLC-to-LVDS interface board in this Flux project, focused on capturing requirements and defining the system architecture before detailed part selection.
Current Project Status
  • Current schematic contents: empty
  • This plan should be used as the requirements baseline for schematic capture, interface definition, and later component selection.
Scope
The design should implement these functional blocks:
  • One PLC output to LVDS trigger path
  • Two LVDS-to-PLC return status paths
  • DB9 field interface
  • Selectable 5V / 24V trigger input conditioning
  • Isolation between field-side PLC domain and low-voltage logic/LVDS domain
  • Protection for field wiring and logic-side interfaces
  • Basic power handling for field-side and logic-side operation
High-Level Requirements Capture Plan
1. Establish Functional Equivalence Targets
Capture what “functional equivalent” means for the reference board:
  • Identify all external connectors and user-accessible signals
  • Identify which signals are inputs vs outputs
  • Confirm the three channel roles:
    • Channel 1: PLC output to LVDS trigger
    • Channel 2: LVDS status return to PLC
    • Channel 3: LVDS status return to PLC
  • Define whether equivalence means electrical behavior only, or also connector pinout, indicator behavior, configuration options, and power behavior
  • Record any required compatibility constraints with the existing PLC and LVDS equipment
2. Define External Interface Requirements
Capture interface-level requirements before choosing devices.
PLC / Field-side interface
  • PLC voltage environments to support
  • Trigger signal type: sourcing, sinking, or configurable
  • Expected logic thresholds for 5V mode and 24V mode
  • Input current budget presented to the PLC output
  • Return output style for status channels: open collector, push-pull, relay-like equivalent, or other PLC-compatible signaling
  • Cable length expectations and industrial noise environment
  • Required behavior during unplugged, fault, or power-off conditions
LVDS / Logic-side interface
  • LVDS source/destination roles for each channel
  • Connector or board-level interface for LVDS signals
  • Required polarity, idle state, and fail-safe behavior
  • Timing expectations: edge rate, pulse width, latency, and skew tolerance
  • Whether status paths are static state signals or pulse/event signals
  • Required common-mode and ground-reference assumptions on the low-voltage side
DB9 field connector
  • Define exact DB9 pin assignment for:
    • field power
    • field return
    • PLC trigger path
    • two PLC status return paths
    • optional shield or chassis connection
  • Capture mating-cable expectations and whether the pinout must match the attached board exactly
  • Decide whether DB9 shell should connect to chassis, protective earth, field ground, or remain isolated
3. Partition the System into Electrical Domains
Define clear domain boundaries:
  • Field / PLC domain
  • Isolated boundary
  • Low-voltage LVDS / local logic domain
  • Optional chassis / shield domain
For each domain, capture:
  • nominal voltage
  • allowable voltage range
  • reference node / ground strategy
  • expected transient environment
  • permitted couplings across isolation
4. Capture Channel-by-Channel Functional Requirements
Channel 1 — PLC output to LVDS trigger path
Define:
  • Supported field input voltages and tolerance
  • 5V / 24V selection method: jumper, DIP switch, resistor option, or auto-detect requirement
  • Input conditioning requirements: thresholding, filtering, polarity handling, hysteresis, and noise rejection
  • Whether the input must tolerate reverse polarity or accidental miswiring
  • Output requirement on LVDS side: true LVDS, logic-level signal feeding LVDS driver, or isolated logic feeding an LVDS stage
  • Required trigger response time and output pulse integrity
Channels 2 and 3 — LVDS to PLC return status paths
Define:
  • Status signal source characteristics on the LVDS side
  • Required PLC-compatible output behavior on the field side
  • Whether status outputs must sink current, source current, or emulate dry-contact/open-collector behavior
  • Whether both status channels are identical or have different semantics
  • Required default/failsafe state when LVDS is absent or power is lost
  • Need for output current limiting, short-circuit tolerance, and fault indication
5. Capture Isolation Requirements
Define the isolation intent before selecting isolators or isolated power.
  • Isolation needed between PLC field wiring and LVDS/logic side
  • Minimum isolation withstand requirement
  • Working voltage expectations
  • Required creepage and clearance targets based on intended environment
  • Whether each channel needs independent isolation or one shared isolation barrier is acceptable
  • Whether power must also cross the isolation barrier
  • Startup and fault behavior across the barrier
6. Capture Protection Requirements
Record protection expectations for each exposed interface.
Field-side protection
  • ESD protection level target
  • Surge / EFT / burst robustness target if used in industrial cabinets
  • Reverse polarity tolerance
  • Overvoltage tolerance on 24V inputs
  • Short-to-supply and short-to-ground fault cases
  • Protection against miswired DB9 pins
Logic / LVDS-side protection
  • ESD at LVDS connector or board edge
  • Protection against common-mode excursions and cable transients
  • Need for line termination, biasing, or fail-safe input behavior
Mechanical / connector protection
  • Shield termination strategy
  • Chassis bonding strategy if enclosure-mounted
  • Need for connector keying or labeling to avoid field misconnection
7. Capture Power Architecture Requirements
Define the minimum power strategy needed to make the board functional.
  • Identify available input power source(s): field-side supply, logic-side supply, or both
  • Determine whether the board must derive low-voltage rails from 24V field power, accept an existing low-voltage rail, or support both
  • Determine whether isolated power is required for the field-to-logic barrier
  • Capture rail requirements at a high level:
    • field-side voltage domain(s)
    • isolated logic / interface rail(s)
    • LVDS-side rail(s)
  • Define acceptable power-up and power-down sequencing behavior
  • Define indicator requirements for power present, trigger active, and status active
  • Record thermal and dissipation expectations for continuous operation
8. Define Configuration and Serviceability Requirements
Capture how the board will be configured and debugged.
  • 5V / 24V mode selection method and labeling
  • Any channel enable/disable options
  • Test points needed on field side, isolated side, and LVDS side
  • LED indicators for trigger and status channels
  • Silkscreen requirements for pinout, isolation boundary, polarity, and jumper settings
  • Requirement for field-replaceable fuse or resettable protection, if any
9. Capture PCB / Mechanical Requirements
Keep this high-level until part selection begins.
  • Board outline target and mounting constraints
  • Connector placement constraints, especially DB9 edge placement
  • Keepout around isolation barrier
  • Clearance rules between field and LVDS domains
  • Cable-entry direction and mechanical access to jumpers/switches
  • Environmental assumptions: enclosure, DIN rail, panel mount, bench use, etc.
10. Create Verification Requirements Early
Define how success will be checked before drawing the full schematic.
  • Verify 5V trigger mode operation
  • Verify 24V trigger mode operation
  • Verify correct LVDS trigger output generation
  • Verify both LVDS-to-PLC status return channels
  • Verify isolation integrity and no unintended ground coupling
  • Verify protection behavior under ESD/miswire/basic fault cases
  • Verify power-up defaults and fail-safe states
  • Verify DB9 pinout against the intended cable/system interface
  1. Create a project specification or design-notes document capturing the requirements above
  2. Add top-level functional blocks to the schematic:
    • DB9 field interface
    • trigger input conditioning block
    • isolation block
    • LVDS transmit path
    • two LVDS receive / PLC return blocks
    • protection block
    • power block
  3. Define named nets and domain labels for field, isolated, and LVDS sides
  4. Confirm pinout and configuration strategy before selecting exact parts
  5. Only after requirements are frozen, perform part selection for protection, isolation, LVDS interface, and power devices
  6. Then review creepage/clearance, grounding, and connector placement before PCB layout
Deliverables for the Requirements Phase
  • Confirmed functional block diagram
  • Confirmed DB9 pin mapping
  • Confirmed isolation boundary definition
  • Confirmed 5V / 24V trigger-mode behavior
  • Confirmed status-return output behavior toward the PLC
  • Confirmed high-level power architecture
  • Confirmed protection and fault-handling requirements
  • Initial verification checklist
Open Questions to Resolve Before Detailed Design
  • Must the new board match the attached board pin-for-pin, or only functionally?
  • What exact PLC I/O electrical standard must the trigger input and status returns satisfy?
  • Are the two return channels identical in behavior and loading?
  • What LVDS connector/interface exists on the low-voltage side?
  • Is isolated power generated on-board or supplied externally?
  • What isolation rating is required for the target installation?
  • What environmental / EMC robustness level is expected?
  • Should the board default to safe-off, safe-on, or last-state behavior during brownout or cable disconnect?
  • Objective

  • Current Project Status

  • Scope

  • High-Level Requirements Capture Plan

  • 1. Establish Functional Equivalence Targets

  • 2. Define External Interface Requirements

  • 3. Partition the System into Electrical Domains

  • 4. Capture Channel-by-Channel Functional Requirements

  • 5. Capture Isolation Requirements

  • 6. Capture Protection Requirements

  • 7. Capture Power Architecture Requirements

  • 8. Define Configuration and Serviceability Requirements

  • 9. Capture PCB / Mechanical Requirements

  • 10. Create Verification Requirements Early

  • Recommended Flux Execution Sequence

  • Deliverables for the Requirements Phase

  • Open Questions to Resolve Before Detailed Design

Remarkable Harlequin Gadget Copter

Remarkable Harlequin Gadget Copter thumbnail
Isolated PLC-to-LVDS interface board with one trigger output, two LVDS status return channels, DB9 field connector, selectable 5 V or 24 V trigger conditioning, and protected 24 V power input.

Properties

Properties describe core aspects of the project.

Pricing & Availability

Distributor

Qty 1

Arrow

$8.02–$10.81

Digi-Key

$32.75–$35.39

LCSC

$10.37–$10.45

Mouser

$46.16

TME

$12.74

Verical

$41.10–$88.44

Controls