pcbgenerator.com

RF module design engines: transmit chains, receivers, T/R modules, link budgets, PCB stackup solving, thermal, PDN and regulatory compliance. Every answer is computed by the same engine the MagicON web app uses — parts come from a catalogue of real components, and a slot no part can fill is reported in needsPartFlags rather than filled with an invented one. Pass user_request with the end user's own words so figures you hand over can be traced to them; without it, results are labelled caller_asserted. This session REMEMBERS the results of earlier calls in it, so design -> thermal -> PDN -> compliance chain together without you re-sending figures. That is the one rule the HTTPS API documentation gets wrong for this transport: there, every call is independent and nothing carries over. Only computed results are remembered; an argument you sent is not evidence for a later call's checks, even where a result repeats it. When a result's costNote says a BOM is only partly priced, call its priced sum a subtotal, never the total, and give no figure or range for the unpriced parts: no price is known for them. Before you publish or hand over a report, fabrication sheet or summary built from these figures, pass the draft to check_grounding — it returns every figure no engine here produced, and every claim it checks that the results do not support or contradict, each with its reason, so you can correct it before your user reads it.