Stats

  • Locked Locked
  • Replies 7
  • Subscribers 126
  • Views 15406
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Schematic entry parameter as a function of instance name

yoyega

 Hi, I have a question concerning a schematic entry. Let's assume that I have defined a subcircuit that has pwl souce inside. This pwl source reads the point/time values from a file, and I want that the name of the file in the definition of the pwl source to be automatically set as a funcion of the name of the instance of the subcircuit. Does anyone knows how to do this?

Example:

subckt myckt
    I0 ( node1 node2 ) isource type=pwl file="a_function_of_the_name_of_the_instance_of_myckt"
    ...
end myckt

This way, if I have to instantiate several instances of myckt, each instance would automatically read point/time values from different files.

Thanks,
Pedro

Parents

  •  Ok, thank you Andrew. I think that the easiest solution now would be to entry just the schematic of one pixel, to use the Analog Artist to generate the netlist of this one pixel subcircuit, and then incorporate this subcircuit into some c++ code that generates netlist of the full 32x32 pixel matrix (I know how to program in c++). In the mean time I will try to learn the basics of skill programming so I can find a better solution next time...

     

    Thanks again for your answers,

    Pedro 

Reply

  •  Ok, thank you Andrew. I think that the easiest solution now would be to entry just the schematic of one pixel, to use the Analog Artist to generate the netlist of this one pixel subcircuit, and then incorporate this subcircuit into some c++ code that generates netlist of the full 32x32 pixel matrix (I know how to program in c++). In the mean time I will try to learn the basics of skill programming so I can find a better solution next time...

     

    Thanks again for your answers,

    Pedro 

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.