ProSoft Technology, Inc. PROFIBUS comDTM Read Me
PROFIBUS comDTM Version 1.0.1.5 with Install Version 1.02.0002 Readme File
Last updated on 3/2/2009
This README file contains information you should know before you install or upgrade to comDTM Version 1.0.1.5 with Install Version 1.02.0002. This file also contains information that may not be available in other ProSoft documentation. Visit ProSoft Technology for the most up-to-date information about the comDTM.
Table of Contents
comDTM Compatibility
The following system requirements apply to comDTM.
comDTM installation instructions are provided in the comDTM 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.
comDTM 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 PentiumIII (550mhz)
Return to Contents
Introduction
The PROFIBUS comDTM enables connection between bus-connected field devices such as flow meters, actuators etc. and their associated slave DTMs through ProSoft related module. This is accomplished using the FDT technology, the ProSoft Technology PROFIBUS DPV1 master modules and the ProSoft PROFIBUS comDTM.
Typical FDT frame applications are Fieldcare (Endress & Hauser), PACTware (PACTware association) or fdtCONTAINER (MM-Software).
The ProSoft Technology PROFIBUS DPV1 master modules supports Class 1 and 2 services thereby allowing for cyclic Class 1 services to co-exist with the acyclic comDTM Class 2 services on the same network.
The PROFIBUS comDTM allows the FDT container configured DTM's to connect to their associated field devices via a serial or Ethernet interface. Ethernet communications are recommended for speed, and when multiple connections are required.
Note: PTQ-PDPMV1 supports Ethernet only. Please do not use the serial port connection in the communication transport.
MVI56-PDPMV1 supports Ethernet through CIPCONNECT™ with a 1756-ENBT card in the same rack as the MVI56-PDPMV1 (firmware version 1.28.000 or later and comDTM version 1.0.1.5 with install version 1.01.0003 or 1.02.002. For information on how to check the comDTM version and install version, refer to Verifying the comDTM Version and comDTM Install Version in the comDTM Quick Start Guide.
The ProLinx PDPMV1 module supports comDTM access through Ethernet.
Other MVIXX-PDPMV1 modules provide support only for serial. There is only a physical serial port on the MVI.
Return to Contents
System Recommendations
- Windows 98 SE, NT 4.0, 2000, XP
- 2 MBytes free Hard Disk space
- Pentium IV CPU
- 256 MB RAM
- FDT 1.2.1 compliant FDT frame application installed
- Ethernet NIC or
- Serial interface port
- ProSoft Technology Profibus DPV1 master module
Return to Contents
Installation Instructions
- Install a standard FDT frame application, such as Fieldcare, PACTware or fdtCONTAINER.
- Install all desired field device DTMs.
- Install the comDTM. Select "Install PROFIBUS comDTM" from the software CD menu. Review the Getting Started guide for complete installation instructions.
- Select the "Getting Started " from the software CD menu.
- If the ProSoft Technology Master module has not been configured, follow the module's Setup Guide to configure the module and Ethernet or Serial port settings.
- Review the Getting Started guide for comDTM startup instructions. Select "Getting Started" from the software CD menu.
- Check for revision updates on the ProSoft Technology web site for software updates - http://www.prosoft-technology.com or contact Technical Support at 661-716-5100
Important: CIPconnect 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
Instructions on Upgrading the ProSoft Technology COM-DTM
If your PC currently has installed ProSoft Technology COM-DTM version 1.0.0.10 please uninstall this version through "Control Panel/Add or Remove Programs" before installing a newer version.
For any versions later than 1.0.0.10 you can run the setup for the new upgrade (there is no need to uninstall the current version through Control Panel).
Return to Contents
Upgrade Information
Detailed Reasons For Change
- Modified abmdpv.dll to allow diagnostic information for PCB via CIPconnect.
Return to Contents
New Features
- Now allows connection to allow diagnostic information for PCB via CIPconnect.
Return to Contents
Known Issues & Limitations
Return to Contents
Previously Released versions of ProSoft PROFIBUS comDTM
Version 1.0.1.5, Install version 1.02.0001
Detailed Reasons For Change
- Modified abmdpv.dll to allow Ethernet communication through a 1756-ENBT card to the MVI56-PDPMV1 through the backplane of a ControLogix PLC. This feature is only supported for MVI56-PDPMV1 firmware version 1.28.000 or later.
Return to Contents
New Features
- Option to now configure the PROFIBUS comDTM to allow communications through a rack mounted 1756-ENBT to the MVI56-PDPMV1 using CIPCONNECT™.
Return to Contents
Known Issues & Limitations
Return to Contents
Version 1.0.1.5 (January 9, 2007)
Detailed Reasons for Change
- Faulty disabled menu items Configuration, Offline Parameter and Online Parameter in combination with the frame application fdtCONTAINER 2.2.
Return to Contents
New Features
- The option "Selection Communication Interfaces" was changed, now the software doesn't use the PDPMPtDg.dll library any longer. To create/change a transport path an own FDT conform OCX was integrated. So the extra window will not be displayed during the communication interface configuration.
Return to Contents
Known Issues and Limitations
- Adding the ComDTM to a project without previously installing any DTM libraries may cause an initialization error. The DTM libraries must be installed prior to adding the comDTM to the FDT container project (the comDTM can be installed though)
- At the transport path configuration window: selecting the Delete button while there are no communication paths selected may crash Pactware
- The Ethernet connection implements UDP which dynamically allocates a random local UDP port for every connection. This implementation will limit the possibility of using most serial-Ethernet converters to access the MVIxx-PDPMV1 serial port through a PC Ethernet connection. Most converters will require the configuration of a fixed UDP port which is not available for the current implementation.
Return to Contents
Version 1.0.1.3 (September 20, 2006)
Detailed Reasons For Change
- Fixed reconnect issue after interrupting Ethernet/Serial connection (the module does not need to be rebooted after communication interruption)
- Resource allocation problem while adding slaves in MultiUser based FDT frames fixed.
- Handling of simultaneous connections to different modules corrected.
- Installation error during software upgrade fixed. Now when upgrading from version 1.0.1.3 to a more recent version it is no longer required to uninstall the version first.
- Correct version is displayed at FieldCare (the previous version used a specific internal file for displaying the version).
- The new default IP address is 192.168.0.100 (instead of 0.0.0.0) and the new default COM port is COM1 (instead of COM0). This prevents the user to select an invalid transport path and crash the FDT container.
- After deleting a communication path the Communication Interface Selection window will no longer display any record for the path.
- Warning text before starting the transport path configuration utility changed from "Important informations in the FDT-Container may be covered" to "Important informations in the FDT-Container may be hidden".
New Features
- Added support for serial connection to MVIxx-PDPMV1 modules (please refer also to Known Issues & Limitations section for observation regarding the use of Ethernet-serial converters)
- User administration implemented: depending on the FDT frame logged in user level, different configuration functions are enabled/disabled.
- Automatic network setup in connection with on line scan: no address dialog is opened if online scan and automatic network configuration is used. The DTM address is automatically assigned from the scanned live list instead.
- The list of transport paths in the comDTM's configuration utility is automatically updated after closing the transport path configuration utility (it is no longer required to select the Refresh option)
Known Issues
- Adding the ComDTM to a project without previously installing any DTM libraries may cause an initialization error. The DTM libraries must be installed prior to adding the comDTM to the FDT container project (the comDTM can be installed though)
- At the transport path configuration window: selecting the Delete button while there are no communication paths selected may crash Pactware
- The Ethernet connection implements UDP which dynamically allocates a random local UDP port for every connection. This implementation will limit the possibility of using most serial-Ethernet converters to access the MVIxx-PDPMV1 serial port through a PC Ethernet connection. Most converters will require the configuration of a fixed UDP port which is not available for the current implementation.
Return to Contents
Version 1.0.0.10 (September 7, 2006)
Known Issues
- Deleting a communication path will not clear it from the Communication Interface Selection window (displayed as Not Used).
- Installing a newer version over version 1.0.0.10 will cause an error message during installation procedure. Version 1.0.0.10 needs to be uninstalled first (through Control Panel) before installing a newer version.
- Supports only one COM-DTM connection for a FDT container session through auto-scan (to automatically detect the connected slaves). Using more than one connection will cause the connections to mix devices.
- Auto-scan option forces the user to enter the slave addresses for each slave (Create Network option for FieldCare).
- Selecting an IP address of 0.0.0.0 (default but invalid) causes the FDT container to crash.
- Disconnecting the cable during communication will require the module to be rebooted to re-initialize communication.
Return to Contents
August 22, 2006
Updated license agreement in documentation.
Return to Contents
July 7, 2006
Updated documentation to clarify license agreement with regard to hot standby and server installations. No change to software.
Return to Contents
Copyright © ProSoft Technology, Inc. 2009. All Rights Reserved.