Ken Roach

This is a simple configuration example for navigating between Displays in FactoryTalk View ME with a "Navigation Bar".
This example uses the Global Connections feature, pointing the Remote Display Number connection at an internal HMI Tag (Display_Number_Read).
Whatever value is written to the Display_Number_Read tag will be the number of the Display that is shown.
The Global Connections feature is also writing the current Display Number to another internal HMI Tag called Display_Number_Write. This is just for the purpose of showing the difference between these two features, which are very often misunderstood or confused.
All three of the ordinary Displays are "Replace" type, which gives them Display Numbers (1,2,3). The Navigation Bar is another Display but it is an "On Top /Cannot Be Replaced" type and does not have a Display Number.
A Global Object would be another way to implement this functionality of a Navigation Bar. The Remote Display Number tag could also reside in a PLC, rather than as an internal HMI tag.
This project Archive was created in FactoryTalk View ME Studio 6.0 and cannot be opened in any earlier version of FactoryTalk View Studio or RSView Studio.
The file is a *.APA Archive file, compressed as a ZIP file for attachment to the MrPLC server.

This is a step-by-step writeup of how to do some automated Modbus protocol analysis on data passing through a Prosoft MVI56-MCM module using only Windows Hyperterminal, a text editor, and the excellent free Modbus Parser from Chipkin Automation Systems (www.chipkin.com).
This technique could be handy for debugging or monitoring a Modbus data stream during installation and commissioning of a MVI56-MCM, or for checking for a certain Modbus transaction in a stream of data. It's certainly a lot easier than trying to decode Modbus manually.
This technote works with the "classic" MVI56-MCM modules that Prosoft has been selling for about the past 10 years. It should also work with any of the MVI-series modules for the SLC, PLC-5, or FLEX platforms that run the same basic firmware.
The newest MVI56E modules have a web-based monitoring mechanism instead of a diagnostic serial port and I don't know if they have a Data Monitor function.
I still prefer the full-power Frontline Test Equipment (www.fte.com) NetDecoder suite of software, but that's because I do automation communication analysis for a living. For casual Modbus work, the Chipkin tool is a great labor reducer, and the amount of labor can be further reduced using Hyperterminal and a text editor such as UltraEdit.

In applications where unreliable IP transports (such as wireless) are used some users report "flaky" Produced/Consumed tag connections and I/O connections over EtherNet/IP.
Rockwell never recommends wireless Ethernet for I/O but some users overlook this recommendation or install links that should be reliable enough but due to installation or configuration issues are not and need to be troubleshot with the participation of the control system.
This logic example is a diagnostic tool to provide a timestamp and duration for connection faults. It is written for a controller Producing data to another controller over EtherNet/IP but would work the same for a connection across ControlNet or the ControlLogix backplane or for an I/O connection.
The program was written using RSLogix 5000 v12.06.
Just putting the remote Controller into this Controller's I/O tree is enough to establish a connection; the Produced/Consumed tag (called Produced_Data on the producer side and Consumed_Data on the consumer side) is not strictly necessary.
I've used logic like this to find interference from motion controllers or heavy motor starters as well as microwave oven interference in the 2.4 GHz range. It's not a cure-all diagnostic tool but it can tell you when and how often a connection is failing.
This logic may be used in conjunction with the traffic analysis tool triggering example to capture data on an Ethernet network on both sides of a connection failure event.

This is a writeup and two examples of using a ControlLogix or an SLC-5/05 to trigger the TShark IP analysis program on a PC using the SerialKeys feature of Windows.
I am placing this file on the MrPLC website both for sharing and so I can find it again when I need it !

To rule out problems with data traffic to AC drives sometimes I ask a user to monitor the DPI Diagnostic Items in the 20-COMM-E interface. These can be read using Drive Explorer Drive Executive or the 20-COMM-E embedded Web page.
But the controller can also read these values with a little help from the 20-COMM-E User Manual and some ladder logic for messaging.
The DPI Diagnostic Object is Class 0x99. The Diagnostic Item value is Attribute 1. But what's the Instance number ?
The Instance number for Adapter items begins at 0x4000 (16384) and I am interested in Items 49 through 55:
Item# Name Instance # Data Size (bytes)
49 EN Rx Overruns 16433 2
50 EN Packets Received 16434 4
51 EN Rx Errors 16435 4
52 EN Packets Sent 16436 4
53 EN Tx Errors 16437 4
54 Last TCP Reset 16438 2 (Read Only)
55 Missed IO Packets 16439 4
This ladder example just reads those 7 values repeatedly. I could be expanded to cover multiple drives.
These values are all reset when power is cycled which is why I'm interested in having the controller read them instead of standing around looking at the software monitor all day or trying to have people read them before they cycle power to the drive.

This is an example of how to control (start/stop and speed reference) a PowerFlex 40 drive with 22-COMM-E interface from an SLC-5/05 controller over EtherNet/IP.
I do not recommend this practice and this file is provided without warranty or support for illustration purposes only.
DeviceNet is the preferred method to network AC drives to SLC-500 controllers.

RSLogix 500 routine to read the first 20 parameters from an E3/E3+ overload relay on DeviceNet with an SLC-500 controller and 1747-SDN. This example uses the new DeviceNet Explicit Message (DEM) instruction introduced with OS302 Series C FRN10 firmware.
The 21st parameter is also important but will almost always be part of the I/O connection so we're only reading 20 parameters which fits more snugly into a data array.
This routine only reads from one E3+ device at Node 3 on the network.

6-rung code example to read one parameter from multiple AC drives on DeviceNet.

I use a lot of protocol analyzers but most of them lack good event triggers other than time or buffer size. If I'm looking for an event (or non-event) on my automation network that my PLC can detect I want the PLC to stand by all night waiting to push the "pause" button so I don't have to wade through megabytes of buffer data to find the problems.
This example uses a Windows Accessibility function called "SerialKeys" to allow a PLC to "push the button" on your PC running an analysis tool.

A Message instruction can be used to check the Ethernet link status of a 1756-ENBT or other ControlLogix family Ethernet module port to determine if there is a good Ethernet link.
This example shows how to send a CIP Generic Message to Class 0xF6 Instance 1 Attribute 2.
The applicable page from the EtherNet/IP Specification (www.odva.org) is included in the ZIP file. The program file was greated with RSLogix 5000 v15.

RSLogix 5000 v13 example for parsing a data string from a Sartorius-brand scale.
This is in response to Rodger Furey's inquiry in this thread:
http://forum.mrplc.com/index.php?showtopic=3919''>http://forum.mrplc.com/index.php?showtopic=3919' target='_blank'>http://forum.mrplc.

The ASCII instructions in the SLC/MicroLogix can be hard to use even if you are accustomed to other complex A-B instructions. They operate asynchronously to the CPU and work in a queue and have to be managed more carefully than message instructions.

Makes a table of the "diagnostic display" values that scroll across the 1771-SDN indicator.