EthernetIPforCLXCom

EthernetIPforCLXCom

This driver specifically targets the Allen Bradley line of ControlLogix and CompactLogix PLCs. It uses tag names directly to access data values in the PLC.

Properties|-		IPAddress|Pie	Buns	Danish	Croissant
Cheese	Ice cream		Butter	Yogurt

Properties

IPAddress - The TCP/IP address of the PLC to communicate with

CIPConnectionSize - The maximum number of bytes in a single packet. The larger the number, the more efficient the communications. A value of 508 works with all Allen Bradley PLCs tested. Some of the newer models will allow a higher value.

DisableMultiServiceRequest - A multi-service request allows more than one request per packet. This can dramatically increase the speed of retrirving values. Not all PLCs support this, such as the Micro800 series.

DisableSubscriptions - Paused updating of subscriptions. This is useful in cases such as when hiding a form and there is no longer a need to refresh the values. Or when used with a Trend Chart, it can pause the charting.

PollRateOverride - This set the target rate for refreshing all of the subscriptions. When there are a large number of subscriptions that have to be split amongst sever requests, this value is divided by the number of requests required to determine the delay between each packet. A value of 0 will make the driver update as fast as the PLC will respond, but be cautious because it can reach rates less than 5ms and start to use a lot of resources.

Port - The TCP/IP port. In nearly all cases this will be 44818

INIFileName - An INI file can be created to store the properties for being set during application startup. See INI File Usage for more details

INIFileSection - Specifies the section within the INI file

Methods

For the methods common to all drivers see the section on the IComComponent

GetTagList() - Returns the list of controller scope and program scope tags. This is a synschronous method and can delay for a long time when reading a program with a very large tag list.

Addressing

Controller scope tags are addressed by directly using the tag name. For example:

MyTag

Program scope tags require a prefix to indicate which program. For example:

PROGRAM:MainRoutine.MyTag

UDT elements are read by specifying the UDT variable. For example:

MyUDTTag.Element