Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
The terminology used above would be wrong if the analysis were made in a time domain P(t), but we are considering the power varying on an ascendent slope as a function of current P(i) - linear for BJT [P=k.I] and quadratic for MOSFET[ P =K.I2 ]; In any case, read min as initial and max as final...
I also did the same rough estimation, but with a little modification. It should be considered that the MOSFET current rises in a non linear shape, so we should calculate the RMS power, not the instantaneous one, and the average power would be rather somethink like this (If I'm not mistaken)...
If I were you, I wouldn't spend a second debugging a code like this, which in addition to being poorly written ( goto's should be avoided as much as possible ), it is also not quite intelligible.
Did you see what appears on Device Manager panel on the devices tree ( assuming you are on Windows ) ?
If so, did you check if at least what error was diagnosed and/or if some device ID was caught ?
If so, did you search for its device driver somewhere ?
No, don't ever put anything between I2C and microcontroler. You are dealing with low level, high impedance signals, keep in mind that I2C buses are intended to be used at the same board. In addition, there is no decoupling ceramic capacitors at the power bus.
Rather, a function pointer; I built this code, adapted from an example took elsewhere. It essentially allows calling some function, enclosed by portxxxxx_CRITICAL functions, where the function in the argument is a general assignment function allowing any value and destination variable.
I'm not...
Hi there,
I'm refactoring a program that deals with a lot of variables being asynchronously shared among different Tasks.
This is done enclosing them with spinlocks functions this way:
portENTER_CRITICAL(mux);
SharedVariable1 = value1;
// ...
SharedVariableN = valueN;
portEXIT_CRITICAL(mux)...
Every part ehxibit capacitance, inductance and resistence in some extent ( sorry, a general question deserves a general answer ).
Seriously speaking: The equations that govern the operation of any alternating current circuit are the same regardless of how you name such components as Capacitor...
There is no straight response, you need to perform some investigation there to find the suited part to disconnect and inject the external power supply.
You need to see the circuit working, or at least attempting to work to minimaly understand if the problem is on the logic side (PWM IC), in...
Yes...not to burn everything; its a usual procedure in cases like this, unless you have some better idea to put the inverter to work with a limited current, other than with the gigantic capacity of the lead acid battery; If it is capable of igniting a vehicle engine, imagine what it cannot do...
If I were you, on the next repairing 'iteration' I would consider somehow opening the DC bus (battery, charger) and feed the 12v through an external power supply, current protected. Anyway, did you make the test after repair with a small or no load?
The analysis of the operational amplifier's transfer function follows the same script: Determine the nodes of the input branch and the output branch, and then divide the voltage drop of both (Vo - V- )/(V-- Vi ). At the end it is pure algebraic manipulation.
I wonder how one ask this question not giving any relevant information related to the topic...What CAD? Have footprint libraries? Previous experience? 1 or 2 Layers? Size constraint? How urgent is this and what is your level of involvement? How etc...? As you can see, it has not a straight answer.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.