Lean MES Open Source Manufacturing Execution System
Flexible Manufacturing Solutions through Open Standards and Free Software....

RS FactoryTalk OSI-PI Historian and PIBaGen, Explored.


Educational material for system integrators.

Preface


Objective:

Reason:

Implementation:

Reason:

Area of applications:

Typical devices scenarios;
1. Environment: VM-IMAGE1, VM-IMAGE2, VM-IMAGE3, Windows 2003 Server virtual machines builds
    for FT and Vantage Point training course.
   - VMWorkstation images imported to VMWare Fusion.

   - Host system MacBook Pro OSX 10.5.8 Core2DUO@2.46GHz 8GB RAM


2. Original Environment Overview:
Environment before, above.

Environment after, below.
3. Changed Environment Overview (Above)
    Changes Explained:
    a. Historian Buffer deactivated.
    b. RsLinx Enterprise Sever assign/enabled from VM-IMAGE2 to VM-IMAGE3.
    c. FTLD FactoryTalk Live Data Interface assigned/enabled from VM-IMAGE2 to VM-IMAGE3.
    d. Memory increased to 1024 MB on both virtual machines.

Changes were made to simplify the environment, and at the same time demonstrate mechanism of solution components distribution.

Changes in details:
Fig.2

4. Registering new RSLinx Ent server hosted on VM-IMAGE3 in FTDirectory.

    In VM-IMAGE3:

    4.1 FT Console >Right Click the MyPlant >New Area {Sim} >Add New Server >(RSLinx Enterprise) >
          Computer hosting the RSLinx Ent server {VM-IMAGE3}.

    4.2 Restart RSLinx Ent Service.

    4.3 Verify SoftLogix is running.

    4.4 FT Console > Communication Setup > Device Shortcuts click "Add", type "SLogix". In Primary tab navigate to
          2, 1789-L60/A item, select, click "OK" (Fig.2).

5. Creating and Registering new History Data Collection Interface hosted on VM-IMAGE3 in FT Directory.

    In VM-IMAGE3:

    5.1 FT Console >System >connections >Historical Data >Right Click the Production Historian >New Data Collection
          Interface, confirm VM-IMAGE3 selected in Computer hosting the interface (Fig.3), Click OK.
Fig.3

    5.2 Previous step automatically creates a new FTLD2 Interface in FT Directory. Interface is a Windows Service, that
          can be managed trough MMC or PI-Interface Configuration Utility (Fig.4). Suggestion: In addition to service'
          dependency on tcpip driver, add Remote Procedure Call and PI Base Subsystem services.
Fig.4

    5.3 Restart the FTLD2 service to confirm it's operational state and updated dependencies.

6. Creating data source simulation for testing.

    6.1 Two Equations (Fig.5) will provide simulated data for demonstration purposes. Note the function' period,
          of the first equation, increases with the increase of the argument, thus good case for testing OSI-PI interpolation
          mechanism.
          Notes: A -constant, k -cycle count, once argument reaches a certain value, the computation after delay, will repeat
                      with k=k+1.
Fig.5

    6.2 Simulation project developed in RSLogix 5000 V17.00.00 (CPR 9 SR 1) and downloaded to SoftLogix Controller.
          Copy of project file is available here SLogix.ACD.
          Important! Project contains Task in Tasks folder, configured Type: Periodic, with Period:250 ms. (Fig.6).
          In other words, code will execute very 250 ms., computing values in functions indicated in Fig.5.
Fig.6

    6.3 Run simulation, set controller to "Rem Run". Observe function values changing while argument x incrementing.

7. Importing data sources (tags) from processor to PI Historian DP points.

    7.1 Adding Individual Historian Points to OSI-PI in FT Admin Console (FTAC).
          VM-IMAGE3 >FTAC >Right Click:Sim Area >Add Individual Historian Points...
          Select the FTLD2 collection interface, new interface hosted by VM-IMAGE3.
          Set Default scan rate to (3) 0.1 sec, thus Default scan rate =Task period(250 ms)/2.5 = 100 ms =0.1 sec. (Fig.7).
Fig.7

    7.2 Select and add the following tags; cycle, k, x, ySinx, ySqrt4kx (Fig.8). Click the OK, tags are then being created
          as points in OSI-PI database.
Fig.8

8. Modifying imported points in OSI-PI System Management Tool (SMT) Point Builder.
    In SMT navigate to Points >Point Builder >click the "Search" button. Set Tag Mask field to" *Sim*, click Search, then
    Select All, then OK. List of Points displayed in Point Builder. Use General tab to rename all points, to have source
    prefixes removed. Example: MyPlant.Sim:RSLinx Enterprise:SLogix.Program:Sim.cycle rename to Sim.cycle.
    In Archive tab, set both Exception Deviation and Compression Deviation to 0 to all point except cycle. After all
    modifications the Point Builder window will look like this (Fig.9).
Fig.9



Copyright (C) 2011 Agile Automation Technology LLC.