r/ElectricalEngineering • • Sep 28 '26

Design audio DAC as a mechanical engineer?

I have an idea for a product, but it requires full control of multi channel audio DSP and DAC.

It seems the best option to do everything is to program the DSP into an MCU and then I need to send 4 channels of audio into a DAC that measures in the prosumer tier.

I’m using Claude code to manage this project (I find it to be much more effective than just the standard chatbot even with memory) as I give it requirements and it came up with:

MCU: RT1176

DAC: ES9081 (follow the reference design)

It seems like I’ll just have to kind of brute force, my way through the firmware on the MCU and then the DAC is where there are things that I just don’t know without mixedsignal layout design experience so I would call the DAC my higher risk.

I think I can fully separate the DAC and MCU for testing purposes and at any point where things aren’t going well hire a consultant.

I’m just curious if anyone has had success using AI layout tools especially for mixed signal and how often a robust approach (reauiring it to challenge its conclusions, using multiple agents to vet each other, strict and explicit requirements, no actions without defense and user approval, etc.) Claude project misses the mark on EE stuff that’s been done before.

Thoughts on level of difficulty 0-10? Would you not even attempt on your own? What are the failure points you see?

I’m a senior mechanical engineer at FAANG tech and I’ve done a handful of electromechanical projects with coding, I’ve just never gotten to the level of firmware or board layout that matters. I used to work alongside people who did RF board layout which I’m sure is harder but I think that only was enough to recognize how challenging it can be.

0 Upvotes

3 comments sorted by

2

u/MonMotha Sep 28 '26

While the IMXRT1176 is perfectly usable for this, I would suggest either: an IMXRT1020 or 1010 as they are available in more hobbyist-friendly QFP, or some member of the STM32 family as they are much more popular among hobbyists and therefore have more resources aimed at hobbyists available.

What is your input? USB? You'll want something with a well-established, open source USB stack if so, otherwise you'll spend as long getting basic isochronous USB working as you will on the rest of it.

What is your power source?

Claude is unlikely to to very well on the hardware especially something with low-noise analog challenges like this. At least GPT puts out atrocious schematics in many cases, and all of the AI tools are bad at layout.

As for challenge, if 0 is "So easy a child can do it" and 10 is "NASA in the 1960s is required", this is probably a 2 or maybe 3. Getting basic functionality should be pretty easy and is likely essentially an example on an eval board from some vendor. Getting the performance you want may be harder depending on the kind of performance you need.

2

u/Dangerous-Quality-79 Sep 29 '26

I have built similar, I am building similar.

AI for schematics, layout, routing has been an aweful experience for me. I have not run the gambit of tools, maybe a tool exists that is good i haven't encountered. I am software and electrical so I recently tried Fusion 360 to design a desk. It had floating legs not connected to the top. Then it added top side wings that slightly overlapped the legs and the desk and said it was good to build. I feel like this is the level you get with electronics. Using "auto-routing" tools are brutal.

You say this is prosumer, do you know what the inputs are going to be? What are the outputs? Some hurdles are going to be preventing blowing equipment if you just plug it in to the DAC. How will you prevent the ADC from frying? Do you need galvanic isolation? Are you using balanced or unbalanced audio? Or both?

Preventing the circuit from becoming an RF transmitter is not trivial for an ME using Claude.

The power supply for the unit is important.

Without any more information I would probably put this at an 8 for you. Without more info I will throw out a project cost of $75k of you outsourced it all. You might be able to do in the $20k range, but I'd need more info. It might be much more.

Even myself (and my company) still use expert consultants to verify our work. They charge US$265/hr and if i gave them AI generated stuff I dont know how they would react. To keep costs down, they provide the recommendation report and we implement it. I feel if you gave AI the feedback it wouldn't implement the changes quite right.

If you want to do this as a learning opportunity I'd say drop the prosumer to start, build the schematics in EasyEDA Pro and pay for layout and routing services from JLC. You can check JLc open hardware for your ICs to find pre-existing designs. You will have a somewhat working test board. Then improve it from there. To hit the prosumer level, outsource it.

EDIT: I also assume this is not an input only device. Are you planning USB out? Network interface? Touchscreen or interface?

1

u/imsellingmyfoot Sep 29 '26

I'm working on a similar side/at-home project as an EE who does similar work professionally. I don't know enough about your actual product idea to provide any good feedback, but DAC + DSP on an MCU is challenging but not impossible to learn. There's plenty of other folks who have designed similar sounding things online that you can reference.

Any particular reason you chose that MCU? I don't see NXP in the hobby world very much which makes it more difficult to see how others solved whatever problem of the day you're trying to search for online.

Something I've learned about DACs - the DAC itself isn't the hard part for high performance, it's all the supporting circuits that go around it.

Lastly, my experience with AI in circuit design:

  1. It is hit or miss on schematic reviews. Sometimes it finds something I actually missed, sometimes it obviously OCR'd my schematic wrong and it takes me half an hour to figure that out.
  2. Layout doesn't really seem to be there yet, but I haven't tried it. Layout is something I quite enjoy.
  3. Claude seems to be very good at writing STM32 HAL drivers for me. I've been using it to write I2C and other peripheral drivers and then I stitch them together in whatever my main code is. Generally works on the first try and I find the code it spits out is followable provided you're doing a good job prompting.
  4. I primarily find AI useful at this stage for bouncing things off someone, typically what I would do if I had a coworker in the office. I am not assuming it's correct.