How to make Multiple Fieldbus Networks Communicate
Be sure to visit our knowledge Center – http://www.innovativeidm.com/Resources.aspx
1625 Wallace Drive, Ste. 110
Carrollton, Texas 75006
Hi, I’m Jeff Rogers with Innovative-IDM. One of the biggest challenges facing today’s automation specialists is the way to make multiple fieldbuses communicate with upstream and downstream equipment. It’s a very daunting task that could take a lot of programming knowledge that could probably be covered in several college courses. Today we are going to keep it pretty high level and talk about a few components that could be used should you find yourself having to do this.
The first thing is the type of fieldbus. There are all different kinds of fieldbuses out there. Some are proprietary, some are open-source, meaning anyone could use that type of protocol whenever designing a piece of equipment. So obviously, the ones that are proprietary are going to be harder to make communicate with other pieces of equipment, because the gateway type equipment that can be used are somewhat limited. There’s just not that many of them out there. Other fieldbuses for instance, probably one of the most well-known is Ethernet, be it internet IP, Ethernet EPCIP is very widely used standard that I see getting more and more popular every day. It seems to be becoming the standard if people have a choice. So remember proprietary is going to be a bigger challenge, but there are ways of getting around that. What you have to consider is not only the protocol that you need to make it communicate with other protocols but also the transmission media. You can actually transmit profibus protocol over an Ethernet cord, over a cat 5 cord with RJ45 connectors on it. So you have to remember just because the cord looks the same doesn’t mean that the protocol is going to be the same. So remember those things. Ideally I always tell people if it is a new piece of equipment and you want to make sure it is going to communicate with all your other equipment you really need to get with that OEM and almost demand that they use a network you are familiar with so you don’t have to go through that hassle because it’s not fun, it’s kind of a pain. Ideally use should try to standardize on a type of protocol that you are familiar with that’s flexible, gives you many different options and a lot of manufacturers support, such as Ethernet. I would say that is probably the most common in today’s market. Now if you do find yourself, for instance if you have older equipment in your plant that already has a different protocol on it and you want it to be able to communicate with say your Skada setup, or just for some sort of monitoring device or an add on or anything like that to the machine and those two protocols need to be able to talk to each other, then you could setup what is called a gateway. There are different devices that can be used as a gateway which is just allowing two protocols to communicate with each other.
The three most common gateways are:
- Manufacturers out there that make simple discrete adapter components.
- You plug on piece of equipment in one and another on the other end and it allows the equipment to communicate with each other through an internal circuit board.
- They are limited and can be pricey, the manufacturers of them are pretty proud of them. If you have a lot of components where you need to be able to make a bunch of different components talk to each other that could get sort of pricey.
- PLC or IO system
- They can be programmed for making different types of communication protocols talk to each other. For instance, WAGO has an IO system that is known as fieldbus independent. They have fieldbus couplers that support all of the open protocols that exist in today’s market. For instance, this one right here supports Ethernet. If I wanted to make Ethernet talk to Modbus then I could drop a Modbus card in right here and have those two components talk to each other. For instance, if I had a touchscreen that only communicated via Modbus and I wanted to make it talk to a piece of equipment, say a variable frequency drive that communicated over Ethernet I could use this component as the go between. Often time people use touchscreen HMIs themselves as the gateway. This particular touchscreen has both Modbus capabilities as well as Ethernet built in to it. You could plug one piece of equipment in one port and a different piece of equipment that might be a different protocol into the other port and make them communicate via this device essentially turning it into a gateway. It can get pretty complicated. There is a lot of ins and outs as far as needing to know how to program those things, addressing registers properly with in a program to make all those talk. That’s something we have a lot of experience with because it does come up.
- Networking is extremely important,
- it will only become even more important as time goes on because the top brass at all the plants and manufacturing companies around the world are always going to want better access to information, efficiency data, also remote control and data acquisition capabilities. All of that has to be done through networking all these pieces of equipment together.
If you need any help with that please contact us. We have programming specialists, application specialists that can come out and help you with that. You can also find information located on our website in our knowledge center. Just go to innovativeidm.com and you will find our knowledge center there. It has white papers, for the specific products we support, on how to set them up. After all we are Home of the Legendary Customer Experience.
Tags: board repair, circuit board repair, control panel, customer service, industrial automation, Innovative Automation, innovative-idm, legendary customer service, Parker Hannifin, PLC, PLC Training, Wago, YaskawaYou can comment below, or link to this permanent URL from your own site.