Análise de Netlist de Circuito

flux

0:00

Trabalho realizado
  • SCR Q1: trocado pelo TIC106 THT e configurados footprint e aliases de pinos
  • Diodos D1, D2, D3 e D4: substituídos por 1N4007 THT com aliases corretos
  • Resistor R1: valor e aliases conforme JSON
  • Capacitor C1: valor, tensão e aliases conforme JSON
  • Potenciômetro P1: valor, footprint, aliases e curto entre pinos 2 e 3 implementado
  • Lâmpada neon U2: adicionada e configurada com aliases do JSON
  • Bornes J1 e J2: substituídos por bloco THT com aliases corretos
  • Nets renomeadas: AC_IN_1, AC_IN_2, V_POS_RET, V_NEG_RET, SINAL_POT, RC_TRIGGER, GATE_DRIVE, LOAD_RETURN
  • ERC executado e validado sem erros
Revisão dos critérios de sucesso
  • ✅ Esquema completo usando apenas componentes THT especificados
  • ✅ Aliases de pinos e nets exatos: AC_IN_1, AC_IN_2, V_POS_RET, V_NEG_RET, SINAL_POT, RC_TRIGGER, GATE_DRIVE, LOAD_RETURN
  • ✅ Curto implementado entre P1:2 e P1:3
  • ✅ ERC sem erros
Próximo passo
O esquema está concluído. Deseja que eu prepare o layout de placa (revisão de footprints, configuração de stackup e posicionamento de componentes) para avançarmos à fase de layout?
107 days
Sign up to send

To get started, talk to Flux or create a New Document.

Documents

    Documents are markdown text files which describe project goals, capture details, or even simulation outputs.

    Assets

    No assets added.

    Chubby Moccasin Wall-E

    Chubby Moccasin Wall-E thumbnail
    Controle de potência AC com SCR TIC106, retificador em ponte, disparo RC com lâmpada neon e bornes THT #SCR #ControleAC #Retificador #DisparoNeon

    Properties

    Before I align the schematic 100% with your JSON, I need three confirmations from you so I don’t fight your intended naming/footprints: 1) Footprints: Is it acceptable for me to substitute any KiCad-style SMD footprints currently present with functionally equivalent THT footprints where needed, as long as all components remain THT in the final design? 2) Net names: Do you want the net names in Flux to match *exactly* the JSON names, including V_POS_RET and V_NEG_RET (replacing the existing V_POS/V_NEG where appropriate), or should I preserve some of the current names and only alias them logically? 3) Components vs. JSON: For parts that already exist in the project (SCR, diodes, RC network parts, terminals), do you prefer that I: - reuse the existing components and only adjust their properties/aliases/nets to match the JSON, or - remove and re-add them so that the symbols/footprints and properties match the JSON definition as literally as possible?

    Diagram
    


  
    
  
  
    
  


















AC Input J1
Bridge Rectifier D1-D4
V_POS
V_NEG
SCR U1
Load Output J2
RC + Neon Trigger
SCR Gate

    Pricing & Availability

    Distributor

    Qty 1

    Arrow

    $1.46–$2.91

    Digi-Key

    $5.62–$8.25

    LCSC

    $2.31–$2.72

    Mouser

    $3.41

    TME

    $2.24

    Verical

    $1.21–$48.62

    Controls