ProSoft Configuration Builder Read Me
ProSoft Configuration Builder Version 2.1.1
Readme File
This README file contains information you should know before you install or upgrade to ProSoft Configuration Builder Version 2.1.1. 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
PTQ-PDPMV1: The .XSY, .XFM files generated by versions of ProSoft Configuration Builder newer than 2.0.2 and used by UnityPro XL are NOT COMPATIBLE with earlier versions of .XSY files generated by PCB (older than 2.02). The new .XSY, .XFM files generate new data types and function blocks for Unity Pro (please see PCB Version 2.0.2 for specific details. The current PCB Version is Version 2.1.1.
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.
Table of Contents
ProSoft Configuration Builder: Compatibility
The following system requirements apply to ProSoft Configuration Builder.
ProSoft Configuration Builder installation instructions are provided in the ProSoft Configuration Builder Setup and Installation Guide.
Note: System requirements in this document are subject to change and do not represent a commitment to support any particular software or hardware.
ProSoft Configuration Builder Operating Systems Tested
- Windows XP Professional Ver.2002 Service Pack 2 512 MB RAM Pentium 4 (2.66ghz)
- Windows 2000 Ver.5.00.2195 Service Pack 2 522.544 MB RAM Pentium III (550mhz)
Return to Contents
Upgrade Information
Detailed Reason(s) For Change
The following changes were implemented for ProSoft Configuration Builder version 2.1.1:
- Added new parameter for PTQ-PDPMV1: Non-Transfer Area Register. This parameter is used in Hot Standby installations. (TT# ISSREQ04641)
- Added configuration support for new product 5604-RIO-PDPMV1 (TT# ISS04948)
- Fixed problem with File Server Size of 5202-DFNT-MCM4. (TT# ISSBUG04999)
- PCB used to incorrectly allow the user to add up to 100 commands for the MVI56-MNETC. This number is only valid for the MNET, not the MNETC. (TT# ISSBUG05001)
- Added new parameters for 5105-103M-PDPS: Use database paging, Enable passtrhough. (TT# ISS05004)
- Removed non-supported parameter "Enable Database Output" for MVI46-N2, MVI69-N2 and MVI71-N2. (TT# N/A)
- 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. (TT# BUG05002)
Return to Contents
Module(s) Affected
Module
|
Module Firmware Version
|
PCB Version
|
PTQ-PDPMV1
|
1.29
|
2.1.1
|
5604-RIO-PDPMV1
|
2.46
|
2.1.1
|
MVI56-MNETC
|
1.10
|
2.1.1
|
5105-103M-PDPS
|
2.50
|
2.1.1
|
Return to Contents
New Feature(s)
- Added configuration support for the following modules:
Return to Contents
Known Problems and Limitations
CHOOSE MODULE TYPE
- The "Web Option Installed" check box is no longer available on the "Choose Module Type" dialog box for ProLinx modules.
OPTIONAL SETTINGS
- The optional setting Check Firmware Version on Upload/Download is not currently enabled.
- The optional setting Check for Updates on Startup is not currently enabled.
DOWNLOADING CONFIGURATION TO MVI56-MNETC
- 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).
DRAG & DROP EXISTING XML FILE
- After drag and dropping existing XML file to PROFIBUS DP folder then PCB does not inform about the requirements to save the file. This prevents the download of the configuration file. Workaround: Open ProSoft Configuration Builder for PROFIBUS screen and select File / Save to save the file.
PDPMV1 PRODUCTS: ERROR DURING DOWNLOAD
- During download of .ddb file, it was observed on rare occasions the display of "Error 11 Cannot open file". Workaround: Close the download window, and restart the download operation.
- During download via Ethernet, it was observed on rare occasion the module and the driver go into a constant exchange of messages without completing the download. Workaround: Cancel the download window, and restart the download operation.
ProSoft Configuration Builder for PROFIBUS
- PCB for PROFIBUS On-Line Error Error message: memory location is not accessible" during the monitor of a Siemens DP/PA link on the network. Workaround: No workaround known.
- 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.
- The download and upload of the configuration files through the serial port of the PTQ-PDPMV1 module may result in a timeout error. Only the ethernet port for download and upload of the configuration files as instructed by the User Manual.
- In the Hot-Standby system, the monitor/modify from PCB for PROFIBUS must be performed only when the processor is in run mode. In addition, the download configuration is not available at PCB for PROFIBUS (only at PCB).
- While uninstalling the software, it was observed under rare occasions the display of error 1719, The Windows Installer Service could not be accessed. Try to reboot the computer and retry to uninstall the software. Refer to http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q315346 for further information.
- During PCB serial download firmware for PROFIBUS (MVI56-PDPMV1) if the user selects another Windows, the progress bar might not be properly updated.
Return to Contents
Previously Released Versions of ProSoft Configuration Builder
ProSoft Configuration Builder version 2.1.0
Detailed Reason(s) For Change
The following changes were implemented for ProSoft Configuration Builder version 2.1.0:
- PROFIBUS data mapping now displays End Address column to easily determine end address of each data array. This is a display only item, which should not effect exporting data (TT# REQ02429).
- For PTQ-PDPMV1 Product, on Memory Map screen in PCB, it now shows start and end address of area mapped but not used (TT# CHG04689).
- Corrected display of MVI56-PDPMV1's data type End Offset
Corrected printout of MVI56-PDPMV1 memory map (TT# BUG04826) - ProLinx BACNET modules: BACNET Point Count range corrected to allow values of 1 to 25 (TT# 04870).
Return to Contents
Module(s) Affected
Module
|
Module Firmware Version
|
PCB Version
|
5201-DFNT-BACNET
|
2.50
|
2.1.0
|
5201-MNET-BACNET
|
2.50
|
2.1.0
|
PTQ-101M
|
1.15.001
|
2.1.0
|
PTQ-104S
|
1.19.002
|
2.1.0
|
PTQ-101S
|
1.40.002
|
2.1.0
|
PTQ-DFCM
|
1.45
|
2.1.0
|
PTQ-DNPSNET-Q
|
1.24.004
|
2.1.0
|
PTQ-PDPMV1
|
1.25.000
|
2.1.0
|
PTQ-PDPS
|
1.06
|
2.1.0
|
MVI46-101M
|
1.11.001
|
2.1.0
|
MVI46-104S
|
1.09.003
|
2.1.0
|
MVI46-BDW
|
1.03
|
2.1.0
|
MVI46-DNPSNET
|
1.31.001
|
2.1.0
|
MVI56-101S
|
1.29.001
|
2.1.0
|
MVI56-BDW
|
1.03
|
2.1.0
|
MVI56-PDPMV1
|
1.28.000
|
2.1.0
|
MVI69-101M
|
1.12.001
|
2.1.0
|
MVI69-101S
|
1.41.001
|
2.1.0
|
MVI69-DFCM
|
1.41
|
2.1.0
|
MVI69-HART
|
2.04
|
2.1.0
|
Return to Contents
New Feature(s)
- Added configuration support for the following modules:
- PTQ-101M
- PTQ-104S
- PTQ-101S
- PTQ-DFCM
- PTQ-DNPSNET-Q
- PTQ-PDPS
- MVI46-101M
- MVI46-104S
- MVI46-BDW
- MVI46-DNPSNET
- MVI56-101S
- MVI56-BDW
- MVI69-101M
- MVI69-101S
- MVI69-DFCM
- MVI69-HART
Return to Contents
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.
Return to Contents
Module(s) Affected
Module
|
Module Firmware Version
|
PCB Version
|
5201-DFNT-EGD
|
|
2.0.15
|
5209-MNET-CCLink
|
|
2.0.15
|
MVI56-FLN
|
|
2.0.15
|
MVI69-FLN
|
|
2.0.15
|
MVi56-PDPMV1
|
|
2.0.1.5
|
Return to Contents
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.
Return to Contents
ProSoft Configuration Builder Version 2.0.14
Detailed Reason(s) for Change
The following changes were implemented for ProSoft Configuration Builder version 2.0.14:
- Added configuration support for the following modules:
- 5209-DFNT-CCLink and 5209-MNET-CCLink (TT# ISSCHG01349)
- 5108-DFCM-HART, 5128-DFCM-HART, 5208-MNET-HART, 5228-MNET-HART, 5208-DFNT-HART, and 5228-DFNT-HART (TT# ISS04108)
- MVI46-DFNT, MVI46-GEC, MVI46-HART, MVI46-MNET, MVI46-MNETC, MVI46-PDPS, MVI56-104S, MVI56-DH485, MVI56-DH485R, MVI56-DNPSNET, MVI56-FLN, MVI56-GEC, MVI56-HART, MVI56-KOS, MVI56-MNETCR, MVI69-104S, MVI69-DFNT, MVI69-DH485, MVI69-DNPSNET, MVI69-GEC, MVI69-MCM, MVI69-MNET, MVI69-MNETC, MVI69-PDPS, PTQ-DFNT, PTQ-DH485, PTQ-GEC
- Updated GSD file, TELE09CD.GSD, for Schneider Altivar 71 Drive (TT# ISSREQ02546).
- 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).
- Added "Enable Database Output" parameter for PTQ-N2, MVI56-N2 and MVI69-N2 modules (TT# ISSTSK04240).
Return to Contents
Module(s) Affected
Module
|
Module Firmware Version
|
PCB Version
|
ProLinx PDPMV1
|
|
2.0.14
|
5108-DFCM-HART
|
|
2.0.14
|
5128-DFCM-HART
|
|
2.0.14
|
5208-MNET-HART
|
|
2.0.14
|
5228-MNET-HART
|
|
2.0.14
|
5208-DFNT-HART
|
|
2.0.14
|
5228-DFNT-HART
|
|
2.0.14
|
5209-DFNT-CCLink
|
|
2.0.14
|
5209-MNET-CCLink
|
|
2.0.14
|
5301-MBP-DH485
|
|
2.0.14
|
MVI46-DFNT
|
|
2.0.14
|
MVI46-GEC
|
|
2.0.14
|
MVI46-HART
|
|
2.0.14
|
MVI46-MNET
|
|
2.0.14
|
MVI46-MNETC
|
|
2.0.14
|
MVI46-PDPMV1
|
|
2.0.14
|
MVI46-PDPS
|
|
2.0.14
|
MVI56-104S
|
1.22.001
|
2.0.14
|
MVI56-DH485
|
|
2.0.14
|
MVI56-DH485R
|
|
2.0.14
|
MVI56-DNPSNET
|
1.28.001
|
2.0.14
|
MVI56-FLN
|
|
2.0.14
|
MVI56-GEC
|
|
2.0.14
|
MVI56-HART
|
|
2.0.14
|
MVI56-KOS
|
|
2.0.14
|
MVI56-MCMR
|
1.19.001
|
2.0.14
|
MVI56-MNETCR
|
|
2.0.14
|
MVI56-N2
|
|
2.0.14
|
MVI56-PDPMV1
|
|
2.0.14
|
MVI69-104S
|
1.19.001
|
2.0.14
|
MVI69-DFNT
|
|
2.0.14
|
MVI69-DH485
|
|
2.0.14
|
MVI69-DNPSNET
|
1.27.001
|
2.0.14
|
MVI69-GEC
|
|
2.0.14
|
MVI69-MCM
|
|
2.0.14
|
MVI69-MNET
|
|
2.0.14
|
MVI69-MNETC
|
|
2.0.14
|
MVI69-N2
|
|
2.0.14
|
MVI69-PDPMV1
|
|
2.0.14
|
MVI69-PDPS
|
|
2.0.14
|
PTQ-DFNT
|
|
2.0.14
|
PTQ-DH485
|
|
2.0.14
|
PTQ-GEC
|
|
2.0.14
|
PTQ-N2
|
|
2.0.14
|
PTQ-PDPMV1
|
|
2.0.14
|
Return to Contents
New Feature(s)
None for this release
Return to Contents
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:
- Added configuration support for the following modules:
- 5201-DNPSNET-DH485 (TT# ISS02410)
- PTQ-N2 (TT# ISSTSK00765)
Return to Contents
Module(s) Affected
Module
|
Module Firmware Version
|
PCB Version
|
ProLinx 5201-DNPSNET-DH485
|
|
2.0.13
|
PTQ-N2
|
|
2.0.13
|
Return to Contents
New Feature(s)
- Added configuration support for the following modules:
Return to Contents
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:
http://www.prosoft-technology.com/content/view/full/12409 (TT# 02282)
- For the PTQ-PDPMV1 modules, the "Processor Network Memory Map" feature was indicating incorrect byte orientation for the status Byte Swap register. The previous PCB version would indicate: Byte Swap H = Input L = Output Data
This version indicates: Byte Swap H = Output L = Input Data. (TT# 02287)
- ProLinx ASCII driver: The previous minimum baud rate value was 1200. The following options are now also included:
(TT# 02283)
- Added configuration support for the following modules:
- MVI56-WA-PWP
- MVI69-WA-PWP
- PTQ-WA-PWP
(TT# CHG01729)
Return to Contents
Module(s) Affected
Module
|
Module Firmware Version
|
PCB Version
|
All ProLinx Modules
|
All Firmware Versions
|
2.0.13
|
ProLinx ASCII Modules
|
All Firmware Versions
|
2.0.13
|
PTQ-PDPMV1
|
1.19
|
2.0.13
|
ProLinx MBP-PDPMV1
|
2.46
|
2.0.13
|
ProLinx DFNT-PDPMV1
|
2.46
|
2.0.13
|
ProLinx MNET-PDPMV1
|
2.46
|
2.0.13
|
MVI56-PDPMV1
|
1.27
|
2.0.13
|
MVI56-WA-PWP
|
|
2.0.13
|
MVI69-WA-PWP
|
|
2.0.13
|
PTQ-WA-PWP
|
|
2.0.13
|
Return to Contents
New Feature(s)
- The MVI56-PDPMV1 module now accepts configuration and PROFIBUS network monitor through the 1756-ENBT card. This feature requires MVI56-PDPMV1 firmware version 1.27.000 or later.
In order to support this feature a new option (1756-ENBT) is available when selecting the MVI56-PDPMV1 port. The user must also select the slot number where the MVI56-PDPMV1 is located.
Notes:
- The 1756-ENBT card must be located at the same rack as the MVI56-PDPMV1 module.
- This version supports a single connection at a time.
(TT# REQ0230)
Return to Contents
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).
- Included RS-Interface parameter for Prolinx MCM modules (TT# ISSQRY02058).
- 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.
Module(s) Affected
Module
|
Module Firmware Version
|
PCB Version
|
All ProLinx Modules
|
All Firmware Versions
|
2.0.12
|
PTQ-PDPMV1
|
1.19
|
2.0.12
|
MVI56-MNET
|
|
2.0.12
|
MVI56-MNETC
|
|
2.0.12
|
MVI56-MNETR
|
|
2.0.12
|
MVI56-PDPS
|
|
2.0.12
|
MVI56-PDPMV1
|
|
2.0.12
|
Return to Contents
New Feature(s)
- New option "Check to disable range checking functionality" (Tools-Option).
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).
Return to Contents
ProSoft Configuration Builder Version 2.0.11
Detailed Reason(s) For Change
The following changes were implemented for ProSoft Configuration Builder version Version 2.1.1:
- The RBE option was removed from the Prolinx DFNT commands (enable field) because these modules do not support this feature (only applied to DFCM). (TT#ISS01850)
- Re-enabled "Email Log to Support" button on the PCB Diagnostics dialog box (TT#ISSCHG01216).
- 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:
MailInQueue : WORD;
MailOutQueue : WORD;
AlarmQueue : WORD;
LastOutMailID : WORD;
CurrInMailCtr : WORD;
CurrAlarmCtr : WORD; (TT#ISSBUG01920)
Module(s) Affected
Module
|
Module Firmware Version
|
PCB Version
|
ProLinx PDPM Modules
|
See table below
|
2.0.11
|
ProLinx MNET Modules
|
See table below
|
2.0.11
|
ProLinx DFNT Modules
|
See table below
|
2.0.11
|
ProLinx 104S Modules
|
See table below
|
2.0.11
|
PTQ-PDPMV1
|
1.19
|
2.0.11
|
PDPM
Module
|
Module Firmware Version
|
x104-DNPS-PDPM
|
2.44
|
x204-MNET-PDPM
|
2.46
|
x204-104S-PDPM
|
2.46
|
x104-PDPM-MCM
|
2.45
|
x104-DFCM-PDPM
|
2.47
|
x104-DH485-PDPM
|
2.46
|
x604-RIO-PDPM
|
2.46
|
x304-MBP-PDPM
|
2.44
|
x204-DNPSNET-PDPM
|
2.45
|
x204-WEB-PDPM
|
2.44
|
x104-101S-PDPM
|
2.46
|
6104-WA-PDPM
|
2.67
|
MNET
Module
|
Module Firmware Version
|
x303-MBP-MNET
|
2.45
|
x210-MNET-RIO
|
2.45
|
x201-MNET-DFNT
|
2.50
|
x205-MNET-PDPS
|
2.47
|
x207-MNET-HART
|
2.45
|
x201-MNET-DNPSNET
|
2.47
|
x201-MNET-DNPS
|
2.47
|
x201-MNET-DNPM
|
2.46
|
x201-MNET-DFCM
|
2.49
|
x202-MNET-DFCM4
|
2.49
|
x201-MNET-DH485
|
2.49
|
x201-MNET-BACNET
|
2.50
|
x201-MNET-ASCII
|
2.45
|
x202-MNET-ASCII4
|
2.45
|
x201-MNET-103M
|
2.49
|
x206-MNET-DEM
|
2.44
|
x201-MNET-101S
|
2.50
|
x201-WEB-MNET
|
2.45
|
6201-WA-MNET
|
2.47
|
x201-MNET-MCM
|
2.57
|
x202-MNET-MCM4
|
2.57
|
x204-MNET-PDPM
|
2.46
|
x201-MNET-104S
|
2.46
|
DFNT
Module
|
Module Firmware Version
|
x201-DFNT-DNPSNET
|
2.46
|
x201-DFNT-DNPS
|
2.46
|
x201-DFNT-DNPM
|
2.46
|
x201-DFNT-DH485
|
2.49
|
x201-DFNT-DFCM
|
2.59
|
x202-DFNT-DFCM4
|
2.59
|
x201-DFNT-BACnet
|
2.50
|
x201-DFNT-ASCII
|
2.47
|
x202-DFNT-ASCII4
|
2.47
|
x201-DFNT-103M
|
2.50
|
104S
Module
|
Module Firmware Version
|
x210-104S-RIO
|
2.45
|
x201-104S-MCM
|
2.50
|
x201-104S-DH485
|
2.46
|
x201-104S-DFCM
|
2.48
|
x303-MBP-104S
|
2.45
|
x202-104S-DFCM4
|
2.48
|
x202-104S-MCM4
|
2.50
|
x201-MNET-104S
|
2.46
|
X204-104S-PDPM
|
2.46
|
Return to Contents
New Feature(s)
- ProLinx PDPM modules now support the watchdog functionality which requires the following parameters:
- Watchdog Register: DB register to monitor for change (-1=watchdog not used)
- Watchdog Timeout: .1 second intervals for watchdog timeout
- 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)
Return to Contents
ProSoft Configuration Builder Version 2.0.10
Detailed Reason(s) For Change
The following changes were implemented for ProSoft Configuration Builder version Version 2.1.1:
- PCB Export Files xsy file has been fixed to use the correct memory I/O offset (TT# BUG01541, Ticket #:001-00-035590)
- New parameters have been added to ProLinx 104S and ProLinx 101S modules. (TT# CHG01379)
The new parameters are:
- 104S modules:
New parameters for command qualifier settings (define behavior if undetermined qualifier is received):
- Default Command Qualifier
- Override Command Qualifier
- 101S modules:
New parameters for configuration of event report priority:
- Set Priority Queues
- M_SP_NA Priority
- M_DP_NA Priority
- M_ST_NA Priority
- M_ME_NA Priority
- M_ME_NB Priority
- M_ME_NC Priority
- M_IT_NA Priority
New parameters for counter Mode A mode configuration:
- Freeze Start Type
- Interval For Freeze
New parameters for Invalid bit settings:
- Cyclic Set IV Time
- IV Check Delay Time
- IV Fail Count
New parameters for SQ (sequence flag) register :
- M_SP_NA Sequence
- M_DP_NA Sequence
- M_ME_NA Sequence
- M_ME_NB Sequence
- M_ME_NC Sequence
- M_IT_NA Sequence
New data types M_ME_NC (monitored short-floating points) and C_SE_NC (short control floating points).
Also: All monitor points now contain a new parameter for the invalid bit setting (IV Bit)
- The DNPM driver in PCB now supports up to 40 slaves. This support was updated in Section Database version 39 (TT# BUG01359, Ticket # 001-00-037790)
- New parameter added in PCB for the PTQ-PDPMV1 that forces the Ethernet connection to the speed set by the user (TT REQ01228)
- Added parameter "Use Database Paging : N" to [Profibus Slave] Section of the configuration files for all ProLinx modules integrated with PDPS (TT# CHG01643)
- PTQ-PDPMV1 modules generating Concept DTY files using a NULL value entry for IN_DATAF and OUT_DATAF data types has been corrected. (TT# BUG01642, Ticket #: 001-00-038916)
Module(s) Affected
Module
|
Module Firmware Version
|
PCB Version
|
6201-WA-104S
|
2.44
|
2.0.10
|
6201-WA-DFCM
|
2.44
|
2.0.10
|
6201-WA-DFNT
|
2.46
|
2.0.10
|
6201-WA-MCM
|
2.44
|
2.0.10
|
6201-WA-MNET
|
2.46
|
2.0.10
|
6303-WA-MBP
|
2.44
|
2.0.10
|
ProLinx 101S Modules
|
See table below
|
2.0.10
|
ProLinx 104S Modules
|
See table below
|
2.0.10
|
ProLinx DNPM Modules
|
See table below
|
2.0.10
|
ProLinx PDPS Modules
|
See table below
|
2.0.10
|
PTQ-PDPMV1
|
1.19
|
2.0.10
|
101s
Module
|
Module Firmware Version
|
4101-DFCM-101S
|
2.46
|
4101-MCM-101S
|
2.45
|
4102-DH485-101S
|
2.45
|
4201-DFNT-101S
|
2.49
|
4601-RIO-101S
|
2.43
|
X102-DFCM3-101S
|
2.47
|
X102-MCM3-101S
|
2.50
|
X104-101S-PDPM
|
2.45
|
X105-101S-PDPS
|
2.48
|
X201-MNET-101S
|
2.48
|
X301-MBP-101S
|
2.44
|
104s
Module
|
Module Firmware Version
|
X201-104S-103M
|
2.50
|
X201-104S-DFCM
|
2.47
|
X201-104S-DH485
|
2.45
|
X201-104S-MCM
|
2.49
|
X201-DFNT-104S
|
2.46
|
X201-MNET-104S
|
2.45
|
X202-104S-DFCM4
|
2.47
|
X202-104S-MCM4
|
2.46
|
X204-104S-PDPM
|
2.45
|
X205-101S-PDPS
|
2.46
|
X205-TS-104S-PDPS
|
2.52
|
X210-104S-RIO
|
2.44
|
X303-MBP-104S
|
2.44
|
DNPM
Module
|
Module Firmware Version
|
4101-DNPM-DFCM
|
2.46
|
4101-DNPM-MCM
|
2.45
|
4201-DFNT-DNPM
|
2.45
|
4301-MBP-DNPM
|
2.43
|
4601-RIO-DNPM
|
2.44
|
X102-DH485-DNPM
|
2.46
|
X102-DNPM-DFCM3
|
2.47
|
X102-DNPM-MCM3
|
2.46
|
X102-DNPM-PDPS
|
2.44
|
X201-MNET-DNPM
|
2.45
|
DNPS
Module
|
Module Firmware Version
|
4101-DNPS-DFCM
|
2.46
|
4101-DNPS-MCM
|
2.44
|
4102-DH485-DNPS
|
2.45
|
4301-MBP-DNPS
|
2.42
|
4601-RIO-DNPS
|
2.43
|
X102-DNPS-DFCM3
|
2.47
|
X102-DNPS-MCM3
|
2.46
|
X104-DNPS-PDPM
|
2.43
|
X105-DNPS-PDPS
|
2.43
|
X201-DFNT-DNPS
|
2.45
|