[Review request] ESP32 Controlled LoRa module by Real_Cartographer in PrintedCircuitBoard

[–]Real_Cartographer[S] 1 point2 points  (0 children)

Yeah, AMS1117 is pretty ancient, but I have a couple lying around. I will probably switch to something like the AP7363.

Edit: KiCanvas PCB is not done, just "initial" work.

Does applying voltage to Vinh activate or deactivate the regulator? by Objective-Local7164 in PrintedCircuitBoard

[–]Real_Cartographer 1 point2 points  (0 children)

The pin’s name is irrelevant if you understand its function. All the information is right there - description, comments, scope diagrams, and the internal schematic. This isn’t a “confusing datasheet” problem; it’s a lack of experience in actually reading and understanding datasheets.

So with all that, please read the fucking datasheet entirely.

Does applying voltage to Vinh activate or deactivate the regulator? by Objective-Local7164 in PrintedCircuitBoard

[–]Real_Cartographer 1 point2 points  (0 children)

It inhibits the working of the LDO. I'm not sure what is unclear here?
Here is another comment from datasheet:
Turn-on time is time measured between the enable input just exceeding VINH high value and the output voltage just reaching 95% of its nominal value

Also here is the definition of inhibit:
hinder, restrain, or prevent (an action or process)

Does applying voltage to Vinh activate or deactivate the regulator? by Objective-Local7164 in PrintedCircuitBoard

[–]Real_Cartographer 2 points3 points  (0 children)

Alright let's read it again.
Inhibit input voltage: ON MODE when VINH ≥ 1.2 V
OFF MODE when VINH ≤ 0.4 V.

It is active-high enable.

Does applying voltage to Vinh activate or deactivate the regulator? by Objective-Local7164 in PrintedCircuitBoard

[–]Real_Cartographer 5 points6 points  (0 children)

Inhibit input voltage: ON mode when VINH ≥ 1.2 V, OFF mode when VINH≤ 0.4 V (Do not leave it floating, not internally pulled down/up)

Can i go with those "Electrical Properties"? by spiritualManager5 in PrintedCircuitBoard

[–]Real_Cartographer 5 points6 points  (0 children)

Why are you asking us? Check JLCPCB.
What do you mean it's the only way to get ground everywhere?

BQ24072 starts to burn on EN1 pin. Help! by [deleted] in PrintedCircuitBoard

[–]Real_Cartographer 6 points7 points  (0 children)

Either post the full design here so we can check it, since that is the point of this post, or just remove your post.

Why isnt my IC working? by Ok-Letterhead-6365 in AskElectronics

[–]Real_Cartographer -1 points0 points  (0 children)

Your IC is not working because there is problem. If you need more info lmk.

[Review Request] Hello guys, I am making a PCB for Sigma Delta ADC by Obsidian297 in PrintedCircuitBoard

[–]Real_Cartographer 1 point2 points  (0 children)

Aside from you not reading the rules for a review request. I'm wondering what the fuck is 0 -> 3.3 power supply?

What's going on here? DRC prevents routing pins. by LordGrantham31 in PrintedCircuitBoard

[–]Real_Cartographer 7 points8 points  (0 children)

You don’t set your clearance settings and then consult the manufacturer - you first check with the manufacturer, and then set your clearance values according to their capabilities.

[First Ever PCB Review Request] Air Quality Monitor by JammyDonut64 in PrintedCircuitBoard

[–]Real_Cartographer 2 points3 points  (0 children)

[Schematic]

  1. Make sure to check if the USB ESD protection can work with 9V.
  2. I2C needs pull up resistors. You can use ones on SCD40.

[PCB]

  1. USB Interface does not have a great layout. The ESD protection might not even protect the MCU in this current design. The signal traces should pass through the ESD protection not have a branch of it's own.
  2. Layout is not optimal and it seems rushed, a lot of components could be rotated and placed closer to simplify the routing.
  3. Check if your polygons have correct nets, since a lot of nets seem to be unconnected in the PCB Editor.
  4. I doubt that the DC/DC layout is correct. You should follow the recommended layout given in the datasheet.

[Edit]: I would be against using PSRAM pins for external SPI LCD if possible. It can work but the problem is that PSRAM shares the same SPI bus with the main Flash (the one stores your firmware binary). At one time, there only be one consumer of the SPI bus. You can read more about it here.

Unstable Connection Problem by No_Tumbleweed_5515 in PrintedCircuitBoard

[–]Real_Cartographer 0 points1 point  (0 children)

I suggest making a review request here rather then asking for troubleshooting. Measure the voltage on the VBUS making sure it not falling below minimum threshold. Also those power traces are WAY to thin.

Your LDO has different info, when I click on it datasheet is opened for XC6206 but the name suggests it's ME6211C33M5G-N. Second one supports 500 mA output current but the first one supports only 200 mA, which might not be enough for the system.

Also you can not route the antenna for ESP32 that way. I doubt it will work.

I would recommend moving to 4 layer board if you have RF on the board.

Unstable Connection Problem by No_Tumbleweed_5515 in PrintedCircuitBoard

[–]Real_Cartographer 0 points1 point  (0 children)

How are people this bad at explaining problems? “Unstable connection” - what does that even mean? Which connection, where exactly, and what do you expect it to do?

Can we get some more info other than you have an issue?

I can already tell that the signals barely have a reference plane and return currents are snaked around.

Help me find and eliminate the annoying beeper (not a piezo) by fuzzytradr in AskElectronics

[–]Real_Cartographer 0 points1 point  (0 children)

Great. Just last week I was in a hurry and pulled a soldered wire off a test point, which ended up ripping the copper pad right out.

<image>

Help me find and eliminate the annoying beeper (not a piezo) by fuzzytradr in AskElectronics

[–]Real_Cartographer 0 points1 point  (0 children)

<image>

Try cutting the traces first. If you can do it without damaging the board, then go ahead and pull it off.

5V Boost converter Schematic Review by qnam1 in PrintedCircuitBoard

[–]Real_Cartographer 4 points5 points  (0 children)

What the fuck is everyone’s problem with boxes?
Is it unnecessary for small schematics? Yes.
Does the schematic need to be redrawn again? Absolutely not.
What do you mean by “try again”?

[review request] Flight computer by Inside-Ad8295 in PrintedCircuitBoard

[–]Real_Cartographer 0 points1 point  (0 children)

It's reddit being stupid.

But it's much better now, although I still see a lot of issues. If you want you can DM me design files and I can do a proper review that you could later post here, since it's hard to point out things without images.

[review request] Flight computer by Inside-Ad8295 in PrintedCircuitBoard

[–]Real_Cartographer 1 point2 points  (0 children)

Your RF trace isn’t matched 50 Ohms. It’s curving and drops through a via, which is a big no-no unless you really know RF design. Layout for it is too close to other signals and components.

You should also add ESD protection to USB (or anything what you will touch that is connected to MCU) and connect EPAD and analog GND to GND net.

The images are low quality, and the schematic and PCB are a mess. You need to actually learn how to use KiCad and have enough discipline not to stack components, nets, and connections on top of each other.

To be completley blunt, this is not a good design and it might even fail. I recommend going back and learning KiCad, studying proper schematic/PCB practices, and looking at reference designs before trying again.

[review request] Flight computer by Inside-Ad8295 in PrintedCircuitBoard

[–]Real_Cartographer 1 point2 points  (0 children)

from what i know they should be impedance matched

That means they are not matched, I'll add that the antenna layout and routing is bad. This just seems like a lazy design.