그리고 Flux의 export는 데이터 포터빌리티/제조 중심 기능으로 안내되며, 협업은 보통 Flux 내부 공유를 권장합니다. 또한 현재 export 도구 안내상 내보내기 형식들은 PCB layout data 기준으로 생성되며 schematic export는 포함되지 않습니다
즉, 지금 보신 것처럼 결선이나 컴포넌트 정보가 없는 이유는 Flux에서 회로도 PDF export 자체를 지원하지 않기 때문입니다.
이전 답변은 제가 잘못 안내했습니다.
This document defines the initial board-to-board connector pin allocation between the real-time control board and the upper control board for the EV charger project. The goal is to reserve a practical and reviewable signal map that supports requirements capture, schematic capture planning, and later connector selection.
This is an architectural allocation document, not a final footprint or connector MPN decision. Final connector family, current rating, insulation system, pin pitch, shielding, and creepage/clearance suitability must be confirmed during detailed schematic and layout design.
Scope
The connector allocation covers:
Power and ground distribution between boards
Safety and charge control signals
Board health and fault reporting
A primary board-to-board data channel
Reserved pins for bring-up, debug, and future expansion
System Context
The EV charger architecture uses two logical controller domains:
Real-time control board: safety interlocks, CP/PP evaluation, contactor control, measurement, protection, and immediate shutdown behavior
Upper control board: network services, higher-level control, user-facing logic, logging, and supervisory charging commands
The board-to-board connector must therefore support both:
deterministic control/status exchange
serviceability and future protocol evolution
Connector Architecture Recommendation
Use one primary board-to-board connector group with the following logical partitions:
Power and return pins
Critical discrete control/status pins
Primary serial communication pins
Optional service/debug pins
Reserved expansion pins
For early design, keep safety-critical sensing local to the real-time control board and only export evaluated status or permission signals unless a clear system-level reason exists to do otherwise.
Initial Pin Allocation Table
Table
Pin
Signal Name
Direction
Domain
Type
Description
1
B2B_24V
Upper -> RT
Power
Power
24 V board-to-board supply input to real-time board
2
B2B_24V_RET
RT -> Upper
Power
Return
24 V return paired with supply path
3
B2B_5V_AUX
Upper -> RT
Power
Power
Optional auxiliary 5 V rail if required by architecture
4
B2B_5V_RET
RT -> Upper
Power
Return
5 V return
5
B2B_GND_1
Bidirectional
Ground
Ground
Digital/reference ground
6
B2B_GND_2
Bidirectional
Ground
Ground
Additional ground pin for return integrity
7
B2B_GND_3
Bidirectional
Ground
Ground
Additional ground pin for return integrity
8
CHARGE_ENABLE
Upper -> RT
Control
Discrete
Charge permission from upper board
9
CHARGE_STOP
Upper -> RT
Control
Discrete
Explicit stop request
10
RESET_FAULT
Upper -> RT
Control
Discrete
Non-latched fault reset request
11
RT_READY
RT -> Upper
Status
Discrete
Real-time board initialized and operational
12
CHARGING_ACTIVE
RT -> Upper
Status
Discrete
Charging currently active
13
CONTACTOR_STATE
RT -> Upper
Status
Discrete
Main contactor state indication
14
PROTECTION_TRIP
RT -> Upper
Status
Discrete
Summary trip output for immediate supervisor awareness
15
UART_TX_RT
RT -> Upper
Data
UART
Real-time board transmit
16
UART_RX_RT
Upper -> RT
Data
UART
Real-time board receive
17
HEARTBEAT_RT
RT -> Upper
Status
Discrete
Optional watchdog/heartbeat pulse
18
COMM_ENABLE
Upper -> RT
Control
Discrete
Communication channel enable or wake control
19
CURRENT_LIMIT_REQ_0
Upper -> RT
Control
Reserved
Optional discrete current-limit encoding bit 0
20
CURRENT_LIMIT_REQ_1
Upper -> RT
Control
Reserved
Optional discrete current-limit encoding bit 1
21
CP_STATE_0
RT -> Upper
Status
Reserved
Optional discrete CP state bit 0
22
CP_STATE_1
RT -> Upper
Status
Reserved
Optional discrete CP state bit 1
23
FAULT_SUMMARY_0
RT -> Upper
Status
Reserved
Optional discrete summary fault bit 0
24
FAULT_SUMMARY_1
RT -> Upper
Status
Reserved
Optional discrete summary fault bit 1
25
DBG_TX
RT -> Upper
Debug
UART
Optional debug serial transmit
26
DBG_RX
Upper -> RT
Debug
UART
Optional debug serial receive
27
SERVICE_MODE
Upper -> RT
Control
Discrete
Optional service mode request
28
RESERVED_1
TBD
Reserved
Reserved
Future expansion
29
RESERVED_2
TBD
Reserved
Reserved
Future expansion
30
RESERVED_3
TBD
Reserved
Reserved
Future expansion
Minimum Required Pins for First Hardware Revision
If connector pin count must be reduced, keep at least the following:
B2B_24V
B2B_24V_RET
B2B_GND_1
B2B_GND_2
CHARGE_ENABLE
CHARGE_STOP
RT_READY
CHARGING_ACTIVE
PROTECTION_TRIP
UART_TX_RT
UART_RX_RT
Signal Group Notes
Power and Ground
Provide multiple ground pins before adding optional feature pins.
If the 5 V rail is not exported, remove B2B_5V_AUX and B2B_5V_RET and convert those pins to extra ground or reserved pins.
Final current through board-to-board power pins must be reviewed against connector contact rating and temperature rise.
Critical Control and Status
CHARGE_ENABLE should be treated as the supervisory permission input.
CHARGE_STOP should remain separately visible even if equivalent functionality exists in the serial protocol.
PROTECTION_TRIP is useful as a fast summary signal independent of packet parsing.
Data Channel
Use one primary serial channel first. UART is acceptable for first revision if trace length, noise environment, and isolation strategy remain manageable.
If later changed to CAN, repurpose the same logical slot pair to B2B_CAN_H and B2B_CAN_L and keep nearby ground reference pins.
Debug and Service
Keep debug pins available during prototype stages even if they are not populated in production.
SERVICE_MODE should be protected against accidental assertion in production systems.
Alternate Mapping Option: CAN-Based Board Link
If the project decides to use CAN instead of UART between boards, reassign:
Pin 15 -> B2B_CAN_H
Pin 16 -> B2B_CAN_L
Pin 17 -> CAN_STBY or keep HEARTBEAT_RT
Pin 18 -> CAN_WAKE or COMM_ENABLE
In that case, discrete status pins may be reduced later if the system demonstrates reliable startup and fault reporting over CAN.
Allocation Rules
Keep power, return, and ground pins grouped together physically.
Keep UART or CAN pins adjacent to at least one ground reference pin where practical.
Place critical discrete control signals before optional diagnostics.
Do not export raw safety sensor analog signals to the upper board unless there is a strong system requirement.
Keep protection evaluation local to the real-time board and export evaluated states.
Open Items
Final choice of UART vs CAN for board-to-board communication
Whether 5 V must be exported across boards
Whether discrete CP state pins are needed in addition to serial reporting
Whether fault summary should remain a single fast hardware pin only or also use multiple discrete fault outputs
Final connector family, pitch, pin count margin, creepage, and locking method
Review Checklist
Confirm board-to-board link protocol choice
Confirm required power rails shared between boards
Confirm which discrete pins remain mandatory even when serial link is present
Confirm production vs bring-up population strategy for debug pins
Confirm connector current rating and environmental robustness
Confirm pin assignment consistency with the net naming convention document
Exit Criteria
This document is ready for the next phase when:
the board-to-board protocol is selected
mandatory pins are frozen
optional and debug pins are clearly marked
connector family selection can begin with electrical pin count and grouping already defined