Import-Export

Introduction

Hello and welcome to the new quick start guide on how to best use Movicon.NExTâ„¢.
In this technote we will use an example to show you how to import and export elements to and from a Movicon.NExTâ„¢ project.
We will use tags in this example to show you how this is done.

Procedure

Importing tags from a driver

The editor allows you to import tags from files or directly from field devices using drivers and to export tags to files.
We will proceed with importing tags directly from a field device.
Most of the drivers in Movicon.NExT offer a tool to export and import tags to and from the PLC project.
We will now see how to import tags in this way by first opening Movicon.NExT in development mode and using the OPC UA Client driver:

Exporting tags from a project

The I/O Data server allows you to import and export tags from a CSV file so they can be handled in an optimized manner with third-party software such as Microsoft Excel.
We shall now proceed with exporting tags from a project.
To facilitate this, create a BakTags folder on the C disk of your PC. Create a tags.csv file within this folder.
Open Movicon.NExT in development mode and load a project, such as the DemoMoviconNExT project for example. To open this project from the editor's startup page:


 
You should now see the project opened on screen with the Project Explorer window's tree structure populated with the application's resources.
At this point, we can go ahead and export the project's tags:

When this procedure has finished, you should have successfully exported the project tags. By opening the tags.csv file with a text editor or with Microsoft Excel for example, you will be able to manage and modify the tags as needed.

Tag Import

Now we will import the tags we just exported to a new project.
Create an empty Movicon.NExT project and open it in development mode:

If no errors occur duing the import operation, we will see the tags imported on the Tag List in the I/O Data Server directly.
If errors do occur, the software will alert us and ask whether we want to open the System Log to view them in order to find out why they occurred.
The procedure described here is perfectly replicable with any of the Movicon.NExT project's components such as, for example, structures, alarms, converters, Historians and Data Loggers.