Going back a few posts - to run Garys setup we could instrument with 6 hall sensors in two sets 30 degrees out of phase and just switch those at the same time we switch the main phase wires with any number of off the shelf $0.10 parts. Just TTL signals. In microcontroller time, those mechanical parts are moving at a snails pace.
As far as doing something crazy... I will say this:
If someone knows what the timing should be there is no doubt that I could write the code to drive any motor at any speed in any combination.
Though like georgeycc pointed out, it will be implementation specific - one controller - one motor
The uControllers I am working with these days have a Meg of ram, floating point math, 60 I/0 lines, A/D's, D/A's, counters, comparitors, and the kitchen sink all built in.
They run at 24Mhz, are programmed in C++, and draw less than 1uA standby, generally drawing less 10uA average for a complex program.
They can wake up from sleep for an interupt in 1 microsecond
Running a motor is childs play for these things. Slow as dirt they are.
So if someone wants to wind an old X5 I have a blown X5 I could donate
If someone else wants to instrument that with hall sensors go ahead
Then someone can design the high power board as I think that ish is voodoo. I am a digital guy.
We can get a motor guy to spec out all the timing at lay out the high level requirements for the uC.
I can write code to make **ANYTHING** do whatever I like but....
but...
All that sounds like a whole lot of work :|
I usually favor hacking existing products
In the past I have found that investing a great deal of time in a quasi new idea always lands me dissapointed when some company in China starts selling them for $5 the day after I am done.
I sure like your enthusiasm though! :wink:
-methods