What do pizza and PROFIBUS have in common with each other? Cheese!
Bandini Cheese is a South African cheese manufacturer supplying their products to numerous pizza restaurants around South Africa. They are always striving to provide the highest quality products and this ethos can been seen in other aspects of their manufacturing process. For them, the up-time of their PROFIBUS network is critical - not only do they have expectant customers, but the very nature of the cheese making process means that batches cannot just sit around while technicians try to troubleshoot the PROFIBUS network.
Realizing this, the engineers and technicians working on the plant attended the certified PROFIBUS Engineers Course at the South African PROFIBUS Competence Centre (PCC). It was here that they heard of new innovative product called COMbricks and they became one of the first companies to implement the COMbricks solution.
Solution to what? The problem is knowing the health of the PROFIBUS network. This can be determined by looking at how many corrupted, repeated, illegal or diagnosic messages are passing through the network and of course by looking at the signal itself. COMbricks can do all of this and report on any errors before they become failures.
Bandini optimized their network by adopting a tree layout verses a linear layout. A PROFIBUS cable connects the PLC in the control room to a COMbricks Scope Repeater Module. 5 more Scope Repeater Modules are used to repeat the signal to 5 new PROFIBUS segments running to different areas of the plant, each of which loop back to a location near the COMbricks. Active terminators are used at the ends of these segments so that if a slave fails or needs to be replaced, the segment is unaffected by reflections caused by an un-powered termination. This layout makes troubleshooting much simpler.
Being able to share the reports that the COMbricks produces with experts at the South African PCC, brings the expert to the site without him having to travel there. Even a screen shot in an email can be a much quicker way of trying to diagnose what the problem is. We can quickly narrow down the problem to the segment connected to slot 7 of the COMbricks - awesome!
Popular posts from this blog
Last week IDX were called to site at a large commercial residence building in Pretoria, South Africa. Where our client was implementing an IoT solution for remote monitoring and control of various HVAC and power systems in the building. The control system the SI chose in this case was a Modbus enabled Industrial Micro PC called the Revolution PI. The client had Modbus sensors connected to boilers, air conditioning systems, ventilation systems and power meters. The Modbus communications between the controller and the sensors were intermittently failing due to various installation and implementation faults: 1. Earthing and Shielding Within any fieldbus communication installation, one of the requirements to ensure uninterrupted operation is to implement adequate grounding and shielding techniques. Effective grounding and Shielding help to prevent electrostatic and electromagnetic pickup, which can lead to failed communications. Some of the shielding and grounding req
In this blog, I will discuss the steps involved in getting the Netbiter to record and display values coming out of the ComAp Generator Panel, so that one can do remote monitoring and control of the generator. The Netbiter Model used in this case is the EC220 and the panel used is the InteliLite AMF 26 P. The steps followed here can be applied to any MODBUS device due to the generic nature of the Netbiter. S tep 1 - Physical Connection Check that the Control Panel has a communication module attached to the back of it. You will need to establish the medium (RS458/RS232) and the protocol spoken (MODBUS RTU/ASCII) - all of this information will come from the user manual of the generator. Finally confirm the communication settings (baud rate, parity, stop bits, etc) - these can sometimes be changed so check what they are on the actual panel. In this case, we have the following settings: MOUBUS RTU over RS232 (you'll need an external converter to convert the RS232 to RS
Time to dust off the cobwebs and do some "legacy" development! In this blog, I'm going to show you how to get to a point where you can start writing Java code on the HMS Anybus Communicator. I find that it doesn't matter what language you code in, the tricky bit is getting to the point where you can simply create and run the time-honoured "Hello World!" program. Using new editors, sorting out dependencies, making physical hardware connections can take up a big chunk of your time. First, some information on the hardware platform: The Anybus brand from HMS contains hundreds of gateways (or protocol converters) that can be used to convert between common industrial communications protocols such as PROFIBUS, MODBUS, Ethernet/IP, ControlNet, DeviceNet, PROFINET, CANOpen, J1939, etc. Check out anybus.com for a full list of protocols supported out of the box. Using these gateways you can for instance read registers from a MODBUS device and make them available