Schematic Review Request

flux

I see the schematic PDF attachment. What would you like me to do with it — review it for issues, recreate it in Flux, extract the BOM, or use it as a reference for a new schematic?
mraouf

mraouf

review it for issues

flux

I’ll review the attached schematic PDF for electrical/design issues and summarize the findings. I’ll inspect the document first, then create a concise review note if the findings are detailed.

flux

I reviewed the PDF and saved the detailed findings in Schematic PDF Review — MRCOMM MRT134.
Key concerns: possible VBAT/VBATT net mismatch, LTE modem power/current capacity, STM32 special power pins, USB-C details, RF antenna layout, SIM interface, and TP4056 charger/power-path behavior. The next best step is to import or recreate the schematic in Flux so I can run a real ERC/netlist check instead of relying on PDF OCR.
Import and verify
Recreate schematic
Fix power nets
Check LTE power
Review charger path
No schematic yet

Talk to Flux to get started.

Refine this doc
Ask about this doc
Schematic PDF Review — MRCOMM MRT134
Source: SCH_Schematic1_2026-06-19.pdf
Method: OCR extraction from the uploaded PDF. Critical findings should be verified against the original EasyEDA schematic/netlist because OCR can miss junction dots and exact net labels.
Overall Assessment
The schematic appears to be a GPS/LTE tracker with STM32L496 MCU, LC29H GNSS, Quectel EG915 LTE, Li-ion charger/protection/fuel gauge, 5 V buck, 3.3 V/1.8 V rails, USB-C, CAN, SIM, and IO protection/filtering.
Several areas need review before PCB layout/manufacturing. The most important risks are power-path ambiguity, LTE current capability/decoupling, inconsistent battery net naming, USB-C implementation details, MCU analog/power pin completeness, and RF/SIM/layout-sensitive circuits.
High-Priority Issues / Risks
1. Battery and power-rail naming appears inconsistent
  • Page 6 uses VBATT around TP4056/DW01A/MAX17048.
  • Page 4 uses VBAT for the LTE modem supply and related regulators.
  • Page 3 uses VBATT on the STM32 VBAT pin.
Risk: VBAT and VBATT may be separate nets unintentionally. If so, LTE, charger, fuel gauge, and MCU backup domain may not share the intended battery node.
Recommendation: Explicitly define the battery system nets: raw cell, protected battery output, LTE VBAT, MCU VBAT backup, and charger BAT. Rename nets so the separation is intentional and documented.
2. LTE modem power supply may be underspecified or unclear
The EG915 section includes MIC29302, RT9193, SGM2019, bulk caps, and VBAT, but the source path from battery/5 V to modem VBAT is not clear from OCR.
Risk: LTE modules have high pulsed current demand, often around 2 A peak depending on module and radio conditions. Inadequate regulator current, trace width, or bulk capacitance can cause brownouts or network instability.
Recommendation: Verify EG915 hardware design guide requirements for VBAT voltage range, peak current, required low-ESR bulk capacitance near VBAT_BB/VBAT_RF pins, and layout trace width. Confirm MIC29302 output voltage setpoint and thermal dissipation.
3. MIC29302 adjustable regulator feedback should be recalculated
U26 MIC29302WU-TR has R52/R53/R54 around ADJ/EN/OUT, but OCR does not prove the exact feedback topology.
Risk: Wrong feedback resistor placement or value can produce an incorrect LTE VBAT rail.
Recommendation: Calculate expected VOUT from the actual feedback divider and compare against EG915 VBAT range. Confirm EN is driven to a valid logic level and not floating.
4. STM32 power pins need completeness check
STM32L496ZGT6 has many VDD/VSS pins plus VDDA, VSSA, VREF+, VREF-, VDDUSB, VBAT, and VDDIO2. OCR shows many 3.3 V labels and decoupling capacitors but does not clearly prove all special rails are correctly connected.
Risk: Missing VDDA/VREF/VDDUSB/VDDIO2 connections or insufficient decoupling can prevent boot, USB operation, ADC accuracy, or IO-bank operation.
Recommendation: Verify every STM32 power pin against the datasheet reference design. Add local 100 nF per VDD pin, appropriate bulk caps, connect VDDA/VREF+ per ST guidance, and ensure VDDUSB is powered when USB is used.
5. USB-C connector implementation should be checked
The MCU USB-C page shows CC1/CC2 with 5.1 k resistors, which is appropriate for a UFP/device. The LTE USB connector appears as micro-USB style with D+/D- ESD, VCC, ID, and GND.
Risks:
  • If USB-C is power input only or data+power, VBUS protection/current limiting should be defined.
  • D+/D- routing should be impedance-controlled enough for USB FS/HS as applicable.
  • Shield grounding/ESD strategy should be intentional.
  • For USB-C, both DP pins and both DN pins must be tied correctly if using a 16-pin receptacle.
Recommendation: Verify CC resistors are 5.1 k to GND and not accidentally tied elsewhere, add VBUS fuse/TVS as needed, and confirm D+/D- orientation and ESD placement.
6. GNSS RF front end requires datasheet/layout validation
LC29H page includes RF_IN, antenna connector, L12 27 nH, C/R network, and backup battery.
Risk: GNSS RF matching, antenna bias, and ESD are layout- and module-specific. Incorrect matching can significantly reduce GPS sensitivity.
Recommendation: Follow the LC29H hardware design guide exactly for RF_IN, active/passive antenna configuration, 50 Ω transmission line, ground keepout, and antenna connector placement. Mark matching components as DNP/fit options if required.
7. LTE RF antenna networks should be verified
Main and AUX antenna paths show DNP capacitors and 0 Ω series resistors.
Risk: RF performance depends on 50 Ω controlled impedance, pi matching footprint placement, grounding, and antenna connector layout. Missing ESD or poor ground stitching can degrade performance.
Recommendation: Keep pi matching networks close to module/connector per Quectel guide, route 50 Ω traces, add ground vias, and leave final matching values for RF tuning.
8. SIM interface protection and level shifting need careful check
The SIM section includes TXS0108EPWR, ESD/TVS, series resistors, and SIM connector.
Risk: SIM_CLK/DATA/RST/VCC have strict voltage and ESD requirements. TXS0108 can be unsuitable on some edge-sensitive or pull-up-heavy interfaces depending on directionality and capacitance.
Recommendation: Compare with Quectel EG915 reference SIM circuit. Usually the module provides USIM signals directly at the correct voltage; avoid unnecessary level translation unless required. Confirm SIM_DET polarity and pull-up voltage.
9. TP4056 charger/protection/fuel-gauge circuit needs functional review
Page 6 has TP4056 charger, DW01A+8205 protection, and MAX17048 fuel gauge.
Risks:
  • TP4056 is a linear charger; thermal dissipation can be high at 5 V input and high charge current.
  • PROG resistor value appears 1.2 k, likely about 1 A charge current; verify cell and thermal constraints.
  • The fuel gauge should monitor the protected cell node as recommended by Maxim.
  • TP4056 does not provide power-path/load sharing by itself.
Recommendation: Decide whether the system must operate while charging. If yes, add proper power-path/load sharing or charger IC with power-path management. Verify charge current, battery connector polarity, NTC/TEMP handling, and protection IC wiring.
10. Buck converter page needs datasheet verification
Page 2 appears to use XL4015E1 with 47 µH inductor, SS34 diode, large capacitors, and feedback divider R60/R61.
Risks:
  • XL4015 component values depend on input/output/current/switching frequency.
  • Inductor current rating/saturation and diode current/thermal rating must be checked.
  • Feedback divider must match the intended 5 V output.
Recommendation: Verify the exact XL4015 datasheet formula with R60/R61 and confirm VOUT. Confirm VIN range, load current, diode rating, capacitor ESR/ripple, and layout loop area.
Medium-Priority Issues / Review Items
11. CAN transceiver termination and connector protection
MCP2562 is present with CANH/CANL connector, but OCR did not show a 120 Ω termination across CANH/CANL on the connector page.
Recommendation: Add optional 120 Ω termination footprint or confirm termination is external. Add TVS for CANH/CANL if connecting off-board/automotive harnesses.
12. IO protection values may be inappropriate for all signal types
IO ports use 33 V TVS devices, BAT54S clamps, RC filters, 100 Ω/1 k resistors, and Schmitt buffers.
Risk: 33 V TVS may clamp too high for 3.3 V inputs unless series resistance/clamps are adequate. RC values may limit maximum signal frequency.
Recommendation: Define expected input voltage ranges and bandwidth for each connector. Size protection and dividers per use case.
13. ULN2003 outputs need load and flyback review
ULN2003A appears for DO1/DO2/DO3 with VIN and resettable fuses.
Recommendation: Confirm loads are low-side switched and share ground. Connect COM pin to the inductive load supply if driving relays/solenoids; otherwise document if unused.
14. External flash hold/reset/WP pins may need defined states
W25Q flash connections show WP, RESET_M, HOLD, CS1, but not all pull-ups are clear.
Recommendation: Ensure /CS, /WP, /HOLD or /RESET have valid default pull-ups so the flash is not accidentally held or write-protected during boot.
15. Boot/reset programming interface should be verified
BOOT0, RESET, SWD/programming header, crystal, and reset switch are present.
Recommendation: Confirm BOOT0 pull-down value and programming header includes SWDIO, SWCLK, NRST, GND, and target voltage. Ensure NRST capacitor/pull-up match ST recommendations.
Layout-Critical Notes
  • Place LTE bulk caps directly at EG915 VBAT_BB/VBAT_RF pins with wide copper pours.
  • Route GNSS and LTE antenna lines as 50 Ω controlled impedance with continuous ground reference.
  • Keep switching regulator hot loop compact and away from GNSS/LTE RF.
  • Keep SIM ESD close to the connector.
  • Place USB ESD close to USB connectors; route D+/D- as a pair.
  • Put each MCU decoupling capacitor next to its corresponding VDD pin.
  1. Export or share the original EasyEDA schematic/netlist if possible, so junctions and net names can be verified without OCR ambiguity.
  2. Perform a formal ERC/netlist check for unintended isolated nets, especially VBAT vs VBATT.
  3. Validate the power tree: VIN → 5 V → 3.3 V/1.8 V/LTE VBAT/battery charger.
  4. Check EG915, LC29H, STM32L496, TP4056, MAX17048, MIC29302, and XL4015 circuits against their reference designs.
  5. Before PCB fabrication, run a layout review focused on RF, LTE pulsed-current supply, USB, SIM, charger thermal, and switching regulator layout.

  • Overall Assessment

  • High-Priority Issues / Risks

  • 1. Battery and power-rail naming appears inconsistent

  • 2. LTE modem power supply may be underspecified or unclear

  • 3. MIC29302 adjustable regulator feedback should be recalculated

  • 4. STM32 power pins need completeness check

  • 5. USB-C connector implementation should be checked

  • 6. GNSS RF front end requires datasheet/layout validation

  • 7. LTE RF antenna networks should be verified

  • 8. SIM interface protection and level shifting need careful check

  • 9. TP4056 charger/protection/fuel-gauge circuit needs functional review

  • 10. Buck converter page needs datasheet verification

  • Medium-Priority Issues / Review Items

  • 11. CAN transceiver termination and connector protection

  • 12. IO protection values may be inappropriate for all signal types

  • 13. ULN2003 outputs need load and flyback review

  • 14. External flash hold/reset/WP pins may need defined states

  • 15. Boot/reset programming interface should be verified

  • Layout-Critical Notes

  • Recommended Next Actions

Documents

Assets

No assets added.

MRCOMM MRT134

MRCOMM MRT134 thumbnail
Welcome to your new project. Imagine what you can build here.

Properties

Properties describe core aspects of the project.

Pricing & Availability

See prices from popular manufacturers for your project.

Controls