I finished putting together a housing for a single driver. CNC milled aluminum goodness:

The machining was done in two operations. All the fancy 3d profiling was done with the part flipped over and held in soft jaws.

Front side:

Back side, before gluing in the magnets:

Here's the assembled driver. I'm using a cheap off-the-shelf pair of earpads.

This version sounded pretty terrible. The pcbway flex-pcb was way too thick, making it both too heavy and too stiff. The response was way to heavy at low frequencies, with a terrible ~100 hz resonance, and there were all sorts of weird notches in the frequency response. But it did make sound, so that was a good start.

I ordered some Pyralux samples from Dupont, and tried etching my own drivers. I first tried with the LF7012R variety, which has 1/2 oz copper, 13 micron kapton layer, and 13 micron adhesive. I measured the total thickness to be 45 microns where there was copper, and ~25 microns without copper, which is half the thickness of the pcbway material. At the time I thought that was their thinnest material, but I hadn't looked through their datasheets carefully enough. The AC 091200EV material has 1/4 oz copper, 12 micron kapton, and no adhesive layer, so it should be in total something like 20-25 microns thick with copper, and 12 without. I've got a sample of that on the way, and will report back when I've etched some.

After a few tries I figured out a pretty good process for etching the pyralux. I did the classic toner transfer and ferric chloride etching method. The etching part worked really well, but doing the toner transfer proved finicky. It took a few tries with a few different laser printers to get the process to work.

Etched:

Assembled into the driver:

This one sounds much, much better, although there's definitely still a little weirdness going on. Listening to it plugged into a function generator and sweeping frequencies, the low-frequency resonance is gone, and over all it's much flatter, but there are still some strange notches in the response. Unfortunately I don't have a good setup for quantifying the frequency response at the moment, but it's definitely a little off right now. But it's getting better. I'm hopeful that the even thinner flex pcb material will improve the situation further. Reducing tension in the membrane might help as well.

## September 17, 2017

## September 1, 2017

### Dynamometer Database

Now that I have a good process for collecting data on the motor dynamometer, and the appropriate scripts for quickly processing the data, I put up a page dedicated to motor dyno data. You can also find it in the navigation bar up top. There's only ~~one motor~~ two motors on it right now, but it will slowly get populated as I get a chance to run more tests.

I'm not sure if anyone else will actually find this useful, but it seems like there's a growing number of people doing legitimate robotics and other cool stuff with hobby-grade motors, so I might as well share what data I've got.

I'm not sure if anyone else will actually find this useful, but it seems like there's a growing number of people doing legitimate robotics and other cool stuff with hobby-grade motors, so I might as well share what data I've got.

## August 20, 2017

### Planar Magnetic Headphones, Part 1

A brief break from 3-phase electric motors, for a different kind of electromagnetic actuator.

Planar magnetic (a.k.a. "orthodynamic", "isodynamic", etc) drivers are a pretty neat topology of linear motor, which, as far as I can tell, has found no application besides speakers and headphones. Here's a well-diagrammed explanation of how they work.

Instead of a voicecoil actuator which drives a stiff cone back and forth, like a conventional speaker driver, a thin membrane with conductive traces sandwiched within a funny magnet arrangement moves back and forth.

I won't try to argue that this is "better" than a conventional driver in any way, because frankly I don't care. It is cool, though, and also a perfect excuse to send out for some flex-PCB's, which my go-to PCB vendor, PCBWay, recently started offering for quite reasonable prices

I started out by playing with magnet arrangements in FEMM, to see how sensitive this arrangement was to changes in magnet dimensions and spacing, and I ended up here:

This uses 1/8" square N52 magnets, with a 2mm airgap, and 9mm pitch. The array 2 inches long (into the page), and each bar is a pair of 1/8" x 1/8" x 1" magnets, which are cheaply available on ebay:

Here's the tangential flux density (which is the normal force producing component) in the middle of the air gap:

Doubling the depth of the magnets got it up to .5T peak (the path around the magnet gets longer, so less flux leaks through it), but I decided it wasn't worth the more than double magnet cost (they are harder to find magnetized through the small face).

Here's what the actual flex pcb coil looks like. The traces go up and down in the regions of ±.35T field in the plot above. This was very unpleasant to draw in Eagle. 0.25mm trace width with .5mm pitch. PCBWay claims to be able to do .1mm between traces, but I didn't want to push it.

For the actual PCB, I chose single layer, 75µm flexible adhesiveless base, .1mm FPC thickness, no solder mask, and 1/3 oz copper, to keep the board as light and flexible as possible. Maybe a 2-sided trace would have been better, for a higher ratio of conductor to pcb material, but this whole thing is an experiment anyway.

Front: A few of them came out a little wrinkly. Not sure why, or if it will cause problems. In retrospect, it might have been a good idea to put a thick copper trace around the outside of the whole board, to stiffen up the perimeter. Coil resistance came out to 16 ohms.

Back:

Planar magnetic (a.k.a. "orthodynamic", "isodynamic", etc) drivers are a pretty neat topology of linear motor, which, as far as I can tell, has found no application besides speakers and headphones. Here's a well-diagrammed explanation of how they work.

Instead of a voicecoil actuator which drives a stiff cone back and forth, like a conventional speaker driver, a thin membrane with conductive traces sandwiched within a funny magnet arrangement moves back and forth.

image credit: innerfidelity.com |

I started out by playing with magnet arrangements in FEMM, to see how sensitive this arrangement was to changes in magnet dimensions and spacing, and I ended up here:

This uses 1/8" square N52 magnets, with a 2mm airgap, and 9mm pitch. The array 2 inches long (into the page), and each bar is a pair of 1/8" x 1/8" x 1" magnets, which are cheaply available on ebay:

Here's the tangential flux density (which is the normal force producing component) in the middle of the air gap:

Doubling the depth of the magnets got it up to .5T peak (the path around the magnet gets longer, so less flux leaks through it), but I decided it wasn't worth the more than double magnet cost (they are harder to find magnetized through the small face).

Here's what the actual flex pcb coil looks like. The traces go up and down in the regions of ±.35T field in the plot above. This was very unpleasant to draw in Eagle. 0.25mm trace width with .5mm pitch. PCBWay claims to be able to do .1mm between traces, but I didn't want to push it.

For the actual PCB, I chose single layer, 75µm flexible adhesiveless base, .1mm FPC thickness, no solder mask, and 1/3 oz copper, to keep the board as light and flexible as possible. Maybe a 2-sided trace would have been better, for a higher ratio of conductor to pcb material, but this whole thing is an experiment anyway.

Front: A few of them came out a little wrinkly. Not sure why, or if it will cause problems. In retrospect, it might have been a good idea to put a thick copper trace around the outside of the whole board, to stiffen up the perimeter. Coil resistance came out to 16 ohms.

Back:

I CNC milled half of a housing out of some Delrin:

Glued in the magnets:

There's a lip on the housing that will apply some tension to the flex pcb to hold it flat, once both halves of the housing are made, but it was secure enough for some testing with only one half.

It actually works even with only half of the magnet arrangement - half the magnet gets you half the flux density. It should produce the same volume on roughly half the power, once the whole thing is assembled.

I'll reserve qualitative judgement until the whole thing is assembled, but from the brief testing I've done on this single partially assembled driver, it seems promising.

## August 13, 2017

### Reamer Regrinding

In the near future I'll need to make a bunch of things with tight-tolerance 22 mm bores, so instead of buying a 22 mm reamer, or just boring the holes like a normal person, I tried out re-grinding a 7/8" reamer (22.225 mm) reamer down to 20 mm by setting up my toolpost spindle as a toolpost grinder.

Here's the setup:

The reamer is set up between centers, and the toolpost spindle has a 4" grinding wheel on an arbor. There's a mist-coolant dispenser to keep everything cool and lubricated. The center on the chuck-side was turned in place out of some steel scrap, to ensure its concentricity with the spindle.

Here's the setup:

The reamer is set up between centers, and the toolpost spindle has a 4" grinding wheel on an arbor. There's a mist-coolant dispenser to keep everything cool and lubricated. The center on the chuck-side was turned in place out of some steel scrap, to ensure its concentricity with the spindle.

a

All together it turned out pretty well. I turned down the shank and ground it as well, so it will fit in the lathe's drill chuck.

I overshot my target 22 mm by 5 microns, but that's not too shabby, considering the ticks on the lathe's cross slide are 25.4 microns each. It seems to cut a tiny bit oversized, so it works out in the end to give me a

*very*tight slip fit onto a 20mm ground shaft.
This method leaves no relief behind the cutting edges, so as you might expect, they drag a little bit. The surface finish inside the bore is okay, but definitely not as nice as I'm used to getting with reamers. Over all, this was definitely way more time and effort than just boring the holes like I normally would, but it was a fun exercise, and good to get some experience using a toolpost grinder.

## May 30, 2017

### Vector Hysteresis FOC

Here's round 3 of wrapping up draft blog posts I've been sitting on for a while.

This came out of thinking about sliding mode control and direct torque control, thanks to the nonlinear controls class I took this past term. I did a more formal writeup for my final paper for the class, in the (unlikely) case you find that a more readable format.

In a typical FOC implementation, phase currents are measured and transformed into the rotor frame to get d and q axis currents. Then two PI loops are run to control the d and q currents, with some feed-forward deal with the coupling between the voltage equations. The two PI controllers output d and q voltages, which are transformed back to the stator frame, and approximated with PWM.

This usually works great, but here's another controller I thought of which is (maybe) conceptually easier, and requires no controller design or gain calculating to work. In fact, it doesn't even use any motor parameters. And it doesn't even use PWM. At every step, it just picks which switches to turn on and off. Because of how it works, it's quite robust to changing parameters, like the motor's inductance changing when it saturates. Also, it has as fast as possible response given the open-loop dynamics of the motor.

The basic idea is as follows: Given the position of the rotor and errors in d and q currents, which switches should be turned on and off to make the error decrease as fast as possible?

Every loop cycle, the controller measures current, looks at the error and where the rotor is, and chooses the switch states that send the current error towards zero the fastest.

While it probably looks very confusing at first, I think the vector diagram below best explains the situation:

First, there are six vectors drawn in black, V1-V6, which represent the six stator voltage vectors. Each of these corresponds to a set of switch-states. The states with all switches on or all switches off are not used. Then there's the ĩ vector in blue, which is the vector sum of the d and q current errors. In red is the (negative of the) vector from motor dynamics, minus inductance. Looking at the motor voltage equations in d and q:

$$V_{d} = R_{d}i_{d} + L_{d}\frac{d i_{d}}{dt} - \omega L_{q}i_{q}$$

$$V_{q} = R_{q}i_{q} + L_{q}\frac{d i_{q}}{dt} + \omega(L_{d}i_{d} + \lambda_{r})$$

The intuition is, pick the stator voltage vector which causes the di/dt vector to be in the right direction. The "right" direction is the direction of the error vector, ĩ. In the 1-D case, if error is positive, that means that actual current is less than desired current, so di/dt should be positive to cause current to increase.

To pick the right set of switch states, just take the dot product of the error vector and the six stator vectors, and then pick the switch state corresponding to the largest dot product. But wait, that's not the right thing to do, is it? Shouldn't I be picking the switch state which causes the dot product of the di/dt vectors and error vector to be the largest? Yes, but fortunately these two decisions are actually the same. Vdynamics is added to all the stator vectors, and dot products distribute. So you can ignore the Vdynamics vector, and just pick based on the stator voltage vectors and the error vector.

To limit switching frequency, you can also add a "hysteresis circle" around the origin. As in, if the error vector lies within the circle, don't change switch states:

Does it actually work?

Well, my motor model says it does. This is also using a motor model which includes a lookup table for inductance and flux linkage saturation. The motor parameters are from a KIA hybrid starter generator at 160 volts, with switching frequency limited to 15 kHz. I also threw in some real hardware effects like a few amps of noise on the current sensors, and 12 μs of propagation delay (which occurs in the Toyota Prius inverter).

Here's what phase current looks like at ~20 phase amps. As expected, it has way more ripple than a linear controller would, since the minimum switch on-time is one loop period, but it's quite tolerable - especially given the 200A max current of this system.

This is an electric go kart started by Bayley and Nick last summer, with lots of work by myself and other MITERS-folk in it as well. Eventually it will get its own thorough documentation but, but as a brief overview, it's a stock shifter kart frame, with the motor from a KIA hybrid, the inverter from a Prius, the battery from a Battlebot, and a bunch of custom motor control logic.

So how'd it work? Here's 20 phase amps on the actual motor, as measured by LEM-stick. Hey, that plot looks really familiar!

And here's a log from spinning up the wheels off the ground. d-axis current stops tracking around 1000 rad/s, because the reference currents were generated using an in correct inductance. So the commanded trajectory was actually un-trackable.

Qualitatively, it performed quite well. It produces an audible white-noise hiss from the extra current ripple. 1600 rad/s in the plot above corresponds to a ground speed of over 130 mph, although in reality on the ground the kart won't have the power (nor the space, in Cambridge at least) to go that fast. Yet.

To make if very clear, this type of controller is often not feasible to implement - for small hobby motors, for example, the inductance is too low for this to work with reasonable loop frequencies. This is one reason PWM is great - the timing resolution of when the switches turn on and off is dictated by a super-fast timer that runs in the background, rather than by the timing of the control loop. So for a given loop rate, normal PWM-based approaches will have way less current ripple than this controller. But for some motors (in particular high-inductance motors like those in electric cars), the numbers actually work out fairly favorably, and you can get away with running this controller at reasonable speeds.

There are certainly some improvements that could be made to this by including motor parameters to reduce current ripple, but I haven't tried any of them out yet.

Also, I thought I was really cool and came up with something new here, but (unsurprisingly) it turns out other people have already done similar things. Although they don't put it on hardware.

This came out of thinking about sliding mode control and direct torque control, thanks to the nonlinear controls class I took this past term. I did a more formal writeup for my final paper for the class, in the (unlikely) case you find that a more readable format.

In a typical FOC implementation, phase currents are measured and transformed into the rotor frame to get d and q axis currents. Then two PI loops are run to control the d and q currents, with some feed-forward deal with the coupling between the voltage equations. The two PI controllers output d and q voltages, which are transformed back to the stator frame, and approximated with PWM.

This usually works great, but here's another controller I thought of which is (maybe) conceptually easier, and requires no controller design or gain calculating to work. In fact, it doesn't even use any motor parameters. And it doesn't even use PWM. At every step, it just picks which switches to turn on and off. Because of how it works, it's quite robust to changing parameters, like the motor's inductance changing when it saturates. Also, it has as fast as possible response given the open-loop dynamics of the motor.

The basic idea is as follows: Given the position of the rotor and errors in d and q currents, which switches should be turned on and off to make the error decrease as fast as possible?

Every loop cycle, the controller measures current, looks at the error and where the rotor is, and chooses the switch states that send the current error towards zero the fastest.

While it probably looks very confusing at first, I think the vector diagram below best explains the situation:

First, there are six vectors drawn in black, V1-V6, which represent the six stator voltage vectors. Each of these corresponds to a set of switch-states. The states with all switches on or all switches off are not used. Then there's the ĩ vector in blue, which is the vector sum of the d and q current errors. In red is the (negative of the) vector from motor dynamics, minus inductance. Looking at the motor voltage equations in d and q:

$$V_{d} = R_{d}i_{d} + L_{d}\frac{d i_{d}}{dt} - \omega L_{q}i_{q}$$

$$V_{q} = R_{q}i_{q} + L_{q}\frac{d i_{q}}{dt} + \omega(L_{d}i_{d} + \lambda_{r})$$

Vdynamics is equal to the vector sum of

$$ -R_{d}i_{d} + \omega L_{q}i_{q}$$

and

$$-R_{q}i_{q} - \omega(L_{d}i_{d} + \lambda_{r})$$

in the d and q directions, respectively.

If the d-axis component of stator voltage plus the d-axis component of the dynamics is positive, then id will increase, and the same for the q axis.

The green vectors are di/dt scaled by inductance - mostly their direction is what matters. Given a dynamics vector and one of the stator vectors, the six di/dt vectors are the possible directions the current will change in.

Basically:

$$V_{stator} + V_{dynamics} = L\frac{d i}{dt}$$

and

$$-R_{q}i_{q} - \omega(L_{d}i_{d} + \lambda_{r})$$

in the d and q directions, respectively.

If the d-axis component of stator voltage plus the d-axis component of the dynamics is positive, then id will increase, and the same for the q axis.

The green vectors are di/dt scaled by inductance - mostly their direction is what matters. Given a dynamics vector and one of the stator vectors, the six di/dt vectors are the possible directions the current will change in.

Basically:

$$V_{stator} + V_{dynamics} = L\frac{d i}{dt}$$

The intuition is, pick the stator voltage vector which causes the di/dt vector to be in the right direction. The "right" direction is the direction of the error vector, ĩ. In the 1-D case, if error is positive, that means that actual current is less than desired current, so di/dt should be positive to cause current to increase.

To pick the right set of switch states, just take the dot product of the error vector and the six stator vectors, and then pick the switch state corresponding to the largest dot product. But wait, that's not the right thing to do, is it? Shouldn't I be picking the switch state which causes the dot product of the di/dt vectors and error vector to be the largest? Yes, but fortunately these two decisions are actually the same. Vdynamics is added to all the stator vectors, and dot products distribute. So you can ignore the Vdynamics vector, and just pick based on the stator voltage vectors and the error vector.

To limit switching frequency, you can also add a "hysteresis circle" around the origin. As in, if the error vector lies within the circle, don't change switch states:

Does it actually work?

Well, my motor model says it does. This is also using a motor model which includes a lookup table for inductance and flux linkage saturation. The motor parameters are from a KIA hybrid starter generator at 160 volts, with switching frequency limited to 15 kHz. I also threw in some real hardware effects like a few amps of noise on the current sensors, and 12 μs of propagation delay (which occurs in the Toyota Prius inverter).

Here's what phase current looks like at ~20 phase amps. As expected, it has way more ripple than a linear controller would, since the minimum switch on-time is one loop period, but it's quite tolerable - especially given the 200A max current of this system.

"It works is simulation" is where most people would have stopped, especially for a class project, but what's the point of controls if you don't put it on hardware? And then ride your hardware:

So how'd it work? Here's 20 phase amps on the actual motor, as measured by LEM-stick. Hey, that plot looks really familiar!

And here's a log from spinning up the wheels off the ground. d-axis current stops tracking around 1000 rad/s, because the reference currents were generated using an in correct inductance. So the commanded trajectory was actually un-trackable.

Qualitatively, it performed quite well. It produces an audible white-noise hiss from the extra current ripple. 1600 rad/s in the plot above corresponds to a ground speed of over 130 mph, although in reality on the ground the kart won't have the power (nor the space, in Cambridge at least) to go that fast. Yet.

To make if very clear, this type of controller is often not feasible to implement - for small hobby motors, for example, the inductance is too low for this to work with reasonable loop frequencies. This is one reason PWM is great - the timing resolution of when the switches turn on and off is dictated by a super-fast timer that runs in the background, rather than by the timing of the control loop. So for a given loop rate, normal PWM-based approaches will have way less current ripple than this controller. But for some motors (in particular high-inductance motors like those in electric cars), the numbers actually work out fairly favorably, and you can get away with running this controller at reasonable speeds.

There are certainly some improvements that could be made to this by including motor parameters to reduce current ripple, but I haven't tried any of them out yet.

Also, I thought I was really cool and came up with something new here, but (unsurprisingly) it turns out other people have already done similar things. Although they don't put it on hardware.

### Toolpost Spindle, Part 2

I've mostly finished the toolpost spindle.

I found the perfect spindle motor on All Electronics, of all places, for $17. It's a very cute brushless inrunner. I dyno-ed it at 500 watts peak output at 48V, running of a 17A sensorless e-bike motor controller. I forgot to take a picture of the inside, but the rotor has a thin steel sleeve around it, so the magnets won't fly off the rotor at high speed. So I'm not worried about running it at 48V, even though it's nominally a 24V or so motor.

Unfortunately, none of my motor controllers are quite the right for this thing. I wanted ~48 V, 10-20 amps, with hall sensor position feedback, and closed-loop speed control. Fortunately, Charles and Bayley recently acquired a massive pile of mostly-not-working hoverboards. The motor controllers in hoverboards pretty much exactly fit the bill. They even do closed loop speed control with hall feedback! I did a little investigation, and it seems like they run ST's motor library, doing dual-FOC on an STM32F103. At low, speeds, they block-commutate, and at high speeds the phase currents become sinusoidal once they can interpolate between hall edges.

Phase current at low speed, scoped with the LEM-Stick:

Phase current at higher speed:

Fortunately, other people have figured out the serial protocol the hoverboard controllers use, so it was fairly straightforward to get it spinning the motor.

Unfotunately, the hall effect sensors in the All Electronics motor had very advanced timing, in the wrong direction for my application. I opened up the motor, broke the glue holding down the hall sensor PCB, and reversed the timing:

I CNC milled an aluminum connector housing, for a DB25 connector. Each phase has 6 parallel pins, plus 5 pins for hall sensors: The steel front plate was made with a Bridgeport and hand files to match the motor curvature. The 2-stepped HTD pulley was done on the CNC mill.

I made a height adjuster out of a chunk of steel. I still need to make a nice thumbwheel for it.

I shoved a Nucleo and the hoverboard controller into the shell of an old G5 Mac Mini. The power button on the left also came from a hoverboard, and I found an appropriately labeled knob to stick on the speed potentiometer:

Here it is mounted on the toolpost. The spacing between the two pulleys is fixed, and I was able to choose the two sets of pulleys to have almost exactly the same center distances and belt lengths, so there's no need for a belt tensioner:

I've used it for a few jobs so far., including in-place drilling a bolt patterns into a big pulley and hub I turned, and also for deburring some internal ring gears:

I found the perfect spindle motor on All Electronics, of all places, for $17. It's a very cute brushless inrunner. I dyno-ed it at 500 watts peak output at 48V, running of a 17A sensorless e-bike motor controller. I forgot to take a picture of the inside, but the rotor has a thin steel sleeve around it, so the magnets won't fly off the rotor at high speed. So I'm not worried about running it at 48V, even though it's nominally a 24V or so motor.

Unfortunately, none of my motor controllers are quite the right for this thing. I wanted ~48 V, 10-20 amps, with hall sensor position feedback, and closed-loop speed control. Fortunately, Charles and Bayley recently acquired a massive pile of mostly-not-working hoverboards. The motor controllers in hoverboards pretty much exactly fit the bill. They even do closed loop speed control with hall feedback! I did a little investigation, and it seems like they run ST's motor library, doing dual-FOC on an STM32F103. At low, speeds, they block-commutate, and at high speeds the phase currents become sinusoidal once they can interpolate between hall edges.

Phase current at low speed, scoped with the LEM-Stick:

Phase current at higher speed:

Fortunately, other people have figured out the serial protocol the hoverboard controllers use, so it was fairly straightforward to get it spinning the motor.

Unfotunately, the hall effect sensors in the All Electronics motor had very advanced timing, in the wrong direction for my application. I opened up the motor, broke the glue holding down the hall sensor PCB, and reversed the timing:

I CNC milled an aluminum connector housing, for a DB25 connector. Each phase has 6 parallel pins, plus 5 pins for hall sensors: The steel front plate was made with a Bridgeport and hand files to match the motor curvature. The 2-stepped HTD pulley was done on the CNC mill.

I made a height adjuster out of a chunk of steel. I still need to make a nice thumbwheel for it.

I shoved a Nucleo and the hoverboard controller into the shell of an old G5 Mac Mini. The power button on the left also came from a hoverboard, and I found an appropriately labeled knob to stick on the speed potentiometer:

Here it is mounted on the toolpost. The spacing between the two pulleys is fixed, and I was able to choose the two sets of pulleys to have almost exactly the same center distances and belt lengths, so there's no need for a belt tensioner:

I've used it for a few jobs so far., including in-place drilling a bolt patterns into a big pulley and hub I turned, and also for deburring some internal ring gears:

## May 29, 2017

### Motor Dyno Efficiency Mapping

I finished up the code for automatically generating and post-processing efficiency maps on the motor dyno. You give it a maximum speed, a maximum command vs speed, and number of points to sample in speed and command, and it auto-generates a time-stamped .csv file my dyno software can read. Then the dyno plays back the time series, and logs the data. To extract the points of interest, the log has a flag in it, which is set to 1 after each operating point has settled, and 0 the rest of the time. The post-processing script just finds all the intervals where the flag is 1, averages all the samples collected over that period, and combines them into one point. So each point on the efficiency map is from several seconds of data.

Here's a video clip showing part of the process. The motor being tested is a cheap knock-off of a Tiger Motor U8, at 22 volts, and 22 peak phase amps.

Here's the scatter plot of data points tested during the efficiency map:

And here's the data interpolated into a surface, in the classic efficiency map style:

I wouldn't read too much into the relatively low numbers (~74% peak efficiency), as this test was only at 22V and high peak current and these motors are good to spin much faster on more volts.

Also, some time soon I'm going to add a motor data page to the site, with whatever data I pull off the dyno on it, so keep your eye on the top bar. I figure it might eventually be a useful resource, to have a page with lots of electric motor performance curves, efficiency maps, etc. on it.

Subscribe to:
Posts (Atom)