NFC RFID Testing Device


Thought for 1 min 10 sec
Thought for 7 sec
Referenced guidance.
1/5 Extract subsystem requirements and candidate constraints from project files
Thought for 19 sec — Delegating Executors
Created 2 threads
RFID front-end research
Starting...
View Thread
MCU security charger research
Starting...
View Thread
Thought for 7 sec
Reading "project-specification" project doc.
Reading "mechanical-stack-up-budget" project doc.
Thought for 6 sec
2/5 Research NFC and 125 kHz RFID front-end candidates

Extract subsystem requirements and candidate constraints from project files

Research NFC and 125 kHz RFID front-end candidates

Research BLE MCU, secure element, and charger candidates

Verify electrical, package, firmware, and sourcing compatibility

Document selected parts, alternatives, and unresolved risks

Thought for 9 sec
Awaiting 1 background task
Received notification from "RFID Front Ends" that it finished — picking the work back up.
Requirements and mechanical/power constraints were extracted, and both RF-front-end and MCU/security/charger research executors completed. I cannot retrieve and reconcile their reports because no ACUs remain; final part selection, compatibility verification, Flux-library checks, and the persistent component-selection report are still pending.
Received notification from "BLE MCU Secure Parts" that it finished — picking the work back up.
Both component-research sub-threads have completed, but their reports have not been reconciled into a verified chipset selection. With no ACUs currently available, I cannot inspect those reports or create the final BOM; remaining work is cross-checking supply rails, interfaces, RF modes, package heights, current budget, lifecycle, and Flux-library availability, then documenting the selected parts.

Waiting for input

No schematic yet

Talk to Flux to get started.

Battery Options and Standby Budget
Scope
Preliminary battery comparison for an authorized, wallet-format NFC/RFID test instrument using BLE and motion-triggered wake. The estimates are architectural, not final: the NFC and 125 kHz reader front ends, antenna tuning, BLE duty cycle, and exact cell protection leakage must be measured on the prototype.
Candidate rechargeable cells

Table


CandidateNominal sizeCapacityStrengthsMain concerns
NGK EnerCera EC382704P-T38 × 27 × 0.45 mm24 mAh at 4.2 V; 27 mAh at 4.3 VBest verified thin format; 560 mA specified peak capability; suitable for short RF/BLE burstsSpecialty sourcing; unusual 3.8 V chemistry; charger must match selected 4.2/4.3 V limit
NGK EnerCera EC382704P-Hr38 × 27 × 0.45 mm20 mAhExtremely thin; 130 mA peak supports a carefully power-managed designLower capacity and peak margin than P-T
LNC LNC05172323 × 17 × 0.5 mm12 mAhVery small; published charge/discharge and cycle dataMaximum discharge only 12 mA, likely inadequate for simultaneous RF and BLE peaks without a buffer capacitor; protection status unclear
PowerStream PGEB00422550.4 × 22 × 55 mm25 mAhThinnest listed off-the-shelf conventional pouch optionMaximum current and protection details not published; long narrow shape competes with antenna area
PowerStream GM00865350.8 × 65 × 35 mm50 mAhPublished 500 mA peak; good capacity and realistic prototype availability0.8 mm cell alone makes a sub-1.5 mm finished card difficult
PowerStream PGEB00845450.8 × 45 × 45 mm100 mAhHighest capacity among credible sub-1 mm options foundLarge central area blocks routing/antenna space; peak current not published
PowerStream PGEB01043481.0 × 43 × 48 mm130 mAhStrong runtime and purchasable in engineering quantitiesFinished assembly likely exceeds the desired wallet-slot thickness
Cymbet EnerChip CBC050SMT solid-state cell0.05 mAhReflowable and robustCapacity is orders of magnitude too low for active RFID/BLE operation; not suitable as primary energy storage
Vendor-listed pouch dimensions and capacities require sample verification. Ultra-thin pouch cells are commonly custom or semi-custom, may have minimum order quantities, and may not include protection. Cell swelling allowance, tab thickness, lamination, adhesive, and local PCB/component stack height must be included in the mechanical envelope.
Standby architecture assumption
The only always-powered blocks should be:

Table


Always-on loadEstimated current
BMA400 motion detection in ultra-low-power mode0.8 µA
BLE MCU in system-off with GPIO wake0.3 µA
Battery protection, charger reverse leakage, and power switches1.0 µA budget
Divider leakage, pull resistors, capacitor leakage, margin0.4 µA
Estimated electronic standby total2.5 µA
Both RFID front ends should be disconnected by low-leakage load switches while asleep. A continuously polling NFC or LF receiver would destroy multi-week standby.
Standby consumption is approximately:
2.5 µA × 24 h = 0.060 mAh/day
Motion-triggered use model
A representative wake event is modeled as 10 seconds at an average 15 mA battery current. This covers MCU startup, a short RF scan, and BLE transfer, but not sustained high-power card emulation or long write operations.
15 mA × 10 s / 3600 = 0.0417 mAh per event
Runtime uses 70% of nominal capacity to allow for temperature, aging, cutoff, conversion losses, and capacity-rating uncertainty. Calendar self-discharge is not included, so long standby-only figures are optimistic.

Table


Cell capacityUsable budgetSleep only5 events/day20 events/day
12 mAh8.4 mAh140 days31 days9 days
24–27 mAh16.8–18.9 mAh280–315 days63–71 days19–21 days
50 mAh35 mAh583 days131 days39 days
100 mAh70 mAh1,167 days261 days78 days
The event rate dominates practical runtime. For example, a 27 mAh cell uses only 0.06 mAh/day asleep, but five ten-second sessions add about 0.208 mAh/day.
Sensitivity to active session duration
For a 27 mAh cell with 18.9 mAh usable capacity:

Table


Usage patternAverage daily consumptionEstimated runtime
Standby only0.060 mAh/day315 days before self-discharge correction
5 × 10 s sessions/day at 15 mA0.268 mAh/day71 days
5 × 30 s sessions/day at 15 mA0.685 mAh/day28 days
20 × 10 s sessions/day at 15 mA0.893 mAh/day21 days
10 minutes/day active at 15 mA2.56 mAh/day7 days
Recommendation
Use the NGK EnerCera EC382704P-T class (0.45 mm, approximately 24–27 mAh) as the preferred thin-card target because it combines verified thickness with enough pulse capability for RF and BLE bursts. Use the 0.8 mm, 50 mAh GM0086535 as the lower-risk proof-of-concept alternative if obtaining EnerCera samples or a compatible charging solution delays development.
Design goals:
  • Target 2.5 µA electronic standby; set a hard maximum of 5 µA after measurement.
  • Power-gate both RFID front ends and any antenna-tuning switches.
  • Buffer radio/RF current pulses with low-profile bulk capacitance after verifying cell ESR.
  • Use edge-pad charging and a charger selected for the cell's exact maximum voltage.
  • Avoid a continuously running fuel gauge; estimate state of charge periodically from voltage unless testing proves a gauge's leakage acceptable.
  • Validate battery safety documentation, protection requirements, cycle life, bend restrictions, swelling allowance, and minimum order quantity before freezing the PCB outline.
Sources
  • Scope

  • Candidate rechargeable cells

  • Standby architecture assumption

  • Motion-triggered use model

  • Sensitivity to active session duration

  • Recommendation

  • Sources