1461048248-110115ca-51d7-4b9c-9edc-55748e92e10b

1. A manually operated brushless direct current (DC) motor, comprising:
a power source;
a set of magnets;
a rotor with coil wire wound around, and placed between the magnets by means of a rotation axle;
a set of bearings used to support the rotation axle, and to provide the connection required between the coil wire of the rotor and the power source without a brush;
a set of switches electrically connected to the bearings and the power source respectively;
a set of sensor plates, hung around one of the bearings by a wire; and
a set of sensors installed at specific places to detect the existence of the sensor plates, and generating a responsive signal;
wherein the alternatively pressed switches work just like brushes of a conventional motor and make the rotor to rotate; and
wherein the sensors detect the sensor plates intermittently passing by when the rotor rotates to drive the sensor plates moving upward and downward (back and forth).
2. The manually operated brushless direct current (DC) motor as claimed in claim 1, wherein the power source comprises at least a battery.
3. The manually operated brushless direct current (DC) motor as claimed in claim 1, wherein an upper and lower half portions of the rotor are painted with different colors, and the switches are painted with the same colors corresponding to the rotor.
4. The manually operated brushless direct current (DC) motor as claimed in claim 1, wherein the set of magnets comprises a plurality of magnets whose N poles and S poles are evenly distributed on an inside surface of a stator of the motor.
5. The manually operated brushless direct current (DC) motor as claimed in claim 1, further comprising a counter used to count the numbers of signals from the sensors and to show the counting results.
6. The manually operated brushless direct current (DC) motor as claimed in claim 1, further comprising a speaker used to give forth a sound when receiving the signal from the sensors.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A method of testing emulator boards in a hardware emulator, comprising:
receiving a request to test one or more emulator boards in the hardware emulator;
in response to the request, reading, in a first server, a list of commands associated with the request;
passing the commands to a second server coupled to the one or more emulator boards; and
executing the commands received by the second server on the one or more emulator boards in order to test the emulator boards.
2. The method of claim 1, further including opening a list of tests associated with the request and wherein a first test includes the list of commands and other tests include additional lists of commands.
3. The method of claim 1, further including receiving a response to each of the commands and passing a result to a user interface.
4. The method of claim 1, wherein the commands include function calls with parameters including an emulator board number.
5. The method of claim 1, further comprising modifying the list of commands and executing the modified list without compilation.
6. The method of claim 1, wherein the request includes a name of a file and a list of emulator boards to be tested.
7. A computer-readable medium having computer-executable instructions thereon for performing the method of claim 1.
8. A hardware emulator, comprising:
plural emulator boards having programmable logic thereon for emulating a user design;
a first server coupled to the emulator boards, the first server configured to send test commands to be performed on the emulator boards; and
a second server coupled to the first server, the second server including a command sequencer configured to sequence through a file including a list of testing commands and to send the testing commands to the first server.
9. The hardware emulator of claim 8, wherein the first and second servers are located in a hardware emulation workstation coupled to the plural emulator boards.
10. The hardware emulator of claim 8, further including a database coupled to the second server, the database including a first file comprising a list of tests, the database further including a plurality of secondary files associated with the tests, the secondary files including testing commands associated with the tests.
11. A method in a hardware emulator, comprising:
receiving a request to test one or more emulator boards in the hardware emulator;
in response to the request, opening, in a first server, a first list of tests associated with the request;
reading a first test name from the list of tests;
opening a second list of commands associated with the first test name; and
passing the commands from the second list to a second server for executing the commands on the one or more emulator boards in order to test the emulator boards.
12. The method of claim 11, wherein the commands are function calls.
13. The method of claim 11, wherein the commands are passed sequentially and a next command is passed only after a response from the previous command is received.
14. The method of claim 11, wherein the request is received from a user interface and further including displaying results of the request in the user interface.
15. A computer-readable medium having computer-executable instructions thereon for performing the method of claim 11.
16. A method of testing emulator boards in a hardware emulator, comprising:
receiving a test to be executed and an identification of one or more emulator boards to be tested;
reading a list of function calls associated with the test;
executing each function call on the identified emulator boards and sending the response to each function call to a server; and
determining a result of the test.
17. The method of claim 16, further including displaying the result of the test.
18. The method of claim 16, wherein the function calls are executed sequentially.
19. The method of claim 16, further including reading a list of sub-tests to be executed associated with the test.
20. The method of claim 19, wherein each sub-test has an associated list of function calls.
21. A hardware emulator to emulate a user’s design, comprising:
means for emulating a user design;
means for reading a first test file including a list of tests to perform and for reading a second command file including a list of commands associated with each test in the test file; and
means for sending the commands to the means for emulating to test the means for emulating.