RSNetWorx - 28.01.00 (Released 6 - 2019)

Release Notes
( 9357-x ) RSNetWorx™ provides design and configuration management services for ControlNet™, DeviceNet™, and
EtherNet/IP™.
Version 28.01.00 (released 6/2019)
Catalog Number RSNetWorx
These release notes describe version information for RSNetWorx, version 28.01.00 (released 6/2019).
Requirements
This release has the following requirements.
RSNetWorx for DeviceNet works within the system requirements of all Rockwell Automation® software products. For the latest information regarding software
platform support, refer to Rockwell Automation Product Compatibility and Download Center .
Hardware requirements
An Intel® Core™ 2 Duo processor running at 2.8 GHz or faster or another processor with equivalent specifications
4 GB or more memory RAM
At least 16GB of available hard drive space
Software requirements
Operating systems
RSNetWorx for DeviceNet is tested on operating systems installed from original Microsoft® media only. It runs on either the 32-bit or 64-bit versions of the
following Windows® operating systems:
Windows Server 2019 Standard Long-Term Servicing Channel 64-bit

Windows Server 2019 Datacenter Long-Term Servicing Channel 64-bit
Windows 10 Semi-Annual Channel v1903
Windows 10 Long-Term Servicing Channel 2019
Windows 10 Enterprise v1703, 1709, and v1803
Windows 10 Professional v1703, 1709, and v1803
Windows 7 Ultimate with Service Pack 1
Windows 7 Enterprise with Service Pack 1
Windows 7 Professional with Service Pack 1
Windows Server 2016 Standard
Windows Server 2016 Datacenter
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Datacenter
Windows Server 2008 R2 Standard with Service Pack 1
Windows Server 2008 R2 Enterprise with Service Pack 1
Compatible software
The following software is compatible with this version of RSNetWorx:
FactoryTalk® Activation Manager version 4.03

FactoryTalk® Services Platform version 6.11
RSLinx® Classic version 4.11
RSLogix™ 5 version 9.00
RSLogix 500® version 12.00
Studio 5000 Logix Designer® version 32.00
Firmware requirements
If you are using any of the Allen-Bradley modules listed in the following table, they must have the association minimum firmware revision installed:
Module Firmware Revision
1747-SDN Version 2.004 or later; version 3.001 for slave mode support; version
4.008 for ADR support; version 4.015 for pass-through (bridging) support.
1756-DNB Version 1.003 or later; version 1.5 or later for pass-through (bridging)
support; version 3.001 or later for ADR support.
1769-SDN/B Version 2.001 or later for ADR support.
1770-KFD Version 1.004 or later.
1794-ADN Version 1.4 or later; or version 2.1 or later.
High Resolution Display Support
Windows 10 build 1703 or later is the recommended operating system if running this software with a 2K or 4K High Resolution Display.
Supported browsers
The following web browsers have been tested and are supported for use with this release:
Google® Chrome™ browser

Internet Explorer® 11
Mozilla® Firefox®
RSNetWorx for ControlNet works within the system requirements of all Rockwell Automation® software products. For the latest information regarding software
platform support, refer to Rockwell Automation Product Compatibility and Download Center .
Operating systems
RSNetWorx for ControlNet is tested on operating systems installed from original Microsoft® media only. It runs on either the 32-bit or 64-bit versions of the

Compatible software

Firmware requirements
RSNetWorx for ControlNet can configure single-keeper networks or multi-keeper networks. You can mix both single-keeper and multi-keeper devices on the
same ControlNet™ network as long as the lowest node address is a multi-keeper device.
Rockwell Automation ControlNet 1.5 or ControlNet International 2.0 specifications
For Hot Backup support, the PLC-5®C processors must be at the following series/revision levels or later:
PLC-5/40C15 – F/A
PLC-5/80C15 – F/A
For multi-keeper and Merged Edits support, the PLC-5C processors must be at the following series/revision levels or later:
PLC-5/20C15 – C/M, D/D, E/C

PLC-5/40C15 – C/M, D/D, E/C
PLC-5/46C15 – E/C
PLC-5/60C15 – D/D
PLC-5/80C15 – D/D, E/C
For multi-keeper support, the 1756-CNB devices must be at the following series/revision levels or later:
1756-CNB – B/A, D/A
Supported browsers

Mozilla® Firefox®
RSNetWorx for EtherNet/IP works within the system requirements of all Rockwell Automation® software products. For the latest information regarding
software platform support, refer to Rockwell Automation Product Compatibility and Download Center .
Operating systems
RSNetWorx for EtherNet/IP is tested on operating systems installed from original Microsoft® media only. It runs on either the 32-bit or 64-bit versions of the

Compatible software

Supported browsers

Mozilla® Firefox®
Features
This release includes the following system features.
RSNetWorx for DeviceNet version 28.01.00 has no new features or enhanced features.
RSNetWorx for ControlNet version 28.01.00 has no new features or enhanced features.
RSNetWorx for EtherNet/IP version 28.01.00 has no new features or enhanced features.
Corrected Anomalies in This Release

This release corrects the following anomalies.
There are no corrected anomalies in this release.
Known Anomalies in This Release

This release has the following known anomalies.
Edits to the chassis does not alter the associated slot mask.
After you have defined connections to any 1747 or 1794 adapter modules in a chassis, any subsequent edits to the chassis (for example, adding
devices) does not alter the associated slot mask for the adapter module. First reported in version 3.00. [ 363939]
To avoid this issue, delete any affected adapter connections and redefine them.
Diagnostic view does not indicate connection errors.

If you have a connection from a non-PLC-5, non-ControlLogix scanner (for example, a 1747-SCNR) to a 1771 module, the Diagnostic view will not
indicate a connection error when there is a connection error. First reported in version 5.00. [ 363940]
To work around this issue and view the actual connection error, launch the Scanlist Configuration Tool for the non-PLC-5, non-ControlLogix scanner
and view the Connection Status view.
To avoid this issue, ensure that your 1771 target exists in the network configuration and the device is communicating properly on the network before
opening the Diagnostic View.
Diagnostic view does not indicate connection warnings.

If you have a connection from a non-PLC-5, non-ControlLogix scanner (for example, a 1747-SCNR) to a peer target device (for example, a PLC-5
processor), the Diagnostic view does not indicate a connection warning when the target is not in Program Mode. First reported in version 5.00.
[363941]
To avoid this issue, manually change the peer target device to Program mode prior to running diagnostics.
The diagnostics in the first instance of Networx Health Diagnostics are stopped.
If you are running NetWorx Health Diagnostics in one instance of RSNetWorx and perform connection edits in a second instance of RSNetWorx, the
diagnostics in the first instance of Networx Health Diagnostics will be stopped. First reported in version 4.00. [363942]
To avoid this issue and resume diagnosing your network, manually restart diagnostics in the first instance of RSNetWorx.
The redundant connection conflicts with the stored configuration.

When saving a configuration file (*.xc) online that specifies a Redundant owner connection from a PLC-5C (Series F, Revision A or later) processor
that does not have the Hot Backup cartridge (1785-CHBM) installed, the Scanlist Configuration Tool displays an error message. In this cases, the
PLC-5 returns information about the redundant connection that conflicts with the stored configuration. First reported in version 3.00. [363943]
To avoid this issue, ensure that the PLC-5C processors used in the Hot Backup configuration have the Hot Backup cartridge installed when the
Redundant owner connection type is specified in the Scanlist Configuration Tool.
Updates to a PLC-5C keeper are not recognized

If you are connected to a ControlNet network through a ControlLogix gateway and the 1756-CNB is the active keeper device on your network, updates
to a PLC-5C keeper on that same network are not recognized. First reported in version 4.00. [363944]
To avoid this issue, perform one of the following:
Use a 1756-CNB other than the one that is currently configured as the active keeper device on your ControlNet network.
Update the PLC-5C firmware to series F, revision C.1 (or later).
Open the Keeper Status dialog box and update the individual keeper that failed to update (particularly if the failure occurred during a save or
download operation).
Not responding when bridging from the offline configuration file in one instance to another.
If you are running multiple instances of RSNetWorx for DeviceNet (instance A and instance B), and attempting to bridge from the offline configuration
file in the first instance to the second offline configuration file in the second instance, the software stops responding. First reported in version 3.00.
[363931]
To avoid this issue, we recommend using only a single instance of RSNetWorx for DeviceNet when configuring device bridging or using associated
networks.
RSNetWorx does not prevent the user from downloading SmartGuard EIP when logic with an invalid address exists. The download fails and the original
configuration in the hardware is lost. First reported in version 10.00. [363932]
To avoid this issue, open the original configuration, and then go online to download SmartGuard EIP to restore its configuration.
The download operation to 1753-DNSI DeviceNet Safety Scanner fails.

If you are using the SmartGuard USB driver in RSLinx Classic or EtherNet/IP port of SmartGuard EIP and attempt to download to a 1753-DNSI
DeviceNet Safety Scanner (in RSNetWorx for DeviceNet, right-click the 1753-DNSI DeviceNet Safety Scanner, and then select Download to Device),
the download operation fails. First reported in version 9.00. [363933]
To avoid this issue, use a direct connection from your computer to the DeviceNet network (for example, a 1784-PCD driver) or bridge to your
DeviceNet network through another device.
Communication error occurs when communicating to a safety device.

RSNetWorx for DeviceNet reports a communication error if you are communicating to a safety device (for example, 1753-DNSI, 1791DS-IB12,
1791DS-IB4XOW4, 1791DS-IB8XOB8) using a revision of 1756-DNB prior to v6.002, and you try to lock/Unlock that safety device. First reported in
version 6.00. [363934]
To avoid this issue, update the flash firmware for the 1756-DNB module to v6.002 or higher. For more information, contact Technical Support.
Items selected in one view are not selected among the other available views.
When navigating between the Graph and Spreadsheet views for the network configuration, you may encounter a situation where the items selected in
one view are not selected among the other available views. For example, if you select your entire network configuration in the Graph view, navigate to
the Spreadsheet view and click the adapters to display the modules contained within the chassis, and then return to the Graph view, the chassis
originally selected in the Graph view is no longer selected. First reported in version 5.00. [363935]
To avoid this issue, select the desired devices again in the final destination view.
General Protection Faults may occur with multiple instances.

When initiating concurrent browses in multiple instances of RSNetWorx through the same communication device, the software will encounter General
Protection Faults (GPFs). First reported in version 5.00. [363936]
To avoid this issue, do not initiate multiple browses of RSNetWorx through the same communications device.
The Diagnostic view does not indicate errors.

If you have a connection from an EtherNet/ IP scanner to a target peer device (for example, another EtherNet/IP scanner), the Diagnostic view will not
indicate an error when the target is in Program Mode. First reported in version 5.00. [363937]
The diagnostics in the first instance of RSNetWorx MD is stopped.

If you are running RSNetWorx MD in one instance of RSNetWorx and perform connection edits in a second instance of RSNetWorx, the diagnostics in
the first instance of RSNetWorx MD will be stopped. First reported in version 5.00. [363938]
To avoid this issue, you must manually restart diagnostics in the first instance of RSNetWorx to resume diagnosing your network.
Known Anomalies from Previous Releases

These anomalies are from previous releases but are still known in this release.
Edits to the chassis does not alter the associated slot mask.
After you have defined connections to any 1747 or 1794 adapter modules in a chassis, any subsequent edits to the chassis (for example,
adding devices) does not alter the associated slot mask for the adapter module. First reported in version 3.00. [363939]
To avoid this issue, delete any affected adapter connections and redefine them.
Diagnostic view does not indicate connection errors.
If you have a connection from a non-PLC-5, non-ControlLogix scanner (for example, a 1747-SCNR) to a 1771 module, the Diagnostic view will
not indicate a connection error when there is a connection error. First reported in version 5.00. [363940]
To work around this issue and view the actual connection error, launch the Scanlist Configuration Tool for the non-PLC-5, non-ControlLogix
scanner and view the Connection Status view.
To avoid this issue, ensure that your 1771 target exists in the network configuration and the device is communicating properly on the network
before opening the Diagnostic View.
Diagnostic view does not indicate connection warnings.
If you have a connection from a non-PLC-5, non-ControlLogix scanner (for example, a 1747-SCNR) to a peer target device (for example, a
PLC-5 processor), the Diagnostic view does not indicate a connection warning when the target is not in Program Mode. First reported in version
5.00. [363941]
The diagnostics in the first instance of Networx Health Diagnostics are stopped.
If you are running NetWorx Health Diagnostics in one instance of RSNetWorx and perform connection edits in a second instance of RSNetWorx,
the diagnostics in the first instance of Networx Health Diagnostics will be stopped. First reported in version 4.00. [363942]
To avoid this issue and resume diagnosing your network, manually restart diagnostics in the first instance of RSNetWorx.
The redundant connection conflicts with the stored configuration.
When saving a configuration file (*.xc) online that specifies a Redundant owner connection from a PLC-5C (Series F, Revision A or later)
processor that does not have the Hot Backup cartridge (1785-CHBM) installed, the Scanlist Configuration Tool displays an error message. In
this cases, the PLC-5 returns information about the redundant connection that conflicts with the stored configuration. First reported in version
3.00. [363943]
To avoid this issue, ensure that the PLC-5C processors used in the Hot Backup configuration have the Hot Backup cartridge installed when the
Redundant owner connection type is specified in the Scanlist Configuration Tool.
Updates to a PLC-5C keeper are not recognized
If you are connected to a ControlNet network through a ControlLogix gateway and the 1756-CNB is the active keeper device on your network,
updates to a PLC-5C keeper on that same network are not recognized. First reported in version 4.00. [363944]
To avoid this issue, perform one of the following:
Use a 1756-CNB other than the one that is currently configured as the active keeper device on your ControlNet network.
Update the PLC-5C firmware to series F, revision C.1 (or later).
Open the Keeper Status dialog box and update the individual keeper that failed to update (particularly if the failure occurred during a
save or download operation).
Not responding when bridging from the offline configuration file in one instance to another.
If you are running multiple instances of RSNetWorx for DeviceNet (instance A and instance B), and attempting to bridge from the offline
configuration file in the first instance to the second offline configuration file in the second instance, the software stops responding. First
reported in version 3.00. [363931]
To avoid this issue, we recommend using only a single instance of RSNetWorx for DeviceNet when configuring device bridging or using
associated networks.
RSNetWorx does not prevent the user from downloading SmartGuard EIP when logic with an invalid address exists. The download fails and the original
configuration in the hardware is lost. First reported in version 10.00. [363932]
To avoid this issue, open the original configuration, and then go online to download SmartGuard EIP to restore its configuration.
The download operation to 1753-DNSI DeviceNet Safety Scanner fails.
If you are using the SmartGuard USB driver in RSLinx Classic or EtherNet/IP port of SmartGuard EIP and attempt to download to a 1753-DNSI
DeviceNet Safety Scanner (in RSNetWorx for DeviceNet, right-click the 1753-DNSI DeviceNet Safety Scanner, and then select Download to
Device), the download operation fails. First reported in version 9.00. [363933]
To avoid this issue, use a direct connection from your computer to the DeviceNet network (for example, a 1784-PCD driver) or bridge to your
DeviceNet network through another device.
Communication error occurs when communicating to a safety device.
RSNetWorx for DeviceNet reports a communication error if you are communicating to a safety device (for example, 1753-DNSI, 1791DS-IB12,
1791DS-IB4XOW4, 1791DS-IB8XOB8) using a revision of 1756-DNB prior to v6.002, and you try to lock/Unlock that safety device. First reported
in version 6.00. [363934]
To avoid this issue, update the flash firmware for the 1756-DNB module to v6.002 or higher. For more information, contact Technical Support.
Items selected in one view are not selected among the other available views.
When navigating between the Graph and Spreadsheet views for the network configuration, you may encounter a situation where the items
selected in one view are not selected among the other available views. For example, if you select your entire network configuration in the Graph
view, navigate to the Spreadsheet view and click the adapters to display the modules contained within the chassis, and then return to the Graph
view, the chassis originally selected in the Graph view is no longer selected. First reported in version 5.00. [363935]
To avoid this issue, select the desired devices again in the final destination view.
General Protection Faults may occur with multiple instances.
When initiating concurrent browses in multiple instances of RSNetWorx through the same communication device, the software will encounter
General Protection Faults (GPFs). First reported in version 5.00. [363936]
To avoid this issue, do not initiate multiple browses of RSNetWorx through the same communications device.
The Diagnostic view does not indicate errors.
If you have a connection from an EtherNet/ IP scanner to a target peer device (for example, another EtherNet/IP scanner), the Diagnostic view
will not indicate an error when the target is in Program Mode. First reported in version 5.00. [363937]
The diagnostics in the first instance of RSNetWorx MD is stopped.
If you are running RSNetWorx MD in one instance of RSNetWorx and perform connection edits in a second instance of RSNetWorx, the
diagnostics in the first instance of RSNetWorx MD will be stopped. First reported in version 5.00. [363938]
To avoid this issue, you must manually restart diagnostics in the first instance of RSNetWorx to resume diagnosing your network.
Functional Changes
This release has the following functional changes from the previous release.
There are no functional changes in RSNetWorx for ControlNet version 28.01.00.
There are no functional changes in RSNetWorx for DeviceNet version 28.01.00.
There are no functional changes in RSNetWorx for EtherNet/IP version 28.01.00.
Application Notes
This release has the following application notes.
VeriSign Universal Root Certification Authority certificate
If the VeriSign Universal Root Certification Authority certificate does not exist on the local computer, the certificate is installed while installing Rockwell
Automation software. Use Microsoft Management Console (MMC) to view the certificate in Console Root > Certificates (Local Computer) > Trusted
Root Certification Authorities > Certificates .
Unattended or silent install
Use command-line parameters to perform an unattended or silent installation of the software.

Command-line parameters
The following table identifies the installation command-line parameters. Command-line parameters are case-insensitive. However, if a specified value
includes a space, be sure to enclose the value in quotation marks (for example, "value with spaces").
Parameter Description
/? Displays the usage options for installation parameters.

Silent Install, install runs in a quiet mode without any user
/Q interface.
This parameter is recommended if you are deploying the
software installation using an IT tool or script, and don’t
expect to see any error or restart messages. When using this
parameter, your IT tool or script should check the error codes,
and respond as needed. For example, if the installation
returns error code 1641, then the IT tool or script should
restart the computer and relaunch the installation after restart.
This parameter is required if /QS or /Record is not specified.
Unattended Install, install runs in a quiet simple mode and
/QS shows progress through the UI, it does not accept any input
but still shows error or restart messages.
When using this parameter, you will not have to check the
error codes, and the installation will stop and display a
prompt if there are error or restart messages. For example, if
an immediate restart is required to complete the install, a
restart message will be displayed for you to confirm the
restart. Installation resumes automatically from the point of
interruption after restart.
This parameter is required if /Q or /Record is not specified.
Acknowledges acceptance of the license terms.
/IAcceptAllLicenseTerms
This parameter is required for /Q or /QS parameters.
Automatically restarts the computer after the installation is
/AutoRestart complete. Used when a restart is required to complete the
installation.
This parameter is optional. If this parameter is not used silent
install (/Q) will return either error code 1641 or 3010 if a
restart is required, and unattended install (/QS) will result in a
confirmation prompt that must be agreed to before the
installation is completed.
Specifies which language will be displayed during install
/SetupLanguage="value" process.
The value must be the one of the following:
ENU
CHS
DEU
ESP
FRA
ITA
JPN
KOR
PTB
This parameter is optional. If this parameter is not used, the
default language is the current user or operating system user
interface language.
Records the installation options chosen to a recording file.
/Record
This parameter is optional.
Plays back a recording file to specify the installation options.
/Playback
Specifies that the setup ignores warnings and continues.
/IgnoreWarning
This parameter is optional. If it is not specified, the setup
exits when a warning occurs.
Specifies the language version of the software being
/ProductLanguage="value" installed.
ENU
CHS
DEU
ESP
FRA
ITA
JPN
KOR
PTB
default language is the same as the setup language.
If the software does not support multiple languages this
parameter is not available.
Specifies the install location.
/InstallLocation="value"
default install location is "C:\Program Files (x86)\Rockwell
Software".
Some software restricts the installer to only change the drive
the software is installed on. Use /? to determine which
parameter is supported.
Specifies the serial number of the software being installed.
/SerialNumber="value" This is used to activate the software during installation.
This parameter is optional. If it is not specified the software
must be activated manually after installation if activation is
required.
Some software does not require activation. If activation is not
required this parameter is not available.
Specifies the product key used to get activation keys during
/ProductKey="value" installation.
required.
Specifies the version of the software to activate which
/Version="value" corresponds to the product version associated with the
SerialNumber and ProductKey.
This parameter is optional. If it is not specified the installer
will use the most recent product version available.
Error codes
The following table identifies the error codes that can be returned by an installation.
Error Code Value Description
ERROR_SUCCESS 0 The installation completed successfully.

ERROR_INVALID_PARAMETER 87 One of the parameters was invalid.
ERROR_INSTALL_USEREXIT 1602 The installation was cancelled by the user.
ERROR_INSTALL_FAILURE 1603 A fatal error occurred during installation.

ERROR_BAD_CONFIGURATION 1610 The configuration data for this product is
corrupt. Contact your support personnel.
ERROR_SUCCESS_REBOOT_INITIATED 1641 The installer has initiated a restart. After
restart installation will continue.
ERROR_SUCCESS_REBOOT_REQUIRED 3010 A restart is required to complete the
installation. After restart the product is
successfully installed.
ERROR_SUCCESS_RELAUNCH_REQUIRED3011 Restart of setup needed before
installation can continue.
Scanlist Configuration Tool
While downloading a PLC-5C processor via RSLogix 5, close the corresponding Scanlist Configuration Tool. This prevents a potential General Protection
Fault (GPF) in the Scanlist Configuration Tool, while also improving the performance of the download.
Security considerations
For information on the security considerations when using Rockwell Automation products, see the following Answer ID's:
File extensions created by Rockwell Automation software, firewall rules, and service dependences - 609492 .
TCP/UDP ports used by Rockwell Automation products - 29402 .
Software updates
The Rockwell Automation Knowledgebase maintains the current list of Rockwell Automation product updates.
For the latest product updates and patch information see the following Answer ID's:
Firmware and Software Updates - 748683

Master list of all available Patch TOCs - 604248
Click the Subscribe to Updates link at the top of each article to receive an email notification when the article is updated.
Alternatively, follow the instructions provided in "Subscribing to Product Safety Advisory (PSA) or Product Notice (PN) Notifications" Answer ID 35704 to
choose specific products about which to receive notifications.
To directly download software or firmware updates, and patch roll-ups , go to Product Compatibility and Download Center .
Note for SmartGuard 600 Safety Controllers users only
To write logic for the SmartGuard PLC, bulletin 1752-L24BBBxx, the RSNetWorx for DeviceNet installation includes the SmartGuard editor, which requires
MSXML 4.0 to function properly. However, MSXML 4.0 is not installed with RSNetWorx for DeviceNet. To use a SmartGuard PLC, you need to download and
install it manually. MSXML 4.0 is no longer supported by Microsoft and has security risks associated with it. When installing MSXML 4.0, read the MSXML
Roadmap for security considerations.
Root Certification Authorities > Certificates .

/Q interface.
installation.
ENU
CHS
DEU
ESP
FRA
ITA
JPN
KOR
PTB
interface language.
/Record
/Playback
/IgnoreWarning
ENU
CHS
DEU
ESP
FRA
ITA
JPN
KOR
PTB
Software".
required.
required.
Error codes





RSNetWorx MD
If you are diagnosing a DeviceNet network in RSNetWorx MD, we do not recommend that you attempt to commission any device on that same network with
the Node Commissioning Tool. Attempting to perform both of these operations at the same time may cause a conflict on the network and result in abnormal
behavior (for example, no reads in the Diagnostics view or the inability to connect to a device with the Node Commissioning Tool) in RSNetWorx.
Software updates

Root Certification Authorities > Certificates.

/Q interface.
installation.
ENU
CHS
DEU
ESP
FRA
ITA
JPN
KOR
PTB
interface language.
/Record
/Playback
/IgnoreWarning
ENU
CHS
DEU
ESP
FRA
ITA
JPN
KOR
PTB
Software".
required.
required.
Error codes


EtherNet/IP file service
An error message is logged when uploading to network with devices configured for L1y, L2y, or L3y controllers with connections. A message like the following
is displayed:
A connect exists from address 10.224.107.244, slot 00. The error 'Unexpected Failure (Error code: 0xD0:0x0000)' occurred while attempting to communicate
with Originator Connection List Object.
In this case, ignore the message. The uploading was actually successful.
Performance
If your network contains a large number of devices (for example, more than 75), you may notice some performance degradation when using the Graph view.
To achieve better performance, use the Spreadsheet view by selecting View > Spreadsheet.
Software updates

Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment with the movement
toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such terms and making changes to our
products and content. Please excuse the use of such terms in our content while we implement these changes.
Copyright © 2024 Rockwell Automation, Inc. All rights reserved.

Rockwell Automation, Allen-Bradley, and FactoryTalk are trademarks of Rockwell Automation, Inc.
To view a complete list of Rockwell Automation trademarks please click here.
Trademarks not belonging to Rockwell Automation are property of their respective companies.

RSNetWorx - 28.01.00 (Released 6 - 2019)

Uploaded by

Copyright:

Available Formats

RSNetWorx - 28.01.00 (Released 6 - 2019)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RSNetWorx - 28.01.00 (Released 6 - 2019)

Uploaded by

Copyright:

Available Formats

Release Notes

Catalog Number RSNetWorx

Windows Server 2019 Standard Long-Term Servicing Channel 64-bit

The following software is compatible with this version of RSNetWorx:

FactoryTalk® Activation Manager version 4.03

Module Firmware Revision

1794-ADN Version 1.4 or later; or version 2.1 or later.

High Resolution Display Support

Google® Chrome™ browser

Windows Server 2019 Standard Long-Term Servicing Channel 64-bit

The following software is compatible with this version of RSNetWorx:

FactoryTalk® Activation Manager version 4.03

Rockwell Automation ControlNet 1.5 or ControlNet International 2.0 specifications

PLC-5/20C15 – C/M, D/D, E/C

1756-CNB – B/A, D/A

High Resolution Display Support

Google® Chrome™ browser

Windows Server 2019 Standard Long-Term Servicing Channel 64-bit

The following software is compatible with this version of RSNetWorx:

FactoryTalk® Activation Manager version 4.03

Google® Chrome™ browser

High Resolution Display Support

Corrected Anomalies in This Release

There are no corrected anomalies in this release.

Known Anomalies in This Release

Diagnostic view does not indicate connection errors.

Diagnostic view does not indicate connection warnings.

The redundant connection conflicts with the stored configuration.

Updates to a PLC-5C keeper are not recognized

The download operation to 1753-DNSI DeviceNet Safety Scanner fails.

Communication error occurs when communicating to a safety device.

General Protection Faults may occur with multiple instances.

The Diagnostic view does not indicate errors.

The diagnostics in the first instance of RSNetWorx MD is stopped.

Known Anomalies from Previous Releases

Diagnostic view does not indicate connection errors.

Diagnostic view does not indicate connection warnings.

The redundant connection conflicts with the stored configuration.

Updates to a PLC-5C keeper are not recognized

The download operation to 1753-DNSI DeviceNet Safety Scanner fails.

Communication error occurs when communicating to a safety device.

General Protection Faults may occur with multiple instances.

The Diagnostic view does not indicate errors.

The diagnostics in the first instance of RSNetWorx MD is stopped.

There are no functional changes in RSNetWorx for ControlNet version 28.01.00.

There are no functional changes in RSNetWorx for DeviceNet version 28.01.00.

There are no functional changes in RSNetWorx for EtherNet/IP version 28.01.00.

VeriSign Universal Root Certification Authority certificate

Unattended or silent install

Use command-line parameters to perform an unattended or silent installation of the software.

/? Displays the usage options for installation parameters.

Error Code Value Description

ERROR_SUCCESS 0 The installation completed successfully.

ERROR_INSTALL_FAILURE 1603 A fatal error occurred during installation.

Firmware and Software Updates - 748683

Note for SmartGuard 600 Safety Controllers users only

VeriSign Universal Root Certification Authority certificate

Unattended or silent install

Use command-line parameters to perform an unattended or silent installation of the software.