VIO Software - Choosing the Right VIO Version for Your Real-World Needs

Introduction

Choosing the right version isn’t simply a matter of “newer = better.” Each branch (V1, V2, V3) has a different purpose: stability, EIS capability, or feature richness. This guide helps you compare, understand the trade-offs, and select the correct version for your project.

1. Summary Comparison Table (Essentials)

✔ = Supported

✖ = Not supported

⚠️ = Partially supported / early stage / limited

2. When to Choose V1 (Legacy & Stable)

• Existing systems that do not require EIS.
• Environments that have been integrated for a long time and prioritize maximum stability.
• No need for RAW IR or ultra-high-zoom tracking.

3. When to Choose V2 (Core 2.x)

• You need EIS and tracking but prefer to stay within the 2.x app line.
•   Customers who have tuned their systems on 2.x and want to avoid major changes.
•  V2.2.0 (final) includes many 3.x features - making it an ideal bridge version.

 4. When to Choose V3 (Current Branch)

• New projects requiring EIS, RAW IR, EagleEye, ROI tools, and bandwidth control.
•  Users who want SDK v3 for AI integration and automation.
•  Deployments involving multiple devices that need optimized OTA and web settings.

 5. Migration Path (Best Practices)

• From V1.x → Mandatory upgrade to V1.5.0 (bridge) → then move to V2.x or V3.x.
•   Always back up configurations before upgrading.
•  Update gimbal firmware to the required version before mission testing.

6. Risks & Mitigation

• Skipping firmware checks → may cause startup errors: always verify gimbal FW requirements.
•   Forgetting SDK/tool companions → main software updates but SDK becomes incompatible: download the matching SDK/Tools.
•  No downgrade path → prepare a rollback plan (backup & staging environment).

 Conclusion

Choose your version based on:

1.  EIS/tracking requirements;
2.  IR/AI data needs;
3.  Your current version state;
4.  Your ability to maintain firmware & tools.

For most new deployments, V3 is the recommended choice.

About Gremsy