iFIX 2023
iFIX 2023
No part of this publication may be reproduced in any form, or stored in a database or retrieval system, or transmitted or distributed in any
form by any means, electronic, mechanical photocopying, recording or otherwise, without the prior written permission of General Electric
Company. Information contained herein is subject to change without notice.
Trademark Notices
GE, the GE Monogram, and Predix are either registered trademarks or trademarks of General Electric Company.
Microsoft® is a registered trademark of Microsoft Corporation, in the United States and/or other countries.
We want to hear from you. If you have any comments, questions, or suggestions about our documentation, send them to the following email
address:
[email protected]
Table of Contents
Install Changes 4
Installation 8
Installing as an Administrator 8
Installing iFIX 8
Upgrade Notes 9
Upgrade Steps 10
Alarm Viewer 15
FIX Desktop 15
Classic Historian 15
Migration Tools 15
Speedstep Technology 15
IPv6 15
WorkSpace Startup 18
Close All Dialog Boxes in the WorkSpace Before Running the Report Wizard 20
Code Example: Checking for a Null Value with the iFIX RealTime ODBC Driver 24
Software Requirements 44
Index 49
Welcome to the newest version of iFIX! The features of iFIX 2023 include:
l The option to select which protocol to use for SCADA Synchronization communications for
Enhanced Failover: TCP or UDP. In previous versions, only UDP was available. TCP is a reliable, con-
nection-oriented protocol that handles message acknowledgement, retries, and so on. TCP can be
used to cover longer distances between Failover pairs, without a dedicated network, and with
fewer failures.
l New iFIX installations will default to TCP, while upgrades or use of an existing, pre-iFIX 2023 Sys-
tem Configuration Utility (SCU) file will continue to use UDP by default. Protocol selection is made
in the SCU’s SCADA Configuration dialog. It takes longer for SCADA Sync to initially get to an Act-
ive/Standby state with TCP than UDP. While TCP offers significant advantages, it does introduce
overhead as opposed to UDP, so it can be slower as a protocol. If speed is critical, we still provide
UDP support with its more stringent failover setup requirements.
l When using TCP for Enhanced Failover, the Primary and Secondary SCADA computers do not need
to be located near each other. When using UDP, the requirement to locate these computers in the
same location/room still applies.
l For Enhanced Failover, Gigabit-Ethernet cards (or better) are required for Data Sync Transport
communication. When using UDP, a dedicated card is required for Data Sync Transport com-
munication. When using TCP, one card can be used for both iFIX and Data Sync Transport
For more information, see the Enhanced Failover section of the iFIX documentation.
l Model updates. The iFIX model now allows you to reference parent substitutions, specify different
variable types, and include or exclude contained types by a template within an iFIX Model Type.
l New Project Configuration capabilities. You can now manage multiple iFIX Projects through Con-
figuration Hub and start or stop them as needed. Multiple iFIX nodes SCU and Security Settings
can be updated from one central Configuration Hub from any browser.
l Project Deployment capabilities. Project Deployment provides the ability to deploy (copy) key HMI
components and/or settings between iFIX SCADA or iClient (View) nodes. You now have the ability
to transfer key HMI components (including pictures, tag groups, color tables, and so on) quickly and
easily from one node to multiple other nodes. This eliminates the need to connect to each node
individually to make local updates, or to employ shared folders as a means of distribution.
l Proficy Authentication (UAA) 2023 provides identity-based security for Proficy-based applications
and APIs. It supports open standards for authentication and authorization, including Oauth2.
l Support for Operations Hub 2023. Operations Hub 2023 includes out-of-the-box high-per-
formance HMI graphics. It also includes an SVG graphics editor for creating new custom HMI graph-
ics that you can access from the Operation Hub plugin in Configuration Hub. HMI graphics are
accessible only with the latest version of Operations Hub layout.
l Operations Hub 2023 also supports a new Webspace widget for iFIX and CIMPLICITY that you can
use to view your HMI screens from the Operations Hub plugin in Configuration Hub.
l Support for the MQTT Protocol in Configuration Hub.
When upgrading, be aware of the following new prerequisites for using Configuration Hub 2023:
l To publish a Model when using iFIX 2023 with Operations Hub, you must use Operations Hub 2023.
Operations Hub 2023 must also be registered to same the Proficy Authentication to which iFIX is
registered.
l iFIX entities like the database name, tag names, alarm areas, model types, and model instances
must be unique. Ensure you use unique names when creating these items.
l When upgrading from iFIX 6.5 or 2022 to iFIX 2023, clear your browser cache and then re-register
iFIX with Configuration Hub for the new Project Settings to appear (click the Register iFIX Plugin
option on the Windows desktop, or from the iFIX Workspace on the Applications tab). Be aware
that iFIX Security must be enabled to access Configuration Hub. For steps, refer to iFIX Plugin
Registration.
l When multiple iFIX and Historian plugins are registered to Configuration Hub, they should all use
the same Proficy Authentication (UAA) Server Name. If Configuration Hub or Proficy Authentic-
ation Server are in a domain system, then a Fully Qualified Domain Name (FQDN) name should be
used for the Server Name.
l For Configuration Hub, it is recommended to use a display setting at 1920 x 1080 or greater with
scaling set to 100%.
l iFIX 2023 is compatible with Configuration Hub 2022 with Proficy Authentication 2022. However,
be aware that the deploy functionality will only work with iFIX 2023 nodes. iFIX 2022 nodes will
not be displayed in the list of target nodes when deploying.
l iFIX 2022 is compatible with Configuration Hub 2023 with Proficy Authentication 2023.
l Be aware that the scada.fix.shared.APPLICATION_DESIGNER group is not available by default
when you upgrade from iFIX 6.1 or 6.5. You must manually create the group with the required iFIX
application features, or update your existing groups to include the following iFIX application fea-
tures (if you want users in these groups to have access to and use Configuration Hub):
For more information on Configuration Hub, click the Help button from the Configuration Hub application.
Or, open the Configuration Hub content from the GE Documentation web page.
Install Changes
The new integrated installer helps you install iFIX, Historian, IGS, Configuration Hub, Licensing, Oper-
ations Hub, and other Proficy related applications quickly and efficiently. The 2023 integrated installer
includes Operations Hub and all the new 2023 components. The integrated product installer streamlines
the deployment experience for iFIX, along with the other products it is often used with. The individual iFIX
install is no longer provided as a single download; it is included on the Integrated Installer with everything
you need to set up your SCADA system.
You can run the integrated installer from a command line or programmatically. A response file, SilentIn-
stallResponseFile.json, is saved to the install directory with the settings from your install. Use the fol-
lowing command line to run it:
where D:\ is the ISO mounted drive (the drive where the integrated installer is located).
IMPORTANT: If enabling access controls when installing iFIX, do not delete the user group created/used
by the iFIX installer (to apply ACLs) before you uninstall the iFIX product. Instead, uninstall iFIX first, and
then you can optionally remove this Windows group. If you accidentally delete this group, run the Con-
figureWizard.exe tool, which is found in the iFIX install folder (by default: C:\Program Files (x86)\Profi-
cy\iFIX). Restart the machine and then restart iFIX. Confirm that you can open the iFIX WorkSpace and
the Database Manager. After that, you will be able to uninstall iFIX if necessary.
For the full install steps, refer to the "Installing the iFIX Software" topic in the Getting Started guide.
iFIX 2023 can now leverage the MQTT Client application to handle and support MQTT data received from
the Client applications. Through MQTT Clients, you can access the published data from various devices
such as the sensors, units, and other PLCs. The data received by the MQTT Client is translated to OPC UA
data. The translated data is then used by the SCADA products to visualize and monitor the data. This
allows you to leverage the advantages of both MQTT and OPC UA protocols.
The MQTT Client establishes a connection with the MQTT broker and subscribes to the data that is pub-
lished on various topics. The published data received through the MQTT Client will then be translated into
the OPC UA data. The OPC UA clients in products such as iFIX and Operations Hub can connect to the
OPC UA server and subscribe to the data.
For more information on MQTT, see the Configuration Hub online help.
l Support for new Microsoft Windows versions. Webspace now supports Microsoft® Windows® 11
and Microsoft® Windows® Server 2022. It also supports Microsoft® Windows® 10 (Build 21H2 or
higher).
l The latest version of Webspace also has its own web server and no longer requires IIS or Apache.
l Operations Hub 2023 also supports a new Webspace widget for iFIX and CIMPLICITY that you can
use to view your HMI screens from the Operations Hub plugin in Configuration Hub.
For a complete list of all supported operating systems, refer to the System Requirements tab.
l Storage of critical process data that is smaller and faster than using a relational database.
l Tight integration with CIMPLICITY and iFIX, allowing you to configure your tags all in one place.
l Native Proficy Historian for Cloud offering.
For more details on all the new features provided with Historian 2023, see the Historian 2023 doc-
umentation and the Cloud Historian documentation.
l Enable the iFIX Screen directly from the iFIX SCU's Local Startup options. You can configure more
by clicking the Settings option the Local Startup Definition dialog box. No need to configure it from
the operating system settings, outside of iFIX, like in previous releases.
l You can now configure a Wait time right from the SCU too. The wait time is how long the user ses-
sion that FIX.EXE runs in is idle before the screen saver is activated. You can enter a wait time of 1
to 9999 minutes.
l The iFIX Screen Saver is now supported in iClientTS and WebSpace sessions.
l iFIX must be restarted if you enable or disable the iFIX screen saver or if you change the screen
saver wait time. It does not need to be restarted if you change the screen saver options.
For upgraders, be aware that you can still continue to use the old way of enabling the iFIX screen saver
via the Windows Display settings and not via the iFIX SCU, but there are limitations. For instance, one lim-
itation could be that the iFIX Screen Saver will not work for Remote Desktop sessions. It is recommended
that you use the new, simpler way to configure the iFIX Screen Saver in the SCU.
For more information on the iFIX Screen Saver, refer to the iFIX Screen Saver topic in the Configuring
Security Features e-book.
If you want to enable Access Controls or change your current settings, you can do so by using the Con-
figureWizard.exe provided with iFIX. The ConfigureWizard.exe can be found on the Start menu in the iFIX
folder, and then selecting the Setup Access Controls option. You can also access it from the iFIX install
folder; by default, this location is: C:\Program Files (x86)\Proficy\iFIX\ConfigureWizard.exe
For more information on Access Controls, refer to the Access Controls in iFIX topic in the iFIX Getting
Started guide.
l iFIX Productivity Tools from Catapult (included on the iFIX install media). Includes updates to sup-
port the latest version of iFIX. The Productivity Tools are supported in English only.
l IGS 7.612. The latest IGS has three new premium drivers to meet your connectivity needs: IEC
61850, the DNP suite, and MQTT are now included.
l Dream Report 2020 for Proficy.
l Win911 version 4.20.10.
For a complete list of products and versions tested to work with iFIX 2023, go to the System Require-
ments tab and scroll to the Compatibility with Other GE Products section.
If this is your first time using the iFIX product, try launching the Sample System from your desktop icon of
the same name. There is a specific chapter in the help documentation, under the heading Sample Sys-
tem, which will instruct you on how to interact with the Sample System in run mode. When configuring a
new iFIX system with Configuration Hub, and you want to use the Sample System, make sure you start
iFIX first before starting the Sample System.
You can also run iFIX in Demo mode. In Demo mode, you can run iFIX applications for 2 hours. To start in
Demo mode, start iFIX from command line using the parameter, like this:
Launch.exe /t
NOTE: You can run Sample System with an iFIX license by removing the /D switch from the Sample System shortcut.
However, be aware that you need to have an appropriate license installed for the Sample System to be fully functional.
For a general overview of iFIX and the WorkSpace, refer to the Understanding iFIX electronic book.
For an overview of how to configure your iFIX system, refer to the Setting up the Environment electronic
book.
Installation
Installing as an Administrator
You must install iFIX with a local Windows user account with administrator rights. See your Windows
manuals or online Help for information on creating this account.
Installing iFIX
Without an iFIX license, you can run iFIX applications for 2 hours in Demo mode.
NOTE: When configured for WebSpace, none of the iFIX SCUs on WebSpace Server should be configured to start iFIX as
service, as this is a unsupported configuration.
Upgrade Notes
Before you upgrade the iFIX product installed on your computer, make sure you shut down all GE applic-
ations. It is important that no GE products are running when you run the iFIX installation program.
If you plan to uninstall iFIX before reinstalling, unregister the iFIX plugin for Configuration Hub before unin-
stalling iFIX.
IMPORTANT: Direct upgrades from iFIX 3.5 to the latest version of iFIX are not supported. To upgrade iFIX in this case,
upgrade to 5.8 first and then upgrade to the latest version of iFIX. Search the iFIX Upgrade Guide for "In-place Upgrades
vs. New Systems" for a table describing the upgrade paths.
NOTE: iFIX WebSpace must be uninstalled before/after the upgrade to iFIX 2023. Instead of iFIX WebSpace, WebSpace
5.0 needs to be installed and configured to work with iFIX.
IMPORTANT: If you are upgrading from a previous version of iFIX with failover enabled, and you want to use the
Enhanced Failover feature in iFIX 5.0 or greater, there are a number of issues that you must be aware of. For detailed
information and steps describing how to upgrade your failover system, see the Enhanced Failover and Upgrading" sec-
tion on the New Features tab.
Save copies of your existing .INI files with your application preferences and any custom files you create;
customized files may be overwritten during an upgrade. As such, you may need to integrate your custom
changes into the newer versions of these files after you upgrade.
Back up your existing iFIX projects. This includes the files in your LOCAL, Config Files Backup, PIC, and PDB
folders.
It is also recommended that you create a backup copy of your Alarm ODBC configuration file(s).
Export a report of your system configuration (SCU), for reference. (In the SCU, on the File menu, click
Report.)
Export a report of your security configuration, for reference. (In the Security Configuration application, on
the File menu, click Export.)
If you have an application created by an Integration Toolkit, Database Dynamo Toolkit, or System Exten-
sion Toolkit from iFIX 2.5 or earlier, and you want to use this application with iFIX 2023, do not uninstall
iFIX. You must install iFIX 2023 over your existing iFIX configuration. Your toolkit application will not run if
you uninstall your previous version of iFIX.
Be sure to obtain any toolkit updates that you need, prior to installing iFIX.
CAUTION: If you choose to integrate Historian with iFIX, make sure that your database tags have unique names. If
both your iFIX and Historian databases have the same tag name, when you import an iFIX tag into the Historian data-
If you plan to use Configuration Hub with iFIX, before you upgrade iFIX, delete the old OPC UA Con-
figuration certificate (iFIX_OpcuaConfigRoot.crt) from the Program Files (x86)\GE\iFIX\LOCAL\iFIX_
OpcuaConfigService\pki folder, and then upgrade to the latest version of iFIX.
IMPORTANT: If you forget to delete the OPC UA certificate before upgrading, you will need to follow the steps in this
topic in order to trust the certificate again after the upgrade.
After upgrading iFIX and Configuration Hub, you will need to add the APPLICATION_DESIGNER group in
iFIX Security Configuration, and then export it to Proficy Authentication. The group name from iFIX 6.5
contained a space character, which is not supported in the current version of Configuration Hub and is
why the group name is not migrated. Before you export the group, be sure that the APPLICATION_
DESIGNER group contain the following iFIX application features: Database Block Add-Delete, Database
Manager, Database Reload, Database Save, Enable Task Switching, OPC UA Confiugration Tool, Runtime
Visual Basic Editor Access, WorkSpace Configure, WorkSpace Runtime, and WorkSpace Runtime Exit.
After upgrading iFIX and Configuration Hub, you will need to manually add two missing privileges to the
ch_admin user. In the Navigation panel from Configuration Hub, select Proficy Authentication. From the
Users list, select the ch_admin user and add the following items to its group membership: scada.fix_
shared.IFIX_PROFICY_AUTH_ADMIN and scada.fix.shared_APPLICATION_DESIGNER.
Upgrade Steps
To upgrade to the latest version of iFIX, perform the following steps:
1. Confirm that you backed up all the applicable files. Refer to the Before You Upgrade or Reinstall...
section above for more details.
2. Shut down any GE applications or Proficy services that are running. For instance, if you have His-
torian Collectors configured to start when you start Windows, use the Services window to shut
them down.
3. Run the iFIX product install. A message box appears asking you if you want to upgrade your sys-
tem.
4. Click Yes to continue.
5. Follow the instructions on your screen.
You can use both the Logical and Enhanced Coordinate Systems with iFIX. For example, you can edit a leg-
acy picture before you upgrade it. By default, the Enhanced Coordinate System is enabled for new picture
creation. For more information on this expert and on coordinate systems, refer to the Creating Pictures
e-book
NOTE: Be aware that pictures with Enhanced Charts containing tag groups will display a message on upgrade.
However, pictures with Historical datalinks and Historical animations with tag groups will not.
Due to the design of the VisiconX objects in iFIX 5.0 and greater, it is recommended that you manually
replace your older VisiconX objects with the newer versions (if you are upgrading from a version of iFIX
prior to iFIX 5.0).
When you upgrade your database, the high and low engineering units (EGU) fields are converted from
single precision to double precision floats. This means the degree of accuracy (the Epsilon value) changes
from +/_0.00000012 to +/_0.00000000000000022. If you are using extreme ranges (very large or very low
values) for your EGU limits, you may possibly experience issues after an upgrade. To resolve these issues,
open the Database Manager, export your database and then re-import it. This procedure resets the block
values.
If you configured Database Dynamos, also known as loadable blocks, or other custom programs to run as
part of iFIX startup, you should compare the new FIX.INI file in the Local folder against the FIX.INI file
stored in the Config Files Backup folder. If you find any changes between the two files, add the necessary
lines to the FIX.INI stored in the Local path.
Additionally, you should restore other .INI files as necessary, using the same process.
The GE Digital web site contains updated versions of the Database Dynamos supplied by GE Digital. To
obtain updated version of other dynamos, contact the vendor of that dynamo. To obtain the current ver-
sion of the Database Dynamo Toolkit, contact your local iFIX sales representative.
If a picture created with an earlier version of iFIX contains a VisiconX Data Control, and also contains
VBA 5.5 scripts added for the VisiconX Data Control's ErrorOccurred event or ExecuteComplete event,
when the picture is opened in iFIX 2023, it will generate a compiler error indicating an invalid character '_
'.
This occurs because the ErrObject in VBA 5.5 is declared as type "VBA._ErrObject", and in VBA 6.5, it is
declared simply as "ErrObject".
To correct the compiler problem and make the scripts function correctly, make the following changes to
the event declarations:
End Sub
End Sub
End Sub
For example, when you have the WorkSpace in Ribbon view (the default), the caption bar with the Min-
imize icon is displayed off screen. It's there, but you cannot view it. >My-T-Soft allows you to customize
where the Minimize button positions itself through the MYTSOFT.ini file located in the iFIX install folder.
By changing the ButtonOffsetY=0 setting to a positive number, you can move the button down a specified
number of pixels, allowing the Minimize button and caption bar to show in full screen, when in ribbon
view. After this value is configured, the My-T-Soft keyboard will always display in that specified offset pos-
ition.
1. Open Windows Explorer by clicking the Start button, and pointing to Programs, Accessories, and
then Windows Explorer.
2. Locate the folder to which you installed iFIX. (For example: C:\Program Files (x86)\Proficy\Proficy
iFIX.
3. Right-click the iFIX folder and select Properties from the right-click menu. The Properties dialog
box appears.
4. Click the Security tab.
5. Select the Users group in the top half of the dialog box.
6. Select the Allow check box for the Modify, Read & Execute, List Folder Contents, Read, and Write
permissions in the bottom half of the dialog box.
7. Click OK.
l An iFIX client node, installed with iFIX version 5.5 or later, is fully compatible with iFIX version 5.9
Enhanced Failover SCADA nodes.
l An iFIX client node, installed with iFIX version 5.1 and updated with the iFix51_Pulse10_Work-
space_019 SIM (Software Improvement Module), is fully compatible with iFIX version 5.9 Enhanced
Failover SCADA nodes.
l An iFIX client node, installed with iFIX version 5.1 and is not updated with the iFix51_Pulse10_
Workspace_019 SIM is not compatible with iFIX version 5.9 Enhanced Failover SCADA nodes.
l An iFIX client node, installed with iFIX version 5.0 or earlier, is not compatible with iFIX version 5.9
Enhanced Failover SCADA nodes.
IMPORTANT: In an Enhanced Failover pair, both SCADA nodes must have the same iFIX version installed
with all SIMs.
If you want to archive these Microsoft applications along with your project with Backup and Restore or
Change Management, the Excel and Word documents must be saved to "App" sub-folder in the
WorkSpace system tree.
FIX Desktop
iFIX no longer supports FIX Desktop.
Classic Historian
As of 6.1, iFIX no longer supports Classic Historian and it has been removed from the program. Updating
to iFIX 2023 (or later) from a previous version will remove the Classic Historian binaries. Before updating,
make sure you have a plan to migrate your historical data to Historian Essentials, or some other per-
manent storage.
Migration Tools
iFIX 2023 does not support the FIX32 migration tools. If an .ODF files exists, that you want to convert, you
must use an older version of iFIX to upgrade screens first before opening the picture in iFIX 2023.
Speedstep Technology
SpeedStep® technology is not supported and must not be enabled.
IPv6
FIX does not make use of any IPv6 functionality.
If you disable IPv6 to use WebSpace, make sure that your local HOSTS file does not contain any IPv6 ref-
erences. For example, remove the "::1 localhost" lines from the HOSTS file, and replace them a line that
references the IP address and the local host name (if necessary).
If you want to run the OPC Client driver on a specified operating system, be sure to check with the vendor
of your OPC Server software to confirm that your OPC Server supports the operating system you want to
run it on.
It is recommended that you install the latest OPC Core Components from the Downloads section of the
OPC Foundation web site: http://www.opcfoundation.org. The latest OPC Core components are designed
for use on a 64-bit OS.
To fix this issue, display hidden files in Explorer, delete the icon cache file, and restart Windows. This
action restores the icon cache.
WorkSpace Startup
After starting the operating system, the first time the WorkSpace is started, you may notice that it takes
longer for the WorkSpace to start up. Subsequent WorkSpace startups will not experience the delay. The
delay is related to the number of pictures in the picture folder, so smaller projects may not experience
the delay.
The report generation remains halted until you click on the Cross Reference Tool. This causes the fol-
lowing message to appear: "An action cannot be completed because a component (iFIX WorkSpace (Con-
figure) is not responding. Choose "Switch To" to activate the component and correct the problem."
Close All Dialog Boxes in the WorkSpace Before Running the Report Wizard
If you try use the Cross Reference Tool Report Wizard when certain dialog boxes are open in the
WorkSpace, such as the User Preferences or the Find and Replace dialog boxes, an error may occur.
For instance, the following message may display: "The Cross Reference application could not export VBA
script files. Your ExpertGlobal may be corrupted. Cross Reference is exiting."
Click OK to acknowledge this message and allow the Cross Reference application to exit. To prevent this
message from occurring in the first place, close all dialog boxes in the WorkSpace before you run the
Report Wizard in the Cross Reference Tool.
When you switch to the WorkSpace, this error appears: "Error number -2147211306. The file you are
attempting to open has been renamed outside the WorkSpace. Please make sure you have write access
to the file and try again."
Once you clear these messages, run the report again. Additionally, you can also use either of these tech-
niques to resolve this issue:
Remove the read-only attribute – Identify all files being searched for that have a read-only attribute.
Remove the read-only attribute.
Upgrade the file – Upgrade the file if you choose to leave the read-only attribute. To upgrade the file,
remove the read-only attribute on the file, open the file in the WorkSpace configuration mode, and close
the file. The file is automatically upgraded. You then have to add the read-only attribute to the file.
If security is enabled for Historian, and you do not have the necessary security group memberships, you
will not be able to use Mission Control to start or stop Historian collectors. To give the iFIX WorkSpace
and Mission Control access to the Historian collectors, configure a user name and password in one of the
following Historian dialog boxes:
l Configure the Historian Server(s) Access this dialog box by clicking Configure Historian Server on
the Historian toolbar.
l Historian Administrator Login Access this dialog box by opening the Historian Administrator and
clicking Main.
Please refer to the following KB article, article ID:15129, for authentication information for WebSpace
and Historian: http://support.ge-ip.com/support/index?page=kbchannel&id=S:KB15129&actp=search
The iFIX Scheduler and charts can use Historian data that supports Daylight Savings Time. However,
before allowing automatic Daylight Saving Time to be used in a production environment, you should test
your application under each of the following scenarios for proper behavior:
Use the Advanced tab of the PowerTool dialog box to set the Auto Start for each driver. If you do not use
the /A parameter and:
l the Auto Start setting in the PowerTool is set to On, 7.x driver starts automatically.
l the Auto Start setting in the PowerTool is set to Off, 7.x driver does not start automatically.
l ABR
l GE9
l M32
l MBE
l OPC
l SI5
l SL4
l SI7
Refer to the GlobalCare web site for software downloads for I/O driver updates:
https://digitalsupport.ge.com
For more information, refer to the Microsoft Knowledge Base article 318597.
To eliminate this error, you need to make the following registry change for the OPC data source.
For example, if your third-party OPC server is installed as SOMEOPCSERVER, then you would add the
string value "ValidateItemsNotSupported" to \HKEY_CLASSES_
ROOT\FIX32\DataSources\SOMEOPCSERVER key, setting the string value to "true." This change verifies
that data items on OPC Servers not implementing the ValidateItems call can be read.
l Refrain from using punctuation marks, pound sign (#), and VBA reserved words within VBA file
names.
l Avoid generating a script within a script, that is currently executing. This causes unpredictable res-
ults.
l Do not use the WM_CLOSE SendMessage to close a user form; the object does not get destroyed
properly. If you must close a form with a script, use the WM_DESTROY SendMessage.
l Avoid referencing the Intellution iFIX Find and Replace Mechanism v1.0 Type Library in your pro-
ject. It causes an error when you compile your script.
l Be aware that a script based on an object's event should not call the DestroyObject method on
the parent of the same object. Doing so causes unpredictable results.
l If you are using any of the iFIX subroutines to write data back to the database, use the F_CV field
as the data link. Using the A_CV field may cause unpredictable results.
l Do not use the DblClick event when you configure a Data link for "In-Place" data entry. If you do,
the DblClick event does not execute.
l Do not access class modules that are declared as PRIVATE in an out of process environment, such
as user.fxg, expert globals, or any Global pages. This is not allowed.
l Be aware that when you change a source tag in iFIX, an automation error displays if you do not
allow iFIX enough time to establish the new connection before you read the InputValue property.
The wait time depends on the scan time of the event object source tag.
l If you set a tag with a static value as the source tag twice in a row, you will cause an automation
error.
For more information on using VBA in your iFIX projects, look up "summaries" or "scripting, in iFIX" in the
online help Index.
To avoid this problem, replace the second line in the above sample script with the following line:
Dim iApp As Object
For example, say UserA installs iFIX to C:\LocationA, and then both UserA and UserB make use of iFIX. If
UserA uninstalls iFIX and then reinstalls iFIX to another location, say D:\LocationB, without deleting
C:\LocationA, UserB may experience issues. Although UserA will be able to use iFIX in its new location
without any problems, UserB will see several error messages if he tries to launch iFIX or the SCU, since
his registry paths still point to C:\LocationA.
As a workaround, open the Windows Registry and delete the HKEY_USERS\<USER'S ID>\Soft-
ware\Proficy\iFIX\ProjectPaths key which contains the old paths. For example, deleting the HKEY_
USERS\S-1-5-21-3882306234-4042192530-3641380709-1028\Software\Proficy\Proficy iFIX\Pro-
jectPaths key would alleviate this issue for a user with an ID of S-1-5-21-3882306234-4042192530-
3641380709-1028. After updating the Registry, be sure to restart iFIX.
If you have iFIX with Productivity Tools installed and you upgrade from to
DE124575 Upgrade iFIX 2023, manually update the FIX.INI to include this entry at the end of
the [SCADA] section: RUN=%IFIX_CONFIG_SERVICE.EXE run -config ifix_
config_service.json. Restart iFIX after you save your changes.
OPC UA Clients Do Not Discover OPC UA Server on VMWare Image
When running iFIX with its OPC UA Server enabled on a computer that has
DE118716 OPC UA VMWare installed, you may find that you cannot discover the OPC UA
Server from clients on the local machine. In this case, you may repeatedly
see the following error in the iFixUaServer.log file: Error: "Registration with
Discovery Server failed." This occurs because the VMWare virtual network
adapter fails to respond during Discovery Server registration, which
causes the entire registration operation to time out.
In order to work around this, you can disable the VMWare network
adapter (if it is not used) in Control Panel. Otherwise, you will need to
manually enter the endpoint URL of the OPC UA Server into client applic-
ations, since they cannot find the server by discovery. Note that this issue
only affects discovery of the iFIX OPC UA Server and has no impact on fur-
ther connectivity or functionality of the iFIX OPC UA Server.
OPC Core Components subinstall displays a request to install a VC 2013
Redistributable (version 12.0.30501)
DE122938 Install This error occurs only on a fresh install. It occurs because the target sys-
tem already has the Microsoft VC++ 2013 Redistributable Update 5
(12.0.40660) installed. Acknowledge the message and continue. The install
will run properly despite the message.
Cannot open OPC UA Client Driver Configuration Tool When the Windows
Firewall is Enabled
OPC UA Client
DE120941 Add port 9444 to the Windows firewall exception list, along with any other
Driver
port associated with this driver that you want to include, such as ports
4855, 4856, and 4857.
iFIX UA client will not fully work with OPC UA Aggregators that change
iFIX OPC UA Cli- server namespaces dynamically
TA626596
ent
This is not supported in iFIX 2023.
Discover and Auto Configure Does not Support Long Tags Names or OPC
Discover and UA
TA592883
Auto Configure
These items are not supported in iFIX 2023.
Size of HPLinearGauges Dynamo Not Maintained After Upgrade
This is a known issue in iFIX 2023. When the HPLinearGauge Dynamo in pic-
DE114780 WorkSpace ture is upgraded with the iFIX 2023 Master Dynamo, then the updated
Dynamo will be reduced in length. There is no workaround for this issue
except to manually resize the upgraded Dynamo.
iFIX Collector Fails When Browsing iFIX Tags in the Historian Administrator
If you try to browse tags, for instance from the Add Multiple Tags from Col-
lector dialog box in the Historian Administrator, the iFIX Collector will fail.
Historian Integ-
DE92547 Be aware that you can still add tags, up to 199 characters long, for col-
ration
lection using FixToHist.exe.
This is a known issue with the Historian Collector in Historian 7.0 and has
been addressed in newer versions.
Bad WebHMI Server Name Entered Into User Preferences or Web HMI Pub-
DE91265 WorkSpace lish Screen Causes WorkSpace to Be Unresponsive
This is a known issue in iFIX 2023 and only occurs if a you enter a bad
server name.
OPC UA Server Does Not Start
If you have iFIX with Productivity Tools installed and you upgrade to iFIX
DE90938 Upgrade 2023, then the FIX.INI file does not contain an entry for the iFIX OPC UA
Server. As a workaround, manually update the FIX.INI to include this entry
at the end of the [SCADA] section: RUN=%IFIXUASERVER.EXE. Restart iFIX
after you save your changes.
HTC Tab is not Working With Historian Installed
DE90685 Mission Control In iFIX 2023, Historical Collector actions are no longer supported from the
iFIX Mission control application, mission.exe. Please use the Historian
Administrator UI instead.
Alarm Shelving Related Fields Are Not Shown in the Text Compare Report
Change Man-
DE89991 Alarm Shelving related fields are not shown in the Text Compare Report in
agement
the Change Management History window.
Alarm Shelving Status Incorrect When Alarms Are Sent Over AAM
DE84751 Alarm Shelving When using the Auto Alarm Manager (AAM) with Alarm Shelving, be aware
that the Alarm Shelving Status is incorrect when alarms are sent via AAM.
Altered Table Failing for Microsoft Access Database Due to Long Tag
Names and Descriptions
After upgrading to iFIX 2023, when using Microsoft Access to log Alarms
using ODBC, an error occurs. To use iFIX after an upgrade with Microsoft
Access requires a manual update to the Registry and an update of the
Microsoft Access database in Design View. The ALM_TAGNAME and ALM_
TAGDESC (if it exists) rows needs to be formatted as a LONGTEXT (MEMO)
field.
1. In the Windows Registry, make the following entries for the MaxLock-
sLimit key: REG_DWORD and 0x00030d40 (200000). To find the MaxLock-
DE87524 Upgrade sLimit key, look to the Microsoft Office version-specific Registry entry
under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.
5. Select the ALM_TAGNAME row, Data Type column, and then change
Text to Memo.
6. Repeat the previous step with the ALM_TAGDESC row, if it exists in the
table.
When using VisiconX, be aware that you must configure your environment
variables correctly for Oracle. If you select the Microsoft OLE DB Provider
for ODBC Drivers as your data source, when you try to select an Oracle
table, you will experience an error. On the Oracle Client machine where
iFIX is installed, set the ORACLE_HOME environment variable to point to
the Oracle Admin Client installation directory.
For example:
4. Add the ORACLE_HOME variable to the New System Variable box, then
click OK. For example: ORACLE_HOME-
E=C:\app\Administrator\product\12.1.0\client_1
5. Select the PATH variable in the System Variables panel, and click Edit.
6. In the Edit System Variable box, add the path to ORACLE_HOME at the
start of the PATH variable: %ORACLE_HOME%\bin
For the CTR, GAB, ITM, PAR, and P12 blocks, an upgrade to iFIX 2023 does
Database Man- not fix issues with the Alarm Area 2 and Alarm Area 3 ordering. As a work-
DE85273 around, you need to export the database to a .CSV file, edit the Alarm
ager
Area 2 and Alarm Area 3 values, and then reimport the database back into
iFIX 2023 to fix the designated Alarm Areas. If the blocks are created using
iFIX 2023, there is no issue with alarm areas.
iFIX-SOA Ser- Tags Created After Connection Established to the SOA Server Appear Miss-
DE86292
vice Provider ing When Browsing Tag Properties on SOA Node
The workaround is to restart iFIX each time you add a new block type to
the existing iFIX database.
Identifier Too Long Error for Long Tag Name on Script Behind Event
DE71528 WorkSpace Microsoft Visual Basic limits character identifiers to a maximum of 255
characters.
Recipe Report Limits Tag Identifier to 100 Characters
DE75993 Recipes
This is a known limitation in iFIX 2023.
Quick Trend and Tag Control Panel Have Tag Length Limitations
DE81968 WorkSpace Tag Control Panel and Quick Trend Screens are limited to tag names of 234
characters.
Alarm Shelving and OPC UA Configuration Tool Security Features Not
Added to iFIX Administrative User on Upgrade
DE82453 Upgrade This is as designed for security purposes. After an upgrade, if you want to
update your administrative groups to include the new security features,
you will need to add them manually.
ToolTip Does Not Display Full 256 Character Tag Length in Command
Script Wizard for Schedules
DE79939 WorkSpace
Tooltip does not show full tag length in this case. This is a known software
limitation.
DE82077 WorkSpace Tag Status Screens Have Tag Length Limitations
There are limitations on screen that will not allow the full tag name to be
displayed in Tag Status pictures. Even with the use of tooltips, you are
restricted to 160 characters.
New Document Option Is Disabled in the System tree for Microsoft Word
and Excel Files
As a workaround, you can create the registry keys as described in the fol-
lowing articles. Restart the iFIX WorkSpace after doing making your
changes.
DE69641 WorkSpace
https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365ad-
min/why-docobject-registry-keys-with-a-
value-of-16-are/24cd9c98-46a9-4c10-8ca1-cb3933bd7817
https://community.qlik.com/docs/DOC-14030
Tag Lookup Takes Longer Than Expected
DE80338 WorkSpace When browsing tags in the Expression Editor on a view node (iClient), it
may take 50% longer to perform the initial tag lookup.
Long Tag Name Not Readable or Shrinks in Enhanced Charts
Enhanced
DE66431 After inserting a Line Chart or XY Chart, a long tag name is not readable or
Charts
shrinks on the chart display.
iFIX Charts (with Historian data) Not Working on a System with Historian
Historian Integ- 7.0 Mirroring when Primary Historian Server is Unavailable
N/A
ration
iFIX 2023 currently does not support Historian 7.0 mirrored systems.
Sometimes the Values Displayed on the HPTanksAnim and HPLin-
earGauges Dynamos Are Cut Off.
DE17435 Dynamos Try saving the picture before switching to run mode or run the WorkSpace
in Full Screen mode. Disabling Zoom to Fit may also display the values cor-
rectly.
When Shape objects are aligned to each other with the Edge Width prop-
erty set to 0, the objects display a white line within GE Web HMI browser
client.
When a picture is created in iFIX with Shape objects that are aligned to
each other and the Edge Width property is set to 0, the objects in the
Web HMI
DE14743 exported picture display a white line when viewed within GE Web HMI.
Export
Workaround: If the Edge Width property is 0, set the Edge Style property to
“EdgeStyleNone” in the object’s property window, or set Edge Style to “No
Edge” via the object’s Right Mouse Menu option. Confirm that the objects
look correct in iFIX Configure mode. Then, save and export the picture for
Web HMI.
Some Anti-Aliased Lines that are Near Horizontal Appear Fuzzy
DE29895 WorkSpace With SmoothShapes (anti-aliasing) enabled, edge lines of some objects can
appear fuzzy when they are at certain angles... such as with line objects
when they are in a near-to-horizontal position.
Some Text Objects Draw Lighter than Normal
Text objects with a font size of 13 or smaller will draw without anti-ali-
asing regardless of the SmoothShapes setting in the picture. Size 13 fonts
with the bold property set will draw with anti-aliasing.
Changing the font style from Regular to Bold, or increasing the font size
improves the readability of the text.
Dynamo sets with text objects that use small fonts may need to be edited
in pictures where SmoothShapes is enabled. Changing the font style from
regular to bold or increasing the font size improves the appearance of the
text within the Dynamo.
Anti-aliased Objects with Edge Style = 6 (inside frame) will See Color Out-
side the Object Frame
DE25183 WorkSpace Anti-aliased objects with edge style = 6 (inside frame) will see pixels for
the background color or fill color outside the object's frame. There is cur-
rently no workaround.
These popup pictures are meant for the associated Dynamo objects
DE29588 WorkSpace (Chart_LineHist and Chart_LineRealTime). When the Chart_LineHist or
Chart_LineRealTime Dynamo is dropped onto a picture, it displays the
associated popup screen to set the plot styles and time definitions. These
pictures are not meant to be edited directly.
An Error Message Appears when Trying to Start My-T-Soft after Installing
iFIX
If you see a "server not licensed" error message from IMG, start the service
DE28601 My-T-Soft manually. From Start menu, select My-T-Soft > License Information to
open the IMG application, and click the Start Service button. You can also
use the command line to start the service: Manage.exe START. After the
service starts, try to run My-T-Soft again.
VisconX dialog boxes display a few headings with clipped text (in Configure
mode only)
DE113972 VisconX When using the VisiconX controls, be aware that the Database and Record
Source tabs may contain some subheadings with clipped text. This is a
known issue due to a Microsoft coding limitation on text allowed on frames
used within frames. There is no known workaround at this time.
Unable to Configure Historian Server in the iFIX WorkSpace after installing
Historian 8.1 or 9.0 Client Tools one time
DE151572 Historian
When this issue is encountered, install the Historian 8.1 or 9.0 Client Tools
a second time on the iFIX system, restart, and then try again to configure.
The OPC UA Server cannot monitor more than 32,000 tag fields at a time
DE139692 OPC UA Server There is currently no support for more than 30,000 tags in the OPC UA
Server.
Model tags not initially shown in Expression Builder after Model Import
Configuration The workaround is wait a few minutes and do a refresh, or close the
DE150686
Hub WorkSpace and then restart after a few minutes. The indirect tags should
now be listed.
Deleted Shelve Policy Still Appears in Configuration Hub UI
Configuration If you delete a shelve policy in the Database Manager, it will still appear
DE145434 assigned to tags in the Configuration Hub UI. No error appears when you
Hub
open the tag in Configuration Hub. As a workaround, you need to manually
update the tag with a new policy.
Browse dialog opens slowly with IGS and IDS when connected to a large
configuration
Database Man-
DE137521 The browse button may take over a minute or more to open when with a
ager
large database. As a workaround, wait a few minutes for the database to
open.
WorkSpace will not start when the domain user is added to the secure
group after the install
DE137082 iFIX WorkSpace After adding a user to the iFIX secure users group on a Domain, you may
not have immediate access to iFIX resources (cannot run iFIX). Wait for a
few minutes and then try again.
Default Tag values always displayed with US Regional Settings
Configuration
DE152368 The iFIX plugin for Configuration Hub is only supported with English
Hub
regional settings.
The Progress Bar for the Publish does not Update Fast
Configuration
DE153297 Publish operation may take a while depending on the number of tags being
Hub
published to the active iFIX node. Please wait for the Done indication.
Configuration No error seen when publishing simultaneously - Second publish hangs
DE153266
Hub It is recommended that you only perform one publish operation at a time.
Firefox Browser - Model Tree: Object Type and Instance context menu
options are not working
Configuration In the Firefox browser, in the Model panel, if any Object Type/Object is
DE153266
Hub selected, and any right-click menu option is selected, then the operation is
not being done. The workaround is to select the overflow icon to do the
intended operation.
JSON Files for REST API Have Wrong Encoding
ferent
Be aware that Configuration Hub supports only UTF-8 encoded files. The
iFIX Database Manager uses ANSI encoding.
If you export a .CSV database file from Configuration Hub, you need to
change the format from UTF-8 to ANSI before importing it into the iFIX
Database Manager. Open the .CSV file in Notepad, save the file with ANSI
Hub
encoding, and then import it into the Database Manager.
Likewise, to import a .CSV database file from the Database Manager into
Configuration Hub, the file format must be in UTF-8 format. If you exported
your .CSV file from the iFIX Database Manager, you must change the
format to UTF-8 before importing it into Configuration Hub.
The iFIX installation fails if the host name or computer name is greater
than 15 characters This limitation is because the network NetBIOS name
can be only 15 characters.
DE166800 Installation
With greater than 15 characters, you cannot set the iFIX Secure Mode-
Service user. Also, the Configuration Hub certificate will not be created
properly, making it so that you cannot log in to Configuration Hub.
When running the Plant Applications Report Server as a service (for the
Microsoft Excel Addin), you may experience issues if you do not have the
security settings correct for ActiveX controls.
If you see this message and ignore it or disable the control, you will also
ActiveX Con-
DE146496 experience issues: "Microsoft Forms: This application is about to initialize
trols
ActiveX controls that might be unsafe. If you trust the source of this file,
select OK and the controls will be initialized using your current workspace
settings."
1. Log into the Plant Applications Report Server with the account the
report server services are configured to run as. (On a client system, skip
this step.)
6. Click OK twice.
7. On the Report Server, restart the Plant Applications Report Server ser-
vices.
trol" utility from the Start Menu and set the service account and password.
Otherwise, iFIX will fail to start.
iFIX Installer Can Not Create IFIXUSERS Group when Machine Name Con-
tains non-English Characters
DE173848 Installation
Running iFIX on a computer with a machine name that contain non-English
characters such as æ, ø, å in the name is not supported.
OPC UA Client Working Prior to Upgrade, but Now Registration Shows Cer-
tificate Not Trusted
If you forget to delete the certificate before upgrading iFIX, you will need to
follow the steps in this topic in order to trust the certificate again after the
upgrade: https://www.ge.com/digital/documentation/confighub/g_ifix_con-
fighub_server_name_changes_ifix.html#g_ifix_confighub_server_name_
changes__ifix_certs1.
APPLICATION DESIGNER Group Does Not Migrate on Upgrade or Export to
Proficy Authentication After Upgrade
This issue occurs because Proficy Authentication does not support spaces
in group names. To resolve this issue after upgrading, create the group
again in iFIX and then export it to Proficy Authentication.
1. In the iFIX Security Application go to Edit > Group Accounts. The Group
Accounts dialog box appears.
5. Click OK until you return the the Group Accounts dialog box.
On the Security panel, click the Users link. Double-click the ch_admin user.
In the Details pane, in the Group Membership area, click Edit to open the
Group Membership dialog box. Select the check box for the following
groups: scada.fix_shared.IFIX_PROFICY_AUTH_ADMIN, and
scada.fix.shared_APPLICATION_DESIGNER, and then click Apply. Save your
changes. The APPLICATION _DESIGNER will give you access to iFIX in Con-
figuration Hub, while IFIX_PROFICY_AUTH_ADMIN will allow you to use
Proficy Authentication.
When an Operations Hub Model File is Imported, Instances Are Not seen in
Model List
Configuration Spaces are not supported in model or tag names in Configuration Hub. So
DE174332 for instance, if your Operation Hub model is imported into Configuration
Hub
Hub and the model names have spaces, the model instances will not be
seen the model list. As a workaround, update the model file to remove the
unsupported space characters before importing.
Getting "Failed to load plugin Application: Undefined" while Loading the
Configuration Remote iFIX Plugin
DE174443
Hub The Configuration Hub node and the iFIX node need to be in the same
domain or same workgroup.
Error Seen Frequently that iFIX is Not Started or Unable to Retrieve Local
Configuration Information
DE169376
Hub Make sure that Configuration Hub and iFIX server (or iFIX servers in
Enhanced Failover setup) share the same time zone and system locale.
Issues registering upgraded iFIX Server with remote Configuration Hub
When iFIX 2023 is upgraded from a previous version of iFIX, sometimes the
iFIX Register to Configuration link shows as non-trusted. You will need to
recreate the iFIX_OpcuaConfigService certificate. The steps to do that are:
Configuration
DE174910 NOTE: If you experience any certificate issues when you open up Con-
Hub
figuration Hub, you can use these same steps to remove the certificates
and then re-add them.
1. From the iFIX install folder, open the iFIX Configuration Service Cer-
tificate Tool (iFixConfigServiceCertTool.exe) tool as an Administrator. By
default, this tool is found in the C:\Program Files (x86)\GE\iFIX\ folder.
6. Restart iFIX. When iFIX starts, and you open the Configuration Hub
Server Registration page to register Configuration Hub from the iFIX
WorkSpace, the trust should now appear on this page.
iFIX Database Name Issues with Capital Letters in German, French, and
Polish
Configuration For German, French, and Polish languages, when using Configuration Hub,
DE182433 the iFIX database name can only be in lower case letters. Do not use cap-
Hub
ital letters for the iFIX database file name in these languages; capital let-
ters in an iFIX database file name are not supported for German, French,
or Polish.
Configuration Publish Model to Operations Hub fails with Operations Hub 2022
DE197211
Hub If publishing a model from iFIX 2023, you must use Operations Hub 2023.
Alarms issue seen if Alarm Area and Model names are same
Configuration
DE194475 Alarm name, Tag name, and Model object instance names should not be
Hub
same.
Model browse - Can't browse children of a Type or Instance that has same
name as an alarm area
Configuration
DE194485 iFIX entities like the database name, tag names, alarm areas, model types,
Hub
and model instances must be unique. Ensure you use unique names when
creating these items.
Proficy Common and Proficy License Server folders are created at the
default location even if a different location was specified during the install
DE194980 Installation 'Proficy Common' and 'Proficy License Server' folders are created under
default location: C:\Program Files (x86)\Proficy. You cannot specify a cus-
tom location for these install folders with the integrated installer.
Unable to publish screens to Operations Hub using a remote Proficy
DE197305 Operations Hub Authentication (UAA) instance
This is a known issue in iFIX 2023. There is currently no workaround.
Login to Registration failing when iFIX Security path is using shared
mapped drive/UNC paths
When iFIX security configuration paths are set to reside on shared drives,
Configuration the login to the plugin registration page fails.
DE197220
Hub
Computers connected in a Work Group environment is not supported in
iFIX 2023 with shared drive Security Paths (using Configuration Hub).
machine account from where the plugin registration occurs. For example:
say the folder to be shared is named "security" and located on Computer1,
and you want to access by iFIX from Computer2 and Computer2 is
registered to Configuration Hub. On Computer1, in Windows Explorer nav-
igate to the "security" folder, right-click it and select Properties. Click the
"Sharing" tab. Click the "Share…" button and add Computer2$ with read
permissions. This ensures that the folder is accessible to the Computer2
machine account. The login to the plugin registration page should now be
successful.
When iFIX is started as Service, the iFIX plugin fails to load in Configuration
Hub when iFIX Security Paths or any other SCU paths are using a shared
mapped drive/UNC paths
When iFIX is started normal mode, this issue will not be encountered.
Configuration In a domain environment, the shared folder should be given access to the
DE197296 machine account from where the plugin registration occurs. For example:
Hub
say the folder to be shared is named "security" and located on Computer1,
and you want to access by iFIX from Computer2 and Computer2 is
registered to Configuration Hub. On Computer1, in Windows Explorer nav-
igate to the "security" folder, right-click it and select Properties. Click the
"Sharing" tab. Click the "Share…" button and add Computer2$ with read
permissions. This ensures that the folder is accessible to the Computer2
machine account. The login to the plugin registration page should now be
successful.
Files found under subfolders (for example: PIC\SUBFOLDER) are not dis-
played in the Deploy Panel
Configuration
DE193115 The iFIX 2023 Project Deployment feature does not support the deploy-
Hub
ment of pictures from subfolders. Only pictures in the default PIC folder
can be deployed.
After an Upgrade from iFIX 6.5/2022 to iFIX 2023 new panels show up
Configuration blank in Configuration Hub
DE182575
Hub When upgrading from iFIX 6.5 or 2022 to iFIX 2023 you must re-register
iFIX with Configuration Hub for the new Project Settings to appear.
If ACL is Not Configured, launch.exe or fix.exe unable to start when web-
space WSM cache is enabled
word
iFIX Screen When running Webspace Sessions in "Loose Mode" (using command-line
N/A options useApp=true&embed=false) or using the Desktop Client (Proficy
Saver
Webspace - AllUsers App), the iFIX Screen Saver experiences blank screen
issues. This is a known limitation and there is currently no workaround.
Can't start ihFixCollector.exe after uninstalling and then reinstalling His-
torian Client Tools
sc delete ihFixCollector
sc delete ihiFixAECollector
l Software Requirements
l Hardware Requirements - iFIX SCADA Server
l Hardware Requirements - iFIX iClient/View
l Wireless Devices and iFIX
l Virtual Machine Support
l Remote Desktop (Terminal Server) Support
l Compatibility with other GE products
l A 3.0 GHz Intel® Core™ i5 Processor or equivalent with 8GB of memory. For better performance,
please consider using a faster processor and more memory. When running Proficy Authentication
or Historian on the same server at the iFIX SCADA Server, we recommend at least 16 GB of
memory.
l SpeedStep® technology is not supported and must not be enabled.
l For time synchronization, the Windows Net Time and W32tm commands are both supported.
However, if using the W32tm command, be sure to use the /nowait instruction when resyn-
chronizing the clock. For example: W32tm /resync /nowait. The /nowait parameter instructs the
operating system to make a stepping adjustment against the time server.
NOTE: With virtual machines, the host and guest operating system need to synchronize against an external
physical Network Time Protocol (NTP) Server.
l The power save settings on your computer must be disabled. Do not use any power setting fea-
tures that affect CPU clock speed. For Enhanced Failover, the power save settings on both com-
puters and dedicated network card (NIC) must be disabled.
l For Enhanced Failover, Gigabit-Ethernet cards (or better) are required for Data Sync Transport
communication. When using UDP, a dedicated card is required for Data Sync Transport com-
munication. When using TCP, one card can be used for both iFIX and Data Sync Transport com-
munication, although two are strongly recommended to avoid slower updates of data and alarms
on clients. When using a network card dedicated for Data Sync Transport communication, it
should be disabled as an available LAN Redundancy Path under the Advanced section of your Net-
work Configuration. Additionally, the card dedicated for Data Sync Transport communication
should be the only card enabled under SCADA Configuration's Data Sync Transport Options. Net-
work cards must be of the same speed, and appear on the compatibility list for each card. It is
strongly recommended that the cards be of the same make and model number, and use the same
drivers.
l For Enhanced Failover, when using UDP, you must use a direct connection via a Cat6 crossover
cable, without going through any switches, hubs, or routers. Due to limited bandwidth and latency,
wireless networking technology should not be considered.
l For Enhanced Failover, when using UDP, the Primary and Secondary SCADA computers must be
located physically next to each other, in the same location/room.
l For Enhanced Failover, when using UDP, Jumbo Frames technology must be used on the dedicated
network. Jumbo Frames technology allows for an Ethernet frame of 9000 MTU for the payload,
compared to a frame of 1500 bytes without the Jumbo Frames.
l A minimum of 40 GB of free hard drive space for iFIX pictures, databases, alarm files, and other
data files, in addition to the free disk space required by the operating system for Windows
Updates. It is strongly recommended that many GBs of additional free space exist on the hard
drive to avoid performance issues.
l Be aware that iFIX alarm and historical data files grow dynamically. If you plan to perform extens-
ive alarm or data collection on a node, you may need more disk space on that particular node.
l Other GE products, such as Proficy Plant Applications and Proficy Historian, impose additional
requirements. Refer to the System Requirements in the associated product's electronic books for
that product's specific system requirements.
l 100 MBit or faster Full Duplex TCP/IP-compatible network interface adapter for iFIX network com-
munication between SCADA and Client nodes.
NOTE: iFIX does not support NetBIOS or IPv6.
l A 3.0 GHz Intel® Core™ i3 Processor or equivalent with 4GB of memory. For better performance,
please consider using a faster processor and more memory.
NOTE: To use more than 4 GB of memory on a 32-bit platform you need to use Physical Address Extension
(PAE). For more information on PAE please reference: http://msdn.microsoft.com/en-us/lib-
rary/windows/desktop/aa366796%28v=vs.85%29.aspx.
l SpeedStep® technology is not supported and must not be enabled.
l For time synchronization, the Windows Net Time and W32tm commands are both supported.
However, if using the W32tm command, be sure to use the /nowait instruction when resyn-
chronizing the clock. For example: W32tm /resync /nowait. The /nowait parameter instructs the
operating system to make a stepping adjustment against the time server.
NOTE: With virtual machines, the host and guest operating system need to synchronize against an external
physical Network Time Protocol (NTP) Server.
l The power save settings on your computer must be disabled. Do not use any power setting fea-
tures that affect CPU clock speed.
l A minimum of 20 GB of free hard drive space for iFIX pictures, databases, alarm files, and other
data files, in addition to the free disk space required by the operating system for Windows
Updates. It is strongly recommended that many GBs of additional free space exist on the hard
drive to avoid performance issues.
l Be aware that iFIX alarm and historical data files grow dynamically. If you plan to perform extens-
ive alarm or data collection on a node, you may need more disk space on that particular node.
l Other GE products, such as Proficy Plant Applications and Proficy Historian, impose additional
requirements. Refer to the System Requirements in the associated product's electronic books for
that product's specific system requirements.
l 100 MBit or faster Full Duplex TCP/IP-compatible network interface adapter for iFIX network com-
munication between SCADA and Client nodes.
NOTE: iFIX does not support NetBIOS or IPv6.
l One free direct-connect USB port. Some touch screens, pointing devices, and I/O drivers require a
serial port. Additional ports for I/O hardware should be ordered with the computer.
l SVGA or better color monitor with a 24-bit (16,777,216 colors) graphics card capable of at least
1024x768 resolution.
l Two-button mouse or compatible pointing device (such as a touch screen) that can open a context
menu.
GE Digital will support the functional operation of the product that is running on a supported Operating
System in a virtualized environment and will address any functional issues related to the software.
GE Digital cannot guarantee performance of the software in the virtualized environment due to the wide
range of parameters associated to the hardware, configuration, memory settings, 3rd party software,
and the number of virtual sessions running on the same hardware, all of which can affect performance.
It is the responsibility of you, the customer, to ensure that the performance of the GE HMI/SCADA soft-
ware and application are adequate to meet the needs of their runtime environment. GE does not support
issues related to functionality that is not available as a result of running in a virtual machine. Examples
include the functionality of card level drivers such as Genius, RMX, SA85 and functions requiring direct
video access, or functionality of other software running in the same environment. It is your responsibility
to check with the vendor of those applications for their ability to run in a virtualized environment.
Each virtual machine instance that is using our software is required to have a valid license. The licensing
in a virtualized environment will depend on the access to a hardware key or a license server depending
on the selected license type.
l Microsoft Windows 10: Remote Desktop Connection Version 10.0.19041 – Remote Desktop Pro-
tocol 10.8
l Microsoft Windows 11: Remote Desktop Connection Version 10.0.22000 – Remote Desktop Pro-
tocol 10.10
l Microsoft Windows Server 2016: Remote Desktop Connection Version 10.0.14393 – Remote
Desktop Protocol 10.2
l Microsoft Windows Server 2019: Remote Desktop Connection Version 10.0.17763 – Remote
Desktop Protocol 10.6
l Microsoft Windows Server 2022: Remote Desktop Connection Version 10.0.20348 – Remote
Desktop Protocol 10.9
IGS NOTE: For a list of supported operating systems, refer to IGS article id 000004780 on
https://digitalsupport.ge.com/ with the latest downloads and information on the IGS
driver.
NOTE: For information on product compatibility with critical Microsoft security patches, go to the GE
Digital support web site:
https://digitalsupport.ge.com/communities/en_US/Article/Information-on-Product-Compatibility-with-
Critical-Microsoft-Security-Patches