The project opens without the Version Mismatch after Automation Studio can resolve the exact technology-package identity and version recorded in the project. For this case, the unresolved requirement is order number 4PPC70.0702-0F008, version 1.6.1.0, with status Missing. Treat the similar order number 4PPC70.0702-20F008 as a separate candidate until B&R confirms compatibility.
Initial package requirement
- Open the project and copy the complete entry from the Version Mismatch message: order number
4PPC70.0702-0F008, required version1.6.1.0, and statusMissing. - Check whether Automation Studio reports another installed version or no package at all.
Missingmeans the local installation cannot resolve the required package identity; it does not by itself prove that the project is corrupt. - Do not move on until the order number and version have been recorded exactly. Technology-package selection depends on the full identifier, including every digit and hyphen.
| Reading | Meaning | Next check |
|---|---|---|
4PPC70.0702-0F008, 1.6.1.0, Missing
|
The required package is unavailable to the current Automation Studio installation. | Search the local catalogue and installed-package inventory. |
| Same order number, different version | The package family may be present, but the project-specific version is absent. | Obtain version 1.6.1.0 or use a controlled project-upgrade path. |
| Different order number | The available package is not an exact identity match. | Confirm substitution with B&R before installation or conversion. |
Local catalogue and installation check
- Search the Automation Studio catalogue for the full order number
4PPC70.0702-0F008. Confirm both the identifier and displayed version before selecting anything. - Inspect the installed technology packages using the package-management function available in the installed Automation Studio release. Search by the full identifier rather than the shortened product family.
- If version
1.6.1.0appears as installed, restart Automation Studio and reopen the project. A stale package index or an incomplete application restart can leave the project resolver unaware of a newly added package. - If the package remains absent from both locations, continue to the official-download access check. Repeated catalogue searches will not resolve a package that is not published through that catalogue channel.
Automation Studio validates project dependencies before it can fully resolve the configured hardware and its associated engineering objects. The project stores a package reference, while the workstation maintains its own installed-package inventory. A mismatch occurs when those two sets do not contain the same required identity and version.
Official-download access check
- Log in to the official B&R website before searching the download area. The identified hardware-upgrade download requires authenticated access.
- If no account is available, submit the B&R account request and wait for approval. Account access is a prerequisite for retrieving a restricted package; Automation Studio cannot compensate for missing download authorization.
- After login, search using the complete required order number and version. Record the identifier displayed on the download page before downloading.
- If the portal returns only
4PPC70.0702-20F008, stop at the identity check below. Do not install it merely because most characters match.
Use the official B&R download channel or an official B&R support channel for unavailable legacy packages. A project dependency can remain valid even when its package is not visible in the standard Automation Studio catalogue, particularly when distribution requires a registered account.
Order-number identity decision
The project requests 4PPC70.0702-0F008, while the indicated hardware-upgrade entry is labeled 4PPC70.0702-20F008. The additional 2 is a material difference, not a formatting variation that an integrator should silently discard.
| Check result | Decision | Required confirmation |
|---|---|---|
The downloaded package explicitly lists 4PPC70.0702-0F008 and 1.6.1.0
|
Proceed with installation. | Confirm the package manifest or installer displays both exact values. |
The page or package lists only 4PPC70.0702-20F008
|
Do not treat it as the requested package. | Ask B&R whether it supersedes, contains, or supports the required identity. |
| B&R confirms a replacement or upgrade path | Follow that documented path on a project copy. | Confirm the target hardware selection and project dependency after conversion. |
| No compatibility confirmation is available | Retain the original project requirement. | Request the exact archived package from an official B&R support channel. |
Similar catalogue identifiers may represent different hardware variants, revisions, or distribution packages. Installing a near match can leave the original dependency unresolved or prompt a project conversion whose hardware impact has not been reviewed.
Controlled package installation
- Create a separate backup copy of the project before installing a replacement package or accepting any conversion. Keep the untouched copy tied to
4PPC70.0702-0F008version1.6.1.0. - Close Automation Studio, then install the authenticated B&R package through the installation method supplied with the download.
- Confirm that the installer or package inventory reports the exact required order number and version. Do not move on if it reports only
4PPC70.0702-20F008without an official compatibility statement. - Restart Automation Studio so its package inventory is rebuilt, then open the project copy.
- If Automation Studio offers a project upgrade, read the proposed source and destination package identities before accepting it. An upgrade changes the engineering baseline and is not equivalent to restoring the missing original version.
Project verification and recurring pitfalls
- Reopen the project and confirm that the Version Mismatch entry for
4PPC70.0702-0F008version1.6.1.0no longer showsMissing. - Open the hardware configuration and confirm that the intended target remains selected. A cleared dialog is insufficient if a conversion changed the target definition.
- Run the project build and review the resulting diagnostics. Resolve any remaining missing-package or hardware-reference messages before connecting to equipment.
- Compare the dependency list against the recorded pre-installation values. Confirm whether the project still references the original package or an officially approved replacement.
Common commissioning errors are searching without first logging in, shortening the order number, accepting a visually similar package, and treating successful installation as proof that the project resolved the intended hardware. Each error is caught by checking the exact identifier at the message, download, installed-package inventory, and reopened project.
FAQ
How do I clear the B&R Automation Studio Version Mismatch?
Install the exact technology package requested by the project: 4PPC70.0702-0F008 version 1.6.1.0. Restart Automation Studio and confirm the dependency no longer reports Missing.
How do I download a B&R package that is not in the catalogue?
Log in to the official B&R website and search the authenticated download area. If you do not have an account, request one from B&R before attempting the download.
How do I know whether 4PPC70.0702-20F008 replaces 4PPC70.0702-0F008?
Compare the package manifest and obtain confirmation from an official B&R channel. The identifiers differ by an added 2, so visual similarity alone does not establish substitution.
How do I verify the package installation fixed the project?
Reopen the project, confirm version 1.6.1.0 is no longer Missing, verify the intended hardware target, and complete a project build with no remaining dependency message for 4PPC70.0702-0F008.