Project Specification: CT04 Intelligent Control PCB
Project Overview
Status: Draft / requirements capture only — no schematic implementation approved yet.
The CT04 Control PCB is the central control board for a robotic platform. It coordinates low-voltage logic power, wired and wireless communications, local sensing, subsystem power gating, fan control, status lighting, and proactive functional-safety monitoring for Safe Torque Off (STO).
Latest User Updates Captured
The power supplies are not part of the Control PCB; they are located on a separate Power PCB.
The Control PCB receives already-regulated 5V and 24V through connectors from the Power PCB.
The separate Power PCB contains the DC/DC supplies. The Control PCB should be treated only as a consumer/distribution/control board receiving regulated 5V and 24V via connector(s).
PCB target size is approximately 260mm × 140mm.
Ethernet and USB connectors must be double-row / dual-row board connector or header style, similar in concept to the linked Würth Elektronik dual-row connector example.
Connector choices should be derived from the attached CT04 electrical drawings PDF; most connectors appear to be Molex Micro-Fit / related Molex families.
Current focus is the Control PCB only.
Planning-only remains active; no schematic or PCB implementation is authorized yet.
User requested staged implementation: Step 1 = MCU + Ethernet + CAN, Step 2 = LoRa + Wi‑Fi, then additional subsystems in later approved steps.
Intended Use
Robotic platform system controller / coordination board.
Prototype-to-validation schematic design focus.
Expected to interface with motor-drive logic, peripheral sensors, camera/LIDAR USB devices, BMS communication, CAN buses, Ethernet devices, wireless links, fans, status lighting, and STO safety loops.
Intended environment and compliance class are not yet confirmed.
What the Device Should Do
Receive regulated 5V and 24V power from the separate Power PCB through board connectors.
Generate local 3.3V logic rails from 5V.
Provide isolated power for selected communication interfaces.
Run an STM32F427ZI MCU as the main coordinator.
Provide wired communication: Ethernet switch, USB hub, RS-485/BMS link, and two CAN buses.
Provide wireless communication: LoRa and Wi-Fi.
Gate selected subsystem power rails under MCU control.
Drive RGB status lighting and IR LED arrays with PWM-capable constant-current / MOSFET driver stages.
Monitor board temperature and control cooling fans.
Provide redundant hardware-level STO cutout and diagnostic feedback paths.
Main Features
Table
Area
Required Feature
Control power input
Regulated 5V and 24V supplied from external Power PCB connectors
Main 5V conversion
Located on separate Power PCB, not implemented on Control PCB
Legacy / field rail references
PDF includes 24V_1, 5V_1, 3.3V_1, DC BUS Voltage nets; exact relationship to 54.6V input needs confirmation
Logic rail
3.3V derived from 5V via local regulator(s)
Isolated rail
5V_ISO / 3.3V_ISO, at least 1.5kV galvanic isolation
Protection still TBD: connector input fuse/current limit, reverse-polarity protection if needed, TVS/surge protection, and separation between 5V/24V domains and isolated domains.
MCU Core
MCU: STM32F427ZI in 144-pin LQFP.
VDD: 3.3V on all VDD pins.
Decoupling: 100nF per VDD pin, plus appropriate bulk capacitance.
Analog domain: VDDA/VSSA filtered with ferrite bead.
Power control outputs: DO_Power_ON, DO_Power_Drives, DO_PTC_Switch, DO_Switch_Charging_contacts.
Target standby power limit remains less than or equal to 1W until changed. Exact loads and current limits are TBD.
Lighting and Indicators
RGB left/right light connectors appear in the PDF as Molex 43045-0400 4-pin connectors.
Signals include DO_Left_Light_R/B/G, DO_Right_Light_R/B/G, ON/OFF_Light_R/G/B, and DO_EM_Light.
IR LED connectors include IR_LIGHT_ANODE and IR_LIGHT_CATHODE; PDF shows Floor IR / Fork IR using 43650-0300 3-pin style and LED driver 1A notes.
Thermal Control
Fan connector appears as Molex 43045-0400 4-pin in the PDF.
Signals include FAN Power (+), DI_FAN_Feedback, and PWM fan power notes.
Temperature sensor references include Temperature sensor1 and Temperature Sensor2; exact sensor type and connector pinout TBD.
Functional Safety / STO
PDF references STO_1, STO_2, STO_1_RTN, and STO_2_RTN across several drive-control connectors.
Dual-channel STO remains safety-critical and requires explicit architecture confirmation before schematic implementation.
Connector Information Extracted from Attached PDF
OCR extraction from the CT04 electrical drawings PDF indicates these connector families and uses. Critical pinouts must be verified from the original PDF before schematic capture.
Power PCB ↔ Control PCB Interface Connector
User-provided interface connector image shows connector reference J8. User confirmed to use a 20-pin connector for this interface.
Table
J8 Pin
Signal
1
24V_1
2
24V_1
3
DC BUS Voltage
4
DC BUS Voltage(-)
5
DI_Charger_1_Connected
6
DI_Charger_2_Connected
7
DI_PS1_Power_Good
8
Not shown / TBD
9
24V_1(-)
10
24V_1(-)
11
5V_1
12
5V_1(-)
13
Not shown / TBD
14
Not shown / TBD
15
Not shown / TBD
16
Not shown / TBD
17
DO_Power_Drives
18
DO_Switch_Charging_contacts
19
DO_PTC_Switch
20
DO_Power_ON
Implementation notes for this connector:
Pins 1–2 and 9–10 appear to parallel the 24V rail and return for higher current capacity.
Pins 11–12 provide the 5V rail and return from the Power PCB.
Pins 3–4 expose the DC bus voltage sense/reference; exact voltage-scaling and isolation/protection strategy must be defined before connecting to MCU ADC.
DI signals from the Power PCB should use protected digital-input conditioning before MCU pins.
DO signals going to the Power PCB should use appropriate output drivers / open-drain or high-side/low-side topology as required by the Power PCB input circuit.
Screw terminals remain prohibited. Pluggable keyed connectors are required, with Molex Micro-Fit / related Molex families preferred based on the PDF.
Power and Runtime Expectations
Control PCB input: regulated 5V and 24V from the separate Power PCB.
5V rail: PDF references 5V 5A; final supply capability and derating must be confirmed against DC2468A configuration.
3.3V load current is not yet defined.
Isolated rail load current is not yet defined.
PDF references many 24V_1 loads and 24V 3A notes; on the Control PCB this 24V is treated as an incoming rail from the Power PCB and may be passed through or gated to loads.
Standby target: less than or equal to 1W, enforced partly by load gating unless changed.
Power Tree and Power Budget
Diagram
Open power-budget items before schematic implementation:
Table
Rail
Known Loads
Missing Information
5V input from Power PCB
USB hub ports, LDO input, isolated DCDC input, logic loads as applicable
Connector pinout, fuse/current limit, max continuous/peak current from Power PCB
5V
USB hub ports, LEDs, fans, LDO input, isolated DCDC input
Confirm 5A target, USB per-port current, fan count/current, LED/IR current
3.3V
STM32, CC3300, SX1262, logic gates
Wi-Fi peak current, MCU current mode, peripheral logic current
5V_ISO / 3.3V_ISO
Isolated CAN and RS-485 sides
Number of isolated channels, transceiver current, field-side connector loads
24V_1 input from Power PCB
Drive controls, PC 24V, LIDAR 24V, sensors, spare outputs
Current per output, which 24V supply feeds each load, fuse/current-limit strategy
Manufacturing and Assembly Expectations
Screw terminals prohibited.
Molex Micro-Fit / related Molex connectors preferred based on PDF.
Ethernet and USB connectors must be double-row where applicable.
Four Ethernet switch ports use RJ45 connectors with integrated magnetics.
Target board size: about 260mm × 140mm.
High-speed routing requirements imply likely 4-layer or higher PCB; final layer count TBD.
Controlled-impedance routing required for USB, Ethernet, and RF.
Isolation spacing: at least 2mm keepout between GND_SYSTEM and GND_ISO across all layers unless isolation standard requires more.
Assembly preference, manufacturer, and package constraints are TBD.
Firmware-Relevant Hardware Requirements
STM32F427ZI firmware must control:
power-gating outputs,
fan PWM outputs,
RGB/IR LED PWM outputs,
STO relay outputs,
CAN interfaces,
Ethernet host link,
USB hub control/status as required,
LoRa SPI,
Wi-Fi SDIO/SPI or USB configuration path if selected,
I2C temperature sensors.
Required debug/programming interface not yet specified; SWD header is assumed but must be confirmed.
Boot/reset controls not yet specified.
PDF includes the note “How to automatic Upgrate CPU FW? Needed??” — firmware upgrade method must be decided.
Physical Design Expectations
Board size target: approximately 260mm × 140mm.
Mounting holes: TBD.
Enclosure assumptions: TBD.
Connector edge placement: TBD.
Antenna placement and keepout: required for LoRa and Wi-Fi; exact mechanical constraints TBD.
Isolation boundary: physical keepout of at least 2mm between system and isolated grounds.
USB D+/D-: 90 ohm differential impedance, stubs under 2mm.
RF path: 50 ohm coplanar waveguide to antenna connector with continuous ground reference and dense via stitching.
The 54.6V/DC-bus conversion area is not on the Control PCB. Any DC-bus voltage sense lines entering the Control PCB still require appropriate connector clearance, protection, scaling, and isolation/safety review.
Ground domains:
GND_SYSTEM: MCU, wireless, regulators, local logic.
GND_ISO: isolated CAN slave and BMS RS-485 field side.
Maintain at least 2mm clearance between GND_SYSTEM and GND_ISO on all layers with no overlapping traces unless a different safety/EMC requirement is chosen.
Important Design Decisions Captured So Far
Main MCU direction: STM32F427ZI, 144-pin LQFP.
Main 5V and 24V power conversion is off-board on the Power PCB; Control PCB receives regulated 5V and 24V through connector(s) and only handles local regulation/distribution/protection.
Wi-Fi direction: TI CC3300, with PDF showing possible USB configuration path.
LoRa direction: Semtech SX1262.
Ethernet direction: Microchip KSZ8895.
USB hub direction: Infineon CY7C65642.
PCB target size: about 260mm × 140mm.
No screw terminals; use keyed Molex Micro-Fit / related connectors where possible.
Ethernet and USB connectors must be double-row where applicable.
Isolation required for selected CAN and RS-485 links.
Controlled impedance is mandatory for USB, Ethernet, and RF.
Staged Implementation Plan
Implementation will proceed in approved steps. Each step should first produce/confirm the schematic plan, then implement, then run ERC/design review before moving on.
Local 5V-to-3.3V regulation required for the MCU and communication logic.
Ethernet block using KSZ8895 reference/eval schematic as the starting point.
Ethernet topology confirmed: use the KSZ8895 as a 4-port external Ethernet switch, with the additional switch port connected to the STM32 Ethernet MAC.
Ethernet host interface between STM32 and KSZ8895 confirmed as RMII.
Four external Ethernet ports will use RJ45 connectors with integrated magnetics.
CAN block using STM32 internal CAN controllers:
one isolated CAN slave/PC link,
one non-isolated CAN master/peripheral link unless changed.
Slave CAN uses TI ISO1042DWEVM / ISO1042-based isolated CAN design, quantity 1 unit.
Master CAN is non-isolated.
ISO1042 isolated CAN field side will be powered from isolated 5V generated locally on the Control PCB from J8 5V.
CAN connector style confirmed as RJ45 with pinout: pin 1 = CAN_H, pin 2 = CAN_L, pin 3 = GND.
CAN termination confirmed: master CAN port requires 120Ω termination; slave CAN port has no termination.
CAN protection and isolated power domain as required.
Step 1 open decisions before implementation:
Ethernet topology confirmed: 4 external switch ports plus one MCU Ethernet uplink using RMII.
Ethernet connector style confirmed: RJ45 connectors with integrated magnetics for the four external Ethernet ports.
CAN connector confirmed as RJ45: pin 1 CAN_H, pin 2 CAN_L, pin 3 GND.
CAN termination confirmed: fixed 120Ω on master CAN, no termination on slave CAN.
Confirmed: only slave CAN is isolated; its ISO1042 isolated side receives isolated 5V generated locally on the Control PCB from J8 5V. Master CAN is non-isolated.
Step 2 — Wireless: LoRa + Wi‑Fi
Scope:
SX1262 LoRa reference/eval schematic adapted to the CT04 board.
LoRa SPI/control lines to STM32, RF matching network, RF switch/filter if required, and SMA or U.FL/IPEX antenna connector.
TI CC3300 Wi‑Fi reference/eval schematic adapted to the CT04 board.
Wi‑Fi interface to STM32: SDIO preferred unless the final module/reference design requires another interface.
RF layout constraints: antenna keepout, 50Ω RF feed, ground stitching, and separation from Ethernet/USB noise sources.
Step 2 open decisions before implementation:
Confirm LoRa region/frequency: 868MHz, 915MHz, or dual population option.
Confirm LoRa antenna connector: SMA, U.FL/IPEX, or external cable connector.
Confirm whether Wi‑Fi is CC3300 bare IC/module and whether antenna is onboard or external.
Confirm if the PDF's Wi‑Fi USB configuration path is required or only a service/programming option.
Proposed Later Steps
USB hub + USB/RS‑485/BMS communication.
Power-input connectors, protection, monitoring, and 5V/24V distribution.
24V/5V load gating outputs and connector pinout reconstruction from the PDF.
Sensors, fans, RGB/IR lighting, and panel interface.
STO safety monitoring/control architecture after explicit safety requirements are confirmed.
PCB floorplanning, stackup, connector placement, controlled-impedance routing, and final DRC/ERC review.
Assumptions
This file is a planning/specification file only; no implementation is authorized until the user answers clarification questions and approves a schematic plan.
The PDF OCR may contain errors; critical connector part numbers and pinouts must be verified against the original drawing before schematic capture.
4-layer PCB is likely the minimum practical stackup due to RF, USB, Ethernet, 24V distribution, isolation, and ground-plane requirements, but this is not yet approved.
Safety-related STO circuitry will require explicit architecture confirmation before design.
Clarification Questions Before Implementation
Confirm J8 connector physical part number/series for the 20-pin Power PCB ↔ Control PCB interface.
What are the maximum available currents from the Power PCB for the 5V rail and 24V rail at the Control PCB connector?
Confirmed: the Control PCB receives separate 24V rails for PC power and other components.
Confirm the 5V rail target delivered to the Control PCB: is it 5V 5A as the PDF suggests, or another current?
Can you provide the connector pinout table from the original CAD/PDF, or should I manually reconstruct pinouts from the PDF OCR and ask you to verify each one?
Which exact Molex connector series should be standardized: Micro-Fit 3.0, Mini-Fit, Micro-Lock, or the exact part numbers shown such as 43045-xxxx and 43650-xxxx?
For Ethernet/USB “double row”: do you mean stacked/double-deck connectors, dual-row board headers, or two-row pin headers for cable harnesses?
How many Ethernet RJ45 ports and USB downstream ports are final?
Should USB downstream connectors be USB-A, cable headers, or both?
What are the mounting-hole locations, connector edge placement requirements, and keepout zones for the 260mm × 140mm PCB?
Should the board be 4-layer, 6-layer, or another stackup?
For STO: what safety category / PL / SIL target, relay part preference, and exact external safety-loop behavior are required?
Do you want me to keep staying planning-only until you explicitly say “implement schematic”?
Change Notes
Initial project specification created from user-provided pasted requirements on 2026-06-29.
Corrected power architecture: DC/DC supplies are on the separate Power PCB; Control PCB receives regulated 5V and 24V through connectors and must not implement battery/DC-bus DC/DC converters.
User confirmed J8 should be implemented as a 20-pin Power PCB ↔ Control PCB interface connector.
User confirmed the Control PCB receives separate 24V rails for PC power and general components.
Added staged implementation plan: Step 1 MCU + Ethernet + CAN, Step 2 LoRa + Wi‑Fi, followed by USB/RS‑485, power distribution, load gating, sensors/fans/lights, STO, and PCB layout.
Step 1 updates: Ethernet confirmed as 4 external switch ports plus MCU uplink; CAN RJ45 pinout confirmed as pin 1 CAN_H, pin 2 CAN_L, pin 3 GND; master CAN has 120Ω termination and slave CAN has no termination.
Step 1 update: STM32-to-KSZ8895 host Ethernet interface confirmed as RMII.
Step 1 update: four Ethernet ports use RJ45 connectors with integrated magnetics; isolated CAN reference is TI ISO1042DWEVM / ISO1042-based design for slave CAN only, quantity 1 unit.
Step 1 update: only slave CAN is isolated using one ISO1042-based channel; master CAN is non-isolated. Step 1 uses 5V from J8. Common Flux/library parts may be selected during implementation when exact MPNs are not specified.
No schematic, components, or PCB layout have been created yet.
Project Overview
Latest User Updates Captured
Intended Use
What the Device Should Do
Main Features
System Architecture
Hardware Subsystems
Power Input and Regulation
MCU Core
Wireless Communication
Wired Communication
CAN Bus Architecture
Load Gating
Lighting and Indicators
Thermal Control
Functional Safety / STO
Connector Information Extracted from Attached PDF
Power PCB ↔ Control PCB Interface Connector
Interfaces and Connections
Power and Runtime Expectations
Power Tree and Power Budget
Manufacturing and Assembly Expectations
Firmware-Relevant Hardware Requirements
Physical Design Expectations
Layout and Routing Requirements
Important Design Decisions Captured So Far
Staged Implementation Plan
Step 1 — MCU + Ethernet + CAN Base Bring-Up
Step 2 — Wireless: LoRa + Wi‑Fi
Proposed Later Steps
Assumptions
Clarification Questions Before Implementation
Change Notes
Reviews
Documents
Project Specification: CT04 Intelligent Control PCB
Step 1 Schematic Implementation Plan — MCU + Ethernet + CAN
Step 1 Implementation Review — MCU + Ethernet + CAN
Firmware Starter — STM32F427ZIT6
Step 1 Board Bring-Up Plan — MCU + Ethernet + CAN
Assets
No assets added.
CT04 Intelligent Control PCB
Control PCB for a robotic platform with 24V input, STM32F427ZI coordination, Ethernet/USB/CAN/RS-485/wireless interfaces, load gating, thermal control, and STO safety monitoring.
Properties
Properties describe core aspects of the project.
Pricing & Availability
Distributor
Qty 1
Arrow
$25.28–$27.21
Digi-Key
$18.05
HQonline
$15.13
LCSC
$19.93–$21.57
Mouser
$72.85
TME
$30.36
Verical
$41.46–$53.06
Controls
Welcome 👋
Flux helps you build PCBs faster with an AI teammate!
Create your account to collaborate, stay updated, fork your own version, and get instant answers from our AI agent.