VECTOR-MCC
The VECTOR-MCC (Mission Control Computer) is highly suitable for projects that require extensive I/O capabilities and/or custom payload management. It allows for the segregation of flight safety-critical and non-critical functionalities.
The VECTOR-MCC allows the correct segregation between stabilization, control, and mission management algorithms.
VECTOR-MCC hardware is qualified to MIL-STD-810F, MIL-STD 461F and ISO 9001:2015 standards.
The VECTOR-MCC has an open architecture (third-party FCC friendly) that enables the development of mission logic or payload control. It is completely separate from the core UAV control, thereby eliminating any risk to flight safety. This flexibility includes guidance commands to the autopilot in flight modes.
The MCC interface on VECTOR can be used to interface with third-party MCC systems and flight controllers as long as this hardware complies with the communication protocol. The company offers specialized training and support packages to simplify programming and ensure a smooth development experience.
Make your platform unique by creating your own functionalities. The VECTOR-MCC includes its own independent microprocessor that is different from the FCC, which ensures flight safety in case of failure in the MCC.
Expand the VECTOR autopilot connection capabilities with extra I/O ports for the most advanced configurations.
The VECTOR Mission Control Computer (VECTOR-MCC) is highly suitable for projects that require extensive I/O capabilities and/or custom payload management.
The VECTOR-MCC allows the correct segregation between logic related to stabilization and control and special payloads or mission management. This procedure facilitates the certification process.
In this example, the VECTOR autopilot provides a robust and reliable flight control solution, while the VECTOR-MCC is set up to manage the payloads. Both the Ground Control Station (GCS) and the VECTOR-MCC receive the complete telemetry stream reported by the VECTOR autopilot (FCC). Likewise, the VECTOR-MCC sends information from every external sensor that needs to be displayed in the GCS software back to the autopilot in bidirectional communication.
The VECTOR-MCC hardware is rigorously qualified to MIL-STD-810F and MIL-STD-461F standards, ensuring exceptional robustness and reliability for your most demanding applications and challenging missions.
The VECTOR-MCC enhances the already impressive I/O capabilities of the VECTOR autopilot, thereby allowing the user to increase even further the number of payloads that can be controlled on an advanced UAV. In this configuration, the mission is managed as usual by the UAV system operator via the GCS, which takes advantage of Visionair GCS software for pre-flight configuration, mission execution and post-flight analysis. The VECTOR-MCC can automatically manage the mission based on telemetry information received from the VECTOR and any devices or payloads connected.
The VECTOR-MCC provides the user flexibility to focus on adding value to the production process and developing their own drivers for payloads that are not critical to flight safety and without the risk of interfering with core UAV control.
The VECTOR-MCC software may be developed independently by the client. It also has its own audit. This allows the user to develop the code without the need to share sensitive information about payloads or missions with third-party FCC manufacturers.
Similarly, our VECTOR autopilot family is designed to seamlessly integrate with a wide range of third-party MCC systems, accommodating various hardware and architectures to offer clients the flexibility to select their preferred setup. For those utilizing our hardware, we provide comprehensive programming libraries and C/C++ code examples, as well as specialized training courses and support packages to streamline the programming process and ensure a smooth development experience.
The VECTOR-MCC provides the possibility of creating a segregated architecture that makes the certification process easier and helps to establish the different DAL levels in the architecture. This way, flight safety is ensured as the unit with FCC functionalities is isolated from payload features, reducing failure probability.
- Facilitates the certification process by segregating critical functions related to control and stabilization from the payload functions.
- Extends the VECTOR autopilot connection capabilities with extra I/O ports for the most advanced configurations. Even more connectivity options while maintaining the reliability and performance of the UAV Navigation-Grupo Oesía Flight Control System based on VECTOR and Visionair.
- Safety and flexibility to develop payload-related features that are completely separate from core UAV control, thereby eliminating any risk to flight safety.
- Maximum flight safety thanks to the VECTOR autopilot. Actuators and key sensors necessary for flight control are connected to the VECTOR.
- Differentiated from competitors by creating custom mission logic.
- Customizable telemetry representation by means of panels created using Visionair SDK.
- MIL-STD-810F, MIL-STD 461F and ISO 9001:2015 qualified hardware.
- VECTOR SDK and Visionair SDK availability for MCC programming* and Visionair customization.
- The use of the known UAV Navigation-Grupo Oesía tools (Breakout Board, Software update application…) to implement your own code.
- Correct behavior of critical subsystems, such as Transponders or Magnetometers. They are ensured as they are controlled by the VECTOR autopilot FCC.
*Customers will require the IAR Systems Embedded Workbench version 7.80 compiler to compile software using the VECTOR-MCC SDK. UAV Navigation-Grupo Oesía does not supply this, so please contact your local IAR Systems reseller. The newer IAR workbench version could be used, but they have not been evaluated.
|
COMPUTING CAPABILITY |
|
|
Mission Control CPUs |
2 CPUs: Twin CPUs system, based on the ARM Cortex A5 processor, achieving 536 MHz of clock speed. |
|
Memory |
|
|
Maximum Task Frequency
|
1000Hz |
|
I/O |
|
|
Total I/O Lines |
62 |
|
Servo or General Purpose I/O Lines |
24 (fully configurable), LVTTL: PWM, Discrete Input, Discrete Output, Pulse Counter (RPM), Simulated GPS PPS, Strobe Light Signal |
|
PWM Rate |
50Hz, 200Hz or 400Hz |
|
PWM Signal |
0.8ms to 2.2ms high, 1us steps |
|
CAN 2.0 A and B |
2 (up to 1Mbps) |
|
Serial Comm |
|
|
Ethernet |
100 Base Tx Channel according to IEEE 802.3 standard |
|
High-speed ADC lines |
8 ADC inputs with 12-bit resolution and up to 1 MHz conversion rate. All channels 0 to 3.3V conversion range |
|
ELECTRICAL |
|
|
Supply (unregulated) |
9V to 36V DC |
|
Power consumption |
2.5 W |
|
MECHANICAL / ENVIRONMENTAL |
|
|
Enclosure Material |
Grade 6082 Aluminium Alloy |
|
Environmental Qualification |
MIL-STD-810 |
|
EMI Qualification |
MIL-STD-461 |
|
Size (mm, H x W x L, box less connectors, width less mounting lugs) |
45.0 x 68.0 x 74.5 |
|
Weight |
160g |
|
Humidity |
Up to 90% RH, non-condensing |
|
Temperature Range |
-40ºC to +85ºC |
|
System Connector #1 |
25-pin GLENAIR MWDM2L-25PCBR-.110 |
|
System Connector #2 |
37-pin GLENAIR MWDM2L-37PCBR-.110 |
|
Auxiliary (serial) port |
|
|
Shock Survival |
500g 8ms 1/2 sine |
|
Mounting Screws |
4 x M4 |
|
ESD Compliant |
IEC 61.000-4-2-level 4 |
| VECTOR MCC Installation Kit |
- 37-Pin Connector Female (model: GLENAIR MWDM2L-37S-6E5-18).
- 25-Pin Connector Female (model: GLENAIR MWDM2L-25S-6E5-18).
- Binder M8 Wire P/N: 77-3406-0000-50006-0200.
The kit also includes programming libraries, examples, and templates in C/C++ code, providing references for better understanding and easier implementation.
In order to further explain VECTOR-MCC, this section will describe three different product setups. It is for the interactions between this mission control computer and the related systems needed for the operation.
MCC for Custom Payload Control
The VECTOR-MCC enhances the integration of a camera with camera-guided mode, allowing operators to fly the aircraft as if in First Person View (FPV), thereby increasing bullseye precision in certain applications.
This aligns with the philosophy of segregating critical tasks from non-critical ones, such as payload control. The MCC runs custom payload software developed by the customer, ensuring that it does not interfere with the Flight Control Computer (FCC) decisions. In this setup, the MCC can execute any algorithms or logic related to the desired payload for the mission, such as artificial intelligence (AI) applications.
MCC to Implement Own FC Laws
Through our VECTOR-MCC or a third-party MCC, always connected to our VECTOR-600 (FCC) system, clients can develop their own flight laws and control the servos directly via two flight modes.
The Mission Control Manual Command (MCM) allows clients to send position commands directly to the servo. The Mission Control Assisted Command (MCA) lets clients send desired attitude or body axes velocity commands from their MCC code to our VECTOR (FCC) autopilot, which translates this information to control the servos. MCM mode is ideal for moments requiring manual control. However, we believe that the FCC controlling the flight is safer and more efficient. MCM supports both fixed-wing (FW) and rotary-wing (RW) platforms and is capable of controlling up to five surfaces.
MCC Commanding FCC
In this third example, the main advantage of this configuration is the independence and freedom of the customer to develop their own software to command the autopilot.
The MCC is connected to the FCC and also to an external data link that communicates with a third-party ground control station. Any guidance command can be sent from the MCC to the FCC with this configuration. Furthermore, it can define no-fly zones, changes in the fly modes, and activation of other systems (FTS), etc.
Own MCC or MCC from Third-Parties
Our VECTOR autopilot family is designed to seamlessly integrate with third-party MCC systems, accommodating a variety of hardware and architectures to provide clients with the freedom to select their preferred system.
For those utilizing our MIL-STD-certified and field-proven hardware, we offer a comprehensive suite of programming libraries and C/C++ code examples to streamline functionality development. If opting for third-party software, clients can use different programming languages, such as MATLAB or others.
However, it is essential that command packages sent from the MCC to our FCC adhere to our proprietary TSIP communication protocol. To facilitate this, we provide an ICD (Interface Control Document) to ensure smooth integration and clear command interpretation by our VECTOR autopilot.
MCC Commanding HIL Simulator
In this fifth scenario, the VECTOR-MCC is connected to a Hardware-In-the-Loop (HIL) simulator, which is primarily used for testing new customer-developed applications. This setup enables on-ground testing, significantly reducing the costs and effort associated with flight testing. Our VECTOR-HIL simulator supports the connection, simulation, and testing of the system configuration—whether using our VECTOR-MCC or a third-party MCC—allowing for thorough code evaluation in a controlled operational environment. The documentation we provide includes a dedicated section to guide clients in setting up this testing scheme and ensuring safe, effective product validation.
The VECTOR Mission Control Computer (VECTOR-MCC) is highly suitable for projects that require extensive I/O capabilities and/or custom payload management.
The VECTOR-MCC allows the correct segregation between logic related to stabilization and control and special payloads or mission management. This procedure facilitates the certification process.
In this example, the VECTOR autopilot provides a robust and reliable flight control solution, while the VECTOR-MCC is set up to manage the payloads. Both the Ground Control Station (GCS) and the VECTOR-MCC receive the complete telemetry stream reported by the VECTOR autopilot (FCC). Likewise, the VECTOR-MCC sends information from every external sensor that needs to be displayed in the GCS software back to the autopilot in bidirectional communication.
The VECTOR-MCC hardware is rigorously qualified to MIL-STD-810F and MIL-STD-461F standards, ensuring exceptional robustness and reliability for your most demanding applications and challenging missions.
The VECTOR-MCC enhances the already impressive I/O capabilities of the VECTOR autopilot, thereby allowing the user to increase even further the number of payloads that can be controlled on an advanced UAV. In this configuration, the mission is managed as usual by the UAV system operator via the GCS, which takes advantage of Visionair GCS software for pre-flight configuration, mission execution and post-flight analysis. The VECTOR-MCC can automatically manage the mission based on telemetry information received from the VECTOR and any devices or payloads connected.
The VECTOR-MCC provides the user flexibility to focus on adding value to the production process and developing their own drivers for payloads that are not critical to flight safety and without the risk of interfering with core UAV control.
The VECTOR-MCC software may be developed independently by the client. It also has its own audit. This allows the user to develop the code without the need to share sensitive information about payloads or missions with third-party FCC manufacturers.
Similarly, our VECTOR autopilot family is designed to seamlessly integrate with a wide range of third-party MCC systems, accommodating various hardware and architectures to offer clients the flexibility to select their preferred setup. For those utilizing our hardware, we provide comprehensive programming libraries and C/C++ code examples, as well as specialized training courses and support packages to streamline the programming process and ensure a smooth development experience.
The VECTOR-MCC provides the possibility of creating a segregated architecture that makes the certification process easier and helps to establish the different DAL levels in the architecture. This way, flight safety is ensured as the unit with FCC functionalities is isolated from payload features, reducing failure probability.
- Facilitates the certification process by segregating critical functions related to control and stabilization from the payload functions.
- Extends the VECTOR autopilot connection capabilities with extra I/O ports for the most advanced configurations. Even more connectivity options while maintaining the reliability and performance of the UAV Navigation-Grupo Oesía Flight Control System based on VECTOR and Visionair.
- Safety and flexibility to develop payload-related features that are completely separate from core UAV control, thereby eliminating any risk to flight safety.
- Maximum flight safety thanks to the VECTOR autopilot. Actuators and key sensors necessary for flight control are connected to the VECTOR.
- Differentiated from competitors by creating custom mission logic.
- Customizable telemetry representation by means of panels created using Visionair SDK.
- MIL-STD-810F, MIL-STD 461F and ISO 9001:2015 qualified hardware.
- VECTOR SDK and Visionair SDK availability for MCC programming* and Visionair customization.
- The use of the known UAV Navigation-Grupo Oesía tools (Breakout Board, Software update application…) to implement your own code.
- Correct behavior of critical subsystems, such as Transponders or Magnetometers. They are ensured as they are controlled by the VECTOR autopilot FCC.
*Customers will require the IAR Systems Embedded Workbench version 7.80 compiler to compile software using the VECTOR-MCC SDK. UAV Navigation-Grupo Oesía does not supply this, so please contact your local IAR Systems reseller. The newer IAR workbench version could be used, but they have not been evaluated.
|
COMPUTING CAPABILITY |
|
|
Mission Control CPUs |
2 CPUs: Twin CPUs system, based on the ARM Cortex A5 processor, achieving 536 MHz of clock speed. |
|
Memory |
|
|
Maximum Task Frequency
|
1000Hz |
|
I/O |
|
|
Total I/O Lines |
62 |
|
Servo or General Purpose I/O Lines |
24 (fully configurable), LVTTL: PWM, Discrete Input, Discrete Output, Pulse Counter (RPM), Simulated GPS PPS, Strobe Light Signal |
|
PWM Rate |
50Hz, 200Hz or 400Hz |
|
PWM Signal |
0.8ms to 2.2ms high, 1us steps |
|
CAN 2.0 A and B |
2 (up to 1Mbps) |
|
Serial Comm |
|
|
Ethernet |
100 Base Tx Channel according to IEEE 802.3 standard |
|
High-speed ADC lines |
8 ADC inputs with 12-bit resolution and up to 1 MHz conversion rate. All channels 0 to 3.3V conversion range |
|
ELECTRICAL |
|
|
Supply (unregulated) |
9V to 36V DC |
|
Power consumption |
2.5 W |
|
MECHANICAL / ENVIRONMENTAL |
|
|
Enclosure Material |
Grade 6082 Aluminium Alloy |
|
Environmental Qualification |
MIL-STD-810 |
|
EMI Qualification |
MIL-STD-461 |
|
Size (mm, H x W x L, box less connectors, width less mounting lugs) |
45.0 x 68.0 x 74.5 |
|
Weight |
160g |
|
Humidity |
Up to 90% RH, non-condensing |
|
Temperature Range |
-40ºC to +85ºC |
|
System Connector #1 |
25-pin GLENAIR MWDM2L-25PCBR-.110 |
|
System Connector #2 |
37-pin GLENAIR MWDM2L-37PCBR-.110 |
|
Auxiliary (serial) port |
|
|
Shock Survival |
500g 8ms 1/2 sine |
|
Mounting Screws |
4 x M4 |
|
ESD Compliant |
IEC 61.000-4-2-level 4 |
| VECTOR MCC Installation Kit |
- 37-Pin Connector Female (model: GLENAIR MWDM2L-37S-6E5-18).
- 25-Pin Connector Female (model: GLENAIR MWDM2L-25S-6E5-18).
- Binder M8 Wire P/N: 77-3406-0000-50006-0200.
The kit also includes programming libraries, examples, and templates in C/C++ code, providing references for better understanding and easier implementation.
In order to further explain VECTOR-MCC, this section will describe three different product setups. It is for the interactions between this mission control computer and the related systems needed for the operation.
MCC for Custom Payload Control
The VECTOR-MCC enhances the integration of a camera with camera-guided mode, allowing operators to fly the aircraft as if in First Person View (FPV), thereby increasing bullseye precision in certain applications.
This aligns with the philosophy of segregating critical tasks from non-critical ones, such as payload control. The MCC runs custom payload software developed by the customer, ensuring that it does not interfere with the Flight Control Computer (FCC) decisions. In this setup, the MCC can execute any algorithms or logic related to the desired payload for the mission, such as artificial intelligence (AI) applications.
MCC to Implement Own FC Laws
Through our VECTOR-MCC or a third-party MCC, always connected to our VECTOR-600 (FCC) system, clients can develop their own flight laws and control the servos directly via two flight modes.
The Mission Control Manual Command (MCM) allows clients to send position commands directly to the servo. The Mission Control Assisted Command (MCA) lets clients send desired attitude or body axes velocity commands from their MCC code to our VECTOR (FCC) autopilot, which translates this information to control the servos. MCM mode is ideal for moments requiring manual control. However, we believe that the FCC controlling the flight is safer and more efficient. MCM supports both fixed-wing (FW) and rotary-wing (RW) platforms and is capable of controlling up to five surfaces.
MCC Commanding FCC
In this third example, the main advantage of this configuration is the independence and freedom of the customer to develop their own software to command the autopilot.
The MCC is connected to the FCC and also to an external data link that communicates with a third-party ground control station. Any guidance command can be sent from the MCC to the FCC with this configuration. Furthermore, it can define no-fly zones, changes in the fly modes, and activation of other systems (FTS), etc.
Own MCC or MCC from Third-Parties
Our VECTOR autopilot family is designed to seamlessly integrate with third-party MCC systems, accommodating a variety of hardware and architectures to provide clients with the freedom to select their preferred system.
For those utilizing our MIL-STD-certified and field-proven hardware, we offer a comprehensive suite of programming libraries and C/C++ code examples to streamline functionality development. If opting for third-party software, clients can use different programming languages, such as MATLAB or others.
However, it is essential that command packages sent from the MCC to our FCC adhere to our proprietary TSIP communication protocol. To facilitate this, we provide an ICD (Interface Control Document) to ensure smooth integration and clear command interpretation by our VECTOR autopilot.
MCC Commanding HIL Simulator
In this fifth scenario, the VECTOR-MCC is connected to a Hardware-In-the-Loop (HIL) simulator, which is primarily used for testing new customer-developed applications. This setup enables on-ground testing, significantly reducing the costs and effort associated with flight testing. Our VECTOR-HIL simulator supports the connection, simulation, and testing of the system configuration—whether using our VECTOR-MCC or a third-party MCC—allowing for thorough code evaluation in a controlled operational environment. The documentation we provide includes a dedicated section to guide clients in setting up this testing scheme and ensuring safe, effective product validation.
