jakestern

Please send resumes to jacob(at)teslamotors.com. Job Title and Description: Manufacturing Test Engineer This Manufacturing Test Engineer is a member of the Powertrain Manufacturing Engineering team. He/she will use engineering knowledge and creativity to develop a variety of manufacturing tests and equipment to be used on Tesla’s powertrain production lines. This will require the design, programming, fabrication and documentation of test equipment, along with ongoing daily support once deployed. The ideal candidate takes pride in his/her hands-on and analytical abilities, organization skills and attention to detail. He/She appreciates an environment where superior work is encouraged, noticed and rewarded. Essential Functions and Duties: Integration of Test Equipment Hardware and Software Development of Test Plans and Hardware and Software Requirements Specifications in conjunction with Design Engineering, Manufacturing Engineering, and Production Procurement, installation and configuration of test instrumentation and hardware Design and development of Production Test Equipment hardware with emphasis on: 1. Safety – The equipment must be designed to be safe for use by production personnel with minimal training. In addition, the equipment should protect itself and the product under test.2. Robustness – The equipment will be deployed in a factory environment and must be designed to withstand a high number of cycles under rugged conditions.3. Documentation – Multiple copies of the equipment will be built and accurate and detailed documentation will be required to facilitate replication efforts.4. Serviceability – Equipment must be easily serviced and repaired. Development of software to run tests according to test plans Development of software to assist with the gathering and presentation of factory production data for analysis by engineers and production managers Development of equipment manufacturing processes in conjunction with Manufacturing Process Engineers Investigate test issues and incorporate corrective actions as required in conjunction with Design Engineering and Production teams Skills and Experience: BS or higher degree in Mechanical or Electrical Engineering 5+ years of Manufacturing Test Engineering experience 3+ years of experience with LabVIEW (CLAD, CLD, or CLA a plus) and/or TestStand Experience with RS232, GPIB, and LXI control of instrumentation. Experience with CAN communications a plus. Familiarity with electronic circuits, experience with high voltage environments is preferred but not required Experience designing electrical test hardware, with an emphasis on safety for the operator and the product Solid understanding of production equipment design issues such as user friendliness, serviceability, ruggedness, noninvasive electrical test connections, etc Ability to design, fabricate and document moderately complex wiring harnesses utilizing a solid understanding of connectors, termination, crimping, wire/connector labeling, etc Ability to work well under pressure while managing competing demands and tight deadlines Experience with verbal and pictorial documentation of manufacturing processes Excellent written and communication skills Well organized with meticulous attention to detail Mastery of Word, Excel, PowerPoint Demonstrated proficiency with SolidWorks or Catia is highly desired About Tesla Motors: Tesla Motors is a small, well-funded company in the San Francisco Bay Area. We design and manufacture advanced electric vehicles, battery packs, and drive systems and are working to change the future of the transportation industry. We are building a technically strong, fast-moving team that prides itself on superior execution. Our Mission: Tesla Motors designs and sells high-performance, highly efficient electric sports cars. Our cars combine style, acceleration, and handling with advanced technologies that make them among the quickest and the most energy efficient cars on the road.

About Tesla Motors: Tesla Motors is a small, well-funded company in the San Francisco Bay Area. We design and manufacture advanced electric vehicles, battery packs, and drive systems and are working to change the future of the transportation industry. We are building a technically strong, fast-moving team that prides itself on superior execution. Our Mission: Tesla Motors designs and sells high-performance, highly efficient electric sports cars. Our cars combine style, acceleration, andhandling with advanced technologies that make them among the quickest and themost energy efficient cars on the road. Job Title and Description: Manufacturing Test Engineer This Manufacturing Test Engineer is a member of the Powertrain Manufacturing Engineering team. He/she will use engineering knowledge and creativity to develop a variety of manufacturing tests and equipment to be used on Tesla’s powertrain production lines. This will require the design, programming, fabrication and documentation of the test equipment, along with ongoing daily support once deployed. The ideal candidate takes pride in his/her hands-on and analytical abilities, organization skills and attention to detail. He/She appreciates an environment where superior work is encouraged, noticed and rewarded. Essential Functions and Duties: · Development of Test Plans and Hardware and Software Requirements Specifications in conjunction with Design Engineering, Manufacturing Engineering, and Production · Procurement, installation and configuration of test instrumentation and hardware · Design and development of Production Test Equipment hardware with emphasis on: 1. Safety – The equipment must be designed to be safe for use by production personnel with minimal training. In addition, the equipment should protect itself and the product under test. 2. Robustness – The equipment will be deployed in a factory environment and must be designed to withstand a high number of cycles under rugged conditions. 3. Documentation – Multiple copies of the equipment will be built and accurate and detailed documentation will be required to facilitate replication efforts. 4. Serviceability – Equipment must be easily serviced and repaired. · Development of software to run tests according to test plans · Development of software to assist with the gathering and presentation of factory productiondata for analysis by engineers and production managers · Development of equipment manufacturing processes in conjunction with Manufacturing Process Engineers · Investigate test issues and incorporate corrective actions as required in conjunction with Design Engineering and Production teams Skillsand Experience: · Familiarity with electronic circuits. Experience with high voltage environments is preferred but not required · Experience designing electrical test hardware, with an emphasis on safety for the operatorand the product · Solid understanding of production equipment design issues such as user friendliness,serviceability, ruggedness, noninvasive electrical test connections, etc · Ability to design, fabricate and document moderately complex wiring harnesses utilizing a solid understanding of connectors, termination, crimping, wire/connector labeling,etc · Ability to work well under pressure while managing competing demands and tight deadlines · Experience with LabVIEW and TestStand (CLD, CLA, CTD or CTA a plus, but not required) · Experience with verbal and pictorial documentation of manufacturing processes · Excellent written and communication skills · Well organized with meticulous attention to detail · Mastery of Word, Excel, PowerPoint This is a full-time position only. If you are interested, please email your resume to me at jacob (at) teslamotors.com.

I'm trying to print out a webpage programmatically, without the user having to do anything (and hopefully, not even see anything). I've tried using the ActiveX container to load a page, but when I try to print, I get an error (see ActiveXPrintWebpage.vi). I've also looked into using the .NET container, which is a bit more complicated, but I've had no luck there as I don't quite understand how it works. The third idea I had was to invoke a browser using the command line, but I don't know how to send in a command to print. Any ideas?

Tesla Motors is looking for an experienced LabVIEW programmer to join the Manufacturing Test Team. See the official listing here: www.teslamotors.com/about/employment.php?id=449 We're looking for someone with who can architect LabVIEW applications and who has the electronics/electrical and mechanical skills to design and build test fixtures. Certification as a Developer or Architect is a big plus. You'll be designing and bulding test tools for the manufacturing environment for components that go into the Tesla Roadster. In addition, we are looking for someone with the experience to help us build a solid LabVIEW development environment within our team (i.e. establish a reuse library, participate in code design reviews, start a LabVIEW user's group, etc.). The work involves close interaction with the engineering team responsible for designing the product. It's also a hands-on environment - you'll swing a wrench and a soldering iron quite often, alongside technicians who are here to help. If this work interests you, please contact me directly with your resume: jake at teslamotors dot com. -Jake Stern

I'm about to embark on a project that involves more than one developer. I've just read "A Software Engineering Approach to LabVIEW" by Jon Conway and Steve Watts, and I like what they've presented. They choose to use Enums defined as Strict Typdef custom controls to be the selector for case structures in their state machines. There are advantages to using either Enums or Strings for these case structures, but the one area I haven't seen discussed is what issues might arise when Source Code Control with either method. With Strict Enums, during development, if one person adds a new element to the enum, then all subVIs need to be resaved. This involves checking out a potentially large number of VIs, often to do nothing other than resave. With Strings as the selector, this isn't an issue. Of course there are many other facets to the debate of Strings vs. Enums, but I'd like to know if this particular issue is really that big of an issue or not. Have you developed with multiple developers using Source Code Control, and had problems with developers getting hung up because another person has a large number of files checked out due to something simple like a Strict change, or a (gasp) Globals.vi change? Also, with your SCC tool, how do you go about rapidly checking out all files that have changed? We are currently using CVS, which I have not yet learned to work with. I have LV PRO, but others only have FULL, so they do not have access to the built-in SCC interface.