ProSoft Configuration Builder README

ProSoft Configuration Builder 4.4.17 README File

This README file contains information you should know before you install or upgrade to ProSoft Configuration Builder 4.4.17. This file also contains information that may not be available in other ProSoft documentation. Visit ProSoft Technology for the most current information about the ProSoft Configuration Builder.

IMPORTANT NOTE

Forward Compatibility:

Always back up any PPF files before editing them with a new version of PCB. In some cases, PPF files edited and saved with newer versions of PCB may no longer be compatible with older versions of PCB. The latest version of PCB is always the recommended platform for the latest functionality support. The current PCB Version is 4.4.17.

If upgrading from very old versions of PCB, v2.0.1, or earlier:

For the PTQ-PDPMV1 module: The .XSY and .XFM files used by Unity Pro, generated and exported by ProSoft Configuration Builder versions 2.0.2 and newer, are NOT COMPATIBLE or INTERCHANGEABLE with earlier versions of .XSY and .XFM files generated by PCB versions 2.01, or earlier. The newer .XSY and .XFM files contain new Unity Pro data types, function blocks, and data structures that did not exist in the older versions of these files, created by older versions of PCB (please see PCB Version 2.0.2 for specific details). If upgrading from a PCB version older than v2.0.2, please be sure to verify your PROFIBUS configuration and re-export the Unity Pro .XSY and .XFM processor files and upgrade your Unity Pro project, to be sure you are using the latest enhanced versions of these files.

NOTE: To use PCB under the Windows 7 OS, you must be sure to install PCB using the "Run as Administrator" option. To find this option, right-click on the Setup.exe installer program icon. In the context menu, you will see the "Run as Administrator" option. Left-click to use this install option. Be aware, you must install using this option even if you are already logged in as an Administrator on your network or personal computer (PC). Using the "Run as Administrator" option will allow the PCB installer to create folders and files on your PC with proper permissions and security. If you do not use the "Run as Administrator" option, PCB may appear to install correctly; but you will receive numerous, repeating file access errors whenever PCB is running, especially when changing configuration screens. If this happens, to eliminate the errors, you will have to completely uninstall PCB and then re-install using the "Run as Administrator" option.

Known Problems and Limitations

Known Anomalies:

Possible issues with earlier versions of Windows XP and the installation of ProSoft fdt Configuration Manager. If installing ProSoft Configuration Builder in an XP OS, make sure the OS is updated with the latest Service Packs and .NET Framework.

When attempting to delete a second project in PCB, a Save As dialog box will appear inferring the configuration file will be saved. When this configuration file is saved, the old project file is lost.

When uploading from two different modules in the same project without first closing and reopening PCB, the second module is renamed with the first module's name.

Exporting the configuration of any module generates an error that an intermediate file is missing and the export is not completed. This does not affect CID files, AOI files, or PROFIBUS files.

The PLX32-EIP-MBTCP-UA Security Jumper (J3) will NOT prohibit the user from accomplishing a Cold Boot option from the diagnostic screen of PCB.

ProSoft Configuration Builder Version 2.2.2 (November 2010)

Detailed Reasons For Change

The following changes were implemented for ProSoft Configuration Builder (PCB), version 2.2.2 (November 2010):

For the PTQ-DNPS: PTQ-DNPS is now configurable using PCB. TT# CHG08052

For the MVI56(E)-MCMR: The configuration parameters that appear on the setup screens for MVI56-MCMR and MVI56E-MCMR are filtered based on whether user chooses Master/Slave, Slave only, or Master only port types. Only parameters needed for each specific type will be displayed. TT# CHG09059

For the ProSoft Configuration Builder (PCB): PCB had only one diagnostic screen available. To view diagnostics for more than one module, you would have to close the diagnostics screen on one and open it again for the other. PCB now supports opening multiple diagnostic screens, one screen per module, and viewing multiple screens simultaneously to make it easier to troubleshoot problems between modules. TT# CHG09060

For ProLinx 5201-DFNT-BACNET and 5201-MNET-BACNET: Added support for Type 2 (Analog Value) and Type 5 (Binary Value) data type commands in BACnet Client driver. The new driver has been designated as "BACnet, Edition 2". TT# CHG09110

For ProLinx 5104-MCM-PDPMV1: This gateway is now configurable using PCB. TT# CHG09111

For PCB: If Rockwell Software RSLinx Ethernet communication drivers are installed on the same computer as PCB, for the MVI56E modules, PCB will offer the option of connecting through an RSLinx Ethernet driver for uploading and downloading configuration files. TT# CHG09132

For PCB: 5201-BACNET-ASCII and 5202-BACNET-ASCII4, new products added to PCB. TT# CHG09633

For PCB: New splash pictures. TT# CHG09634

For PCB: MVI56 customers can choose "Change Module Type" to have PCB automatically switch their configuration to a MVI56E. This applies to MVI56-MCMR, MVI56-MNET, MVI56-MNETC, MVI56-MNETCR, and MVI56-MNETR products. TT# CHG09652

New Feature(s)

The following new features were implemented for ProSoft Configuration Builder version 2.2.2:

Three new products have been added to this version of ProSoft Configuration Builder (PCB):

ProLinx 5104-MCM-PDPMV1

ProLinx 5201-BACNET-ASCII

ProLinx 5202-BACNET-ASCII4

PCB now allows multiple diagnostics screens to be open simultaneously, one per configured module, for easier troubleshooting.

IEC 60870-5-101 Master, IEC 60870-5-103 Master, and HART configurations now allow use of any command function code that is valid for the protocols. This means that users are no longer restricted to only a specified subset of command functions, as in the past. This new feature is implemented by adding a "User Defined" Command Function Code entry field for entering any valid function code.

PCB now works with Rockwell Software RSLogix communication software (if installed on the same PC) for making connections to MVI56E modules for uploading or downloading module configuration files.

PCB now has the capability of converting configuration files created for certain MVI56 modules to make them ready for download to replacement MVI56E modules. With one menu selections, users may now convert MVI56-MCMR, MVI56-MNET, MVI56-MNETR, MVI56-MNETC, and MVI56_MNETCR configuration files to files compatible with MVI56E versions of the same protocol. This makes it easier to upgrade from older MVI56 products to the newer MVI56E versions.

ProSoft Configuration Builder Version 2.2.1.9.0171 (September 2010)

Detailed Reasons For Change

The following changes were implemented for ProSoft Configuration Builder (PCB), version 2.2.1.9.0171 (September 2010):

For the MVI56-104S: Added enhanced support for the IEC 60870-5-104 Edition 2 Server protocol. New features include support for 32-bit Bitstring data types, as well as an increased number of Causes of Transmission (COTs) that control when event messages are generated and sent. TT# CHG09021

ProSoft Configuration Builder Version 2.2.1 (August 2010)

Detailed Reasons For Change

The following changes were implemented for ProSoft Configuration Builder (PCB), version 2.2.1 (August 2010):

For the MVI56-PDPMV1: Fixed an issue that caused conflicting indications of module operating status. Before the fix, once a configuration file had been downloaded using CIPconnect™, PCB would show "Module is running". But, the module OK LED would still be RED and the APP Status LED would still be ON for some additional time, indicating that the module was not running. It was found that modules take a little bit longer than anticipated to return to RUNNING status after a download using CIPconnect. This display timing issue has been fixed is for all modules that use CIPconnect. TT# BUG08965

For the MVI56-PDPMV1: Fixed a problem on the MVI56-PDPMV1 that if user hits ESC (Warm Boot) key on the diagnostic menu, it showed characters but module did not reboot. TT# BUG08968

For the MVI56E-MCM and MVI56E-MCMR: If the module is an MVI56E-MCM, PCB will no longer upload a configuration file if there is a mis-matched between the module type defined in the PCB configuration and the module type read from the module during a hardware version check, which is done at the beginning of the download process before the download can begin. This is because an MVI56E-MCM is mainly configured via ladder logic and uploading a mis-matched configuration file might impair module operation. TT# BUG08967

For MVI56E-FLN: This module may now be configured using PCB. TT# CHG08995

For MVI69-PDPMV1: The module now offers CIPconnect support for configuration and diagnostics. To use CIPconnect, the module must be installed in a Rockwell Automation® CompactLogix™ Programmable Automation Controller™ (PAC) system using a PAC with built-in Ethernet port, such as the 1769-L32E or 1769-L35E. TT# REG8051

For MVI69-104S: PCB now includes additional parameters for enhanced IEC-60870-5-104, Edition 2 support for 32-bit Bitstring data types and additional Causes of Transmission for monitored data types. TT# BUG08061

For PTQ-DNPS, PTQ-DNP, PTQ-DNPQ, and PTQ-DNPSNET: These modules may now be configured using PCB. TT# REG08052 and CHG08964

For PTQ-104S: PCB now includes additional parameters for enhanced IEC-60870-5-104, Edition 2 support for 32-bit Bitstring data types and additional Causes of Transmission for monitored data types. TT# REQ07861

For ProLinx 5201-104S-101M: This gateway may now be configured using PCB. TT# REQ07586

For the PCB: PCB now supports the Microsoft Windows 7 operating system (OS). TT# REQ7373

NOTE: To use PCB under the Windows 7 OS, you must be sure to install PCB using the "Run as Administrator" option. To find this option, right-click on the Setup.exe installer program icon. In the context menu, you will see the "Run as Administrator" option. Left-click to use this install option. Be aware, you must install using this option even if you are already logged in as an Administrator on your network or personal computer (PC). Using the "Run as Administrator" option will allow the PCB installer to create folders and files on your PC with proper permissions and security. If you do not use the "Run as Administrator" option, PCB may appear to install correctly; but you will receive numerous, repeating file access errors whenever PCB is running, especially when changing configuration screens. If this happens, to eliminate the errors, you will have to completely uninstall PCB and then re-install using the "Run as Administrator" option.

New Feature(s)

The following new features were implemented for ProSoft Configuration Builder version 2.2.1:

This version of ProSoft Configuration Builder (PCB) has been installed, run and tested on personal computers using the MicroSoft Windows version 7 operation system.

PCB now supports configuration and diagnostics on more modules and gateways than ever before. Recently added:

MVI56E-FLN (New Product) ProLinx 5201-104S-101M (New Product)

PTQ-DNP PTQ-DNPS

PTQ-DNPQ PTQ-DNPSNET

PCB now includes support and addition parameters for IEC 60870-5-104 Server modules, PTQ-104S and MVI69-104S.

Support for CIPconnect, a popular and convenient way to configure and monitor ProSoft products via Ethernet, has been added to the MVI69-PDPMV1 module, expanding PCB's communication options for that module.

For the MVI46-MNET: In the PCB configuration for this module, corrected M1 Write Size range to be 0 to 5000 words and corrected Word Input Offset range to be 0 to 4999 words. TT# BUG07526

For the MVI56-101M: Made session and sector handling configuration easier to accomplish. PCB will now automatically update the Session Sections whenever the Session Count is changed. TT#CHG04417

For the MVI56-DNP: There had been some problems when downloading a configuration from PCB or when downloading an exported .cfg file via a terminal emulator program like HyperTerminal. Those issues have been corrected. TT#BUG07523, BUG 07524

For the MVI56-PDPMV1: Made the module setup for FLEX mode easier for the user. PCB will automatically adjust values in the L5X rung export file to match FLEX mode Input and Output Image Size settings. TT# REQ07360

For the MVI56-PDPMV1: PCB downloads had been failing due to a timeout when downloading the configuration to the module if the Use Legacy parameter is set to No and the correct ladder is not present. This has been corrected. TT# BUG07517

For MVI56-PDPMV1 and MVI56E products: CIPconnect Ethernet downloads occasionally timed-out while downloading large configuration files. This problem has been fixed. TT# BUG07514

For MVI69-PDPMV1: Corrected a problem which had been causing the first configured Slave's I/O map to be lost during a download. TT# BUG07510

For PTQ-101S: The parameter, Backup Port Handshaking, has been given a default value of None. TT# CHG07525

For PCB: After an upload or download, PCB will no longer automatically, and without notifying the user, silently save the configuration file on the user's PC. It will, instead, now prompt the user to save the configuration file when exiting PCB. TT# CHG07516

For PCB: The options for saving Export Files when exiting PCB have been changed. TT# CHG07278

For PCB: In the PCB Main Screen - Info Pane upper left, the date format of Last Download and Last Change display items was changed to show a more familiar and easier-to-read format. Example: New format "Feb. 5, 2010" instead of old format "2010.02.05". TT# CHG07518

New Feature(s)

Adds auto-adjustment of Input and Output Image sizes and ladder logic Limit instructions, as well as automatic update and export of RSLogix 5000 .L5X Rung Import files for Flex Mode applications with MVI56-PDPMV1 modules. These enhancements make it much easier to use the Flex Mode logic with this inRAx module.

For 5102-MCM4-ADM4 and 5102-MCM4-DFCM4, when a port is already set to one of the protocol, right click the protocol, now, the context menu should have an option, Select Protocol, to select another protocol (TT# ISSBUG05524)

STATIC ARP TABLE parameters added for these products:

MVI56-MNET

MVI56-MNETC

MVI56-MNETR

MVI69-MNETC (TT# ISSBUG05554)

For all ProLinx products, in Section CommonNet, E-MAIL item has been removed (TT# ISSCHG05559)

For the following ProLinx products, the Modbus Enable parameter inadvertently allowed only 0, 1, or 2 but not 3. Now it allows 0, 1, 2, or 3.

Fixed issue: When importing a .CFG file into PCB 2.0.14.12, whether you select the correct module name before or after selecting "Load config file", the wrong module type is in the project tree. Also, when uploading an config DFNT-ASCII from the ProLinx, the upload config has only one ASCII port (TT# ISSBUG05002)

ProLinx PDPMV1 Memory Map display is fixed and is now correctly displayed data address according to configuration parameters (TT# ISSBUG05126)

Now allows for ProLinx MBP products to configure up to 200 Modbus Plus commands (TT# ISS05186)

Fixed PCB to allow configuration of up to 100 commands for MVI46-MNET module (TT# ISSBUG05192)

New Feature(s)

ProSoft Configuration Builder Version 2.1.2

Detailed Reason(s) For Change

The following changes were implemented for ProSoft Configuration Builder version 2.1.2:

Modified diagnostics screen to new look & feel. There is a new menu and toolbar buttons on this screen. For MVI56 Rev. 2 products, the option to display Rev. 2 information is shown in a treeview on the left-hand side of the screen.

Module(s) Affected

New Feature(s)

For MVI56E products, there’s a new option to invoke the ProSoft Discovery Service to browse for MVI56E devices on the Ethernet network. It’s available from the Main screen on the module’s right-mouse-click popup menu, on the Diagnostic screen’s Diagnostic Connection window, and from the Upload/Download window.

ProSoft Configuration Builder Version 2.0.15

Detailed Reason(s) for Change

The following changes were implemented for ProSoft Configuration Builder version 2.0.15:

MVI56-FLN, MVI69-FLN: Allowable Minimum Frame Interval (MFT) parameter. The module cannot join the network when this parameter is configured with a value less than 20. Changed minimum value from 0 to 20 (TT# ISS04600)

Added configuration support for the following modules:

5201-DFNT-EGD (TT# ISS04575)

5209-DFNT-CCLink (TT# ISSCHG01349)

Added extended CIPconnect function to be able to remotely connect to MVI56-PDPMV1. With this release CIPconnect will be able to remotely "bridge" over ControlNet and other CIP based interfaces.

Important: This functionality requires Microsoft .NET 2.0 Framework. ProSoft Configuration Builder installer will prompt you to install .NET 2.0 if this component is not already present. If you do not wish to use the CIPconnect Path Editor, you can skip this portion of the installation. If you choose at a later time to use CIPconnect, please rerun the ProSoft Configuration Builder installer to install .NET framework v2 then ignore if the installer prompt to alter PCB installation.

Module(s) Affected

New Feature(s)

Added extended CIPconnect function to be able to remotely connect to MVI56-PDPMV1. With this release CIPconnect will be able to remotely "bridge" over ControlNet and other CIP based interfaces.

Important: This functionality requires Microsoft .NET 2.0 Framework. ProSoft Configuration Builder installer will prompt you to install .NET 2.0 if this component is not already present. If you do not wish to use the CIPconnect Path Editor, you can skip this portion of the installation. If you choose at a later time to use CIPconnect, please rerun the ProSoft Configuration Builder installer to install .NET framework v2 then ignore if the installer prompt to alter PCB installation.

PDPMV1 modules (MVI46, MVI56, MVI69, PTQ, ProLinx): PROFIBUS data mapping now displays End Address column to easily determine End Address / End Offset of each data array. This is a display only item, which should not affect exporting data (TT# ISSREQ02429).

New Feature(s)

ProSoft Configuration Builder Version 2.0.13

Detailed Reason(s) For Change

The following changes were implemented for ProSoft Configuration Builder version 2.0.13:

For PTQ-PDPMV1 HSBY and other modules with IP-base download/upload capability, PCB now has a button on the download screen to test the Ethernet connection(s) before beginning the download function (TT# BUG01218)

In PTQ-PDPMV1 Hot Standby application, PCB now downloads configuration for the Passive master first and then downloads to active master, this is to solve an issue found when Bus Baud rate changed master will not start communicating with configured slaves (TT# CHG02114)

The default value of the PTQ-PDPMV1 parameter Duplex/Speed Code has been changed from Auto-Negotiate to 10MB/Half-Duplex. This new default setting helps reduce the amount of traffic handled by the module on high-traffic networks. Further information about this topic can be located at the following web address:

ProSoft Configuration Builder Version 2.0.12

Detailed Reason(s) For Change

The following changes were implemented for ProSoft Configuration Builder version 2.0.12:

ProLinx 101S modules have a new command control block that allows a remote node (second protocol) to request the following tasks from the 101S driver:

GetEventBuffer

Send timestamp event

Set Clock

Get Clock

To support these features the following new parameters were added:

DB Input Window Start

DB Output Window Start (TT# ISS01952)

ProLinx MNET Client applications: Corrected error with Coil command and reg count parameter. If the command is Coil command and the reg count is set to a value higher than 125, the PCB reported it as an error. It allows the reg count to be 1 to 800 (TT# ISSBUG01935).

Using a High serial port (higher than 10) with MVI56-PDPMV1 - diagnostics feature, produced the following error to the screen:

BX_PutString : Error message send | Step : -1

BX_PutString : Error message send | Step : -1

BX_PutString : Error message send | Step : -1

BX_PutString : Error message send | Step : -1 (TT# ISSBUG01948)

For the PTQ-PDPMV1 module, the txt file containing the project variables for concept will also assign the CRC values to the PTQ output status variables. Therefore, the SETCRC function block is an optional feature for this and later PCB versions(TT# ISSCHG01961).

The MBP driver parameter Master Command Timeout Preset display was truncated. The parameter area is now expanded to allow full display (TT# ISSBUG01213)

Now the user can install PCB with administrator privileges and run PCB with user privileges (TT# ISSBUG01995).

The 103M modules will now used a fixed configuration structure with 16 sessions and 3 sectors per session (regardless on the value set for the Session Count parameter). This overcomes specific issues concerning the update of the configuration structure depending on the Session Count value.

The module will ignore the extra sessions that are not used (higher than set by Session Count), but these will be always downloaded to the module (TT# ISSBUG00581).

PCB writing configuration files for the PTQ-PDPDMV1 sent directly to Compact Flash via PCB software now match CRC values with files sent to the PTQ module directly (TT# ISSBUG01866).

PTQ-PDPMV1 includes the Cyclic IO Starting address in the status block (TT# ISSREQ01978).

ProSoft Configuration Builder for PROFIBUS changes.

PTQ-PDPMV1 includes the Cyclic IO Starting address in the status block (TT# ISSREQ01978).

Fixed issue with PCB for PROFIBUS that would prevent the import of "User prm data" certain GSD files that contains comments at the end of line. Problem fixed in PCB for PROFIBUS version 1.4.1.2 (TT# ISSBUG01732)

ProSoft Configuration Builder for PROFIBUS was stopping the PROFIBUS Master after Monitor Modify mode was stopped even if the processor was in RUN mode (TT# ISSBUG01733).

New configuration parameter was added to allow the user to control the operation of the master. If the master was stopped by mail box message from the processor while the user was on online using monitor/modify the master will not stop but when the user goes off line the master will stop and the user accidentally went online again the Master will start communicating again with slaves, but if user chooses to keep the master in stop parameter will prevent the master from starting up and communicating with slaves.

New Feature(s)

The previous PCB versions would only allow the user to enter parameter values if these were within specific allowed ranges (corresponds to checkbox cleared).

If the checkbox is set, the range checking functionality will be disabled and the user can enter values within any range.

It allows the user to overcome very specific situations where PCB might not allow the setting of valid values (but out of the allowed range checking) (ISSBUG01367).

Support added for new module 5201-MNETC-DFNT (TT# ISS02080).

PCB now supports Zmodem file transfers for the following MVI56 modules.

MVI56-MNET

MVI56-MNETC

MVI56-MNETR

MVI56-PDPS

Known issue: due to the configuration file size for the MVI56-MNETC, the download functionality of PCB might need to be manually retried occasionally (TT# ISSREQ02047).

For the PTQ-PDPMV1 module, the txt file containing the project variables for concept will also assign the CRC values to the PTQ output status variables. Therefore, the SETCRC function block is an optional feature for this and later PCB versions (TT# ISSCHG01961).

The data map functionality of the ProLinx modules allowed the remapping from address 18000. This value was increased to 100000 to guarantee compatibility with existing modules (TT#ISS01931)

When a new 103M module is created, PCB sets a fixed number of 16 sessions and 3 sectors per session. The actual session and sector count can still be changed by the user, but the number of visible sessions and sectors will remain the same. This is to prevent previous issues concerning the dynamic change of session and sectors (TT#BUG1592)

Fixed default DH-485 ProLinx module name once a new module is created. The previous version would display only "D" instead of "DH-485" (TT#BUG1719)

The command paste functionality section (applied for all modules that contain a command-like structure) now creates a new command with the copied information. The previous version would force the user to create a new command a paste the copied command over that one (TT#BUG1811)

The exported DTY file contained registers in the status input type that were not used if mailbox copy was not selected (Mailbox Messaging=N). The following registers were removed from the .DTY file (status input data type) once mailbox is not selected:

Watchdog Reset Value: Value to set Profibus outputs to on timeout condition

The watchdog functionality allows the module to set the PROFIBUS output registers to a pre-defined value when a communication failure occurs. The watchdog is implemented through the monitoring of a specific database register (configured through the Watchdog Register parameter). The remote node should write a new value to this database register faster than the timeout period (configured through the Watchdog Timeout parameter). If this time period elapses but no change is detected then the module will force all PROFIBUS output registers to a specific value (configured through the Watchdog Reset Value parameter).

In order to disable this functionality set the Watchdog Register to -1 (TT#ISS01787).

ProLinx MNET modules support a configurable ARP Timeout value, through a new configuration parameter ARP Timeout.

This parameter defines the minimum time period (milliseconds) that the module will wait for an ARP response from a node. During that time the module will not communicate with any nodes. If the module does not receive an ARP response within this period of time it will proceed communicating with other nodes for 30 seconds until the next ARP request attempt. Configurable range is between 1 and 65535 milliseconds (TT#ISS01788).

ProLinx DFNT modules now support the unconnected client functionality. Includes new [DFNT UClient x] section and [DFNT UClient x Commands]. These sections follow the same syntax as the [DFNT Client x] and [DFNT Client x Commands] sections (TT# ISS01834).

ProLinx 104S modules have a new command control block that allows a remote node (second protocol) to request the following tasks from the 104S driver:

GetEventBuffer

Send timestamp event

Set Clock

Get Clock

To support these features the following new parameters were added:

DB Input Window Start

DB Output Window Start (TT#ISS01757)

Added support for the following ASDU types:

58: Single command with time tag CP56Time 2a

59: Double command with time tag CP56Time 2a

60: Regulating step command with time tag CP56Time 2a

61: SetPoint command, normalized value with time tag CP56Time 2a

62: SetPoint command, scaled value with time tag CP56Time 2a

63: SetPoint command, short floating point with time tag CP56Time 2a

107: Test command with time tag CP56Time2a

To support this feature a new parameter Command Delay Timer was included (TT#ISS01784).

ProSoft Configuration Builder Version 2.09

Detailed Reason(s) For Change

The following changes were implemented for ProSoft Configuration Builder version 2.0.9:

PCB supports all parameters available for ProLinx 5102-MCM-101S products.

PCB now performs range checking for the PDPS-104s ProLinx driver allowing for a new limit for all data types (Point column) from 64000 to 16777215.

PTQ-PDPMV1 user can issue a module Coldboot "reset" function over backplane with module version 1.19

PTQ-PDPMV1 version 1.19 firmware adds a new parameter Duplex/Speed. This parameter allows user to set the connection speed manually between 10Mbps Full/Half-duplex and 100Mbps Full/Half duplex or to Auto negotiate baud rate with HUB or switch. Default value is Auto Negotiate.

Module(s) Affected

New Feature(s)

ProSoft Configuration Builder Version 2.0.6

Detailed Reason(s) For Change

The following changes were implemented for ProSoft Configuration Builder version 2.0.6:

The ProSoft Configuration Builder option "Check for Updates on startup" has been temporarily disabled.

The "Email Log to Support" button on the ProSoft Configuration Builder Diagnostics dialog box has been temporarily disabled.

The operation of the "Export Module Configuration" menu command has been temporarily disabled.

The PROFIBUS Master (ProLinx PDPM) had information regarding the swap input bytes and the swap output bytes that were saved to an exported file as 0 or 1 rather than "Yes" or "No". This has been corrected.

If ProSoft Configuration Builder was installed to a location different from the default location (C:\Program Files\ProSoft Technology Inc\PCB) PCB sometimes was not able to find its database files. PCB now uses the installation path in the system registry to determine the location of its database files.

New Feature(s)

Detailed Reason(s) For Change

The following changes were implemented for ProSoft Configuration Builder version 2.0.5

Problems related to the automatic update of the PCB and its databases have been resolved.

PCB was not correctly exporting the XSY file.

Removed the SETCRC function block from the XFM file used by Unity Pro.

When a user tried to copy and paste a hot standby module, PCB pasted a stand-alone module instead. This problem has been fixed.

Fixed a bug affecting some non-US English versions of Microsoft Windows, where PCB accesses various files from the hard-coded "\Program Files" path. Instead, the PCB now uses the functional equivalent of this folder in non-US English version of Windows.

Module(s) Affected

New Feature(s)

When a user Right clicks on Ethernet configuration to perform download, Ethernet is no longer an option in the download window.

In the Main download window, a user can change the IP address dynamically

Implements comments for DTY file in Concept.

Added XFM file generation to use with Unity. A new XFM file is generated each time the user uses the PCB to create a Unity XSY file. Also, when the PCB saves information when it closes, the exported XSY files also have corresponding XFM files.

Detailed Reason(s) For Change

Issue fixed: ppf extension files are now registered to with the PCB.exe file installation. With this version the user can double-click on the .ppf file to open it with PCB.

Issue fixed: incorrect warning message when entering an invalid parameter value (for example: a parameter value out of range). Also once this window is displayed the user can click OK to continue with setting other parameters.

Issue fixed: new parameter set as invalid at existing PCB project. When a new parameter is added to the PCB database an existing project will now accept it by setting its default value.

Issue fixed: for PTQ-PDPMV1 module, CRC value is correctly calculated during exporting of files (issue found on PTQ version 2.0.2 Build 25).

Module(s) Affected

New Feature(s)

Added file export functionality. The software generates upon closing the project a structure of folders that contains configuration files for all configured modules. For the PTQ-PDPMV1 module the software will also export the processor files for Unity Pro and Concept ladder program support.

The files will be exported during both conditions:

Select Project/Export Files

Exit PCB and confirm that the changes will be saved (if the project is not saved then PCB will not export the files).

Detailed Reason(s) For Change

While configuring PROFIBUS slaves the slaves comments are not correct once you open and close a project (NT127-4)(H 2.26)

At PCB for PROFIBUS the GSD Viewer functionality (Tools-GSD Viewer) now it correctly displays the GSD file for the selected PROFIBUS slave (NT127-2)

SR1-6901071: When online with the ProSoft PDPMV1 module through the PCB software and I try to access a DP slave through Siemens DP/PA link and an error message saying "memory location 00x000000 is not accessible... " is displayed and closes PCB Master software has been corrected (H 2.04)

Error while shifting of address offset in PCB for PROFIBUS user can come across this error indicating GSD_DLL.DLL in Function GetFirst_UserPRMDataREF_TextNetTool Workaround: Close PCB for PROFIBUS screen and start again.

Module(s) Affected

New Feature(s)

In Windows OS ’start Menu' the name displayed for ProSoft Technology Configuration Builder was ProSoftConfigBuilder and is now changed to "ProSoft Configuration Builder" with spaces (2X 1.6).

The previous PCB install folder of '\program files\ProLinx\ProLinxConfig\' was changed to '\Program Files\ProSoft Technology Inc\PCB'. The file name will change from ProLinxConfig.exe to PCB.exe (2X 1.14, 2.2).

PROFIBUS master configurator will now automatically insert the master icon in the Busview window.