Tracer BACnet Setup Tool

Modbus, BACnet and Profibus are some of the widely used protocols in the world of industrial automation. I suppose that the bottom line is: a protocol is the guidelines for how to exchange data over a network. This eventually will take the form as a professionally written specification governing how each protocol is to function. Everything should is very well defined from the baud rates, type of cable as well as the structure of the data are very well defined. You might be asking; What kinds of things are in the specs of Modbus, BACnet or Profibus "rules"? Modbus, BACnet and Profibus are often seen in HVAC equipment, but you will also see it in almost all areas of automation including off shore drilling rigs. Albeit you must make your own decisions in life, my opinion is that the best Profibus is only from Modbus BACnet Profibus Gateways.

We must thoroughly understand the difference between a gateway and a router. A "gateway" is like a United Nations translator that can speak two protocols. "Routers" are simply devices that connect multIPle networks together. These networks may, the same or different. If you need to transmit data over networks are of different types, actual data etc. of the message will most likely get changed. A gateway is needed. A gateway opens the data-package, interprets the raw data, repackages it, then sends it over a new protocol. We may have a

need to take BACnet to Modbus, this aint your mama's RS422 to Ethernet or 422 to 232 converter, and I've already talked about how easy it is getting Modbus RTU to TCP. (This may also be a good time for a Industrial Gateway Server). It takes much more time and energy to do a extraction/repackaging than to simply store and forward a message so gateways are of a more complicated design. Essentially, most serial protocols likegateway serial can translate to an Ethernet base like Ethernet/TCPIP easily. A simple serial protocol converter is needed. By now you should have a clearer understanding the difference between a Modbus Ethernet converter and others devices like a Modbus TCP converter and when to use a simple Black Box converter or a reliable Industrial Gateway. The real secret to getting your data to translate easily really doesn't have to do with the protocol as it does with timing! Although things like baud rates are covered by the rules of the protocol, it really has to do when data is asked for and when it is given. Now add the timing matter of "Protocol 1" with timing matter of "Protocol 2" and you have an added layer of intracity that you don't get with a plain rs485 rs422 converter. It's like to a complicated relay race, have the picture yet? Now picture that several points of data is requested from management through a SCADA Master over BACnet MS TP to BACnet IP exactly how will you get that data without the use of an industrial protocol converters to achieve the timing of the request but also how and where to request the data and the actual data itself! Also, if you are trying to bridge over to many networks, you most likely won't get your data. Don't loose focus, when implementing a rs485 rs422 converter that these devices work on serial protocols, not Ethernet. Things usually get a wee-bit more harsh when dealing with Modbus TCP Ethernet to Profibus. Serious timing issues have to be dealt with. Understand that on your home computer, anything that you see, a request for that piece of information had to happen first. The same is the case concerning any industrial protocol; a request must be made data before is presented. I suppose you can undoubtedly value why you should have a industrial protocol conversion of some type. This data must be handled correctly. It's a seems like a jumble when all of this communication is vaulting across a single network. Add the complexity of various protocols identical to Modbus TCP/IP to BACnet MS/TP and deliberation how it ever works will ensue. It is a good idea to get everything working on the lower levels first. This would be like the basic serial devices. Then check your higher function network like Ethernet/IP before moving on. Now you can introduce the Modbus over TCP gateway or whatever device you have figure out, between the two networks. Then, test some simple communications between the two networks first before moving on to something more complex. It is also a very good idea to test all of the wiring, and terminations, loop-back devices and any termination resistors that you may need on the line for impedance purposes before adding a Profibus to Modbus converter . When implementing with a Modbus over TCP gateway , make sure that you test the network before going somewhere like on off-shore rig! That could be disastrous! It's apparent that I need to gain much knowledge about things concerning Modbus, BACnet and Profibus since they seem to be the most common in the industry. Because a network that isn't fully operational is no good to us, I really want to not only get my network running dependably. The tricky thing about industrial networking is that it may look like it will work on paper. But that isn't the way things work out in the field, get some experts help you out. Find

an expert for your protocol on the web, they will have much more detailed information concerning Modbus, BACnet or Profibus products. Including configuration of the network.