r/rfelectronics "How do you actually use AI in your RF work" — lessons (2026-10-21)¶

Source: the thread text you pasted (post by u/magicon_support, 2 days old, 11K views, 27 comments). Everything below is read from that text. Whether MagicON already covers each gap is not checked unless it says so.

1. What people said (grouped)¶

Theme	Who	What they said, in short
Trust / wrong figures	wynyn, vtjballeng	AI is "confidently incorrect"; check every value it looks up; "always get the source" (datasheet page). A DOA board is not defended by "Claude said so".
Hard physics fails	wynyn	Noise of an antenna with several averaged LNAs: AI got correlated vs uncorrelated noise wrong, then argued.
Verification of outputs	korshenk	Big data scripts are hard to trust; code must be readable so a human can verify it. Gave up on "meaningful analysis".
Small tools win	wynyn, betafusion, korshenk, sswblue	S-parameter viewer in HTML, array pattern generators, matching calculators, n-way synthesizer, plotting, Excel LAMBDA for BOMs.
Lab / instrument automation	wynyn, vtjballeng, leverphysicsname, StageMajestic613	Most common real win: scripts that drive power supplies, VNAs, spectrum analyzers.
Wants MCP/API on their tools	kawfey	"would love if my company/rf analysis tools had MCPs or APIs".
Can't use cloud	StageMajestic613	Employer forbids cloud AI — local models only.
No money for solvers	jephthai	Builds interfaces to open-source tools (NEC2) with AI + authoritative references + test loops.
BOM chores	sswblue, korshenk	Format the BOM, find LCSC part numbers.
Review of own work	sswblue, vtjballeng	Use AI as a second reviewer for schematic/layout/spreadsheet, not as the designer.
Learning a new area	natedn10, kawfey	PLL loop filter for a new VCO; "how do I approach X".

2. Lessons¶

Your core pain is shared. Two people independently said "check the source / the datasheet page". That is exactly the pitch "every figure has its datasheet page". It is a real need.
Nobody asked for "AI designs my module". The wins are narrow, checkable tools. Lead with one checkable answer, not with a full design flow.
Trust is earned by showing the check, not the answer. korshenk and wynyn both reject output they cannot verify.
Your question-replies got answers; your opinion-replies did not. "When you say AI built you mean all code?" got a reply. "Any CAD GUI will become obsolete" and "these big CAD companies will have a hard time" got none (except one pushback from you on Photoshop).
Some threads were dropped. heavisidepiece (Monte Carlo loops) and korshenk (data scripts) got one question, then nothing. Dismal_Plate5226 got "this sounds vague" — accurate, but curt for a hobbyist.
Sub rules matter. Rule 2: no commercial posting without approval. Rule 3: no AI posting / low effort. Your username is magicon_support, so anything that points at the product may be read as an ad. Ask the mods before naming the tool.

3. Gaps (possible MagicON work — none checked against the code)¶

Correlated vs uncorrelated noise when LNAs are combined (array / averaged receivers). wynyn's case is a ready-made test case.
Obsolete / not-recommended parts excluded from search (your own post's complaint).
Local / offline use for people whose employer bans cloud AI.
S-parameter (Touchstone) viewing and quick plots without ADS.
BOM formatting + distributor part numbers (LCSC, etc.).
Lab instrument control — probably out of MagicON's scope; note it, don't chase it.

4. How to ask for more feedback (ready-to-paste)¶

Status 2026-10-21: the reply to wynyn is posted. The other four are held on purpose — wait for wynyn's case, build one real test from it, then decide.

Rule of thumb: ask one concrete question per person, about their case, and offer to do work for them. No links, no product name, until the mods approve.

To wynyn (best lead — a test case):

Your averaged-LNA noise case is exactly the kind of thing I want to get right. Could you share the setup (number of LNAs, how they combine, which noise sources you treat as correlated)? I'd like to use it as a test case and post back what the tool gets right or wrong.

⛔ Do not send the four replies below (owner decision 2026-10-21): they read as product research ("the rule I'm building around", "if a tool like this ran..."). Section 6 is the rule now.

To vtjballeng (source pages):

"Always get the source" is the rule I'm building around. When AI gets a datasheet figure wrong, what's the most common way — wrong part revision, typ vs max, wrong temperature, a value from a plot? That tells me what to check first.

To StageMajestic613 (local-only):

If a tool like this ran fully on your own machine (no cloud), would that be enough for your employer, or is any AI tool off the table?

To korshenk (verification):

If every number came with the line of the datasheet or the formula it came from, would that make you trust the output, or do you still need to read the code?

To heavisidepiece (follow-up you dropped):

Coming back to this — what is the Monte Carlo loop varying, and what does the AI decide between runs?

To the mods (before any product mention): — ON HOLD (owner, 2026-10-21): no product posts yet; collect improvement feedback only

Hi — I'm the author of the "How do you use AI in RF work" thread. I'm building a free RF tool (component lookup with datasheet page citations, link budgets). Several commenters asked for things it does. Would it be OK to post one follow-up showing results, clearly marked as my own project?

Follow-up post idea (in ~2 weeks, only after mod approval): "I took 3 of your requests from the AI thread and tried them — here's where it worked and where it failed." Show the failures too. That fits rule 3 (not low effort) and earns trust (lesson 3).

5. Next posts to get feedback (one a week, no product name until mods approve)¶

"Where has AI given you a wrong datasheet figure?" Ask for the part, the field, and what the datasheet really says. Collects real failure cases (test cases) and builds on lesson 1.
"What RF calc do you still redo by hand every week?" One narrow question; the answers are a ranked wish list (lesson 2: small, checkable tools win).
"Obsolete parts: how do you check a part is still active before you design it in?" Your own pain from the first post; finds out if others share it.
Results post (after mod approval): "I took 3 asks from the AI thread and tried them — here is where it worked and where it failed." Show the failures.

Other subreddits to try (their rules NOT checked yet — read them before posting): r/AskElectronics, r/PrintedCircuitBoard (stackup questions), r/ECE, r/amateurradio.

Owner rule (2026-10-21): no "try MagicON" posts and no mod request for now — only questions that collect feedback on what to improve. The "results post" and "try it" ideas above are on hold.

No scheduled questions and no weekly task (deleted 2026-10-21). Survey-style questions — answer forms, "what stops you", "what would you automate", "which file do you use" — read as product research, and more so from an account named magicon_support. Readers must never feel used to build a product.

Rule: post only when there is something real to share — a problem you hit, a finding, how you solved it — then ask ONE open question about how others handle the same thing. The discussion is the feedback. No answer forms. No product name, no link.

Things worth sharing: none right now. The three θJC findings (GRF5616 two-stage values, simulated θJC on Analog Devices parts, Infineon RthJS) were already answered — an outside answer was checked against the datasheets and the owner decided issue 808 — so posting them would ask what is already known. Add a finding here only when its answer is NOT known yet.

Retired (in git history if ever needed): the 14-week queue and the two full drafts (tools and hand-copying; thermal budget). Dropped earlier because the owner already knew the answer: N1 filter passband (#814), N3 mounting (#815), #818 GCPW; "wrong datasheet figure from AI" was already posted by someone else.