AUTOSAR software component function interface development method based on Simulink in Matlab
By setting and matching ClientServer Interface and ClientPorts in Simulink in Matlab, the problem of excessive number of ports and functions in AUTOSAR system is solved, improving work efficiency and development convenience.
Patent Information
- Application Number
- CN202210451111.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-26
- Publication Date
- 2025-01-10
- Estimated Expiration
- 2042-04-26
AI Technical Summary
In the "bottom-up" workflow of the AUTOSAR system, when establishing the application layer SWC software components based on the Simulink model, multiple ports and functions need to be constructed, resulting in increased workload, low work efficiency, and inconvenient IO function port connection in later IO function .
By using Simulink in Matlab, set the relevant parameters of the Function Caller function of all the same type of IO input ports in the controller application layer and match it with the ClientServer Interface, establish the ClientServer Interface and ClientPorts receiving ports, and confirm that the IO functions and ClientServer in Simulink are both the same parameters and match it. Interface matches ServicePorts correspondingly, reducing the number of ports and functions.
It realizes the reduction of the number of ports and functions, reduces the workload, improves work efficiency, simplifies the connection of later IO function ports, and improves the efficiency and convenience of AUTOSAR development.
Smart Images
Figure CN115202632B_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of software component function interface development, and in particular, relates to an AUTOSAR software component function interface development method, device, electronic device and computer-readable storage medium based on Simulink in Matlab. Background Art
[0002] In the "bottom-up" workflow of the AUTOSAR system solution, it is necessary to establish the application layer SWC software component based on the existing Simulink model and configure the generated code and arxml description file. The ports and interfaces of the SWC software component need to be constructed, and each input and output signal must correspond to a port.
[0003] like Figure 1 As shown, in the prior art, the IO signal input and output in Simulink requires the establishment of multiple functions and ports, which increases the workload, reduces the work efficiency, and is inconvenient for the subsequent IO function port connection.
[0004] Therefore, how to reduce the number of ports and functions, reduce workload, and improve work efficiency is a technical problem that technical personnel in this field urgently need to solve. Summary of the invention
[0005] The embodiments of the present application provide a method, device, electronic device and computer-readable storage medium for developing an AUTOSAR software component function interface based on Simulink in Matlab, which can reduce the number of ports and functions, reduce workload and improve work efficiency.
[0006] In a first aspect, an embodiment of the present application provides an AUTOSAR software component function interface development method based on Simulink in Matlab, comprising:
[0007] Set the relevant parameters of the Function Caller function of all the same type of IO input ports in the controller application layer to be the same, and match them with the ClientServer Interface;
[0008] In the AUTOSAR configuration interface of Simulink, create a ClientServer Interface and a ClientPorts receiving port of the software component. The ClientServer Interface matches the ClientServer Interface used by the AUTOSAR service port, and the server interface implementation corresponds to the relevant parameters of the Function Caller function.
[0009] In the Function Caller configuration interface of Code Mappings-AUTOSAR of Simulink, confirm that the IO function and ClientServer Interface, ClientPorts receiving port and ServicePorts service port in Simulink correspond to each other.
[0010] Furthermore, the method further comprises:
[0011] In Simulink, input the constant module into the Function Caller module input port of IO;
[0012] Enter the channel number of the corresponding IO in the constant module.
[0013] Furthermore, the relevant parameters of the Function Caller function of all the same type of IO ports in the controller application layer are set to be the same and matched with the ClientServer Interface, including:
[0014] Set the function name, input parameter, output parameter, input parameter data type, and output parameter data type of the Function Caller function of all the same type of IO input ports in the controller application layer to be the same, and match them with the ClientServer Interface.
[0015] Furthermore, the name of the ClientServer Interface is the same as the name of the Function Caller function, and the input and output parameters of the ClientServer Interface correspond to the input and output parameters of the function.
[0016] In a second aspect, the embodiment of the present application provides an AUTOSAR software component function interface development device based on Simulink in Matlab, comprising:
[0017] The parameter setting module is used to set the relevant parameters of the FunctionCaller function of all the same type of IO input ports in the controller application layer to be the same, and match them with the ClientServer Interface;
[0018] The port establishment module is used to establish a ClientServerInterface and a ClientPorts receiving port of the software component in the AUTOSAR configuration interface of Simulink, where the ClientServer Interface matches the ClientServer Interface used by the AUTOSAR service port, and the server interface implementation corresponds to the relevant parameters of the Function Caller function;
[0019] The confirmation module is used to confirm the matching of IO functions and ClientServer Interface, ClientPorts receiving ports and ServicePorts service ports in Simulink in the Function Caller configuration interface of Code Mappings-AUTOSAR of Simulink.
[0020] Furthermore, the device also includes:
[0021] The input module is used to input the constant module at the input end of the Function Caller module of the IO in Simulink; the channel number of the corresponding IO is entered in the constant module.
[0022] Furthermore, the parameter setting module is used to set the function name, input parameter, output parameter, input parameter data type, and output parameter data type of the Function Caller function of all the same type of IO input ports in the controller application layer to be the same, and match them with the ClientServer Interface.
[0023] Furthermore, the name of the ClientServer Interface is the same as the name of the Function Caller function, and the input and output parameters of the ClientServer Interface correspond to the input and output parameters of the function.
[0024] In a third aspect, an embodiment of the present application provides an electronic device, the electronic device comprising:
[0025] a processor and a memory storing computer program instructions;
[0026] When the processor executes the computer program instructions, the AUTOSAR software component function interface development method based on Simulink in Matlab as shown in the first aspect is implemented.
[0027] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the AUTOSAR software component function interface development method based on Simulink in Matlab as shown in the first aspect is implemented.
[0028] The AUTOSAR software component function interface development method, device, electronic device and computer-readable storage medium based on Simulink in Matlab in the embodiments of the present application can reduce the number of ports and functions, reduce workload and improve work efficiency.
[0029] The AUTOSAR software component function interface development method based on Simulink in Matlab includes: setting the relevant parameters of the Function Caller function of all the same type of IO input ports in the controller application layer to be the same, and matching them with the ClientServer Interface; establishing a ClientServer Interface and a ClientPorts receiving port of the software component in the AUTOSAR configuration interface of Simulink, wherein the ClientServerInterface matches the ClientServer Interface used by the service port of AUTOSAR, and the server interface implementation corresponds to the relevant parameters of the Function Caller function; in the Function Caller configuration interface of Code Mappings-AUTOSAR of Simulink, confirming that the IO function in Simulink matches the ClientServer Interface, and the ClientPorts receiving port matches the ServicePorts service port, so that the number of ports and functions can be reduced, the workload can be reduced, and the work efficiency can be improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0030] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0031] Figure 1 It is a schematic diagram of IO signal input in Simulink in the prior art;
[0032] Figure 2It is a flowchart of an AUTOSAR software component function interface development method based on Simulink in Matlab provided by an embodiment of the present application;
[0033] Figure 3 This is a schematic diagram of IO signal input in Simulink provided by an embodiment of the present application;
[0034] Figure 4 It is a flowchart of an AUTOSAR software component function interface development method based on Simulink in Matlab provided by an embodiment of the present application;
[0035] Figure 5 It is a structural schematic diagram of an AUTOSAR software component function interface development device based on Simulink in Matlab provided by an embodiment of the present application;
[0036] Figure 6 It is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION
[0037] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.
[0038] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "include..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0039] In the "bottom-up" workflow of the AUTOSAR system solution, it is necessary to establish the application layer SWC software component based on the existing Simulink model and configure the generated code and arxml description file. The ports and interfaces of the SWC software component need to be constructed, and each input signal needs to correspond to a port.
[0040] like Figure 1 As shown, in the prior art, the IO signal input in Simulink requires the establishment of multiple functions and ports, which increases the workload, reduces the work efficiency, and is inconvenient for the subsequent IO function port connection.
[0041] In order to solve the problems of the prior art, the embodiments of the present application provide a method, device, electronic device and computer-readable storage medium for developing an AUTOSAR software component function interface based on Simulink in Matlab. The following first introduces the method for developing an AUTOSAR software component function interface based on Simulink in Matlab provided by the embodiments of the present application.
[0042] Figure 2 The flowchart of the method for developing the AUTOSAR software component function interface based on Simulink in Matlab provided by one embodiment of the present application is shown. Figure 2 As shown, the AUTOSAR software component function interface development method based on Simulink in Matlab includes:
[0043] S201, setting the relevant parameters of the Function Caller function of all the same type of IO input ports in the controller application layer to be the same, and matching them with the ClientServer Interface;
[0044] In one embodiment, the relevant parameters of the Function Caller function of all the same type of IO ports in the controller application layer are set to be the same and matched with the ClientServer Interface, including:
[0045] Set the function name, input parameter, output parameter, input parameter data type, and output parameter data type of the Function Caller function of all the same type of IO input ports in the controller application layer to be the same, and match them with the ClientServer Interface.
[0046] S202, establishing a ClientServer Interface and a ClientPorts receiving port of the software component in the AUTOSAR configuration interface of Simulink, wherein the ClientServer Interface matches the ClientServer Interface used by the AUTOSAR service port, and the server interface implementation corresponds to the corresponding parameters of the Function Caller function;
[0047] In one embodiment, the name of the ClientServer Interface is the same as the name of the Function Caller function, and the input and output parameters of the ClientServer Interface correspond to the input and output parameters of the function.
[0048] S203. In the Function Caller configuration interface of Code Mappings-AUTOSAR of Simulink, confirm that the IO function and ClientServer Interface, ClientPorts receiving port and ServicePorts service port in Simulink correspond to each other.
[0049] In one embodiment, the method further includes: inputting a constant module at the input end of the Function Caller module of the IO in Simulink; and inputting a channel number of the corresponding IO in the constant module.
[0050] The AUTOSAR software component function interface development method based on Simulink in Matlab includes: setting the relevant parameters of the Function Caller function of all the same type of IO input ports in the controller application layer to be the same, and matching them with the ClientServer Interface; establishing a ClientServer Interface and a ClientPorts receiving port of the software component in the AUTOSAR configuration interface of Simulink, wherein the ClientServerInterface matches the ClientServer Interface used by the service port of AUTOSAR, and the server interface implementation corresponds to the relevant parameters of the Function Caller function; in the Function Caller configuration interface of Code Mappings-AUTOSAR of Simulink, confirming that the IO function in Simulink matches the ClientServer Interface, and the ClientPorts receiving port matches the ServicePorts service port, so that the number of ports and functions can be reduced, the workload can be reduced, and the work efficiency can be improved.
[0051] In order to explain the above method in detail, a specific embodiment is described below.
[0052] In order to reduce the number of ports and functions, reduce workload, improve work efficiency, and facilitate the subsequent IO function port connection, this embodiment can construct a client-server interface (ClientServerInterface, C / S) corresponding to a receiving port for all IO input signals, simplify the number of ports and unify IO input and receiving client functions for easy use.
[0053] The technical means of this embodiment include: AUTOSAR SWC software component C / S port establishment technology in Simulink and Simulink technology. The technical solution is: using AUTOSAR SWC software component C / S port establishment technology in Simulink and Simulink technology to implement the C / S port establishment of the controller application layer software SWC.
[0054] like Figure 3 As shown, this embodiment only needs to establish an IO Function Caller function, which reduces the number of AUTOSAR ClientServer interfaces and the workload; reduces the number of AUTOSAR ClientServer ports; reduces the corresponding work of IO functions and ClientPorts receiving ports in Simulink; and facilitates the subsequent IO function port connection.
[0055] like Figure 4 As shown, the AUTOSAR software component function interface development method based on Simulink in Matlab includes the following steps:
[0056] (1) Name the function caller functions of all the same type of IO ports in the controller application layer the same, with the same input parameters, output parameters, and data types of the input and output parameters. Reduce the number of functions and use one function to represent them uniformly.
[0057] (2) In the AUTOSAR configuration interface of Simulink, you only need to create a ClientServer Interface, and then create an Operation in the ClientServer Interface. The name of the Operation must correspond to the name of the FunctionCaller function, and the input and output parameters of the Operation must correspond to the input and output parameters of the function. This reduces the number of AUTOSAR ClientServer interfaces and reduces the workload.
[0058] (3) The receiving port of the software component ClientPorts established in the AUTOSAR configuration interface of Simulink should match the ClientServer Interface. Reduce the number of AUTOSAR ClientServer ports.
[0059] (4) In the Function Caller configuration interface of Code Mappings-AUTOSAR in Simulink, confirm that the IO function in Simulink matches the ClientServer Interface. This reduces the matching work between the IO function in Simulink and the ClientServer Interface receiving interface.
[0060] (5) Input the constant module into the input terminal of the Function Caller module of the IO in Simulink, and input the channel number of the corresponding IO into the constant module. This makes it easier for the function to call the channel number and output the IO signal of the channel.
[0061] This embodiment has the following beneficial effects: by compiling the AUTOSAR tool to generate code, a ClientServer function is generated, and the ClientServer function is implemented in the function, which can be called by other modules; the workload of AUTOSAR development is reduced, work efficiency is improved, and work content is simplified; by unifying the IO receiving client functions of the same type, the number of ports is reduced, and the purpose of ease of use is achieved; the work efficiency of AUTOSAR development is improved; and the labor cost of software development is reduced.
[0062] Figure 5 The schematic diagram of the structure of the AUTOSAR software component function interface development device based on Simulink in Matlab provided by the embodiment of the present application is shown. Figure 5 As shown, the AUTOSAR software component function interface development device based on Simulink in Matlab includes:
[0063] The parameter setting module 501 is used to set the relevant parameters of the Function Caller function of all the same type of IO input ports in the controller application layer to be the same, and to match them with the ClientServer Interface;
[0064] The port establishment module 502 is used to establish a ClientServer Interface and a ClientPorts receiving port of the software component in the AUTOSAR configuration interface of Simulink, wherein the ClientServerInterface matches the ClientServer Interface used by the service port of AUTOSAR, and the server interface implementation corresponds to the relevant parameters of the Function Caller function;
[0065] The confirmation module 503 is used to confirm the correspondence between the IO function and the ClientServer Interface, the ClientPorts receiving port and the ServicePorts service port in Simulink in the Function Caller configuration interface of Code Mappings-AUTOSAR of Simulink.
[0066] Furthermore, the device also includes:
[0067] The input module is used to input the constant module at the input end of the Function Caller module of the IO in Simulink; the channel number of the corresponding IO is entered in the constant module.
[0068] Furthermore, the parameter setting module 501 is used to set the function name, input parameter, output parameter, input parameter data type and output parameter data type of the Function Caller function of all the same type of IO input ports in the controller application layer to be the same, and match them with the ClientServer Interface.
[0069] Furthermore, the name of the ClientServer Interface is the same as the name of the Function Caller function, and the input and output parameters of the ClientServer Interface correspond to the input and output parameters of the function.
[0070] Figure 5 Each module / unit in the device shown has the function of realizing Figure 2 The functions of each step in the process can achieve the corresponding technical effects, which will not be described in detail here for the sake of brevity.
[0071] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application is shown.
[0072] The electronic device may include a processor 601 and a memory 602 storing computer program instructions.
[0073] Specifically, the processor 601 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
[0074] The memory 602 may include a large capacity memory for data or instructions. By way of example and not limitation, the memory 602 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, the memory 602 may include a removable or non-removable (or fixed) medium. In appropriate cases, the memory 602 may be inside or outside the electronic device. In a particular embodiment, the memory 602 may be a non-volatile solid-state memory.
[0075] In one embodiment, the memory 602 may be a read-only memory (ROM). In one embodiment, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or a flash memory, or a combination of two or more of these.
[0076] The processor 601 reads and executes the computer program instructions stored in the memory 602 to implement any one of the AUTOSAR software component function interface development methods based on Simulink in Matlab in the above embodiments.
[0077] In one example, the electronic device may further include a communication interface 603 and a bus 610. Figure 6 As shown, the processor 601, the memory 602, and the communication interface 603 are connected via a bus 610 and communicate with each other.
[0078] The communication interface 603 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.
[0079] Bus 610 includes hardware, software or both, and the parts of electronic equipment are coupled to each other. For example, but not limitation, bus may include accelerated graphics port (AGP) or other graphics bus, enhanced industrial standard architecture (EISA) bus, front side bus (FSB), hypertransport (HT) interconnection, industrial standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In appropriate cases, bus 610 may include one or more buses. Although the present application embodiment describes and shows a specific bus, the application considers any suitable bus or interconnection.
[0080] In addition, in combination with the AUTOSAR software component function interface development method based on Simulink in Matlab in the above embodiment, the embodiment of the present application can provide a computer-readable storage medium for implementation. The computer-readable storage medium stores computer program instructions; when the computer program instructions are executed by the processor, any one of the AUTOSAR software component function interface development methods based on Simulink in Matlab in the above embodiment is implemented.
[0081] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.
[0082] The functional modules shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. Programs or code segments can be stored in machine-readable media, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable media" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.
[0083] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.
[0084] The above reference is according to the method of the embodiment of the present application, the flow chart of the device (system) and the computer program product and / or the block diagram described various aspects of the present application.It should be understood that each square box in the flow chart and / or the block diagram and the combination of each square box in the flow chart and / or the block diagram can be realized by computer program instructions.These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the realization of the function / action specified in one or more square boxes of the flow chart and / or the block diagram.Such a processor can be but is not limited to a general-purpose processor, a special-purpose processor, a special application processor or a field programmable logic circuit.It can also be understood that each square box in the block diagram and / or the flow chart and the combination of the square boxes in the block diagram and / or the flow chart can also be realized by the dedicated hardware that performs the specified function or action, or can be realized by the combination of dedicated hardware and computer instructions.
[0085] The above is only a specific implementation of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.
Claims
1. A method for developing AUTOSAR software component function interface based on Simulink in Matlab, characterized in that: include: Set the relevant parameters of the Function Caller function of all the same type of IO input ports in the controller application layer to be the same, and match them with the ClientServer Interface, wherein the name of the ClientServer Interface is the same as the name of the Function Caller function, and the input and output parameters of the ClientServer Interface correspond to the input and output parameters of the Function Caller function; In the AUTOSAR configuration interface of Simulink, a ClientServer Interface and a ClientPorts receiving port of the software component are respectively established, wherein the established ClientServer Interface matches the ClientServer Interface used by the AUTOSAR service port, and the server interface implementation corresponds to the relevant parameters of the Function Caller function; the established ClientPorts receiving port corresponds to the established ClientServer Interface; In the Function Caller configuration interface of Code Mappings-AUTOSAR of Simulink, confirm that the IO function in Simulink matches the ClientServer Interface established in the AUTOSAR configuration interface of Simulink, and that the ClientPorts receiving port matches the ServicePorts service port.
2. The AUTOSAR software component function interface development method based on Simulink in Matlab according to claim 1, characterized in that: The method further comprises: In Simulink, input the constant module into the Function Caller module input port of IO; Enter the channel number of the corresponding IO in the constant module.
3. The AUTOSAR software component function interface development method based on Simulink in Matlab according to claim 1, characterized in that: Set the relevant parameters of the Function Caller function of all the same type of IO ports in the controller application layer to be the same, and match them with the ClientServer Interface, including: The function name, input parameter, output parameter, input parameter data type and output parameter data type of the Function Caller function of all the same type of IO input ports in the controller application layer are set to be the same and matched with the ClientServer Interface.
4. A device for developing AUTOSAR software component function interface based on Simulink in Matlab, characterized in that: include: A parameter setting module, used to set the relevant parameters of the FunctionCaller function of all the same type of IO input ports in the controller application layer to be the same, and to match them with the ClientServer Interface, wherein the name of the ClientServer Interface is the same as the name of the Function Caller function, and the input and output parameters of the ClientServer Interface correspond to the input and output parameters of the Function Caller function; A port establishment module is used to establish a ClientServerInterface and a ClientPorts receiving port of the software component in the AUTOSAR configuration interface of Simulink, respectively, wherein the established ClientServerInterface matches the ClientServer Interface used by the service port of AUTOSAR, and the server interface implementation corresponds to the relevant parameters of the Function Caller function; the established ClientPorts receiving port corresponds to the established ClientServer Interface; The confirmation module is used to confirm that the IO function in Simulink corresponds to the ClientServerInterface established in the AUTOSAR configuration interface of Simulink in the Function Caller configuration interface of Code Mappings-AUTOSAR of Simulink, and that the ClientPorts receiving port corresponds to the ServicePorts service port.
5. The AUTOSAR software component function interface development device based on Simulink in Matlab according to claim 4, characterized in that: The device also includes: The input module is used to input a constant module at the input end of the Function Caller module of the IO in Simulink; and input the channel number of the corresponding IO in the constant module.
6. The AUTOSAR software component function interface development device based on Simulink in Matlab according to claim 4, characterized in that: The parameter setting module is used to set the function name, input parameter, output parameter, input parameter data type and output parameter data type of the Function Caller function of all the same type of IO input ports in the controller application layer to be the same, and match them with the ClientServer Interface.
7. An electronic device, characterized in that: The electronic device comprises: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the AUTOSAR software component function interface development method based on Simulink in Matlab as described in any one of claims 1 to 3 is implemented.
8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the method for developing an AUTOSAR software component function interface based on Simulink in Matlab as described in any one of claims 1 to 3 is implemented.