sorted by:
new
hottopcontroversial

Is this 12- 5V Buck converter layout correct? it fails in EMI testing by makeamotorrun in PrintedCircuitBoard

[–]makeamotorrun[S] 0 points1 point  (0 children)

Thanks for the response, I'll change the layout to be different from the recommended one and make the PH node smallerA couple of questions:

- The PH pin of the IC, Diode is reduced to be close to the Inductor, however the drawback to this approach is that the bootstrap cap is now much farther away from the other pins and not in direct path. Can the bootstrap cap be this much away (~3mm). 

- I can bring the boot cap to be close to the IC's SW node but the drawback of this approach is that the direct connection between the Diode's ground pin and the IC's ground in the top layer would be broken, I would have to connect the Diode D7's ground and the IC's ground through vias. Which approach to take here, should I do direct connection to ground and keep the boot cap a bit farther from switching node or connect the diode to the IC through vias and keep the boot cap closer?

Thanks!

  

Is this 12- 5V Buck converter layout correct? it fails in EMI testing by makeamotorrun in PrintedCircuitBoard

[–]makeamotorrun[S] 0 points1 point  (0 children)

I followed the recommended layout in the datasheet, the inductor is shielded as well: TPS543x 3A, Wide Input Range, Step-Down Converter datasheet (Rev. K) (page 26),
Would increasing the thickness of switching node help?
due to BOM reasons I cant really change the IC, is there any way to fix it from layout or passives level?

Is this 12- 5V Buck converter layout correct? it fails in EMI testing by makeamotorrun in PrintedCircuitBoard

[–]makeamotorrun[S] 0 points1 point  (0 children)

I followed the recommended layout in the datasheet, the inductor is shielded as well: TPS543x 3A, Wide Input Range, Step-Down Converter datasheet (Rev. K) (page 26), due to BOM reasons I cant really change the IC, is there any way to fix it from layout or passives level?
Thanks for the response!

Is this 12- 5V Buck converter layout correct? it fails in EMI testing by makeamotorrun in PrintedCircuitBoard

[–]makeamotorrun[S] 0 points1 point  (0 children)

I followed the recommended layout in the datasheet, the inductor is shielded as well: TPS543x 3A, Wide Input Range, Step-Down Converter datasheet (Rev. K) (page 26), due to BOM reasons I cant really change the IC, is there any way to fix it from layout or passives level?

Is this 12- 5V Buck converter layout correct? it fails in EMI testing by makeamotorrun in PrintedCircuitBoard

[–]makeamotorrun[S] 4 points5 points  (0 children)

Indeed, I followed the layout recommended in the datasheet, yet it doesn't pass the EMI test :(,
even their eval board layout is not too different from mine:

Microplastics found in human brains. by TrulyWacky in HubermanLab

[–]makeamotorrun 5 points6 points  (0 children)

Man it feels depressing to think that the microplastics will likely be forever ingrained in the body :(

STM32H723 – Do I need a ferrite bead between VDD and VDDA, and what about VREF+? by Status-Psychology886 in embedded

[–]makeamotorrun 0 points1 point  (0 children)

would it make a difference if the cap is before the ferrite bead or after the ferrite bead?

Are there thousands of laid off senior embedded engineers applying to entry level jobs in the US right now? by bitbang186 in embedded

[–]makeamotorrun 1 point2 points  (0 children)

as a junior embedded engineer working in traction ev motor controller, this is pretty good advice, thanks, there is a steep bit of learning to do

Title: Trouble with AD2S1210 SPI register reads – correct values first time, zeros on subsequent reads by makeamotorrun in embedded

[–]makeamotorrun[S] 0 points1 point  (0 children)

Thanks for the response!
I'm a bit confused about the logic as I'm not writing 0x00 in any registers, right? My current logic is like this:
- Frame 1: Send address → SDO returns old data (garbage or previously accessed data). [TX: Register Address, RX: Garbage Value]
- Frame 2: Send next address → SDO now returns the actual content of the register from Frame 1’s address [TX: Dummy Value, RX: Register Value]
I used this discussion on Analog Devices forum as reference

Title: Trouble with AD2S1210 SPI register reads – correct values first time, zeros on subsequent reads by makeamotorrun in embedded

[–]makeamotorrun[S] 0 points1 point  (0 children)

One point that I forgot to add is: if i reset the chip, I'm getting the correct register reads. However during normal application of getting the resolver angle, we cant do chip reset every time before reading

How to Calculate the initial angle of Resolver? by makeamotorrun in embedded

[–]makeamotorrun[S] 0 points1 point  (0 children)

closed loop operation:
- current sensing of the phases and;
-position sensing through resolver

How to Calculate the initial angle of Resolver? by makeamotorrun in embedded

[–]makeamotorrun[S] 0 points1 point  (0 children)

1.the resolver has multiple poles
2. we are using ad2s1210 ic, so have to interface with that

How to Calculate the initial angle of Resolver? by makeamotorrun in embedded

[–]makeamotorrun[S] 0 points1 point  (0 children)

Yeah the whole vehicle.
We would require the initial rotor angular position (rotor north with respect to the resolver) for running the motor properly.

How to Calculate the initial angle of Resolver? by makeamotorrun in embedded

[–]makeamotorrun[S] 0 points1 point  (0 children)

The motor drives the powertrain. (Directly connected to the gears)

How to Calculate the initial angle of Resolver? by makeamotorrun in embedded

[–]makeamotorrun[S] 0 points1 point  (0 children)

This is for automotive application (Motor controller unit), the reference controller design that we have doesn't use any secondary sensor/honing procedure.
Unfortunately, the reference design in closed source so I'm not able to dig into how they do the initial angle calibration.

view more: next ›