This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
A couple things I need help with:
1) I would like a Spice model of the LM555.
2) Failing that, I would like help with the TLC555 simulation model. It looks like it would get me most of where I'm trying to get, but the parameter VT is undefined, causing errors in the execution of the file.
3) What I'm trying to do is explain why the 555 timer appears to operate correctly for a long duration, but will randomly transition to producing a sinusoidal output at a different frequency. Prevailing theory right now is some sort of EMI problem is causing unstable oscillations, and I was hoping to be able to inject the noise into the simulation profile to try to match the behavior in sim.
Thanks for your quick response, Ron. I kind of assumed the LM555 wouldn't have a model (or you probably would have it on your website's page for that component ; ). As far as using the TLC555 model, I also assumed that it would work but TI-Tina must have a default or specially defined VT parameter that LTSpice does not have. Usually, I have no problems importing a TI model into LTSpice, as LTSpice will run any standard PSpice subcircuit model, but I guess this sim is different enough or something.
I'm going to ask IT to install TI-Tina on my computer, and hopefully they'll get around to it before the universe ends.
We're troubleshooting the connections the timer makes. Sorry about the quality, and also sorry about this technically not being the direct output of the 555 timer (this is coupled through the field director's transformer). Approximate frequency of the 555 timer is ~3.3kHz, and the sine frequency seen is ~20kHz (but 20kHz is the frequency of motor commutation, and is most like EMI. You can see it in the first capture anyways, as those enormous spikes).
I'll give you some application information in case it helps you think of what could be causing this:
The 555 timer feeds several demodulators and a high-power motor's field director. The sinusoid seen is consistent with the motor's turning, and since it's such a high power motor some EMI coupling is expected. The 555 timer's output starts out as a roughly square wave with a little distortion (above) with sharp spikes at the frequency the sinusoid will occur at. The 555 timer actually works, right up until some point (we haven't figured out the trigger that causes this and are still investigating), but eventually this near-perfect sinusoid at the motor frequency replaces the signal. And once the signal is replaced, the square wave behavior doesn't return. Is it possible to latch up the LM555 so that it's output goes high impedance? That effect would match what we are seeing here.
Hi Ron! We did some more testing with the 555 timer. We tried decoupling caps in various locations and values with no change in effect. But we did have success!!
Why the 20kHz jump, I am not sure. I still think the chip is picking the frequency up from the GND line. BUT: the chip is overheating and that is what is causing the transition. We know this because we triggered the transition by heating the component with a heat gun set to low, and reversed the transition (something we had never been able to do prior to isolating to a heating issue) by hitting the 555 with freeze spray.
The 555 timer is driving a 75ohm load, and has a 1uF capacitor in its output to lower the slew rate and prevent large harmonic content from the square wave. The actual power dissipation in the chip is comparatively high to drive the 1uF cap at 3kHz, which is why the chip is overheating. Ron, I would defer to your knowledge of the internals of the chip as to why the 555 timer jumps in frequency, rather than drifts slowly as it heats.
However, removing the capacitor from the output of the 555 timer we no longer see the frequency transition. The 555 timer also runs far cooler to the touch.
Thanks for your help, if you have an explanation for the jump (rather than drift w/ temperature), I know I'd love to hear it, but otherwise I would consider the issue solved. Capacitive load dissipating too much power was the source of the problem.
-Will