17 November 2008

LogixView Utility Version 4 Release Notes

LogixView Utility is a tool for reducing configuration time of Logix controllers and Factory al! View "#$ a%%lications& 'evelo%ment time is reduced t(roug( t(e a%%lication of user)configurable Logix code libraries and "#$ com%onents libraries& LogixView is an engineering wor!station software t(at is intended to com%lement* not re%lace* t(e use of +,Logix -000 and Factory al! View ,tudio& LogixView consists of four sets of tools. /10 Logix library builder tool* /20 "#$ library builder tools* /10 Logix controller configuration tools* and /20 Factory al! View "#$ configuration tools& "#$ develo%ment time is reduced by integrating information from t(e Logix controller configuration wit( "#$ %ro3ect com%onents& (ese configuration tools are described below& Note t(at most of t(e tools function inde%endently of eac( ot(er& $t is not necessary to create com%lete Logix libraries or com%lete "#$ libraries to use LogixView& 4ou can %ic! t(e tool to use t(at will (el% reduce your develo%ment time&

(e software can be used by two ty%es of users. library builders and %rocess control engineers or configuration tec(nicians& 5n exam%le of library builders is 6or%orate 7ngineering res%onsible for maintaining consistency and standards across all t(e %lants in t(e com%any& 6or%orate 7ngineering is res%onsible for develo%ing t(oroug(ly tested libraries for reuse in t(e %lants& 5not(er exam%le of library builders is ,ystem $ntegrators /,$0& ,$ wants to increase %rofitability by reducing engineering cost t(roug( t(e reuse of configuration tem%lates& 8rocess control engineers or configuration tec(nicians are res%onsible for building t(e Logix controller configuration and "#$ a%%lication by de%loying t(e library tem%lates& 9(ile t(e number of LogixView tools and t(e si:e of t(e user manual may seem overw(elming* t(e user can c(oose t(e tool to use and t(e section to read& wo tutorials %rovide ste%)by)ste% instructions in creating a sam%le Logix and ,7 a%%lication using t(e LogixView tools&

1.1

Logix and HMI Library Builder Tools

(e following library builder tools are %rovided for building Logix tem%lates and "#$ library com%onents. 1& Logix Library Builder Tool& Logix control strategy tem%lates are created by t(e user using +,Logix -000& LogixView can add code to a target controller by creating an instance of t(e control tem%late and re%lacing t(e tag names and tag data in t(e tem%late wit( user)s%ecified values& (e tem%lates can be created using any of t(e standard %rogramming languages /, * +LL* ,F6* and F;'0& 7<ui%ment %(ase %rograms can also be used as tem%lates& (e tem%lates can contain U' s* 5=$s* and any %redefined data ty%e& 7ac( controller 56' file containing t(ese tem%lates can be considered a source library file& #ulti%le libraries can be created for different a%%lications or different customers by using different source 56' files& (e Logix Library ;uilder ool is used for defining t(e tem%late %arameters& LogixView uses t(is information to determine w(at variables in t(e tem%lates are to be substituted w(en t(e tem%late is instantiated* (ow t(e variables are de%loyed /controller sco%e or %rogram sco%ed0* if t(e variables are ma%%ed to $=* and if "#$ gra%(ic library dis%lays are associated wit( t(e tem%late& 2& HMI Alarms Builder Tool for Logix ata Ty!es& LogixView %rovides an alarm builder tool for t(e following "#$ server based alarm systems. ,7 57 tag)based alarms /for use wit( Factory al! View Version -0& ,7 "#$ alarms /for use wit( Factory al! View Version 2 or Version -0& #7 "#$ alarms /for use wit( Factory al! View Version 2 or Version -0&

Unfortunately* none of t(e alarm database files for t(e above alarms systems are com%atible wit( eac( ot(er and none of t(em s(are common definitions& LogixView uses common alarm definitions t(at can be used for generating all t(ree ty%es of alarms& 5larm definitions are based on Logix tag data ty%es& For exam%le* su%%ose you want to use t(e following 8$'>7N"5N67' data ty%e elements for alarming. a& Use 8V""5larm and 8VLL5larm ;oolean out%uts for 8V (ig()(ig( and 8V low)low alarms* res%ectively& (e alarm server raises an alarm w(en t(e 8V""5larm and 8VLL5larm are non):ero& b& Use t(e 8V real in%ut as an analog in%ut& Use t(e 8V"Limit and 8VLLimit values as t(e alarm limits& (e alarm server %olls t(e 8V value and t(e current 8V"Limit?8VLLimit values& $f t(e 8V value goes outside of t(e alarm limits* t(e alarm server generates an alarm& c& Use t(e ,tatus1 bit values for alarms& $f any of t(e bit value c(anges to 1* an alarm is generated and t(e alarm message corres%onding to t(e bit value& For exam%le* t(e @,tatus1&0A bit indicates instruction fault* @,tatus1&1A bit indicates 8V faulted* etc& 9it( t(e LogixView alarm definition* t(e same 8$'>7N"5N67' alarm definition can be used for all t(ree ty%es of alarm servers& (ere would be additional configuration %arameters for eac( %articular ty%e of alarm servers /e&g&* t(e alarm severities are defined differently in t(e different alarm servers0& 1& HMI Alarms Builder Tool for Logix I"# Modules& 5larms for $?= modules are useful to %rovide notification in t(e "#$ t(at t(ere are %roblems wit( (ardware& ;uilding alarm definition for $?= modules is more difficult because different data ty%es can be used for t(e same module ty%e& (e $?= tag data ty%e de%ends on t(e communication format configured for t(e module& $nstead of (aving to !now a %riori t(e module data ty%e you want to build alarms for* LogixView %rovides an tool for building $?= alarms& 2& HMI $ra!%i& #b'e&ts Builder Tool& #ost %rocess gra%(ic dis%lays are develo%ed using common dynamic gra%(ical symbols& (e following %rocess dis%lay contains many valve symbols& 6lic!ing on a valve symbol o%ens t(e corres%onding 8$'7 tag face%late& 6onfiguring eac( symbol and lin!ing t(em to t(e correct controller tag can be very time consuming& LogixView %rovides a gra%(ics symbols builder tool t(at can automatically create t(e gra%(ic symbols wit( t(e dynamic lin!s %reconfigured& (e user creates "#$ gra%(ic ob3ect tem%lates using Factory al! View ,tudio& (e ob3ect tem%lates can contain Factory al! View global ob3ects& (ese tem%lates are ex%orted into B#L format so t(at t(ey are readable by LogixView& (e LogixView tool is used for defining t(e dynamic lin!s in t(e tem%lates to Logix data ty%es& (e tool can be used for Factory al! View ,7 and #7&

-& HMI is!lay Tem!late Builder Tool& $n many a%%lications t(ere are common units t(at (ave t(e same or very similar dis%lays& (ese common units are often combined into new dis%lays to re%resent gra%(ics for a new or uni<ue %rocess& (e LogixView 'is%lay em%late ;uilder ool is used for building dis%lay tem%lates t(at contain references to multi%le tags of t(e same or different data ty%e& (ese references can %oint to ob3ects configured wit( t(e LogixView "#$ ob3ects builder tool or ot(er "#$ ob3ects& (e %rocedure for building dis%lay tem%lates is very similar to t(e %rocedure for building gra%(ic ob3ect tem%lates for s%ecific Logix data ty%es& C& HMI Library (ontainer& "#$ library com%onents can be organi:ed using t(e LogixView "#$ %ro3ect tree& 5 %ro3ect tree exam%le is s(own below& (e library com%onents are organi:ed into se%arate @framewor!A folders to distinguis( t(em from a%%lication s%ecific com%onents& 9(en a new "#$ a%%lication is created* LogixView %rovides a function to co%y t(e "#$ library com%onents to t(e "#$ a%%lication server directories& ,everal sam%le "#$ framewor! libraries are included wit( t(e LogixView %ac!age&

1.2

Logix Configuration Tools

(e following Logix configuration tools are %rovided to reduce controller develo%ment time. 1& 6reating new controller file by eit(er co%ying an existing 56' file tem%late or creating a new one wit( some default features different from +,Logix -000& 2& 5dding new tas!s* %rograms* and routines& 1& 'eleting tas!s* %rograms* and routines& as!s and %rograms can be deleted wit(out (aving to unsc(eduled t(e %rogram from t(e tas! before(and& 2& Use Logix library tem%lates to add code to t(e controller&

-& 7dit tag data using filters& (e tag data editor window allows t(e user to configure reusable data element filters& For exam%le* define a filter for t(e 8$'>7N"5N67' data ty%e t(at s(ows only t(e 8* $* and ' tuning %arametersD define anot(er filter s(owing t(e engineering unit scaling %arameters* etc& (is sim%lifies tag data editing by not (aving to scroll t(roug( all t(e tag data elements to find t(e ones to edit& C& #a% $= tag elements to alias tags& 7& #a% $= tag elements to tag buffers& LogixView automatically generates structured text code for ma%%ing $= tag values to s%ecified tag elements& 8& ag 'escri%tion 7x%ort and $m%ort ool& (e +,Logix -000 controller tag descri%tion is commonly configured wit( tag information /e&g&* tag label* tag descri%tor* engineering unit* drawing number* etc&0& LogixView can extract t(e information from t(e controller file based on user)defined field formats /e&g&* t(e tag descri%tion can be viewed as containing several fields* wit( eac( field se%arated by a delimiter E tab* carriage)return* etc&0& LogixView uses t(e tag label* tag descri%tor* and engineering units in t(e ot(er tools&

(e LogixView tag descri%tion tool ex%orts selected tag descri%tions into a text file& (e text file can be edited using a text editor or s%reads(eet %rogram /e&g&* #icrosoft 7xcel0& (e edited file can be im%orted bac! to t(e +,Logix -000 controller 56' file& F& ag 'ata 7x%ort and $m%ort ool& +,Logix -000 controller tag data values for selected tags and selected data ty%e elements can be ex%orted into a text file& (e tag data can be edited using a text editor or s%reads(eet %rogram& (e edited data file can be im%orted bac! into t(e +,Logix -000 controller 56' file& (is

allows easy off)line bul! editing of controller data& 5 conversion tool is %rovided t(at converts t(e tag data text files to a format used by t(e +,Logix -000 ag 'ata U%load ? 'ownload tool E t(is allows bul! editing of online controller tag data&

1.3

FactoryTalk ie! HMI Configuration Tools

(e following "#$ configuration tools are %rovided to reduce "#$ develo%ment time. 1& 5larms ;uilder ool& Using t(e Logix data ty%es "#$ alarm library definitions t(is tool creates "#$ alarm im%ort files for use wit( t(e Factory al! View ,7 "#$ alarm server* 5larms G 7vents /570 tag)based alarm server* and t(e #7 "#$ alarm server& 2& #odule $= 5larms ;uilder ool& Using t(e Logix $?= modules "#$ alarm library definitions* t(is tool creates "#$ alarm im%ort files for use wit( t(e Factory al! View ,7 "#$ alarm server* 5larms G 7vents /570 tag)based alarm server* and t(e #7 "#$ alarm server& 1& Hra%(ic =b3ects ;uilder ools for ,7 and #7& Using t(e "#$ gra%(ic ob3ects library* t(is tool creates instances of t(e "#$ ob3ects for selected Logix controller tags& For exam%le* t(e "#$ library may contain a valve symbol tem%late to associate t(e valve wit( 8$' data ty%es& (e valve symbol may contain a numeric value t(at dis%lays t(e 8$' controller out%ut* a tag descri%tion text and a touc( animation for launc(ing t(e 8$' face%late& (e tool creates instances of t(e valve for all selected 8$' tags& 7ac( instance would automatically be configured wit( t(e tag descri%tion* face%late name and t(e Logix tag address& 2& 'is%lay ;uilder ool& Using t(e dis%lay tem%late libraries* t(is tool allows you to create "#$ dis%lays by dragging)and)dro%%ing Logix tags to t(e configuration window& -& Hlobal =b3ects Lin! ;rea!er ool& Hlobal ob3ects are very useful for creating gra%(ic tem%lates& 6(anges to t(e global ob3ect tem%lates /base ob3ects0 are automatically reflected in t(e lin!ed instance ob3ects /reference ob3ects0& Unfortunately* if t(ere are @manyA instances of global ob3ects in a dis%lay or if t(e global ob3ects are @com%lexA /e&g&* contains a great deal of animations and tag values0* t(en loading t(e dis%lay can be very slow& (ere are no rules t(at define w(at is too @manyA and w(at is @com%lexA& $f you observe t(at dis%lays wit( global ob3ects are loading too slowly* t(en you can use t(e Hlobal =b3ects Lin! ;rea!er ool to remove all t(e global ob3ect lin!s from t(e dis%lay& 4ou can !ee% a co%y of t(e dis%lays t(at contain t(e global ob3ects for develo%ment and you can create a co%y of t(e dis%lays for de%loyment t(at do not (ave global ob3ect lin!s&

C& LogixView "#$ organi:er and library container& LogixView automatically organi:es t(e %arameter files t(at it creates for t(e different tools /e&g&* se%arate folders for navigation trees* dro%)down menus* toolbars* tag %arameter files* $= %arameter files0& (e user can also organi:e %rocess dis%lays and face%late dis%lays into user defined folders& 6ommonly used com%onents can be organi:ed under @framewor!A folders to denote t(em as library files for reuse in different View "#$ %ro3ects& LogixView %rovides tools for organi:ing t(e files under different library folder names E e&g&* organi:e t(e libraries based on industry or customers& ools are also %rovided t(at can co%y t(e library files to and from t(e "#$ a%%lication directories& 7& Navigation ree ;uilder ools for ,7& (e navigation tree builder tool generates s%ecially formatted %arameter files t(at can be used wit( t(e LogixView navigation tree 5ctiveB control& 7rror. +eference source not found %rovides instructions on using t(e 5ctiveB control& ,7 dis%lays using t(e 5ctiveB control is used for s(owing t(e following list ty%es in a tree view structure. a& #odule $= list& ,imilar to t(e a%%earance of t(e $= configuration tree in +,Logix -000& 6lic!ing on a tree branc( launc(es a module face%late& 6ustom module face%lates can be associated wit( module $= ty%es& $f custom module face%lates are not configured* LogixView %rovides a generic face%late t(at dis%lays t(e moduleIs in%ut configuration data& $f t(e controller configuration contains code generated by t(e Logix 6onnection ,tatus 6ode Henerator Utility* t(en t(e $= module connection status face%late is also automatically launc(ed w(en a tree branc( is clic!ed& b& 6ontroller tag list& 5 list of all controller tags wit( face%lates associated wit( t(e tag data ty%e& 6lic!ing on a tree branc( launc(es t(e tag face%late& c& 'is%lay tag list& 5 site ma% of all %rocess dis%lays in t(e "#$ a%%lication can be easily created& ;y organi:ing %rocess dis%lays under user)defined folders in t(e LogixView "#$ tree* t(e site ma% automatically reflects t(e folder structure& 6lic!ing on a tree branc( launc(es t(e dis%lay& 8& oolbar and 'ro%)'own #enu ;uilder ools for ,7& ,imilar to t(e navigation tree builder* t(e toolbar and dro%)down menu builder creates s%ecially formatted %arameter files& ,7 dis%lays containing V;5 code reads t(e %arameter file and %o%ulates ,7 button ob3ects wit( ca%tions and ,7 commands& ,am%le dis%lays are %rovided wit( t(e LogixView "#$ libraries& LogixView %rovides a gra%(ical interface for configuring t(e toolbars and dro%)down menus using sim%le drag) and)dro% o%erations& 5 new feature is added in LogixView Version 2 t(at creates navigation %arameter files for Factory al! View Version - navigation dis%lays t(at do not use V;5 coding&

F& ,am%le LogixView "#$ libraries for ,7 and #7& wo sam%le ,7 "#$ libraries are included& =ne t(at can be used in +,View Version 2 or Factory al! View Version -& (e ot(er is used for Factory al! View Version - t(at includes t(e new 57 alarm ob3ects and t(e o%tion of using t(e new dis%lay doc!ing features& $t also %rovides sam%le dis%lays for use wit( t(e ot(er LogixView tools& 9(en used wit( t(e LogixView tools* t(e sam%le "#$ libraries %rovide a <uic!)and) easy way of develo%ing "#$ a%%lications t(at (ave many features ex%ected from traditional '6, "#$ users& 10& Juic!;uild ools& (e LogixView Juic!;uild tools execute several ot(er tools wit( a single clic!& +unning Juic!;uild co%ies "#$ library files to t(e "#$ %ro3ect directory* creates alarm im%ort files* creates controller tag list and $= module list& 9it(out doing anyt(ing else* Juic!;uild %rovides a running a%%lication wit( alarming and access to controller tags via face%lates& Use t(e ot(er LogixView tools to build a full featured "#$ client wit( dis%lay navigation and %rocess gra%(ics&

1."

#oft!are Installation

5ut(ori:ed users are given instructions to access a F 8 site for downloading t(e LogixView software %ac!age& 5ccess instructions are not %rovided in t(is document&