USB Power Delivery giving you trouble? Start from a design that already works.
We adapt our proven USB-C PD design to your product, with power negotiation, charge-through and data role swap. Already have a design that fails? We find the cause and fix it.
We start from a USB-C PD design we built and proved in a 2022 project. It covers the parts that usually cost the most time:
Power negotiation: The design negotiates with USB-C PD chargers and passes the right power profile to your device.
Charge-through: Your device charges from the charger while it stays connected to a host or hub.
Data role swap: The device switches between host and device roles while it keeps charging.
Restart recovery: Newer tablets and phones drop the power contract when they restart. We know how to get them charging again.
Microchip PD controllers: The design runs on UPD301C and UPD350, with schematic and firmware to adapt.
Specify: We agree on the power levels, data needs, connectors, and the chargers and devices you must support.
Adapt: We fit our schematic and firmware to your board, your enclosure, and your feature list.
Verify and hand over: We build prototypes and test them with real chargers and devices. You get the design files, the source code, and a test report.
A PD fault rarely has one cause. Firmware, hardware, and the connected device all play a part. These are the causes we see most often:
Stack settings: Wrong voltage limits in the PD stack trigger power faults. The port shuts down right after a device attaches.
Device behavior: Newer tablets and phones drop the power contract when they restart. A fixed-function PD chip cannot recover without a manual port reset.
Board errors: A single pin wired to the wrong net can block a PD controller. Every sample carries the same fault.
Chip changes: Moving from a fixed-function PD chip to a configurable controller means your team now writes the negotiation logic.
No visibility: Without logs or a protocol analyzer, the team guesses. Each guess costs a week.
We fix it in three steps:
Diagnose: We review your schematic and capture the PD traffic on your hardware. We tell you whether the fault sits in firmware, on the board, or in the device behavior.
Fix: We change the PD stack setup, the power profile mapping, and the recovery logic. If the board has an error, we give you a rework your team can apply to existing samples.
Verify: We test with real chargers and your target devices. You get the binaries, the source code in your repository, and a short test report.
A US maker of rugged vehicle docks found us through our USB-C PD design guide. Their new iPad Pro dock lost charging every time the tablet restarted, and their end customer was waiting.
We found a board error that affected every prototype and gave their team a rework. Then we fixed the PD stack setup and wrote firmware that renegotiates power after a restart.
Result: The dock now restores charging after every iPad reboot. We tested it with four chargers from 20 W to 100 W.
You are building a new product. Start with a scoping call. We walk you through our PD design and agree on what to adapt. Within a few working days you get a proposal with scope and timeline.
You have a design with a PD problem. Start with a diagnosis. You send the schematic, two boards, and your target device. Within a few working days you get a written report with the root causes and a fix plan. If you go ahead, we apply the fix. If you fix it in-house, the report is yours to keep.
German contract. You sign with Oxeltech GmbH in Berlin. NDA first, then work.
US and EU clients. We run weekly calls across time zones and share code through your repository.
PD experience. We have built PD charge-through designs with data role swap on Microchip UPD301C and UPD350 controllers since 2022.
One team for firmware and hardware. We find board errors during firmware work, so you avoid a second supplier.
Related reading: Design guide on USB-C PD with data role swap