u/Volcano_Dragon13

What this board does

This PCB is only a "power module".

Its job is to:

1. USB-C power input
2. Singlecell Li-ion battery charging
3. 3.3V power generation
4. Battery/USB power switching
5. Provide power and USB signals to another PCB through board-to-board connectors.

The second PCB (which will stack on top of this one) will contain:

1. ESP32
2. OV2640 camera
3. 2.8" LCD
4. MIC

In the final product these will likely become one combined PCB, but for now I'm separating the power section so I can validate it independently.

My main concern

The USB D+ and D- lines have to travel a relatively long distance and change layers using vias because they need to reach the stacking connector.

1. Are the vias on D+/D- a concern?
2. Is the routing length excessive?
3. Should I change the connector placement instead?

Since this is my first PCB, I'd also appreciate comments on:

• Power routing
• Ground plane implementation
• Thermal considerations
• Placement of switching regulator and charger components
• Decoupling capacitor placement
• Return current paths
• Any obvious EMI issues
• Manufacturability
• Anything that immediately looks "wrong"

im attaching the image of top bottom individual and together tracks and also about the usb data lines highlighted pcb tracks images, and actual pcb 3d images...

Thank you :D

What this board does

This PCB is only a "power module".

Its job is to:

1. USB-C power input
2. Singlecell Li-ion battery charging
3. 3.3V power generation
4. Battery/USB power switching
5. Provide power and USB signals to another PCB through board-to-board connectors.

The second PCB (which will stack on top of this one) will contain:

1. ESP32
2. OV2640 camera
3. 2.8" LCD
4. MIC

In the final product these will likely become one combined PCB, but for now I'm separating the power section so I can validate it independently.

My main concern

The USB D+ and D- lines have to travel a relatively long distance and change layers using vias because they need to reach the stacking connector.

1. Are the vias on D+/D- a concern?
2. Is the routing length excessive?
3. Should I change the connector placement instead?

Since this is my first PCB, I'd also appreciate comments on:

• Power routing
• Ground plane implementation
• Thermal considerations
• Placement of switching regulator and charger components
• Decoupling capacitor placement
• Return current paths
• Any obvious EMI issues
• Manufacturability
• Anything that immediately looks "wrong"

im attaching the image of top bottom individual and together tracks and also about the usb data lines highlighted pcb tracks images, and actual pcb 3d images...

Thank you :)

They are doing this drama of e85 Flex fuel to hide this, bcz e85 have at least 5 years to become normal fuel.. bcz all city busses police vehicles and local vehicles are not e85 compatible... But like how they forced e20 on petrol vehicles. Now they will do the same with e20.. they will push e25 and more on e20 vehicles... Studies already began.

Hello everyone,

I’m planning to buy my first bike, and the TVS Ronin has honestly been my dream bike for quite some time. I currently ride a Honda Dio DLX (2016), so this would be my first proper motorcycle upgrade.

But after researching online, I’ve become really confused.

I keep reading on Reddit and other forums that TVS after-sales service is very bad. I also checked the Google reviews of nearby TVS service centers in my area (Gujarat), and compared to Honda service centers, TVS reviews definitely seem worse.

This is what’s confusing me:

If TVS service is actually that bad, then how are they selling so many vehicles? Every day I see TVS Raider, Jupiter, and sometimes Apache everywhere. TVS is among the top 3 seller of 2-wheeler brands, so how can service be that bad compared to Honda or Hero?

At the same time, I’m wondering if I’m just seeing more negative reviews than positive ones, because usually people post online only when something goes wrong.

For example, I’ve seen many people on Reddit say Tata service is bad, but every day I still see tons of Nexon EVs, Harriers, etc. on the road.

My other option is Yamaha FZ-S, but honestly, the Ronin is the bike I actually want. Although Yamaha also seems to have a smaller service network.

So I wanted to ask actual owners:

• Is TVS service really that bad in real life?
• Does it depend more on the individual service center/city?
• Are negative reviews overrepresented online?
• Would buying a Ronin be a bad idea as a first bike because of service concerns?

Would love to hear from Ronin owners, TVS owners, or even people from Gujarat.

The Link for the Schematic Pdf File (For better View): https://drive.google.com/file/d/1pePRykFdu6V69PQ7Nl3Pby1v24CvdhrB/

I added the Images of Schematic and Plug-Play Module.

Hi everyone,

I'm designing a custom ESP32-S3 based PCB and would appreciate a schematic review before I finalize the PCB layout.

Main features:

• ESP32-S3-WROOM-1-N16R8
• OV2640 camera
• INMP441 I2S microphone
• MPU6050 IMU
• 0.96" I2C OLED
• MCP23017 I/O expander
• USB-C power input
• Single-cell Li-ion battery support
• Battery charging and power-path switching
• ESD protection on USB
• Plug-and-play expansion headers/modules

Design goals:

• Compact all-in-one board
• Camera, audio, and motion sensing on a single ESP32-S3
• Battery-powered operation with USB charging
• Future expandability through plug-and-play modules

Specific areas where I'd like feedback:

1. Power architecture and battery charging section
2. ESP32-S3 boot/reset circuitry
3. USB-C implementation and protection
4. OV2640 power supply and signal routing considerations
5. I2C bus design (OLED + MPU6050 + MCP23017)
6. Decoupling capacitor placement and values
7. Any missing pull-ups, pull-downs, or protection components
8. Potential PCB layout concerns before routing
9. I also marked some PIN NC (Not Connected), bcz that pins have weird behavior at boot like JTAG and Straping Pin.

I'm particularly interested in catching any mistakes that could prevent first-power-up or cause reliability issues later.

Thanks for taking a look. Any criticism is welcome - I'd rather fix issues now than after ordering boards.

The Link for the Schematic Pdf File (For better View): https://drive.google.com/file/d/1pePRykFdu6V69PQ7Nl3Pby1v24CvdhrB/

I added the Images of Schematic and Plug-Play Module.

Hi everyone,

I'm designing a custom ESP32-S3 based PCB and would appreciate a schematic review before I finalize the PCB layout.

Main features:

• ESP32-S3-WROOM-1-N16R8
• OV2640 camera
• INMP441 I2S microphone
• MPU6050 IMU
• 0.96" I2C OLED
• MCP23017 I/O expander
• USB-C power input
• Single-cell Li-ion battery support
• Battery charging and power-path switching
• ESD protection on USB
• Plug-and-play expansion headers/modules

Design goals:

• Compact all-in-one board
• Camera, audio, and motion sensing on a single ESP32-S3
• Battery-powered operation with USB charging
• Future expandability through plug-and-play modules

Specific areas where I'd like feedback:

1. Power architecture and battery charging section
2. ESP32-S3 boot/reset circuitry
3. USB-C implementation and protection
4. OV2640 power supply and signal routing considerations
5. I2C bus design (OLED + MPU6050 + MCP23017)
6. Decoupling capacitor placement and values
7. Any missing pull-ups, pull-downs, or protection components
8. Potential PCB layout concerns before routing
9. I also marked some PIN NC (Not Connected), bcz that pins have weird behavior at boot like JTAG and Straping Pin.

I'm particularly interested in catching any mistakes that could prevent first-power-up or cause reliability issues later.

Thanks for taking a look. Any criticism is welcome - I'd rather fix issues now than after ordering boards.

The attached Circuit Diagram is from the Datasheet of the LM66100 Ideal Diode https://www.ti.com/lit/ds/symlink/lm66100.pdf

In The ORing Configuration the higher voltage power supply get connected to Load, for example in this above figure the Vin1 have 5v so it will connects to the load (bcz Vin2 is 3.3V) and Vin1 current will not flow back to the Vin2 to protect it from reverse current. But What if Vin1 (5v) is active and from some inductor or capacitor on the Load side the reverse current flow in the Vout so now Vout > Vin1 (5v). So in that case the current will flow from Vout to Vin1 which I want to block.

The Datasheet also have the circuit diagram (Always-ON Reverse Current Blocking (RCB)), in which CE is connected to the Vout which blocks the MOSFET when Vout > Vin, So Current will be blocked and will not flow back into the Vin.

But in ORing Configuration how to achieve that.

Also I'm trying to build my own DIY version of LM66100 with P-channel Mosfet and Op-amp in voltage comparator format.

In short, I want to know how to achieve Reverse Current Blocking from Vout to Vin In Oring configuration, and any suggestion for DIYing this IC.

Thank You :)

The attached Circuit Diagram is from the Datasheet of the LM66100 Ideal Diode https://www.ti.com/lit/ds/symlink/lm66100.pdf

In The ORing Configuration the higher voltage power supply get connected to Load, for example in this above figure the Vin1 have 5v so it will connects to the load (bcz Vin2 is 3.3V) and Vin1 current will not flow back to the Vin2 to protect it from reverse current. But What if Vin1 (5v) is active and from some inductor or capacitor on the Load side the reverse current flow in the Vout so now Vout > Vin1 (5v). So in that case the current will flow from Vout to Vin1 which I want to block.

The Datasheet also have the circuit diagram (Always-ON Reverse Current Blocking (RCB)), in which CE is connected to the Vout which blocks the MOSFET when Vout > Vin, So Current will be blocked and will not flow back into the Vin.

But in ORing Configuration how to achieve that.

Also I'm trying to build my own DIY version of LM66100 with P-channel Mosfet and Op-amp in voltage comparator format.

In short, I want to know how to achieve Reverse Current Blocking from Vout to Vin In Oring configuration, and any suggestion for DIYing this IC.

Thank You :)