Connectivity for online replaceable units

Abstract

A replaceable, stand-alone device configured for installation in a docking station comprising: - at least one first operational connector configured for connection to a second operational connector of said docking station for the purpose of exchanging operational data during the nominal operation of said device, - at least one first detection connector configured for connection to a second detection connector of said docking station for the purpose of exchanging detection data before the nominal operation of said device, - at least one first detection module coupled to said first detection connector configured to determine, from detection data exchanged with a second detection module of said station via said first and second detection connectors, an installation position of said device in said station. (No abbreviation figure)

Description

Title of the invention: Connectors for online replaceable units technical field

[0001] The present invention relates to line-replaceable or "on-the-go" units in modular architectures. In the aeronautical field, these units are designated as "Line Replacement Units" (LRUs) in Anglo-Saxon terminology. It relates more particularly to their method of installation in their operational locations.

[0002] The invention has applications in all fields using electronic system architectures interconnecting modules that can be individually and independently replaced, for example for reasons of maintenance, failure or otherwise. Technological background

[0003] In the aeronautical field, LRUs are modular components designed to be replaced in the field (for example, during a stopover while an aircraft is in transit at an airport) without requiring significant modification to the aircraft. Their replacement falls under the category of aircraft maintenance. Their modular design reduces downtime. The modularity of LRUs allows for on-demand and partial replacement. This results in simpler and less expensive maintenance.

[0004] LRUs can include various types of components such as sensors, actuators, computers, avionics modules, communication systems, etc.

[0005] When a fault is detected in a system, the defective LRU can be identified and replaced on-site without needing to return the entire aircraft to a maintenance center. The replacement can be carried out at the airport where the fault is detected, provided the correct replacement LRU is available. This allows for more efficient maintenance management, reducing costs and minimizing aircraft downtime.

[0006] Several advantages are associated with the use of LRUs, particularly in aeronautics. LRUs are designed to be self-contained and interchangeable components. In the event of a failure or the need for an upgrade, technicians can replace a specific LRU rather than having to dismantle an entire system. This modularity simplifies maintenance and reduces the costs associated with component replacement. The modular design also allows for faster problem diagnosis. When a failure occurs, integrated sensors and diagnostic systems can identify the LRU responsible for the failure. This allows the Maintenance teams can directly target the faulty component without having to perform complex system-wide testing. The ability to quickly replace a Long Range Unit (LRU) in the field significantly reduces aircraft downtime. Rather than having to return the aircraft to a maintenance center, where the repair procedure could take considerably longer, technicians can perform the replacement on-site. This is particularly crucial in commercial aviation, where aircraft operational availability is critical. LRUs also facilitate preventive and corrective maintenance management. Maintenance teams can schedule regular LRU replacements to prevent unplanned failures, and when a failure does occur, they can quickly isolate and replace the faulty component. Finally, LRUs facilitate the integration of new technologies.Advances in avionics systems, sensors, or other components can be implemented simply by replacing the outdated LRU with an updated version.

[0007] In summary, LRUs play a crucial role in the efficient management of aircraft maintenance, enabling rapid repair, accurate diagnosis and technological scalability while minimizing downtime.

[0008] This role can only be fulfilled if the LRUs are correctly installed in their intended location within the system. This is important to ensure that the LRUs are not damaged due to incorrect installation and to guarantee the system's safe operation. Furthermore, for certain types of equipment that can be automatically configured based on their installation location, detection of the installation location is necessary to perform this automatic configuration.

[0009] Several techniques exist to ensure the correct connection of an LRU to its intended location and to avoid any replacement error.

[0010] The first technique lies in the use of mechanical anti-missing devices.

[0011] According to this technique, the connectors of each LRU have a unique arrangement corresponding exactly to that of the corresponding connector of the docking system. Figure 1 illustrates an LRU 100 having two connectors 101, 102. Each of these connectors is a multi-pin connector. Thus, each connector has pins 103 (A, B, C, D, ..., V). Each connector is intended to be mated with a corresponding connector 106 of a docking station (not shown). For example, the pins of connector 102 are female pins and the pins 105 of connector 106 are male pins. In a correct connection, the pins (A, B, C, D, ..., V) of connector 106 must fit into the pins of connector 102. For example, to ensure this correct insertion, a keying feature 107 A keying feature 104 is located on connector 102, and a corresponding keying feature 104 is located on connector 106. In a correct connection, the keying feature 104 is a tab that can be inserted into the keying feature 107, which consists of a corresponding slot. The fact that the positions of the keying features 104 and 107 are the same (here in the 12 o'clock position) ensures that in case (a), the connection is correct. However, in case (b), the keying feature 104 is in a different position (here in the 3 o'clock position), which does not correspond to that of the keying feature 107 (which remains in the 12 o'clock position). Therefore, the pins cannot be inserted correctly. Another embodiment is shown in case (c), in which, instead of the keying features 107 and 104, the female pins of the connector are closed (N, P, S, T, V).In this case, unless the corresponding male pins of connector 106 are removed, the connection is not possible because these pins (N, P, S, T, V) will interfere with connector 102 and prevent a proper connection. This design allows the keying feature to be integrated into the connector itself using the pins.

[0012] This technique, however, suffers from numerous drawbacks. In particular, this type of connector is subject to mechanical wear. Furthermore, in the event of very poor handling, the keying notches can be forced, still allowing installation with an incorrect connection that may not be detected in time. In addition, this type of technique offers a limited number of configurations, whether in terms of the position of the keying notches or the possible combinations for closed or open pins. Finally, this type of connection requires that all possible LRUs for a given system be available at each maintenance location in order to perform a replacement for each keying notch configuration. This technique therefore suffers from several disadvantages that make it impractical.

[0013] The second technique involves programming the connector pins.

[0014] According to this technique, certain pins of the docking station connector are assigned specific electrical characteristics (generally open or grounded). Once an LRU is connected, it checks these characteristics to compare them to the expected ones. In case of an unexpected installation, the LRU enters a safety state to prevent damage. Figure 2 illustrates an LRU 200 with two connectors 201, 202. Each of these connectors is a multi-pin connector. Thus, each connector has pins 203 (A, B, C, D, ..., V). Each connector is intended to be mated with a corresponding connector 206 of a docking station (not shown). For example, the pins of connector 202 are female pins and the pins 205 of connector 206 are male pins.According to this technique, certain pins 207 (F, G, H) of connectors 202, 206 are reserved for mating verification. Location verification can also enable automatic configuration. By. For example, certain specific functions (such as debugging) may be enabled in certain locations (flight tests, test benches), while the same functions will not be enabled during normal operation. A pin programming set (requiring a variable number of pins) typically includes control pins (usually one) whose function is to detect equipment failure on a set of pins (for example, a pin is bent / disconnected).

[0015] This technique, however, also suffers from numerous drawbacks. First, it requires allocating pins to this identification function, even though they could be used for operational purposes. Particularly in the aeronautical field, all resources are allocated optimally to save weight and energy consumption. Therefore, allocating pins to something other than data transport has a cost in terms of finding the optimal operational solution. Second, here too, the number of possible pin combinations for identification is limited, which makes this technique impractical when the number of LRUs in the system is high. Third, the error mode detection capability is limited.

[0016] There is therefore a need to improve the connectivity of LRUs in avionics systems.

[0017] The present invention falls within this framework. Summary of the invention

[0018] According to a first aspect, the invention relates to a replaceable, stopover device configured for installation in a docking station comprising:

[0019] - at least one first operational connector configured for connection to a second operational connector of said docking station for the purpose of exchanging operational data during the nominal operation of said device,

[0020] - at least one first sensing connector configured for connection to a second detection connector of said docking station for the purpose of exchanging detection data prior to nominal operation of said device,

[0021] - at least one first detection module coupled to said first connector of detection configured to determine, from detection data exchanged with a second detection module of said station, via said first and second detection connectors, an installation position of said device in said station.

[0022] For example, said first identification module is configured to self-configure said device according to said installation position of said device in said station.

[0023] For example, said self-configuration includes the activation of functionalities associated with said installation position of said device in said station.

[0024] According to embodiments, said identification module is configured to place said device in a fault state according to said installation position of said device in said station.

[0025] According to embodiments, said detection data exchanged with the second detection module (405) of said station includes an identification code allowing verification of the integrity of said device and / or of said docking station.

[0026] According to a second aspect, the invention relates to a docking station configured for the installation of at least one replaceable device during a stopover, comprising:

[0027] - at least one second operational connector configured for connection to a first operational connector of said at least one device for the purpose of exchanging operational data during the nominal operation of said device,

[0028] - at least one second sensing connector configured for connection to a first detection connector of said at least one device for the purpose of exchanging detection data prior to nominal operation of said device,

[0029] - at least one second detection module coupled to said second connector detection configured to exchange a set of detection data with a first detection module of said at least one device, via said first and second detection connectors, enabling the determination of an installation position of said device in said station.

[0030] For example, said detection data exchanged with the first detection module of said at least one device includes an identification code allowing verification of the integrity of said device and / or said docking station.

[0031] According to a third aspect, the invention relates to a system comprising a device according to the first aspect and a docking station according to the second aspect.

[0032] According to a fourth aspect, the invention relates to a method for connecting a replaceable device during a stopover in a docking station comprising:

[0033] - detect a connection between at least a first detection connector of said device and a second connector for detecting said docking station,

[0034] - exchange a set of detection data before nominal operation of said device between at least a first detection module (402) of said device coupled to said first detection connector and a second detection module of said station coupled to said second detection connector,

[0035] - determine an installation position for said device in said station, and

[0036] - to authorize, depending on said position, an exchange of operational data via at least one first operational connector of said device and a second operational connector of said docking station.

[0037] The method may further include a self-configuration step of said device according to said detection data set. Brief description of the figures

[0038] Other features and advantages of the invention will become apparent from the following detailed description, by way of non-limiting example, and the accompanying figures, among which:

[0039] [Fig-1] illustrates an LRU connection according to a first art technique prior,

[0040] [Fig.2] illustrates an LRU connection according to a second art technique prior,

[0041] [Fig.3] illustrates a context for implementing embodiments of the invention,

[0042] [Fig.4] illustrates an LRU connection according to embodiments,

[0043] [Fig.5] illustrates a method for connecting LRUs according to embodiments,

[0044] [Fig.6] illustrates a system architecture for implementing modes of realization. Detailed description of the invention

[0045] An implementation context for embodiments of the invention is first described with reference to [Fig. 3]. In the following examples, embodiments of connections between line-replaceable units (LRUs) or "on-the-ground" units in modular architectures are described. These LRUs (Line Replacement Units) 300, 301, 302 can take various forms such as sensors, actuators, computers, avionics modules, communication systems, etc. These LRUs are intended to be interconnected in a modular system by connection to a docking station 309 which has operational slots for each LRU A, B, C, etc. The docking station can be a simple interconnect bus or a cable harness but can also take a more complex form with specific docking electronics. To accommodate the LRUs, the docking station includes connectors 306, 307, 308.Each connector is located at a specific position A, B, C. These connectors are configured to mate with connectors 303, 304, 305 of LRUs 300, 301, 302 (respectively). For example, each position in the docking station is dedicated to a function within the overall system formed by the docking station and the LRUs. Thus, each location has dedicated connectors and electronics specific to that function, designed to cooperate with a corresponding LRU.

[0046] As explained below, in the described embodiments, it is not necessary to connect a specific module to a single location in the station. Here, each of the modules 300, 301, and 302 can be connected to any of the slots A, B, and C. Thus, each of the LRU connectors 303, 304, and 305 can be mated to each of the docking station connectors 306, 307, and 308. Therefore, it is not necessary to provide keying features on the connectors or to dedicate connection pins to a detection function.

[0047] Several advantages can be obtained in this way. In terms of design, it is no longer necessary to add elements dedicated to keying, whether mechanical or electrical. Since these keying devices are no longer needed, problems related to their wear do not arise. In terms of maintenance, it is no longer necessary for an operator to ensure that an LRU is connected in the correct location. In terms of logistics, it is no longer necessary to have all types of LRUs at the maintenance sites to deal with failures that may occur in LRUs connected to locations A, B, C, etc.

[0048] Indeed, embodiments of the invention allow for the detection of incorrect installation of an LRU in the wrong location within a docking station. Once the LRU is installed in the docking station, it can detect the installation location and determine whether this location is correct and allows for normal operation of the LRU. If an incorrect installation is detected, the LRU enters a safe mode to prevent damage. In other cases, embodiments allow for the self-configuration of an LRU based on its installation location. For example, a generic autopilot controller can automatically load the necessary commands when installed in the correct position.For example, when a controller is common to different versions of the same aircraft, it can, depending on the embodiment, select the parameters relevant to the aircraft in which it is installed (by detecting the version of the aircraft in question). It is also possible to consider disabling test-related functionalities when the LRU detects that it is connected to an operational aircraft station and not a test station.

[0049] These advantages are obtained with connection embodiments for LRUs as described with reference to [Fig. 4]. This figure illustrates an LRU 400 intended to be connected to a docking station 401. The LRU has one or more operational connectors 406, 408. These connectors of the LRU can cooperate with corresponding operational connectors 407, 409 of a location N of the docking station. The operational connectors allow data exchange between the LRU and the docking station during nominal operation of the LRU. In each LRU, a detection module 402 associated with a detection connector 403 is present. This detection connector of the LRU can be coupled to a detection connector 404 of one of the docking stations. The detection connector is coupled to A detection module 405 is located on the docking station. At each location (A, B, C, etc.) of the docking station, there is a data connection (connectors 407, 409) for the LRU's functionalities during normal operation, and a specific detection connection 404 for cooperation between the detection modules of the docking station and the LRU before normal operation. The cooperation between modules 402 and 405 makes it possible to identify the location where the LRU is installed and to take the necessary measures.

[0050] For example, the docking station's detection module 405 includes memory that stores information about the location of the associated connectors 407 and 409 in the docking station. This memory can also store functions associated with that location. It can also store an LRU configuration associated with that location. The detection module's memory can be reprogrammable. In some embodiments, it is EPROM (Erasable Programmable Read-Only Memory). It is also possible to provide embodiments with other types of memory (ROM, Flash, or other). In some embodiments, the docking station's detection module can also include a security code for verifying the conformity of the connected LRUs. This improves system security by ensuring the integrity of the LRUs located in the docking station.

[0051] For example, the detection module 402 allows the execution of computer code that reads the information contained in the detection module 405. The LRU detection module can thus determine the location where it is installed and trigger an LRU configuration to perform the associated functionalities. Therefore, it is possible to use LRUs that are self-configuring according to their location. Maintenance is simplified because the operator does not have to worry about the LRU being installed, as it will automatically determine the functionalities to be implemented. Logistics are also simplified since all LRUs are configured to operate according to each location. The cooperation between the detection modules 402 and 405 allows the functionality to be selected according to the location where the LRU is placed.

[0052] The operation of an LRU according to embodiments is described with reference to [Fig. 5]. Initially, an LRU is connected to a docking station. This involves coupling the connectors of the LRU with those of a docking slot on the station. The detection module then detects the connection during step 501. Communication is then established between the respective modules of the LRU and the docking station during step 502. During this step, a set of detection data is exchanged. For example, the LRU reads the data from the The docking station detection module stores data. The data read by the LRU detection module may include an identification of the docking location's position within the docking station, a function to be implemented by the LRU at that location, and a required LRU configuration at that location. During this exchange, identification data may also be exchanged and verified by both parties for security reasons. For example, the docking station may verify the integrity of the connected LRU using an identification code or other method. Conversely, the LRU may verify the integrity of the docking station using an identification code or other method. Once the data exchange has occurred in step 502, the LRU determines its installation position within the docking station in step 504.For example, whether the location to which it has been connected is valid for the operations it can perform. If the location is incorrect (NOK), the LRU enters a fault state during step 503. Otherwise (OK), it determines during step 505, based on data received from the docking station's detection module, whether autoconfiguration is necessary to perform the expected functions at the docking station location to which it has been connected. If no specific configuration is required, or if the LRU is already in the correct configuration, the LRU enters an operational state during step 507. In this operational state, the exchange of operational data between the LRU and the docking station via the operational connectors is permitted. Otherwise, it proceeds to an autoconfiguration step 506 before entering the operational state.During this self-configuration step, the detection module can, for example, activate functionalities associated with the installation position of the device in the station.

[0053] Figure 6 is a functional diagram of a 600 system for implementing one or more embodiments of the invention. The LRUs or docking stations described above may have the same structure.

[0054] The system 60 0 includes a communication bus to which are connected:

[0055] - a processing unit 60 1, such as a microprocessor, called CPU;

[0056] - a 60 2 MB random access memory unit, called RAM, for code storage executable of a process according to an embodiment of the invention as well as registers adapted to record the variables and parameters necessary for the implementation of a process according to embodiments, the memory capacity of which can be extended by an optional RAM connected to an expansion port for example;

[0057] - a 60 3 memory unit, called ROM, for storing programs computer systems designed to implement the embodiments of the invention;

[0058] - a network interface unit 60 4 connected to a communication network on which is the area where the digital data to be processed is transmitted or received. The network interface 60 4 can be a single network interface, or composed of a set of different network interfaces (for example, wired and wireless interfaces, or different types of wired or wireless interfaces). Data is written to the network interface for transmission or read from the network interface for reception under the control of the software application running in CPU 60 1;

[0059] - optionally, a 60 5 graphical user interface unit allowing to receive input from a user or to display information to a user;

[0060] - optionally, a 60 6-bit hard drive labeled HD

[0061] - an I / O module 60 7 for receiving / sending data from / to external systems such as a video source or a screen.

[0062] The executable code can be stored either in read-only memory 603, or on the hard disk 606, or on removable digital media such as a disk. According to one embodiment, the executable code of the programs can be received by means of a communication network, via the network interface 604, in order to be stored in one of the storage means of the communication system 600, such as the hard disk 606, before being executed.

[0063] The processing unit 60 1 is adapted to control and direct the execution of instructions or parts of software code of the program(s) according to the embodiments of the invention, these instructions being stored in one of the aforementioned storage means. After power-up, the processing unit 60 is capable of executing the instructions from the main RAM 60 2 relating to a software application after these instructions have been loaded from the ROM program 60 3 or the hard disk drive (HDD) 60 6, for example. Such a software application, when executed by the central processing unit 60 1, causes the execution of the steps of a method according to various incarnations.

[0064] The present invention has been described and illustrated in this detailed description with reference to the accompanying figures. However, the present invention is not limited to the embodiments shown. Other variations, embodiments, and combinations of features can be deduced and implemented by a person skilled in the art upon reading this description and the accompanying figures.

[0065] To satisfy specific needs, a person competent in the field of the invention may apply modifications or adaptations.

[0066] In the claims, the term “include” does not exclude other elements or steps. The various features presented and / or claimed may be advantageously combined. Their presence in the description or in different dependent claims does not preclude the possibility of combining them. The reference symbols shall not be construed as limiting the scope of the invention.

Claims

Demands

1. A replaceable station-based device (400) configured for installation in a docking station (401) comprising: - at least one first operational connector (406) configured for connection to a second operational connector (407) of said docking station for the purpose of exchanging operational data in nominal operation of said device, - at least one first detection connector (403) configured for connection to a second detection connector (404) of said docking station for the purpose of exchanging detection data before nominal operation of said device, - at least one first detection module (402) coupled to said first detection connector configured to determine, from detection data exchanged with a second detection module (405) of said station, via said first and second detection connectors, an installation position of said device in said station.

2. Device according to claim 1, wherein said first identification module is configured to self-configure said device according to said installation position of said device in said station.

3. Device according to the preceding claim, wherein said self-configuration includes the activation of functionalities associated with said installation position of said device in said station.

4. Device according to any one of the preceding claims, wherein said identification module is configured to place said device in a fault state depending on said installation position of said device in said station.

5. Device according to any one of the preceding claims, wherein said detection data exchanged with the second detection module (405) of said station include an identification code enabling verification of the integrity of said device and / or of said docking station.

6. Docking station (401) configured for the installation of at least one standby replaceable device (400) comprising: - at least one second operational connector (407) configured for connection to a first operational connector (407) of said at least one device for the purpose of exchanging operational data in nominal operation of said device, - at least one second detection connector (404) configured for connection to a first detection connector (403) of said at least one device for the purpose of exchanging detection data before nominal operation of said device, - at least one second detection module (405) coupled to said second detection connector configured to exchange a set of detection data with a first detection module (402) of said at least one device, via said first and second detection connectors, allowing the determination of an installation position of said device in said station.

7. Docking station according to the preceding claim, wherein said detection data exchanged with the first detection module (402) of said at least one device includes an identification code enabling verification of the integrity of said device and / or of said docking station.

8. System comprising: - at least one device according to one of claims 1 to 5, and - a docking station according to one of claims 6 to 7.

9. Method of connecting a replaceable stationary device (400) in a docking station (401) comprising: - detecting (501) a connection between at least a first detection connector (403) of said device and a second detection connector (404) of said docking station, - exchanging (502) a set of detection data prior to nominal operation of said device between at least a first detection module (402) of said device coupled to said first detection connector and a second detection module (405) of said station coupled to said second detection connector, - determining (504) an installation position of said device in said station, and - allowing (507), depending on said position, an exchange of operational data via at least a first operational connector (406) of said device and a second operational connector (407) of said docking station.

10. Method according to the preceding claim further comprising a step of self-configuration of said device according to said detection data set.

Images