PLC110 compatibility with MS4D 1.3 remains unconfirmed in the available evidence. Reported tests show that the engineering environment can connect to the controller, but project download can stop because the software requests newer firmware that was not available.
Compatibility status and evidence limits
The evidence contains no official release statement confirming PLC110 support in MS4D 1.3. It includes informal reports that support was still under discussion, along with a later assertion that PLC110 would not be supported because its resources were insufficient for the full 1.3 feature set. Treat both statements as unverified until the manufacturers publish a supported-device list, firmware package, or compatibility notice.
| Item | Evidence-supported finding | Engineering decision |
|---|---|---|
| MS4D 1.3 environment | Reported to run and connect to PLC110 | A connection alone does not prove deployment compatibility |
| Project download | Reportedly blocked by a request for newer firmware | Do not approve migration without a matching firmware package |
| MS4D 1.3.X projects | Reported project errors and incorrect operation | Validate the complete application before production use |
| Install v1.3.1 for PLC110 | An installer was reported to have existed, but its status and support were not confirmed | Do not treat installer availability as proof of official support |
Observed deployment failure
The clearest reported failure sequence is: the environment connects to PLC110, project loading is attempted, and deployment is refused because newer firmware is required. The evidence provides no firmware identifier, download location, or approved workaround. Installing an unconfirmed package cannot resolve the compatibility gap unless the required controller firmware also exists and is approved for that exact software release.
Other reports state that MS4D 1.3.X contained errors and that one project did not operate correctly, while a simple project might be testable. This is project-specific evidence, not proof that simple applications are supported or safe for production.
Migration decision and verification procedure
- Record the installed MS4D release, including whether it is 1.3, 1.3.1, or another 1.3.X build.
- Connect to PLC110 and confirm only that communications succeed; do not interpret this result as firmware or runtime compatibility.
- Attempt deployment in a controlled test environment and capture the complete firmware requirement displayed by the software.
- Verify that the required PLC110 firmware and the selected MS4D build appear together in official compatibility information. The supplied evidence contains no such confirmation.
- Run the full project test set after deployment, including every function needed by the application. If deployment remains blocked or project behavior is incorrect, retain the previously validated software and firmware combination.
Do not base a production migration on the reported Install v1.3.1 package alone. Approval requires a loadable firmware combination and successful application-level verification, not merely an operational engineering environment.
FAQ
Does MS4D 1.3 officially support PLC110?
The available evidence does not contain official confirmation. Reports conflict between support being under discussion and PLC110 being excluded because of insufficient controller resources.
Why does MS4D 1.3 connect to PLC110 but refuse the project download?
The reported deployment attempt requested newer firmware that was unavailable. Successful connection verifies communications only; it does not verify a compatible runtime and firmware combination.
Can Install v1.3.1 be used safely with PLC110?
An Install v1.3.1 package for PLC110 was reported, but its official support status and matching firmware were not established. Use it only in a controlled test after confirming manufacturer compatibility, then verify the complete project before production deployment.
