After sending out 108 more ballots and receiving 12 returns, the results of the second round of voting are as follows:
10 Jeff Epler 10 Chris Radek 9 Alex Joni 8 John Kasunich 4 Stephen Wille Padnos 3 Sam Sokolik 3 Dan Falck
47 of 540 votes were cast.
Combining these with the results of the first round of voting, the final results are:
First Round Second Round Total 63 9 72 Alex Joni 60 10 70 Chris Radek 58 8 66 John Kasunich 55 10 65 Jeff Epler 43 4 47 Stephen Wille Padnos 28 3 31 Sam Sokolik 25 3 28 Dan Falck
After two rounds of voting the newly elected members of the EMC BoardOfDirectors are
Stephen Wille Padnos
Congratulations, once again.
Hi all, it's time to have another election for the Board of Directors.
The first step is to have nominations. These take place on the emc-users list. To make a nomination, please put NOMINATION in the subject of your message. Nominations must be seconded by another person to be considered; to second a nomination please put SECONDED in the subject. The nominated person should then accept or decline the nomination.
Let's start nominations now and run them through July 31 2007, 23:59:59 UTC.
Like last time, we'll have a wiki page where the nominees can write a bit about their experience and goals if they like:
The Board has asked Michael Cornelius to run the voting for us. Michael is not involved in the EMC project but he is a Free Software advocate in many ways and has graciously offered to help out. The Board will provide him a list of email addresses made from joining the lists of people receiving the emc-users and emc-developers emails.
He will send a ballot to each person and have a special email address set up to receive the votes. When voting closes he will report back the names of our new Board members. When the time comes he will give us all specific instructions about how to vote.
I wish good luck to the nominees, and give my sincere thanks to everyone on the lists who will participate in setting the future direction of the EMC project.
When I was young my father started acquiring manual machine tools. He bought Lathe, mill, shapers and such. He wanted a little job shop that would also allow him to tinker. This was good for me because it also allowed me to tinker and learn. Now sometime in the mid 80’s my father came across 2 identical machining centers in a junkyard. These were kerney & trecker Milwaukeematic series III. Actually what he brought home first was all the manuals and wiring diagrams. After reading up for a bit – he decided that maybe nc machines would be fun to play with ;)
We actually looked at retro-fitting this with a new controller at the time. This was before we had internet and finding info was a pain. What we did find – we knew we could not afford.
We got the machines and after building a building and pouring a huge concrete machine base we set one of the machines. Now this started my summer vacation project. I had to splice all the electrical and hydraulic lines. The mill was literally saw-zalled apart when it was removed. Thankfully we had all the wiring diagrams and manuals for it. At the summer end we were able to power it up. It is a bit fuzzy at that point but I don’t remember there being too many issues. I Think it just worked. Now remember this controller was discrete components (germanium transistors). It actually ran up until a few years ago.
Now it was time for college. I had actually thought about going into cnc but after setup of the K&T I decided to go with my other hobby – electronics. Now while going to school the company I worked for found out I knew cnc. They offered me a position in their newly formed laser department. I ran cad and the cnc laser cutting materials. I did this for a few years until they also found out I could do computer support. So I do IT for the same company now. My electronics and cnc knowledge turned into the hobby now.
One of our acquisitions at my fathers shop was a large stepper run gantry. We started using turbocnc to run it but figured out we wanted constant velocity contouring. The stopping at each end point was getting old. I had looked at emc1 a few years before but hadn’t the patience to get it to work. This time I downloaded the bdi and actually got it to run the machine. I wasn’t too impressed with it at the time as it seemed clunky. Now I had questions and got onto the irc channel. After the helpful bunch had answered all of my questions they had mentioned that there was an emc2 package. I promptly built it on my bdi install and was blown away. The wheels started to turn. I could see with Hal and classic ladder that I could convert our old K&T to one hell of a machining center - Cheap. That is where I am at now.. You can read about it here.
So mainly I bring some cnc experience and lots of testing. I am not a programmer (well as far as emc goes) but I have tested emc quite a bit and found a few bugs that have been fixed promptly by the developers. I have proposed features that actually have been implemented which is very cool. Oh - and I speak the praises of emc2 to everyone I can :)
I have been developing for emc since 2004, when Chris Radek and I collaborated to write a new user interface (AXIS). Since then, I have contributed in many areas, including tools for writing realtime modules, several hardware drivers, and lots of documentation.
During the next year, I see the following as valuable projects:
I have been Board chairman since 2005.
My area of interest in programming EMC is the basic functionality - I like to get it to do new things that are useful to people. Some of my programming accomplishments since 2005 have been: A new trajectory planner that fixed many problems with the tool motion and gave us a well-understood platform for adding new functionality; Tolerance mode specified in the gcode; Lathe tool offsets and tool shape compensation; Spindle-synchronized motion (Lathe threading and rigid tapping); A flexible canned threading cycle to make thread cutting on lathes easy; Coordinated motion in additional linear axes (UVW).
Some of my administrative accomplishments have been: Working as release engineer for the 2.0 and 2.1 series of releases (overseeing when to release, what to release, building the releases themselves); building and administering cvs.linuxcnc.org and related tasks for developers; administering the linuxcnc apt repository to make updates easy for users; building and maintaining the Ubuntu 6.06LTS/EMC2 Live CD to make initial installs as easy as possible.
Along the way I have fixed many bugs and helped many users on the lists and on IRC. I consider these my most important work for the project. Whether or not I am reelected to the Board I will continue to do them.
I currently use EMC2 on my lathe and mill and am hoping to get another mill soon.
I don't have any big promises to make except that I will continue working for the project and acting in what I feel is its best interest.
Board member as of 2004
I was the original lead coder for HAL, the interface used by EMC2 to address hardware configurability and related issues. I also wrote most of RTAPI, the interface to the realtime OS used by EMC2 - it got rid of a lot of messy OS specific code inside EMC proper. Many others have contributed to both HAL and RTAPI since then however.
I did a lot of other work on EMC2, mostly in the motion controller, and other low-level code, with minor visits to task and iocontrol. I tend to be pretty vocal in technical discussions, but I admit I don't know the GUIs or interpreter very well, and have little actual hand-on CNC machining experience.
I am a hobby level machinist. I own a Shoptask 3-in-1 that I've been meaning to retrofit with EMC for about 4 years now, but I keep getting caught up in coding and such and never seem to work on my own machine. I am coming up to speed a bit on CNC operation, especially at the CNC workshop in 2007. Working on the Mazak at the workshop is a chance to understand the issues of industrial scale machines.
I also handle some EMC administrivia. (I'm one of several mailing list admins, for example, and I set up the bug trackers on Soureforge a while back.)
My day job is an electrical engineer (power electronics) designing large industrial VFDs. Many of the same control, safety, etc. principles apply to EMC, so it is usefull experience.
My ongoing interests in EMC are HAL, drivers (especially the Mesa 5i20), and the motion controller. I'm mostly responsible for homing, jogwheels, and a few other features that are part of the motion controller, and I will continue to focus in those areas. As I get my own machine running, I'll have more hands on experience, and probably spread out into other areas.
Board member since 2005
I started with emc 3 years ago (feels like yesterday), and have been enjoying the ride since. I have gathered some experience with the codebase of emc2 (not many areas I haven't touched), but also with the infrastructure for emc2 (built the kernel and rtai packages for the official platform - Ubuntu DapperDrake?). As I've been working on various parts of emc2 (IO control, spindle control, task, interpreter etc.), mainly for adding new features and cleaning out bugs.
Been taking care of the webpage at www.linuxcnc.org, announcing new releases and updating pages & translations. Likewise at sourceforge.
I am available on the irc channel most days and I spend some time helping new EMC users with not only EMC problems but also general Linux problems (on IRC, on the lists and a couple german places: forums & wikis).
I started using EMC in 1999 with several machines set up for engraving and routing for guitar parts. I saw the huge potential for development, because it is open source. Whenever I requested a feature, it seems like someone implemented it right away. Originally it was only set up for A/D servo cards and I asked if it could be made to control step and direction drives via the parallel port. The next week, Fred Proctor had the stepper module running (if my memory is correct).
After using EMC for fun and profit for several years, I became interested in the programming languages that make EMC tick. At first, I looked under the hood at tkemc.tcl and saw that I could understand it. Much later, I have become very interested in python and C. EMC also indroduced me to Linux. It's been a very long and fruitful love affair. The machine that I started with was running RedHat? 5.1 or something. I have played with Mandrake, Redhat, Debian, and ultimately settled on Ubuntu (which I really like a lot). So, you could say that EMC made me a Linux/open source convert.
I am interested in industry/production shop issues related to CNC controls. The place where I work uses Fanuc based CNC controls (lots and lots of them). I have had to become used to the old and closed box way of doing things that these machines impose on us. Hopefully, we can convert some of these over to open source control someday. I plan on making the machines that I retrofit boot up to EMC staight away, without a login prompt. These will be dedicated machines, purely for CNC control. I think that I have learned enough about python and tkinter to create a very simple gui for EMC that will do exactly what I want it to. This sort of gui will only show the machine operator what needs to be seen for production work.
I've been dabbling with or working on EMC for about 3-4 years now. I have a Bridgeport mill that I'm converting to EMC2 (slowly but surely). I've written a few HAL components and helped out with driver work. My primary contribution has been in the form of IRC and Fest discussions about direction and architecture. (ie, I haven't contributed much code lately :) ) I also take part in "customer support" and "promotion" when I have the chance.
In the longer term (starting this year), I'd like to see and help make progress toward:
I have lots of lofty goals, and I hope to be able to do some of the work myself.