3.3V 레귤레이터 추가 안내

flux

검토용 회로도 PDF를 내보냈습니다.
원하시면 이어서 외주 검토용으로 같이 보낼 수 있게
  • BOM CSV
  • 검토 요청 메일 초안
  • 현재 남은 ERC/DRC 요약 1페이지 도 바로 정리해드릴게요.
hwangmoonjin

hwangmoonjin

회로도에 결선이나 컴퍼넌트 정보가 없습니다.

flux

맞습니다. 제가 드린 PDF는 검토용 회로도 PDF가 아니었습니다.
Flux 문서에서 가장 직접적인 답은 이겁니다:
Can I export my schematic as a PDF?
No, you cannot export a PDF of your schematic from Flux right now.
Source
그리고 Flux의 export는 데이터 포터빌리티/제조 중심 기능으로 안내되며, 협업은 보통 Flux 내부 공유를 권장합니다. 또한 현재 export 도구 안내상 내보내기 형식들은 PCB layout data 기준으로 생성되며 schematic export는 포함되지 않습니다
즉, 지금 보신 것처럼 결선이나 컴포넌트 정보가 없는 이유는 Flux에서 회로도 PDF export 자체를 지원하지 않기 때문입니다.
이전 답변은 제가 잘못 안내했습니다.
필요하시면 다음으로는:
  • 외주 검토 요청용 문구를 정리해드리거나
  • Flux에서 상대방이 프로젝트를 직접 보도록 공유하는 방식 기준으로 안내해드릴게요.
공유 방법 알려줘
U1부터 점검
ERC 문제 확인
BOM 정보 보기
Sign up to send

Files

Schematic

Layout

Preview

Upper Control Board I/O Allocation Document
Purpose
This document defines the first-pass I/O allocation for the Upper Control Board in the EV charger architecture. The Upper Control Board owns supervisory control, external communications, user/service interfaces, logging coordination, and non-safety-critical system management. Safety-critical sensing and protection decisions remain local to the Real-Time Control Board.
Allocation Principles
  • Keep all hard real-time and safety shutdown functions on the Real-Time Control Board.
  • Route external communications and service interfaces to the Upper Control Board.
  • Keep board-to-board control and status exchange explicit and reviewable.
  • Reserve margin for protocol growth, diagnostics, and future product variants.
  • Separate communication, service, storage, and user-interface I/O groups.
I/O Ownership Summary

Table

I/O GroupUpper Control Board OwnsNotes
Network uplinkEthernetPreferred location for backend / OCPP / service network
Field bus / expansionCAN, RS-485For external devices or system integration
Service interfaceRS-232 or service UARTLocal debug / manufacturing / field service
Board-to-board commsUART or CAN to Real-Time BoardFinal selection still open
System control outputsCharge authorization, operating mode, reset requestSent to Real-Time Board through defined interface
Status inputsFault summary, CP state, charging state, measured valuesReceived from Real-Time Board
User interfaceLEDs, buttons, display, buzzer if presentUpper board ownership preferred
StorageeMMC / SD / flash / EEPROM if usedLogging, configuration, updates
Wireless / modemOptional LTE / Wi-Fi / BT module controlOptional, architecture dependent
External Interface Allocation
Ethernet
  • 1 x Ethernet interface allocated to Upper Control Board
  • Intended for backend connectivity, configuration, diagnostics, and OCPP / future higher-level protocols
  • PHY/RJ45 or external magnetics approach to be decided in detailed design
CAN
  • 1 x external CAN interface allocated to Upper Control Board
  • Intended for site integration, optional expansion modules, or future subsystem coordination
  • If internal board-to-board link uses CAN, external CAN must remain logically separated
RS-485
  • 1 x RS-485 interface allocated to Upper Control Board
  • Intended for industrial integration, metering add-ons, or installer-facing field connections
RS-232 / Service UART
  • 1 x service serial interface allocated to Upper Control Board
  • Intended for bring-up, maintenance, manufacturing test, and local diagnostics
Optional Wireless / Modem Control
  • Reserve GPIO/UART/SPI class resources for optional communications module integration
  • Do not freeze until product connectivity scope is finalized
Board-to-Board Interface Ownership
The Upper Control Board should own the supervisory side of the inter-board interface.
Outputs from Upper Control Board to Real-Time Board
  • B2B_CHARGE_EN
  • B2B_CHARGE_STOP
  • B2B_RESET_FAULT
  • B2B_MODE_SEL or equivalent frame field
  • B2B_CURRENT_LIMIT_SET or equivalent frame field
  • B2B_SESSION_ID or equivalent control context
  • B2B_HEARTBEAT_TX if discrete heartbeat is retained
Inputs from Real-Time Board to Upper Control Board
  • B2B_RT_READY
  • B2B_CHARGING_ACTIVE
  • B2B_CONTACTOR_STATE
  • B2B_CP_STATE
  • B2B_PP_VALID
  • B2B_FAULT_OUT or framed fault summary field
  • B2B_WARNING_SUMMARY
  • B2B_AC_VOLTAGE_RMS
  • B2B_AC_CURRENT_RMS
  • B2B_ACTIVE_POWER
  • B2B_ENERGY_ACCUM
  • B2B_LINE_FREQUENCY
  • B2B_TEMP_TERM
  • B2B_TEMP_CONTACTOR
  • B2B_HEARTBEAT if a discrete heartbeat line is retained
Logical I/O Class Allocation

Table

Logical ClassDirection at Upper BoardTypical Resource TypeNotes
Inter-board receive statusInputUART RX / CAN RX / GPIO statusPrefer framed transport over many discrete pins
Inter-board transmit controlOutputUART TX / CAN TX / GPIO controlKeep safety semantics documented
EthernetBidirectionalMAC/RMII/RGMII or SPI NIC classDepends on processor choice
CANBidirectionalCAN controller + transceiverExternal field bus
RS-485BidirectionalUART + direction controlInstaller / field devices
Service UARTBidirectionalUARTDebug / maintenance
UI indicatorsOutputGPIO / PWMLEDs, buzzer
User inputsInputGPIO / interruptButtons, service switches
StorageBidirectionalSDIO / SPI / eMMC / QSPILogging / configuration
Optional module controlIn/OutUART / GPIO / SPILTE / Wi-Fi / BT options

Table

FunctionMinimum Budget
Ethernet1
CAN controller1
UARTs2 to 3
RS-485 direction controls1
GPIO outputs6+
GPIO inputs4+
Storage interface1
Debug interface1
Timer/PWM for UI1 to 2
Optional high-speed expansionReserve if using modem / advanced HMI
Suggested Signal Grouping
Group A: Power and Ground References
  • Board power input(s)
  • Board ground reference(s)
  • Shield / chassis strategy to be reviewed later
Group B: Inter-Board Supervisory Control
  • Charge enable / stop
  • Mode selection
  • Current limit command
  • Fault reset request
  • Session / command context
Group C: Inter-Board Status and Measurements
  • RT ready
  • Charging active
  • Fault summary
  • Warnings
  • CP state
  • Key measurement values
Group D: External Communications
  • Ethernet signals
  • CAN TX/RX
  • RS-485 TX/RX/DE
  • Service UART TX/RX
Group E: User / Service Interfaces
  • LED outputs
  • Button / service input
  • Local debug connection
  • Optional buzzer / display control
Group F: Storage / Update / Expansion
  • Boot / recovery indicators
  • Update control path
  • Nonvolatile storage bus
  • Optional modem or wireless control signals
Unified Test Point Naming Convention
The Upper Control Board shall use the same project-wide test point naming convention as the Real-Time Board so connector bring-up, power validation, CAN debug, and service procedures use one consistent naming system.
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 the shared connector-facing inter-board net itself
Naming Rules
  • Use uppercase with underscores only.
  • Prefer the actual local net name where the test point is located.
  • Use B2B_ names only for direct connector-side shared nets.
  • Keep the same style across power, CAN, UART, RS-485, Ethernet support rails, status GPIO, and debug/service nodes.
  • Avoid ambiguous names that omit the board origin.
  • TP_UPPER_24V_IN_RAW
  • TP_UPPER_3V3_MAIN
  • TP_UPPER_CAN_TXD
  • TP_UPPER_CAN_RXD
  • TP_UPPER_RS485_TXD
  • TP_UPPER_RS485_RXD
  • TP_UPPER_DBG_UART_TX
  • TP_UPPER_ETH_3V3
  • TP_B2B_CAN_H
  • TP_B2B_CAN_L
  • TP_B2B_CHARGE_EN
Bring-Up Coverage Expectation
When test points are added to Upper Board interface pages, they should follow the unified naming rule and cover at least:
  • board power-entry validation
  • board-local CAN controller/transceiver visibility if populated
  • board-to-board connector-side CAN visibility where practical
  • service UART or field bus access where retained
  • any dedicated sideband control/status lines kept in the architecture
Upper Board Functional Ownership Matrix

Table

FunctionUpper Control BoardReal-Time Board
Backend communicationsOwnerNo
User/session supervisionOwnerNo
Charge permission policyOwnerReceives result only
Safety shutdown decisionNoOwner
CP waveform/state evaluationNoOwner
GFCI trip decisionNoOwner
Environmental protection tripNoOwner
Logging coordinationOwnerShared source
Firmware update orchestrationOwnerApplies local image as defined
Diagnostics / service UIOwnerShared support
Open Decisions Affecting Final I/O Freeze
  • Final inter-board transport choice: UART-first or CAN-first
  • Ethernet physical implementation and connector strategy
  • Whether RS-232 remains required in production hardware
  • Whether optional wireless or modem capability is included in Rev A
  • Local HMI scope: LED only vs display + buttons
  • Storage strategy: onboard flash only vs removable storage support
  • Isolation requirements for any external ports
  • Ground/chassis/shielding partition strategy
  1. Freeze external communications scope
  2. Freeze board-to-board transport method
  3. Freeze user/service interface scope
  4. Freeze storage/update architecture
  5. Freeze processor class and peripheral count
  6. Freeze connector and pin allocation
  7. Freeze final I/O map for schematic capture
Exit Criteria
  • Upper board responsibilities are clearly separated from Real-Time Board responsibilities
  • External communications ports are selected and documented
  • Minimum peripheral budget is accepted
  • Inter-board signal ownership is documented
  • Open items affecting processor choice are explicitly listed
  • Document is sufficient to support processor selection and schematic page planning

  • Purpose

  • Allocation Principles

  • I/O Ownership Summary

  • External Interface Allocation

  • Ethernet

  • CAN

  • RS-485

  • RS-232 / Service UART

  • Optional Wireless / Modem Control

  • Board-to-Board Interface Ownership

  • Outputs from Upper Control Board to Real-Time Board

  • Inputs from Real-Time Board to Upper Control Board

  • Logical I/O Class Allocation

  • Recommended First-Pass Peripheral Budget

  • Suggested Signal Grouping

  • Group A: Power and Ground References

  • Group B: Inter-Board Supervisory Control

  • Group C: Inter-Board Status and Measurements

  • Group D: External Communications

  • Group E: User / Service Interfaces

  • Group F: Storage / Update / Expansion

  • Unified Test Point Naming Convention

  • Naming Format

  • Board Prefix Rules

  • Naming Rules

  • Recommended Examples

  • Bring-Up Coverage Expectation

  • Upper Board Functional Ownership Matrix

  • Open Decisions Affecting Final I/O Freeze

  • Recommended Freeze Order

  • Exit Criteria