Overunity.com Archives is Temporarily on Read Mode Only!



Free Energy will change the World - Free Energy will stop Climate Change - Free Energy will give us hope
and we will not surrender until free energy will be enabled all over the world, to power planes, cars, ships and trains.
Free energy will help the poor to become independent of needing expensive fuels.
So all in all Free energy will bring far more peace to the world than any other invention has already brought to the world.
Those beautiful words were written by Stefan Hartmann/Owner/Admin at overunity.com
Unfortunately now, Stefan Hartmann is very ill and He needs our help
Stefan wanted that I have all these massive data to get it back online
even being as ill as Stefan is, he transferred all databases and folders
that without his help, this Forum Archives would have never been published here
so, please, as the Webmaster and Creator of these Archives, I am asking that you help him
by making a donation on the Paypal Button above.
You can visit us or register at my main site at:
Overunity Machines Forum



Kapanadze Cousin - DALLY FREE ENERGY

Started by 27Bubba, September 18, 2012, 02:17:22 PM

Previous topic - Next topic

0 Members and 159 Guests are viewing this topic.

verpies

Quote from: NickZ on March 23, 2017, 11:46:16 AM
I thought that the purpose of the driver chip was to assure that both mosfets don't fire at the same time. 
No, the purpose of the driver chips is to provide more current to gates of the MOSFETs.

It is the job of the PWM Controller (in your case the TL494) to time the driver chips+MOSFETs properly, including the dead-time between them.  Unfortunately you are misusing the dead-time control input as a duty cycle control input.

NickZ

Quote from: verpies on March 24, 2017, 04:10:43 AM
No, the purpose of the driver chips is to provide more current to gates of the MOSFETs.

It is the job of the PWM Controller (in your case the TL494) to time the driver chips+MOSFETs properly, including the dead-time between them.  Unfortunately you are misusing the dead-time control input as a duty cycle control input.
Verpies
   Are you saying that I've made a mistake on the connections, or that the topruslan7 schematic is wrong.
What should I do about it? And why? Please explain.
Is the video I posted a link to "How to use a TL494" also not showing the dead time? As it is showing the same thing, pulses between the peaks, same as mine.
  I'll change whatever needs changing, just let me know what actually is not right, and why.

  Edit: what I see as not being the same as in the topruslan 7 schematc, is that my 50k pot is installed backwards. That is the #3 pot pin (which is the ground pin), is going to the TL494 #7 pin. And it should be that the pots #1 pin should go to the TL494 #7 pin, instead. Or not?
Should I reverse the pot?

lost_bro

Quote from: NickZ on March 24, 2017, 09:50:11 AM
   Are you saying that I've made a mistake on the connections, or that the topruslan7 schematic is wrong.
As I'm not the only one seeing the TL chip working in this way. You mention that there is a huge pause between the push and the pull. And now, that I'm misusing the purpose of the TL controller.
What should I do about it? And why? Please explain.
Is the schematic wrong, or what? Is the video I posted a link to "How to use a TL494" also not showing the dead time? As it is showing the same thing, pulses between the peaks, same as mine.
  I'll change whatever needs changing, just let me know what actually is not right, and why.

  Edit: what I see as not being the same as in the schematc, is that my 50k pot is installed backwards. That is the #3 pot pin is going to the TL494 #7 pin. And it should be that the pots #1 pin should go to the TL494 #7 pin, instead.
Should I reverse the pot?

Good day NickZ

Please see attached TL494 layout.
Normally the d/c (duty cycle) control for the TL494 IC is connected to Error Amp 1.
Pin#4 is used to determine *DeadTime* which is the OFF time that occurs between the Push-Pull outputs *MarkTime* (on-time).
This is accomplished by tying Pin#4 to *ground* with the appropriate value resistor.  Further down in the attached spec. sheet for the TL494 you will find a chart depicting Timing Capacitor values and inherent DeadTime vs. Oscillator Freq.

The Tl494 chip architecture guarantees a certain percentage of DeadTime according the the chosen values of CT (oscillator timing cap. Pin#5) & RT (oscillator timing resistor, Pin#6). By changing these values a certain value for DeadTime can also be had.

By connecting a *pot* to Pin#4 you are basically manipulating the *DeadTime* to create your variable pulse width (d/c).
While this can done, it is NOT the standard engineering/design protocol. I would opt to use Pin#4 for *DeadTime* control and use error amp 1 for d/c control.

I hope this helps;

take care,peace
lost_bro


itsu


Nick,

so, use the leftmost circuit, not the one on the right as it is (mis)using the dead-time control input (pin 4) as a duty cycle control input.

Itsu

AlienGrey

Quote from: itsu on March 24, 2017, 12:21:08 PM
Nick,

so, use the leftmost circuit, not the one on the right as it is (mis)using the dead-time control input (pin 4) as a duty cycle control input.

Itsu
it might seem a strange thing here to say or ask here but what does this part of the circuit do ??? One might think the 17.68 khz is 100 times the 'F' of the Tesla coil 'yeah' but its free running and not locked in frequency or phase ! Also in other devices the push pull is used to demodulate the 'F' to 50 or 60 hz grid frequency and also isn't the Tesla coil the wrong way round since we are counting power peeks and not the other way round ? any one any ideas ?