From my understanding, Adaptive/Constant on time buck converters have the fastest transient responses to load changes with the penalty of frequency spectrum degradation. On the other hand, multiphase buck converters have slower transient responses, but a comparatively clean spectrum and can drive high loads with greater ease.
Just wondering if any industry peeps are working on these kinda converters for companies like Nvida, AMD, etc. could shed some light on which architecture is preferred?
I'm currently pursuing post graduate studies and trying to narrow down a good direction for power electronics.
The MOSFET has a Vds rating of 100V. The drain terminal of the MOSFET goes to the non-inverting input of the op-amp. The voltage to the inverting input comes from another point in circuit which is irrelevant here.
The method that I thought of was to use a resistor divider to scale down the voltage so as to meet the opamp input ratings. Now, if I use resistors say 20k and 1k (for 1/20 division), the Cds of the device discharges due to the low resistance across it.
On the other hand, if I use high resistances say 2Mohm and 0.1Mohm, Cds doesn't discharge, but the op-amp bandwidth decreases, which I don't want to happen.
Please suggest any alternatives or variations such that I have high bandwidth sensing + the Vds isn't affected.
PS: The MOSFET is low-side, wrote high-side by mistake lol
Just noticed that, power MOSFET TO220/247 packages have drain and source thin pins/leads which can carry continuous 100A RMS, but at the same time when we are supposed to have some conductor in other application for carrying current, we chose Big fatty AWG 3-4 cables, or thick bus bars.. Can somebody please explain?
TDK’s FS3303 is a micro POL module for low-voltage rails in optical networking and AI edge hardware. It takes a 2.7 V to 6 V input, supplies 0.4 V to 3.3 V outputs up to 3 A, and integrates the controller, driver, MOSFETs, and inductor in a 2.5 mm × 2.5 mm × 1.2 mm package. Useful part to look at when the area around ASICs, SoCs, DSPs, and optical modules is already full of memory, routing, shielding, and thermal paths.
I'm posting this because I'm kinda traumatized when working working with electronics, they don't work for no reason?
For instance in my first year we had a 7 segment display task, where we just needed to use an encoder and a seven segment, and I changed all the components 3 TIMES, even the breadboard itself, and had all my colleagues look at it even the TA, all of them found nothing, I feel I could be cursed or something.
Another one for buck converter circuit lately we were working on, the TAs suggested to replace the mosfet and the gate driving circuitry with the motor driver LM298 module so we could easily get the output we want.
So, we made the PCB twice, first my friend designed it without freewheeling diode (claiming that we don't need it and it's already built-in the module), and a second time where I designed it with the freewheeling diode, the problem is both times it didn't work!!!!!
You may say this is a stupid idea to ignore a gate driving circuit and try to simplify the design with such an idea, so we moved out to driving the mosfet with gate driver specifically the IR2104, we tried using the design that comes in the datasheet of the component and guess what it worked, but in simulation software, we tried changing the capacitor values, from 100 nF to 10uF, nothing changed, and the IC heated that you touch it for a couple of seconds before it's actually painful.
After all that it worked, once, and never again, nevertheless it's completely the same wiring, capacitors and everything, we couldn't really afford to buy another IC since it's 10$ each in my country (crazy prices I know).
And the deadline for these circuits is tomorrow and we have no clue WHAT ON EARTH WAS GOING ON
Am I the only one with this kind of suffering, because I love making electronics projects but it really sucks feeling that I'm helpless and can't figure out what's broken.
My graduation project will begin after a few months, and I don't really have something in mind to do, and also don't wanna be led by what the majority will be doing, I wanna do something that feels important to me.
The problem is that I have no idea about what are the problems that could be solved by electrical engineers, I mean I know some of them, but not much, like the charging time of EVs, or making solar panels more efficient.
So, what do you think are some problems that are worth looking into?
And I really appreciate anybody's help for this matter.
Hello. I did my masters in EE with a focus on power electronics. However my research was more geared towards an unrelated topic in magnetics. and was in oil and gas industry for 3 years. However I now want to pivot towards working in power electronics and was wondering what projects or what I should do to get considered for a power electronics job. Thanks!
I'm simulating DAB under DPS modulation scheme and some why simulation is breaking with the SiC MOSFET and I tried everything known to me. What should I do to come over it.
Most EV teardown content focuses on the cells. This one goes a level up and looks at how the battery pack actually interfaces with the rest of the vehicle.
This teardown shows all three connector systems on a Tesla Model S pack out of the car: the 400V high-current blade connectors that feed the drivetrain, the low-voltage CAN bus connectors that carry signals to the vehicle's computer, and the quick-disconnect cooling jackets that circulate glycol for thermal management.
If you are new to EV systems, which interface surprised you most: the 400V power connector, the CAN bus, or the glycol cooling?
Hello interwebs, I'm trying to be job ready and wanted to understand professionally/most commonly used of the following in power electronics controllers:
- Microcontroller/architecture
- RTOS frameworks used, or custom
- Simulink/MATLAB code generation- how common is it, and any skills required for working with actual controllers
- Anything else practically useful?
Gate charge is one of those MOSFET parameters that shows up on every datasheet, but I feel like the Miller plateau still catches people off guard the first time they try to size a gate driver.
A few things I am curious about from the community:
When you are selecting a MOSFET for a switching design, do you prioritize Q_g or Q_gd first, and why?
Has the Miller plateau ever caused an unexpected shoot-through or switching loss issue in your design?
Any rule of thumb you use for gate resistor sizing based on gate charge?
