This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LM5106: PWM signal into ENable rather than IN pin

Part Number: LM5106
Other Parts Discussed in Thread: LM5109, LM5111

Compared to the LM5106, the LM5109 has two inputs - one for low side and one for high side. This means that it is "easily" possible to achieve three different drive options with the LM5109 : only drive the Low Input, only drive the High Input and possibly (with dead time added - which may not be quite as "easy") drive both. In essence, the LM5109 can be used as a Low Side, High Side and Half Bridge driver, it's just down to how you configure the signal source.

As an example of how and when this could be useful, consider for a moment a load which is connected to something other than the half-bridge's VBUS - you may want to control the Low Side transistor of the half bridge, and you may be happy for the load (if inductive) to fly back up to VBUS (forward biasing the high side transistor's body diode). What you do not want to do, though, is to force the controlled end of the load up to VBUS when it should be "off". Moreover, even if it was OK to drive that side of the load up to VBUS, at 100% HS duty you would eventually discharge the bootstrap cap - you would need to cycle the output to recharge it and you may not want (or be allowed) to.

In contrast, when used in its intended way, the LM5106 can only act as a Half Bridge driver [so long as it is ENabled, either HO or LO will be on] - it "could not" be used as per the example above, since you never want to turn on the high side transistor (content with it acting as a flyback diode to VBUS). This then begs the question : would it be "permissible" to reverse the allocation of the ENable and IN pins ? [In case someone is wondering "why not use an LM5111 if you only need low side drive?", consider flexible hardware which is not application specific and/or where you cannot predict what sort of load you will need to drive, ergo the output stage must cope with as many scenarios as is realistically feasible].

Using the same situation as above, we see we need to generate an LS PWM signal and we do not want to drive the HS. This is easily achievable by driving IN to 0 (so LM5106 will drive the LO) and then applying the PWM signal to the EN pin. There will be around 36ns of delay as per datasheet both on turn on and off, so it won't distort the applied duty. It doesn't need to worry about dead time because the IN pin will not be changing in this drive mode.

It would appear, at least per the information in the datasheet, that an LM5106 can do "everything" an LM5109 can but better in one regard - the signal source does not need to insert dead time. That can be of some benefit where adding such dead time is hard / computationally expensive or impossible in the signal source. Whilst this potential drive paradigm still requires two PWM capable pins, it sacrifices the ability to change the dead time in the signal source (if the source is even capable of that) for the ability to drive a half bridge without needing to add the dead time at the source.

My question here is whether anyone can see any reason why this would not work ? The datasheet doesn't consider this drive paradigm (understandably so) yet states nothing that suggests it wouldn't work. The Simplified Block Diagram looks like it should work. But a Simplified Block Diagram is just that, and may not cover nuances which would preclude this drive method.

Best regards,

Patrick Herborn.

Appendix : For full bridge operation with 2 LM5106s it is still possible to pre-charge the bootstrap caps by doing a single cycle with both INs at 0 and ENabled. When using only one LM5106 switching only the high side, the ground connected load would provide the charge path for the bootstrap anyway.



  • Hi Patrick,

    Thanks for reaching out.

    Switching the EN while IN is low may in theory generate the PWM signal on the low-side LO according to the device functional mode Table in the datasheet. However, I would caution that EN specifically the logic stage is meant to be used in continuous High or low state to put the device in low power mode or enabling the outputs. You application may work and you may certainly operate the device so long as the signals are within the recommended operating conditions but this pin is not intended for continuous switching in the datasheet.

    Regards,

    -Mamadou     

  • Hiya Mamadou,

    Many thanks for looking at this and coming back to me!

    You make a very good point that is not at all obvious from the Simplified Block Diagram (reaffirming my caution about drawing conclusions from it) - that the ENable pin does more than just turn off both outputs - it puts the device into a low power state. That does beg the question about what constitutes a low power state, and how expectations from that align with what Figure 1 on page 6 of the datasheet shows.

    One might expect that a low power state means that no output is driven - the device outputs are likely totem poles and if neither the pull-up nor the pull-down of the totem pole is asserted then one could conclude that is a "low power state". That gave me concern regarding what happened when ENable is de-asserted - "what if a power transistor gate had charge on it and then the outputs went Hi-Z ?"

    Fortunately, Figure 1 suggests that the device does not simply go Hi-Z when not ENabled [it would be bad if it did]. If we look at the final part of the waveform in Figure 1, we see two instances where ENable goes from high to low. In both cases - be that with IN at 0 or IN at 1 - after a period of t_sd the outputs go Low (not HiZ, that state never seems to be shown at all). Indeed the datasheet specifically states "LO and HO are held in the low state when EN is low" - but it does also state "Enable Pin - Reduces operating current when disabled to improved power system standby power".

    Sounds like the best way to figure this out is to actually try it and see what happens!

    Many thanks,

    Patrick Herborn.

  • Hello Patrick,

    If you try this operation approach, let us know if there are any additional questions on the operation.

    Regards,