User manuals, dimensioned drawings, and technical specifications are provided below for the v3 USB-PD chargers. Documents for previous generations can be found at the bottom of the page.


USER MANUAL

The user manual will be available shortly.


DIMENSIONS
CORE CHARGER
Render of USB-PC charger

View Dimensions

AIRCRAFT PANEL MOUNT 2 ¼” / 57mm
Render of 57mm aircraft panel mount adapter plate

View Dimensions

AIRCRAFT PANEL MOUNT 1 ¼” / 32mm
Render of 32mm aircraft panel mount adapter plate

View Dimensions

EXISTING V2 UPGRADE PANEL MOUNT
Render of the v2 to v3 panel mounting adapter plate

View Dimensions


SPECIFICATIONS

Provisional specifications for the dual port units

USB Ports2 x Type USB-C
USB PowerUp to 45 Watts per port.
Adjustable to meet regulatory or aircraft available power restrictions
Max input power consumption7.14A @ 14V input (both ports at 45W)
3.57A @ 28V input (both ports at 45W)
Input votltage14V to 28V nominal, 12V to 32V acceptable
Nominal output voltageUSB Standard 5V, 9V, 15V, 20V
USB PPS supported variable between 5V to 20V
USB Protocol supportUSB-PD 3.2 v1.0
Diagnostic / configuration portUSB-C located on the rear of the charger for diagnostics and configuration
USB Port status indicationPort active and OK, Port fault
Dimensions
Weight
Operating temperature (Celsius)0 – 50
Power input connectorMolex Micro-Fit 3.0
Standards complianceEN 50498:2010

FREQUENTLY ASKED QUESTIONS
What is the diagnostic port for?

The port enables the power output of the charger to altered, setting limits on the power. This is for two reasons:

  1. Some regulatory routes set per-port power limits. To maintain compliance, the ports can be turned down to comply with the requirements. Should they be increased in the future, the ports can simply be turned up as required.
  2. Depending on the amount of available from the aircraft electrical system, power may need to be reduced to ensure the electrical system is not overloaded.

The application used to adjust the power output also gives real time data on the state of each port. It also permits firmware updates to the charger.

What’s wrong with a generic plug-in charger?

The answer depends on the specific unit in question, but broadly, generic plug-in chargers present several common issues in an aviation context: RF interference, poor voltage regulation (particularly under load), limited device compatibility, insufficient safety and protection features, and the risk of device damage as a result of the above.

It is also worth noting that generic chargers are designed for short-term use not extended operation. Prolonged use introduces additional risks.

On the subject of emissions testing, generic cigarette chargers should be tested for radiated emissions, though in practice many have undergone only rudimentary testing, and some have bypassed it entirely. Conducted emissions testing is not required for battery-powered devices, leaving a further gap in oversight.

A particularly common issue is inaccurate power output ratings. A charger rated at 3A, for example, may experience significant voltage drop and fluctuation when approaching that load, often causing overheating. This is compounded when the charger identifies itself to the connected device as a high-power source, prompting the device to draw maximum current – potentially damaging both the device and the charger and creating a hazard in flight.

The fundamental problem is straightforward: these products were never designed for aviation use.

Issues with the uAvionix SkyEcho

Short version

SkyEcho back feeds power onto the USB cable when powered on, against all the USB specifications.  This could damage the equipment it is connected to. Whilst it will not damage our chargers, they will not supply power to a SkyEcho if connected when it is turned on.  They will, correctly, report the connected device as faulty.

Long version

First some very basic USB power notes. The amount of power a device draws is down to the device. It decides how much to try and draw, based on what the charger says it can deliver. Some chargers say they can deliver 2.5A, and they can. Some say they can deliver 1.0A, but they can’t. As the current increases, their output voltage drops. The charger should only advertise what it can physically deliver. The client should only draw what the charger says it can deliver.

As a rule, prior to the USB-C connector, power was ‘simple’, and it was one reason why USB cables had different connectors on each end. The host supplies the power, and the client uses the power. The host (your PC, USB hub, or plug-in charger) has a USB Type-A connector that only connects to a client using a non USB Type-A connector (Mini-B for example). Type-A to Type-A cables are a bad idea, as power can be back-fed to the host. For USB-C, this is no longer a problem, as the power delivery is negotiable. Either side can source or sink power.

For SkyEcho the USB-C port doesn’t look for any kind of specific charger. When plugged in, it will try to draw up to 1A, as that is what the battery charging chip is set to do. Nice and simple, but don’t plug it into anything that cannot deliver 1A. The charger voltage will drop, as it can’t supply the power, or it will overheat. If it is plugged into a USB-C charger, there will probably be no power delivered, as there is no attempt to enumerate/negotiate the level of power required. The charger will, rightly, supply nothing.

It’s more interesting if the SkyEcho is powered on before connecting. When powered, SkyEcho will supply what looks like the battery voltage (less the voltage drop over a diode) from the USB-C port. It can happily* supply at least 0.5 A. After contacting uAvionix, this is because the USB-C port is intended to power some as yet unreleased accessories.

Now, this can cause issues. If the charger does what good chargers should do and checks the power on the attached device, it will see a voltage there. It will then try to discharge the bus, which it will never do as the SkyEcho is powering the USB-C port. The charger may ignore this and turn on the 5V supply. It may say there is a device connected but not turn the power on. It is totally dependent on how the charger handles this ‘error’ condition. A client should not back feed a host. For USB-C PD it is mandated to discharge the bus when switching power levels.

*When I say ‘happily’, I mean it will, up to a point. If you have an iffy USB cable or connect it to something that can draw more power, I suspect the diode or MOSFET feeding it, preventing the USB-C power from going directly into the battery, will probably fail. At 0.5A it was running at ~65 Celsius, with a 25 Celsius rise in a couple of seconds. I suspect a short will simply cause the component(s) to fail. If they fail open, that’s fine, unless this stops the charging lights from working. If they fail short and the cable is not removed, then it will be down to the battery protection to stop bad things from happening unless the PCB tracks or cable fail and break the circuit. There is a lot of power stored in those batteries.