Digital Device Access Software for Allen-Bradley on_Digital_UNIX[TM]_________________________________ Release Notes Operating System and Version: Digital UNIX Version 3.2 Software Version: Device Access Software for Allen-Bradley, Version 3.0 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ April 1996 Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. The following are trademarks of Digital Equipment Corporation: Alpha, BASEstar, DEComni, Digital, OpenVMS, TK, VAX, VMS, and the Digital logo. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. PLC, PLC-2, and PLC-3 are registered trademarks of Allen- Bradley Company Inc. PLC-5, Data Highway and Data Highway Plus are trademarks of Allen-Bradley Company, Inc. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using DEC DOCUMENT Version 2.3. _________________________________________________________________ Contents 1 New and Changed Features for V3.0............. 1 1.1 Support for DEComni V3.0.................. 1 1.2 Support for BASEstar Open V3.0............ 1 1.3 Support for Additional PLC Models......... 1 1.4 DEComni status returned in omni_l_iosb_general field................. 1 2 Problems Fixed in This Release................ 1 2.1 Total Byte Count Calculation.............. 1 2.2 Documentation Corrections................. 2 2.2.1 BASEstar Open Examples Corrected........ 2 2.3 Template File Correction.................. 2 3 Known Restrictions............................ 2 3.1 Restriction on Devices on a Line.......... 2 4 Known Problems................................ 2 5 Documentation Errata.......................... 2 iii 1 New and Changed Features for V3.0 The following changes are included in this release: 1.1 Support for DEComni V3.0 Support was added for DEComni V3.0. DEComni V3.0 changed the way that a DAS is installed as well as added the capability to delete objects. The setld script procedure was changed to support the new version of DEComni and support for deleting VMDs, variables, data types, etc. was added to the DAS. 1.2 Support for BASEstar Open V3.0 The BASEstar Open configuration template file was updated to use the new data/device server provided with BASEstar Open V3.0. Using the combined data/device server is more efficient than using seperate device and data servers. 1.3 Support for Additional PLC Models Support for the Allen-Bradley PLC-5/80 PLC was added. 1.4 DEComni status returned in omni_l_iosb_general field The DAS now returns a DEComni status code in the omni_l_ iosb_general field of the IOSB for DEComni API calls. The DAS still returns a device specific error in the omni_l_ iosb_provider or omni_l_iosb_network fields of the IOSB. 2 Problems Fixed in This Release The following problems from the previous release were fixed in this release: 2.1 Total Byte Count Calculation Previously, the total byte count calculated for data in a packet was incorrect if DLE (hex 10) bytes were received in a data packet from a device. The effect of the miscalculation caused data to be corrupted in the first data packet received from the device in a multi-packet data transfer. 1 2.2 Documentation Corrections The following documentation errors were fixed in this release: 2.2.1 BASEstar Open Examples Corrected BASEstar Open examples for creating variable definitions were corrected to use ADDRTYPE rather than ADDRESS_TYPE. 2.3 Template File Correction The BASEstar Open configuration template file was corrected to create one VMD per activity rather than an activity with multiple VMDs. Only one VMD is allowed per activity. 3 Known Restrictions The following restrictions exist in this release: 3.1 Restriction on Devices on a Line All devices configured on a particular line must be accessed using a single process. This restriction exists because all devices on a line must share the same physical port. 4 Known Problems There are no known problems as of this release. 5 Documentation Errata There are no documentation corrections at this time. 2