Document Overview
TL;DR Our camping lanterns with bidirectional USB-C PD deliver up to 18W input for charging the internal battery and up to 10W output for charging external devices — all through a single port. Understanding how the power management circuit handles simultaneous operation determines whether you…
- Document type
- Certification Report
- Prepared by
- Ryan Cooper
- Published
- Last reviewed
- Topics
- Camping Lanterns
TL;DR
Our camping lanterns with bidirectional USB-C PD deliver up to 18W input for charging the internal battery and up to 10W output for charging external devices — all through a single port. Understanding how the power management circuit handles simultaneous operation determines whether you leave a device dead at basecamp or not.
Bidirectional USB-C PD: How One Port Does Two Jobs
USB-C Power Delivery is a negotiated protocol, not a fixed voltage rail. When you plug a charger into our lantern’s USB-C port, the port controller negotiates input — up to 18W (9V/2A) — and routes current to the battery management IC. When you plug a phone or GPS into the same port, the controller switches to source mode and outputs up to 10W (5V/2A). The hardware arbitration happens at the port controller level in under 100ms, which is fast enough that most devices never notice the handshake.
We chose bidirectional USB-C PD over a two-port design (separate in/out ports) for a specific reason: field use punishes complexity. Every additional port is another entry point for moisture, sand, and debris. A single USB-C port with a rated IP54 dust/splash seal is substantially more durable than two separate ports each requiring its own protective cover. Fewer connectors also means fewer failure points in the enclosure gasket.
The USB-C PD specification is maintained by the IEC Standards body under IEC 62680-1-2. Our lantern’s port controller is certified to this standard, which governs voltage negotiation, current limits, and fault protection behavior.
For a deeper look at how we size battery capacity against runtime demands in our lantern line, see LED Lumen Output vs Runtime: Engineering the Tradeoff in Portable Camping Lanterns.
Battery Management Architecture During Simultaneous Operation
The most technically demanding scenario is this: the lantern is illuminating a campsite at mid-brightness, a phone is charging from the USB-C output port, and the lantern itself is connected to a solar panel or wall adapter via USB-C input. Three simultaneous power flows — LED driver load, device output load, and battery charge input — all managed by one battery management IC.
We engineered this with a power path management topology rather than a simple linear charge controller. In power path mode, input current goes directly to the load first, with residual current allocated to battery charging. This means a connected phone charges at full 10W even when the battery is at 20%, because the 18W input covers the 10W output plus 8W toward battery recovery. If input is removed, the battery seamlessly takes over without a glitch or reset to connected devices.
The thermal behavior here required careful validation. During simultaneous operation testing — 18W input, 10W output, LED running at 200 lumens, at 40°C ambient — the battery management IC junction temperature peaked at 78°C after 90 minutes of continuous operation. Our thermal throttle threshold is set at 85°C, so normal summer camp use with all three loads active stays within margin. At 50°C ambient (worst-case desert or vehicle interior), we recommend disconnecting the device charge output if the lantern will run continuously for more than 2 hours.
The FCC requires that USB-C devices operating as power sources meet conducted emissions limits under Part 15B. Our lantern passes this at the 10W output level, meaning it won’t generate RF interference that disrupts a nearby ham radio or emergency beacon — a genuine concern in backcountry camp setups.
Input Charging: 18W PD and Charge Time Across Sources
At 18W input (9V/2A PD), a fully depleted 10,000mAh internal battery charges to 80% in approximately 3.2 hours and reaches 100% in approximately 4.5 hours. These figures assume the lantern is off during charging. With the lantern running at low mode (approximately 50 lumens, ~2W LED draw), add roughly 20 minutes to the full charge time.
Not all USB-C chargers support PD negotiation. A standard 5V/2A USB-C charger — common with older phones — will charge the lantern at 10W instead of 18W, extending full charge time to approximately 7 hours. The port controller handles the downgrade gracefully; there’s no damage, just slower charging. We recommend verifying your field charger supports USB Power Delivery if charge time matters to your itinerary.
Solar input via USB-C is viable with any panel that outputs regulated 9V or 5V USB-C. Unregulated or variable-output solar panels can confuse the PD handshake and drop to minimum charging current. If using solar, choose a panel with a built-in USB-C PD controller, not a bare panel with a USB-C pigtail.
The IEC Standards IEC 62133 standard governs the safety of the lithium-ion cells inside the lantern, including overcharge, overdischarge, short circuit, and thermal abuse tests. Every cell batch we source is validated against this standard before it reaches our assembly line.
Output Charging: 10W Performance and Device Compatibility
The 10W USB-C output (5V/2A) covers the majority of field-use devices: smartphones (virtually all current models fast-charge at 18W or less from a compatible charger), GPS units, headlamps with USB-C inputs, satellite communicators, and small Bluetooth speakers. It will not deliver enough power to meaningfully charge a laptop — USB-C laptops typically require 45W or more — but it will maintain a laptop at low-power idle or charge it very slowly overnight.
One compatibility note worth flagging: some devices negotiate USB PD and expect a 12V or 20V profile if they don’t see 5V fast-charge acknowledgment. Our output port is fixed at 5V/2A and does not offer a 12V or 20V output profile. This is a deliberate constraint — supporting higher output voltages on a 10,000mAh cell would require a boost converter that adds cost, weight, and thermal load disproportionate to the use case. A camping lantern is not a laptop power bank, and we didn’t engineer it to pretend otherwise.
For reference on how our portable inflation products handle battery output architecture under load, the same power-path principles apply — see Portable Tire Inflator Battery Technology: Lithium-Ion Cell Configurations.
Output port overcurrent protection triggers at 2.2A (10% above rated 2A), with a 200ms response time. Short circuit protection responds in under 50ms and requires device disconnect/reconnect to reset — it does not auto-retry, which prevents sustained current into a faulted cable or connector.
The RoHS directive compliance of our lanterns ensures the battery cells, PCB, and USB-C connector assembly are free of restricted substances including lead, cadmium, and hexavalent chromium — relevant for B2B partners selling into the EU market.
Charge State Indicator and User Feedback
The battery indicator on our lanterns uses a 4-LED dot array rather than a percentage display. This was a deliberate tradeoff: a percentage display requires a fuel gauge IC with coulomb counting, which adds ~$0.80 to BOM cost and draws a small continuous quiescent current (~50µA) even when the lantern is off. For a product that may sit in storage for 3-6 months between uses, that quiescent draw matters.
The 4-LED system maps to four charge bands: >75%, 50–75%, 25–50%, and <25%. Each LED also blinks when the lantern is actively charging — a slow blink at 1Hz for normal charge rate, and a fast blink at 4Hz when thermal throttling is active. If all four LEDs blink simultaneously at 4Hz, that’s the fault indicator: overcurrent, overtemperature, or cell protection event. In our field testing, this condition was most commonly triggered by third-party cables with resistive damage that caused voltage drop and confused the PD handshake.
Comparison: Charging Modes and Power Levels
| Scenario | Input Source | Effective Charge Rate | Notes |
|---|---|---|---|
| USB-C PD 18W charger, lantern off | 9V/2A PD adapter | 18W — full charge ~4.5 hrs | Fastest charging mode |
| USB-C standard 5V/2A charger | 5V/2A non-PD | 10W — full charge ~7 hrs | No PD negotiation required |
| Solar panel with USB-C PD controller | 9V/variable | 9–18W depending on irradiance | Regulate panel output for best results |
| Lantern charging phone (output) | Internal battery | 10W output (5V/2A) | Runs from battery; lantern off extends runtime |
| Simultaneous: input 18W + output 10W | 9V/2A PD adapter | Net +8W to battery | Power path topology; phone charges at full rate |
| Simultaneous: input 10W + output 10W | 5V/2A adapter | Net 0W to battery | Battery neither charges nor depletes |
Maintenance & Best Practices
Keep the USB-C port covered when not in use. Even with IP54 rating, repeated exposure to campfire particulates and fine sand degrades the connector contact surfaces over time. We include a silicone port cap for this reason — use it.
Inspect the USB-C cable before each trip. The most common field failure we see is cable insulation damage at the connector bend point, which creates a high-resistance connection that throttles charging to well below rated power. A damaged cable also generates heat at the connector, which triggers the lantern’s thermal protection and shows as a fast-blink fault indicator.
Store the lantern at 40–60% charge if it will sit unused for more than 30 days. Lithium-ion cells stored at full charge experience accelerated calendar aging. At 50% state of charge, cell degradation rate drops by roughly 30% compared to 100% storage — a meaningful difference over a product lifetime.
Charge the lantern fully before any extended trip. A 10,000mAh cell at 20% gives you approximately 8 hours of low-mode runtime, not the 40+ hours available from a full charge. Running a pre-trip charge check takes 30 seconds and eliminates the most common cause of “lantern died” complaints we receive from users.
Do not charge the lantern in ambient temperatures below 0°C. Lithium-ion cells should not be charged below freezing — this causes lithium plating on the anode and permanently reduces capacity. The BMS in our lanterns will block charge current below 0°C automatically, but a better practice is to warm the lantern before connecting a charger in winter conditions.
Frequently Asked Questions
Q1: Can I charge my phone from the lantern while the lantern is also charging from a wall adapter?
A: Yes. The power path management circuit supports simultaneous input and output. At 18W input and 10W output, the battery still receives a net 8W of charge current — your phone charges at full rate while the lantern battery recovers at the same time.
Q2: What’s the difference between a USB-C PD charger and a regular USB-C charger for this lantern?
A: A USB-C PD charger negotiates 9V/2A (18W) with the lantern’s port controller, cutting full charge time to approximately 4.5 hours. A standard 5V/2A USB-C charger delivers only 10W and takes approximately 7 hours for a full charge. The lantern accepts both — PD is faster, not required.
Q3: Will the lantern charge a USB-C laptop?
A: It will provide 10W (5V/2A), which is enough to keep a low-power laptop from depleting during light use or charge it very slowly overnight. It cannot deliver the 45–100W that laptops require for normal operation or fast charging. We engineered the output for smartphones, GPS units, and similar field devices.
Q4: What certifications apply to the USB-C charging system?
A: The USB-C port controller is certified to IEC Standards IEC 62680-1-2 (USB PD specification). The battery cells meet IEC 62133 for lithium-ion safety. The product meets FCC Part 15B for conducted emissions, and the full assembly carries RoHS compliance for EU market sales.
Q5: The fault indicator (all 4 LEDs blinking fast) triggered during charging — what caused it and how do I reset it?
A: The most likely cause is a damaged or high-resistance USB-C cable creating a voltage drop that confuses the PD handshake, or a brief overcurrent event. Disconnect the cable, wait 10 seconds, and reconnect with a known-good cable. If the fault indicator returns immediately with a different cable, the issue is likely a thermal event — let the lantern cool for 20 minutes in a ventilated area before retrying. Persistent fault indication after cooling with a good cable warrants a warranty claim.
Published by ETENWOLF Technical Team | Request a quote