General Information

This technical notice describes the changes included in R2.1.1. The software is available now.

Installation Requirements, Instructions, and Troubleshooting

Refer to “Software Installation.pdf” located both at the root of the folder that contains the installation files and in the documentation set that is installed with RemoteConnect.

Application and Firmware Versions

SCADAPack x70 RemoteConnect application version is 3.4.3

SCADAPack x70 English Documentation version is 3.4.3

SCADAPack x70 French Documentation version is 1.2.3

SCADAPack x70 Security Administrator version is 1.2.0

SCADAPack 57x Firmware version is 9.1.3

6601 I/O module firmware version 1.80.10

6601 I/O module bootloader version 1.80.10

6602 I/O module firmware version 1.77.64

6602 I/O module bootloader version 1.77.64

 

Software and Firmware Version Compatibility

RemoteConnect version 3.4.3 is intended for use with SCADAPack x70 firmware version 9.1.3

As of R2.0 and newer, RemoteConnect and SCADAPack 57x firmware is cross compatible with future software and firmware releases. This compatibility is limited to features common to the version of software and firmware available. Unknown feature configurations are parsed and do not block reconfiguration, though the features themselves may be unavailable.

Supported Devices

SCADAPack 570

SCADAPack 574

SCADAPack 575

Supported Operating systems

Windows 7 Professional 32 bit and 64 bit

Windows 8.1 Professional 32 bit and 64 bit

Windows 10 Professional 32 bit and 64 bit

Windows Server 2012 R2

Windows Server 2016

Unity Pro Compatibility

RemoteConnect installations can coexist with specific Unity Pro installations. If RemoteConnect is installed on a computer that had Unity Pro installed previously, the RemoteConnect installation automatically confirms that all components in the SCADAPack x70 Logic Editor and Unity Pro are correctly referenced. If Unity Pro is installed or upgraded on a computer that already had RemoteConnect installed, then a “repair” process is likely required on RemoteConnect to confirm that all components are correctly referenced. A “repair” process must always be “Run as administrator”.

The Unity Pro versions that are verified as suitable for coexisting installation with RemoteConnect are:

  • Unity Pro version 11.1
  • Unity Pro version 12
  • Unity Pro version 13

Removing Unused Function Blocks

After you click Update & Build Logic on the SCADAPack x70 Logic page, the SCADAPack x70 Logic Editor may display an error that a function block is not in the library. This situation can occur if you have an existing project that contains EFBs that are no longer in the latest custom library. You will need to rework your logic application to resolve the issues and remove the function blocks that are no longer in the custom library.

------------------------------------------------------------------------------------------------------------------------------------------

NOTICE

------------------------------------------------------------------------------------------------------------------------------------------

INCONSISTENT DATA, UNPREDICTABLE RESULTS

When you remove elementary function blocks and derived function blocks, the project will no longer perform as it did in the past.

You will need to add new function blocks to update the logic application.

Failure to follow these instructions can result in equipment damage.

------------------------------------------------------------------------------------------------------------------------------------------

To remove function blocks that are no longer in the custom library

  1. In the SCADAPack x70 Logic Editor, remove the EFBs from your project that are causing the errors.
  2. Navigate to Project > Variables & FB Instances > Elementary FB Instances and double-click to open.
  3. In the Data Editor, delete the function block(s).
  4. Navigate to Tools > Types Library Manager > Application and right-click on any item.
  5. Select Purge Unused Types.

The project is updated and linking to EFBs that were in the project, but no longer in the custom library, is cleaned up.

Fixed Issues (R2.1.1)

  • Feature Affected: Modbus Scanner

Issue: The Modbus scanner did not write values when configured to write On change. Values were written at the scan rate when configured to write At scan rate or On change and at scan rate.

Resolution: Values are written when a change is detected when configured to write On change.

Engineering reference: FUN-1471

  • Feature Affected: DNP3 File Transfer

Issue: A cancelled DNP3 file transfer would block subsequent transfers until the original file transfer timed out.

Resolution: The subsequent transfer is no longer blocked.

Engineering reference: FUN-1367

  • Feature Affected: Modbus Scanner

Issue: Modbus Scanner didn’t start after firmware patch and writing configuration.

Resolution: The Modbus Scanner restarts after firmware patch and writing configuration.

Engineering reference: FUN-1455

  • Feature Affected: Modbus Serial Master and Slave

Issue: Modbus serial task can deadlock when a new configuration is applied and a Modbus slave request is received.

Resolution: The Modbus serial task restarts after a configuration is applied.

Engineering reference: FUN-1495

  • Feature Affected: Force LED

Issue: The Force LED turns on incorrectly after a firmware upgrade when no variables are forced due to T_SPx70_INT and T_SPx70_UINT analog forcing, which was removed in R2.1.

Resolution: The Force LED turns on when variables are forced.

Engineering reference: FUN-1503

  • Feature Affected: RemoteConnect project export

Issue: After opening an archived project upgraded from R1.6 to R2.1, the project cannot be exported without making a change to the project.

Resolution: The project can now be exported without making a change

Engineering reference: RSC-2721

  • Feature Affected: RemoteConnect project management

Issue: Opening and closing an unmodified program from an older version of RemoteConnect results in "There are unapplied changes in the project" message.

Resolution: The project is no longer marked as modified until a modification is made by the user.

Engineering reference: RSC-2743

  • Feature Affected: RemoteConnect Read from Device

Issue: The Source Details column in the Object Configuration view is empty after reading from a SCADAPack device. The information is available from the pop-up dialog but not in the table.

Resolution: The information read from the device is now displayed.

Engineering reference: RSC-2765

  • Feature Affected: RemoteConnect Communication Settings

Issue:  When a configuration is written to a SCADAPack device with a changed DNP3 address, RemoteConnect does not reconnect to the device with the new DNP3 address.

Resolution: The new DNP3 address is now used.

Engineering reference: RSC-2769

  • Feature Affected: HART Documentation

Issue: A user must wait 30 seconds before reconnecting a HART device when moving it from one channel to another. This allows the host enough time to recognize that the device is disconnected.

Resolution: Added a procedure for disconnecting and reconnecting a HART device to the documentation.

Engineering reference: DSUM-1049

Known Issues/ Known Customer Difficulties (R2.1.1)

See the section Known Issues / Known Customer Difficulties (R2.1) later in this document.

Post Installation Troubleshooting

Logic Editor is unable to communicate with SCADAPack RemoteConnect

Symptoms:

The SCADAPack x70 Logic Editor is starting, but is unable to communicate with SCADAPack RemoteConnect. When this occurs, the Logic Editor may not display variables that were created in the Object Editor and you may not be able to build the application from RemoteConnect.

Steps to resolve:

Register pserver.dll as described below

1.    Close the Logic Editor and RemoteConnect applications if they are running on the PC.

2.    In the Windows menu, search for cmd.exe then right-click on it and select Run as administrator to open it.

3.    In the command line window, change to the default installation directory by typing one of the following commands:

64-bit systems: cd “C:\Program Files (x86)\Schneider Electric\UnityScadaPack 11.1”

32-bit systems: cd “C:\Program Files\Schneider Electric\UnitySCADAPack 11.1”

4.    Type the following command to complete the registration:

regsvr32.exe pserver.dll

When the registration is complete, a dialog box with the message DllRegisterServer in pserver.dll succeeded is displayed.

Logic editor or Types Library update tool library modification

Symptoms:

SCADAPack Logic Editor or Types Library Update tool reports the library is opened by another application when attempting to modify the logic library

Steps to resolve:

Check that no instances of Unity Pro and RemoteConnect/SCADAPack x70 Logic Editor are running. Use the Process Scrubber, if necessary. If the problem persists, it is likely a Windows folder permissions problem.

Check the following:

  1. With administrator privilege right-click on the following folder:

C:\ProgramData\Schneider Electric

  1. Select Properties.
  2. Select the Security tab.
  3. Click Edit.
  4. Click on the Users entry in the Group or user names section.
  5. Scroll down the Permissions for Users area until you see a row called "Write".
  6. Check the box in the "Allow" column for the "Write" row.
  7. Click OK.

The security settings will update on all the sub-folders.

  1. Click OK to exit the Properties dialog.

Engineering reference: DSUM-919

SCADAPack 57x and 6601 Firmware Version Compatibility

6601 upgrade recommendations: Upgrade 6601 I/O modules (both external and built into SP575) to firmware version 1.80.10 and bootloader version 1.80.10. If extended over-range capabilities for analog inputs are required, return the module to a Schneider Electric facility so the analog inputs can be recalibrated.

6601 minimum firmware version: 6601 I/O modules shipped from the factory with 1.80.6 or 1.80.10 firmware should not be downgraded to versions earlier than 1.80.6.

6601 bootloader upgrade mechanism: The command line command “restart iofirm <filename> <module address>” is provided for 6601 firmware upgrades. The 6601 firmware upgrade command can be used to upgrade the 6601 bootloader. This is only supported on device firmware 9.0.4 and later and 6601 firmware 1.80.6 and later. “restart iofirm bl6601.bin <module address>” will apply bootloader file bl6601.bin. The filename bl6601.bin is the only filename that is accepted for the bootloader. Other file names will result in an attempt to patch the 6601 firmware and not the 6601 bootloader. The 6601 bootloader version is not reported on the command line.

SP57x minimum firmware version: If there is an attached 6601 or a built-in 6601 (SP575) the device firmware version should be 9.0.4 or later.

------------------------------------------------------------------------------------------------------------------------------------------

NOTICE

------------------------------------------------------------------------------------------------------------------------------------------

loss OF SENSOR ACCURACY

If you use firmware versions that are incompatible with extended over-range calibration on 6601 analog inputs, the analog inputs may report values 10% lower than the actual value.

Use only firmware versions that are compatible with extended over-range calibration.

Do not use SP570 or SP575 9.0.3 or earlier firmware in conjunction with a 6601 1.80.6 or later with extended over-range calibration. They are not compatible.

Do not use 6601 firmware earlier than 1.80.6 with extended over-range calibration. They are not compatible.

Failure to follow these instructions can result in equipment damage.

------------------------------------------------------------------------------------------------------------------------------------------

A new version of 6601 I/O module firmware and bootloader has been released since the release of SP57x firmware 9.0.3. A new calibration format for 6601 analog inputs has been added to support extended over-range capabilities. Interoperability of various versions of firmware and calibration is described below.

  SP57x Firmware 6601 Firmware 6601 Calibration 6601 AI Value Over-range Comment
9.0.3 or earlier 1.77.131 or earlier 0…20 mA Reported normally Always active at 20.05 mA
9.0.4 or later 1.77. 131 or earlier 0…20 mA Reported normally Always active at 20.05 mA
9.0.3 or earlier 1.80.06 or later 0…20 mA Reported normally Always active at 20.05 mA 6601 I/O modules upgraded to 1.80.6 from earlier versions will leave calibration unchanged. Recommended for upgrading systems that do not require extended over-range capabilities.
9.0.4 or later 1.80.06 or later 0…20 mA Reported normally Always active at 20.05 mA
9.0.4 or later 1.80.06 or later 0…22 mA Reported normally Always active at 22.00 mA Recommended choice for new installations
X 9.0.3 or earlier 1.77. 131 or earlier 0…22 mA AI report 10% lower values Always active at 20.05 mA NOT RECOMMENDED. Should only occur when a 6601 is mistakenly downgraded from 1.80.6 to an earlier version.
X 9.0.4 or later 1.77. 131 or earlier 0…22 mA AI report. 10% lower values Always active at 20.05 mA NOT RECOMMENDED. Should only occur when a 6601 is mistakenly downgraded from 1.80.6 to an earlier version.
X 9.0.3 or earlier 1.80.06 or later 0…22 mA AI report 10% lower values Always active at 20.05 mA NOT RECOMMENDED. When adding new 6601 I/O modules to existing systems, SP57x firmware should be upgraded to 9.0.4 or later. If this is not practical, contact Schneider Electric technical support.