Search Engine www.edaboard.com

Expected Value

Add Question

112 Threads found on edaboard.com: Expected Value
for the Nominal case (TT) it has a strange value, instead in the others corners it seems quite good. ??? The numbers show higher PSRR (better) for TT. - - - Updated - - - Higher than expected is a bit different from failure. Everything is just simulation, it's easy to "look into" the
What is Convert.ToBoolean(date) expected to mean? Seems useless.
Are there any more specifications? What is the minimum load value allowed on the output? Are you limited to one active device per stage? What is the maximum output swing expected? Maximum output distortion allowed? Frequency bandwidth of operation? - - - Updated - - - It would be much easier if
Hello, Hopefully this is posted in the right area. I'm trying to model the current of the device which is captured by one of the last lines of this code: (I(p,n) <+ ddt(polar);) // VerilogA for tech_support3, test, veriloga `include "constants.vams" `include "disciplines.vams" `define M_PI 3.14159 module test(p,n); inou
I like to run simulations to see what behavior can be expected. This schematic shows approximately how a flyback converter boosts 30V to 96V, 300W. of the 1:1 winding ratio, it needs an unusually long duty cycle. The 12 uH primary value was determined by hit-and-miss exper
You'll need RF transistors to achieve power gain at 100 MHz. A 2 N3904 zener diode can be expected to generate wideband current noise, but it needs to operate on a much lower load resistor for almost frequency independent output. You find much literature about RF noise generators, e.g.
Makes no sense: cli(); int temp = profile.moved_steps; sei(); process(profile.moved_steps); did you mean process(temp); I don't see a particular fault. I guess you are seeing the correct actual value, but probably from a time different than expected.
The shown schematic is expected to work. Possible reasons for the observed problem: - MOSFET defective - wrong MOSFET pin assignment I guess, your actual schematic has an additional signal path to turn the MOSFET on. May be it's generating an unwanted voltage across R1.
The amplifiers can be expected to have |S11| < 1, respectively positive dB value of return loss, respectively negative dB value of reflection factor. Surely not negative return loss dB value.
i face problem with simulation in proteus i got wrong output not the expected from the written program but i dont know why ?! while(1){ start : temp = temp_sensor_func(); // call temp sensor function dtostrf(temp, 1, 2, buffer); //convert temp value from double to char to display on LCD and transmit with Uart lcd_print(&Lcd , buf
Although Power Spectral Density (PSD) of EMG signals ranges from 10 to 500Hz most is from 20 to 250Hz. The lower end filter of 70Hz may or may not be ideal. 70Hz is useful for some EMG sources but a lower value has a wider application. The upper range should match your expected PSD of 250 to 500Hz. Since the PSD is asymmetrical the mean nois
I see different values from 0.25 to 1.85 when I connect 40W bulb. What do the numbers mean, Irms A? What's the expected value? How do you calculate AC current from instantaneous sensor output voltage?
The second option is just a blind attempt of producing the output according to the known behaviour of the plant, but do not perform any correction of actual value of output, which in real world could differ from the value expected due to many reasons do not predicted on the ideal plant model, which, no matter how good the model, in certain (...)
I expected a value of some floating point type, but I am always getting 0 instead. Yes, 100 % expectable. You may want to review a C text book about automatic type conversion involved with arithmetic expressions. In this case, language rules require that an integer division is performed and then the quotient converted to float. T
Is "Read the manual" asking too much? For the said UT33A, the AC measurement is specified as Displays effective value of sine wave (mean value response) That could be expected for a non "true rms meter", it's measuring averaged rectified value, result is corrected to be equal with rms for sine voltage. Example, average (...)
The half-bridge applies 12 V peak-to-peak, so 6 V peak. The secondary will receive 6*(220/9.5) = 140 V peak. Since the DVM is calibrated for sine wave the 74 V reading is not unreasonable even if a little lower than expected. If you can't get a true RMS meter, half wave rectify and filter the output, this will give you the true peak value. Accor
Once you have enough memory, as FvM mentioned, the load factor would interfere on the generated output, therefore in my oppinion you should consider storing sinewave tables for different maximum duty-cycles, in order to allow feedback control for compensation of deviations from the expected value at each point of the curve. In addition, as c_mitra
beyond these voltages what will happen to the transformer? In some poor designs where the transformer is sized to operate close to its nominal power rating capacity, a few drop voltage is expected due to losses, therefore if it is the case, it may be expectable a small increase in the output voltage value.
What kind of value should be expected realistically
Hi! The circuit below is not functioning as I'd hoped/expected. This is an experiment making a milli ohmeter, that is the purpose of this circuit; I was unable to breadboard it, or simulate a couple of the ICs, so I just made a prototype to see what would happen, therefore it's very rough and ready. Are there any obvious mistakes in the de