Muller Dynamo

[Rawbush]

here is a great video with bias magnets and lenz law. http://www.youtube.com/watch?v=0x46bAPO24I&NR=1

It answers why we see speed up with bias mag in attraction.
Peace
rawbush


after thoughts.. short the coil wire ends.. then position bias magnets to get top speed? Off to the garage

[plengo]

here is a great video with bias magnets and lenz law. http://www.youtube.com/watch?v=0x46bAPO24I&NR=1

It answers why we see speed up with bias mag in attraction.
Peace
rawbush

Thank you. It is very inline with what I have been thinking today.

Fausto.

[slapper]

hi plengo:

guess i've volunteered to be a scope cop on this thread.

There is a problem with your scope probes. You are only reading one of the coils voltage, hence the unbalanced scope shot.

To accurately measure different parts of the circuit you need to isolate one channel of the scope.

I addressed some solutions to this in an article in Syscomp...

http://www.syscompdesign.com/AppNotes/current-measurement.pdf

I hope this link takes you there... if not look under app notes, customer applications and circuits.

Ron

Ron has a point. me thinks you've got a ground issue that needs to be resolved.

per your schematic you are fine, however you have several other ground/neutral connections that could cause problems.

your external volt meter across your output load, your external power supply, your arduino eval board through the usb
all could be influencing the scope shot.

you could say that your input drive control hardware and your output circuitry is completely isolated from each other but
that is probably not the case.

the common leads off the 2 probes are most likely connected to your laptop/pc neutral/ground/common. your arduino is
also connected to the same system ground of which your power supply is connected to run your drive coils.

the output from your power supply may or may not be isolated from ground. your voltmeter leads may also not be isolated
from ground as well.

lets start by trying to disconnect the usb and run your controller standalone so, at least, we can get past this part.

thanks for all the good work guys.

take care.

nap

[Rawbush]

I shorted one coil set (series adding) and ran motor to top speed.
768 rpm
added a 3/8 dia neo (same size in rotor) to top coil
955 rpm
added 3/8 neo to bottom coil
1067 rpm

Turned on battery charger to keep battery bank full so i/p was a little higher
shorted coil top speed
910 rpm
added a 1" dia neo and got 1340 rpm
went to add a bottom one and motor stopped. I think the neo was interfearing with the hall switch..lol I will have to try on another set of coils. But I think were on to something here.
Peace
rawbush

[mondrasek]

@ M

Well, it is theoretically the same thing, but as i said i can't get any measurable signal out of that coil as can be seen in Plengo`s video.
If i put the scope across one i/p of the coil and the center point that connects the
two coils then i see the in-phase currents from one coil.

I wonder why Plengo sees any currents/voltages at all, because
if he had a mismatch of 0.001H between the 2 coils, he would only see millivolts induced.

It must be about the magnet being inbetween the coils and of course the windings carrying the opposite currents not being physically close.
As i understand it Plengo has his top coil clockwise and his bottom coil counter-clockwise wound. The flux direction that each coil sees is the same (in theory)

One thing is for sure the bucking coils ARE capable of creating a magnetic field individually (as Naudin showed) (during the Lenz establishment for example)
My bifilar coil CANNOT create a magnetic field. That is the major difference that i see.

@X,  are you measuring the output of a coil pair after recifying through a FWBR and then into a (VERY LARGE CAPACITY) dump cap?

Those elements are what trigger this system. 

They must be in your circuit or it will not work.

M.

PS. The last few comments were for the benefit of the rest of the audience.  No offence intended toward you, X.  You are obviously doing a great job and I thank you for everything you are adding to our knowledge base.