T
TomH
Guest
I just spent several hours trying to figure out ORCAD student pspice
circuit simulation ware. There's no tutorial, there's no "view from 30000
feet" explanation as to how all 8 sub-applications interact with each other,
you can't just create a file representing a circuit, you have to create a
workspace, then a component libraray, then a stimulus input file, there's no
explanation as to how get circuit "a" to be subjected to stimulus file 'b',
ahhh, I surrender.
Can someone recommend some intuitive circuit simulation ware suitable for
simulating basic RF circuits?
I suppose when you're dealing with concepts as abstract as AC circuitry,
intuitive software is a tall order, but still, how much is it to ask for
information that someone who has never seen the application before will
obviously need. It's tough when you're developing software to know what
someone is going to think when they see it for the first time, when you the
developer have spent hundreds of hours fiddling with its minutia, but that's
what they have software testers for.
Anyway, has anyone out there been confronted with this issue? How did you
solve it --- keep plowing away at pspice (because it's so comprehensive),
get a tutorial on pspice, or find another more intuitive package?
circuit simulation ware. There's no tutorial, there's no "view from 30000
feet" explanation as to how all 8 sub-applications interact with each other,
you can't just create a file representing a circuit, you have to create a
workspace, then a component libraray, then a stimulus input file, there's no
explanation as to how get circuit "a" to be subjected to stimulus file 'b',
ahhh, I surrender.
Can someone recommend some intuitive circuit simulation ware suitable for
simulating basic RF circuits?
I suppose when you're dealing with concepts as abstract as AC circuitry,
intuitive software is a tall order, but still, how much is it to ask for
information that someone who has never seen the application before will
obviously need. It's tough when you're developing software to know what
someone is going to think when they see it for the first time, when you the
developer have spent hundreds of hours fiddling with its minutia, but that's
what they have software testers for.
Anyway, has anyone out there been confronted with this issue? How did you
solve it --- keep plowing away at pspice (because it's so comprehensive),
get a tutorial on pspice, or find another more intuitive package?