im new and im not sure how to test it, i have tried the transient analysis but how do i know if it works
Attachments
-
8 KB Views: 19
What is it?im new and im not sure how to test it, i have tried the transient analysis but how do i know if it works
so would i have to test parts of the schematics separately?What is it?
Your going to have to define some test cases and expected results to test it.
Declare what the circuit is supposed to do (its purpose).so would i have to test parts of the schematics separately?
There are some LTSpice tutorials in the web by Simon Bramble. Not sure but maybe they could help.No idea what your circuit us, but, just ss an example, here is how you would test an audio amplifier in the simulator:
1. Create an AC voltage source that is a sine wave at 1KHz and connect it to the input of the amp.
2. Run transient analysis.
3. Probe the inout and output to see the waveforms.
To test frequency response:
1. Set up an AC analysis as a frequency sweep across the audio spectrum plus some more.
2. Make your input voltage source the AC analysis source.
3. Run the AC analysis.
4. Probe the output. You will get a Bode diagram.
To test for distortion:
Run a Fourier analysis. Look at the error log, it will give you the total harmonic distortion.
You might want to find a tutorial that covers these topics as LTSPICE is not all that intuitive.
the circuit is brake system plausibility device where if a driver brakes and accelerates at the same time for 500ms it shuts down the engine, so it has 2 sensor inputs, each sensor is connected to a window comparator toDeclare what the circuit is supposed to do (its purpose).
Divide the circuit into "functional blocks" (this looks like its already been done).
Then, develop test cases for testing each of the functional blocks.
The test cases define what to test and the expected results.
so for example how would i test the window comparators on the left which is supposed to keep the input of a current sensor between the range set by the voltage dividers which in this case is 1.6-4.5V but if the input were to go above or below that range then it would output low here is what it should look likeDeclare what the circuit is supposed to do (its purpose).
Divide the circuit into "functional blocks" (this looks like its already been done).
Then, develop test cases for testing each of the functional blocks.
The test cases define what to test and the expected results.

im just not sure how to input the settings for a sin wave or pulseThere are some LTSpice tutorials in the web by Simon Bramble. Not sure but maybe they could help.
If you reread my post it was related to the possibility that Simon Bramble's could serve on what he mentioned.im just not sure how to input the settings for a sin wave or pulse
i get that but i mean like how do i know what numbers to inputYou right-click on the voltage source, and then "Advanced", and then select the signal type you want (below):
View attachment 320310
That comes from the system requirements.i get that but i mean like how do i know what numbers to input
how exactly am i supposed to know themThat comes from the system requirements.
Don't you know them?
Exactly from the application.how exactly am i supposed to know them
if you mean like the input voltages for example andExactly from the application.
You have stated:
"the circuit is brake system plausibility device where if a driver brakes and accelerates at the same time for 500ms it shuts down the engine,"
So you should be able to infer the inputs and the expected outputs for that.
If you don't know them, then you need more information about the requirements of the system, which we certainly don't know.
do you mean like the voltage inputs for example and its output, if so yesExactly from the application.
You have stated:
"the circuit is brake system plausibility device where if a driver brakes and accelerates at the same time for 500ms it shuts down the engine,"
So you should be able to infer the inputs and the expected outputs for that.
If you don't know them, then you need more information about the requirements of the system, which we certainly don't know.