1 Reply Latest reply on Dec 2, 2013 4:57 AM by jduquette

    Error in Hyperlynx Analog simulation > illegal node and error in diablo function

    Luckii

      Working in schematic design circuit simulation, It is an power filter design using Powerfactor controller (PFC) While runing Simulation I am facing the below errors.

       

      ..\..\sym\NCP1607.mod(2): error -- ground is an illegal node in the definition of subcircuit ncp1607.

      ..\..\sym\NCP1607.mod(61): error -- Error in DIABLO function diablo163.

       

       

      For >> "ground is an illegal node in the definition of subcircuit ncp1607."

       

      Procedure followed

       

      1. Vendor supplied PSpice model library converted through Pspice converter in Dxdesigner.

      2. Symbol pin number checked appropriately with the pin name and it is consistent as per Spice file header node.

       

      Query >> Eventhough pin and node consistency exist, facing ground is an illegal node error. How to identify the cause for this error

       

      FOR >>  Error in DIABLO function diablo163

       

      Spice file command line appears as below

       

      D_Activeclamp_D20         N_0036 N_0037 D1N5234

      E_Activeclamp_ABM11         N_0037 0 func(1) vdd 0 diablo163

      .FUNC

      diablo163(a1)

      {

      value  a1 +2;

      return value;

      }

      .ENDFUNC

       

       

      Query >> Any syntax based error exist in the spice code. How to identify the cause for this error.

        • 1. Re: Error in Hyperlynx Analog simulation > illegal node and error in diablo function
          jduquette

          I believe the problem is the '0' after 'E_Activeclamp_ABM11         N_0037'.  That is an absolute reference to ground and it should be referencing the pin number of the module that is connected to ground at a higher level.  In ohter words, the model is breaking the hiierarchy of the design.

           

          If this is a three terminal device, it looks like the terminals are N_0036, N0037, and 0; they should be N_0036, N0037, and N_0666 (or the proper number, because the devil is in the details!).  Fix that in the model.