Abstract: A power tool is provided including a housing and an electric motor disposed in the housing. The motor includes a stator having pole pieces mated together and field coils disposed on the pole pieces, the stator having an outside diameter. The motor also includes an armature having an outside diameter that is at least 0.625 of the outside diameter of the stator.

Abstract: A power tool has a motor having a stator made by separately forming pole pieces and field coils. The field coils are placed over necks of the pole path pieces. An armature has an outside diameter of at least 0.625 the outside diameter of the stator is placed in the stator. The housing has a girth of 200 mm or less with the motor wound to provide a maximum watts out to housing girth ratio of at least 5 maximum watts outs to 1 mm of housing girth. The field coils may be formed so that they extend beyond pole tips of the pole pieces.

Abstract: One embodiment of the invention comprises a system and method enabling a guard condition for a statechart to be defined using graphical data flow code. Another embodiment of the invention comprises a system and method enabling an action for a statechart to be defined using graphical data flow code. The statechart may be created in response to user input, e.g., user input to a statechart development environment that includes a graphical statechart editor. The graphical data flow code that defines the guard condition or the action may be created in response to user input to a graphical data flow code editor. In some embodiments the graphical data flow code editor may be integrated with or embedded in the graphical statechart editor.

Abstract: A power tool has a motor having a stator made by separately forming pole pieces and field coils. The field coils are placed over necks of the pole path pieces. An armature has an outside diameter of at least 0.625 the outside diameter of the stator is placed in the stator. The housing has a girth of 200 mm or less with the motor wound to provide a maximum watts out to housing girth ratio of at least 5 maximum watts outs to 1 mm of housing girth. The field coils may be formed so that they extend beyond pole tips of the pole pieces.

Abstract: Various embodiments of a system and method enabling a user to create a statechart and select an event mode for the statechart are disclosed. The statechart may be created in a graphical manner in response to user input and displayed on a display. A graphical user interface enabling a user to select from a plurality of event modes for the statechart may be displayed. The plurality of event modes may include both a synchronous mode and an asynchronous mode. The statechart may be configured to receive events from an external program either synchronously or asynchronously, depending on which event mode the user selects.

Abstract: A system and method for creating a graphical program operable to asynchronously pass one or more trigger events to a statechart. The graphical program may include a first node which is operable to asynchronously send one or more trigger events to a statechart. For example, in some embodiments the first node may be operable to place the one or more trigger events in an event queue associated with the statechart. The statechart may receive and process events from the event queue asynchronously with respect to when the events are placed in the event queue.

Abstract: A power tool has a motor having a stator made by separately forming pole pieces, return path pieces and field coils. The field coils are placed over necks of the pole path pieces and the return path pieces are affixed to the pole pieces. An armature having an outside diameter of at least 0.625 the outside diameter of the stator is placed in the stator. The field coils may be formed so that they extend beyond pole tips of the pole pieces.

Abstract: A universal termination system is provided for power tools. The universal termination system includes criteria for each of the main switch platforms that define the number, type, location and orientation of the terminations. That is, the number, type, location and orientation of the terminations in each main switch platform are standardized and the power tools that use that type main switch platform use the main switch platform having the standardized terminations. That is, power tools that use push button switches use the push button switch with the standardized terminations, power tools that use overhang switches use the overhang switch with the standardized terminations, and power tools that use in-line VSR switches use the in-line VSR switch with the standardized terminations. In an aspect of the invention, a right-angle pin terminal is received in one or more sets of the standardized terminations.

Abstract: System and method for generating a data flow diagram. A first case structure may be specified. Each case of the first case structure that includes a respective plurality of input bound data flow nodes may be partitioned into one or more data flow diagram portions. The first case structure may be replaced with a first conditional structure and one or more second conditional structures. The first conditional structure may be operable to select one or more of the plurality of input bound data flow diagram portions in accordance with the conditions of the first case structure. The one or more second conditional structures may be operable to select at least one output from the plurality of input bound data flow diagram portions in accordance with the conditions of the first case structure. The partitioning and replacing may be performed automatically in response to specification of the first case.

Abstract: A system and method for automatically generating a graphical data flow program from a statechart are disclosed. The statechart may be created in a graphical manner in response to user input, e.g., in response to the user arranging state icons on a display and creating interconnections representing transitions among the respective states. The statechart may include at least one hierarchical state, where each hierarchical state includes one or more sub-states. A graphical data flow program may be automatically generated from the statechart. The graphical data flow program may include a plurality of interconnected nodes that visually indicate functionality of the graphical data flow program, where connections among the nodes visually indicate data flow among the nodes. The graphical data flow program may be executable to implement the functionality of the statechart.

Abstract: A power tool has a motor having a stator made by separately forming pole pieces, return path pieces and field coils. The field coils are placed over necks of the pole path pieces and the return path pieces are affixed to the pole pieces. An armature having an outside diameter of at least 0.625 the outside diameter of the stator is placed in the stator. The field coils may be formed so that they extend beyond pole tips of the pole pieces.

Abstract: A power tool has a motor having a stator made by separately forming pole pieces, return path pieces and field coils. The field coils are placed over necks of the pole path pieces and the return path pieces are affixed to the pole pieces. An armature having an outside diameter of at least 0.625 the outside diameter of the stator is placed in the stator. The field coils may be formed so that they extend beyond pole tips of the pole pieces.

Abstract: System and method for generating a data flow diagram. A data flow diagram is provided that includes one or more non-input bound data flow (NIBDF) nodes, each with a respective functionality, and at least one of which is a subsystem node representing a non-input bound data flow sub-diagram comprising a plurality of interconnected nodes. All non-input bound data flow nodes in the data flow diagram are converted into input bound data flow (IBDF) nodes to produce an IBDF diagram, including: for each NIBDF subsystem node in the data flow diagram: partitioning the NIBDF sub-diagram into a plurality of IBDF sub-diagrams that operate according to input bound data flow semantics without changing data dependencies of the NIBDF sub-diagram, and including a plurality of IBDF nodes respectively representing the plurality of IBDF sub-diagrams in the IBDF diagram in lieu of the NIBDF subsystem node. The IBDF diagram is then stored.

Abstract: A universal termination system is provided for power tools. The universal termination system includes criteria for each of the main switch platforms that define the number, type, location and orientation of the terminations. That is, the number, type, location and orientation of the terminations in each main switch platform are standardized and the power tools that use that type main switch platform use the main switch platform having the standardized terminations. That is, power tools that use push button switches use the push button switch with the standardized terminations, power tools that use overhang switches use the overhang switch with the standardized terminations, and power tools that use in-line VSR switches use the in-line VSR switch with the standardized terminations. In an aspect of the invention, a right-angle pin terminal is received in one or more sets of the standardized terminations.

Abstract: A power tool has a motor having a stator made by separately forming pole pieces, return path pieces and field coils. The field coils are placed over necks of the pole path pieces and the return path pieces are affixed to the pole pieces. An armature having an outside diameter of at least 0.625 the outside diameter of the stator is placed in the stator. The field coils may be formed so that they extend beyond pole tips of the pole pieces.

Abstract: One embodiment of the invention comprises a system and method enabling a guard condition for a statechart to be defined using graphical data flow code. Another embodiment of the invention comprises a system and method enabling an action for a statechart to be defined using graphical data flow code. The statechart may be created in response to user input, e.g., user input to a statechart development environment that includes a graphical statechart editor. The graphical data flow code that defines the guard condition or the action may be created in response to user input to a graphical data flow code editor. In some embodiments the graphical data flow code editor may be integrated with or embedded in the graphical statechart editor.

Abstract: A system and method for automatically generating a graphical data flow program from a statechart are disclosed. The statechart may be created in a graphical manner in response to user input, e.g., in response to the user arranging state icons on a display and creating interconnections representing transitions among the respective states. The statechart may include at least one hierarchical state, where each hierarchical state includes one or more sub-states. A graphical data flow program may be automatically generated from the statechart. The graphical data flow program may include a plurality of interconnected nodes that visually indicate functionality of the graphical data flow program, where connections among the nodes visually indicate data flow among the nodes. The graphical data flow program may be executable to implement the functionality of the statechart.

Abstract: Various embodiments of a system and method enabling a user to create a statechart and select an event mode for the statechart are disclosed. The statechart may be created in a graphical manner in response to user input and displayed on a display. A graphical user interface enabling a user to select from a plurality of event modes for the statechart may be displayed. The plurality of event modes may include both a synchronous mode and an asynchronous mode. The statechart may be configured to receive events from an external program either synchronously or asynchronously, depending on which event mode the user selects.

Abstract: A system and method for creating a graphical program operable to asynchronously pass one or more trigger events to a statechart. The graphical program may include a first node which is operable to asynchronously send one or more trigger events to a statechart. For example, in some embodiments the first node may be operable to place the one or more trigger events in an event queue associated with the statechart. The statechart may receive and process events from the event queue asynchronously with respect to when the events are placed in the event queue.

Abstract: Welding a first body (11) of a first metal which has been plated on one surface thereof with a layer (13) of a second metal comprises the step of vaporizing a portion of said layer. This is done by directing a first pulsed laser beam (17) at the layer (13), the first pulsed laser beam having a first relatively high peak power and a first relatively low pulse duration. The vaporizing results in exposure of a portion of the first body (11). Thereafter, part of the first body is melted by directing a second pulsed laser beam (20) at the exposed portion of the first body, said second pulsed laser beam having a second peak power smaller than the first peak power and a second pulse duration longer than said first pulse duration. By using the same laser (18) in a two-step process, first to vaporize a portion of the plating, such as gold plating on Kovar, and thereafter using the same laser for making the weld, one can avoid a microcracking problem in a manner that is quick, simple and convenient.