그리고 Flux의 export는 데이터 포터빌리티/제조 중심 기능으로 안내되며, 협업은 보통 Flux 내부 공유를 권장합니다. 또한 현재 export 도구 안내상 내보내기 형식들은 PCB layout data 기준으로 생성되며 schematic export는 포함되지 않습니다
즉, 지금 보신 것처럼 결선이나 컴포넌트 정보가 없는 이유는 Flux에서 회로도 PDF export 자체를 지원하지 않기 때문입니다.
이전 답변은 제가 잘못 안내했습니다.
This document defines the real-time board side circuit requirements for the CAN-based board-to-board connector between the real-time control board and the upper control board.
It is intended to guide schematic capture for the connector interface, CAN physical layer, power entry through the connector, optional status/control lines, and bring-up provisions.
Scope
This document applies only to the real-time board side of the board-to-board interface.
Included:
24 V power entry from the board-to-board connector
Ground return and shield/bond handling at the real-time board side
CAN transceiver interface from MCU to connector
Optional wake and standby control handling
Optional status, fault, and debug sideband signals
Protection, filtering, and design-for-test expectations
Excluded:
Upper control board side implementation details
Internal RT board functional circuits beyond the connector interface boundary
The real-time board shall expose the connector-facing nets defined in the connector pin map and route them into the following local interface blocks:
connector power entry block
connector ground / bond block
CAN transceiver block
sideband status / control GPIO block
debug / service interface block
optional wake / standby handling block
Required Connector-Facing Nets on the RT Board
Mandatory
B2B_24V_IN
B2B_GND
B2B_CAN_H
B2B_CAN_L
Recommended
B2B_RT_READY
B2B_FAULT_OUT
B2B_CHARGE_EN
Optional
B2B_HEARTBEAT
B2B_RESET_REQ
B2B_SAFE_STATE
B2B_CAN_STB_CTRL
B2B_CAN_WAKE
B2B_DBG_UART_TX
B2B_DBG_UART_RX
B2B_BOOT_REQ
B2B_LOG_TRIG
B2B_INT_EVENT
B2B_WDOG_MON
B2B_3V3_AUX
B2B_ID0
B2B_ID1
B2B_SHIELD_GND
B2B_AUX_IO1
B2B_AUX_IO2
RT Board Side Circuit Requirements
1. Connector Power Entry
The connector power entry circuit on the RT board shall:
accept B2B_24V_IN through the allocated parallel connector pins
join the parallel 24 V pins into a local protected 24 V input node
join all connector ground returns into the local RT board return strategy
include footprint and routing provisions sized for the expected connector current
support downstream control of the local auxiliary 24 V domain when required by protection logic
Power Entry Design Rules
The two 24 V pins shall be shorted together locally with low-impedance copper.
The connector ground pins shall be tied into the RT ground entry region with short return paths.
If the RT board can disconnect or gate local 24 V loads, the connector entry node and switched local 24 V node shall be clearly separated by net naming.
The connector power entry region shall provide test access for voltage bring-up.
Recommended Nets
B2B_24V_IN
RT_24V_IN_RAW
RT_24V_IN_FUSED if a local fuse is used
RT_24V_AUX_SW if locally switched
B2B_GND
2. Ground and Bond Strategy
The RT board connector interface shall clearly distinguish the following where applicable:
digital / power return tied to B2B_GND
optional shield or bond connection from B2B_SHIELD_GND
any local chassis or quiet-bond strategy used for EMI management
Ground Rules
All connector return pins assigned as B2B_GND shall connect into the RT board ground return network.
B2B_SHIELD_GND shall not be assumed to be identical to logic ground until the system bonding strategy is frozen.
If a shield or bond connection is populated, its treatment shall be explicitly documented in schematic notes.
CAN return current paths shall remain short and local around the connector and transceiver area.
3. CAN Transceiver Interface
The RT board shall implement a dedicated CAN physical layer block between the MCU CAN controller pins and connector-facing nets.
Required Functional Elements
CAN transceiver
local decoupling for the transceiver supply
connector-facing B2B_CAN_H and B2B_CAN_L
MCU-facing CAN TX and CAN RX nets
optional standby or enable control if the selected transceiver supports it
optional wake handling if the selected transceiver supports wake signaling
CAN Block Requirements
The transceiver shall be placed close to the board-to-board connector.
B2B_CAN_H and B2B_CAN_L shall route as a tightly coupled differential pair from transceiver to connector.
Stub length between the transceiver and connector shall be minimized.
The CAN transceiver supply shall be decoupled locally.
Transceiver logic-level interface nets shall use project naming consistent with the MCU I/O allocation.
Recommended Nets
RT_CAN_TXD
RT_CAN_RXD
RT_CAN_STB if used
RT_CAN_WAKE_INT if used
B2B_CAN_H
B2B_CAN_L
4. CAN Termination Policy
The RT board side schematic shall include an explicit termination policy and shall not leave termination assumptions implicit.
Requirements
CAN termination shall not be implemented in the connector itself.
If the RT board is one physical end of the CAN link, the RT board may host one termination location.
The termination location shall be configurable by population option, resistor option, or clearly documented assembly variant.
If the termination is not populated on the RT board, the schematic shall show that the far end is expected to host the termination.
Recommended Implementation Pattern
one local CAN termination footprint near the transceiver
default DNP or fitted state clearly documented
optional split termination only if later EMC results justify it
Recommended Nets / Notes
RT_CAN_TERM_EN as documentation note or assembly option label if used
assembly notes for FIT / DNP termination population
5. CAN Wake and Standby Policy
B2B_CAN_WAKE
Use B2B_CAN_WAKE only if the power-state architecture requires one board to wake the other independently of normal CAN traffic.
If both boards remain powered in normal operation, B2B_CAN_WAKE should remain optional and may be left unpopulated at system level.
B2B_CAN_STB_CTRL
Use B2B_CAN_STB_CTRL only if the selected CAN transceiver requires or benefits from explicit standby control.
Requirements
Any use of B2B_CAN_WAKE shall be tied to a documented low-power strategy.
Any use of B2B_CAN_STB_CTRL shall be tied to the actual transceiver feature set.
If not used, these nets shall remain reserved or DNP and not be given undefined logic behavior.
6. Sideband Status and Control Lines
The RT board may expose sideband GPIO signals to simplify bring-up, fault visibility, or system integration.
Recommended Sideband Lines
B2B_RT_READY
B2B_FAULT_OUT
B2B_CHARGE_EN
Optional Sideband Lines
B2B_HEARTBEAT
B2B_RESET_REQ
B2B_SAFE_STATE
B2B_INT_EVENT
B2B_WDOG_MON
Sideband Rules
Each sideband signal shall have a defined default state at power-up.
Critical sideband outputs from the RT board shall not float during reset.
Inputs from the upper board shall have defined default behavior if disconnected or absent.
Any sideband line that duplicates CAN-framed information should be justified as a bring-up, service, or safety simplification.
7. Debug and Service Signals
Optional Debug Nets
B2B_DBG_UART_TX
B2B_DBG_UART_RX
B2B_BOOT_REQ
B2B_LOG_TRIG
Requirements
Debug lines shall be optional and must not be required for normal charging operation.
Debug lines shall be isolated from normal system operation in documentation and schematic intent.
If debug UART is included through the connector, the board shall still retain a local debug/programming path for MCU recovery.
8. Protection and Filtering Expectations
The RT board connector interface should include practical provisions for robust operation.
Recommended Practices
series damping / protection options on sideband GPIO lines where appropriate
RC filtering on noisy sideband inputs if required by system timing
no unnecessary series discontinuity in the CAN differential path
local decoupling at active interface ICs
clear separation between noisy switched power nodes and CAN / debug routing near the connector area
Caution
Do not add filtering on CAN_H / CAN_L that is inconsistent with the selected transceiver and bus design.
Do not rely on weak undefined logic defaults for critical control inputs.
9. Test and Bring-Up Requirements
The RT board connector interface shall support first power-up, staged bring-up, CAN debug, and connector-side fault isolation.
Required Bring-Up Features
test access to B2B_24V_IN or local derived entry node
test access to at least one local ground near the connector
ability to observe CAN TX/RX or CAN bus activity during bring-up
visibility of connector-facing sideband signals if they are populated
clear documentation for which optional connector pins are fitted, used, reserved, or DNP
clear probing access for power-entry validation before the CAN transceiver is enabled
test access that supports isolation of connector faults from MCU-side faults
Bring-Up Objectives
The connector interface test strategy should support the following early validation steps:
verify that 24 V reaches the RT board correctly through the connector
verify that connector ground and local RT ground are continuous as intended
verify that the CAN transceiver is powered correctly before bus communication is attempted
verify MCU-side CAN TX / CAN RX behavior independently from connector-side CAN_H / CAN_L behavior
verify optional sideband control and status lines without depending only on firmware logs
support fault isolation for no-power, no-bus-activity, stuck-sideband, or incorrect assembly cases
Required Test Point Coverage
At minimum, the RT board connector interface shall expose practical probe access for the following signal classes:
Power Entry
B2B_24V_IN or RT_24V_IN_RAW
local post-entry 24 V node such as RT_24V_IN_FUSED if used
local switched node such as RT_24V_AUX_SW if used
local connector-region ground
CAN MCU-Side
RT_CAN_TXD
RT_CAN_RXD
transceiver supply rail
transceiver standby or enable node if populated
CAN Connector-Side
B2B_CAN_H
B2B_CAN_L
termination option visibility or documented assembly state
Sideband Signals
B2B_RT_READY if populated
B2B_FAULT_OUT if populated
B2B_CHARGE_EN if populated
B2B_CAN_WAKE if populated
B2B_CAN_STB_CTRL if populated
Optional Debug / Service
B2B_DBG_UART_TX if populated
B2B_DBG_UART_RX if populated
B2B_BOOT_REQ if populated
Recommended Test Point Table
Table
Net / Node
Test Point Priority
Purpose
Bring-Up Stage
Notes
RT_24V_IN_RAW
Required
Verify connector power arrival
First power application
Preferred primary power-entry probe
RT_24V_IN_FUSED
Recommended
Verify post-protection 24 V continuity
Early power validation
Include if fuse or protection stage exists
RT_24V_AUX_SW
Recommended
Verify switched auxiliary 24 V behavior
Power-control validation
Include if RT board gates local 24 V
B2B_GND
Required
Probe reference near connector
All stages
At least one easily accessible local ground point
RT_CAN_VDD
Required if transceiver used
Verify CAN transceiver supply
Before CAN traffic check
Name may follow chosen transceiver rail naming
RT_CAN_TXD
Required
Verify MCU transmit activity
Firmware and bus bring-up
Helps separate MCU issues from physical-layer issues
RT_CAN_RXD
Required
Verify receive activity into MCU
Firmware and bus bring-up
Helps diagnose bus silent / bus stuck cases
B2B_CAN_H
Required
Observe connector-side CAN bus level
Physical-layer bring-up
Place access with minimal stub impact
B2B_CAN_L
Required
Observe connector-side CAN bus level
Physical-layer bring-up
Place access with minimal stub impact
RT_CAN_STB or B2B_CAN_STB_CTRL
Optional
Verify standby control state
Low-power / transceiver control validation
Include if standby control is implemented
RT_CAN_WAKE_INT or B2B_CAN_WAKE
Optional
Verify wake behavior
Low-power bring-up
Include only if wake strategy is implemented
B2B_RT_READY
Recommended
Confirm RT ready indication
Early firmware bring-up
Useful even before full CAN stack validation
B2B_FAULT_OUT
Recommended
Confirm hardware-visible fault state
Protection bring-up
Useful during fault injection and no-CAN debug
B2B_CHARGE_EN
Optional
Observe upper-board enable line
Integration bring-up
Include if dedicated sideband enable is retained
B2B_DBG_UART_TX
Optional
Observe debug log stream
Service / development
Best effort only
B2B_DBG_UART_RX
Optional
Inject service console input
Service / development
Optional if debug UART is routed through connector
Unified Test Point Naming Guidance
The RT board and Upper Control Board shall use one shared project-wide test point naming convention so bring-up procedures, schematics, and debug logs remain aligned.
Naming Format
TP__
Board Prefix Rules
RT for Real-Time Board local nets
UPPER for Upper Control Board local nets
B2B only when the measured node is intentionally the connector-facing inter-board net itself and not a board-local derivative
Naming Rules
Use uppercase with underscores only.
Prefer the actual local net name when the probe point is on a board-local node.
Use the connector-facing B2B_ net name only when the test point is physically on that connector-side shared net.
Use identical naming style on both boards for power-entry, CAN, sideband, and debug access.
Do not mix board-local and shared naming on the same test point.
Recommended Examples
TP_RT_24V_IN_RAW
TP_RT_GND_B2B_1
TP_RT_CAN_TXD
TP_RT_CAN_RXD
TP_B2B_CAN_H
TP_B2B_CAN_L
TP_B2B_RT_READY
TP_B2B_FAULT_OUT
TP_UPPER_24V_IN_RAW
TP_UPPER_CAN_TXD
TP_UPPER_CAN_RXD
TP_UPPER_RS485_TX
TP_UPPER_ETH_3V3
Intent
This convention ensures that any bring-up document can distinguish whether a probe point is on the RT board, on the Upper Control Board, or on the shared board-to-board interface itself.
Placement Guidance
Place at least one ground test point adjacent to the connector/CAN transceiver region.
Place the main 24 V entry test point close enough to the connector to validate connector delivery, but after any immediately relevant entry element if the intent is to validate protected power.
Place MCU-side CAN test points close enough to the transceiver/MCU interface to allow signal capture without probing deep inside dense routing.
Place connector-side CAN_H / CAN_L test access so that probing does not create long stubs or compromise the differential path.
Sideband test points should be grouped logically near the connector interface page region or debug cluster.
Test points intended for oscilloscope probing should have practical mechanical access after assembly.
Bring-Up Sequence Supported by Test Points
The test point plan should allow the following sequence: