Installation Files | Versioning Scheme
Understanding Sepasoft MES Module Versioning
The Core Principle: A Symbiotic Relationship with Ignition
The fundamental principle of Sepasoft's versioning system is its inextricable link to the underlying Inductive Automation Ignition® platform. Sepasoft modules are built directly on Ignition, and as a result, our module versions are designed to correspond directly to the Ignition version you have installed. Understanding this symbiotic relationship is the most critical factor for ensuring system compatibility, stability, and success during any installation or upgrade project. The following section deconstructs the versioning scheme itself to reveal this direct correspondence.
Deconstructing the Version Number
Being able to read and interpret a Sepasoft version string is a crucial skill. It allows you to instantly identify the module's target Ignition platform, its release maturity, and its place within our development cycle. This knowledge is key to selecting the correct software for your specific system requirements.
The standard versioning pattern follows a clear and consistent format:
SEPASOFT MES PLATFORM (dot) IGNITION VERSION (dot) MINOR VERSION (SPACE) RELEASE CANDIDATE
The following table breaks down the example version string 3.81.1 to illustrate how this pattern works in practice:
Component | Example Value | Meaning |
MES Platform | 3 | The major platform generation (e.g., MES Platform 3). |
Ignition Version | 81 | Corresponds directly to the target Ignition version (e.g., 8.1). |
Minor Revision | 1 | Represents a service pack or minor update (e.g., Service Pack 1). |
This structure instantly communicates compatibility without requiring the user to consult a version matrix. The direct correlation is the most important takeaway. For instance, if you are running an Ignition 8.1.x installation, you would need Sepasoft 2.81.x modules for MES Platform 2 or 3.81.x modules for MES Platform 3.
Differentiating Between Release Types
Understanding the distinction between release types—from stable production builds to early-access beta versions—is essential for proper risk management. Selecting the appropriate software for your specific environment, whether it's a live production system or a development sandbox, begins with knowing what each release designation signifies.
- Stable Release and Service Pack (SPx): These are production-ready installations. A stable release is suitable for live manufacturing environments and receives ongoing support through monthly service packs (e.g., SP1, SP2), which deliver targeted bug fixes.
- Release Candidate (RCx): A Release Candidate has successfully passed Sepasoft's internal QA processes and is considered ready for customer development and QA environments. It is not intended for production deployment.
Critical Installation and Upgrade Requirements
The following rules should be treated as non-negotiable best practices for maintaining a stable and functional MES system. Adhering to these requirements is essential for preventing module incompatibility, runtime errors, and unexpected system behavior.
The primary installation best practice is to always install the Ignition version listed as the ‘Highest Tested Ignition Version’ on the official Sepasoft downloads page for the modules you are using.
Furthermore, to prevent gateway errors and ensure data integrity between modules, you must adhere to the following strict version consistency rules:
- All Sepasoft MES modules must have the same version.
- The Business Connector and Web Services Modules must have the same version.
- All MES Utility Modules must have the same version.
Finally, a critical warning is in effect for users moving to our latest platform.
WARNING: If you are upgrading to MES 4.0 from any previous version, you must read the upgrade guide first before installing MES 4.0. Visit the following URL for more information before installing: MES 4.0 Upgrade Guide
For detailed instructions and guidance, please consult our official documentation and support channels.
Essential Resources and Support
This section serves as a central hub for users seeking official documentation, archived software versions, or direct support for specific upgrade paths. Use these resources to ensure your projects are planned and executed correctly.
Upgrade Guides
Support and Archives