AVEVA Simulation for Foxboro Control 2024

XREF extraction problem with FDC

The FDC app would crash when extracting XREF for DCI blocks configured with large negative value point numbers (Value Info). Affected Block Types include BIN/R, BOUT/R, IIN/R, IOUT, PAKIN/R, PAKOUT, RIN/R, ROUT/R.

The XREF extraction process can now handle large negative and alphanumeric point numbers without problem or warning. Point numbers out of range generate a WARNING in Dynsim. Point numbers that cannot be parsed generate an ERROR in Dynsim.

Problem corrected for all CP types in SCP 24.0 QF1.

IC restore for Sequence block String params

The String params of certain block types (IND, DEP, EXC, STRIN, STROUT, STRING) that are 80 characters were incorrectly restored from snapshot causing HMI display problems.

Problems corrected in SCP 24.0 QF1

Alarms on AW or WP

When running SCP with ComexZMQ on AW or WP computers:

• The alarm subsystem would occasionally hang and require a reboot to fix.

• Loading an IC would occasionally cause the alarm IC file to be deleted.

  Problems corrected in SCP 24.0

IC alarm file deletion

While loading an IC, the target IC alarm file "FSIMAlarmData" on AW or WP computers was occasionally deleted.

Problem corrected in SCP 24.0

Uninstall on AW or WP did not check IA/CCS running

When uninstalling SCP from an AW or WP computer, the setup program removed some files before checking if IA or CCS was running. This resulted in a failed uninstall.

Setup program now checks if IA or CCS is running before uninstalling.

Problem corrected in SCP 24.0

Secure Boot

The SCP IA Virtual Switch Driver was not compatible with Secure Boot (UEFI).

The workaround was to disable secure boot.

Problem corrected in SCP 24.0

Selective Restore Tool (SRT)

The tool did not properly restore an IC if the SCPRestore.json file was present but empty. The tool did not properly support the memory parameters for CALC / CALCA / LOGIC / MATH blocks. Certain Blocks: Params were deemed inappropriate for the SRT and removed from the tool.

The tool may not restore certain BLNALM shadow parameters correctly from snapshots saved in earlier version numbers (11 and lower). Fixes for the tool required a new snapshot version number (12). Create a new snapshot.

Problem corrected in SCP 23.0.

Installation – non-C drive location

If the SCP is installed to a non-C drive location (such as the D drive), then the SCPApps fails to restore their snapshots.

Problem corrected in SCP 23.0.

SCPEngine fails to find SCPApps

The SCPEngine occasionally has problems finding SCPApps running on the local computer. This happens when there are many other processes running on the computer. The SCPEngine was improved to filter more efficiently through the processes to find the SCPApps.

Problem corrected in SCP 4.2QF.

CP crashed loading checkpoint at startup

FDC controller crashes when validating ECBs during checkpoint load. In some cases the SCP 4.2 saves a bad checkpoint. Controller must be initialized and new checkpoint created using SCP 4.2QF.

Problem found in SCP 4.2.

Problem corrected in SCP 4.2QF.

SEQ block SENDMSG crash

SEQ blocks using SENDMSG occasionally cause CP to crash. The problem occurs when freeing the message memory.

Problem found in SCP 4.2.

Problem corrected in SCP 4.2QF.

MON block 3214 error

MON block goes into manual mode with 3214 error. This was a bug in the Foxboro CP code FCP280 image 093007 and was corrected in Foxboro CP code FCP280 image 093009.

Problem found in SCP 4.2.

Problem corrected in SCP 4.2QF.

Snapshot save issue with AIN/R and FLOP=2

Snapshots do not save all required parameter(s) of the AIN/R block when Butterworth filtering is enabled (FLOP=2). Snapshot restore may experience a bump for this configuration for older snapshots (snapversion 10 and lower).

New snapshot version (snapversion) 11 saves the required AIN/R parameter(s) for all AIN/R FLOP options.

Problem found in SCP 4.1.

Problem corrected in SCP 4.2QF.

Snapshot save issue with SEQ block

The following message appears in the SCP window and DYNSIM message manager when saving an IC under certain circumstances:

"sub# -1 – invalid length (1784) for shadow DS at 0x0…."

The SEQ block SimAPI code has a built-in arbitrary limit of 1000 characters when saving details to an IC. The limit was extended to the size of short data type or 32767 characters.

Problem found in SCP 4.1.

Problem corrected in SCP 4.2.

SCP Engine not passing cross-referenced values to SCP Apps after an Initial Condition (IC) load

After an Initial Condition (IC) load, the Simulation Control Processor (SCP) Engine does not pass the cross-reference (xref) list value to the SCP App unless the From symbol is changed. This occurred in the following circumstance:

1. Have an IC.

2. Change the cross-reference list, and then load cross-reference (LX).

3. Restore the previously saved IC.

   For example, the xref list passes DIGFALSE to the control block in SCP. After the change, the xref list passes DIGTRUE to the control block in SCP. Next, restore a saved IC when DIGFALSE passes. The control block does not receive the DIGTRUE update until you perform an LX after the IC loads.

   Problem found in SCP 4.0.

   Problem corrected in SCP 4.1.

Field Device Controller (FDC) Fault Tolerant (FT) controller crashing

The FDC FT controller is crashing because it does not properly handle the FT portion of the system monitor (SMON) message.

Problem found in SCP 4.0.

Problem corrected in SCP 4.1.

Dell

To set the UEFI Secure Boot to OFF

4. Power on your computer.

5. During boot up, press F12.

6. Select change boot mode setting, and then select UEFI Boot Mode.

7. Select Secure Boot OFF.

8. Select Save and exit.

HP

To set the UEFI Secure Boot to OFF

9. Power off your computer.

10. Power on your computer, and then immediately press Esc repeatedly until the Start Menu opens.

11. Select BIOS Setup (F10), and then press Enter.

12. Select the Advanced tab, and then select Secure Boot Configuration.

13. Select the Configure Legacy Support and Secure Boot dropdown menu. Then select Legacy Support Enable and Secure Boot Disable.

14. Select the Main tab, then select Save Changes and Exit, and then select Yes to display a random 4 digit PIN.

15. Enter the PIN displayed from the previous step, and then press Enter.

16. Power off your computer.

17. Power on computer, and then immediately press Esc repeatedly until the Start Menu opens.

18. Select BIOS Setup (F10), and then press Enter.

19. Select the Advanced tab, and then select Boot Options.

20. Under Legacy Boot Order, select a boot device (hard drive), and then press Enter.

21. Select the Main tab, select Save Changes and Exit, and then select Yes to confirm.

Refer to the following HP support document (Secure Boot settings for business notebooks and workstations): https://support.hp.com/us-en/document/c04784866

Lenovo

To set the UEFI Secure Boot to OFF

22. Power on your computer.

23. During boot up, press F1 until BIOS screen appears.

24. Navigate to the Security tab using the arrow keys.

25. Select Secure Boot in the menu using arrow keys and select Enter.

26. Disable Secure Boot.

27. Press F10 to save and exit.

    Refer to the following Lenovo support document (How to Turn on SecureBoot on 'Think' systems): https://support.lenovo.com/us/en/solutions/ht509044-how-to-enable-secure-boot-on-think-branded-systems-thinkpad-thinkstation-thinkcentre

24.0

Uninstall

Running SCPSetup.exe to uninstall a ONE_BOX installation on a Foxboro IA-installed computer does not offer removal of SCP.

Workaround:

Use Programs and Features to uninstall SCP.

24.0

Installation – WebView2

If MS Edge is installed but MS WebView2 Runtime is not installed, the SCP installer skips installing WebView2.

Workaround:

Manually install MS WebView2 Runtime. The installer is included in the SCP installation files. See "Appendix J" of the AVEVA Simulation for Foxboro Control – Installation Guide.

24.0

Domain

If the Foxboro computers are part of a Domain, then the SCP computer must be part of the Domain. If it is not, then communications issues may occur between the Foxboro and SCP computers. The SCP App may repeat the "I’M ALIVE" message.

This is a long standing issue that affects many previous versions of SCP.

24.0

System Monitor

If the system definition specifies a CP is monitored by a computer that is not present (or turned off) in the simulation system, the SCP App may repeat the "I’M ALIVE" message.

To Fix:

28. In the System Definition, reassign the CP to an existing simulation station for monitoring (ASMON).

29. Perform a Day 1 on all I/A computers.

30. Generate a new SCP Launcher configuration.

4.2 QF

Installation - non-C drive location

If the Simulation Control Processor (SCP) is installed to a non-C drive location (such as the D drive), then the SCPApps fails to restore their snapshots. This is a problem with the Selective Restore Tool (SRT).

Workarounds:

• Install the SCP to the C drive.

  Or

• Create an SCPRestore.json file using the SRT with all params selected, and then save the file.

4.1

Environment Setup (Windows Certificates)

An SCPApp fails to acquire a license and does not start.

The SCPApp uses Licensing 2.0 (Auth0) software, which requires the following Windows certificates to function properly:

* CA = Certificate Authorities

You can enter certlm.msc in the Windows Search or Run app to open the Windows Certificate Manager to view and manage your installed certificates.

Workaround:

31. Install the certificates in the preceding table to the specified locations.

32. Reboot the computer and start the SCPApp.

4.1

Installation — License server

If you select FNP/TKN during installation, the installer creates and populates IPASSI_LICENSE_FILE environment variable:

• The DYNSIM installer creates and populates for both the user and the system.

• The SCP installer creates and populates for only the system.

  The user environment variable takes precedence over the system environment variable. This can create a condition in which SCP is unable to find its license.

  Workaround:

  There are two options to ensure that SCP finds its license:

• Modify both the user and system IPASSI_LICENSE_FILE environment variables to be the same.

• Delete the user IPASSI_LICENSE_FILE environment variable and only use the system variable.

4.1

Installation — .Net Framework 4.8

If Microsoft .NET Framework 4.8 fails to install properly, the SCP 4.1 installation cannot proceed. You may see the following:

To manually install Microsoft .NET Framework 4.8

33. Exit the SCP installer.

34. Run Microsoft .NET Framework 4.8 using the installer (NDP48-x86-x64-AllOS-ENU.exe) provided in the DotNetFX48 directory included with the SCP installer.

35. Rerun SCP installer.

4.0

Microsoft .Net Framework 4.6.2 fails to install in Foxbase WinServer2008R2

(SCP 4.0)

When installing SCP 4.0 in a Foxbase WinServer2008R2, Microsoft .Net Framework 4.6.2 fails to install. It throws the below error.

Workaround:

Install the Microsoft Certificate "MicRooCerAut2011_2011_03_22.crt" as a trusted certificate and then proceed with installing SCP 4.0. For more information, see "Appendix G" of the AVEVA Simulation for Foxboro Control – Installation Guide.

4.0

Windows Power Plan

Windows 10 and Windows Server 2016 have a Power Plan feature that conserves energy by turning off the hard disk or putting the computer to sleep after a certain amount of inactive time. If one of the simulation computers experiences such a "power conserving" event, the simulation may shutdown or crash.

Workaround:

Consult "Appendix H" in the AVEVA Simulation for Foxboro Control – Installation Guide for instructions on how to set the power plan for Windows.

4.0

LaaS License Log Files

The SCP installer configures the LaaS License Log Files to be written to the C:\TEMP directory in the AVEVA_ARMS_LOGFILE environment variable. If this directory does not exist, the log files are not written.

Workaround:

Manually create the C:\TEMP directory if it does not exist.

3.1 HF2

Environment setup — Daylight Savings Time (DST)

DST can affect the time shown on FoxView trends. Computers running FoxView have Foxboro Group policies that disable DST whereas Windows Out-of-Box enables DST. This means that when the DST comes into effect, the time shown on the FoxView trends can be off by an hour. Moreover, restoring an Initial Condition (IC) saved when DST had been off can lead to even more time shift.

To fix the DST error

36. Enable DST on all computers running simulation engines (DYNSIM, SCP, TriSim, FAIM, SimSync, etc.)

37. Synchronize the system time on all computers (set non-Foxboro installed computer system time to the Foxboro installed computer system time).

3.1 HF2

Environment setup — Anti-virus

Anti-virus software such as McAfee Endpoint Security may interfere with the operation of SCP by quarantining certain files. We recommend disabling all anti-virus software.

Workaround:

Do not use anti-virus software on simulation computers or examine the quarantined files. If they are in the SIMSCI directories, then add them to the approved file list and restore them.

3.1

Environment setup — Power plan

The "Balanced" power plan in Windows 10 & Server 2016 can result in the SCP apps momentarily losing contact with the license server. In this case, the SCP apps immediately shut down.

Each computer running SCP apps and/or a local FNP license server should have its power plan set to "High Performance"

To set the power plan to High Performance

38. Run gpedit.msc.

39. Navigate to Local Computer Policies > Computer Configuration > Administrative Templates > System > Power Management > Select an active power plan.

40. Enable and choose the High Performance Plan.

3.1

Environment setup — Windows update

Windows 10 & Server 2016 operating systems automatically update themselves. Unplanned Windows updates while the simulation is running can cause problems.

To disable unplanned Windows updates

41. Disable the Windows Update service on all SCP computers.

42. Open the Services Desktop App.

43. Locate Windows Update (wuauserv), and then right-click and select Properties.

44. Select Startup type: Disabled.

45. Select Apply.

Note: I/A and Control Core Services (CCS) installation automatically disables the Windows Update service.

3.0 HF2

Defect 517745

(SCP 3.1)

SCPEngine crashes on a very large simulation. The crash was traced to the ACE/TAO libraries distributed with SCP 3.0. The ACE/TAO libraries in SCP 3.1 are the same distributed libraries used by DYNSIM 6.0.

Corrected:

This was corrected in SCP 3.1.

Note: DYNSIM 5.3.x must be installed prior to SCP 3.1. If the user plans to install a newer version or HF for DYNSIM 5.3.x, then SCP 3.1 must be uninstalled before DYNSIM 5.3.x is uninstalled, and DYNSIM 5.3.x must be installed before SCP 3.1 is installed.

3.0

Installation

SCP intentionally modifies the network interface card (NIC) properties for the NIC that connects to the Foxboro Evo Control Network (FECN), formerly MESH. It removes checkboxes from all options except:

• Internet Protocol Version 4 (Transmission Control Protocol [TCP]/IPv4)

• Intelligent Automation (IA) Virtual Switch Protocol

  When SCP is uninstalled, it does not return the NIC to the original settings.

3.0

Installation

When installing SCP on a Foxboro AW, it installs components only when the correct version of FoxView is found. For systems using Foxboro Evo Control Human Machine Interface (HMI), formerly Wonderware InTouch, install the equivalent Foxboro Evo Simulation software.

If SCP is installed on a system with Control HMI, then no features are installed, but SCP appears in the list of installed software in Programs and Features.

3.0

Defect 481202

(SCP 3.0)

SCPEngine scenario watch point file is not read correctly. The SCPEngine was updated to read the 3rd and 4th field in the file. This requires updates to the watch point file to include commas for these additional fields.

For example, if the scpeng.sce file contains the following, then the watch point file should be modified as follows:

• DEMO:LVL_CTRL.SPT,0.01 to DEMO:LVL_CTRL.SPT,0.01,,

• DEMO:LVL_CTRL.OUT,0.01,M to DEMO:LVL_CTRL.OUT,0.01,M,

2.1

Installation

SCP installation fails if any of the following files exist on an Application Workstation (AW) computer.

• D:\opt\fox\wp\FoxView\foxview.exe.ia_orig

• D:\opt\fox\wp\FoxView\foxview_rc.dll.ia_orig

• D:\opt\fox\wp\FoxView\lic_swi.dll.ia_orig

• D:\usr\fox\system32\wam.dll.ia_orig

• D:\usr\fox\wp\ams\bin\aaServer.exe.ia_orig

• D:\usr\fox\wp\ams\bin\aht.exe.ia_orig

• D:\usr\fox\wp\ams\bin\am.exe.ia_orig

  The above files are the original files installed during the Intelligent Automation (I/A) / Control Core Services (CCS) installation. SCP moves the original files before it installs its own version of each of these files.

  SCP installation fails if this file exists on an AW computer:

• D:\opt\scp\SCPAlmSnapMgr.exe

To correct the installation process

46. Restore the original files (move foxview.exe.ia_orig to foxview.exe, etc.)

47. Ensure that each of the original files (.ia_orig) and SCPAlmSnapMgr.exe no longer exists by deleting the files.

48. Reboot the computer, and then attempt the installation again.

    For more information, see "Appendix E" of the AVEVA Simulation for Foxboro Control – Installation Guide.

2.1

Environment setup — Firewall

All Firewall software must be disabled on the SCP computer. Examples of Firewall software include:

• Windows Firewall

• McAfee Host Intrusion Prevention (HIP) for desktop

• Norton Internet Security

  If one or more of these Firewall software applications is running, it may prevent SCP from functioning properly.

2.1

HIFS#363

DYNSIM 5.1 installation fails on Windows Server 2008 R2 when using an I/A customized image.

Workaround:

Install Java version 7 (jdk-7u5-windows-i586.exe) before installing DYNSIM 5.1.

2.1

Defect 457966

(SCP 2.1+)

Since the SCP 2.0 release (including hotfixes), the digital signature for the virtual switch driver has been updated from SHA-1 to SHA-2 (SHA-256) hash encryption.

This may require the Windows security update KB3033929. If the system is up to date on Windows security patches, this is not an issue. Otherwise, if you experience a -2005 error when starting the SCP app, you need to patch your Operating System (OS) and reinstall the SCP application.

Please read the security information and download the update at https://www.microsoft.com/en-us/download/details.aspx?id=46148

24.0

Engine warnings

SCP 24.0 removed two unused SCPEngine options (HBtimeout and pubRounds). When starting a simulation configured in a previous version of SCP, warnings may appear in the SCPEngine window for unknown options HBtimeout and pubRounds. These warnings cause no problem.

Workaround:

To remove the nuisance warnings, the simulation engines.json file must be manually edited to remove deprecated options HBtimeout and pubRounds.

Remove the following sections from each SCPEngine:

• <Option>\n<Name>HBtimeout</Name>\n<Default>60</Default>\n</Option>

• <Option>\n<Name>pubRounds</Name>\n<Default>3</Default>\n</Option>

• Shutdown, close and save the simulation. Close Dynsim.

3.1 HF1

Error Loading Xref / Internal Xref in SimExec

When loading a full simulation using any simulation engine, the following two errors may occur if the network is misconfigured:

One possible cause for these errors is incomplete host file settings. For more information, please see "Simulation on Multiple Computers" and “Hosts File on AW / WP” in the AVEVA Simulation for Foxboro Controls — User Guide.

3.1

FoxView applications show parameters with CYAN color background ("smurfing").

Simulation stops responding and all FoxView application display parameters with CYAN color background ("smurf"). This may happen when many operator stations are used simultaneously.

One possible cause of this is incorrect SimSyncEngine settings. Consult the AVEVA Simulation for Foxboro Control – User Guide > SimSync Engine Time Slice Behavior > Suggested Settings.

3.1

FAIM

Initial Conditions (ICs) containing Foxboro AIM (FAIM) historian data do not restore properly after FAIM .inp file is modified.

The .inp is processed by FAIMBatch. The processed result is used by the FAIMengine to save collected data into a database. FAIMengine ICs are stored using this database. If the FAIM .inp file is modified, the database is no longer valid. The FAIM portion of ICs saved prior to the .inp file change is unusable.

24.0

Day 1

It is not possible to perform a "Day 1" operation on a Foxboro-installed CCS computer in MS Azure. Azure requires a slightly different CCS installation than a normal on-prem system; therefore, there are differences with the arp table preventing the "Day 1".

Workaround:

None.

4.1

Alarm Devices

Alarm devices are not imported when performing a loadall using Control Core Services (CCS) 9.5, 9.6, or 9.7 with a saveall created in a previous version of CCS. This is a problem with CCS and not Simulation Control Processor (SCP).

Workaround:

Edit the station block and re-enter the alarm devices.

4.1

FDC Control Processor (CP) Image number

In FoxView, the CP STA block displays the CP image number where the FCP270 and FCP280 have 6 digit image numbers, and the FDC280 has a 10 digit image number.

FoxView displays only 6 digits of the image number. The last 4 digits of the FDC image number will not be displayed.

Workaround:

Use Control Software to view the entire 10 digit image number of the FDC CP.

4.1

System Manager with SCP (4.1 and 4.0)

The System Manager is not fully supported by SCP.

FBMs for FCP280s do not appear in the System Manager. There is no workaround at this time.

FBMs for FCP270s appear in the System Manager.

4.1

Online Upgrade (OLUG)

Foxboro Control Processors (CPs) can be upgraded while online (OLUG), and a maintenance pack or quick fix can be loaded into CP memory.

Simulation Control Processor (SCP) does not support Online Upgrade. Each version of SCP contains a unique CP image that cannot be changed. The only way to change the CP image is to change the version of SCP.

4.0

Start / Reboot SCPs using AVEVA LaaS license service

The AVEVA License as a Service (LaaS) license server cannot handle parallel applications applying to its service at the same time. When starting or rebooting multiple SCPs at one time, newly started SCPs may return Unauthorized use when trying to obtain an AVEVA LaaS license.

Workaround:

Start or reboot one SCP at a time from the SCPLauncher when using the AVEVA LaaS license service. Modify the start batch file (generated by the SCPLauncher) to have a five-second delay between SCP starts (instead of the default one-second delay).

timeout /t 5 > NUL

3.1

Multiple Remote Desktop Protocol (RDP) sessions on an AW / Workstation Processor (WP)

(SCP 3.0 HF2 and earlier)

Multiple RDP sessions on an AW / WP are not supported by SCP 3.0 HF2 and earlier. The SCP processes running on the AW / WP expect only one session.

Workaround:

A workaround is available upon request for SCP 3.0 HF2.

Supported in SCP 3.1:

In SCP 3.1 and later, multiple RDP sessions on an AW / WP are supported.

3.1

FDC 280 Object Manager (OM) Packet Checksums

The FDC280 in SCP 3.1 has been simplified to skip checksum comparisons for OM packets.

3.0

SCP does not support active Device reconfiguration

(SCP 1.0+)

SCP does not adjust its internal device table if an external device requests a change to its address.

Example:

Upon SCP startup, a Common Network Interface (CNI) registers its device address with the SCP.

All control generated alarms are sent to the CNI for distribution.

If the CNI reboots, the CNI registers with the SCP with the CNI’s new device address, but the SCP does NOT process the new CNI’s device address.

As the SCP continues to send alarms to the old CNI device address, they are neither received nor distributed.

Workaround:

Reboot the SCP.

2.1

Identify Duplicate SCP launching

When the SCP application is running on more than one computer, the Launcher does not recognize that the Control Processors (CPs) may be "Active" on another computer. The Launcher currently tracks only SCPs running on the same computer as the Launcher.

2.1

System Manager with SCP

(SCP 1.0+)

The System Manager is not fully supported by SCP.

Due to the lack of Fieldbus Module (FBM) emulation, the System Manager displays:

• Equipment Control Block (ECB) devices are shown in cyan although they are healthy and online. This applies to all Input/Output (I/O)/Distributed Control Interface (DCI) Intelligent devices.

• When expanding a CP to see attached FBMs, the System Manager hangs. The only recourse is to restart (kill and start) System Manager.

2.1

Message Manager

Message Manager is not implemented in SCP.

2.1

Fault Tolerant CPs

SCP does not support the fault tolerant features of the Fault Tolerant versions of FCP270 / ZCP270 / CP280 / FDC280 controllers. A Fault Tolerant controller is comprised of two concurrently running CPs (primary & secondary), and when a failure occurs on the primary, it switches to the secondary.

SCP simulates a Fault Tolerant controller as a single CP.

2.1

PLB Monitor with SCP

PLB Monitor is not supported with SCP.

2.1

Alarm History Display

SCP AIM* historian (FAIM) does not support Alarm History Display Feature.

3.1

Ethernet (copper) Network Interface Cards (NIC)

Software QA testing uses virtual machines with virtual NICs. It is possible that you may encounter problems when using Simulation Control Processor (SCP) with physical ethernet (copper) NIC cards. These problems are usually addressed by updating the NIC card drivers.

3.1

Fiber NIC cards

You may encounter problems when using SCP with physical fiber NIC cards, as SCP does not support fiber NIC cards. Software QA testing uses virtual machines with the use of virtual NICs. Software QA does not have fiber hardware available to stage support systems to diagnose problems.

Workaround:

Use ethernet (copper) NIC cards instead.

24.0 QF1

XREF extraction problem with FDC

The FDC app would crash when extracting XREF for DCI type I/O blocks (BIN/R, BOUT/R, IIN/R, IOUT, PAKIN/R, PAKOUT, RIN/R, ROUT/R) configured with large negative value point numbers.

Corrected:

The problem was corrected for all CP types in SCP 24.0 QF1.

24.0 QF1

Snapshot restore for Sequence block String params

The String params of certain block types (IND, DEP, EXC, STRIN, STROUT, STRING) that are 80 characters were incorrectly restored from snapshot - causing HMI display problems. The strings may also be stored incorrectly in the checkpoint.

Corrected:

The snapshot restore problem was corrected in SCP 24.0 QF1.

Create new checkpoints for CPs with 80 character strings in the above block types. Initialize CP, load controls, and save checkpoint.

Recreate or resave affected ICs as necessary.

24.0

Restoring a snapshot that contains an NaN

The SCPApp avoids restoring an NaN value from snapshot. If the SCPApp encounters an NaN value during snapshot restore, it skips the NaN and sends a Warning to the SCPEngine and Dynsim.

The Foxboro controls should prevent the calculation of NaN values; nevertheless, NaN values may occur.

One known issue is the PIDA block. The OUTL param may calculate NaN if the RTERM param value is zero.

Workaround:

Use a text editor like NotePad++ to search all snapshots for "NaN". Edit affected snapshot(s). Set PIDA.OUTL = 0.0 and PIDA.RTERM = 1.0. Save snapshot(s).

23.0

Saving a snapshot with active sequence standard block exception handler (SBX)

Simulation Control Processor (SCP) is unable to properly save/restore a snapshot with any active sequence that has an active SBX (SBXNO > 0). Snapshots saved with an SBXNO > 0 do not restore properly.

Workaround:

Clear all SBXs before you save a snapshot. Ensure that SBXNO = 0 for all sequences before you save a snapshot.

4.2 QF

FDC 280 checkpoint file

The FDC 280 image 090200500 may experience difficulty loading its checkpoint after a controls deployment. Foxboro is working on this problem.

If your FDC 280 SCPApp dies while loading its checkpoint, you should consider using an earlier version of SCP that contains an earlier version of the FDC 280 image.

4.2 QF

CP 270 image number

The CP 270 image number in the STA block mistakenly shows 920061. The CP 270 image number is actually 920062.

4.2

Checkpoint file (SCP 4.2)

For all processors, checkpoints saved in SCP 4.2 may not load properly.

Corrected:

This was corrected in SCP 4.2QF.

If you upgrade from SCP 4.2 to SCP 4.2QF because your SCPApp crashes loading a checkpoint saved in SCP 4.2, then perform the following procedure.

To start an SCPApp after upgrading to SCP 4.2QF

49. Initialize the affected SCPApp.

50. Load controls and compile sequences.

51. Save a new checkpoint.

4.1

Snapshot

Snapshots do not save all required parameters of the AIN/R block when Butterworth filtering is enabled (FLOP=2). Snapshot restore may experience a bump for this configuration.

Corrected:

This was corrected in SCP 4.2QF.

New snapshot version (snapversion) 11 saves the required AIN/R parameter(s) for all AIN/R FLOP options. Older snapshots, such as snapversion 10 and lower, may experience a bump when restoring snapshots.

4.1

Alarm Display

After an extended period of running the simulation, alarm snapshots fail to restore in the FoxView alarm display. Alarm snapshot files are still written but do not load.

Workaround:

Shutdown simulation, reboot affected FoxView computer, restart simulation.

4.1

Loading a snapshot with sequences

When restoring a snapshot saved with sequences in a previous version of SCP, a warning may appear in DYNSIM and the following error message may appear in the SCPApp window:

ERROR: IND block CMPD:BLK - Snapshot file failed validation check!

Ignoring remainder of snapshot for this block; the restored state may be invalid.

The SCPApp compares the sequence stats in the checkpoint against sequence stats that are saved in the snapshot. If a difference is detected, this error is thrown. Differences in sequence stats may be caused by actual sequence code differences or SCPApp version differences.

The SCPApp will skip the snapshot load for this sequence block. When the simulation runs, the sequence in this block will start from the beginning.

Workaround:

Run the simulation after a snapshot restore. Verify that the sequences in the affected block are running as expected. Resave snapshot.

4.1

FCP270 on Win 7 with I/A 8.8

(SCP 4.0)

When running Simulation Control Processor (SCP) 4.0 with an Application Workstation (AW) using I/A 8.8, the following error was encountered in the Integrated Control Configurator (ICC) when trying to access the FCP270:

E22 – UNABLE TO OBTAIN DATE/TIME

Workaround:

When running SCP 4.0 with Windows 7 or Server 2008, set the Launcher to run in Windows 7 Compatibility Mode. See "Running on Windows 7 or Server 2008" in the AVEVA Simulation for Foxboro Control - User Guide for the steps to set the Launcher to this mode.

4.0

Checkpoint file

If your SCP constantly repeats the message Info: requesting loading of checkpoint file from AW, then you may have a bad checkpoint file on the AW.

Workaround:

See "Appendix H" of the AVEVA Simulation for Foxboro Control – Installation Guide for the workaround procedure.

4.0

Checkpoint file (SCP 4.0)

Control Processors (CPs) shut down upon start up after you have upgraded SCP from a previous version of SCP.

Workaround:

See "Appendix H" of the AVEVA Simulation for Foxboro Control – Installation Guide for the workaround procedure.

4.0

Checkpoint file (SCP 4.0)

After upgrading your SCP version to 4.0, in the Human Machine Interface (HMI) display, linked parameters are displaying OOS (cyan) after loading CPs checkpoint files in the simulation.

Workaround 1:

Checkpoint your CP through your controls configurator.

Workaround 2:

See "Appendix H" of the AVEVA Simulation for Foxboro Control – Installation Guide for the workaround procedure.

4.0

FCP270 / ZCP270

(SCP 4.0)

For the FCP270 and ZCP270 processors, checkpoints saved prior to SCP 4.0 may not load properly.

If you upgrade to SCP 4.0 (from a previous version) and discover that an SCPApp does not start properly, then perform the following.

To start an SCPApp after upgrading to SCP 4.0

52. Initialize the affected SCPApp.

53. Load controls and compile sequences.

54. Save a new checkpoint.

    Should IC restore problems occur after an upgrade to SCP 4.0 or later, it is recommended to delete all ICs and generate new ones.

3.1 HF1

Loading a snapshot with sequences

When a snapshot (IC or backtrack) is restored and a sequence changes from inactive to active state as a result of the snapshot load, a special procedure is required. This includes sequences in the following blocks: IND, DEP, MON, EXC.

When this special procedure is required, the SCP Engine reports a warning like this:

The SCP Application console window (3CP502) reports that the snapshot must be restored twice.

Workaround:

When prompted by the message above in the SCP Application console window, use the following procedure.

To load a snapshot with sequences

55. Load the snapshot.

56. Run the simulation must be run for a few seconds.

57. Load the snapshot again.

58. Run the simulation normally.

3.1 HF1

Virtual Switch not found

The SCPApp could not find the virtual switch during startup. To correct this, ensure that each network adapter has the proper items enabled/disabled for its function.

Refer to the SCP Installation Guide.

For a normal system, check the "Post Installation Steps" \ "Various Checks on the SCP computer".

For a one-box system, check "Appendix A: Single Box Solution" \ "Post Installation Steps for Single Box Setup".

3.1 HF1

AIN/AINR/MAIN blocks with connected KSCALE or BSCALE params

SCP contains a feature called I/O Control Block Scaling to assist the project engineer. Connected (variable) KSCALE and/or BSCALE parameters interfere with this feature and produce unexpected results.

Refer to the SCP User Guide / Enhanced DYNSIM GUI / Cross Reference Database / Database Structures / I/O Control Block Scaling for more information.

Workaround:

The block with connected (variable) KSCALE / BSCALE is referred to as the problem block.

Configure a new upstream AIN/AINR/MAIN block with constant KSCALE=1 and BSCALE=0. Set IOMOPT = 1 and set SCI to that of the problem block.

Modify the problem block. Set IOMOPT = 2 and set SCI = 0.

Connect the MEAS of the problem block to the MEAS of the upstream block.

Cross-reference to the upstream block instead of the problem block.

3.1

IIN/IINR block signed to unsigned conversion

From the IIN/IINR block description in B0193AX: "As part of the block’s input processing, the raw value from the external device, in the form of signed or unsigned 8-bit, 16-bit, 24-bit, or 32-bit integer, or single-precision float, is converted to 32-bit long integer data for use by the I/A Series system".

Implemented in SCP 4.0:

In SCP, the default cross reference type IIN POINT or IINR POINT_1/POINT_2/POINT_3 handles the full range of signed 32-bit integer and float values. If the cross-reference value is using unsigned 32-bit integer, the POINT parameter must be manually changed to POINTUSG. For IINR, the POINT_1/POINT_2/POINT_3 must be manually changed to POINTUSG_1/POINTUSG_2/POINTUSG_3.

Note: The values shown in the IIN/IINR displays are shown as signed integers. For example, if you pass the full unsigned integer value 4,294,967,295 (in hex FFFF FFFF), it is displayed as -1.

3.1

SCPEngine crashes in simulation with HistorianSim engine

If a large number of Control Core Services (CCS) (I/A) points are historized in Evo, then a problem can occur with the SCPEngine if the HistorianSim engine starts first.

Workaround:

Choose a name for the HistorianSim engine that falls alphabetically after the SCPEngine. For instance, if the SCPEngine is called "SCPEng1," then name the HistorianSim engine "zHistSim1".

3.1

Defect 488056

(SCP 2.1)

SCP 2.1 software crashes when deploying multiple compounds.

The SCP280 sometimes crashes when deploying multiple compounds with extensive sequence blocks using internal subroutines. The crash resulted from SCP memory structure problems related to sequences / subroutines (particularly those using SBX).

Corrected:

This was corrected in SCP 3.1.

As a result, ICs and checkpoints saved in versions of SCP prior to 3.1 may not restore properly in SCP 3.1. ICs from previous versions of SCP should be deleted. Checkpoints from previous versions of SCP should not be used. Initialize the affected SCP, load controls, compile sequences, and save a new checkpoint. Should IC restore problems occur after an upgrade to SCP 3.1 or later, it is recommended to delete all ICs and generate new ones.

3.1

Defect 506952

(SCP 3.1)

The CP280 did not create a local checkpoint when the SCPLauncher had the Local Checkpoint Option set to "On" after deploying controls.

Corrected:

This was corrected in SCP 3.1

3.1

FAIM Options Control Panel application

The Foxboro AIM (FAIM) Options Control Panel application on Windows Server 2016 must be run as Administrator. To start, right-click on the FAIM Options object and select "Run as administrator".

If "Run as administrator" is not present in the context menu, then disable the UAC. Open the registry, navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Policies\System, set EnableLUA =0, and reboot.

You can also launch FAIM Options directly.

To launch FAIM Options directly

59. Navigate to d:\opt\faim\bin

60. Right-click on FAIMPanel.cpl, and then choose Run as administrator.

3.1

SCP application execution speed

The standalone SCP App executes at approximately real time. The SCP App may run slightly faster or slower than real time depending on the operating system, cp loading, and hardware.

Workaround:

Use Simulation Mode. Use an SCP Engine and a SimSync Engine to regulate SCP App(s) execution speed.

3.1

FDC 280 ECBs

The FDC 280 in SCP 3.1 only supports the Ethernet Primary ECB. It does not support the four Serial Primary ECBs. This produces errors during deployment of the FDC280 CP but does not affect cross-referencing.

3.0 HF2

Defect 518670

(SCP 3.0 HF2)

PLB logic processing for TOF functions overwrite other block functions output values.

Corrected:

This was corrected in SCP 3.0 HF2.

3.0

SCP Block List Rebuild

Any time a configurator (Integrated Controls Configurator [ICC]/Intelligent Automation Series Configuration Component [IACC]/Foxboro Evo) is connected to a running SCP, blocks may be reset and the block list may be rebuilt. This is true even if the user if only looking at a block configuration and no edits are made to the block. For example, if the SCP contains a PLB block, the block is reset. This causes values in the PLB code to be reset and affect the state/performance of the simulator. It is recommended that all configurators remain closed during simulator operation.

3.0

SCP connecting to simulation

Once the "SCP is simulation ready" message appears, it is ready to connect to an AVEVA Dynamic Simulation (DYNSIM) simulation through the SCPEngine. An SCP starts up running in the "Real time" mode. Until SCP is connected to a simulation, it continues running in the "Real time" mode.

Note: All of the SCPs must display the above banner "SCP is simulation ready" before starting the Dynamic Simulation (DYNSIM) simulation. The simulation only connects to SCPs that display the above banner. If an SCP displays "SCP is simulation ready" after the SCPEngine launches, that SCP is not part of the simulation. To correct the problem, shutdown the DYNSIM simulation and restart.

3.0

Input blocks using conversion function SCI51

(SCP 2.1 and greater)

AIN/AINR/MAIN/RIN/RINR conversion function SCI51 is based on raw counts between -32768 to 32767. In the CP code, the raw counts are only positive. Thus, the CP code does not calculate the engineered unit value correctly for raw counts between -32768 to -1.

Workaround:

The only workaround is to use SCI1 function in place of SCI51. Control changes must be made for the simulation.

2.1

FoxSelect

Upon a FoxSelect "Refresh All," the Graphical User Interface (GUI) displays fewer compounds than are actually loaded, and the message Checkpoint in progress appears.

Workaround:

Wait for some time (depending on the SaveAll size) and perform a "Refresh All" again to see the contents of the SCP.

2.1

STA block issue

STA block station idle time for executing the idle loop shows incorrect information (always shows as 0.0).

There is a sudden bump in Station time on freeze and start even after loading the simulation with SimSync added (for example, the station time always matches system time, not simulation time).

2.1

Checkpoint file

SCP cannot use a checkpoint saved from a physical CP. SCP can only use a checkpoint file saved by SCP. Redeploy the SCP and create a new checkpoint file for SCP.

See "Appendix H" of the AVEVA Simulation for Foxboro Control – Installation Guide for the workaround procedure.

2.1

Single User Account requirement

When a different user logs in to the SCP computer, the SCP System configuration.xml file created by a different user does not function. Each user must create a user-specific configuration file.

2.1

SCP Path Change

With SCP software release 2.0 and greater, the software is now located in the following directory: C:\Program Files (x86)\SimSci\SCP.

Modify any custom scripts to reflect the new application path.

2.1

SCP Data Path Change

The SCP data path has changed between SCP270 1.0 and SCP 2.0. The new path is now:

\Users\<USER NAME>\Documents\SIMSCI\SCP\

Please modify any custom scripts to reflect the new data path.

3.0 HF2

Simulation Control Processor Engine (SCPEngine) reports severe error

SEVERE ERROR: Timeout in calculation cycle

This error can occur when Simulation Control Processor (SCP) is running on a virtual machine (VM) with multiple snapshots – especially when a backtrack is written. Snapshot in this context refers to saved states of the virtual machine (and not to Initial Conditions [ICs]/Backtracks). When a backtrack write (or any write) occurs, the hypervisor must check each VM snapshot. This extra checking can slow the performance to the point where SCP Apps do not report back to the SCPEngine in a timely fashion.

Another symptom of this problem is that FoxView graphics show cyan during a backtrack save.

Workaround:

Delete VM snapshots. VM snapshots are not intended for long term operation.

23.0

Encryption

Dynsim 6.4 introduced an optional encryption feature. Dynsim and Dynsim Activation Manager must be installed on all computers without encryption to function with Simulation Control Processor (SCP) 23.0 or older.

23.0

Startup

Dynsim 6.4 (2023) has a defect with the wait_time feature found in the config_file.dat file. Regardless of the value entered for wait_time, Dynsim defaults to 20 seconds. If your simulation’s engines are unable to register within 20 seconds, then the simulation is unable to start.

Corrected in DYNSIM 6.4.0 HF:

Use Dynsim 6.4.0 HF instead of the DYNSIM 6.4 release.

23.0

Cross Reference Update

In Dynsim 6.4 (2023), the “Update Xref with Foxboro / Triconex I/O” tool does not open the “Cross Reference Translate and Merge” tool when you select the Merge SCP and TRISIM option.

4.2

Licensing

If Dynsim 6.3.1 is installed on a computer after Simulation Control Processor (SCP) or Trisim, the licensing and SCP or Trisim does not start. This is a problem with Dynsim, not SCP or Trisim.

Workaround:

Contact Control Emulations Support for instructions to repair the Windows Registry settings at [email protected]

Corrected in SCP 23.0

SCP 23.0 includes an updated version of licensing that corrects this problem.

4.1

Initial Condition (IC) restore problems

When loading an IC, the SimExecutive may direct the Simulation Control Processor (SCP) Engine to run before the IC load is complete. This causes a process bump or a process crash in the simulation after loading a stable IC. This symptom occurs more frequently in large simulations. Previously, the only workaround was to shutdown the simulation, close DYNSIM (ending the SimExecutive), and restart the simulation.

Corrected in DYNSIM 6.2.0 HF:

Use DYSNIM 6.2.0.9 HF instead of DYNSIM 6.2 release.

3.1

Engine Error backtrack.0

An error may appear in AVEVA Dynamic Simulation (DYNSIM) message manager stating that backtrack.0 does not exist.

This is a problem with DYNSIM 6.0 release and not Simulation Control Processor (SCP) 3.1.

Workaround:

Use DYSNIM 6.0 HF instead of DYNSIM 6.0 release.

3.1

SimSyncEngine Error

The SimSyncEngine running on a FoxView computer may report the following error.

Error: Downstream program (Connection ID 0) did NOT COMPLETE its IC Save.

If this occurs, the FoxView Alarm data did not save for the Initial Condition (IC). The Foxboro AIM (FAIM) historian tasks may also be affected. Immediately save the simulation, shutdown, and reboot affected computer.

This problem is targeted for correction in the SCP 4.0.

2.1

SCPEngine Timeout Error

Launching more than 20 Simulation Control Processors (SCPs) may result in timeout messages as shown below.

To continue launching SCPs

64. Open Task Manager, and then find the SCP App instance with the same PID number.

65. While looking at your list of SCPs in SCPLauncher, end the process.

66. Relaunch the SCP that changes from Active to Available after ending the process.

2.1

Cross Reference Issue

SCPEngine is unable to identify Cross Reference Simulation Application Programming Interface (SIMAPI) points on LX even if the controls are healthy.

Workaround:

Reload the simulation.

2.1

Shutdown of one SCP disconnects the Engine from all other SCPs

When a running SCP App is shut down, the following message appears in AVEVA Dynamic Simulation (DYNSIM) stating that the SCP is offline. All the SCP App instances connected to the SCPEngine are also disconnected. This functionality is by design.

Workaround:

Reload the DYNSIM simulation to reconnect the SCP App instances to SCPEngine.

2.1

Initial Condition (IC) Restore issues with large control set

If multiple CP280 SCP applications are loaded with full controller memory of 16MB each, then the IC Restore of any saved snapshots will take up to 90 seconds to restore completely.

2.1

Backtrack Save Performance Limitation Causes SCP Engine to go Offline

Running the simulation at faster than real time speeds with a small Backtrack Rate may cause a SEVERE ERROR from the SCP Engine and shutdown of the simulation. The following messages appear in the DYNSIM Monitor:

SEVERE ERROR: ENG: <ENGINE NAME>

SCP <SCP NAME> appears to be offline

SEVERE ERROR: ENG: <ENGINE NAME>

Due to <NUMBER OF FAILED SCPS> SCPs appearing offline. The engine is shutting down!

The save time for one CP270 SCP to complete a backtrack is about 15 seconds real time. The save time for one CP280 SCP to complete a backtrack is about 60 seconds real time. This can be configured in DYNSIM’s Backtrack and IC Configuration.

For example, if the simulation is running at faster than real time (500% real time) then the backtrack rate must be set to a minimum of 90 seconds for CP270s and about 360 seconds for CP280s. In a simulation with five CP270s, the minimum backtrack rate is 90 seconds with a maximum speed of 500%. In a simulation with five CP270s and five CP280s, the minimum backtrack rate is 360 seconds with a maximum speed of 500%.

Workaround:

Shut down and increase the backtrack rate in DYNSIM’s Backtrack and IC Configuration option, or run the simulation at a slower simulation speed.

2.1

SCP App and FoxViewTM

You may be unable to modify I/A-configurable parameters in FoxView, receiving the message Setting process variable disabled.

Workaround:

Perform a checkpoint of each Control Processor (CP) instance.

2.1

PAKIN / PAKINR Cross Referencing

The DYNSIM PACKINT utility produces output values in SIGNED LONG while SCP PAKIN block expects the input using UNSIGNED LONG.

Workaround:

Cross Reference the PAKIN/PAKINR with two entries and concentrate with an equation in DYNSIM.

2.1

Snapshot Save Performance Limitation Causes SCP Engine Warning

A warning may appear in the DYNSIM message manager and SCPEngine console window stating "<Timestamp> SCP <SCP NAME> may not have completed its last snapshot save operation".

Simultaneously, a warning message may appear in the console window of the affected SCP(s).

This situation occurs in rare conditions when an IC Save and a Backtrack Save are requested in quick succession. The issue is exacerbated when:

• The snapshot files are large

• The Backtrack Rate (time interval in seconds) is small

• The simulation is running faster than real time

  The consequence of this situation is that the later of the two snapshot requests may not include a snapshot file for every SCP in the simulation (i.e., the later snapshot may not be complete).

  Workaround:

  Increase the Backtrack Rate so that the time interval between backtracks is 600 seconds or more.

  If IC snapshots are scheduled automatically (using a scenario file, for example), ensure that IC Save and a Backtrack Save requests are not scheduled in quick succession.

  If this warning occurs when a user manually saves an IC representing an important operating condition, save a second IC to ensure completeness.

-1041

Unable to communicate with AW hosting this CP

-1066

Illegal letterbug; not 6 alphanumeric characters

-1072

Illegal pointer passed to vsw_reg()

-2000

Generic failure when opening Foxvswch driver

-2005

Digital signing not recognized. This may result from the BIOS Setting for UEFI Secure Boot. For more information, please view Secure Boot (UEFI).

-2021

Virtual Switch not found – see Known Issues

-4000

Generic failure when accessing Foxvswch driver after open

-5000

Generic failure when attempting to register with Foxvswch driver

-5001

String conversion error while creating device name

-5002

Failed to copy section address to 32-bit user space

-5003

Failed to copy section address to 64-bit user space

-5004

Failed to map view of section object

-5005

Failed to create section object - name collision

-5006

Failed to create section object - general error

-10000

Failed to load interface DLL, VSWlib.dll