Release 2.11 Standard AXE Primary Firmware is not intended for use on any 8521 Controller not licensed as a RTU.
|
|
- Erica Walton
- 6 years ago
- Views:
Transcription
1 GFK-2594 September 2010 PAC RT-DE RTU Controller Firmware release 2.11 for the 8521-RT-DE RTU Controller adds DNP3 protocol support with store and forward capability. For details, see New Features and Enhancements on page 2H3. Product Documentation 8000 System Specification Datasheet Instruction Manual INM8521 System Specifier s Guide SSG8002 Product documentation can be downloaded from 0H1Hhttp://support.ge-ip.com. Release Information This is the initial relase of the 8521-RT-DE module. Functional Compatibility Release 2.11 Standard AXE Primary Firmware is not intended for use on any 8521 Controller not licensed as a RTU. Subject PAC8000 Workbench Version Requirements DNP3 Control Package ISaGRAF Control Package Compliance Information Description Version 8.4 or later of PAC8000 Workbench is required for programming the PAC8000 RTU controller. This version of the AXE firmware is compatible with DNP3 Control Package version This version of the AXE firmware is compatible with ISaGRAF Control Package version For detailed installation and operating procedures, refer to the Instruction Manual INM8521.
2 2 PAC RT-DE RTU Controller GFK-2594 Problems Resolved by Revision 2.11 Note: This is the initial release of the RTU. References are in relation to Version 2.05 AXE firmware. Clean flash only cleaned master in duplex systems Previously when a clean flash was commanded, only the master controller processed it. Beginning with release 2.11 both controllers will clean flash when commanded in a healthy duplex system. AXE Reset Coil causes Railbus Mismatch In previous releases resetting the master controller using the xxx_axe_reset coil (8449) could cause one or both controllers to enter failsafe due to a railbus mismatch on the new master. This resulted in a Forced other, railbus mismatch event in the log. AXE Reset Coil causes DDA CRC Mismatch In previous releases resetting the master controller using the xxx_axe_reset coil (8449) could cause one or both controllers to enter failsafe due to a "DDA CRC SST different" error. Both controllers reset when using AXE Reset Coil In previous releases using the xxx_axe_reset coil (8449) sometimes reset both controllers in a duplex system. The coil is only supposed to reset the master controller. Abort due to TmrPIT FIT Interrupt rate In previous releases under heavy communication load or rarely under normal load a controller could abort with a log event indicating TmrPIT FIT Interrupt rate. This was due to an incorrect diagnostic check in the controller and has now been corrected. Additionally, the diagnostic check was changed to only log an event rather than abort. Abort due to TCP or UDP task timeout In previous releases a rollover of an internal clock could result in a controller aborting. The event log would indicate Abort due to SpvTaskTimeout for either a UDP or TCP task. The clock rollover occurs at approximately 13 months from the last reset or power cycle. Heavy Modbus traffic causes master abort or standby refresh In previous releases large numbers of Modbus reads could cause the master to abort or the standby to refresh in duplex systems. This could exhibit in multiple ways: The master would abort and would record an Abort by other processor log event. The standby would record an Abort master, rendezvous timeout xx ms at <xxxxxx> event. The master would record multiple Inter AXE Link Events such as IAL incomplete Rx standby diag [3] size 2 bytes and Inter AXE Link failed: retries Tx 0, Rx 1. Finally a Force standby, Inter AXE Link failed event would be recorded and the standby would refresh. The master would record a Forced other, railbus mismatch event and the standby would refresh. This issue is corrected in this release. IO modules go into failsafe when execution cycle is not consistent In previous releases wide variations in execution cycle time could occasionally cause IO modules to enter failsafe. When this occurred a <<slot no>> Enter failsafe detected event was logged.
3 PAC FT-MT Mass Termination Assembly 3 GFK-2569 New Features and Enhancements DNP Protocol Support DNP is implemented up to Level 3 and supports the select-before-execute (SBE) and communication sequence for control operation as well as the Store & Forward. Store and forward capability is provided for up to 15,000 DNP events. For additional information see the Help in the PAC8000 Workbench software. PAC8000 Logic Controller Functionality This release of the PAC8000 RTU supports the functionality provided by release 2.05 of the PAC LC-MT Logic Controller. Restrictions and Open Issues Standby offline due to "Refresh warm init took too long" following refresh or PQ rollover On rare occasions a Refresh warm init took too long event may occur after a persistent queue rollover (see operational note 3HPersistent queue Rollover Description on page 4H7) or a refresh. When this occurs the standby will be unable to refresh with the master and will remain offline. If this problem occurs the IO Configurator should be used to do a clean flash of the DNP Data Logging on the master with the standby powered down. The standby should then be able to refresh successfully when powered on. Standby offline due to CSC_CORRUPT for the persistent queue After power cycling the master, taking the standby from offline to online, or resetting the master via the xxx_axe_reset_coil (8449) the new standby may occasionally fail to refresh and report a Download Persistent Queue CSC_CORRUPT event. When this occurs the standby will be unable to refresh with the master and will remain offline. If this problem occurs the IO Configurator should be used to do a clean flash of the DNP Data Logging on the master with the standby powered down. The standby should then be able to refresh successfully when powered on Cause controller abort Occasionally a clean flash will result in an abort due to RtosFree NU_Deallocate_Memory NU_INVALID_MEMORY. If this failure occurs a subsequent clean flash will succeed. DDA CRC Control Package A Vars Different after firmware download Occasionally after firmware download, a DDA CRC Control Package A Vars Different event will be logged and the standby will go through an additional refresh. The second refresh will be successful.
4 4 PAC RT-DE RTU Controller GFK-2594 Controller aborts due to ISaGRAF strategy too large If the ISaGRAF strategy exceeds the maximum supported size the download will be rejected and an ISaGRAF strategy too large event is logged. When this occurs an attempt to clean flash may result in a controller abort due to MmuDtmLISR Data Address invalid. The abort will occur on both controllers in a duplex system. Further attempts to clean flash should be successful. If this problem is encountered reduce the size of the ISaGRAF strategy, clean flash, and download the smaller strategy. Refresh of standby fails due to CSC_TIMEOUT After power cycling the master, taking the standby from offline to online, or resetting the master via the xxx_axe_reset_coil (8449) the new standby may occasionally fail to refresh and report a Download Persistent Queue CSC_TIMEOUT event. The second refresh will be successful. After power cycle standby remains offline When retained variables are used a power cycle with a downtime close to the configured Retained Variables Delay may result in the standby remaining offline. The standby will report that it has newer retained variables than the master. If the problem occurs the IO Configurator should be used to do a clean flash of the standby with the master powered down. The standby should then be able to refresh successfully with the master. To avoid this configure the Retained Variables Delay to be a longer time than the Warm Start Time in the controller configuration. DDA CRC NVMQ Pool mismatches after reset Power cycling both controllers may cause a DDA CRC NvmQ pool different event upon completion of the refresh. When this occurs the standby will be unable to refresh with the master. If the problem occurs the IO Configurator should be used to do a clean flash of the DNP Data Logging on the master with the standby powered down. The standby should then be able to refresh successfully when powered on. Control relay output block pulse commands latch rather than pulse Commands to pulse a DNP point on or off cause the point to latch that value rather than pulse. If a pulse is needed, consecutive latch commands can be used to manually generate a pulse. Controller enters continuous reset On rare occasions in a duplex system after resetting the master via the xxx_axe_reset_coil (8449) the new standby may enter into a continuous reset state. When this occurs the standby will be unable to refresh with the master and will remain offline. If this problem occurs the controller should be powered on in a simplex configuration with the change state button held until power up completes. After the controller powers up the IO Configurator should be used to do a clean flash with all options selected. The standby should then be able to refresh successfully with the master.
5 PAC FT-MT Mass Termination Assembly 5 GFK-2569 Persistent queue is not recreated after strategy download On rare occasions the persistent queue is not recreated after a strategy download. This will result in Queue file does not exist events in the event log and failure to record DNP events. A subsequent strategy download or reset of the controller will cause the persistent queue to be created successfully. RTU does not honor the unsolicited parameters for event delay The RTU currently ignores the Class X Event Delay configuration settings on the DNP Attributes 1 tab. The RTU will generate an unsolicited response immediately for an event. RTU does not honor the unsolicited parameters for number of events The RTU currently ignores the Number Class X Events configuration settings on the DNP Attributes 1 tab. The RTU will generate an unsolicited response for every event. Occasional standby abort following power cycle. On rare occasions power cycling a duplex system may result in the standby coming up in the failed state with an Abort due to DmaFinish Copy. After this problem occurs resetting or power cycling the standby will allow it to successfully refresh with the master. Rendezvous timeouts cause additional refresh with high cycle times In systems running high execution cycle times (>200ms) an additional refresh may occur after a power cycle due to a rendezvous timeout on the initial refresh. In this case a Force standby, rendezvous timeout event will be logged. The second refresh may be successful or the standby may be unable to refresh with the master and remain offline. If the standby remains offline, it can be commanded to exit offline by pushing the button on the controller carrier or issuing a Simulate Button Press command via the Network Configurator utility. Scan Overload Shutdown Time should not be set above 2 seconds The Workbench programmer allows the Scan Overload Shutdown Time to be configured up to 10 seconds. The controller has a maximum execution cycle time of 2 seconds. Therefore, any values above 2 seconds have no effect. A single event may be reported twice when polling A single event may be reported twice when polling events during a persistent queue rollover (see operational note 5HPersistent queue Rollover Description on page 6H7) or a controller refresh. This data point is stale and may cause data to appear out of sequence if timestamps are ignored. Refresh fails after DNP channel is closed After closing the DNP channel, restarting the standby will result in the subsequent refresh failing with DDA CRC errors or rendezvous timeouts. The subsequent refresh will be successful and the system will continue in duplex operation.
6 6 PAC RT-DE RTU Controller GFK-2594 DDA CRC Timer Pool mismatches after master reset In a duplex system power cycling or resetting the master may cause a DDA CRC Timer pool different event upon completion of the refresh. When this occurs the subsequent refresh will be successful and the system will continue in duplex operation. Standby aborts after reset during retained variables save Resetting both controllers in a duplex pair while a retained variables save is in progress may result in the standby aborting on the subsequent power up. After this problem occurs resetting or power cycling the standby will allow it to successfully refresh with the master. Rendezvous timeout when opening DNP channel Occasionally a rendezvous timeout will occur when opening DNP channel. When this occurs the standby will remain offline. The standby can be commanded to exit offline by pushing the button on the controller carrier or issuing a Simulate Button Press command via the Network Configurator utility. RTU does not provide point data during refresh The RTU will respond to a DNP master poll while executing a refresh but will not provide data (it will appear as if there is no data). After completing the refresh, DNP master polls complete as expected. Freeze counter command may cause standby to refresh After issuing a freeze counter command, if standby has to refresh with Master, then first refresh may fail with DDA CRC Control Package A Vars different message in event log. The second refresh will be successful. Negative values clamped for 16 bit signed DNP variations The RTU treats 16 bit signed variations as unsigned and clamps negative values at DNP master timeouts when failover occurs on RTU. If a DNP read or write is in progress when a failover occurs, the DNP request may not be responded to. This will cause the DNP master to detect a timeout for that request. Further behavior is dependent on the actions of the DNP master. If this occurs, the RTU will respond to further DNP requests. ISaGRAF debugger allowed in protected mode The controller allows the ISaGRAF debugger to connect when the controller is in protected mode. This connection should be blocked in protected mode module operation If a channel configured for single pulse mode receives configuration for any other mode while energized, the output will remain energized until the pulse time completes. Single pulse mode on the 8142 module should not be used.
7 PAC FT-MT Mass Termination Assembly 7 GFK-2569 Large DNP polls may cause missed events With large cycle times (>150ms) polling large numbers of events (>100) may cause events to be missed. More frequent polling to prevent large numbers of events being returned will avoid this. Setting the Transmit Fragment Size on the controller DNP Attributes 1 tab in the IO Configurator to 1024 or 512 can also be used to avoid this. Controller aborts when power cycled with no strategy and configuration Powering up a controller with no strategy or configuration downloaded sometimes results in a controller abort. The event log will indicate Abort due to MmuDtmLISR Data Address invalid if this occurs. This issue has no impact on operation and can be ignored under these circumstances. Object group 0 not supported The RTU does not support DNP3 object group 0. Invalid data when using packed discrete points in Modbus master When the PAC8000 controller is used as a Modbus Master and an option other than No Packing is selected from the WorkBench, the controller could return erroneous ModBus values to the slave. The issue occurs only for discrete Modbus registers. Ensure that the No Packing option is selected if the PAC8000 controller is used as a Modbus Master. Operational Notes Subject Description Persistent queue Rollover Description The store-and-forward feature of the RTU uses 384K bytes of flash memory for nonvolatile storage. This storage is referred to as the persistent queue. As DNP events are recorded and polled the persistent queue eventually fills and requires that space be reclaimed. This processing occurs automatically and is referred to as a persistent queue rollover. During a rollover stored events may be discarded if the number of unpolled events exceeds 2/3 of the persistent queue size. In this case a Persistent Queue overflow - oldest entries overwritten event will be logged. Maximum Number of DNP Points A maximum of 4096 DNP points are supported. By default all HMI tags are DNP points in the Workbench software. If maximum number of DNP points is reached tags can be set to inactive in the Assign DNP Points to Classes window in Workbench. DNP Sample Rate DNP points are sampled for change every execution cycle. Events are recorded once per second, however. Point changes that occur more frequently than once per second will be detected but not reported. This may also result in consecutive events being reported with the same value when a point changes and then changes back to the original value. It should be noted that events are not recorded at intervals of exactly 1 second. They are recorded during the execution cycle and therefore the maximum time between recorded events is 1 second plus the execution cycle time.
8 8 PAC RT-DE RTU Controller GFK-2594 Subject Description Maximum DNP Event Rate through refresh The maximum number of DNP events that can be handled during a refresh of the standby varies based with the execution cycle time. For execution cycle times of approximately 60ms this is four events per second. For execution cycle times of 250ms a sustained rate of events will likely result in some DNP events being discarded. When this occurs Persistent Queue Add Failure - Transaction Buffer Full or Persistent Queue Del Failure - Transaction Buffer Full events are logged. Maximum DNP Event Rate through persistent queue rollover The maximum number of DNP events that can be handled during a persistent queue rollover (see operational note 7HPersistent queue Rollover Description on page 8H7) varies based with the execution cycle time. For execution cycle times of approximately 60ms, this is seven events per second. For execution cycle times of approximately 250ms this is four events per second. Higher rates of events may result in new DNP events being discarded. When this occurs Persistent Queue Add Failure - Transaction Buffer Full or Persistent Queue Del Failure - Transaction Buffer Full events are logged. Clean flash of persistent queue Doing a clean flash that includes cleaning DNP data logging will result in DNP events being discarded as well as new DNP events not being recorded for a short time (approximately 20 seconds). Analog deadband By default a fixed deadband of +/- 0.5 is applied to the scaled value for all analog object types. The deadband for each point can be set from a DNP master. Analog jitter To prevent excessive DNP events analog inputs should be filtered. This can be achieved by setting the analog deadband through a DNP master (see above). This can also be achieved by using the filtering capability of the analog modules. See PAC8000 Workbench help for information. Only use one method of time synchronization. Only one method of time synchronization should be enabled on the controller. If using DNP3 time synchronization SNTP and AXE to AXE time synchronization should be disabled. To disable SNTP, simply do not configure time servers on the controller Attributes tab in the IO Configurator. To disable AXE to AXE time synchronization uncheck the Act as Time Master option on the controller System tab for all controllers on the network. Note that some DNP masters automatically synchronize time and do not allow this functionality to be disabled. Self Addressing not supported The RTU does not support DNP self address functionality. DNP Events discarded during firmware download Performing a firmware download will cause the persistent queue to be deleted and recreated. This will result in a loss of any stored DNP data. DNP Events discarded during strategy download Performing a strategy download will cause the persistent queue to be deleted and recreated. This will result in a loss of any stored DNP data. Standby refresh with persistent queue In systems with large execution cycle times (>200ms) refreshing a standby controller can take approximately 90 seconds to complete.
9 PAC FT-MT Mass Termination Assembly 9 GFK-2569 Subject Description Flash wear for DNP event logging The persistent queue that stores DNP events uses flash memory for non-volatile storage. Write and erase cycles will cause wear to the flash storage eventually causing the component to fail. Changes in class1 or higher DNP points cause changes to the persistent queue. Therefore large numbers of these points or frequent changes to these points will accelerate wear of the flash storage. If the flash component fails, the event log will contain Flash sector xx write failed or Flash sector xx write timeout events. Maximum cycle times for RTU Sustained cycle times above 250ms are not supported for the RTU. DNP Qualifier 17 does not apply Because all AXE IO is at address 256 and above, qualifier 17 (8 bit addressing) does not apply and should not be used. DNP cold and warm start not supported The RTU does not support the cold and warm start DNP functions. A controller can be reset using the xxx_axe_reset coil (8449). This can be written via DNP if the point is mapped as a DNP point. This can also be done from application logic or written via Modbus. In duplex systems this will only reset the master controller. Cannot set Remote Supervisory Control The RTU does not support configuring Remote Supervisory Control. DNP3 dynamic class assignment not supported The RTU does not support dynamic DNP class assignment (DNP function code 22). DNP point classes must be statically assigned in the PAC8000 Workbench programming software. For more information see the Assign DNP Points to Classes topic in the PAC8000 Workbench help.
Release 2.11 Standard AXE Primary Firmware is not intended for use on any 8521 Controller not licensed as a RTU.
December 2010 PAC8000 8521-RT-DE RTU Controller This release consists of firmware release 2.12 for the 8521-RT-DE RTU Controller and DNP Control Package release 2.14. It provides a performance enhancement
More informationFix serial communications not functioning after reboot when the station number is set to iptables Fix iptables.
Sixnet IPm Firmware Revision History Note: IPm firmware versions are of the form major.minor.buildnumber. A letter X will be appended in the case of unreleased experimental versions. Other letters may
More informationCP30/G30/MC31 Firmware Version 3100 Known Issues
CP30/G30/MC31 Firmware Version 3100 Known Issues Introduction This document lists issues that have been identified with firmware version 3100 for the Kingfisher CP30/G30/MC31 modules. Where possible, workarounds
More informationDNP3 V3.00 DEVICE PROFILE DOCUMENT
DNP3 V3.00 DEVICE PROFILE DOCUMENT Vendor Name: DAQ Electronics. Device Name: DNP3 Master Station Server in the Callisto Computer. Date: June 8, 2000 Highest DNP Level Supported: For Requests: DNP-L3.
More informationDAQ Electronics, Inc 262B Old New Brunswick Road, Piscataway, NJ
DAQ Electronics, Inc 262B Old New Brunswick Road, Piscataway, NJ 08854-3756 DNP3 Server Configuration CallistoView version 5.0A This is a description of the unique DNP configuration dialogs and files in
More informationFisher ROC Plus Serial Driver Help Kepware Technologies
Fisher ROC Plus Serial Driver Help 2014 Kepware Technologies 2 Table of Contents Table of Contents 2 5 Overview 5 Channel Setup 6 Device Setup 7 Tag Import Settings 7 Address Specification 8 Operator Identification
More informationDNP Master Serial Driver Help 2010 Kepware Technologies
DNP Master Serial Driver Help 2010 Kepware Technologies 1 Table of Contents 1 Getting Started... 4 Help Contents... 4 Overview... 4 2 Channel Setup... 4 Channel Setup... 4 3 Device Setup... 5 Device Setup...
More informationDNP Master Ethernet Driver Help Kepware Technologies
DNP Master Ethernet Driver Help 2012 Kepware Technologies 2 Table of Contents Table of Contents 2 9 Overview 9 Channel Setup 10 Communications General 10 Timing 10 Device Setup 12 Communications 12 Polling
More informationSOFTWARE DOCUMENTATION. DNP3 Configuration / Interoperability Guide for the DATRAN XL4 DNP3 RTU
SOFTWARE DOCUMENTATION DNP3 Configuration / Interoperability Guide for the DATRAN XL4 DNP3 RTU Table of Contents 1 DNP V3.0 DEVICE PROFILE... 3 2 DNP V3.0 IMPLEMENTATION TABLE... 6 3 DNP V3.0 POINT LIST...
More informationFisher ROC Plus Ethernet Driver Help Kepware, Inc.
Fisher ROC Plus Ethernet Driver Help 2015 Kepware, Inc. 2 Table of Contents Table of Contents 2 5 Overview 5 Channel Setup 7 Device Setup 13 Scan Mode 15 Timings and Timeouts 16 Automatic Demotion 17 Automatic
More informationGE MDS, LLC. NETio Series. Protocol Communications Supplement. March 2013 Part No A01, Rev. C
GE MDS, LLC. NETio Series Protocol Communications Supplement March 2013 Part No. 05-4672A01, Rev. C Modbus Protocol NETio Architectural Implementation As described in detail below, the Modbus RTU protocol
More informationCP30/G30/MC31 Firmware Service Update Version 2993 (19 Aug 2013) Release Notes
CP30/G30/MC31 Firmware Service Update Version 2993 (19 Aug 2013) Release Notes Summary This package contains updated firmware for the Kingfisher CP30/G30/MC31 modules. Note: This firmware should be used
More informationLufkin Modbus Serial Driver Help Kepware Technologies
Lufkin Modbus Serial Driver Help 2012 Kepware Technologies 2 Table of Contents Table of Contents 2 3 Overview 3 Channel Setup 4 Device Setup 5 Cable Diagram 5 Modem Setup 6 Block Sizes 6 Framing 7 Error
More informationPAC BI-DP BIM and 8701-CA-BI Carrier
June 2013 PAC8000 8507-BI-DP BIM and 8701-CA-BI Carrier PROFIBUS DP Bus Interface Module and Carrier The 8507-BI-DP Bus Interface Module (BIM) provides the communications link between the PAC8000 series
More informationDNP Master Serial Driver Help Kepware Technologies
DNP Master Serial Driver Help 2013 Kepware Technologies 2 Table of Contents Table of Contents 2 8 Overview 8 Channel Setup 9 Timing 9 Device Setup 10 Communications 10 Polling 13 Unsolicited Messaging
More informationFisher ROC Plus Serial Driver Help Kepware, Inc.
Fisher ROC Plus Serial Driver Help 2015 Kepware, Inc. 2 Table of Contents Table of Contents 2 5 Overview 5 Channel Setup 7 Device Setup 13 Scan Mode 15 Timings and Timeouts 16 Automatic Demotion 17 Automatic
More informationSOFTWARE DOCUMENTATION. DNP3 Configuration / Interoperability Guide for the DATRAN II excel DNP3 RTU
SOFTWARE DOCUMENTATION DNP3 Configuration / Interoperability Guide for the DATRAN II excel DNP3 RTU QTech Data Systems Ltd Unit 6 Amuri Park 404 Barbadoes Street Christchurch New Zealand Phone: +64 3 3663713
More informationTOP Server V5 to MicroLogix Using DNP3 Ethernet Driver
TOP Server V5 to MicroLogix 1400 Using DNP3 Ethernet Driver Page 2 of 36 Table of Contents INTRODUCTION 3 CONFIGURING THE MICROLOGIX 1400 AS A DNP3 SLAVE 4 CONFIGURING TOP SERVER AS A DNP3 MASTER 9 TESTING
More informationTejas V Master Protocol
Connector Configuration Parameters Max ABE/COS Points This value sets the maximum count of RBX points that may be read in with an ABE/COS Dump poll. RTS ON DelayX10ms Enter a number from 0 to 255 (0 to
More informationKepware Technologies Differences Between 4x and 5x for DNP Drivers
Kepware Technologies Differences Between 4x and 5x for DNP Drivers June, 2010 V 1.000 Kepware Technologies Table of Contents 1. General... 1 2. Changes in Channel Properties... 1 2.1 DNP Master Ethernet...
More informationCutler-Hammer ELC Serial Driver Help Kepware Technologies
Cutler-Hammer ELC Serial Driver Help 2012 Kepware Technologies 2 Table of Contents Table of Contents 2 3 Overview 3 Device Setup 4 Modem Setup 5 Cable Diagram 5 Data Types Description 7 Address Descriptions
More informationDNP 3.0 device profile for AQ (5) DNP 3.0 device profile for AQ 200
DNP 3.0 device profile for AQ 200 1 (5) DNP 3.0 device profile for AQ 200 DNP 3.0 device profile for AQ 200 2 (5) Revision: 4.0 Date: October 2018 Changes: - Added Counter support Checked By: DNP 3.0 device
More informationREAD THIS INFORMATION FIRST. IC693CPU374 CPU Module with Ethernet Interface
IMPORTANT PRODUCT INFORMATION READ THIS INFORMATION FIRST May 29, 2003 Product: IC693CPU374 CPU Module with Ethernet Interface Introduction IC693CPU374-BE (and later) with CPU Firmware Release 11.03 This
More informationModbus ASCII Serial Device Driver Help 2009 Kepware Technologies
Modbus ASCII Serial Device Driver Help 2009 Kepware Technologies 1 Table of Contents 1 Getting Started... 3 Help Contents... 3 Overview... 3 2 Device Setup... 3 Device Setup... 3 Cable Diagram... 4 Modem
More informationMicroLogix 1400 Programmable Controllers FRN 13
Release Notes MicroLogix 1400 Programmable Controllers FRN 13 Catalog Numbers 1766-L32BWA, 1766-L32AWA, 1766-L32BXB, 1766-L32BWAA, 1766-L32AWAA, 1766-L32BXBA Contents Topic Page About This Publication
More informationIEC Master Driver Help Kepware Technologies
IEC 60870-5-101 Master Driver Help 2014 Kepware Technologies IEC 60870-5-101 Master Driver 2 Table of Contents Table of Contents 2 IEC 60870-5-101 Master Driver Help 3 Overview 3 Channel Setup 4 Device
More informationDNP Points List and Implementation
S&C IntelliCap Plus Automatic Capacitor Control DNP Points List and Implementation Table of Contents Section Page Section Page DNP Points List for IntelliCap Plus Controls...1 Status Points....2 Analog
More informationFisher ROC Serial Driver Help Kepware Technologies
Fisher ROC Serial Driver Help 2012 Kepware Technologies 2 Table of Contents Table of Contents 2 4 Overview 4 Channel Setup 5 Device Setup 6 Tag Import Settings 6 Address Specification 7 Operator Identification
More informationDNP3 Router. User Manual A-DNP3R. Document No. D /2018 Revision 1.24
DNP3 Router User Manual A-DNP3R Document No. D109-010 12/2018 Preface CONTENTS 1. Preface... 6 1.1. Introduction to the DNP3 Router... 6 1.2. Features... 6 1.3. Architecture... 8 1.4. Additional Information...
More informationMODBUS Protocol for MiCOM P30 Series
MODBUS Protocol for MiCOM P30 Series Substation Protocols Technical Documentation This document does not replace the Technical Manual Version: MiCOM P30, MODBUS Index: B Release: 08 / 2011 MODBUS Protocol
More informationDevice Profile Document
Voltage Regulators CL-6A Regulator Control DNP3 Device Profile Document Reference Information R225-90-11 Device Profile Document For Communications Protocol DNP3 For Use With Cooper Power Systems CL-6A
More informationCampbell Scientific Australia DNP3 DEVICE PROFILE
S.UTLEY 1 1 Campbell Scientific Australia DNP3 DEVICE PROFILE Real-time monitoring and Control Systems S.UTLEY 1 2 DNP3 v.28 Device Profile Document Vendor name: Campbell Scientific, Inc. Device Name:
More informationDNP3 Field Device Profile. for
DNP3 Field Device Profile for Document Name: Eaton DNP3 XML File Revision History Date Time ion Reason for change Edited by 2012-01-11 2015-04-16 1 Initial ion Joerg Katzer 15:00:00 2 First updates Joerg
More informationDNP3 Master Serial Driver PTC Inc. All Rights Reserved.
2018 PTC Inc. All Rights Reserved. 2 Table of Contents 1 Table of Contents 2 9 Overview 9 Setup 9 Channel Properties General 10 Channel Properties Serial Communications 11 Channel Properties Write Optimizations
More informationSIXNET EtherTRAK Driver PTC Inc. All Rights Reserved.
2018 PTC Inc. All Rights Reserved. 2 Table of Contents 1 Table of Contents 2 3 Overview 3 Setup 4 Channel Properties General 4 Channel Properties Ethernet Communications 5 Channel Properties Write Optimizations
More informationDNP3 Master Ethernet Driver PTC Inc. All Rights Reserved.
2018 PTC Inc. All Rights Reserved. 2 Table of Contents 1 Table of Contents 2 10 Overview 10 Setup 11 Channel Properties General 11 Channel Properties Ethernet Communications 12 Channel Properties Write
More informationIEC Master Driver PTC Inc. All Rights Reserved.
2017 PTC Inc. All Rights Reserved. 2 Table of Contents 1 Table of Contents 2 4 Overview 4 Setup 5 Channel Properties General 5 Channel Properties Ethernet Communications 6 Channel Properties Write Optimizations
More informationImportant Product Information
Important Product Information April 15, 2009 READ THIS INFORMATION FIRST Product: IC693CPU366 CPU Module with PROFIBUS Master Upgrades IC693CPU366-CD with CPU Firmware Version 10.74 PROFIBUS Firmware Version
More informationOpto 22 Ethernet Driver Help Kepware Technologies
Opto 22 Ethernet Driver Help 2011 Kepware Technologies 2 Table of Contents Table of Contents 2 4 Overview 4 Device Setup 5 Communications Parameters 5 Import 6 Cable Connections and Diagrams 7 Data Types
More informationMVI46-MCM SLC Platform Modbus Interface Module USER MANUAL. February 5, 2004
MVI46-MCM SLC Platform Modbus Interface Module USER MANUAL ProSoft Technology, Inc. 1675 Chester Avenue Fourth Floor Bakersfield, CA 93301 (661) 716-5100 (661) 716-5101 Fax prosoft@prosoft-technology.com
More informationSCADA. SurvalentONE. STC Explorer
SurvalentONE SCADA SurvalentONE SCADA Survalent SCADA is a software automation solution to provide real-time control and data acquisition for utility operations. Survalent SCADA software includes STC Explorer
More informationInstrumentationTools.com
Author: Instrumentation Tools Categories: Communication Difference between Modbus and DNP3 Communication Protocols Overview Modbus and DNP are both byte-oriented protocols. Modbus is an application layer
More informationGeneral Specifications
General Specifications GS 34P02P22-02E DNP3 Communication Portfolio (FCN-500/FCN-RTU) GENERAL This General Specifications document describes the Distributed Network Protocol (DNP3) Communication Portfolio
More informationVoltage regulator TAPCON 240
Voltage regulator TAPCON 240 Supplement 2398461/01 Protocol description DNP3 All rights reserved by Maschinenfabrik Reinhausen Copying and distribution of this document and utilization and communication
More informationAlstom Redundant Ethernet Driver Help Kepware Technologies
Alstom Redundant Ethernet Driver Help 2012 Kepware Technologies 2 Table of Contents Table of Contents 2 3 Overview 3 Channel Setup 4 Device Setup 5 Device ID 5 Block Sizes 6 Redundancy Settings 6 Data
More informationIEC Master Driver Help Kepware Technologies
IEC 60870-5-104 Master Driver Help 2014 Kepware Technologies IEC 60870-5-104 Master Help 2 Table of Contents Table of Contents 2 IEC 60870-5-104 Master Driver Help 3 Overview 3 Channel Setup 4 60870 Settings
More informationDNP3 Device Profile. Device Profile Template. Data Dictionary. Release 2.0. January 30, 2001
Reclosers Kyle Form 4C Recloser Control Serial Communications Reference Information R280-90-1 DNP3 Device Profile Device Profile Template Data Dictionary Release 2.0 January 30, 2001 For Use With Cooper
More informationFor CP-30 and G30 RTUs Version Toolbox Plus+ for CP-30 and G30 RTUs
For CP-30 and G30 RTUs Version 3.11.0 Toolbox Plus+ for CP-30 and G30 RTUs Document Information Copyright 2007-2013 CSE Semaphore (Australia) Pty Ltd. ABN 35 006 805 910 Web: http://www.cse-semaphore.com
More informationVERIS H8035 and H8036
VERIS H8035 and H8036 MODBUS IMPLEMENTATION SPECIFICATION OVERVIEW This document describes the implementation of Modbus protocol used in the Veris H8035 and H8036 power meters. It is intended to assist
More informationIntelliCAP PLUS Supplement for Landis & Gyr Telegyr 8979 Protocol
IntelliCAP PLUS Supplement for Landis & Gyr Telegyr 8979 Protocol March 31, 2003 1135 Atlantic Avenue Alameda, California USA 1023-563 / 3-31-03 IntelliCAP PLUS Capacitor Control Proprietary Notice This
More informationSCADAPack DNP Driver. User and Reference Manual
SCADAPack DNP Driver User and Reference Manual CONTROL MICROSYSTEMS SCADA products... for the distance 48 Steacie Drive Telephone: 613-591-1943 Kanata, Ontario Facsimile: 613-591-1022 K2K 2A9 Technical
More informationA36D/TPSD DNP 3.0 & Modbus SCADA INTERFACE
SCADA INTERFACE INSTRUCTIONS - OPTION 21P / 21Q - FOR A36D/TPSD SYSTEMS A36D/TPSD DNP 3.0 & Modbus SCADA INTERFACE OPTION 21P / 21Q INSTRUCTIONS This manual is only valid for A36D/TPSD Chargers equipped
More informationCutler-Hammer ELC Serial Driver PTC Inc. All Rights Reserved.
2018 PTC Inc. All Rights Reserved. 2 Table of Contents 1 Table of Contents 2 4 Overview 4 Setup 5 Channel Properties General 6 Channel Properties Serial Communications 7 Channel Properties Write Optimizations
More informationDNP3 Device Profile Based on DNP XML Schema version
Seite 1 von 52 DNP3 Device Profile Based on DNP XML Schema version 2.08.00 Document Name: DNP3 XML File Document Description: TIM 4R-IE DNP3 Complete Device Profile Revision History Date Time Version Reason
More informationPACSystems* RX3i IC695CMM002 and IC695CMM004
May 2010 PACSystems* RX3i IC695CMM002 and IC695CMM004 Serial Communications Modules PACSystems* RX3i Serial Communications modules expand the serial communications capabilities of the RX3i system. Serial
More informationModel 5100/5200 Quick Reference Register Guide
Model 5100/5200 The information in this document is current as of the following Hardware and Firmware revision levels. Some features may not be supported in earlier revisions. See for the availability
More informationControlLogix Redundancy System Revision 8
Release Notes ControlLogix Redundancy System Revision 8 Cat. No. 1756-CNB/D, -CNBR/D, -L55, -L55M13, -L55M14, -L55M16, -L55M23, -L55M24, 1757-SRM/A, -SRM/B IMPORTANT If you have a 1756-L55 controller,
More informationFor Kingfisher CP-30 RTUs Version 4.2.0
For Kingfisher CP-30 RTUs Version 4.2.0 Document Information Copyright 2007-2017 Servelec Technologies Pty Ltd. ABN 35 006 805 910 Web: http:/www.servelec-technologies.com/ Email: info.kingfisher@servelec-technologies.com
More informationNOTE The documentation and/or manuals provided by the IEDs vendors must be read and understood thoroughly prior to configuration.
ConfigWiz Addendum This is the DNP3.0 client addendum. This addendum describes the pop-up window tabs, fields, and ranges of valid parameters for entry in those fields. NOTE The documentation and/or manuals
More information345 Transformer Protection System
GE Digital Energy 345 Transformer Protection System Transformer protection and control GE Digital Energy 650 Markland Street Markham, Ontario Canada L6C 0M1 TELEPHONE: Worldwide +1 905 927 7070 Europe/Middle
More informationPLX51-HART-4I. 4-Channel HART Input Multidrop Field Device USER MANUAL
PLX51-HART-4I 4-Channel HART Input Multidrop Field Device USER MANUAL November 27, 2018 Page 2 of 88 CONTENTS 1. Preface... 5 1.1. Features... 5 1.2. Additional Information... 5 1.3. References... 6 1.4.
More informationDNP3 Device Profile Based on DNP XML Schema version Showing both the Device's Capabilities and its Current Configuration
Page 1 of 17 DNP3 Device Profile Based on DNP XML Schema version 2.11.00 Document Name: MHT410 XML File Document Description: Device Profile for the MHT410 Showing both the Device's and its Current Configuration
More informationGeneral Specifications
General Specifications DNP3 Communication Portfolio GS 34P02P22-01E GENERAL This General Specifications document describes the Distributed Network Protocol (DNP3) Communication Portfolio for STARDOM. The
More informationAPPLICATION NOTES - PIGNONE P6008 RTU CUSTOM PROTOCOL
APPLICATION NOTES - PIGNONE P6008 RTU CUSTOM PROTOCOL &VMWXSP&EFGSGO Revision: January, 1999 TABLE OF CONTENTS 1. INTRODUCTION... 3 2. REFERENCES... 3 3. DEFINITIONS... 3 4. FUNCTIONAL REQUIREMENTS...
More informationMitsubishi FX Net Driver PTC Inc. All Rights Reserved.
2017 PTC Inc. All Rights Reserved. 2 Table of Contents 1 Table of Contents 2 3 Overview 3 Device Setup 4 Channel Properties 5 Channel Properties - General 5 Channel Properties - Serial Communications 6
More informationDNP3 Communications Protocol
Powermeter and Power Quality Analyzer PM174 DNP3 Communications Protocol Reference Guide BG0413 Rev. A3 Every effort has been made to ensure that the material herein is complete and accurate. However,
More informationDNP3 Device Profile Document For ARE-M Series Float Chargers Single-Phase Input
DNP3 Device Profile Document For ARE-M Series Float Chargers Single-Phase Input PM990.1072.00, Issue 6 UNIPOWER, LLC 3900 Coral Ridge Drive Coral Springs, FL 33065 Phone: +1-954-346-2442 Toll Free: 1-800-440-3504
More informationModicon Modbus Driver
Modicon Modbus Driver Filename Modbus.dll Manufacturer Modicon Devices Protocol Version 3.1.36 Any device compatible with Modbus protocol v1.1b Modbus v1.1b Last Update 03/17/2017 Platform Win32 and Windows
More informationProSoft Technology, Inc. RTU-5/03 Processor for Allen-Bradley SLC Modular Racks Inside this Manual
Revision : 1.2 Updated : 6/30/04 ProSoft Technology, Inc. RTU-5/03 Processor for Allen-Bradley SLC Modular Racks Catalog Numbers : 3250-L532M RTU-5/03 Processor with 16 K RAM This manual is provided in
More informationHow to Configure MODBUS TCP/IP in Proficy HMI/SCADA CIMPLICITY V1.1
How to Configure MODBUS TCP/IP in Proficy HMI/SCADA CIMPLICITY V1.1 1 Outline The Proficy HMI/SCADA CIMPLICITY product has the ability to communicate to any MODBUS TCP/IP device that meets the Modicon
More informationUnderstanding printer messages
The operator panel displays messages describing the current state of the printer and indicates possible printer problems you must resolve. This topic provides a list of all printer messages, explains what
More informationFANUC CNC Parts IMPORTANT PRODUCT INFORMATION. Hardware Identification. Firmware Identification. PACSystems RX7I Ethernet Module
June 3, 2003 IMPORTANT PRODUCT INFORMATION READ THIS INFORMATION FIRST Product: PACSystems RX7I Ethernet Module IC698ETM001-AA This document contains information that is not available in any other publication;
More informationGE Intelligent Platforms PAC8000 RTU
GE Intelligent Platforms PAC8000 RTU A ruggedized, reliable RTU PAC8000 Remote Terminal Unit (RTU) thrives in the desert heat of the Arabian Peninsula and the arctic cold of Siberian oil fields delivering
More informationETC II Modbus Communications Protocol Reference Guide
ETC II Modbus Communications Protocol Reference Guide SATEC Ltd. BG0595 Rev. A1 Every effort has been made to ensure that the material herein is complete and accurate. However, the manufacturer is not
More informationEGW1-IA3-MB User s Manual
www.exemys.com Rev. 0 1 Products are in constant evolution to satisfy our customer needs. For that reason, the specifications and capabilities are subject to change without prior notice. Updated information
More informationIMPORTANT PRODUCT INFORMATION
April 27, 2004 IMPORTANT PRODUCT INFORMATION READ THIS INFORMATION FIRST Product: IC697 Factory LAN Ethernet Interface (Type 2) IC697CMM742-KL or later with Firmware Version 2.84 Hardware Identification
More informationREL 512 Connectivity With A Harris Westronics RTU Using DNP 3.0
ABB Application Note Substation Automation and Protection Division REL 512 AN-45A-99 REL 512 Connectivity With A Harris Westronics RTU Using DNP 3.0 ABSTRACT: DNP 3.0 is a popular communication protocol
More informationOn Control SUSA v1.1 MODBUS Functions
Summary of functions: Function code 0x03 Read holding registers and Function code 0x04 Read input registers (both functon codes are equivalent): Register address: 0x0000..0x0102 (0..258) 0x0200..0x0281
More informationDNP3 SPECIFICATION DEVICE PROFILE
DNP3 SPECIFICATION DEVICE PROFILE Version 2016 DISCLAIMER STATEMENT DNP Users Group documents and publications are not consensus documents. Information contained in this and other works has been obtained
More informationIMPORTANT PRODUCT INFORMATION
IMPORTANT PRODUCT INFORMATION February 2011 GFK-1490TU READ THIS INFORMATION FIRST Product: IC693CPU364 CPU Module with Ethernet Interface IC693CPU364-FM with CPU Firmware Version 10.75 Firmware version
More informationModbus Unsolicited Serial Driver PTC Inc. All Rights Reserved.
2018 PTC Inc. All Rights Reserved. 2 Table of Contents 1 Table of Contents 2 3 Overview 4 Setup 5 Channel Setup 5 Channel Properties 6 Channel Properties General 6 Channel Properties Serial Communications
More informationSCADA Controlled LOR/ER - DNP3.0 Communications Protocol - TECHNICAL MANUAL ES-SLOR-1
SCADA Controlled LOR/ER - DNP3.0 Communications Protocol - TECHNICAL MANUAL ES-SLOR-1 Telephone: 781-335-5200 fax: 781-335-4253 180 King Avenue Weymouth, MA 02188 www.electroswitch.com 1 Introduction...
More informationFirmware Release Notes PREMIUM ETYPORT EXEC V5.4 TSX P M TSX P M TSX P M
Status: Official Doc. No.: S1A5907607 Revision: 04 Firmware Release Notes PREMIUM ETYPORT EXEC V5.4 TSX P57 1634M TSX P57 2634M TSX P57 3634M Affected Product (s) Prior Version (s) New Version (s) Date
More informationCAN-Transceiver Data Register Map MODBUS Slave RTU
MODBUS Slave RTU V1.40 Table of Contents INTRODUCTION... 3 CAN TRANSCEIVER GLOBAL DATA... 3 OPTIONAL DIGITAL INPUTS... 3 AVC (TR CONTROL) REGISTER BASE ADDRESSES... 3 AVC MODBUS REGISTER DEFINITION...
More information350 Feeder Management System
Title page GE Digital Energy Multilin 350 Feeder Management System Feeder Protection and Control Communications Guide SR350 revision: 1.20 Manual P/N: 1601-9087-A2 GE publication code: GEK-113511B Copyright
More informationMPU-32 AND FPU-32 TIA-485 NETWORK
3714 Kinnear Place Saskatoon, SK Canada S7P 0A6 Ph: (306) 373-5505 Fx: (306) 374-2245 www.littelfuse.com/protectionrelays MPU-32 AND FPU-32 TIA-485 NETWORK SEPTEMBER 5, 2006 PRELIMINARY Publication: MPU-32/FPU-32
More informationMaxiflex Single Harwell NIM M1588 User Manual
Maxiflex Single Harwell NIM M1588 User Manual SCOPE This document describes the installation, configuration and use of the Maxiflex M1588 Single Harwell NIM. This version of the manual refers to the NIM
More informationVPGate Manual PROFIBUS to serial
VPGate Manual PROFIBUS to serial Important information Purpose of the Manual This user manual provides information how to work with the VPGate PROFIBUS to serial. Document Updates You can obtain constantly
More informationIMPORTANT PRODUCT INFORMATION
IMPORTANT PRODUCT INFORMATION READ THIS INFORMATION FIRST January 2010 Product: IC693CPU364 CPU Module with Ethernet Interface IC693CPU364-FL with CPU Firmware Version 10.73 Firmware version 10.73 is a
More informationWebAccess Driver Configuration Manual
Date Version Author Reviewer Description WebAccess ModSim MOD_DEV.DLL Driver date: 2017/7/18 English Version 1.0 2018-10-02 1.0 Eden.Sun Joseph.Chiu Initial Release Revision History Table of Contents Modsim
More informationP2 Configuration Guide
P2 Configuration Guide March 2018 Rev. 4.00 #220, 550 71 st Avenue SE Calgary, Alberta, Canada T2H 0S6 Phone: (403) 255-9544 Fax: (403) 259-2343 www.barnettprotalk.com E-mail: sales@barnettprotalk.com
More informationPACSystems* RX3i IC695CMM002 and IC695CMM004
April 2010 PACSystems* RX3i IC695CMM002 and IC695CMM004 Serial Communications Modules PACSystems * RX3i Serial Communications modules expand the serial communications capabilities of the RX3i system. Serial
More informationFNL Modbus TCP Interface
FNL Modbus TCP Interface Users Manual V0.1 17.06.2009 Project No.: 5304 Doc-ID.: FNL Modbus TCP Interface-UM-V0.1 Status: Released COMSOFT d:\windoc\icp\doku\hw\fnl\modbus tcp\version_0.1\fnl_modbus_tcp_e.doc
More informationWebAccess DNP3 Master Ethernet Driver Guide. Advantech WebAccess. - DNP3 Master Ethernet Driver Guide Version: 1.01
Advantech WebAccess - DNP3 Master Ethernet Driver Guide Version: 1.01 1 1. Introduction... 3 1.1 Introduction for DNP3 Master Ethernet Driver... 3 1.2 Features of DNP3 Master Driver... 3 1.2.1 Functionalities...
More informationPing Driver PTC Inc. All Rights Reserved.
2017 PTC Inc. All Rights Reserved. 2 Table of Contents 1 Table of Contents 2 3 Overview 4 Channel Properties General 4 Channel Properties Ethernet Communications 5 Channel Properties Write Optimizations
More informationmbc082 Bus Converter
BUS CONVERTER RS485 TO 1-WIRE BUS mbc082 mbc082 Bus Converter Document. 10910, Revision - February 2007 2007 CMC Industrial Electronics Ltd. This page intentionally left blank. mbc082 Bus Converter Technical
More informationProtection Terminal REF 54_ Protection Relay REX 521
Protection Terminal Protection Relay 1MRS755260 Issued: 02.04.2004 Version: C/22.06.2004 Protection Terminal Protection Relay Contents 1. About this manual...4 1.1. Copyrights...4 1.2. Trademarks...4
More informationDNP 3.0 & Modbus SCADA INTERFACE INSTRUCTIONS FOR 205T BASED SYSTEMS
DNP 3.0 & Modbus SCADA INTERFACE INSTRUCTIONS - OPTION 21PQ - FOR 205T BASED SYSTEMS DNP 3.0 & Modbus SCADA INTERFACE OPTION 21PQ INSTRUCTIONS FOR 205T BASED SYSTEMS CPN114830 ECN/DATE ISSUE DATE: ECN
More informationInstructions. Modbus RTU Card (WSIQ-COM-MB)
Instructions (WSIQ-COM-MB) Contents 1 Warnings... 2 2 Important User Information... 2 3 Installation... 2 4 Operation... 3 5... 4 6 Specifications... 15 Product Compatibility The is suitable for use with
More informationPACSystems* RX3i IC695CMM002-EG and IC695CMM002CA-EG IC695CMM004-EG, IC695CMM004CA-EG, and IC695CMM004LT-EG
September 2017 PACSystems* RX3i IC695CMM002-EG and IC695CMM002CA-EG IC695CMM004-EG, IC695CMM004CA-EG, and IC695CMM004LT-EG Serial Communications Modules PACSystems* RX3i Serial Communications modules expand
More information