u/FransUrbo

How many of you, that aren't professionals (!) in circuit and PCB design, have managed to do your "thing", got the PCB manufactured (with or without doing the soldering yourself), and it worked the first time!?

Was it luck, or what did you do to maximise your chances of it working??

I'm now in that position myself. I'm not completely useless, I was pretty good at it "once". As in, thirty plus years ago, with designs WAAAAY smaller and simpler 😄. But I had a fair understanding of electronics, component, how they work and what makes them work together. Fair. At best 😄 😄.

My design is now ready to be manufactured. I've run it through an AI for review *several* times (and it have absolutely found stuff that would have made it into a smoke machine! 😄). But AIs can't be trusted, I know that. Not yet anyway! One day, absolutely, but I do not believe that day is today.. 😄

A PCB is cheap enough to get manufactured, components not so much (almost 15 times the cost of the PCB! 😄), and spending time to do the soldering (or unsoldering! 😄) myself is somewhat easy (have the right tools, and the knowledge, although not the experience 😄). But that first power-on IS going to be .. interesting 😃.

Can't afford a professional to take a look (in the thousands of dollars I've heard), don't have any (close) friend(s) that can do it for free, and I've tried getting through here and elsewhere, but didn't get much interest in it.

What else can I do, besides hoping for luck!? Solder on only "relevant" components, check with a multimeter that everything looks ok (no shorts, the right power in the right place).. What else?

I'm going through a CW/Logs log group, looking for a certain message (as a Metric Filter). If a specific message is found, I then trigger an CW/Alarm, which sends a message to a SNS topic, which sends an email to a mailinglist.

However, the error is intermittent (and might/should not occur unless something gone really wrong, which it doesn't normally 😄), so after five minutes, CW is automatically OK'ing it.

Both the ALARM and the OK goes to the same SNS topic (see no reason for multiple ones), so first comes the ALARM email, then five minutes later the OK email.

I'd like to *keep* it in ALARM ("no matter what", as in even if it haven't found anything in the last five minutes), and have .. "something else" (another Metric Filter + CW/Alarm? Lambda?) change it (that first one) to OK.

Any ideas how to do that? Am I over-complicating things?

Basically, we're looking for a status=400 in the logs: failed to send an email - which only happens if 1) the external service we're using for this is unavailable (network errors, external service down etc) or 2) if we've configured the auth key for this external service wrong (happened yesterday, when we had to change the key and I accidentally added a newline in the SecretsManager secret 😄).

*What I would like* is that the next time a message/mail is sent, *and* if that is successful (status=200), *then* I'd like to clear the ALARM, not otherwise.

This is probably (likely?) the wrong place, but I figured I'd give it a try :) .

Anyone have any information on the deprecation versions of macOS?

AutoDesk list the supported versions on their website, but not how long they'll be supported :(.

I got bitten quite hard on my MBP 11,1 a few weeks ago. It's Monterey only :(.

Tried OBP and Squoia, and although Fusion warned me (a bit harshly imo :), it still worked. But it was seriously unstable, graphics didn't keep up, and it either just froze or crashed. OBPs fault, not Fusion!

I have a much better one lined up (MBP 15,1 with 32Gb instead of the 16GB in my current one), which seems to be Sequoia native as latest. BUT, that is EOL (or at least out of support) in '28. That isn't as far off as I'd like :).

I DO get it! I truly do, I just hate having to .. "recycle" every year or two!! :) My 11 year old MBP is still perfectly usable!!

But if AutoDesk stops supporting Fusion "just" because Apple stops supporting the OS.. !!!