Hey! I can't see your links to the LEDs or the QT Py, but I'm assuming they're probably neopixels as you mentioned "IC" LEDs. Drag your parts into flux and just ask copilot how to connect them together properly. Just to speculate on your project, you probably want some sort of gate buffer for the neopixel signal. And just ensure whatever power source you are using (be it a 5V source or a battery or buck boost converter) can handle the total current draw of those LEDs. I believe they have a wide operating voltage, but also just double check that if you are using a constant voltage source (which you probably are), it isn't over the maximum forward voltage of the LEDs. You can ask in detail with copilot by the way!
Just wanted to echo some more resources to get you oriented. The second video shows actual examples of how to leverage copilot in your exact scenario.
Flux End to End tutorial: https://youtu.be/Nz-XvvlozK4
AI Architecture Exploration: https://youtu.be/iGJOzVf0o7o
It's a weird feeling knowing that Altium isn't a pure ECAD company anymore. Like sure, the team is all the same and will build an EDA tool, but somewhere higher up, there will be a skew towards the automotive industry.
I used Altium in my previous job in high voltage and we were amonst the first to use the Creepage feature. It reminded me that there's niche features to be developed for every industry, and there's a future where they resource heavily on automotive. On one hand, $6B seems like enough to go around for everyone but on the other hand, Renesas would only spend $6B if they saw it making/saving them $10B+.
I'd like them to speak more on the long term vision and focus of the product; I think they've done a good job at serving EEs so far and if they'll still hold that position or get pulled away into one loud market. Regardless, that's like in 5-10 years time; I'd be impressed if anything changes in the next 2 years.
Full disclosure, I'm now working at flux.ai but I don't think that doesn't really changes the news for me; I understand Altium is still used by many EE companies who I can still sympathize with, and we're humbly comin' after them :P
PCB Design is a broad "field." Depends on what you're building. I think people place too much of an emphasis on the tool you use instead of the skillsets you need. At the end of the day, in 99% of cases, we're integrating highly complex, yet modular systems built by semiconductor companies.
Expand your design capabilities by understanding these semiconductor black boxes that are available to you in your field (power electronics, audio, RF, etc.) As another user mentioned, read up on design references! And datasheet graphs, and try to get your hands on closely related previous designs. As EEs, we should talk more about design patterns and primitives like software engineers see it.
But of course, I understand why there's a big discussion about tooling, it's like picking the first language to start programming in. Imo, if you're starting out in PCB design, pick a tool that doesn't get in the way with your learning; something simple but also capable when you progress. The software engineering choice would be python, and I think flux.ai is the closest thing we get to that. But still, if you learn one, you can use the rest! We're all constrained by a pretty standardized manufacturing process so the functions you perform in all these tools will be very similar.
Just wanted to echo some more resources to get you oriented. The second video shows actual examples of how to leverage copilot in your exact scenario. Flux End to End tutorial: https://youtu.be/Nz-XvvlozK4 AI Architecture Exploration: https://youtu.be/iGJOzVf0o7o