JP5583073B2 - Tracking antenna control device - Google Patents

Description

  The present invention relates to a tracking antenna control apparatus.

  The tracking antenna can be used for a variety of purposes, including satellites, rocket communications, and astronomical telescopes. The control program of the tracking antenna control apparatus has a common drive function for tracking automatically or manually, and this is handled as a drive mode. For example, drive modes possessed by the control for rocket communication include an automatic tracking mode, a program tracking mode, and a manual mode. The drive modes that the control for the astronomical telescope has include a program tracking mode and a manual mode. Here, even if the models are different, the program structure of the drive mode is similar. For this reason, it is desired to realize a development efficiency by sharing a drive mode program among models.

  For example, the following patent documents 1 to 3 describe a technique for sharing a program. In Patent Document 1, the same software is installed in each sub-central processing means for generating estimated antenna directivity data, and when the condition is changed, only the software of the sub CPU corresponding to the changed tracking station is stored. An invention is described in which the setting is changed by manipulating the unique parameter. Patent Document 2 describes an invention that allows a plurality of types of vehicles to be handled by selectively executing a vehicle control program including a dedicated portion for each vehicle type. In Patent Document 3, software parts are divided into a common part and a different part in a plurality of software, the common part is not allowed to be modified, and different parts are strengthened to the extent that they do not hinder development. An invention for sharing parts and facilitating diversion is described.

JP-A-8-29525 JP 2002-303203 A JP 2005-56012 A

  In Patent Documents 1 to 3, software customization methods by adding parameters and processes are proposed. However, each has the following problems.

  Since the technology described in Patent Document 1 can cope with changes in software conditions using specific parameters, it is possible to easily realize model-specific specifications for functions established by program logic. There is. However, there is a problem that it cannot be applied when the program logic needs to be changed depending on the model.

  The technology described in Patent Document 2 has a dedicated unit for each model and can be selectively executed to support multiple types of models. There is an advantage that it can respond to. However, since it is necessary to create a dedicated program for each vehicle type, there is a problem that the development amount of the entire product line becomes large.

  The technique described in Patent Document 3 has an advantage that development efficiency can be improved because a portion common to a plurality of software can be reused when developing other software. However, there is a problem in that development efficiency deteriorates when changes occur in common parts as software expands.

  In the control program of the tracking antenna control device, it is a challenge to achieve both high reusability of the program and customization flexibility required for model development. As a feature of the control program for the tracking antenna device, a different control method can be selected by selecting a drive mode, and this control method is almost the same regardless of the model, while the drive mode provided by a specific model is a product series. It is a subset of the drive mode group defined in common as a whole, and the transition determination process between the drive modes is greatly different for each model. If a control program for a tracking antenna control device having such a feature is to be constructed by the methods listed in Patent Documents 1 to 3, development by a single model is caused by the problems described in the respective sections of Patent Documents 1 to 3. There arises a problem that the efficiency is lowered or the development amount of the entire product line is increased.

  The present invention has been made in view of the above, and an object of the present invention is to obtain a tracking antenna control apparatus capable of improving development efficiency when a variety of devices equipped with a tracking antenna are deployed. .

  In order to solve the above-described problems and achieve the object, the present invention provides a drive mode which is a drive function of a tracking antenna, and is selected from a plurality of common drive modes regardless of the type of device mounted. A tracking antenna control apparatus that controls the tracking antenna by selecting at least two codes, and the control program for the tracking antenna is a code that is common to all models regardless of the type of the apparatus having the tracking antenna. And a unique part consisting of a code that realizes a drive mode transition process unique to a specific type of device among devices equipped with a tracking antenna, and when executing the control program A setting unit that holds a result of selecting one or more drive modes from the plurality of types of drive modes as information to be referred to by the specific unit; And features.

  ADVANTAGE OF THE INVENTION According to this invention, the function addition or change to the tracking antenna control program of the apparatus provided with the tracking antenna becomes easy, and there exists an effect that the development efficiency at the time of multi-model expansion can be improved.

FIG. 1 is a diagram illustrating a configuration example of a tracking antenna control apparatus. FIG. 2 is a diagram showing a drive control program configuration and a drive processing control method. FIG. 3 is a flowchart showing a flow of processing of a control program in the tracking antenna control apparatus. FIG. 4 is a flowchart showing details of the process executed in step S4 of FIG. FIG. 5 is a diagram illustrating an example of source code indicating the process executed in step S4 of FIG. FIG. 6 is a flowchart showing details of the process executed in step S5 of FIG. FIG. 7 is a diagram illustrating an example of source code indicating the process executed in step S5 of FIG. FIG. 8 is a flowchart showing details of the process executed in step S6 of FIG. FIG. 9 is a diagram showing an example of source code indicating the process executed in step S6 of FIG. FIG. 10 is a flowchart showing details of the process executed in step S7 of FIG. FIG. 11 is a diagram showing an example of source code indicating the process executed in step S7 of FIG. FIG. 12 is a diagram illustrating a configuration at the time of executing the driving process.

  Embodiments of a tracking antenna control apparatus according to the present invention will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

Embodiment.
FIG. 1 is a diagram showing a configuration example of a tracking antenna control apparatus according to the present invention. As will be described in detail later, this tracking antenna control device selects at least one of a plurality of common driving modes as a driving mode, which is a driving function of the tracking antenna, regardless of the installed model. Control the tracking antenna. As shown in FIG. 1, the tracking antenna control device 1 includes a CPU 2, a file system 3, and a RAM 4.

  The file system 3 includes a control program 5 and data 6. The control program 5 includes a common unit 7 and a specific unit 8, and the common unit 7 is a control program that is commonly used by all models in the product line related to the tracking antenna. Therefore, the common unit 7 does not need to be changed regardless of the model when it is mounted. The specific unit 8 is a control program that realizes the operation of a specific model in the product line related to the tracking antenna. The operation of the specific model is a drive mode state transition process, and the control program of the specific unit 8 is added to the extension point set in the common unit 7. The data 6 includes a setting unit 9. The setting unit 9 includes a list (function selection table 10) for switching the valid / invalid of drive modes existing in the product series of tracking antennas for each model and a list for registering the state transition process of the drive mode ( And a construction list 11). These lists are changed in advance according to the model in which the control program is installed. The function selection table 10 registers the selection result of the drive mode to be mounted on the mounted model, and the construction list 11 registers the state transition process corresponding to the function selection table 10. A memory image in which execution programs of the common unit 7, the unique unit 8, and the setting unit 9 are arranged on the RAM 4 is the common unit 12, the unique unit 13, and the setting unit 14.

  The configuration and control method of the drive control program will be described with reference to FIG. The common unit 7 includes a drive mode 71, a function selection table call process 72, a function selection table data storage 73, a function selection table access I / F 74, a construction list call process 75, an extension process 76, and an extension point. 77.

  The drive mode 71 has a common drive mode process (in this example, an automatic tracking mode 71a, a program tracking mode 71b, a manual mode 71c, and a position mode 71d). The automatic tracking mode 71a is a mode for autonomously tracking a tracking target such as a rocket, and the program tracking mode 71b is a mode for operating the antenna in accordance with a pre-programmed trajectory. The manual mode 71c is a mode in which the antenna shaft is operated according to a human operation, and the position mode 71d is a mode in which the antenna is directed in a specified specific direction.

  The function selection table calling process 72 is a process for calling the function selection table 10 in the setting unit 9. The function selection table data storage 73 stores the information of the function selection table 10. The function selection table access I / F 74 is an I / F for the drive mode 71 to refer to the function selection data storage 73. The construction list calling process 75 is a process for calling the construction list 11 in the setting unit 9. The extension process 76 is a process for calling a model-specific drive mode transition process registered in the extension point 77. The extension point 77 is a place where a model-specific drive mode transition process is registered. The setting unit 9 exists for each model, and holds a function selection table 10 and a construction list 11. The unique unit 8 exists for each model and includes a drive mode transition process 81 and a construction process 82. The drive mode transition process 81 is a state transition process of a model-specific drive mode. The construction process 82 is a process for registering the drive mode transition process 81 in the extension point 77 of the common unit 7.

  FIG. 3 is a flowchart showing the flow of processing of the control program in the tracking antenna control apparatus of the present embodiment. With reference to FIG. 3, the flow of processing of the control program will be described. First, in step S1, the execution programs of the common unit 7, the specific unit 8, and the setting unit 9 shown in FIG. 2 are expanded on the RAM 4 (see FIG. 1). Next, in step S2, program initialization processing is performed, and in step S3, program initialization processing is performed.

  In the initialization process in step S2, first, the drive mode transition process 81 is registered in the extension point 77 of the common unit 7 (step S4), and then the drive mode of the common unit 7 is enabled / disabled according to the function selection table 10. Processing is determined (step S5).

  Details of step S4 will be described with reference to the flowchart of FIG. 4 and the source code example of FIG. Note that the flowchart of FIG. 4 shows details of the processing executed in step S4. In starting the process of step S4, first, the construction list 11 in the setting unit 9 is called from the construction call processing 75 (see FIG. 2) included in the common unit 7. In C3 of FIG. 5, a function (construct_drive_mode_hook_impl) for executing the drive mode transition process 81 is defined as a construction list. The construction call process calls the construction list 11 using the address of the construction list as an argument of the function (constructlist_call) of the construction call process indicated by C1.

  When the construction list 11 is called, the called construction list 11 is read sequentially from the top, and it is determined whether or not the read line is the end (step S41). If the read line is at the end (step S41: Yes), the process ends. On the other hand, when the read line is not the end (step S41: No), it is determined whether or not the construction process is registered in the construction list 11 (step S42). These steps S41 and S42 correspond to the if statement of the construction list call process shown in C1 of FIG. 5, and determine the end of the construction list and whether or not the construction process is registered. If the construction process is registered as a result of the determination in step S42 (step S42: Yes), the construction call process 75 calls the construction process 82, and the address of the function of the drive mode transition process 81 is the extension point 77 of the common unit 7. (Step S43). In step S43, the constructlist_call shown in C1 of FIG. 5 calls the function construct_drive_mode_hook_impl that executes the construction process shown in C4, and registers the function of the drive mode transition process in the extension points init, pre, and post shown in C2.

  After executing step S43, or when it is determined in step S42 that the construction process is not registered (step S42: No), the pointer of the construction list 11 is advanced by one as the next process (step S44). And step S41-S43 mentioned above is performed again. Thereafter, the processing is continued until it is determined as “end” in step S41 (the processing ends when it is determined as “end”).

  Next, details of step S5 will be described with reference to the flowchart of FIG. 6 and the source code example of FIG. Note that the flowchart of FIG. 6 shows details of the processing executed in step S5.

  In step S5, first, the function selection table calling process 72 of the common unit 7 calls the function selection table 10 (step S51). In C5 of FIG. 7, an example of the function selection table 10 is shown. In the illustrated function selection table, valid (YES) / invalid (NO) of the drive mode is defined. This definition is stored in the variable indicated by C7, and the function selection table call processing 72 calls the function selection table 10 using the variable address as an argument of the function setVariability of the function selection table call processing indicated by C7. Further, the function selection table calling process 72 registers the valid / invalid information of the drive mode in the function selection data storage 73 (step S52). In C6 of FIG. 7, a variable w_variability corresponding to the function selection data storage 73 is described. In this step S52, variable w_variability valid / invalid information is registered. When the example of FIG. 7 is followed, the function selection data storage 73 stores information indicating that the automatic tracking mode is “invalid”, the program tracking mode is “valid”, the manual mode is “valid”, and the position mode is “invalid”. be registered.

  Returning to the description of FIG. 3, in the process of step S <b> 3 (post-program initialization process), first, the process of each drive mode is executed (step S <b> 6), and then the drive registered in the extension point 77 of the common unit 7. A transition process of the mode (the drive mode registered in step S4 above) is executed (step S7). When the process of step S7 ends, step S6 is executed again. That is, the processes in steps S6 and S7 are repeated.

  Details of step S6 will be described with reference to the flowchart of FIG. 8 and the source code example of FIG. The flowchart in FIG. 8 shows details of the process executed in step S6.

  In step S6, first, each drive mode 71 of the common unit 7 refers to the function selection data storage 73 via the function selection table access I / F 74 (step S61). C8 in FIG. 9 shows function getVariability of the function selection table access I / F. This function getVariability returns the address of the variable w_variability stored in the function selection data storage 73 (C6 in FIG. 7). Next, it is determined whether the drive mode is valid / invalid (step S62). If it is “valid” (step S62: Yes), a drive mode process is executed (step S63). If it is “invalid”, the process is terminated (step S62: No). These steps S61 to S63 correspond to the if statement of the valid / invalid process shown in C9 of FIG. 9, and determine whether the drive mode is valid or invalid. If the result of determination is that it is valid, processing in the drive mode is executed. In the illustrated source code example, the program tracking mode and the manual mode are effective (see C5 in FIG. 7), and the processing of these drive modes is executed.

  Next, details of step S7 will be described with reference to the flowchart of FIG. 10 and the source code example of FIG. Note that the flowchart of FIG. 10 shows details of the processing executed in step S7.

  In step S7, first, the extension process 76 of the common unit 7 calls the address of the drive mode transition process 81 registered in the extension point 77 in step S43 (step S71), and then via the called address. Then, the drive mode transition process 81 is executed (step S72). In these steps S71 and S72, drive_mode_hooks.init, drive_mode_hooks.pre, and drive_mode_hooks.post registered by executing the construction process shown in C4 of FIG. 11 are called in the extension process shown in C10 and registered in the extension point. The executed functions init_drive_mode_hook_impl, pre_drive_mode_hook_impl, and post_drive_mode_hook_impl are executed.

  FIG. 12 is a diagram illustrating a configuration at the time of executing the driving process, and illustrates a configuration example when the driving process is executed according to the above-described source code. In this example, the program tracking mode 71b and the manual mode 71c are executed, and the drive mode transition process 81 is called and executed by the extension process 76.

  As described above, in the tracking antenna control device of the present embodiment, the configuration of the drive mode control program is made common to the common part that is invariant regardless of the model, that is, the drive mode program having a similar program structure, Blocks that are commonly used by all models in the product line related to the tracking antenna, and specific parts for realizing functions specific to the model, that is, driving that is the operation of a specific model in the product line related to the tracking antenna A block that has a mode transition process and can customize the drive mode transition process by adding a unique part, and multiple drive modes (all models that have a fixed program and can be mounted regardless of the model installed) A plurality of drive modes that can be selectively mounted in the setting unit for setting valid / invalid, ie, tracking Enables / disables the drive mode there are a plurality of each model within the product sequence for container, and the configuration and a block selectable drive modes required for each model. Thus, a single common module can be reused in all models. In addition, in the case of changing the transition condition, which is a logic change that is less frequent, it can be dealt with by adding a process to the specific part. Also, the available drive mode types that are likely to show differences between models can be applied to specific models only by data setting.

  From the above, according to the tracking antenna control apparatus of the present embodiment, more parts of the control program in a plurality of types of devices equipped with the tracking antenna are shared, and functions can be added or changed to the control program. It becomes easy and the effect that the development efficiency at the time of multi-model deployment can be improved is acquired.

  As described above, the present invention is useful as a tracking antenna control apparatus that contributes to improving the development efficiency of various devices including a tracking antenna.

1 Tracking antenna control device 2 CPU
3 File system 4 RAM
5 Control program 6 Data 7, 12 Common part 8, 13 Specific part 9, 14 Setting part 10 Function selection table 11 Construction list 71 Drive mode 71a Automatic tracking mode 71b Program tracking mode 71c Manual mode 71d Position mode 72 Function selection table calling process 73 Function selection table data storage 74 Function selection table access I / F
75 Construction list call processing 76 Extension processing 77 Extension point 81 Drive mode transition processing 82 Construction processing

Claims (6)

Tracking antenna control device for controlling the tracking antenna by selecting one or more driving modes from among a plurality of common driving modes as a driving mode that is a driving function of the tracking antenna. Because
A control program for the tracking antenna
A common part consisting of a code common to all models regardless of the type of device equipped with a tracking antenna, and
Among the devices equipped with the tracking antenna, a unique part consisting of a code that realizes a drive mode transition process unique to a specific type of device,
And comprising
A setting unit that holds a result of selecting one or more drive modes from among the plurality of types of drive modes as information to be referred to by the specific unit when the control program is executed,
A tracking antenna control device comprising:   The plurality of types of drive modes include an automatic tracking mode for autonomously tracking a tracking target, and setting information for valid / invalid of the automatic tracking mode is held in the setting unit. Tracking antenna control device.   The plurality of types of drive modes include a program tracking mode in which a tracking antenna is operated according to a pre-programmed trajectory, and setting information for valid / invalid of the program tracking mode is held in the setting unit. Item 5. The tracking antenna control device according to Item 1.   The plurality of types of drive modes include a manual mode in which an antenna shaft is operated in accordance with a human operation, and setting information for valid / invalid of the manual mode is held in the setting unit. Tracking antenna control device.   The plurality of types of drive modes include a position mode in which an antenna is directed in a specified specific direction, and setting information for valid / invalid of the position mode is held in the setting unit. Tracking antenna control device.   The tracking antenna control device according to claim 1, wherein the unique unit and the setting unit exist for each of a plurality of types of devices including a tracking antenna.

Images