Newton-Willbanks Engineering, Inc.

DeviceNet Troubleshooting Tips

My favorite guide is by Robert Law and can be found at ODVA: http://www.odva.org/Portals/0/Library/Publications_NotNumbered/DeviceNet_Troubleshooting_by_Robert_D_Law.pdf

Turck has some info on DeviceNet and other networks at: http://www.turck-usa.com/Support/White_Papers_~_Tutorials/

If you're using Allen-Bradley's RSNetworx for Devicenet, there is a good guide at: http://www.theautomationbookstore.com/idc/groups/literature/documents/gr/dnet-gr001_-en-e.pdf

Woodhead has a quick guide to design, installation, and testing at: http://www.woodhead.com/data/current4701/Woodhead_Building%20a%20Functional%20DeviceNet%20Network.pdf

Allen-Bradley Inview Notes

I recently hooked up an Allen-Bradley Inview to a PLC5/60 via remote I/O and need to remember a few things.

Inview: A-B #2706-P42R

Remote I/O Module: A-B #2706-PRIOM

Software: Inview Messaging Software 2.2

The Inview itself has a serial port that connects to the RIO communications module. The default parameters of the serial port are 9600, N, 8, 1. You can use a A-B #2706-PC CABLE1 (9-pin male to RJ-45) to talk to the Inview to set the serial port address. You can do this using the Inview software (Tools > Set Serial Address).

You must talk to the serial side of the remote I/O module at least once to configure the RIO parameters. The remote I/O module is the same module as used in PanelViews. So when you use RSLinx, that's what it shows up as when you do a RSLinx auto-configure and when you do a Who. The serial side parameters were 19.2, N, 1 and I used a 9-pin straight "female-female" cable (that seems to be an oxymoron). You configure the RIO parameters using the Network tab in the Inview software. After using the software to configure the network parameters, you will be given the option to save and/or download the parameters. Be sure to enable pass-thru as that lets you download messages from your computer, through the PLC5, into the display. After you get the Inview communicating with the PLC via RIO, you can do the rest of your work using pass-thru just like with a PanelView.

A couple of caveats:

1) The version of Inview Messaging Software that I was using was pretty dumb when it came to downloading. It reported that downloading was taking place (counting up to 100% done) even with the cable disconnected. Very confusing - I spent a lot of time thinking I had downloaded everything when in fact I hadn't even talked to it. When downloading, the Inview screen goes blank or shows some of the messages going by.

2) When you get the RIO module set up, it will show "no network activity" until you correctly hook up the blue-hose. Also, the PLC5 RIO auto-configure will recognize the Inview RIO module if you have everything set up right.

3) Remember that the Inview and the RIO module are two distinct devices. They are connected to each other serially. I thought it was strange that the Inview was configured as 9600 and the serial side of the RIO module was at 19,200, but they communicated OK.

4) The blue-hose connection to the RIO module was the opposite of what I thought it should be. Maybe PanelViews are that way too, I don't remember. Anyway, the connection detail are in the manual. Looking at the connector plugged into the module, the connections from top to bottom are: CLR, SHLD, BLU.

5) On newer Inviews, when an undefined message is triggered, "UNDEFINED MESSAGE #XX" is displayed on the Inview. On older Inviews, a blank message is triggered.

6) If everything downloads OK, but the messages don't display, check to make sure the Inview serial address matches the address in the "download Comms" configuration. If they're not the same, the messages won't be displayed.

Well Control SCADA Project - RTU Slideshow

Here's some pictures of a well control RTU using an Allen-Bradley Micrologix 1500 PLC communicating with an Intellution Fix 32 host.

>

Alternative Source for Allen-Bradley Processor Batteries

Alternative source for batteries for Allen-Bradley processors:

http://www.batterystation.com/lithium.htm

For example, the ControlLogix battery, 1756-BA1, is a CR17335SET-FT with wire and plug attached.

See Allen-Bradley's Knowledgebase Article G16620 for a cross=reference of all A-B batteries:

http://domino.automation.rockwell.com/applications%5Ckb%5CRAKB.nsf/0/EDC55CC3844C6BA085256AFB00647305?OpenDocument

Micrologix 1500 LRP – Intellution ABR Driver Configuration

11/2/04

This document describes how to setup a Micrologix PLC to communicate to a host computer
using the Intellution ABR driver.

Hardware

A null modem cable was used between the host computer and Channel 1 of the Micrologix PLC.
Channel 0 was used for programming.

 

Micrologix Communications Configuration

This is the channel configuration as set up in RSLogix 500.

(Project>Controller>Channel Configuration>Channel 1)

This configuration assumes that remote communications uses Channel 1 of the Micrologix
processor. The node address is 21 decimal.

RSLinxCommunications Configuration

The following screenshots show the polling master configuration as set in RS-Linx.

(Communications>Configure>AB_MASTR-1)

This configuration assumes that remote communications uses Com 1 of the host computer.
The polling list must contain the node addresses of the PLC’s you want to poll. In this
example, the remote node address is entered as 21 decimal.

 

Intellution Fix ABR Driver Configuration

(SCU>ABR)

Channel Configuration

The channel configuration references the driver name as entered in RS-Linx (here as
AB_MASTR-1).

Device Configuration

The device name can be anything (here this is PLC21). This name will be used as the device
name in the Intellution database.

One thing that is potentially confusing here is that the device address must be entered as
an octal number. Everywhere else it is entered as a decimal number. (Here: 21 decimal =
25 octal).

Block Configuration

The block name can be anything (here this is DataBlock0). The Intellution database use
the actual address in the format: Device Name:File:Word:[Bit]

Intellution Database Builder

The device is ABR, the name of the driver. The I/O address is entered in the format of:
Device:File:Word:[Bit]

Here, the address is N7:0/1 of the PLC at node address 21 decimal.

Allen-Bradley Cables

Serial Programming Cable for ControlLogix, PLC5, SLC500, etc.
9-pin, Female-Female, Null Modem

Download Cable for DL40, Old PanelView?
9-pin, Female-Female, Straight Thru

Cable Pin Out - Autotech SAC-RL100 Resolver

Reference	Connector Pin	Wire Color
R1	F	GRN/BLK
R2	E	GRN
S1	D	YEL/BLU
S2	B	BLU/BLK
S3	C	YEL
S4	A	BLU
GND	G	SHLD

TCP QuickPanel/QuickDesigner Compatibility

Total Control Products
Hardware/Software Compatibility
1-22-01

There are three different hardware generations of the Total Control Products series of QuickPanel products.  Additionally, there are many versions of the QuickDesigner software used to program these devices.  Below is a matrix that show which versions of software is compatible with each generation of software.

QuickPanel Generation         QuickDesigner Versions

QPX-1                       1.X to 2.4

QPX-2                        2.2 to 3.4

  QPX-3                       3.32 to 3.4?

Additionally, QPX-1 supports only the downloading of project files.  Uploads of the project file from the QuickPanel are not supported by the QPX-1generation. Both uploads and downloads of project files are supported by QPX-2 and QPX-3.

For additional information on TCP products, contact: 

            GE Fanuc
            Voice:  800-GE FANUC (433-2682)
            Website: http://www.gefanuc.com/en/ProductServices/VisPCSolutions/QuickPanel/index.htm l

Questions?

If you have any questions, email me at don at plcapplications.com

Using Intellution S_7 Driver and Siemens CP-5412

Using Intellution S_7 Driver and Siemens CP-5412
4-22-99
Revised, 10-5-99

Contents

1. General
2. S7app.doc from Intellution
3. S7setup.doc from Intellution
4. Intellution SCU Poll Record Setup Screenshot
5. Siemens COML S7 Setup Screenshot
6. Siemens PG/PC Setup Screenshot
7. Questions?

General

These are some notes on how to use the S_7 Driver from Intellution with the Siemens CP-5412
Profibus board. A Siemens S7-300 was being interfaced with Intellution 6.15 (later Version 7.0).

The following hardware/software was required:

CP-5412 (A2) Profibus Board Siemens 6GK15412BA00 ($782)

S7-5412 Software Siemens 6GK17025CW503AA0 ($736)

S_7 Siemens Driver Intellution ($500)

The Siemens software is copy protected using a software key. However, it will run without the
copy protection installed. A nuisance window is randomly generated until the protection is installed.

 

S7app.doc

The following is the document "S7app.doc" received from Intellution on 2/9/99.

Supported Hardware and Requirements:

The S_7 driver is used to communicate to Siemens Series 7 plc with the 300 or 400 cpu. Step 7 software is required to configure the
plc. The driver communication can be done via Profibus or Siemens Industrial Ethernet. Depending on the mode of communication,
different accompanying software is required.

The Siemens Industrial Ethernet can run with a regular Ethernet card. Intellution tested the 3-Com Etherlink III. When using a standard
Ethernet card, the required Siemens software is the SoftNet for Industrial Ethernet.

Industrial Ethernet can also be run using the tested CP1413 card. The Simatic Net S7-1413/WindowsNT version 1.10 configuration
software for the S7 plc is the minimum requirement. Other Industrial Ethernet cards that can be used are the CP 1411 and CP 1511 cards
with accompanying software.

Profibus can also used, the CP 5412 card was tested. The card comes with the required configuration software. The CP 5411 and CP 5511 can
also be used with Profibus.

Configuration:

Whatever means of communication is being used, the S_7 driver has fields that first must be defined in the required card configuration software.
Two such fields are the VFD name and the connection fields. When these parameters are configured under the card software, they must be
modified into the Siemens Com L database. These names are then entered into the related field under the configurator.

The setup of the card software is similar to that of the Technical Functions,TF1driver, in terms of setting up the Siemens configuration layer
configuration except it does not use application associations.

Troubleshooting

Mission Control is usually the first place to check for information. Unfortunately, the driver error codes only specify that there are errors. A
communication issue is most likely related to the card configuration software not configured correctly.

Some thing to verify:

• The VFD name and Connection in the S7 driver must match the names in the card software and must be configured in the Siemens ComL
  database.
• The Local and Remote TSAP addresses must be correct. Local TSAP is that of the card. Remote TSAP is that of the plc. These are Siemens
  settings.
• If any diagnostics software is available, it should be used to verify communications to the hardware.

 

 

S7_setup.doc

The following is the document "S7_setup.doc" received from Intellution on 2/9/99.

The items in italics are the values for this project.

Here is the information needed for the S_7

1. Softnet Setup , Look at Startup.txt
2. Open COML S7 softnet

   Enable Profibus

   Give a name to the connection for example API1 (S7_PLC2)

   Give a name to the VFD for example VFD1 (VFD1)

   Give the PLC IP Address (2)

   Give Local TSAP for example 01.00 (01.00)

   Give the Remote TSAP: the remote TSAP start with 02.XX (02.00)

   XX is the position of the CPU and not the CP in the PLC RACK for example 02

   Insert the configuration in the station list

   Save as for example Startup.txt. This is your Connections database name.

   Generate the Connections database

3. Under Control Panel Access to the Setting PC/PG
4. Under Access Point of application give a name for example FIX_S7 (CP_L2_1)

   Check the network: Profibus

   Go to the properties button and indicate the same name or Connections database

   In this example the name is Startup, so you would enter C:\SINEC\COMS7.NT\Startup.ldb

   Make sure you have setup the Profibus side.

5. Fix Driver , Look a Example.S_7

Fix Hardware Interface

Communication processor: FIX_S7 (CP_L2_1)

VFD name: VFD1 (VFD)

Connection: API1 (S7_PLC2)

Intellution SCU Poll Record Setup Screenshot

Addressing

A – output

C – counter

E – input

M-bit memory

PA-peripheral output

PE-peripheral input

T-timer

Z-counter

DB-global data block

Data Types

ASCII-text

BYTE-byte (unsigned)

COUNTER-counter

DWORD-double word (unsigned)

DINT-double integer (signed)

INT-word (signed)

REAL-floating point

STRING-complex string defined in the PLC

TIMER-timer

(See Intellution S7 Driver manual for more info on addressing)

Siemens COML S7 Setup Screenshot

Be sure to open up and save to the "startup.txt" file. Also, be sure to convert it to a binary file using the file menu.

 

Siemens PG/PC Setup Screenshot

 

Questions?

If you have any questions, email me at don at plcapplications.com

Quick Setup of PLC5 Ethernet Connection

Quick Setup of PLC5 Ethernet Connection
11-25-02
Contents

1. General
2. Step 1 - Physically Connect PLC5 to Network
3. Step 2 - Setup PLC's Communication Parameters with RSLogix5
4. Step 3 - Verify the Physical Connection
5. Step 4 - Setup RSLinx
6. Step 5 - Test the Connection
7. Questions?

General

These are some notes on how to quickly setup a simple network for use with a PLC-5 Ethernet
processor.  Setup of a SLC5/05 is similar, except that a transceiver is not required.

The following hardware/software was used:

Allen-Bradley PLC5-40E

CentreCOM 210TS 10 Transceiver

Allen-Bradley RSLinx (Lite or better), Version 2.30.01

Allen-Bradley RSLogix5, Version 5.00.01

Microsoft Excel 2000

Step 1 - Physically Connect PLC5 to Network

The first step is to physically connect the PLC5 to your network.  On the PLC5-40/E, the ethernet
port is channel 2 and is also referred to as the AUI port.  It is a 15-pin, female D-shell connection. 
My existing network is a 10 MPS thin net setup with several hubs connecting to a router.  To go from
the 15-pin connection on the PLC to the RJ-45 modular connection on the hub, a twisted pair transceiver
(also called a MAU, medium access unit) is required.  I used a CetreCOM 210TS that I bought for $10
on the internet.  This plugs into the port on the PLC and a standard modular CAT 5 cable was used to
connect this to the hub.

 

Step 2 - Setup PLC's Communications Parameters with RSLogix5

Start up RSLogix and connect to the processor using the DH+ and DH485 (serial port) connection. 
Double click on "Channel Configuration" under  "Controller".  Click on the "Channel 2" tab to reveal
the parameters for the ethernet port.  For a simple network (no subnets), the only parameters that
are important are the IP address and the link ID number.  Make sure that the "BOOTP Enabled" check
box is not checked and enter the desired IP address.  Enter an unused link ID number.  The rest of
the parameters can be left at their default values.

 

Step 3 - Verify the Physical Connection

This is an optional step to verify the physical link.  You can skip this step if you're confident of your
connection.  From a computer on the same network as the PLC, ping the PLC's address.  If everything
is hooked up right, you will get an answer for each ping.  You can use the DOS ping.exe program found
in the "windows" directory or download a Windows-based ping program such as Alchemy Lab's Ping 1.0.

 

Step 4 - Setup RSLinx

Start up RSLinx (Lite or higher) and and go to Communications --> Configure Drivers.  Then under the
"available Drivers" list, select "Ethernet devices" and click on "AddNew".  I usually use the default
name.  When the "Station mapping" window pops up, in the "Station" field, enter the same ID number
you entered in RSLogix5.  In the Host Name field, enter the same IP address as you entered in
RSLogix5.  Then hit the "Apply" button and you should be good to go.

Step 5 - Test the Connection

To test the connection, in RSLinx, go to Communications-->RSWho.  Double click the ethernet connection
and your PLC should show up.  To go online, in RSLogix , go to Comms-->Who Active Go Online and select
the PLC under the ethernet connection.  Programming can be done using RSLinx Lite or better.

Questions?

If you have any questions, email me at don at plcapplications.com (change the "at" to "@").