It’s 7:30 a.m., and the site access window you waited three weeks for is finally open. Your tech plugs a DuraForce Pro 2 into a USB-C power bank, launches the EXFO testing app, and starts recording a trace list. The battery icon is still dropping. By the time the EXFO OTDR tester finishes the measurement, the controller shuts down (ugh, again). On the last one we had, the tech pulled the USB cable, ran to the truck, and charged it for fifteen minutes before driving back. That was the good ending.
I manage the field equipment budget for a 120-person telecom services company, and I’ve tracked every hardware order for the past six years. So when I say the problem isn’t the battery, I mean I’ve seen the same failure across three different batches. The equipment wasn’t broken. The setup was underspecified, and nobody caught it before the PO was signed.
The Surface Problem: It Looks Like a Battery Issue
The visible symptom is simple: the DuraForce Pro 2 dies while plugged in. That triggers a whole chain of guesses. The first guess is a defective battery. The second is a weak charger. The third is a “bad” USB cable. Then someone searches for “USB power delivery while recording list” and lands in a forum still arguing about wattage.
“It says USB Power Delivery. I plugged it in. Why is it dying?”
I get it. But that question hides the real one.
The Deeper Problem: USB Power Delivery Is a Negotiation, Not a Promise
Here’s something vendors won’t tell you: “supports USB Power Delivery” doesn’t mean “supports it while the screen is on, the app is running, and the trace list is recording.” It means the port can negotiate a higher voltage, usually in a quiet state. Under load, the device manages heat and power carefully. The charging IC can throttle input current to protect the battery and the CPU. Plus, the device is also recording the trace list to memory and refreshing the screen, which draws power at the same time.
People think if a phone charges at 18W, it will charge at 18W no matter what. Actually, that rating is a ceiling, not an average. When the screen is on and the EXFO testing app is recording, the phone can consume more than the charging profile provides. The result is a net drain even though it’s “charging.”
When I compared the spec sheet for our first batch of DuraForce Pro 2 devices with the actual behavior under our test load, I finally understood why the failure was so consistent. The sheet listed Power Delivery 3.0. It did not list “continuous charging while recording a list.” No one asked, because no one thought to ask. That gap cost us a two-day outage.
The manufacturer’s own support page for the DuraForce Pro 2 (accessed January 2025) lists a USB-C port with Power Delivery. It does not state that the port maintains full charging speed while the display is on and an app is actively recording. That is not a documentation bug. It’s a clue that this use case has to be validated, not assumed.
The Real Cost: It’s Not the Device, It’s the Do-Over
I still kick myself for not adding a thirty-minute screen-on power test to our acceptance checklist. If I’d done that, we would have caught the problem before a single technician lost time on-site. Instead, we saw it in the worst place: a customer’s window.
In Q2 2024, one of these failures turned a simple EXFO testing run into a second truck roll. The access window alone was $600. The technician’s overtime was $340. The customer had to reschedule, which came with a $450 project delay charge in our contract. That one dead controller cost us $1,390, all because the field device couldn’t keep up while plugged in. The first failure was a red flag; the second was a trend.
Here’s the accounting problem. Our capital budget saw a $200 difference between the cheaper controller and the fully specified one. Our operating budget saw the $1,390 do-over. Those are different spreadsheet tabs, so nobody connected them. That’s how hidden costs work.
I’ve learned to ask “what’s not included” before “what’s the price.” If a vendor quotes a device without a power-under-load test, without a supported PD adapter, and without a stated charging profile, the quote isn’t lower. It’s incomplete.
I have mixed feelings about “field-ready” bundles. On one hand, they save procurement time. On the other, a bundle can hide the weak link—the cable that works in the office but not in a hot van. I’ve stopped approving bundles until I see the power specs.
The Fix: Stop Asking “How Do You Reset a Phone”
When these failures happen, the next search is usually “how do you reset a phone.” Here’s the honest answer: a hard reset might get you through the day, but it does not change the power profile. On a DuraForce Pro 2, a hard reboot is typically Power + Volume Down held for 20-30 seconds. A factory reset is under Settings > System > Reset, but that should be the last resort—after you back up the test logs. If you’re resetting the device to fix charging, you’re treating the symptom. The device resets fine. The power budget is still wrong.
What I’d Rather Do: Set the Acceptance Criteria Before the PO
If you’re buying a field controller for EXFO testing, the fix is not a more expensive device. It’s a more honest specification. Add these four lines to the next quote request:
- The device must maintain a net positive charge while the screen is on, the EXFO testing app is running, and a trace list is recording.
- The kit must include a USB-C Power Delivery charger and power bank that are tested and documented for that exact use case.
- The vendor must state the minimum input wattage under continuous load, not just the peak charging rate.
- The acceptance test must include a 20-minute recording session on battery and a 20-minute recording session while plugged in.
Then, when the vendor answers, get it in writing (note to self: add this to the next RFP template). The vendor who lists all the requirements upfront—even if the total looks higher—is usually the one who costs less at the end. That’s not a slogan. That’s my TCO spreadsheet talking.
Bottom line: the EXFO OTDR tester is solid. The weak link is the device that runs the app, and the weak link is only as strong as the power assumptions we make before we buy. Add the test, document the spec, and stop resetting phones on customer sites.
