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 logics related to stabilization & 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, whilst 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 of every external sensor that wants to be displayed in the GCS software back to the autopilot in bidirectional communication.
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 which can be controlled on an advanced UAV. In this configuration, the mission is managed as usual by the UAV system operator via the GCS, taking 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 from any devices or payloads connected.
The VECTOR-MCC provides the user flexibility to focus in adding value to the production process and develop their own drivers for payloads which are not critical to flight safety and without the risk of interfering with core UAV control.
The VECTOR-MCC software may be developed by the client independently having its own audit. This allows the user to develop the code and need not share sensitive information about payloads or missions with the FCC manufacturer.
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.
- Facilitate the certification process by segregating critical functions related to control and stabilization from the payloads functions.
- Expand the VECTOR autopilot connections capabilities with extra I/O ports for the most advanced configurations. Even more connectivity options, whilst maintaining the reliability and performance of the UAV Navigation Flight Control System based on VECTOR and Visionair.
- Safety and flexibility to develop payload-related features 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.
- Differentiate from the competitors by creating custom mission logics.
- Customize the 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.
- Use already known UAV Navigation’s 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 autopilots FCC.
|
COMPUTING CAPABILITY |
|
|
Mission Control CPUs |
2 |
|
Memory |
|
|
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.
In order to further explain VECTOR-MCC, this section will be describing 3 different setups of this product. It is appreciable for the interactions between this mission control computer and the related systems needed for the operation.
MCC for Custom Payload Control
The MCC is running a custom payload software developed by the customer, which will not affect the FCC decisions.
In this case, the MCC can be executing any kind of algorithms or logic related to the pertinent payload desired by the customer for the mission (e.g. AI).
MCC Commanding FCC
In this second example, the main advantage of this configuration is the independence and freedom of the customer to develop its own software to command the autopilot.
The MCC is connected to the FCC, and also to an external data link that is communicating 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 be defined as no-fly zones, changes in the fly modes, activation of other systems (FTS), etc.
MCC Commanding HIL Simulator
In this third example, the VECTOR-MCC is connected to a HIL (Hardware-In-the-Loop) simulator.
This setup is mainly focused on testing the new applications developed by the customer. This configuration allows performing on-ground tests which minimize the costs and efforts needed previously to fly.
