RSView Enterprise File Viewer Utility

How do I read and save ME, SE Datalog files, ME Alarm Log files, RecipePlus files and dBASE files with the RSView Enterprise File Viewer Utility?

Note: With this Viewer, once the log file is open the file can be saved as a CSV file. You can only access the datalog files if they are closed, as a result you must stop a running RSView ME application or RSView SE Datalog in order to be able to access the file.
This utility is used on Win32 (desktop) only. To read ME files from PanelView Plus CE or PanelView Plus terminals, copy the files to a compact flash card or SD card and move them to the desktop where the utility resides. These log files are in a non-standard format.
The RSView Enterprise File Viewer utility can be used to read and save the following files:

• SE Datalog file (*.DAT, *.OBF)
  
• ME Datalog file (*.LOG)
  
• ME Alarm Log file (HISTORY.ALM)
  
• dBASE file (*.DBF)
  
• ME RecipePlus file (*.RPP)

The SE Datalog files, ME Datalog files, RecipePlus files and ME Alarm Log file can be saved as CSV or DBF files.

---

SE Datalog File

1. Pick SE Datalog file in Files of Type
   
2. Select the DAT or OBF file to open in the Viewer.

---

ME Datalog File (ME Station)

1. Pick ME Datalog File in Files of Type.
   
2. Select the LOG file to open in the Viewer.
   
3. In the Set Time Zone dialog, select the time zone you would like the file to be converted in.

---

ME Alarm Log File 

Note: During runtime, four .ALM files are generated from an ME application with alarms: embedded.alm, history.alm, reset.alm and status.alm. Of these files only the history.alm can be opened by the File Viewer. The history.alm file is the main data table for alarm information, some additional information is saved to other .ALM files. If information is needed from the other files, such as embedded variable information, the File Viewer will automatically open the required files after opening the history.alm file. Any attempt to open the other .ALM files results in This ME Alarm File cannot be open and Convert log file error error messages.

1. Pick ME Alarm Log File in Files of type.
   
2. Select the HISTORY.ALM file to open in the Viewer.
   
3. In the Select RSView ME Alarm Setup File dialog, select the ME version and the alarm setup file (*.mal).

The File Viewer utility uses two (2) files in distinct, separate directories on both ME Station and on PanelView Plus. The first being History.Alm (reference the capture below) located in :
C:\Documents and Settings\All Users\(Shared) Documents\RSView Enterprise\ME\Logs\Alarms\M_Alarms on ME Station and
\storage card\rockwell software\rsviewme\logs\YOUR_APP_NAME\M_Alarms\ on PanelView Plus v3.2-v5.10 and
\Windows\Logs\YOUR_APP_NAME/M_Alarms on PanelView Plus 6 (v6.xx)/
NOTE: Only the History.Alm file will be viewable and useable by the utility.

The second (2nd) file required by the File Viewer utility is MachineAlarms.mal. Reference the capture below located in: C:\Documents and Setting\Your User Login Name/local Settings\Temp\~MER.00\M_Alarms on ME Station and
\Temp\~MER.00\M_Alarms\ on PanelView Plus v3.2-v5.10
NOTE: This folder and file will only be available when ME Station has successfully loaded the MER file.

1. Launch the File Viewer utility and set the Files of Type dialog box to ME Alarm Log File (*.ALM).
   
2. If the Viewer does not automatically open the correct directory containing the History.alm file then navigate to the path in the capture below ( Capture History.alm ) under the RSView ME alarm log file:.
   
3. Click the proper format of  where the alarm files were copied from.
   (See the text in red below for more information on the platform types).
   
4. Click the Ellipses ("...") and browse to the path in the capture below ( Capture MachineAlarms.mal ) under RSView ME alarm setup file:.

A display similar to the one below ( Capture List View - history.alm.jpg ) should appear. The TrigIdx column corresponds to the order of your Triggers, on the Triggers Tab in the Alarm Setup within Studio, reference ( Capture Alarm Setup - Triggers Tab.jpg ). The count (of alarm triggers) starts at 0.
TrigIdx column, Rows 1 - 9, - All Alarm triggers tied to {::[AlarmIt]N7:0,L3}. Only 9 Triggers were used for this bit array, but it has the possibility of using all 16 bits x 3 words or 48 entries/triggers in TrigIdx 0 column and 48 entries in the Messages Tab of the Alarm Setup within Studio. Total count = 9 triggers..

TrigIdx column, Row 10, All Alarm Triggers tied to {::[AlarmIt]N13:20}. Total count = 1 trigger.

TrigIdx column, Row 11 - 17, All Alarm Triggers tied to {[clgx]test}. Total count = 7 triggers.

Alarm Trigger {::[AlarmIt]B70:0/0} was not triggered for this example. Its TrigIdx value would = 2.

Total Count = 0, if triggered 1.

The Alarm Messages tab has been provided for study. Reference Capture Alarm Setup - Messages Tab.jpg.

---

dBASE File

1. Pick dBASE File in Files of type.
   
2. Select the DBF file to open in the Viewer.

Command Line Parameter Capability

Command line parameter capabilities are supported to allow generating automatic reports.

Switches
SE Datalog file:	/sd
ME Datalog file:	/md
ME Alarm log file (Default for CE terminal log file):	/ma
ME Alarm log file generated by CE terminal:	/ma / ce
ME Alarm log file generated by Win32 (3.xx):	/ma /3xx
ME Alarm log file generated by Win32 (4.xx):	/ma /4xx
dBASE file:	/dbf
Adjust time zone:	/tz<Number in hours -12 to 13>
Show help dialog:	/?

Examples:

To convert to a CSV file: RSView Enterprise File Viewer.exe /md process.log process.csv /tz8
To open a file when the Viewer is launched: RSView Enterprise File Viewer.exe /sd datalog.dat

---

Installation

The attached zip file provides RSView Enterprise File Viewer v1.6.0.3 with support for FactoryTalk View 5.0 alarm files dated August 22, 2008.

1. Unzip the attached file.
2. Put RSTXViewCmn.ocx file under: C:\Program Files\Common Files\Rockwell\
3. Run RSView Enterprise File Viewer.exe.

---

Version History

v1.8.0.0 added support for Machine Edition version 6.x Alarm Log files
v1.7.0.0 added support for additional command line options, see the RSView Enterprise File Viewer version Help for details.
v1.6.0.3 added the following:

1. Show tag name in Trend.
   
2. Support to show Trend for ME datalog.
   
3. Change SE Datalog list view to show a tag name instead of tag index when xxx(Tagname).dat exist.
   
4. Fixed a problem with ME alarm on date/time format and alarm Ack date/time introduced in 1.5.0.0

File Attachments

• RSView Enterprise File Viewer 1500.zip (309.76 KB)
• RSView Enterprise File Viewer 1603.zip (313.68 KB)
• RSView Enterprise File Viewer 1700.zip (314.05 KB)
• RSView Enterprise File Viewer 1401.zip (309.18 KB)
• RSView Enterprise File Viewer 1402.zip (309.37 KB)
• RSView Enterprise File Viewer 1403.zip (308.86 KB)
• RSView Enterprise File Viewer 1404.zip (309.31 KB)
• RSView Enterprise File Viewer 1800.zip (53.01 KB)

Source : http://rockwellautomation.custhelp.com/app/answers/detail/a_id/33924

Read More

FactoryTalk View Machine Edition Data Logging Best Practices.

FactoryTalk View Machine Edition Data Logging Best Practices - Understanding Data Logging

This information is applicable only to the native Data Logging of RSView Machine Edition and does not apply to the DataStore or DataStore Plus ActiveX controls.
NOTE: The following information applies to version 5.x and older terminals. Testing has shown that a current, typical application will run faster and have less memory constraints on the 6.x platform.

What Does the RSView ME Data Log Model Do?

• Logs tag data to a storage file during runtime
• Historical Trending

Data Log Model (Design Time)

• Studio allows the creation of multiple Data Log Models. However, only 1 Data Log Model can be configured during runtime.
• Maximum number of tags allowed in a model is 100:
  • The model will not log data for string tags, array tags, parameters or expressions, and you cannot use tag placeholders in your data log model.
  • External Compact flash path is configured as \Storage Card2\log.
  • USB drive path is configured as \USB Storage\log.
    
    NOTE: Only 2711P-RCx, which is the RA Compact Flash card have been tested/supported.
• Data Log Model (Runtime)
• The data log will run as a continuous background task.
• Once the data log starts, it cannot be stopped during runtime by the operator.
• If the data log fails on startup, it will never start. A warning message is logged to diagnostics when the data log starts or fails.
• If diagnostics is not configured, you have no indication whether the data log started or not.
• If a write fails to a remote data log or external compact flash card, the data log will stop and never re-start. For example, if the CF card is removed while data logging, it will try to reconnect 3 times within a few seconds and stop if not reconnected.
• RSView ME doesn't support dynamic log file creation during runtime.
• The DataStore Plus ActiveX does allow dynamic log file creation for Versa View CE platforms.
• For additional information, refer to Technote Answer 35155 - DataStorePlus ActiveX Control for RSView Machine Edition.
• Best practices for a Panel View Plus 400-600 terminal is to data log to a external CF card or remotely.
• The Panel View Plus 400 – 600s are limited to 32 Mb for internal storage memory.
• The data log file can consume a max of ~4.5 Mb for 300,000 data points

Viewing Data Log Files

• File Viewer provides a one step file conversion process.
• For additional information on viewing these files, refer to Technote:
  Answer 33924 - RSView Enterprise File Viewer Utility to Read and Save ME, SE Datalog Files, ME Alarm Log Files, and dBASE Files.
• The log file is viewable in Excel or DBF with the File Viewer utility. Keep in mind that Microsoft Excel only supports a 64000 row limit (data log may be more than 64000 rows).

 Remote Data Logging

• The remote PC is require to be a member of a Domain. Remote Data Logging to a workstation will not work.
• The Panel View Plus/Versa View will be prompted to authenticate when the data log initiates. 
• Pre-authentication can be done from the ME configuration screen.
• RSView ME does not accept specific IP addresses of any remote computer. For example: Custom Logging Path “\\10.10.10.10\logs” will not work. A name resolved from the Domain controller “\\MY_PC\logs” will work.

Why Remote Data Log?

• The Log files are easily available for viewing on the PC.
• Data log memory consumption occurs on the PC, not the PVP/VVCE terminal.

Log Triggers

• Fastest log rate possibly is 100 ms.
• Logging too fast can cause performance related issues. For example, logging 100 tags as 100ms will cause a buffer overflow.
• Data logging is a background task. Best practice is logging at the slowest possible rate desired by the process being monitored.
• Increase datalog time to at least 300ms if logging 100 tags or reduce tag count to 40.
• On change, logging will update based on any tag configured in the model.

Data Logging Runtime Performance

Performance Considerations

• The max number of data points possible is 300,000 records.
• FIFO principal is used on the created Data Log File.
• The max number of data points will consume ~ 4.5 Mb of internal storage space. The data log write buffer will also consume 4.5 MB of RAM.
• Limit the maximum number of data points being logged to what is required.
• RSView ME will write data every 30 seconds to the data log. If the buffer fills up before 30 seconds it will write data to the log immediately.
• Data Log Memory is allocated on startup of the application.
• Fast logging rates can affect overall application performance.
• The HMI is required to Multi-task by data logging and update display information.
• Additional background tasks include Alarming, Global Connections, and Information Messages.

CPU Utilization

As the number of data points logged increases, the terminal CPU utilization at the time of opening a Graphic Display containing a Trend object connected to a Data Log will increase along with the time to open the Graphic Display. Typical CPU utilization for a 300,000 record Data Log is around 20%. Graphic Display opening time is around 15 seconds.

Best Practices for Optimizing Performance & Memory

Data Log Model (Design Time)

• Limit data logging to required tags only.
• Limit the maximum number of data points being logged to what is required.
• Log tag data at the slowest possible rate desired by the process being monitoring.

Data Log Model (Runtime)

• Panel View Plus 400-600 terminals should data log to an external CF card or remotely.
• Remote data log whenever possible.
• Configure all application to display warning messages in Diagnostics to alert the operator when the data log starts or stops.

Read More

Logix PIDE Function Block Information

Information on the PIDE function block and how it works.  Includes information on  using it in Cascade and Ratio Control applications.  This is a two part document which covers the majority of functions incorporated in the PIDE block.
Catalog Number: 1756 Generic
DocFullNum: G9057916
Revision:
Fixed in Revision:
Package:
Modual:

File Attachments

• PIDE Presentation Part 1.zip (115.09 KB)
• PIDE_Presentation 2.zip (157.6 KB)

 Source : http://rockwellautomation.custhelp.com/app/answers/detail/a_id/21894/related/1

 

Read More

ControlLogix RMPS / PIDE Instruction Example.

How to use the Ramp/Soak (RMPS) Instruction with the PIDE block?

The RSLogix 5000 v13 sample file attached below contains a very basic application with a RMPS and PIDE. A process simulator Task is also included for simulation purposes.

• While in Manual mode the user program directly controls the instruction's Out. The CurrentSegProg, SoakTimeProg and OutProg inputs are transferred to the CurrentSeg, SoakTimeLeft and Out outputs.
• When instruction is placed in auto mode, the ramp/soak functions resumes with the values last input from the user program.
• CurrentSegProg and SoakTimeProg are not transferred if they are invalid. This will explain a SoakTimeLeft at zero after a manual to auto transition and SoakTimeProg was zero.

More information can be found in RSLogix 5000 software Instruction Help file or in the Logix5000 Controllers Process Control and Drives Instructions  manual.

File Attachments

• RMPS_Example.ACD (126.53 KB)

 Source :  http://rockwellautomation.custhelp.com/app/answers/detail/a_id/34961/comment/19995
 
 
 

 

Read More

Obtaining Ethernet IP information from a 1756-ENET

1. First create a USER DEFINED tag called IP, and configure it as shown below:
   
   
   
   
2. Create a CIP message instruction like the one shown below.
   
   NOTE: Tag B3.0 is not required.
   
   
   
   
   
3. Configure the CIP message as shown below.  Note that the destination tag ENET_IP_INFO
   is a tag of type IP (User Defined).
   
   
   
   
   
   
4. Also note that the values that come back into IPx will be in reverse order.
   
   Example:
   IP Address of 130.151.191.138  would come back as:
   
   ENET_IP_INFO.IP1 = 8Ah = -118 (SINT) = 138 (DINT)
   ENET_IP_INFO.IP2 = BFh = -65  (SINT) = 191 (DINT)
   ENET_IP_INFO.IP3 = 97h = -105 (SINT) = 151 (DINT)
   ENET_IP_INFO.IP4 = 82h = -126 (SINT) = 130 (DINT)
   
   Since the values that come back have to be stored in a SINT, you would need to move them to an INT or a DINT.
   
   Below, I use the BTD (Bit Field Distribute) functions to move the data.
   
   
   
   
   
   
5. To determine if the Modules Bootp is enabled, create a MSG instruction configured as shown below:
   
   
   
   
   Memory5 is a DINT array, 2 elements in length.
   
   -  If Memory5[0] = 0, then Bootp is DISABLED
   
   -  If Memory5[0] = 1, then Bootp is ENABLED
   
   
6. To enable or disabled Bootp, you would configure a MSG instruction as shown below:
   
   
   
    - Place a value of 1 into Memory5[0] to ENABLE bootp.
   
    - Place a value of 0 into Memory5[0] to DISABLE bootp.
   
   After changing the modules mode to bootp, the module will not request a bootp
   address until the next time it is power cycled.

Source : http://rockwellautomation.custhelp.com/app/answers/detail/a_id/18606/related/1

Read More

Link Status from a Logix Ethernet module via CIP Generic Message in RSLogix 5000

Example below shows 1756-ENBT, but can be used with any Logix modules
Link Loss Status can be obtained from the 1756-ENBT by configuring a CIP Generic message to the module.If the Ethernet connection is broken the status can be monitored in the ControlLogix processor.
Procedure:
1)  Configure a MSG instruction as CIP Generic in RSLogix 5000 for the ControlLogix processor that is to monitor the 1756-ENBT status.


2)  Create the Destination tag (LinkStatusWord in this example) with data type of DINT. The communications path will need to point to the ENBT that you want to get status from, with the Class, Instance and Attribute as shown below.
CIP Generic Message Setup Screen:

3)  When the MSG instruction is executed the Link Status data will be written to the Destination word bit 0, in this example LinkStatusWord.0


IF Bit 0 = 1 The Link is active.IF Bit 0 = 0 The Link is Inactive. The above screen capture shows an active link.
NOTE:Bit 1 is module Duplex mode. If bit 1 = 1 the module is in Full Duplex mode. If Bit 1 = 0 the module is in Half Duplex Mode.Bits 2 - 31 are reserved and not used.

This technote can be used for dual port devices (1756-EN2TR, 1756-EN3TR, 1783-ETAP etc).
Second port information can be accessed by changing the Instance value to 2 (see message above)
Third port information can be accessed by changing the Instance value to 3 (see message above) 

Read More

Access IP information of 1756-ENBT/1788-ENBT modules with MSG instruction

The following steps describe how to access the IP Address for the 1756-ENBT via the user program. This also works with 1788-ENBT module.
The Source or Destination tag ipinfo is a SINT array of 22 elements, but may be longer if a Domain Name is included - see the Notes at the end.


To GET the module IP Address, configure a CIP generic message instruction, as shown below:



To SET the module IP Address, configure a CIP generic message instruction, as shown below:




Notes:

If a Domain Name is included in the SINT array, the source length may have to be up to 70 bytes long:

SINT[20..21]	Word value containing number of characters in Domain Name
SINT[22..69]	Domain Name - 48 ASCII characters

Read Array length should always be 70 bytes:

• 20 for addresses
• 2 for length
• 48 for possible ASCII domain name

Write Array length should be 22 plus the length value in ipinfo[20], padded to an even number of bytes (pad not included in the length).

Read More

RSLogix 5000: PIDE - Function Block Enhanced PID.

PIDE - Function Block Enhanced PID

This technote demonstrates the use of the PIDE function block instruction.
It uses two modes of automatic operation: program setpoint and operator setpoint.
To toggle between program setpoint and operator setpoint simply toggle the ProgOperReq bit in the PIDE instruction which is accomplished with the PROG_MODE_1 bit in the Main Routine.
When in program mode it gets the setpoint from the SPProg word in the PIDE instruction.
When in Operator mode it gets the setpoint from the SPOper word in the PIDE instruction
To toggle between automatic and manual mode simply set the ProgramManualReq bit and clear the ProgAutoReq bit in the PIDE instruction which is accomplished by toggling the AUTO_1 bit in the Main Routine.
The CVEU will track the value at CVProg when in manual mode
This Project has 3 tasks:

1. Main Task:
   The Main Task allows the user to set bits and put the PIDE in Program mode, Operator mode , Manual mode and to use Independent or dependent gains.
2. PID_Functions:
   The PID_FUNCTIONS task is a scheduled task that executes every 100 mS.   It contains the PIDE function block instruction and it has a task called Proc_lag which contains function block instructions that lag the PV from the CV to simulate a process variable.  
3. SETPOINT_GENERATOR:
   The SETPOINT_GENERATOR scheduled task executes every 10 seconds.  It simply changes the program setpoint every 10 seconds with the FAL instruction.  The setpoints are contained in the tag ARRAY1 which are 10, 15, 20, 30, 40, 60,80, 70, 50, and 30. 

The .ACD file is Called PIDS_FUN_BLK_DEMO and is attached below

This .ACD file was created using RSLogix 5000 ver 8.02 and a 1756-L1 firmware ver. 8.20.   It requires no I/O modules.

File Attachments

• PID_FUN_BLK_DEMO.ACD (105.88 KB)

Source : http://rockwellautomation.custhelp.com/app/answers/detail/a_id/20410
 

Read More