Ken Roach

By the way, RSLinx 1.7 is nearly five years old and may not work correctly with Windows 2000 or XP, if those are the operating systems you've chosen. RSLinx Lite 2.41 is a free download !

What's supposed to happen, Kelvin, is that you set both PLC-5's in the hot backup pair to the same DH+ node number (I've never seen anyone use Node 0; try Node 1). The 1785-BCM module then forces the PLC-5's to behave differently; the Primary controller uses the assigned node number, and the Secondary controller uses the assigned node number + 1. Can you see both the PLC-5's using RSWho ? The 1785-BCM/BEM hot backup system isn't for beginners. Have you called Rockwell Automation support on this yet ?

The PLC-2 front port isn't a conventional RS-232 port, so a simple "wiring diagram" won't do the trick. You need a PLC-2 "smart cable" to connect your computer's serial port to the front port of the PLC-2. Only A-B sells those. There's an Australian company that sells a programming package that works with some PLC-2 models, but I haven't heard any feedback about them. PLC-2 isn't something I advise beginners to try; they're old enough that they should be left to guys who already have invested in the software and hardware to work with them.

What kind of interface device are you using to get online ? A 1784-KTX, or 1784-PCMK ? What version of RSLinx, and what is the node number you're assigning to RSLinx ? Going online with PLC-5's over DH+ is really pretty straightforward. Tell us more about your system and maybe somebody will be able to help. What does A-B tech support say about this ?

I would strongly recommend that you team up with Pyramid Solutions (www.pyrasol.com) and use their EtherNet/IP protocol stack. Pyramid is very well versed in ControlLogix connectivity; in fact, they build several products that go to market with an A-B logo on them. The best part about their Adapter software product is that they've ported it to several operating systems; Win32, WinCE, UNIX, and several embedded systems. That means they've already done the hard work to let you test on Windows and run on VMS. I've had two customers do this "the hard way". From one of them I have a file of e-mails demanding, pleading, and threatening for SLC-5/05 protocol examples. Another one borrowed my ControlLogix sales demo for two weeks... and kept it for nine weeks. The third implemented Pyramid's adapter stack in Solaris and is getting ready to ship their first sixteen remote stations. If you're dead-set on doing this yourself, go get the "ControlLogix Data Access" reference document. This should help you narrow down the services of EtherNet/IP to the subset that deals in ControlLogix tag access. http://www.ab.com/manuals/cl/1756-RM005A-EN-E.pdf

Um, yes, using an Ethernet card in your PC and an Ethernet network (or a cross-over cable) is the whole point of having an SLC-5/05 with Ethernet port. When you set up the AB_ETH driver, you'll have an option to Configure it. There will be a table for you to put in the IP addresses of PLCs on your network; put the IP address of the SLC-5/05 on that list. I guess that begs the question... does your SLC-5/05 have an IP address yet ? The PCMK/B card is meant for DH+ and DH-485, not for Ethernet.

"PCL" means "Peer Communication Link". It's an old name for the peer-to-peer protocol that later was renamed "Data Highway Plus". Every interface I've ever used that was labeled "PCL" I was able to interface with using DH+ hardware like 1770-KF2 or 1784-PCMK. Check out the DB9S connector on a Classic PLC-5/25 or PLC-5/15... it says "PCL". You're a brave fellow, getting into a PLC-5/250 system in this day and age. When I get calls on that platform I usually have to call one of our retired guys and consult with him.

Hmm. Works for me in v5.00. You have two check marks under File -> Report Options -> Ladder Setup for those two functions. There is a similar setup window for the on-screen display under View -> Properties -> Address Display. Make sure it's set up in the Report Options location or it won't print even though it's onscreen.

For the curious, here's the datasheet for the Fanuc robot's I/O options: http://www.fanucrobotics.com/datasheets/sc.../R-J3_%20IO.pdf

Come on, folks, get some thicker skins. I've scheduled some ControlNet networks of very few nodes (okay, just two) via the DF1 -> CNB route. Agreed, there's a lot more bandwidth available when you're routing through an ENET or ENBT module, but for just one robot connection on a ControlNet, RSNetworx should work fine bridging through the processor. I was hoping Joe would post some details about the robot interface; I'm surprised it can do three different networks.

You are going to have to explain more about your system. ControlLogix and ControlNet are different but related product families ! Is your robot connected via a ControlNet network and 1756-CNB module to the ControlLogix system ? Is that connection a "scheduled connection" that needs to be set up using RSNetworx for ControlNet software ? Who is advising you to "use Ethernet" in any part of this system ?

But that's likely not your problem at all, because of your description of having to reconfigure things after a power cycle. Go un-check the Auto Device Replacement ("ADR") settings in your 1747-SDN configuration. If you enabled ADR before you configured the 1794-ADN adapter, then there are configuration settings for the FLEX adapter stored in the scanner's ADR memory that are defaults from the EDS file. The analog module I/O size by default is different from what you have configured. When the 1747-SDN establishes communications with a 1794-ADN (such as after power cycle), it loads the ADR configuration (if that's enabled) into the adapter before it makes the I/O connection. If you enable ADR, do so after you have configured all the devices on the network and have their configurations in the RSNetworx offline file. Otherwise, there's a chance that something like this will happen as the ADR function rolls back your configuration changes.

Because the 1794-ADN has an I/O size that depends on settings you make for each module attached to it, you need to take extra care when you set it up. The I/O size of the 1794-ADN cannot be changed while it has an I/O Connection to a master device. You can disable the scanlist entry, or remove the ADN from the scanlist, or simply unplug the scanner from the network. If you don't, and you make a configuration change that affects the I/O size, the software will indicate an error code 0x0C (12 decimal), described as an "Object State Error".

WOW ! I had no idea about the origin of the Shark controllers. I was told seven years ago that I was responsible for supporting them in our office, and in that time there have been no phone calls about them ! Terrific link, jrwb4gm.

It's a classic problem with drives and DeviceNet that your identity object changes with each voltage range and drive model and interface, so there are hundreds of EDS files per manufacturer (OK, so Cutler-Hammer only has two. Then again, the only sell one drive.) I was surprised to find those EDS files on the ODVA site. There are more there than on Yaskawa.Com ! But there still aren't any for the GPD515 and the Si-N1 version 2.02. I guess we just got the very newest hardware in the mill ! Once we got through to a support guy in New Berlin, WI, it only took a few minutes for him to locate and send the correct files. I think I know what's up with your 1794-ADN... I'll look it over and post here.

I wonder what's going on with your DeviceNet scanner... the Scanlist is stored in nonvolatile flash memory, so there's no way you should have to reload it on power cycle. What is the error message flashing on the 1747-SDN when you have a problem with it ? Maybe you could post the *.DNT file from your system and I'd be happy to have a look at it. I use the 1747-SDN every day, but not too often with FLEX I/O.

Hey cpmiller, which kind of Yaskawa drives do you use and which interface ? I commissioned my first GPD515 with the SI-N1 interface last week and it was a big pain in the butt to get the EDS files; the factory finally had to send them to me because they aren't on the website. There is an older DeviceNet interface called I think the CM043, and it has a big colorful user manual. the Si-N1 manual is still in Jenglish, and also is not published on the website. I'm hoping for some hints on how to make the drive handle PLC Idle mode more gracefully... right now it just keeps running at the last commanded speed. If I actually fault the DNet connection, I have to re-establish the DeviceNet connection and send a Stop command before I can reset the drive.

You can inhibit an SLC I/O module and then remove it when the power is off without faulting the processor.. but not without powering down the controller. You will fault the controller, and may damage the module or the chassis backplane chip. The SLC is very protective of it's backplane consistency; it does a full check of module ID's and module health every single program scan. Modules must match their configuration precisely or the controller won't run. The SLC considers missing I/O to be an "out of control" situation. The FLEX I/O family can be removed hot, and can be used as expansion I/O for SLC's. As mentioned previously the ControlLogix system is really the family that was designed for Removal/Insertion Under Power.

That's what I like about the VPN method that lets me keep my logic software local to my PC, not at the customer site; the traffic is just PLC data, not video and keystrokes. It doesn't require a dedicated PC and Logix license at the customer site, either.

A separate post to keep the reading light: I think the preferred method for this sort of Internet access to automation networks is to use a VPN Appliance. You can use software VPN from vendors like CheckPoint and Microsoft, but as our Guest pointed out, it's often best to not depend on the IT weenies. At least once a month I have to go to our in-house IT administrator because one or more of my accounts has been disabled, lost, or shut down during maintenance. Hardware VPN can be cheap or it can be expensive; the SOHO3 device I mentioned above runs about $3000 with licensing and support. A home router/VPN applicance from Linksys can be as cheap as $70. It does take some study to be sure you can always get into your VPN from outside while still keeping out hackers and intruders. I think it's worth it because VPN can dramatically reduce your travel costs and reliance on on-site personnell, and it tends to comfort the IT weenies to the point where they will not demand absolute control over your automation networking.

Here's how one of my customers has done this: 1. Home/Office PC with dialup or broadband Internet access. This is the PC with RSLogix and RSLinx on it. 2. Netopia DSL Router. This connects to the client's DSL Internet service and provides three dedicated Internet IP addresses, and provides routing services for the internal network. 3. SonicWall SOHO3 VPN Appliance. Provides NAT translation for internal PC's to access the Internet, and provides an encrypted IP tunnel to the Home/Office PC in Step 1, using a software VPN Client program at that home PC. Once we overcame a configuration glitch in his A-B controller (no Default Gateway address configured) this worked like a dream. His client was helpful because they let him dedicate one of their external IP addresses to factory automation use, and in return he implemented a secure system by using a VPN appliance.

Take some advice from an old hand; buy the correct cable ! 1761-CBL-PM02 is only $50.00 USD. It's molded right-angle end fits flush with the controller top, and it has a snug notch in it that makes it very difficult to accidentally pull out of the MicroLogix 1200 controller housing. It works with all MicroLogix family controllers. If your time is worth less than $20.00 per hour, do the following: Get an old Appletalk cable from a computer surplus store. Cut it in half. Use pliers to flatten out the keying corners of the male plug. Wire it up according to the diagram in Rockwell Knowbase document G19095. Be always careful plugging this in; the keying corners won't protect you from plugging it in skewed or backwards and bending the pins. Be sure you didn't connect anything to Pin 1; it's +24 VDC and will fry your PC serial port. If you're already spending the money on an A-B controller, pony up the dough and buy an A-B cable.

Implementing the "TAP Protocol" used by most alphanumeric pagers is pretty ambitious for a PLC... and impossible for the MicroLogix 1000, which does not support ASCII functions. I've tried it, and gave up on the project after a couple of weeks of dabbling. It was cheaper to buy an autodialer than to spend my time figuring out the protocol. The simplest way to accomplish this task is to use a modem that is preconfigured to send text messages, but to get it's data from the PLC. A-B sells modems like this: http://support.rockwellautomation.com/pagi...pmodem_main.asp If you already have an Ethernet network in place, or MMI software running on a PC, you might consider the e-mail capabilities of the 1761-NET-ENI or the Messenger feature in RSView32.

I downloaded and read the E-Terminals DF1 driver Help file, and I saw two things that stand out. First, the default error-checking setting for a ControlLogix is "BCC" error checking, but the E-200 appears to only support CRC errror checking. Change that on the ControlLogix serial port configuration. Second, and most important, the E-200 appears to only support the older SLC and PLC type addressing, not ControlLogix tag names. You have to enter an equivalency table in RSLogix 5000 (under "Map PLC/SLC Addresses") that maps PLC-style data files to ControlLogix tag arrays. I'm willing to be incorrect about that; if you have a real user-manual that is more recent than their website then of course follow that. Post some more info about your Logix serial port settings and the addressing you're putting in the E-200 and maybe someone who is familiar with them can help further.

I guess I didn't make myself clear above, so I'll be explicit: The minimum revision of RSLogix 500 that will run on Windows XP is version 5.20. Version 5.00, Version 4.50, Version 4.10, Version 4.00, Version 3.01, Version 2.57, Version 2.10, and Version 2.0 will not run under Windows XP. When you install a new copy of RSLogix, use the ordinary Windows "Remove Programs" utility in Control Panel to remove the previous version; every "upgrade" to RSLogix 500 is a full installation of the software. The upgrade cost is a fraction of the full cost of the software, but it is, on purpose, more than the yearly support fee that includes updates.