AB Intelligent MCC Centerline support with RSlogix5000

RRoc

Member
Join Date
Jan 2017
Location
California
Posts
45
This is my first project dealing with an intelligent AB MCC, Centerline Product Line. Has anyone used RSLogix 5000 to get data on equipment inside the Centerline MCC. We can't use IntelliCenter because comms will be bog down using a radio.

My reading have found one way is the DeviceNet Tag Generator to develop all my controller tags for each equipment in the MCC. Supposedly a CD is provided with the custom ordered MCC which will do this for me.

Another way is just find the Starter, Power Monitor, or VFD Drive and add it to your tree to get each equipment I/O since it's on the network, maybe use messaging to get the data.

Another way is use Studio 5000 V30 and add the add on files that come with the CD and your done. The only issue is that the PLC communicating with this MCC is a 1769-L35E, which can only take V20 or lower.

For those that have used RSLogix 5000 using a L35E controller or similar what worked best for you to get Power Monitor Data, Starter Data, or VFD Data with RSLogix 5000 V20.
 
The CD is only blueprints and other stuff. Not for configuration.
With your actual hardware and assuming that MCC is with DeviceNet, you will need an 1769-SDN scanner and RSNetworx for DeviceNet software. VDF and other drives can communicate data with their own native I/O configuration in DeviceNet. In that I/O you will have the basic data to operate (start, stop, clear faults, running, feedback, reference). Power Monitor in DeviceNet need to use with explicit messages from PLC. First you have to configure your Network in RSNetworx, then download parameters to the devices and to the scanner. Then use DeviceNet Tag Generator to populate tags in the Logix5000 project. And then, associate the DeviceNet created tags with your own tags.
 
Recently completed a AB Intellicenter project using v20 L43 processor. All of the OL in each bucket were E300's with Ethernet. Are all your OL's DeviceNet? E3's?
For our project the MCC utilized Stratix 5700 switches which went to my processor, and each bucket was added into the IO tree. From there you could poll the data via RSLinx. I use RSLinx Gateway, which has OPC, but it also allows to tunnel through ENBT's and Stratix Switches, and you could map data that way.
I used the CPLX processor as a tag aggregator, and communicate via OPC.
 
@dburnum I'm most likely going to be in your shoes. E300 starters with Stratix Switch using RSLinx Gateway.

Did need the CD with that was built for your MCC to do any preprogramming ahead of time? I want to make my HMI screens and programs ahead of the game to prepare for HMI and PLC startup.
 
While the CD had some information that was useful, such as firmware revisions of the E300s and specific equipment for each bucket, I ended up creating an entirely new program, that was for what we needed. Just make sure you know exactly what base sensors you will be using. as well as what control model and firmware.
If I had to do it over, I would have spec'd to have the full Stratic 5700 switches. Typical Intellicenters with out being specified are shipped with a "Lite" firmware 5700 that doesn't support the 1:1 NAT, and I sure could have used that.
Our DCS system is Siemens PCS7, so it took me a lot of extra work to integrate the Intellicenter properly into our HMIs.
The actual configuration ang programming within the PLC was fairly straight-forward.
On a final not, Ive been having some issues with my E300s on firmware 5.83 having a "Non Volitile System" memory fault when maintenance has locked themn out. AB Tech support said it was a known issue and to upgrade to 5.86. Depending on what you get shipped, it might be worth your while to make sure they are to at least 5.86.
 
Update

@dburnum

I just got the CD.

-Each pump has a SMC-Flex Starter (ethernet cable to stratix switch).
-Power Monitor 5000 is also in a bucket. (ethernet cable to Stratix switch).
-MCC section has a Stratix 5700 Ethernet Switch. I could not confirm software version.

Did you add the Individually E300 to your I/O tree or do you have to add Centerline MCC to your I/O tree? I'm thinking I add each device as a stand alone.
 
Did you get the Intellicenter software package with it? That now comes with a feature called Integration Assistant. You load the software onto the same PC as 5000, it recognizes this and asks you if you want to upload the MCC to a project, you give it the project name, select a few options on naming conventions and such, and it loads the whole shebang into your project for you, tags, AOPs, EDS files, everything. Takes 10 minutes, tops. That alone is worth the cost of the software even if you never use the other features.
 
Intellicenter Software was not included it's not a free program. I believe the files were included, but useless w/o program.
 
We have the Intellicenter software, but rarely use it. When the MCC is built you should have been sent a cd with a Logix program on it (ACD). It may not have your specific processor, but the IO tree will match what will be shipped. Just change the project to your appropriate processor, and check the IP addresses assigned if you need to change them.
 
The data CD did not have any .ACD file in it. My intelligent MCC only has 3 soft starts and a Power Monitor. So i just manually added it to my I/O tree and match all the revisions. I also downloaded the AOP from the website, which by the way are under different names. Tech Support was able to help me out.

My company did not buy Intellicenter so we can't use it. I would have to install the client version use integration assistant to get all my tags only for 3 soft starts and a Power Monitor and return the software back. It's just easier if I manually add them match properties and be done with it.

For MCC that has have alot more buckets intellicenter would be the way to go.
 
That ultimately was my route as well. As. Recall my MCC had 4 sections, with mostly ATL starters, and one powerflex 525. I was looking at my ACD that was shipped with it the other day and saw that the PowerFlex drive wasn't in the IO tree.
The E300s are pretty powerful, though and able to spit out a lot more information than I needed.
The bulk of my project was integrating it into our Siemens PCS7 system. The AB side of it was actually quite easy.
I think the integration assistant would be really helpful if dealing with multiple sections on a large project, as well.
 

Similar Topics

I just graduated as a mechanical engineering student, and started this new job a controls specialist with a company in my area. My coworker has me...
Replies
13
Views
906
MELSEQ "intelligent modules" configuration, programmatically resetting the CPU Hello. This is for the Mitsubishi experts, and thanks in advance...
Replies
5
Views
1,016
Haven't done much with soft starts, more-so VFDs' in my time. Looking at replacing 3 x 37KW (415 V 50 Hz) star-delta starters with soft starters...
Replies
11
Views
2,824
We have an old punch press machine. Many years ago (probably around 1990) a machine builder called Steelcase Inc (currently not in machinebuilder...
Replies
4
Views
1,525
Hi, I have a situation at my plant, where I need to interface my existing PLC with some field devices Via Modbus Interface. I can not change the...
Replies
22
Views
5,093
Back
Top Bottom