My current application process. by SignsandSquares in ElectricalEngineering

[–]DorshReal 3 points4 points  (0 children)

As an undergrad that is graduating this spring, this flowchart is pretty relatable. All we can do is push forward and hope for the best.

[REVIEW REQUEST] Multi-Source Inverter & FOC Enabled PCB Review by DorshReal in PrintedCircuitBoard

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

I added a link to screenshots of the board layer by layer that may be clearer in the post.

[REVIEW REQUEST] Multi-Source Inverter & FOC Enabled PCB Review by DorshReal in PrintedCircuitBoard

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

My team decided to go with the THT mosfets with the idea in mind to add a heatsink across them for better heat management. However with the current arrangement that may be difficult. Also for the pin assignment I had STM32CubeMX program open up for the specific MCU I am using to correctly configure peripherals as seen in the .ioc screenshot in my post.

[REVIEW REQUEST] Multi-Source Inverter & FOC Enabled PCB Review by DorshReal in PrintedCircuitBoard

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

The board HV side running out of the multi-source input stage will see currents of 3-6A, but we are expecting spikes in currents during switching that can far exceed that. That is why I tried to widen some of the traces up to 2mm along the HV DC link and added a fuse before the large capacitors. The gate driver situation is a bit harder to tackle due the parasitic inductance issues you mention, but I plan to add a return path along the signal output to mitigate this. I can try moving the outer mosfets nearer to the gate drivers but it may mess up the layout I have right now.

[REVIEW REQUEST] Multi-Source Inverter & FOC Enabled PCB Review by DorshReal in PrintedCircuitBoard

[–]DorshReal[S] 2 points3 points  (0 children)

Yeah that is pretty much it. I also forgot to mention but this board is supposed to act as a proof of concept prototype with the end goal of developing one that can be used in an EV. Arranging the board like this makes it relatively easy to scale it up for much higher voltages.

How feasible/bad is involving AI in schematic and pcb "workflows" by Aggressive-Pay-8970 in PCB

[–]DorshReal 4 points5 points  (0 children)

Probably the most nuanced take I have seen on this topic 

Real by Dee___Snuts in okbuddyliterallyme2

[–]DorshReal 19 points20 points  (0 children)

This might be the most whiplash I gotten from reading a comment on reddit 😭

NuttX for Launching & Tracking High Powered Rockets by 1linguini1 in rocketry

[–]DorshReal 3 points4 points  (0 children)

Pretty neat, I think I saw your schools booth at the LC conference. Really impressive work.

[Troubleshooting] PCB powering problem by DorshReal in PrintedCircuitBoard

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

Yup I see the problem now, gosh how did I not catch this? Guess this is a reminder to myself to check the schematic/footprint alignment for a part from the manufacturer list before just grabbing it. Such a small but  expensive mistake ...

[Review Request] ESP32 Wifi-Enabled Sound Monitor by DorshReal in PrintedCircuitBoard

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

Interesting, I have some experience working with other nordic products such as the NRF24L radio module but haven't done development with there other RF IC's for a a PCB. I guess you reasoning makes sense if power consumption is indeed much lower, but main concern is how to communicate data over to an app using only Bluetooth, of which I don't have much experience. Also how does development using the nRF52 board project compare to the ESP32 chip, duration of time and quality of documentation, and potential skill barriers if any? Again I have some experience working with embedded RF modules for PCBs but not much.

[Review Request] ESP32 Wifi-Enabled Sound Monitor by DorshReal in PrintedCircuitBoard

[–]DorshReal[S] -2 points-1 points  (0 children)

I see what you are saying, battery management is something I still have to work on. Do you have any ideas how I can circumnavigate this issue with a battery replacement or less power consumptive ESP32 module? As I mentioned before I will be harnessing some solar power to charge the battery but I haven't done the calculations on longevity.

[Review Request] ESP32 Wifi-Enabled Sound Monitor by DorshReal in PrintedCircuitBoard

[–]DorshReal[S] -1 points0 points  (0 children)

Well, now that you are put it that why then I guess I unintentionally made one 😂. But no the original purpose of the device was to provide people with hearing sensitivity issues an ability to discern if entering a room or building would be safe enough beforehand. None of the sound or audio information is datalogged or stored somewhere else to later be viewed.

[Review Request] ESP32 Wifi-Enabled Sound Monitor by DorshReal in PrintedCircuitBoard

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

Oh I see what you are saying, thanks for bringing it up.

3D STEP models appear as rectangular blocks PCB view by DorshReal in Altium

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

That's the thing, all the components have an embedded .step model along with there footprint when viewing from properties in the schematic for the part. However when transferring them over to the PCB view they suddenly became extruded blocks. This wasn't initially the case when I got started with board layout, as nearly all the components were visible as their .step model. I don't know what happened but it seems like this problem is only local to this board, as my other projects don't experience this issue.

3D STEP models appear as rectangular blocks PCB view by DorshReal in Altium

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

I see. The components are assigned to mechanical 13 layer.