1. A simulator for developing an acoustic detector of an underwater vehicle, comprising:
an IO communication unit for receiving information required for simulating an underwater environment from an acoustic detector and a motion simulator;
a signal generator for receiving the information from the IO communication unit to calculate a digital signal model;
a DA converter for converting the digital signal model into an analog signal;
a signal conditioner for generating a signal similar to the signal of an actual underwater environment by controlling frequency and gain of the analog signal; and
a remotely controlled computer for loading an OS to the signal generator and displaying various operation status;
wherein the signal generator comprises:
a central controller for receiving the information and controlling operations of the simulator; and
a plurality of processor units for calculating and generating the digital signal model for each channel according to a command of the central controller, wherein the central controller and the plurality of processor units are connected in a process farm structure so that a signal model among channels has parallelism.
2. The simulator of claim 1, further comprises:
an extra CPU for performing an additional function or a signal model calculation.
3. The simulator of claim 1, wherein the DA converter includes a plurality of DAC modules corresponding to the plurality of processor units, and the DAC modules are connected by a DAC control network for synchronization of output signals among channels.
4. The simulator of claim 3, wherein the DAC control network receives a ready signal from the plurality of DAC modules and then generates a load signal for each sample, to thereby synchronize each channel.
5. The simulator of claim 1, wherein the signal conditioner comprises:
a control board for outputting a control signal on the basis of a frequency band to be modulated and a signal gain value; and
a plurality of slave boards for controlling frequency and amplitude of an analog signal of the DA converter according to the control signal.
6. The simulator of claim 5, wherein the signal gain value is calculated in the central controller and provided to the control board while a processor unit calculates a signal model.
7. The simulator of claim 5, wherein the IO communication unit comprises:
a first IO board for communicating with the acoustic detector; and
a second IO board for communicating with the motion simulator and the control board.
8. The simulator of claim 7, wherein the first and second IO boards performs a communication processing by connecting peripheral devices of various communication methods to the central controller.
9. The simulator of claim 8, wherein the connection between the central controller and the peripheral devices is set by software.
10. The simulator of claim 1, wherein the remotely controlled computer is connected to the central controller of the signal generator by an optical cable and communicates with the central controller in a C40 COM port.
11. The simulator of claim 1, wherein the signal generator, the DA converter and the IO communication unit are constructed as a C40 based single DSP board.
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 for recording an event set from a user interface, comprising:
injecting one or more monitoring wrapper functions in the user interface instructions, the one or more monitoring wrapper functions comprising:
a first monitoring wrapper function configured to record a first state of an event generator; and
a second monitoring wrapper function configured to:
record a second state of an event generator; and
send the first state and the second state to a recording engine;
associating a first reference to the one or more monitoring wrapper functions with one or more event handlers; and
associating a second reference to the one or more monitoring wrapper functions, subsequent to the first reference, with the one or more event handlers, comprising:
at least one set of instructions between the first reference and the second reference in the event handler.
2. The method of claim 1, comprising:
using the one or more monitoring wrapper functions to collect information from one or more events invoked by the one or more event generators, comprising:
recording a state of an event generator prior to invocation of an event;
calling one or more event handler functions called by the one or more events;
recording a state of an event generator after completion of the event; and
passing the information to a recording engine.
3. The method of claim 1, comprising:
for one or more event generators, replacing instructions that attach and detach an event handler with instructions for one or more event handler attach and detach wrappers;
upon invocation of an event upon one or more event generators, generating one or more monitoring wrapper functions for one or more event handlers; and
storing the called one or more references to the one or more event handler functions and the one or more references to the one or more monitoring wrapper functions.
4. The method of claim 3, comprising calling a deregistration function using stored references to the one or more event handler functions and references to the one or more wrapper functions.
5. The method of claim 3, replacing instructions comprising:
injecting wrapper instructions for attaching and detaching event handlers; and
replacing references in the one or more event generators to instructions that attach and detach event handlers with references to the one or more event handler attach and detach wrappers.
6. The method of claim 3, replacing instructions comprising at least one of the following:
replacing instructions as an application interface loads; and
replacing instructions after an application interface loads.
7. The method of claim 3, the event generators comprising elements that attach event handlers dynamically.
8. The method of claim 1, the second monitoring wrapper function configured to determine intent of an action upon the event generator comprising comparing the first state with the second state.
9. The method of claim 2, passing the information to a recording engine comprising:
injecting one or more new elements in the user interface instructions; and
sending collected information from the one or more new elements to the recording engine;
10. The method of claim 9, the one or more new elements comprising:
one or more lists of one or more events; and
one or more corresponding properties collected from the one or more events.
11. The method of claim 2, passing the information to a recording engine comprising:
injecting one or more broker objects in the user interface instructions;
sending the information from the one or more monitoring wrapper functions to the one or more broker objects; and
sending the information from the one or more broker objects to the recording engine.
12. The method of claim 1, the first monitoring wrapper function and the second monitoring wrapper function comprising the same monitoring wrapper function.
13. The method of claim 1, the first state of an event generator comprising a state of the event generator prior to an event being called upon the event generator.
14. The method of claim 1, the second state of an event generator comprising a state of the event generator after an event is called upon the event generator.
15. The method of claim 1, the states comprising one or more sets of properties for an element.
16. The method of claim 1, associating by replacing a reference to an event handler function with a reference to a monitoring wrapper function.
17. A system configured to record an event set from a user interface, comprising:
an instruction injector configured to inject monitoring wrapper function instructions into the user interface instructions, the monitoring wrapper function instructions comprising:
a first monitoring wrapper function configured to record a first state of an event generator; and
a second monitoring wrapper function configured to:
record a second state of an event generator; and
send the first state and the second state to a recording engine;
an event handler monitoring wrapper generator configured to:
associate a first reference to the one or more monitoring wrapper functions with one or more event handlers; and
associate a second reference to the one or more monitoring wrapper functions, subsequent to the first reference, with the one or more event handlers, the second reference comprising:
at least one set of instructions between the first reference and the second reference in the event handler.
18. The system of claim 17, comprising:
an instruction injector configured to replace user interface instructions that determine event handler registration and deregistration with new event handler registration and deregistration instructions;
a wrapper generator configured to generate one or more monitoring wrapper functions for one or more event handlers upon calling of an event on one or more event generators; and
a reference storage component configured to store the called one or more references to the one or more event handler functions and the one or more references to the one or more monitoring wrapper functions.
19. The system of claim 17, the monitoring wrapper function instructions configured to:
record a state of an event generator prior to invocation of an event;
call one or more event handler functions called by the one or more events;
record a state of an event generator after completion of the event; and
pass the states to a recording engine.
20. A method for recording an event set from a user interface, comprising:
for one or more event generators, replacing instructions that determine event handler registration and deregistration with new event handler registration and deregistration instructions;
upon invocation of an event upon one or more event generators, generating one or more monitoring wrapper functions for one or more event handlers;
injecting one or more monitoring wrapper functions in the user interface instructions, the one or more monitoring wrapper functions comprising:
a first monitoring wrapper function configured to record a first state of an event generator; and
a second monitoring wrapper function configured to:
record a second state of an event generator; and
send the first state and the second state to a recording engine;
associating a first reference to the one or more monitoring wrapper functions with one or more event handlers;
associating a second reference to the one or more monitoring wrapper functions, subsequent to the first reference, with the one or more event handlers, comprising:
at least one set of instructions between the first reference and the second reference in the event handler; and
storing the called one or more references to the one or more event handler functions and the one or more references to the one or more monitoring wrapper functions.