Abstract: A method for producing a coil includes winding a wire in order to produce a wound coil, and stretching the wound coil from an initial state into a stretched state with an increased spread. The method includes providing the wound coil, in the stretched state, with a coating, and transferring the wound coil from the stretched state back into a state of smaller spread.

Abstract: The invention relates to a segmented coil carrier (20; 20?) for an electric machine (2), comprising a plurality of separately formed, interconnected segments (1) with in each case one carrier (10) with a shaft (100) and a coil (11) surrounding the shaft (100), a groove (N) being formed between two adjacent carriers (10); and a groove wedge arranged in the groove (N).

Abstract: An electric machine includes at least one stator having at least one individual-tooth winding carrier that has at least one spacer configured to space apart turns of an individual-tooth winding mounted on the individual-tooth winding carrier. A hybrid electric aircraft has an electric machine of this kind.

Abstract: An electric machine includes at least one stator having at least one individual-tooth winding carrier that has at least one spacer configured to space apart turns of an individual-tooth winding mounted on the individual-tooth winding carrier. A hybrid electric aircraft has an electric machine of this kind.

Abstract: An electric machine includes at least one stator having at least one individual-tooth winding carrier that has at least one spacer configured to space apart turns of an individual-tooth winding mounted on the individual-tooth winding carrier. A hybrid electric aircraft has an electric machine of this kind.

Abstract: The invention relates to an electric motor comprising at least one winding having at least one electrical conductor (30) that has a non-circular-symmetrical cross-section and having at least one cooling-fluid conductor (60) that has a non-circular-symmetrical cross-section. The hybrid electric vehicle is in particular a hybrid electric aircraft and has such an electric motor (10).

Abstract: The coil winding has an electrical conductor for an electrical machine and includes at least two layers. The electrical conductor, following its longitudinal extension, runs inwardly wound in a first of the at least two layers, and then extends to a second of the at least two layers and runs outwardly wound in the second layer. The electrical machine includes at least one such coil winding. The hybrid electric aircraft is in particular an airplane and includes such an electrical machine and/or at least one such coil winding.

Abstract: An electric machine includes at least one stator having at least one individual-tooth winding carrier that has at least one spacer configured to space apart turns of an individual-tooth winding mounted on the individual-tooth winding carrier. A hybrid electric aircraft has an electric machine of this kind.

Abstract: Various embodiments include a drive system for a vehicle, the system comprising: an internal combustion engine for converting chemical energy stored in a liquid fuel into mechanical energy; a fuel tank for storing fuel for use by the internal combustion engine; and an electric machine having a rotor, a stator, and a cooling system for cooling at least one component of the electric machine using a cooling liquid. The cooling liquid comprises the fuel.

Abstract: A method for accessing functions of an embedded device, for example a controller programmable from memory, wherein function blocks of the embedded device are assigned to at least two hierarchically superimposed levels, an access to a function block of the embedded device occurs from outside of the embedded device by a data interface, and for access an authentication must occur for the level to which the respective function block is assigned, and again for each individual level above the level to which the function block is assigned, to permit execution of a function of the function block, wherein the functions of the function blocks permit access to a firmware of the embedded device.

Abstract: A system for obtaining performance data for different performance events includes a first application monitoring performance of a second application executing on a computing system. The first application identifies the type of event to be measured with respect to the second application, issues a first system call identifying the type of event, receives an identifier corresponding to the event type, and causes the second application to begin execution. After the execution of the second application is completed, the first application issues a second system call including the identifier corresponding to the event type, and receives a value of a hardware counter corresponding to the event type from an operating system.

Abstract: Various embodiments include a drive system for a vehicle, the system comprising: an internal combustion engine for converting chemical energy stored in a liquid fuel into mechanical energy; a fuel tank for storing fuel for use by the internal combustion engine; and an electric machine having a rotor, a stator, and a cooling system for cooling at least one component of the electric machine using a cooling liquid. The cooling liquid comprises the fuel.

Abstract: A method for accessing functions of an embedded device, for example a controller programmable from memory, wherein function blocks of the embedded device are assigned to at least two hierarchically superimposed levels, an access to a function block of the embedded device occurs from outside of the embedded device by a data interface, and for access an authentication must occur for the level to which the respective function block is assigned, and again for each individual level above the level to which the function block is assigned, to permit execution of a function of the function block, wherein the functions of the function blocks permit access to a firmware of the embedded device.

Abstract: A system for obtaining performance data for different performance events includes a first application monitoring performance of a second application executing on a computing system. The first application identifies the type of event to be measured with respect to the second application, issues a first system call identifying the type of event, receives an identifier corresponding to the event type, and causes the second application to begin execution. After the execution of the second application is completed, the first application issues a second system call including the identifier corresponding to the event type, and receives a value of a hardware counter corresponding to the event type from an operating system.

Abstract: A system for obtaining performance data for different performance events includes a first application monitoring performance of a second application executing on a computing system. The first application identifies the type of event to be measured with respect to the second application, issues a first system call identifying the type of event, receives an identifier corresponding to the event type, and causes the second application to begin execution. After the execution of the second application is completed, the first application issues a second system call including the identifier corresponding to the event type, and receives a value of a hardware counter corresponding to the event type from an operating system.

Abstract: A system for providing performance statistics of applications in real time includes a first application that obtains current performance data of at least one second application in real time, utilizes the current performance data to determine a list of functions and the number of events occurred during the execution of each function, presents the resulting data to a user, and periodically refreshes the presented data using up-to-date performance data of the second application.

Abstract: A system for providing performance counter inheritance includes an operating system that receives a request of a first application to monitor performance of a second application, the request identifying an event to monitor during the execution of a task associated with the second application. The operating system causes a task counter corresponding to the event to be activated, and automatically activates a child task counter for each child task upon receiving a notification that execution of a corresponding child task is starting. Further, the operating system adds a value of each child task counter to a value of the task counter to determine a total counter value for the task, and provides the total counter value of the task to the first application.

Abstract: Systems and methods of managing primitives are disclosed. A data structure that is stored in user space is registered, wherein the data structure tracks a user controllable mutual exclusion primitive that is acquired by a process running in the user space, and wherein the user controllable mutual exclusion primitive serves as a lock on a resource provided by a computer system. A termination of the process is detected, wherein the process maintains the lock on the resource after termination and the data structure is searched to identify the user controllable mutual exclusion primitive that is acquired by the process that terminated. The user controllable mutual exclusion primitive is released if the user controllable mutual exclusion primitive is identified as being acquired by the process.

Abstract: A system for handling performance counters and events includes an operating system that receives a request of a first application for performance data associated with a type of event to be performed by a second application, causes a hardware counter pertaining to the event type to be activated, and provides a file descriptor corresponding to the hardware counter to the first application. The operating system then receives a second request of the first application for a value of the hardware counter, where the second request includes the file descriptor, and provides the value of the hardware counter to the first application.

Abstract: A system for providing software performance counters includes an operating system that receives a first request of a first application to monitor performance of a second application, the first request identifying a type of event to monitor during the execution of the second application. The operating system determines that the event is a software event, monitors the performance of the second application with respect to the type of the software event, and updates a counter associated with the type of the software event based on the monitoring. Further, the operating system receives a second request of the first application for performance data associated with the type of the software event counter, and provides the value of the counter to the first application.