Hi jim

Thank's for your kind words

Yes i am presently developing new projects in some flying systems and i have far less time for the OU research , but still at contact, and as soon as i have some time it is always a great pleasure to dig in.

Laurent

They also dismiss EMJ's shorted coil theory,and although he hasnt shown a working device yet,and he messed up the scope measurements,his theory is sound.

@Tinman - To which Coil Shorting Theory are we referring?

Just so there is no confusion, I have never gone down any Coil Shorting path.

I am very pleased you're getting such good results. You always do good work!

   Chris Sykes
       hyiq.org

@Tinman,

Does your Transistor and Diode Conduct at the same time? If not, what's the time delay between the two?

I believe this is where the confusion over "Shorting" has entered.

   Chris Sykes
       hyiq.org

In a hard switching topology using a transistor and diode, simultaneous conduction occurs as the transistor turns off and if the inductor conducts continuously, cross-conduction occurs when the transistor turns-on.

Just a little off-topic comment that some may find interesting.

I have a Windows 7 computer, first-generation quad core.  For some reason just about every computer I have ever had randomly "eats keyboard characters" when I am typing.  It drives me nuts sometimes.  There is some unknown process that somehow kills characters that should be going into the keyboard buffer.  And the keyboard buffer is pretty much independent from other things going on in the computer which makes it that much harder to explain.  It seems like I have never been able to escape this problem.

Sometimes the "character eating" will remove a full word like "the" or "scope."  It all depends on how fast I can type and how long the "blackout" is.

When you read text, for the average person you read in short complete clumps of words at a time.  The problem when you read back prose that you just composed is that it's also automatically playing back in your head from memory, like a tape recorder.  That can override what you are actually reading.

What can happen is that when you proof read your own text you literally can't see your mistakes, like you are blind.  Between the "reading clumps of words at a time" and the "tape recorder playback" your brain simply fills in the missing words.  Sentences are compromised because whole words are missing but are usually still understandable.  It's a real pain in the butt.

Twice today I had to add missing words to my long posting because I simply could not see the mistakes first go round.  It's very frustrating sometimes because to an outsider you can look grammatically or logically challenged because of course they see all of the mistakes.

Having a keyboard/computer that doesn't eat characters would help.  For me it's like I have to wait about 24 hours to see some errors because I have to substantially forget exactly what I wrote so the "tape recorder playback" is shut off.   So I apologize for the strange looking sentences or other typos, sometime I literally can't see them.

MileHigh

Just a little off-topic comment that some my find interesting.

I have a Windows 7 computer, first-generation quad core.  For some reason just about every computer I have ever had randomly "eats keyboard characters" when I am typing.  It drives me nuts sometimes.  There is some unknown process that somehow kills characters that should be going into the keyboard buffer.  And the keyboard buffer is pretty much independent from other things going on in the computer which makes it that much harder to explain.  It seems like I have never been able to escape this problem.

Sometimes the "character eating" will remove a full word like "the" or "scope."  It all depends on how fast I can type and how long the "blackout" is.

When you read text, for the average person you read in short complete clumps of words at a time.  The problem when you read back prose that you just composed is that it's also automatically playing back in your head from memory, like a tape recorder.  That can override what you are actually reading.

What can happen is that when you proof read your own text you literally can't see your mistakes, like you are blind.  Between the "reading clumps of words at a time" and the "tape recorder playback" your brain simply fills in the missing words.  Sentences are compromised because whole words are missing but are usually still understandable.  It's a real pain in the butt.

Twice today I had to add missing words to my long posting because I simply could not see the mistakes first go round.  It's very frustrating sometimes because to an outsider you can look grammatically or logically challenged because of course they see all of the mistakes.

Having a keyboard/computer that doesn't eat characters would help.  For me it's like I have to wait about 24 hours to see some errors because I have to substantially forget exactly what I wrote so the "tape recorder playback" is shut off.   So I apologize for the strange looking sentences or other typos, sometime I literally can't see them.

MileHigh

@MileHigh,

We all make mistakes and are often prone to missing something that we expect that we did when in-fact we didn't.

You have a serious issue, possible IRQ Conflict: http://www.webopedia.com/quick_ref/IRQnumbers.asp

This interrupt is reserved for the keyboard controller. Even on devices without a keyboard, this interrupt is exclusively for keyboard input.

Lookout for old 1970's Dot Matrix Printers, they will try to share IRQ1 - Hahaha - Possible Hardware Conflict or PEBCAK Error...

Mind you, when an error like this follows, even after replacing Hardware, and the PEBCAK Error has been eliminated then only one FINAL result must be possible.

It seems, through process of elimination, that some Computers will, for ever more, randomly "eat keyboard characters" no matter how much the PEBCAK on the other end tries to eliminate a clearly obvious error.

Many an ID10T has tried to ignore it, but this just is not dealing with the issue at hand!

   Chris Sykes
       hyiq.org

Ha ha, the error you have to worry about is the $B0ZO error.

MileHigh, I immediately thought of you when I saw this:

Tit for tit, I now propose a memoriam on the wise cracks.

See, you don't understand, you have drawn them wrong! How can you comprehend, if you draw them wrong?

   Chris Sykes
       hyiq.org

COME ON GUYS LETS GET ON WITH THIS GREAT DISCOVERY FROM TINMAN. LET US ALL TRY TO CONSTRUCT THIS DEVICE AND GET A BETTER RESULT..