Showing 0 products
Frequently Asked Questions
Why is a field bus not just wiring?
It is a transmission line with rules.
Topology, termination and length all constrain it.
Ordinary wiring practice breaks all three.
The result is intermittent, not obvious, failure.
That is why it is blamed on software.
Treat it as a designed circuit.
What is wrong with star or spur wiring?
It causes reflections on the bus.
Reflections corrupt communication intermittently.
Daisy chain device to device is the required topology.
Spurs look harmless and install faster.
They are a common cause of unexplained faults.
Correcting it later means rewiring.
Where do termination resistors go?
At each physical end of a segment, and nowhere else.
Missing terminators corrupt communication.
Extra terminators do exactly the same.
Both produce identical symptoms.
Count them physically during commissioning.
Record where they are fitted.
What limits a segment?
Length and device count together.
Both are specified by the protocol.
A repeater is required beyond them.
Exceeding limits works until it does not.
Marginal segments fail as devices are added.
Design the topology before pulling cable.
Does cable type really matter?
Considerably, and substitution is common.
Screened twisted pair of specified impedance is required.
General multicore is not equivalent.
The screen must be earthed at one point only.
Earthing both ends injects noise into the circuit.
Specify the cable in the tender.
How do physical layer faults present?
Intermittently, and misleadingly.
Devices drop off and come back.
Values go stale without alarming.
Controllers and software get blamed first.
Days of diagnosis follow.
Check the physical layer early, not last.
When is surge protection justified?
Wherever the bus leaves a building.
External runs pick up induced surges.
A single event can destroy many devices.
Protection is cheap against that.
It needs a proper earth to work.
Fit it at the building boundary.