Has anyone seen Lasersabers new motor runs on 1000uf cap

[schuler]

Has anyone tried to use blender 3d modeling tool?
http://www.blender.org/

Blender website says that it has a module for 3d printers.

[TinselKoala]

@Farmhand: Thanks, understood perfectly, so far I think.

For my information to use while fiddling with Arduino code:
As I gather it, then, to interface with an Arduino or other controller we simply need to provide the clock signals from it to the gate inputs shown in the blueprint, right? And we want to be able to vary the timing (delay between "sensor triggered" input and "pulse to mosfets" output) and the dwell (pulse "on" proportion or duty cycle), right?
Can you please sketch a preferred timing diagram for all the mosfet inputs? That would also help to understand the circuit.

Something like this:
Sensor: __________/--------\_____________/---------\_________
MOS1 : ____________/---------\_____________/---------\_______
MOS2 : ----------------\_______/-----------------\________/-------
etc. I'm sure you know what I mean.
thanks--TK

[TinselKoala]

Has anyone tried to use blender 3d modeling tool?
http://www.blender.org/

Blender website says that it has a module for 3d printers.

I've had blender installed for quite a while but the learning curve seems pretty steep and all I've been able to do is make a cube and rotate it ... so that would be a "no" from me.

[TinselKoala]

Wattsup said:

Example from @conradelektro image of his scope (see below). For me the thickness of the rise is showing how the magnets and coils are not perfectly aligned at 60 degrees so you are getting six rises clumped into the same overall instance. This is normal for a hand made wheel, By contrast, the EZ motor should show a thinner and either higher or more intense rise since that motor was made using perfect magnet/coil alignment.

I agree, I think.

One main question will be equal number of coils to magnets or an even/odd mix. I am thinking it will be even/odd as being better because it will really provide the cascade effect to the series coils and not a timed effect on equal coils. That mean two rotors, one with even number and one with odd to experiment the differences.

Not necessarily "odd-even" but "relatively prime", that is with no common factors. Like 5 and 6, or 3 and 5, or 9 and 11. 3 and 6 would not qualify because 6 = 2x3.
7 and 8 are good choices. So you could have an 8-coil stator and rotors with 7 and 8 magnets.
I thought about this too and I dunno. I think if each coil is separately controlled and fired then the relative-prime strategy might be best, but I can't see it working well if all coils are fired at once, like the series or parallel circuits would do.

[Farmhand]

@Farmhand: Thanks, understood perfectly, so far I think.

For my information to use while fiddling with Arduino code:
As I gather it, then, to interface with an Arduino or other controller we simply need to provide the clock signals from it to the gate inputs shown in the blueprint, right? And we want to be able to vary the timing (delay between "sensor triggered" input and "pulse to mosfets" output) and the dwell (pulse "on" proportion or duty cycle), right?
Can you please sketch a preferred timing diagram for all the mosfet inputs? That would also help to understand the circuit.

Something like this:
Sensor: __________/--------\_____________/---------\_________
MOS1 : ____________/---------\_____________/---------\_______
MOS2 : ----------------\_______/-----------------\________/-------
etc. I'm sure you know what I mean.
thanks--TK

Please bear with me if I am seeming to repeat myself, this is to try to help explain it for all TK not just you.  I think i'm trying to explain too many things at once and their relations to each other.

Yeah I know what you mean but there is not really anything to draw. Both Motor switches are in parallel, they switch together, they share a driver chip. I think you mean for a second switching phase, I haven't employed a second switching phase yet. With a fixed sensor the timing would need to be adjusted to suit the rpm and the Pulse width adjusted to limit speed, if a load is detected the pulse width should go to maximum and the voltage automatically boosted via the circuit boost converter till the rpm becomes stable or over idle, all the while keeping timing at optimum, then the setup should adjust values back to keep the rpm at the desired rate.

The way it is now the timing is adjusted by moving the sensor, which works OK for a given load but the pulse width is only optimum when the motor is spinning at the desired rate, when the motor is coming up to speed the PW is always too narrow which is the limiting factor for the power when loaded, if the pulse width widens as the motor is slowed from loading the drop off in torque will be much less or none. Basically when the motor is loaded and slows "as it is" it has less and less power due to less and less PW and so less input power which means the load has more and more slowing effect as the rotor gets slower. If the motor slows the PW needs to widen as it slows to maintain the 40 % duty or optimum duty, when the motor reaches the desired terminal rpm in free running the PW should be auto adjusted back and the input voltage auto adjusted down to keep the rpm at the desired rate, all the while keeping the timing at optimum.

I've made the first part of the video to explain the charging circuit and some other things. Now I'll make part 2 to explain what I missed and show it working.

I think it is quite confusing and as I said I'm not a good explainer, I'm the type of person who doesn't understand why others don't see what I see, so I fail to explain myself properly. I take it for granted that others see what is in my head at times and I know that's not conducive to getting people to see what I see. I don't see dead people or anything  Just working devices. I understand how difficult it is to "get" what a person might be trying to convey at times so all I can do is keep trying. All i can say is that it works and is an obvious improvement to a regular pulse motor when the comparison is so easy, slide the coil away the rotor slows down, slide the coil in close the motor speeds up, but it's not as simple as just adding another motor coil because the extra torque is at extremely low cost, as the magnetizing force is already happening in the charging coil as a result of making an increased voltage for the motor coils and the force is shifted in phase to the motor coils so the input power to the rotor is over a longer period.

I want to forget the inductive return part of the circuit and explain the main thing I made the motor to demonstrate. That is the two driving phases from one switching event using the charging circuit coil to aid the rotation. Everything else is secondary to that principal.

I used Tesla's Ignition coil patent drawing to explain it and the patent should be read to get his explanation of the function of the charging circuit. For those who don't get it yet.

In this video I explain about the charging circuit and how I am applying it to my motor. The next video I'll explain more about the circuitry and show it powering some load and some scope vision to show what I mean about some things.

http://www.youtube.com/watch?v=SUxFHPMa65A

Applying the resonant charging circuit to a motor is a good idea and it works, I don't think anyone has done it like I am doing it before, but i may be mistaken, nonetheless it works and is very useful, as well as particularly and perfectly suited to improve the power/torque of a pulse motor in two or more ways. I am securing a difference in phase between two "series coils" so as to provide a second driving phase from the charging coil as it increases the cap voltage for the motor coils. If people don't "get" it or use it it's their loss, but I'm going to keep explaining it so there is no mistake that the idea to apply the principal to a motor was mine, that the principal is Tesla's charging circuit, and I am open sourcing the application even though I am the only one developing it at this time. I know some will help if they can and I appreciate that more than folks can imagine. It's the basic principal I want to get across first, and show the benefit. With the basic principal understood then my intentions become more obvious. The details can't be considered too much without the principal and the intended application of it being understood.

Cheers