INGEARDRIVERS

INGEAR.NET.LOGIX v3.0 scheduled for release  in 2Q 2010.

Some of the new features packed into NET.LOGIX v3.0 include:

NEW – Logix.PeerMessage class for Unsolicited Messages

The Logix.PeerMessage class handles communications in the background and fires a MsgReceived event notification when the PLC sends data via a MSG instructions.  NET.LOGIX v3.0 supports 3 types of messages.

• CIP Data Table Write
  • Uses native tag addressing
  • Supports BOOL, SINT, INT, DINT, REAL, STRING, UDT, PDT and MDT data types

• SLC Typed Write
  • Supports MicroLogix and SLC (Ethernet IP) controllers
  • Supports I, O, B, N, S, F, A, L and ST data table files

• PLC-Type Write
  • Supports PLC-5 (Ethernet IP) controllers.
  • Supports I, O, B, N, S, F, A and ST data table files

The PeerMessage class automatically distinguishes between the 3 MSG types so there’s no special programming required on your end.   When the PLC sends you a message you’ll received a notification event, then just access message information through PeerMessage class members.

PeerMessage Class Members

NEW – Logix.DTEncoding Class for Defined Data Type Support

NET.LOGIX v3.0 also adds support for User-Defined Types (UDT’s), Pre-Defined Types (PDT’s) and Module Define Types (MDT’s).

The Logix.DTEncoding class facilitates reading and writing structured data types as blocks without having to read/write each ATOMIC member individually.

Defined Data Types is supported by the PeerMessage class as well.

For more information when on NET.LOGIX 3.0 please contact us at 610.935.8282 or email sales@ingeardrivers.com

> Download NET.LOGIX 2.0

INGEAR.NET.LOGIX v.2.0.2010.324 maintenance release available for download.  This version corrects the following problems:

• Fixed “Invalid Tag.Name” exception from being thrown when a name contains a colon “:” character.  (e.g. Tag.Name = “Program:MyProgram.MyTag”)
• Fixed “Invalid Tag.Name” exception from being thrown if a numeric character followed the colon “:” character in the Tag.Name ( e.g. Tag.Name = “Local:2:I.Data.0″)
• Fixed problem with “Invalid Tag Name” exception not being thrown if there were mismatch in ‘[' and ']‘ characters in Tag.Name (e.g Tag.Name = “MyArray[0", or Tag.Name =" MyArray[0]]”)
• Fixed problem with IEC 1131 2.12 naming standard enforcement
• Fixed problem with cached tag write operation thrown “Tag.Value is null” exception”
• Fixed problem with Tag constructor Tag(Controller, Name, Data Type) throwing an exception when reading an element of a boolean array ( e.g new Tag(MyPLC, “MyBoolArray[0]“, Logix.Tag.Atomic.BOOL”)

How to upgrade to NET.LOGIX v2.0.2010.324

• NET.LOGIX users that have a current NET.LOGIX Maintenance Subscription Plan are eligible for a free software update.

• NET.LOGIX users that have let their support expire should contact (sales@ingeardrivers.com) or call 1.866.935.797 (Toll Free US / Canada) Tel 1.610.935.8282 for pricing.

> Download NET.LOGIX v2.0.2010.324

INGEAR.NET.LOGIX Visual Studio .NET class library for Allen-Bradley ControlLogix and CompactLogix programmable automation controllers has be updated to version 2.0.2010.311 to incorporate the following new features and improvements

• Improved CIP inactivity timeout behavior
• Added support for reading ControlLogix/CompactLogix CPU state
• Controller.GroupRead/GroupWrite reports partial failures
• TagGroup.ErrorString returns malformed/nonexistent tag names for GroupRead/Write operations
• Tag.Name property has stricter enforcement of IEC 1131 2.1.2 naming standard
• Improved STRING data type read/write operation

How to upgrade to NET.LOGIX v2.0.2010.311

• NET.LOGIX users that have a current NET.LOGIX Maintenance Subscription Plan are eligible for a free software update.

• NET.LOGIX users that have let their support expire should contact (sales@ingeardrivers.com) or call 1.866.935.797 (Toll Free US / Canada) Tel 1.610.935.8282 for pricing.

> Download NET.LOGIX v2.0.2010.311