| ▲ | matheusmoreira an hour ago | |||||||
> I never did this before so there was plenty to learn, from basic electronics and magnetics to high-speed signal routing. How did you learn this? As a hobbyist I found hardware to be quite impenetrable, given the hard mathematics and physics requirements. My attempts to learn this essentially degenerate to taking an informal engineering course. It quickly becomes clear that I'm years away from making something, and I eventually run out of both free time and executive function. AI's been helping... But I don't have the ability to tell when the output is wrong. | ||||||||
| ▲ | bobjordan 8 minutes ago | parent | next [-] | |||||||
Building something useful in a circuit design using off-the-shelf ICs and components doesn't require a very deep understanding of the theoretical basis for why it works. There's really no need to be gated by thinking that overly complex mathematics and physics concepts must be fully understood before building. Most electronic parts datasheets have example circuits and layouts that can be followed to get a working design. A lot of progress can be made just by reading the datasheet, learning how to use a tool like fusion 360 electronics, kicad, etc., to connect the parts in a schematic, lay them out on a board, generate a gerber, send it to a china PCB shop like PCBway, get the pcb, assemble/solder the parts onto it, some cases may need some firmware which AI can do a lot now, finally fire it up and see if it works. Very few calculations or theoretical knowledge needed, outside of Ohms law. | ||||||||
| ▲ | the__alchemist 40 minutes ago | parent | prev | next [-] | |||||||
> As a hobbyist I found hardware to be quite impenetrable, given the hard mathematics and physics requirements. IMO there aren't any. It's mostly about reading datasheets, and connecting pins to each other IOC those datasheets. Maybe the physics and mathematics are more important for analog electronics or designing ASICS? Do you have any specific projects you'd like to build? Post here and we can talk through it. And/or start by downloading KiCAD and clicking around until you understand the UI. The programming side is mainly also reading datasheets. Instead of connecting the right pins together, you are writing a certain value to a register, as described in tables. | ||||||||
| ▲ | interfeco an hour ago | parent | prev | next [-] | |||||||
Just to be clear, I made a working prototype (and put a hyperbole in the title), I have a lot to learn still. You can learn something practical like "embedded DisplayPort should be impedance controlled to 100 Ohms" without fully understanding the physics behind it. AI can be very convincing. It told me to put the ESD protection as close the Ethernet connector as possible, so I put it between the port and the magnetics. This worked, but resulted in around 1% packet loss. When I moved it after the magnetics, I got 0% packet loss. This cost me a full revision, but I'd say this is the price to pay for not learning everything by the book. | ||||||||
| ||||||||
| ▲ | turkeygizzard 42 minutes ago | parent | prev | next [-] | |||||||
I was going to say, AI has really enabled my hardware projects recently. I've found incorrect output is less common with the newest models - and they're capable of drawing decent diagrams too which can really help me sanity check some of their ideas. I've also had some success with asking it to cite sources where possible, so I get lots of useful links into robotics forums like chief delphi and similar which also help sure up the math | ||||||||
| ▲ | qup an hour ago | parent | prev [-] | |||||||
Or, you could make some mistakes. | ||||||||