Industrial Data Xchange (IDX) is a South African based IT industrial company with a global focus specialising in the provision of data communication solutions. On this blog, IDX experts comment on industrial communication protocols, trends, and tips as well as what is on the go in the labs at IDX.
PROFIBUS wiring error / B-line short
PROFIBUS wiring error / B-line short
IDX attended a PROFIBUS call out for a gold mine situated in Welkom.
The client reported issues as
“loss of communication and network trips”.
Using the PROCENTEC Mercury Pro
Kit (A complete diagnostics tool for troubleshooting PROFIBUS and Industrial
Ethernet Networks) we were able to identify the underlying issue as a short
between the B-core (red wire) and the PROFIBUS cable shield.
The short in the PROFIBUS cable
meant that the differential signal was significantly lower in amplitude and
therefore more susceptible to earthing faults and EMI injections on the bus.
PROFIBUS makes use of a balanced
signal. This means that the signal transmitted on the A and B channels have
similar voltage levels, however, they have opposite polarities. The
differential signal is calculated as B – ( – A).
When a short occurs on the
PROFIBUS cable between either of these cores and the PROFIBUS cable shield, the
shorted core will produce a flat line and the resultant differential signal
will effectively be halved.
This balanced communication
method, also helps to combat any noise that may be picked up on the network.
The assumption is that any interference injected on the bus will be picked up
on both the A and B channel which, when combined, will result in a clean
was still running on a single core, the interference injected onto the network
when certain machines or drives were started, was enough to cause communication
issues and intermittent network trips.
An oscilloscope that is able to
display the individual signals of each of the cores is necessary to effectively
identify a “short to shield”. Both the Osiris software (Mercury Pro Kit) and
the ProfiTrace software (PROFIBUS Troubleshooting Tool Kit) have this
functionality built in.
By enabling the terminating
resistors at certain points on the segment, we could pinpoint the exact
location of the fault and replace the faulty cable.
After limited down-time for the
repair work to take place, we had the network up and running. Oscilloscope
measurements taken after the fault had been rectified confirmed a healthy
PROFIBUS signal on both A & B channels and in turn, a much more robust
No network trips have since been
Maintaining your existing
connections, in this case maintaining a healthy PROFIBUS network, is the
responsibility of the on-site technical team.
As with anything, the necessary
knowledge and the right tools for the job are required to ensure that your
production is not affected.
Simply IDX it! If you’re looking
for certified industrial communications protocol training, if you want to
become a certified PROFIBUS installer and work your way up to a certified PROFIBUS engineer, if you’re looking for troubleshooting kits or permanent
monitoring for your network, contact us and we’ll provide a solution. Feel free to contact the IDX team if you would like to find out more detail on any of the topics mentioned above: email@example.com +27 11 548 9960
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