Michael Lloyd

That's good news. Cell modems are not the easiest things to set up the first time. Consider adding the DHCP settings at the PLC. That'll make plugging in less of a hassle. A year from now you or someone else might not remember to hard code the IP / Subnet Mask in the laptop or pc. Message. Definitely use the Message block. I'm home for Thanksgiving and I don't have my laptop here otherwise I would send you an example of what you are trying to do. One exception though,  I was messaging between two CLX machines (Control Logix) not the Micro. It's supposed to work the same. If you initiate the message from the CLX machine then once you get one working the rest should work. One way to control the polling is to use a Periodic Task and set it to once a <insert time here>. Don't poll it too fast or it won't work. Try 1 second (1000ms) first. Inside of that create your 13 messages, one for each tank. Ethernet is fast. You should be able to just use 13 separate rungs, each with its own message block, for no more data than you're trying to get. I have about a half dozen different messages traveling across a couple hundred miles of pipeline and I run them. It's important to get the IP address structure right in the Message block. xxx.xxx.xxx.xxx,a,b,c where the x's are the IP address octets for the target and the rest are commands. Caveat- the example may be completely out of order.  Here's one more thing to consider. If all of your hair is pulled out and you can't get the message to work in the CLX, try switching to writing from each Micro back to the CLX with a message in the micro. I don't like what they are doing here. It's too kludgy... but it's from AB: https://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm012_-en-p.pdf This is way better. I didn't use his timer. I used a Periodic Task: http://bryceautomation.com/index.php/2017/06/03/controllogix-messaging/

Ya gotta eat an elephant one bite at a time. the en2t port configuration settings ? The card is 192.168.1.55 ... ok... what's the subnet mask? the modem static ip is 63.40.219.224 <--- So the EN2T is speaking English and you've basically set the modem, that I'm assuming is supposed to be connected to the PLC, to speak French... they've got to be on the same subnet...  portstart 44818 portstop 44818 host ip 192.168.1.50 port stop 44818 ----------------------- This is what I would do (and have done). Set a static IP, Subnet Mask, and Default router in the EN2T In your example above: IP: 192.168.1.55; Subnet mask: 255.255.255.0; Default Router: 1922.168.1.1 Now set the Modem up to be a DHCP server. IP: 192.168.1.10; Subnet mask: 255.255.255.0; Default Router: 1922.168.1.1. Now when you plug the laptop into the switch the modem will put our laptop on the LAN that you are building. You are using a switch right? The modem isn't plugged directly into the EN2T correct? Each cell modem will need to be (doesn't actually need to be, it just lets you plug your laptop into the switch and not have to worry about hard coding an IP address / subnet mask) a DHCP server. IP: 192.168.1.xx; Subnet mask: 255.255.255.0; Default Router: 1922.168.1.1 You'll increment the last octet (xx) for each tank site, so the last octet of the IP will be 11, 12, 13...23.  44818 is the right port but what you wrote doesn't look like port forwarding to me. Granted it's been about 5 years since I've set a modem up and you may not even need port forwarding in this scenario. I'm away from work so I don't have any of my references handy.  The main problem you have is that it appears that you're trying to talk across two different subnets. That never works. Never as in a router can be set up to NAT but that's above my skillset and not relevant to what you're doing here.

Couple of things- (1) How far are your tanks from the main processor? Cell modems come with a monthly cost. Freewave non-licensed radios don't. (2) What are you using to convert the "pressure" value to something meaningful, like feet and inches? Using a pressure transmitter for tank level is "economical" :/  Back to the cell modems, they have to be set up to specifically talk to the port that the AB PLC likes to talk on. I'm going to have to dig a little to find it but I made a Sierra Wireless cell modem setup PDF about 5 years ago. That's going to take a little effort.  I can't help you with the Micro 820's. It would have been cheaper to use Point IO (unless there's more than just a tank level transmitter on each tank. Point IO is dirt cheap though) and the IO would live in the main PLC instead of having to kludge around with 13 tank PLC's plus the main PLC.

The CF card can be used to back the program up so it recovers from a "fault" (not all faults). For instance if loss of power corrupts the program it'll reload it. The downside to that is that every time you change the program you have to dump it back to the card. Every time you dump it back to the card the PLC halts and your "stuff" shuts down. Personally, I think the card slot is best left empty. YMMV 

The port protocol was probably different in the original program as comparted to the program you downloaded. Here are some key points of Ron's post: "This port is generally (and by default) set up for “DF1 Full Duplex” but this same port can also be set up for “DH-485” (Data Highway 485)." "Concerning the 1747-PIC “adapter”. This “adapter” is a physical piece of “hardware”. Basically it’s a gray plastic box with two cables attached. It’s primary use is to convert the RS-232 voltage levels from the back of your programming computer to the higher voltage levels used for the RJ-45 connector on the front of some SLC processors (SLC-500, SLC-5/01, SLC-5/02, and SLC-5/03). The conversion of the voltage levels MUST be done by a piece of hardware. Consider the telephone analogy, there is NO WAY to simply “plug in” a German telephone set (5 volts) to the Italian telephone system (24 volts) and expect it to work properly ... to use a German telephone set in Italy would require a physical “adapter” of some sort to convert from one voltage level to the other. Now to the 1747-PIC “driver”. This “driver” is a “software” program. It’s included as part of the RSLinx package. It’s primary use is to convert the RS-232 “language” from the back of your programming computer to the DH-485 “native language” used by some SLC processors (SLC-500, SLC-5/01, SLC-5/02, and SLC-5/03). Consider the telephone analogy, we cannot simply “speak” German on the Italian telephone system and be understood. To speak German on the Italian telephone system would require a “translator” of some sort to convert from one language to the other and so to nail this down, the 1747-PIC “adapter” is a piece of hardware for the DH-485 system and the 1747-PIC “driver” is a piece of software for the DH-485 system. Sometimes the “Channel 0” DB-9 port on the front of an SLC processor is set up for “DH-485”. when that happens the voltage levels on the DB-9 port do NOT change, specifically the port’s voltage levels stay perfectly compatible with the voltage levels used on your programming computer’s RS-232 (serial) port no problem there and specifically, we do NOT need a 1747-PIC adapter. The same old three-wire null modem cable that we usually use for this port will still work just fine." "This might help decide which driver (the “RS-232/DF1” or the “1747-PIC”) you need to use with NO cable connected to the DB-9 port, watch the LED marked “RS-232” on the front of the processor. If it flashes about once every four seconds, then the DB-9 port is (probably) set for “DH-485” and you’ll (probably) need the “1747-PIC” driver in RSLinx, but if there is NO flashing, then the DB-9 port is (probably) set for “DF1 Full Duplex” and you’ll (probably) need the “RS-232/DF1” driver in RSLinx."

Oohh… that's one of those holy poop on a stick batman errors. See above reference to the comm issue. Ron (as always) has a great explanation for how to determine what you need to do to get back into your PLC. It's probably just a driver selection in RSLinx. The last line of his long post explains how to tell which driver to use ("most of the time"). http://www.plctalk.net/qanda/showthread.php?t=106086

Go straight down to Ron Beaufort's explanation. I made a PDF of the explanation that he gave (seemingly, 15 years ain't that long is it?) long ago and I still refer to it (don't connect to SLC's much anymore).

Did you upload the old program from the SLC so you can review the original parameters? Did you look at the fault table to see what the fault was? You might have been able to reset the fault without downloading a new program. You changed something to cause your problem (captain obvious is on the scene). I'd have backed out when I saw that warning. Admittedly there was this one time, not in band camp, where I didn't so I've been there. Have your tried the "auto config setup" in RSLinx rather than defining the comm parameters?  

When you say plant, what kind of plant? If it's gas processing or oil terminal I can send you some things that might be helpful. If it's making beer the best I can do is ask for free samples   Robotics, etc... I'm out (but interested). Like Joe E. The bulk of my time was on SLC 500, S7-300/400, S5, and then I moved Logix 5000.The first PLC was Direct Logic and TI505. I've also built out a couple of Delta V DCS projects. My preference is the Logix 5000, by orders of magnitude

Oh... like Stuxnet...  https://en.wikipedia.org/wiki/Stuxnet

It sounds like he want's to "use features" of PLC without the use of the PLC software or an HMI. :/

I just found this. It's interesting how many machine programmers there are here. I don't think I can add new laws... maybe this one Law #xxx The Allen Bradley SLC to CLX conversion software is the spawn of Satan. Don't use that thing on your poor customers hardware. Figure out the IO and write the program. but I do have a few stories At least 7 years ago an engineer friend called for some help. His plant, an amine treater, was down and had been down for two weeks. Two different companies came from Salt Lake City, the plant was outside of the Rifle, CO. Like really outside. They couldn't figure out what was wrong. He was $5k down for their cost and whatever the treater being offline cost them in production. I wasn't too busy and I had just come off of a startup so I was ready for some R&R. I told him that I would drive up and take a look and then go to Moab or maybe Yellowstone afterward, and only charge one way mileage and time to get there (plus hotel). I got there as a blizzard was "arriving" and by 4:30am there was 8" of snow on the ground and his foreman let me know that the only access to the plant was by snowmobile so we would have to wait. I visited Moab on that day. The next day was worse due to an additional 6" of snow. Dinosaur NP was pretty cool. The third day was better but it was 8 miles of 4WD hell to get in. After a couple of hours of almost not making it we arrived and the foreman showed me the PLC panel (SLC 500), I opened the door, plugged in, turned the key to run , clicked run and the alarm horns came on. Someone had put the key in program mode. I stuck around for a second day and added some conveniences for them. They thought I was a genius lol An electrician was adding a cooling system to a panel a few years ago and the station tripped off. They called me but I couldn't remote in. I drove two hours (the electricians were long gone) and when I got there I found a 4" diameter hole in the side of the panel, not covered btw. They never considered that there was a Control Logix  PLC on the other side. In that case he just sawed off the key even with the face of the PLC and it somehow turned to program mode.  Same electrician... we were installing an HMI in a panel for the company that bought our site (We used a remote scada system to operate and our HMI was in the control building that was going away). I watched the same electrician drill a pilot hole with the door open (good thing) but when I came back he had a Sawzall blade pushed through the hole and was sawing away at it with the door closed. I walked over, expecting (hoping actually) the blade to be short, and suggested that he try a new blade. He pulled the new 6" blade that he had just switched to out of the saw cut  and announced that it was a new blade... well S... it was 6pm on Friday and no prayer of finding another whatever he had cut into... opened the panel and it was a Din rail mounted 24VDC power supply. He had made it 1/2 way through it. His only comment? I thought I heard something pop. We had a spare in one of the other control panels in the building.

Lol, I am working in NM and home is TX. NM adopted the CO franchises since they can't afford one of their own (but we do have a Space Port that we can't use). TX... The Stros almost pulled it off. Texans and Cowboys... eh... <--very unpopular thing to say :) I have mixed feelings about the IP address change cost. When I was an integrator I tried to train the customers techs to do things like change IP addresses for themselves. I didn't charge for my mistakes either. Some don't run their business that way. It can be a tough business. That said, he should have left the customer with all of the programs. They bought them. With any luck 0 will work. I think max is 128 (might be 256). I never needed to go that high but I know of instances where someone would start at 10 and go up ie not use the default. !00% agree on your music choices lol I'd load it up with Eric Church No worries. Been there. I learned to mimic Steve Erkle (did I do that?) over the years.  

That is the Crimson program. A Micrologix program ends in RSS. I can't tell where you are located but if you have an AB rep maybe you can talk them into doing you a favor and connecting to the machine to verify the channel configuration. Or posts it here and we'll look it up. There are two channels. Channel 0 is the DH485 port, default appears to be 1 (I think this is what the Crimson is tied to) and Channel 1 is the DH+ port, default appears to be 1. Correct! The word I was looking for was Node Address. It's in the Channel Configuration --> Chan. 1 - System or Chan. 0 - System tab for the PLC and Drop Number in the Crimson software. They need to match. The rest of this is just FYI "stuff". It looks like there are two Micrologix "devices" in this program. One on the RS-485 port and one on the RS-232 port. I didn't see a wire for the RS-232 port in your photos. I don't think this is particularly important, just an observation.  The Network port has two Protocols, also just an observation. Whoever built the HMI did a nice job (except for maybe the music choices :) ) For your purposes: Top left / Bottom Left Navigation Pane: The tabs in the bottom left change what's in the top left. Bottom right is navigation for the Resource Pane on the right. Communication is what your interested in (I think you know that). Data Tags: is just for the Micrologix data tag setup Display Pages: is what it sounds like, all of the displays Programs: I've never had the need to use the Programs tab but I like what the programmer did Webserver: I'm assuming you have a control room that remotes into the panel. It's handy and it's turned on Data Logger: Just what it sounds like. Not used Security: Just what it sounds like

It's connected to the RS485 port on the HMI and the PLC has a DF1 port. The Red Lion has a built in protocol converter so that explains that. What wasn't clear is why changing the HMI IP address hosed up the connection. Short version - it didn't. When you copied the program from the other HMI you changed the DF1 config. I'm not where I can look but each ML1500 will likely have a distinctive ?? PLC topic, address, node, whatever it's called. Lets say your original panel that worked is Node of 1 and the second panel that you copied panel 1 to is set up with a Node of 2. The protocol converter in the Red Lion is "pointed at" a specific "node" on the RS485 port. That is something you can change on the Crimson end. You just need to know what the node is. If you post the program for the non-working PLC someone here can figure that out pretty quickly and you can edit the HMI and get back online   

Nope. The 3rd octet of the IP address in the PLC would also need to be changed by logging into the PLC with the RSLogix 500 software. HMI and PLC are separate. Ie I can use any compatible HMI with the PLC and I can use any compatible PLC with the HMI. They have to be on the same subnet if the comm link is ethernet. If the comm link is serial (DH+, etc) then my post is null and void

Did you change the IP address in the Micrologix PLC too? The HMI will have it's IP address and the PLC has it's IP address. I'll type it but I'm sure you know this- No duplicate IP addresses.

See attached R8-41335.pdf

Documentation is almost non-existent. Do you know what the IO points are? It contains a lot of indirects. In other words, without program docs this is going to be very hard to follow

Is the subnet mask the same in both?

There was a post a few months ago, by a moderator, where he used Excel to do the same thing. I think it goes out to 5th order but I don’t have access to a computer right now (typing this in my phone, more than once :/ )

Ok, then it’s easy, you can’t do that.

I’m not aware of anyway to see the level addressing that I think you want to see. Ie Tag Bool resides in some absolute memory address In the microprocessor and you want to see it.    Even Mel’s reference to Local: for IO isn’t the actual physical level address of the microprocessor IO. It’s just a pointer.    I think that knowing hardware level memory addressing would pose some level of security risk

Ok, then mapping the tag works (same thing as bit packing, just one at a time). Message to an INT, then assign the bits from the INT to the BOOL

Logix 5000 is a tagname based environment. If there aren't any Boolean tags there aren't any Booleans