KR102432684B1 - Weapon control system capable of firing varous bullets - Google Patents

Abstract

A weapon control system according to an embodiment of the present invention includes: a system initialization unit for initializing the system when driving power is supplied; a bullet type recognition unit for recognizing a type of ammunition based on a signal received from the pod of the ammunition; Flight control interlocking task unit for receiving a command to fire the bullet from the operation console, and transmitting the command execution result and period data to the operation console; an ammunition module management task unit for selecting an ammunition module corresponding to the type of ammunition and managing the ammunition type module; And it characterized in that it comprises a firing procedure proceeding unit for proceeding the firing of the bullet according to the firing procedure module selected by the ammunition module management task unit.

Description

A weapon control system capable of firing a variety of bullets {WEAPON CONTROL SYSTEM CAPABLE OF FIRING VAROUS BULLETS}

An embodiment of the present invention relates to a weapon control system capable of firing various bullets, and in particular, a weapon control system capable of firing various rockets or various bullets capable of firing various bullets by efficiently using resources.

In general, a weapon control system for firing bullets has a problem in that it is difficult to manage various types of bullets.

Specifically, the conventional weapon control system requires redevelopment of the periodic guidance processing module, the aperiodic guidance processing module, and the Flight Control System (FCS) interlocking task management module whenever a new type of ammunition is added. and time consuming problem. In addition, in the conventional weapon control system, whenever a new bullet is added, modules (eg, periodic induction processing module, aperiodic induction processing module, task management module linked to the flight control system, etc.) need to be redeveloped. , cost a lot.

In particular, whenever the type of ammunition of the weapon control system is changed, the interface control document (ICD) for the ammunition, the flight control system interlocking task management module, the periodic induction processing module, the aperiodic induction processing module and module verification The system must be redeveloped. Here, the cycle induction processing module may process periodic data and perform device (hardware) and program (software) initialization functions. Since the aperiodic induction processing module processes and receives aperiodic data and proceeds with the launch procedure, the command of the task management module linked to the flight control system is transmitted to the rocket (tank), and then the execution result is delayed Alternatively, omissions may occur, which makes it difficult to smoothly proceed with the launch procedure of the aperiodic induction processing module.

Korean Patent Registration No. 10-1978489, 'A device and method for controlling and managing the launch of a guided weapon projectile' (registered on May 8, 2019) Korean Patent Registration No. 10-1788195, 'A method for performing power control on a launch vehicle and platform and an apparatus for performing the same' (Registered on April 24, 2017)

It is an object of the present invention to provide a weapon control system that can launch a rocket or bullet immediately by adding a new rocket or bullet launch procedure (eg, a scenario), thereby saving development cost and development time.

Another object of the present invention is to provide a weapon control system capable of launching a small rocket, a large surface-to-air rocket, a large surface-to-air rocket, and the like in one system.

Another object of the present invention is to provide a weapon control system that is optimized to be operated in an operating system (eg, VxWorks) of an embedded system and can efficiently use the resources of the operating system.

A weapon control system according to an embodiment of the present invention includes: a system initialization unit for initializing the system when driving power is supplied; a bullet type recognition unit for recognizing a type of ammunition based on a signal received from the pod of the ammunition; Flight control interlocking task unit for receiving a command to fire the bullet from the operation console, and transmitting the command execution result and period data to the operation console; an ammunition module management task unit for selecting an ammunition module corresponding to the type of ammunition and managing the ammunition type module; And it characterized in that it comprises a firing procedure proceeding unit for proceeding the firing of the bullet according to the firing procedure module selected by the ammunition module management task unit.

In the present invention, the ammunition module management task unit selects a bullet type module corresponding to a type of ammunition from a bullet type module management tree including a plurality of ammunition type modules corresponding to a plurality of bullets, and the plurality of bullets is a first a bullet, a second bullet, and a third bullet; The third bullet is characterized in that it is different from each other.

In the present invention, the ammunition module management task unit, periodic data reception task for periodically receiving the state information of the ammunition; an aperiodic data reception task for confirming the processing result of the command received from the operation console and transmitting it to the operation console; And it characterized in that it comprises a scenario progress task for transmitting the command of the operation console to the bullet.

In the present invention, when firing the first bullet, which is a guided bullet, the firing procedure progress unit includes a first bullet periodic induction module, a first bullet aperiodic induction module, and an induction control module, and the periodic data receiving task includes: Initialization is performed in the first bullet period induction module based on the first bullet control module, and period data is transmitted to the flight control interlocking task and the induction control module, and the aperiodic data receiving task includes the first bullet Initialization is performed in the first bullet aperiodic induction module based on a control module, and a command requested by the flight control interlocking task is received, and the induction control module is configured to include the first bullet period induction module and the first bullet ratio Based on the result received from the periodic guidance module, it is characterized in that the bullet firing procedure is performed.

In the present invention, the first bullet period induction module communicates with the first bullet in a user data protocol communication method, and the first bullet aperiodic induction module communicates with the first bullet in a TCP/IP communication method. characterized by performing.

In the present invention, when firing the second bullet, which is an unguided bullet, the firing procedure progressing unit includes a second bullet non-guided control module, and the periodic data reception task is initialized by the second bullet non-guided control module. and is changed to an idle state, the aperiodic data reception task is in an idle state in the second bullet non-guided control module, and the second bullet non-guided control module is received in the flight control interlocking task It is characterized in that the firing procedure is carried out based on the command given.

In the present invention, the second bullet non-guided control module is characterized in that the communication with the second bullet in a discrete signal communication method.

In the present invention, the launch procedure progress unit is characterized in that it has an interface structure using a callback function.

In the present invention, it is characterized in that it further comprises a power supply for supplying driving power to the system.

In the present invention, it is characterized in that it further comprises a communication unit for transmitting the firing command to the bullet and for receiving the command result from the bullet.

The weapon control system of the present invention has the effect of saving development cost and development time because a new rocket or bullet launch procedure (eg, scenario) can be immediately added by adding a rocket or bullet.

In addition, the weapon control system of the present invention has the effect of being able to launch a small rocket, a large surface-to-air rocket, a large surface-to-air rocket, etc. in one system.

In addition, the weapon control system of the present invention is optimized to be operated in an embedded system (eg, VxWorks) and has the effect of efficiently using the resources of the operating system.

1 is a view showing a weapon control system, an operation console, and a plurality of bullets according to an embodiment of the present invention.
2 is a diagram illustrating a weapon control system according to an embodiment of the present invention.
3 is a view showing a firing procedure progress unit according to an embodiment of the present invention.
4 is a view showing a bullet type module management task unit according to an embodiment of the present invention.
5 is a diagram illustrating an operation of a weapon control system according to an embodiment of the present invention.
6 is a diagram illustrating an operation of a weapon control system according to an embodiment of the present invention.
7 is a diagram illustrating an operation of a weapon control system according to an embodiment of the present invention.

The present invention will be described in more detail.

Hereinafter, embodiments of the present invention and other matters necessary for those skilled in the art to easily understand the contents of the present invention will be described in detail with reference to the accompanying drawings. However, since the present invention can be embodied in various different forms within the scope of the claims, the embodiments described below are merely exemplary regardless of whether they are expressed or not.

Like reference numerals refer to like elements. In addition, in the drawings, thicknesses, ratios, and dimensions of components are exaggerated for effective description of technical content. “And/or” may include any combination of one or more that the associated configurations may define.

Terms such as first, second, etc. may be used to describe various elements, but the elements should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component. The singular expression may include the plural expression unless the context clearly dictates otherwise.

In addition, terms such as "below", "below", "above", "upper" and the like are used to describe the relationship of the components shown in the drawings. The above terms are relative concepts, and are described with reference to directions indicated in the drawings.

Terms such as “comprise” or “have” are intended to designate that a feature, number, step, operation, component, part, or combination thereof described in the specification is present, and includes one or more other features, number, or step. , it should be understood that it does not preclude the possibility of the existence or addition of , operation, components, parts or combinations thereof.

That is, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and when it is said that a part is connected to another part in the following description, it is directly connected In addition, it may include a case in which another element is electrically connected therebetween. In addition, it should be noted that the same components in the drawings are denoted by the same reference numbers and symbols as much as possible even though they are indicated in different drawings.

1 is a diagram illustrating a weapon control system 10 , an operation console 15 , and a plurality of bullets 20 according to an embodiment of the present invention.

Referring to FIG. 1 , the weapon control system 10 may fire a plurality of bullets 20 as a single system. In addition, the weapon control system 10 can fire the rocket or bullet immediately by adding a new rocket or bullet launch procedure (eg, a scenario).

The operation console 15 means a device carried by an administrator, and may transmit a firing command to the weapon control system 10 . At this time, the weapon control system 10 may fire a plurality of bullets 20 according to a firing command.

The plurality of bullets 20 may include a first bullet 30 , a second bullet 40 , and a third bullet 50 . However, the present invention is not limited thereto, and according to an embodiment, the weapon control system 10 may fire four or more bullets 20 . In this case, the first bullet 30 , the second bullet 40 , and the third bullet 50 may mean different types of bullets. For example, the first bullet 30 may be any one of a small bullet, a large surface-to-air missile, and a large surface-to-air missile, and the second bullet 40 may be any one different from the first bullet 30, and the third bullet (50) may be any one different from the first bullet 30 and the second bullet 40.

2 is a diagram illustrating a weapon control system 10 according to an embodiment of the present invention.

Referring to FIG. 2 , the weapon control system 10 includes a system power supply unit 100 , a system initialization unit 200 , an ammunition type recognition unit 300 , a flight control interlocking task unit 400 , and an ammunition type module management task unit 500 . , it may include a launch procedure progress unit 600 and a communication unit 700 .

The system power supply unit 100 may supply driving power to each component of the weapon control system 10 . For example, the system power supply unit 100 may be powered-on according to a user's control.

The system initialization unit 200 may initialize the weapon control system 10 when driving power is supplied by the system power supply unit 100 .

When the weapon control system 10 is initialized, the bullet type recognition unit 300 may recognize the type of ammunition based on a signal (eg, a characteristic value) received from the pod of the ammunition. In the present specification, the pod (pod) refers to objects of a structure in which various equipment is loaded in a cylindrical or box-shaped or similar case among objects mounted on the outside of the bullet.

Flight control interworking task unit 400 may receive a command to launch a bullet (eg, rocket, etc.) from the operation console, and transmit the command execution result and period data to the operation console.

The ammunition module management task unit 500 may select a firing procedure module (eg, an ammunition module) corresponding to the type of ammunition and manage the firing procedure module. For example, the ammunition module management task unit 500 may manage the firing procedure module by performing initialization of the firing procedure module, execution of the firing procedure module, termination of the firing procedure module, and the like. In this specification, the firing procedure module may be referred to as an ammunition module.

For example, the ammunition module management task unit 500 may select a bullet type module corresponding to the type of ammunition from the ammunition type module management tree including a plurality of ammunition type modules corresponding to the plurality of bullets.

The firing procedure progress unit 600 may proceed with firing the bullet according to the firing procedure module selected by the bullet type module management task unit 500 . In addition, the launch procedure progress unit 600 may generate a launch command.

The communication unit 700 may transmit the command of the firing procedure progress unit 600 to the bullet. Also, the communication unit 700 may receive the command result from the bullet.

3 is a diagram illustrating a firing procedure progress unit 600 according to an embodiment of the present invention.

Referring to FIG. 3 , the launch procedure progress unit 600 may have an interface structure using a call back function.

Item [1] shown in FIG. 3 indicates the interface function configuration.

Item [2] shown in Fig. 3 shows the algorithm structure of the launch procedure based on the interface function.

Item [3] shown in FIG. 3 indicates that the tanjong module management tree is managed using a list sort algorithm. In this case, the primary key is the name of the module, and may be used when searching for a target ammunition module from the ammunition type module management tree.

For example, the ammunition module management tree may include a plurality of ammunition modules corresponding to a plurality of bullets.

According to an embodiment, the plurality of bullets may include first to third bullets, and the plurality of bullet type modules may include a first bullet control module, a second bullet control module, and a third bullet control module.

Second, the first to third bullets may be different types of bullets, and the first bullet control module, the second bullet control module, and the third bullet control module may also be different modules.

4 is a view showing the ammunition module management task unit 500 according to an embodiment of the present invention.

The bullet module management task unit 500 may include a periodic data reception task 510 , an aperiodic data reception task 520 , and a scenario progress task 530 .

The conventional aperiodic induction processing L/R module performs the firing procedure, but the aperiodic data reception task 520 of the ammunition module management task unit 500 of the present invention manages only the aperiodic data, and the firing procedure proceeds. is performed in the scenario progress task 530 .

The scenario progress task 530 performs only the launch procedure, and can accurately manage the launch procedure. In addition, the scenario progress task 530 can perform a procedure precisely at a time point that should be performed at a specified time point, and can respond immediately even when an error occurs.

The periodic data reception task 510 may periodically receive bullet state information. In this case, initialization of a user data protocol (UDP), a synchronous data link control (SDLC), a discrete signal device, and the like may also be performed. In particular, UDP and SDLC may periodically receive bullet status information and transmit it to the operation console and the scenario progress task 530 .

The aperiodic data reception task 520 may check the processing result of a command received from the operation console and transmit it to the operation console. In addition, the aperiodic data reception task 520 may allocate the processing result to the launch procedure progress unit 600 (refer to FIG. 2 ). In this case, the communication method uses Transmission Control Protocol/Internet Protocol (TCP/IP), and when a synchronous data link control or a discrete signal device is used, it may exist in an idle (IDLE) state that is not driven.

The scenario progress task 530 may receive bullet state information. In addition, the scenario progress task 530 may receive the command of the operation console, transmit it to the bullet, and proceed with the firing procedure.

The flight control interlocking task unit 400 (see FIG. 2 ) may receive a command received from an operation console (not shown), and receive a command result from the bullet. In addition, the flight control interworking task unit 400 may manage period information.

The weapon control system according to the embodiment of the present invention uses an ICD (Interface Control Document) communication module used in the flight control interlocking task unit 400, and can be used without additional development whenever a bullet launch procedure is added. have. That is, the weapon control system of the present invention does not develop a new program for each type of ammunition, and if a firing procedure for any type of ammunition is defined, it can be registered in the ammunition management list and fired.

5 is a diagram illustrating the operation of the weapon control system 10 according to an embodiment of the present invention. 5 shows in detail the operation of the weapon control system 10 that fires the first bullet 30 that is a guided missile.

1 to 5, the firing procedure progress unit 600 indicates a bullet type module (eg, a first bullet control module) corresponding to the first bullet 30, the first bullet cycle induction module 610, The first bullet may include an aperiodic induction module 620 and an induction control module 630 .

The periodic data reception task 510 and the aperiodic data reception task 520 may check the type of bullet from the bullet. In addition, the periodic data reception task 510 and the aperiodic data reception task 520 may find a bullet type module for executing the firing procedure for the first bullet 30 in the first node of the bullet type module management tree.

The cycle data reception task 510 may perform initialization in the first round cycle induction module 610 based on the found round module (eg, the first round control module). The period data reception task 510 may receive period data and allocate the data to the launch procedure progress of the flight control interworking task unit 400 and the induction control module 630 . For example, the period data reception task 510 may initialize the first bullet period induction module 610 and transmit the received period data to the flight control interworking task unit 400 and the induction control module 630 .

The aperiodic data reception task 520 may perform initialization in the first bullet aperiodic induction module 620 based on the discovered bullet type module (eg, the first bullet control module). The aperiodic data reception task 520 may receive a command requested by the flight control interworking task unit 400 through the scenario progress task 530 . In addition, the aperiodic data reception task 520 may receive the result performed in the command progress of the induction control module 630 and assign it to the flight control interlocking task unit 400 and the launch procedure of the induction control module 630 . have.

The induction control module 630 may perform a bullet firing procedure and fire a bullet based on the results received from the first bullet periodic induction module 610 and the first bullet aperiodic induction module 620 . At this time, the induction control module 630 may check the firing, departure, igniter signal, etc. of the bullet using the discrete signal value.

At this time, the first bullet periodic induction module 610 performs communication with the first bullet 30 in a user data protocol (UDP) communication method, and the first bullet aperiodic induction module 620 is the first bullet 30 . and TCP/IP communication method. Other signal communication between the weapon control system 10 and the first round 30 may be performed via discrete signals.

6 is a diagram illustrating the operation of the weapon control system 10 according to an embodiment of the present invention. 6 illustrates in detail the operation of the weapon control system 10 for firing the second bullet 40, which is an unguided missile.

1 to 6 , the firing procedure progress unit 600 indicates a bullet type module (eg, a second bullet control module) corresponding to the second bullet 40, and the second bullet non-guided control module 640 . may include

The weapon control system 10 of the present invention can fire the second bullet 40, which is an unguided bullet, using only the discrete signal.

The periodic data reception task 510 and the aperiodic data reception task 520 may check the type of bullet from the bullet. That is, the periodic data reception task 510 may determine that it is the second bullet 40 and select a corresponding ammunition type module (eg, the second bullet control module).

In addition, the periodic data reception task 510 may be changed to an idle (IDLE) state after initialization is performed in the second non-guided control module 640 .

In addition, the aperiodic data reception task 520 may exist in an idle (IDLE) state in the second non-guided control module 640 without performing a special operation.

The second bullet non-guided control module 640 proceeds with the firing procedure based on the command received from the flight control interlocking task unit 400, and firing, italing, igniter signals of bullets, etc. can be confirmed using discrete signal values. have.

At this time, the second bullet non-guided control module 640 may communicate with the second bullet 40 in a discrete signal communication method.

7 is a diagram illustrating the operation of the weapon control system 10 according to an embodiment of the present invention. 7 shows in detail the operation of the weapon control system 10 for firing the third bullet 50 using the SDLC (RS-422).

1 to 7 , the firing procedure progress unit 600 indicates a bullet type module (eg, a third bullet control module) corresponding to the third bullet 50 , and includes a third bullet control module 650 . can do.

The third bullet 50 may fire the bullet using Synchronous Data Link Control (SDLC) (eg, RS-422). In this specification, RS-422 means EIA-422 or 　TIA-422, and means a technical standard that defines 'electrical characteristics of a balanced digital interface circuit'.

The periodic data reception task 510 and the aperiodic data reception task 520 may check the bullet type, select an appropriate module, and initialize the SDLC device in the periodic data reception task 510 .

The periodic data reception task 510 and the aperiodic data reception task 520 may receive periodic data and aperiodic data transmitted in the third bullet 50 .

The period data reception task 510 may assign a value in the course of the launch procedure of the flight control interlocking task unit 400 and the third bullet control module 650 .

Since the aperiodic data reception task 520 does not perform a special operation, it may exist in the IDLE state in the third bullet control module 650 .

The third bullet control module 650 may proceed with the firing procedure based on the command transmitted from the flight control interlocking task unit 400 and the value transmitted from the third bullet 50 .

The third bullet control module 650 may check the firing, departure, and igniter signals of bullets using discrete signal values.

In this case, the third bullet control module 650 may communicate with the third bullet 50 in an SDLC or discrete signal communication method.

Through the above-described method, the weapon control system of the present invention can fire various bullets (rockets) with one system.

In addition, the weapon control system of the present invention divides the module into a common part and a non-common part and designs and develops the module, so that if there is a scenario for ammunition, any ammunition can be registered in the ammunition management module and fired. Here, the common part does not modify the ICD or algorithm when changing the scenario, and the non-public part develops a scenario for each type of ammunition and registers it in the ammunition management module tree. There is an effect that can be done. In this system, the common part is verified, and when a new ammunition is added, it is only necessary to verify the ammunition type, so that a reliable scenario algorithm can be developed.

The weapon control system of the present invention has the effect of saving development cost and development time because a new rocket or bullet launch procedure (eg, scenario) can be immediately added by adding a rocket or bullet.

In addition, the weapon control system of the present invention has the effect of being able to launch a small rocket, a large surface-to-air rocket, a large surface-to-air rocket, etc. in one system.

In addition, the weapon control system of the present invention is optimized to be operated in an embedded system (eg, VxWorks) and has the effect of efficiently using the resources of the operating system.

The functional operations described herein and the embodiments related to the present subject matter are implemented in digital electronic circuits or computer software, firmware or hardware, including the structures disclosed herein and structural equivalents thereof, or in combination of one or more of these It is possible.

Embodiments of the subject matter described herein relate to one or more computer program products, ie one or more computer program instructions encoded on a tangible program medium for execution by or for controlling the operation of a data processing device. It can be implemented as a module. A tangible program medium may be a radio wave signal or a computer-readable medium. A radio wave signal is an artificially generated signal, eg, a machine-generated electrical, optical or electromagnetic signal, that is generated to encode information for transmission to an appropriate receiver device for execution by a computer. The computer readable medium may be a machine readable storage device, a machine readable storage substrate, a memory device, a combination of materials that affect a machine readable radio wave signal, or a combination of one or more of these.

A computer program (also known as a program, software, software application, script or code) may be written in any form of any programming language, including compiled or interpreted language or a priori or procedural language, as a stand-alone program or module; It can be deployed in any form, including components, subroutines, or other units suitable for use in a computer environment.

A computer program does not necessarily correspond to a file on a file device. A program may be stored in a single file provided to the requested program, or in multiple interacting files (eg, files storing one or more modules, subprograms, or portions of code), or in files holding other programs or data. It may be stored within some (eg, one or more scripts stored within a markup language document).

A computer program may be deployed to be executed on a single computer or multiple computers located at one site or distributed over a plurality of sites and interconnected by a communication network.

Additionally, the logic flows and structural block diagrams described in this patent document describe corresponding acts and/or specific methods supported by corresponding functions and steps supported by the disclosed structural means, and corresponding It can also be used to build software structures and algorithms and their equivalents.

The processes and logic flows described herein may be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating outputs.

Processors suitable for the execution of computer programs include, for example, both general and special purpose microprocessors and any one or more processors of any form of digital computer. Typically, the processor will receive instructions and data from either read-only memory or random access memory or both.

A key component of a computer is one or more memory devices for storing instructions and data and a processor for executing instructions. In addition, a computer is generally configured to be operable to receive data from, transmit data to, or perform both such operations on one or more mass storage devices for storing data, such as, for example, magnetic, magneto-optical disks or optical disks. combined or will include. However, the computer need not have such a device.

The present description sets forth the best mode of the invention, and provides examples to illustrate the invention, and to enable any person skilled in the art to make or use the invention. This written specification does not limit the present invention to the specific terms presented.

Although the above has been described with reference to the preferred embodiment of the present invention, those skilled in the art or those having ordinary knowledge in the technical field will not depart from the spirit and technical scope of the present invention described in the claims to be described later. It will be understood that various modifications and variations of the present invention can be made without departing from the scope of the present invention.

Accordingly, the technical scope of the present invention should not be limited to the contents described in the detailed description of the specification, but should be defined by the claims.

10: Weapon Control System
100: system power unit
200: system initialization unit
300: bullet type recognition unit
400: flight control interlocking task unit
500: ammunition module management task unit
600: launch procedure progress unit
700: communication department

Claims (10)

a system initialization unit for initializing the system when driving power is supplied;
a bullet type recognition unit for recognizing a type of ammunition based on a signal received from the pod of the ammunition;
a flight control interlocking task unit for receiving a firing command of a bullet from the operation console, and transmitting a command execution result and period data to the operation console;
an ammunition module management task unit for selecting an ammunition module corresponding to the type of ammunition and managing the ammunition type module; and
and a firing procedure progress unit for proceeding firing of the bullet according to the firing procedure module selected by the ammunition module management task unit,
The ammunition module management task unit selects an ammunition module corresponding to the type of ammunition from the ammunition module management tree including a plurality of ammunition modules corresponding to a plurality of bullets,
The plurality of bullets include a first bullet, a second bullet, and a third bullet,
The plurality of bullet type modules include a first bullet control module, a second bullet control module, and a third bullet control module,
The first bullet, the second bullet and the third bullet are characterized in that they are different from each other,
weapon control system. delete According to claim 1,
The ammunition module management task unit,
a periodic data receiving task for periodically receiving the state information of the bullet;
an aperiodic data reception task for confirming the processing result of the command received from the operation console and transmitting it to the operation console; and
Characterized in that it comprises a scenario progress task for transmitting the command of the operation console to the bullet,
weapon control system. 4. The method of claim 3,
When firing the first bullet, which is a guided missile,
The firing procedure progress unit includes a first bullet periodic induction module, a first bullet aperiodic induction module and an induction control module,
The period data reception task, based on the first bullet control module, performs initialization in the first bullet period induction module, and transmits period data to the flight control interlocking task and the induction control module,
The aperiodic data reception task performs initialization in the first bullet aperiodic induction module based on the first bullet control module, and receives a command requested by the flight control interlocking task,
The induction control module, characterized in that based on the results received from the first bullet periodic induction module and the first bullet aperiodic induction module, to perform a bullet firing procedure,
weapon control system. 5. The method of claim 4,
The first bullet cycle induction module communicates with the first bullet in a user data protocol communication method,
The first bullet aperiodic induction module is characterized in that it communicates with the first bullet in a TCP/IP communication method,
weapon control system. 4. The method of claim 3,
When firing the second bullet, which is an unguided bullet,
The firing procedure progress unit includes a second bullet non-guided control module,
The periodic data reception task is initialized in the second non-guided control module, and is changed to an idle state,
The aperiodic data reception task exists in an idle state in the second non-guided control module,
The second bullet non-guided control module, characterized in that the launch procedure is carried out based on the command received from the flight control interlocking task,
weapon control system. 7. The method of claim 6,
The second bullet non-guided control module, characterized in that to perform communication with the second bullet in a discrete signal communication method,
weapon control system. a system initialization unit for initializing the system when driving power is supplied;
a bullet type recognition unit for recognizing a type of ammunition based on a signal received from the pod of the ammunition;
a flight control interlocking task unit for receiving a firing command of a bullet from the operation console, and transmitting a command execution result and period data to the operation console;
an ammunition module management task unit for selecting an ammunition module corresponding to the type of ammunition and managing the ammunition type module; and
and a firing procedure progress unit for proceeding firing of the bullet according to the firing procedure module selected by the ammunition module management task unit,
The launch procedure progress unit, characterized in that it has an interface structure using a callback function,
weapon control system.
According to claim 1,
Characterized in that it further comprises a power supply for supplying driving power to the system,
weapon control system. 10. The method of claim 9,
Transmitting the firing command to the bullet, characterized in that it further comprises a communication unit for receiving a command result from the bullet,
weapon control system.

Images