IoT Fire Alarm Device Design


You should ask Quectel / supplier for the EC25MXGA hardware design package, not just the marketing datasheet.
Ask for:
  1. EC25MXGA Hardware Design Guide
    • Full pin descriptions
    • Power supply requirements
    • PWRKEY / RESET timing
    • UART / USB / SIM / RF reference circuits
    • VDD_SDIO usage guidance
  2. Recommended PCB land pattern / footprint
    • Pad dimensions
    • Pad numbering
    • Paste mask / solder mask recommendations
    • Keepout zones under/around the module
    • Assembly notes
  3. Reference schematic
    • VBAT_RF / VBAT_BB decoupling
    • SIM socket wiring
    • Antenna matching / ESD
    • Status pins
    • Power-on/off sequence
  4. RF layout guidelines
    • 50 Ω antenna routing
    • Ground stitching via recommendations
    • Antenna connector/matching network placement
    • Diversity/GNSS pins if used or unused
  5. Certification documents
    • RCM / ACMA / AS/CA S042 relevance
    • Carrier approval info for Australia
    • LTE band support for AU carriers
    • Test reports if available
  6. Lifecycle / supply confirmation
    • Active production status
    • Recommended replacement if EC25MXGA is not preferred
    • Minimum order / lead time
Short message you can send:
We are designing a dual-modem Australian fire alarm signalling device using 2 × EC25MXGA. Please provide the EC25MXGA hardware design guide, recommended PCB land pattern/footprint, reference schematic, RF layout guide, SIM interface recommendations, VDD_SDIO connection guidance, Australian carrier/certification documentation, and lifecycle/supply status.
Ok I’ll contact them
Good plan. Ask them specifically for the hardware design guide + recommended PCB land pattern for EC25MXGA-128-SNNS.
Until we get that, the safest path is:
  • Keep EC25MXGA in the design.
  • Do not send the PCB to manufacture yet.
  • Continue with placement/routing cleanup only as a draft.
  • Finalize modem footprint, SIM wiring, RF layout, and VDD_SDIO treatment once Quectel confirms the official guidance.
Clean draft layout
Review EC25 wiring
Check power budget
Update factory checklist
Run current checks

Regulatory / Compliance Starting Notes
Product class
The stated product is a UL-listed fire alarm signaling device. This is a safety-critical/life-safety product and must be designed with certification planning from the beginning.
Likely compliance areas to confirm
  • UL fire alarm/signaling standard and listing category
  • NFPA 72 installation/use assumptions
  • FCC/ISED intentional radiator requirements for cellular modules and antenna ports
  • PTCRB/carrier approval implications for Quectel EC21-AUV integration
  • Surge, ESD, EFT, conducted/radiated emissions, and immunity levels
  • Power backup and fault reporting requirements
  • Supervised input requirements and trouble/fault detection behavior
  • Creepage/clearance/isolation requirements for field wiring, modem coupling, and external ports
Design-risk flags
  • Dual cellular modules and dual antennas require careful RF layout, grounding, SIM ESD, keepouts, and antenna separation planning.
  • Fire alarm inputs likely need supervision, current limiting, transient protection, and defined fail-safe fault behavior.
  • USB-C should be service/programming-only unless power-source behavior is explicitly required and certified.
  • Exact LCD interface strongly affects STM32 pinout, memory bandwidth, power budget, and PCB routing complexity.
Required external review
Before production or certification submission, engage a qualified UL/fire alarm compliance lab or consultant. Flux schematic/layout work can support the design, but cannot certify the product.
  • Product class

  • Likely compliance areas to confirm

  • Design-risk flags

  • Required external review