Unity Fastlinx User Documentation

Citect Pty Ltd ABN 88 001 158 854 3 Fitzsimons Lane Gordon 2072 NSW Australia PO Box 174 Pymble 2073 NSW Australia Tel 61 2 9496 7300 Fax 61 2 9496 7399 www.citect.com

Unity FastLinx

User Documentation

Revision 2.0

User Documentation

Contents 1. Introduction ............................................................................................................................2 2. System Requirements ............................................................................................................3 3. Configuring a Linked I/O Device ........................................................................................4 4. Synchronisation Rules..........................................................................................................10

4.1 OPC Protocol Specific.........................................................................................10 4.2 Unite, Modnet, Modbus, MBPlus Protocol Drivers ...........................................17

© Citect Pty Ltd i

User Documentation

1. Introduction The Unity FastLinx product provides the ability to seamlessly integrate tag management between the Schneider Unity Pro tag configuration platform and the CitectSCADA tag configuration system. This allows for the management of tags to be performed from either the CitectSCADA system, Unity Pro or both with each side being maintained in a synchronised state. The Unity FastLinx product also allows the import and export of tags from the CitectSCADA system to Unity Pro or from Unity Pro to the CitectSCADA system. The native Unity .STU file format is supported as well as the .XEF and .XSY XML Unity XML file formats.

© Citect Pty Ltd 2

User Documentation

2. System Requirements Software CitectSCADA v5.5 Service Pack B (CitectSCADA v6.0 recommended) Unity Pro XL 1.0 (Unity Pro 2.0.2 recommended) NOTE – Unity Pro S/M is not supported Operating System Windows XP Service Pack 1, Windows 2000 Service Pack3, Windows 2003 Server (not fully tested), Windows NT not supported Hardware Pentium 500 MHz, 256Mb RAM, 50Mb free HD (Pentium 2GHz, 512 Mb RAM, 256Mb free HD recommended)

© Citect Pty Ltd 3

User Documentation

3. Configuring a Linked I/O Device An I/O device may be linked either through the Express Wizard or via the I/O devices form. To configure the device via the Express Wizard go to the Express Wizard via the CitectSCADA Explorer Window.

Figure 1, Selecting Express Wizard via the CitectSCADA Explorer window.

Click on and the Express Wizard will be invoked. Alternatively the Express Wizard can be invoked via the CitectSCADA Editor Window through the Communication drop down box.

Figure 2, Selecting Express Wizard via the CitectSCADA Editor Window

The following welcome screen for the Express Wizard will be displayed.

© Citect Pty Ltd 4

User Documentation

Figure 3, Express Wizard welcome screen.

Click on to proceed to the I/O Server selection screen.

Figure 4, Express Wizard I/O Server selection screen.

Select or create the I/O Server containing the I/O Device you wish to link to and click

to proceed to the I/O Device selection screen.

© Citect Pty Ltd 5

User Documentation

Figure 5, Express Wizard I/O Device selection screen.

Select or create the I/O device and click to proceed to the I/O Device type selection screen.

Figure 6, Express Wizard I/O Device type selection.

Select External I/O Device and click to continue to the protocol driver selection screen.

© Citect Pty Ltd 6

User Documentation

Figure 7, Express Wizard protocol driver selection screen.

Click on to proceed to the specific protocol driver configuration and then click

to get to the Express Wizard link screen.

Figure 8, Express Wizard Link screen.

Select the Link I/O Device box, Drop down the Database Type and select either Unity FastLinx Dynamic for the live synchronisation mode or Unity FastLinx Static for the XML based import/export mode.

© Citect Pty Ltd 7

User Documentation

Click on the to bring up the Unit FastLinx Link configuration dialog. The following dialog will be displayed.

Figure 9, Unity FastLinx Link Configuration.

The following is a description of the fields. Project File The .STU file for the Unity Pro project to link with. To get access to a network location this should be a UNC path. XML File The XML file to import from or export to when in Static mode. Unity Profile (Not currently supported)

© Citect Pty Ltd 8

User Documentation

DCOM Server Name The name of the server running the Unity Pro application. DCOM User Name The name of the user to run the DCOM component under. Needs to be of the following format <Domain>\<User Name>. DCOM Password The password of the above user. Protocol Driver The driver protocol selected in the I/O device form in CitectSCADA. This will be selected automatically in CitectSCADA v6.0 and above. Logging (Not currently supported)

© Citect Pty Ltd 9

User Documentation

4. Synchronisation Rules

4.1 OPC Protocol Specific The following is the behaviour for synchronisation when using the CitectSCADA OPC protocol driver based tags. With this protocol the CitectSCADA tag address is the Unity Tag name. The CitectSCADA tag name is purely an alias for the CitectSCADA project and does not need to match the Unity tag name. Tag names in CitectSCADA and Unity must be unique. Where there are duplicate address values in CitectSCADA these tag variables will be excluded from the synchronization process. The duplicate tag variables will be clearly set out in the transaction log. The duplicate tag variables will therefore be left in CitectSCADA, maintaining the same information prior to synchronization. Any changes to the Schneider tag variable will not be applied to the duplicate tag variables, and will not be maintained.

4.1.1 Creating a new tag in Unity Pro A new tag created in Unity Pro will subsequently be created in CitectSCADA. The Unity Pro tag address will not be accessible from CitectSCADA. The Unity Pro tag name will be the CitectSCADA tag address and used as the suggested initial.

Scenario : Variable does not exist as a tag name or address in CitectSCADA Addition CitectSCADA Schneider Name Address Type Comment REF Name Address Type Comment

SC_TAG1 INT %MW10 Schneider Tag 1

Result

SC_TAG1 INT SC_TAG1 Schneider Tag 1 SC_TAG1 INT %MW10 Schneider Tag 1

Scenario : Variable exists as a tag name in CitectSCADA in the same IO device but not a tag address

Starting State CitectSCADA Schneider Name Address Type Comment REF Name Address Type Comment

SC_TAG1 SC_TAG0 REAL Schneider Tag 0 SC_TAG0 REAL %MW10 Schneider

Tag 0

Change SC_TAG1 INT %MW120 Schneider Tag 1

Result – This situation will cause a synchronisation error to occur – The CitectSCADA framework will not allow the addition of the duplicate tag in CitectSCADA. The user is notified via the log file.

SC_TAG1 SC_TAG0 REAL Schneider Tag 0 SC_TAG0 REAL %MW10 Schneider Tag

0

© Citect Pty Ltd 10

User Documentation

SC_TAG1 INT %MW120 Schneider Tag 1

Scenario : Variable exists as a tag name in CitectSCADA in a different IO device but not a tag address

Starting State CitectSCADA Schneider Name Address Type Comment REF Name Address Type Comment

SC_TAG1 SC_TAG0 REAL Schneider Tag 0 SC_TAG0 REAL %MW10 Schneider

Tag 0

Change SC_TAG1 INT %MW120 Schneider Tag 1

Result – This situation will not cause a synchronisation error – The CitectSCADA framework will allow the addition of the duplicate tag in CitectSCADA. The user is notified on the next compile of the project. Need to use tag prefix.

SC_TAG1 SC_TAG0 REAL Schneider Tag 0 %MW10 SC_TAG0 REAL %MW10 Schneider

Tag 0

SC_TAG1 SC_TAG1 INT Schneider Tag 1 %MW120 SC_TAG1 INT %MW120 Schneider

Tag 1

4.1.2 Creating a new tag in CitectSCADA A new tag created in CitectSCADA will subsequently be created in Unity Pro. The Unity Pro tag name will be the CitectSCADA tag address. The Unity Pro tag will be unlocated. Scenario : Variable does not already exist in Schneider (Name = Address) Addition CitectSCADA Schneider Name Address Type Comment REF Name Address Type Comment SC_TAG1 SC_TAG1 REAL Citect Tag 1

Result SC_TAG1 SC_TAG1 REAL Citect Tag 1 SC_TAG1 Unlocated REAL Citect Tag 1

Scenario : Variable does not already exist in Schneider (Name != Address) Addition CitectSCADA Schneider Name Address Type Comment REF Name Address Type Comment CI_TAG1 SC_TAG1 REAL Citect Tag 1

Result CI_TAG1 SC_TAG1 REAL Citect Tag 1 SC_TAG1 Unlocated REAL Citect Tag 1


User Documentation

Scenario : Exists in CitectSCADA as tag name but not as address Starting State CitectSCADA Schneider Name Address Type Comment REF Name Address Type CommentCI_TAG1 SC_TAG1 REAL Citect Tag 1 %MW20 SC_TAG1 %MW20 REAL Citect Tag 1

Addition CI_TAG2 CI_TAG1 INT Citect Tag 2

Result

CI_TAG1 SC_TAG1 REAL Citect Tag 1 %MW20 SC_TAG1 %MW20 REAL Citect Tag 1

CI_TAG2 CI_TAG1 INT Citect Tag 2 CI_TAG1 Unlocated INT Citect Tag 2

4.1.3 Deleting a tag in Unity Pro A tag deleted in Unity Pro will subsequently deleted in CitectSCADA. The tag deleted from CitectSCADA will be the one with its tag address the same as the Unity Pro tag name. This behaviour will be configurable allowing the deleting of tags in CitectSCADA to be enabled or disabled. When disabled a subsequent synchronisation may create the tag in Unity Pro again. Scenario : CitectSCADA name and CitectSCADA Address is Identical Starting State CitectSCADA Schneider Name Address Type Comment REF Name Address Type CommentCI_TAG1 CI_TAG1 INT Citect Tag 1 %MW20 CI_TAG1 %MW20 REAL Citect Tag 1

Deletion CI_TAG1 CI_TAG1 INT Citect Tag 1 %MW20

Result %mw20

Scenario : CitectSCADA name and address is not identical Starting State CitectSCADA Schneider Name Address Type Comment REF Name Address Type CommentCI_TAG1 SC_TAG1 REAL Citect Tag 1 %MW20 SC_TAG1 %MW20 REAL Citect Tag 1 CI_TAG2 CI_TAG1 INT Citect Tag 2 %MW30 CI_TAG1 %MW30 INT Citect Tag 2

Deletion CI_TAG1 SC_TAG1 REAL Citect Tag 1 %MW20


User Documentation

Result CI_TAG2 CI_TAG1 INT Citect Tag 2 %MW30 CI_TAG1 %MW30 INT Citect Tag 2

4.1.4 Deleting a tag in CitectSCADA A tag deleted in CitectSCADA will subsequently deleted in Unity Pro. The tag deleted from Unity Pro will be the one with its tag name the same as the CitectSCADA tag address. This behaviour will be configurable allowing the deleting of tags in Unity Pro to be enabled or disabled. When disabled a subsequent synchronisation may create the tag in CitectSCADA again. Scenario : CitectSCADA name and CitectSCADA address are Identical Starting State CitectSCADA Schneider Name Address Type Comment REF Name Address Type CommentCI_TAG1 CI_TAG1 INT Citect Tag 1 %MW20 CI_TAG1 %MW20 REAL Citect Tag 1

Deletion CI_TAG1 CI_TAG1 INT Citect Tag 1 %MW20 CI_TAG1 %MW20 REAL Citect Tag 1

Result %mw20

Scenario : CitectSCADA name and CitectSCADA address not identical

Starting State CitectSCADA Schneider Name Address Type Comment REF Name Address Type CommentCI_TAG1 SC_TAG1 REAL Citect Tag 1 %MW20 SC_TAG1 %MW20 REAL Citect Tag 1 CI_TAG2 CI_TAG1 INT Citect Tag 2 %MW30 CI_TAG1 %MW30 INT Citect Tag 2

Deletion CI_TAG1 SC_TAG1 REAL Citect Tag 1 %MW20 SC_TAG1 %MW20 REAL Citect Tag 1CI_TAG2 CI_TAG1 INT Citect Tag 2 %MW30 CI_TAG1 %MW30 INT Citect Tag 2

Result CI_TAG2 CI_TAG1 INT Citect Tag 2 %MW30 CI_TAG1 %MW30 INT Citect Tag 2

4.1.5 Updating tag type in Unity Pro A tag type updated in Unity Pro will subsequently be updated in CitectSCADA. The tag updated in CitectSCADA will be the one with its tag address the same as the Unity Pro tag name. Scenario Starting State CitectSCADA Schneider Name Address Type Comment REF Name Address Type Comment


User Documentation

CI_TAG1 SC_TAG1 DIGITAL Citect Tag 1 %M10 SC_TAG1 %M10 DIGITAL Citect Tag 1

Change CI_TAG1 SC_TAG1 INT Citect Tag 1 %M10

Result – Change not accepted, user is notified via log file

CI_TAG1 SC_TAG1 DIGITAL Citect Tag 1 %M10 SC_TAG1 %M10 DIGITAL Citect Tag 1

4.1.6 Updating tag type in CitectSCADA The tag type will not be modifiable in CitectSCADA as many type changes require the physical address to also be updated. 4.1.7 Updating tag comment in Unity Pro The tag comment updated in Unity Pro will subsequently be updated in CitectSCADA. The tag updated in CitectSCADA will be the one with its tag address the same as the Unity Pro tag name. 4.1.8 Updating tag comment in CitectSCADA The tag comment updated in CitectSCADA will subsequently be updated in Unity Pro. The tag updated in Unity Pro will be the one with its tag name the same as the CitectSCADA tag address. 4.1.9 Updating tag name in Unity Pro The tag name updated in Unity Pro will subsequently be updated in CitectSCADA. The CitectSCADA tag address will be updated to the new Unity Pro tag name. 4.1.10 Updating tag name in CitectSCADA The tag name updated in CitectSCADA will result in no synchronisation activity. Scenario : Name changed to a tag name that does not already exist in CitectSCADA Starting State CitectSCADA Schneider Name Address Type Comment REF Name Address Type CommentCI_TAG1 SC_TAG1 INT Citect Tag 1 %MW10 SC_TAG1 %MW10 INT Citect Tag 1

Change NEW_TAG SC_TAG1 INT Citect Tag 1

Result NEW_TAG SC_TAG1 INT Citect Tag 1 %MW10 SC_TAG1 %MW10 INT Citect Tag 1

Scenario : Name changed to a tag name that already exists in CitectSCADA Starting State CitectSCADA Schneider


User Documentation

Name Address Type Comment REF Name Address Type CommentCI_TAG1 SC_TAG1 INT Citect Tag 1 %MW10 SC_TAG1 %MW10 INT Citect Tag 1 NEW_TAG SC_TAG2 REAL Citect Tag 2 %MW20 SC_TAG2 %MW20 REAL Citect Tag 2

Change NEW_TAG SC_TAG1 INT Citect Tag 1 %MW10

Result - Outside the scope of FastLinx. This result will not be allowed by the CitectSCADA frame work. A snapshot on the CitectSCADA side will help define that as an error and will require the user to solve the issue before synchronisation.

NEW_TAG SC_TAG1 INT Citect Tag 1 %MW10 SC_TAG1 %MW10 INT Citect Tag 1

NEW_TAG SC_TAG2 REAL Citect Tag 2 %MW20 SC_TAG2 %MW20 REAL Citect Tag 2

4.1.11 Updating a tag address in Unity Pro No visible updates will be made to the CitectSCADA tag 4.1.12 Updating a tag address in CitectSCADA The change of address will either cause the CitectSCADA tag to link to an existing Unity Pro tag with the same tag name as the CitectSCADA tag address or a new Unity Pro tag will be created unlocated with the CitectSCADA tag address as the Unity Pro tag name 4.1.13 Updating a tag in CitectSCADA and Unity Pro A simultaneous modification to a tag in both CitectSCADA and Unity Pro will result in the tag being updated with the Unity Pro changes and the CitectSCADA changes being ignored. 4.1.14 Updating a tag in CitectSCADA and Deleting in Unity Pro A simultaneous update to a tag in CitectSCADA and a delete in Unity Pro will result in the tag being deleted from CitectSCADA and the CitectSCADA changes being ignored. 4.1.15 Updating a tag in Unity Pro and Deleting in CitectSCADA A simultaneous update to a tag in Unity Pro and a delete in CitectSCADA will result in the tag being deleted from Unity Pro and the Unity Pro changes being ignored.

4.1.16 New OPC Tag Originating in CitectSCADA

CitectSCADA Address

CitectSCADA Type

Unity Pro Tag Name

Unity Pro Address

Unity Pro Type Ranges

<tagname> DIGITAL <tagname> Unlocated EBOOL <tagname> INT <tagname> Unlocated INT N/A <tagname> UINT <tagname> Unlocated UINT N/A <tagname> LONG <tagname> Unlocated DINT <tagname> REAL <tagname> Unlocated REAL <tagname> BYTE <tagname> Unlocated BYTE <tagname> STRING <tagname> Unlocated STRING[255]


User Documentation

4.1.17 New OPC Tag Originating in Unity

Unity Pro Tag Name

Unity Pro Address

Unity Pro Type CitectSCADA Address

CitectSCADA Type

Ranges / Comments

<tagname> %M EBOOL <tagname> DIGITAL <tagname> %MW INT <tagname> INT <tagname> %MW UINT <tagname> UINT <tagname> %MW BOOL (bit access) <tagname> DIGITAL <tagname> %MW DINT <tagname> LONG <tagname> %MD DINT <tagname> LONG <tagname> %MB BYTE %MBn BYTE <tagname> %MF REAL <tagname> REAL <tagname> %I EBOOL <tagname> DIGITAL <tagname> %IW INT <tagname> INT <tagname> %IW UINT <tagname> UINT <tagname> %IW BOOL (bit access) <tagname> DIGITAL <tagname> %IW DINT <tagname> LONG <tagname> %ID DINT <tagname> LONG <tagname> %IB BYTE %MBn BYTE <tagname> %IF REAL <tagname> REAL <tagname> %KW INT <tagname> INT <tagname> %KW UINT <tagname> UINT <tagname> %KW BOOL (bit access) <tagname> DIGITAL <tagname> %KW DINT <tagname> LONG <tagname> %KD DINT <tagname> LONG <tagname> %KB BYTE %MBn BYTE <tagname> %KF REAL <tagname> REAL <tagname> %S EBOOL <tagname> DIGITAL <tagname> %SW INT <tagname> INT <tagname> %SW UINT <tagname> UINT <tagname> %SW BOOL (bit access) <tagname> DIGITAL <tagname> %SW DINT <tagname> LONG <tagname> %SD DINT <tagname> LONG <tagname> %SB BYTE %MBn BYTE <tagname> %SF REAL <tagname> REAL <tagname> %Q EBOOL <tagname> DIGITAL <tagname> %QW INT <tagname> INT <tagname> %QW UINT <tagname> UINT <tagname> %QW BOOL (bit access) <tagname> DIGITAL <tagname> %QW DINT <tagname> LONG <tagname> %QD DINT <tagname> LONG <tagname> %QF REAL <tagname> REAL


User Documentation

<tagname> %QB BYTE <tagname> BYTE <tagname> %NW INT <tagname> INT <tagname> %NW UINT <tagname> UINT <tagname> %NW BOOL (bit access) <tagname> DIGITAL <tagname> %CH INT <tagname> INT <tagname> %CH UINT <tagname> UINT <tagname> %MW,

%KW STRING[2x] <tagname> STRING x 1 – 127

<tagname> %MW, %KW

STRING <tagname> STRING internal length of 16 is preserved

<tagname> %MW,

%KW TIME <tagname> LONG TIME type is

preserved <tagname> %MW,

%KW DATE <tagname> LONG DATE type

is preserved <tagname> %MW,

%KW TOD <tagname> LONG TOD type is

preserved <tagname> %MW,

%KW DT <tagname>!A[2] LONG DT type is

preserved

4.1.18 Array Support Arrays are supported for all types except for DT tags and STRING/STRING[x] tags. Arrays in CitectSCADA are denoted by a suffix of !A[x], where x is the dimension of the arrays. Only zero based arrays are supported. For example Unity Tag : Fred %MW4 ARRAY [0..9] OF LONG CitectSCADA Tag : FredTag Fred!A[10] LONG CitectSCADA arrays are limited to no more than 256 bytes of data, ie 32 bit types have a maximum of 64 elements, 16 bit types have a maximum of 128 elements, 8 bit types have a maximum of 256 elements, 1 bit types have a maximum of 2048 elements

4.2 Unite, Modnet, Modbus, MBPlus Protocol Drivers The following is the behaviour for synchronisation when using CitectSCADA Unite, Modnet, Modbus and MBPlus protocol driver based tags. With these protocols the CitectSCADA tag name is the Unity Tag name. Tag names in CitectSCADA and Unity must be unique. The FastLinx Framework prefix feature can be used to assist in keeping tag names unique.

4.2.1 Creating a new tag in Unity Pro A new tag created in Unity Pro will subsequently be created in CitectSCADA. 4.2.2 Creating a new tag in CitectSCADA


User Documentation

A new tag created in CitectSCADA will subsequently be created in Unity Pro. The Unity Pro tag name will be the CitectSCADA tag name. The Unity Pro tag will be unlocated. 4.2.3 Deleting a tag in Unity Pro A tag deleted in Unity Pro will subsequently deleted in CitectSCADA. The tag deleted from CitectSCADA will be the one with its tag name the same as the Unity Pro tag name. This behaviour will be configurable allowing the deleting of tags in CitectSCADA to be enabled or disabled. When disabled a subsequent synchronisation may create the tag in Unity Pro again. 4.2.4 Deleting a tag in CitectSCADA A tag deleted in CitectSCADA will subsequently deleted in Unity Pro. The tag deleted from Unity Pro will be the one with its tag name the same as the CitectSCADA tag name. This behaviour will be configurable allowing the deleting of tags in Unity Pro to be enabled or disabled. When disabled a subsequent synchronisation may create the tag in CitectSCADA again. 4.2.5 Updating tag type in Unity Pro A tag type updated in Unity Pro will subsequently be updated in CitectSCADA. The tag updated in CitectSCADA will be the one with its tag name the same as the Unity Pro tag name. 4.2.6 Updating tag type in CitectSCADA A tag type updated in CitectSCADA will subsequently be updated in Unity Pro. The tag updated in Unity Pro will be the one with its tag name the same as the CitectSCADA tag name. 4.2.7 Updating tag comment in Unity Pro The tag comment updated in Unity Pro will subsequently be updated in CitectSCADA. The tag updated in CitectSCADA will be the one with its tag name the same as the Unity Pro tag name. 4.2.8 Updating tag comment in CitectSCADA The tag comment updated in CitectSCADA will subsequently be updated in Unity Pro. The tag updated in Unity Pro will be the one with its tag name the same as the CitectSCADA tag name. 4.2.9 Updating tag name in Unity Pro The tag name updated in Unity Pro will subsequently be updated in CitectSCADA. The CitectSCADA tag name will be updated to the new Unity Pro tag name. 4.2.10 Updating tag name in CitectSCADA The tag name updated in CitectSCADA will subsequently be updated in Unity Pro. The Unity Pro tag name will be updated to the new CitectSCADA tag name. 4.2.11 Updating a tag address in Unity Pro The tag address updated in Unity Pro will subsequently be updated in CitectSCADA. The CitectSCADA tag address will be updated to the new Unity Pro tag address.


User Documentation

4.2.12 Updating a tag address in CitectSCADA The tag address updated in CitectSCADA will subsequently be updated in Unity Pro. The Unity Pro tag address will be updated to the new CitectSCADA tag address. 4.2.13 Updating a tag in CitectSCADA and Unity Pro A simultaneous modification to a tag in both CitectSCADA and Unity Pro will result in the tag being updated with the Unity Pro changes and the CitectSCADA changes being ignored. 4.2.14 Updating a tag in CitectSCADA and Deleting in Unity Pro A simultaneous update to a tag in CitectSCADA and a delete in Unity Pro will result in the tag being deleted from CitectSCADA and the CitectSCADA changes being ignored. 4.2.15 Updating a tag in Unity Pro and Deleting in CitectSCADA A simultaneous update to a tag in Unity Pro and a delete in CitectSCADA will result in the tag being deleted from Unity Pro and the Unity Pro changes being ignored.

4.2.16 New Unite Tag Originating in CitectSCADA

CitectSCADA Format

CitectSCADA Type

Unity Pro Format

Unity Pro Type

Ranges

%Mn DIGITAL %Mn EBOOL n 0 - 65535 %Sn DIGITAL %Sn EBOOL n 0 - 65535 %Ix.y.z DIGITAL %Ix.y.z EBOOL x 0- 99 : y 0 – 99 : z 0 -

999 %Qx.y.z DIGITAL %Qx.y.z EBOOL x 0- 99 : y 0 – 99 : z 0 -

999 %MWn:b DIGITAL %MWn.b BOOL n 0 – 65535 : b 1 - 16 %MDWn:b DIGITAL %MWn.b BOOL n 0 – 65535 : b 1 - 16 %MDn:b DIGITAL %MWn.b BOOL n 0 – 65535 : b 1 - 16 %KWn:b DIGITAL %KWn.b BOOL n 0 – 65535 : b 1 - 16 %SWn:b DIGITAL %SWn.b BOOL n 0 – 65535 : b 1 - 16 %MBn BYTE %MWn BYTE n 0 – 65534 (n is even) %NWi.j:k INT %NWi.j.k INT i 0 – 127 : j 0 – 63 : k 0 -

63 %NWi.j:k UINT %NWi.j.k UINT i 0 – 127 : j 0 – 63 : k 0 -

63 %SWn INT %SWn INT n 0 – 65535 %SWn UINT %SWn UINT n 0 – 65535 %IWx.y.z INT %IWx.y.z INT x 0- 99 : y 0 – 99 : z 0 -

999 %IWx.y.z UINT %IWx.y.z UINT x 0- 99 : y 0 – 99 : z 0 -

999 %QWx.y.z INT %QWx.y.z INT x 0- 99 : y 0 – 99 : z 0 -

999


User Documentation

%QWx.y.z UINT %QWx.y.z UINT x 0- 99 : y 0 – 99 : z 0 - 999

%MWn INT %MWn INT n 0 – 65535 %MWn UINT %MWn UINT n 0 – 65535 %MWn[x] STRING %MWn STRING[2x] n 0 – 32767 : x 0 - 127 %MWn[8] STRING %MWn STRING n 0 – 65535 %MDWn LONG %MWn DINT n 0 – 65535 %MDn LONG %MWn DINT n 0 – 65535 %MFn REAL %MWn REAL n 0 - 65535 %MDFn REAL %MWn REAL n 0 - 65535 %KWn INT %KWn INT n 0 – 65535 %KWn UINT %KWn UINT n 0 – 65535 %KWn[x] STRING %KWn STRING[2x] n 0 – 32767 : x 0 - 127 %KWn[8] STRING %KWn STRING n 0 – 65535 %KDWn LONG %KWn DINT n 0 - 65535 %KDn LONG %KWn DINT n 0 - 65535 %SDWn LONG %SDn DINT n 0 - 65535

4.2.17 New Unite Tag Originating in Unity

Unity Pro Format

Unity Pro Type

CitectSCADA Format

CitectSCADA Type

Ranges

%Mn EBOOL %Mn DIGITAL n 0 - 65535 %Sn EBOOL %Sn DIGITAL n 0 - 65535 %Ix.y.z EBOOL %Ix.y.z DIGITAL x 0- 99 : y 0 – 99 : z 0 -

999 %Qx.y.z EBOOL %Qx.y.z DIGITAL x 0- 99 : y 0 – 99 : z 0 -

999 %MWn.b BOOL %MWn:b DIGITAL n 0 – 65535 : b 0 - 15 %KWn.b BOOL %KWn:b DIGITAL n 0 – 65535 : b 0 - 15 %SWn.b BOOL %SWn:b DIGITAL n 0 – 65535 : b 0 - 15 %IWx.y.z INT %IWx.y.z INT x 0- 99 : y 0 – 99 : z 0 -

999 %IWx.y.z UINT %IWx.y.z UINT x 0- 99 : y 0 – 99 : z 0 -

999 %QWx.y.z INT %QWx.y.z INT x 0- 99 : y 0 – 99 : z 0 -

999 %QWx.y.z UINT %QWx.y.z UINT x 0- 99 : y 0 – 99 : z 0 -

999 %NWi.j.k INT %NWi.j:k INT i 0 – 127 : j 0 – 63 : k 0 -


User Documentation

63 %NWi.j.k UINT %NWi.j:k UINT i 0 – 127 : j 0 – 63 : k 0 -

63 %SWn INT %SWn INT n 0 – 65535 %SWn UINT %SWn UINT n 0 – 65535 %SWn DINT %SDWn LONG n 0 – 65535 %MWn INT %MWn INT n 0 – 65535 %MWn BYTE %MBn BYTE n 0 – 65535 %MWn UINT %MWn UINT n 0 – 65535 %MWn DINT %MDWn LONG n 0 – 65535 %MWn UDINT %MDWn LONG n 0 – 65535 %MWn WORD %MWn UINT n 0 – 65535 %MWn DWORD %MDWn LONG n 0 – 65535 %MWn REAL %MFn REAL n 0 – 65535 %MWn TIME %MDWn LONG n 0 – 65535 %MWn TOD %MDWn LONG n 0 – 65535 %MWn DATE %MDWn LONG n 0 – 65535 %MWn DT %MDWn[2] LONG n 0 – 65535 %MWn STRING[2x] %MWn[x] STRING n 0 – 32767: x 0-127 %MWn STRING %MWn[8] SRING n 0 – 65535 %KWn INT %KWn INT n 0 – 65535 %KWn UINT %KWn UINT n 0 – 65535 %KWn DINT %KDWn LONG n 0 – 65535 %KWn UDINT %KDWn LONG n 0 – 65535 %KWn WORD %KWn UINT n 0 – 65535 %KWn DWORD %KDWn LONG n 0 – 65535 %KWn TIME %KDWn LONG n 0 – 65535 %KWn TOD %KDWn LONG n 0 – 65535 %KWn DATE %KDWn LONG n 0 – 65535 %KWn DT %KDWn[2] LONG n 0 – 65535 %KWn STRING[2x] %KWn[x] STRING[2x] n 0 – 32767: x 0-127 %KWn STRING %KWn[8] STRING n 0 – 65535

4.2.18 Unite Unsupported Types

The following Unity types are unsupported %ID, %IF, %IB, %QD, %QF, %QB, %KF, %KB, %SF, %CH, %ZZ.MOD, %ZZ.ERR, %ZZ.MOD.ERR The following CitectSCADA types are unsupported %T, %TM, %MN, %C, %R, %DR, %FC, %PWM, %PLS, %SBR, %SC, %MSG

4.2.19 Unite Array Support Arrays are supported for all types except for DT tags and STRING/STRING[x] tags. Arrays in CitectSCADA are denoted by a suffix of [x], where x is the dimension of the arrays. Only zero based arrays are supported.


User Documentation

For example Unity Tag : Fred %MW4 ARRAY [0..9] OF LONG CitectSCADA Tag : Fred %MW4[10] LONG CitectSCADA arrays are limited to no more than 256 bytes of data, ie 32 bit types have a maximum of 64 elements, 16 bit types have a maximum of 128 elements, 8 bit types have a maximum of 256 elements, 1 bit types have a maximum of 2048 elements

4.2.20 New Modnet/Modbus/MBPlus QUANTUM Tag Originating in

CitectSCADA

CitectSCADA Format

CitectSCADA Type

Unity Pro Format

Unity Pro Type Ranges / Comments

1n DIGITAL %In EBOOL n 0 - 65535 3n INT %IWn INT n 0 – 65535 3n UINT %IWn UINT n 0 – 65535 3n.b DIGITAL %IWn.b - 1 BOOL n 0 – 65535

b 1 - 16 3n LONG %IWn DINT n 0 - 65535 0n DIGITAL %Mn EBOOL n 0 - 65535 4n INT %MWn INT n 0 – 65535 4n UINT %MWn UINT n 0 – 65535 4n.b DIGITAL %MWn.b - 1 DIGITAL n 0 – 65535

b 1 - 16 4n LONG %MWn DINT n 0 - 65535 4n REAL %MWn REAL n 0 - 65535 3n[8] STRING %IWn STRING n 0 - 65535 4n[8] STRING %MWn STRING n 0 - 65535 3n[x] STRING %IWn STRING[2x] n 0 – 65535

x 1 - 127 4n[x] STRING %MWn STRING[2x] n 0 – 65535

x 1 - 127

4.2.21 New Modnet/Modbus/MBPlus Quantum Tag Originating in Unity

Unity Pro Format

Unity Pro Type CitectSCADA Format

CitectSCADA Type

Ranges / Comments

%In EBOOL 1n DIGITAL n 0 - 65535 %IWn INT 3n INT n 0 – 65535


User Documentation

%IWn UINT 3n UINT n 0 – 65535 %IWn DWORD 3n LONG n 0 – 65535 %IWn WORD 3n INT n 0 – 65535 %IWn UDINT 3n LONG n 0 – 65535 %IWn REAL 3n REAL n 0 – 65535 %IWn.b - 1 BOOL 3n.b DIGITAL n 0 – 65535

b 1 - 16 %IWn DINT 3n LONG n 0 - 65535 %Mn EBOOL 0n DIGITAL n 0 - 65535 %MWn INT 4n INT n 0 – 65535 %MWn UINT 4n UINT n 0 – 65535 %MWn.b - 1 BOOL 4n.b DIGITAL n 0 – 65535

b 1 - 16 %MWn DINT 4n LONG n 0 - 65535 %MWn DWORD 4n LONG n 0 – 65535 %MWn WORD 4n INT n 0 – 65535 %MWn UDINT 4n LONG n 0 – 65535 %MWn REAL 4n REAL n 0 – 65535 %IWn STRING 3n[8] STRING n 0 - 65535 %MWn STRING 4n[8] STRING n 0 - 65535 %IWn STRING[2x] 3n[x] STRING n 0 – 65535

x 1 - 127 %MWn STRING[2x] 4n[x] STRING n 0 – 65535

x 1 - 127 %MWn TIME 4n LONG n 0 – 65535 %IWn TIME 4n LONG n 0 – 65535 %MWn DATE 4n LONG n 0 – 65535 %IWn DATE 4n LONG n 0 – 65535 %MWn TOD 4n LONG n 0 – 65535 %IWn TOD 4n LONG n 0 – 65535 %MWn DT 4n[2] LONG n 0 – 65535 %IWn DT 4n[2] LONG n 0 – 65535

4.2.22 New Modnet/Modbus/MBPlus PREMIUM Tag Originating in CitectSCADA

CitectSCADA Format

CitectSCADA Type

Unity Pro Format

Unity Pro Type Ranges / Comments

0n DIGITAL %Mn -1 EBOOL n 1 - 65535 4n INT %MWn -1 INT n 1 – 65535 4n UINT %MWn -1 UINT n 1 – 65535 4n[x] UINT %MWn -1 ARRAY [0..x] OF

UINT n 1 – 65535 x 1 - 128

4n.b DIGITAL %MWn -1.b - 1

DIGITAL n 1 – 65535 b 1 - 16


User Documentation

4n LONG %MWn -1 DINT n 1 - 65535 4n REAL %MWn -1 REAL n 1 - 65535 4n[x] REAL %MWn -1 ARRAY [0..x] OF

REAL n 1 - 65535

4n[8] STRING %MWn -1 STRING n 1 - 65535 4n[x] STRING %MWn -1 STRING[2x] n 1 – 65535

x 1 - 127

4.2.23 New Modnet/Modbus/MBPlus PREMIUM Tag Originating in Unity

Unity Pro Format Unity Pro Type CitectSCADA Format

CitectSCADA Type

Ranges / Comments

%Mn -1 EBOOL 0n DIGITAL n 1 - 65535 %MWn -1 INT 4n INT n 1 – 65535 %MWn -1 UINT 4n UINT n 1 – 65535 %MWn -1 UDINT 4n LONG n 1 – 65535 %MWn -1 WORD 4n INT n 1 – 65535 %MWn -1 DWORD 4n LONG n 1 – 65535 %MWn -1.b - 1 BOOL 4n.b DIGITAL n 1 – 65535

b 1 - 16 %MWn -1 DINT 4n LONG n 1 - 65535 %MWn -1 REAL 4n REAL n 1 - 65535 %MWn -1 STRING 4n[8] STRING n 1 - 65535 %MWn -1 STRING[2x] 4n[x] STRING n 1 – 65535

x 1 - 127 %MWn -1 TIME 4n LONG n 1 – 65535 %MWn -1 DATE 4n LONG n 1 – 65535 %MWn -1 TOD 4n LONG n 1 – 65535 %MWn -1 DT 4n[2] LONG n 1 – 65535

4.2.24 Modnet, Modbus, MBPlus Array Support Arrays are supported for all types except for DT tags and STRING/STRING[x] tags. Arrays in CitectSCADA are denoted by a suffix of [x], where x is the dimension of the arrays. Only zero based arrays are supported. For example Unity Tag : Fred %MW4 ARRAY [0..9] OF LONG CitectSCADA Tag : Fred %40004[10] LONG CitectSCADA arrays are limited to no more than 256 bytes of data, ie 32 bit types have a maximum of 64 elements, 16 bit types have a maximum of 128 elements, 8 bit types have a maximum of 256 elements, 1 bit types have a maximum of 2048 elements


Documents

Unity Fastlinx User Documentation