Best practices and limitations
Good practices:
- Do not use folder or file names ending with dot, spaces, or consisting of spaces only.
- If you insert multiple definitions of the same property for one object, the last is taken in account.
- If you want to import a project that uses a different language, you must import the language file after you import the project. For more information, refer to "Switch languages on the HMI device" in the Studio 5000™ View Designer Help.
Limitations:
- You can store and open projects in network locations, but it is not possible to perform export or import to and from network locations. If you require such functionality, you can use the Windows drive-mapping feature.
- The order of screens and shortcuts after an import may differ from the original order in the exported project.
- Project elements that use reserved operating system names (CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9) are exported with an underscore (_) added in front of the file name. For example:_CON.hmi
- Aliases to enum elements export with integer value instead of enumerated value.
For example:
Access := "1"
This limitation also applies to enum values of borders that have an alias created.
For example:
Border_001:= "<Pen><color>#000000</color><style>4</style><capstyle>0</capstyle><joinstyle>128</joinstyle><cosmetic>false</cosmetic><miterlimit>2</miterlimit><width>8</width><name><name></Pen>",
Provide Feedback