Field Buses


[ASI] [ARCNET] [BitBus] [BACnet] [CAN Bus] [ControlNet] [Data Highway] [DeviceNet] [EIB]
[FOUNDATION] [Industrial Ethernet] [InterBus] [LonWorks] [M-Bus] [ModBus] [Optomux] [PAMUX]
[P-Net] [ProfiBus] [SafteyBus] [SDS] [WorldFIP]
[Home]


Industrial Buses with more data are listed on their own individual pages, so the navigation links above may point to a different web page.
Industrial "Field Buses" are sub-divided into categories depending on the capabilities they offer.
Control Buses: such as; High Speed Ethernet (HSE) and ControlNet are the most complex, followed by the,
Field Buses: Foundation Fieldbus and Profibus, than,
Device Buses: DeviceNet, Profibus DP, SDS and Interbus-S, and then,
Sensor Buses: CAN, ASI, Seriplex and LonWorks.

AnyBus Description

AnyBus: is a range of products to implement industrial network connectivity, AnyBus is not a bus in its self. The products are produced as embedded cards or modules, network modules, or PCI based computer boards. The AnyBus range of products will support one or more of the following interface protocols: Profibus, DeviceNet, Modbus, Ethernet, CC-Link, ControlNet, CANopen, Interbus, FIPIO, Fieldbus Foundation, LonWorks, AS-Interface and Bluetooth Many of these listed on this page].
These are my notes on the topic listed for reference.


AS Interface (ASI) Description

ASI: Actuator Sensor Interface. Used to network sensors and actuators. ASi is a two wire interface; Power and Data. Based around ProfiSafe [developed from Profibus DP].ASI bus was developed by Siemens Automation. This is a Unshielded 2-wire [Yellow cable], Unterminated, Ungrounded Sensor Bus. The Topology may be either Bus, Ring, Tree, or Star at up to 100 meters.
Power is provided by a 24V floating DC supply, which can supply at least 8 A over the network.
The AS-Interface is an open standard based on IEC 62026-2 and EN 50295. AS-Interface organization.


ARCNET Description

Attached Resource Computer NETwork [ARCNET] uses a token-passing protocol, with packet lengths of from 0 to 507 bytes.
The data rate is defined as 2.5 Mbps [10Mbps max], but any speed is allowed as long as the standard is adhered to.
ARCNET uses CRC-16. Depending on the topology the following cables may be used:
Coax; RG-62/u, RG-59/u[BNC], or #24 or #22 AWG solid copper twisted-pair cable [RJ-11], or fiber optic cable [SMA or ST].
No Media Interface Connectors [MIC] are specified, but a DB9 and RJ45 [with pin outs] are provided as examples.
ARCNET is also used with [DC or AC coupled] TIA-485.
In fact an entire section just covers the RS485 electrical characteristics.

Local Area Network: Token Bus, withdrawn from ANSI by request in 2007.
ATA 878.1-1999, now available only from the ARCNET Trade Association
RG62 cable drawing, used when a 93 ohm coax cable is used.

RG62 Construction
Pin
DB-9
RJ-45
#
9 Contacts8 Contacts6 Contacts4 Contacts
1Shield---
2---Line-
3B/B'-Line-Line+
4-Line-Line+-
5Common GroundLine+--
6+5 volts---
7----
8A/A'---
9----

{Industrial Field Bus Index}


BACnet Description

BACnet, A Data Communication Protocol for Building Automation and Control Networks. BACnet and is an ISO/ANSI/ASHRAE 135-1995 standard. Like the LonWorks protocol, it has many physical/data-link layers including RS-485, Ethernet, ARCNET, RS-232, IP, and LonTalk. ASHRAE: American Society of Heating, Refrigerating and Air-Conditioning Engineers

BACnet.org, and BACnet Manufacturers Association (BMA).

{Field Bus Index}


Bit-Bus Description

Bitbus Operates up to 62,5kbps, 375kbps or 1,5Mbps over a differential twisted pair 120 ohm cable, using theRS485 interface [9-pin D sub]. Used mainly for communication between programmable logic controllers (PLCs) and the main controller in manufacturing applications.

Tutorials / Data {bitbus.org}

{Industrial Field Bus Index}


CAN Bus Description

The Controller Area Network (CAN) specification defines the Data Link Layer, ISO 11898 defines the Physical Layer. The CAN interface is an asynchronous transmission scheme controlled by start and stop bits at the beginning and end of each character. This interface is used, employing serial binary interchange. Information is passed from transmitters to receivers in a data frame. The data frame is composed of an Arbitration field, Control field, Data field, CRC field, ACK field. The frame begins with a 'Start of frame', and ends with an 'End of frame' space. The data field may be from 0 to 8 bytes.
For additional information refer to: CAN Specification; Version 2.0, or ISO 11898/11519
CANbus description and specifications for CAN bus is listed on the CANbus Interface Description page.






ControlNet Description

Developed by Allen Bradley. Uses RG6, around 250 meter @ 5Mbytes over dual redundant BNC connections.
ControlNet is used for Time/Mission Critical applications. Looks to be Ethernet based.

Over-all Description {Synergetic}

{Industrial Field Bus Index}


DeviceNet Description

CENELEC standard - EN50325

DeviceNet identifies the physical layer and is based on the CanBus protocol but does not use the same physical layer interface as ISO 11898.
DeviceNet provides optical isolation for additional protection and does not use 9-pin subD connectors.
DeviceNet only supports three baud rates: 125, 250 and 500 Kbaud ( @ 500 meters) with up to 64 devices on the (differential) bus.
In addition the cable carries 24 volts which powers the devices.

DeviceNet description

{Industrial Field Bus Index}


European Installation Bus [EIB] Description

The EIB bus transmits data up to 9600bit/sec over RS-485, and is used in building and home automation.
Additional physical layers include Powerline, RF and infrared.






FOUNDATION Description

Uses IEC/ISA-S50.02-1992 as the standard, as does Profibus.
The physical layer (PHY) for device control is H1 which runs at 31.25kbps on a single twisted pair wire that can be run up to 1900 Meters, or HSE [High Speed Ethernet] which runs at 100 Mbps over standard Ethernet physical layers.
FOUNDATION Fieldbus provides up to 32 devices on a H1 segment running at 31.25 kps (differential). H1 is a IEC 61158 standard.

FOUNDATION Info {Fieldbus Inc.}

{Back to Industrial Field Bus Index}


Industrial Ethernet Description

Industrial Ethernet and the "conventional" Ethernet both share the same physical and MAC levels, but use different protocols.
Also check High Speed Ethernet (HSE)
Refer to the Ethernet interface page for data and specifications relating to Ethernet.
Connector manufacturers are listed on either the Ethernet page or the Industrial Ethernet Connectors page.

{Back to Industrial Field Bus Index}


InterBus Description

Developed by Phoenix Contact; uses the following standards:DIN 19258, EN 50.254 and EIA-485 for the electrical interface.
The following page provides a description of the InterBus interface.


Local Area Network: Token Bus Description

See ARCNET which is the common name for the interface.
However the specification is titled Local Area Network: Token Bus.


LonWorks Description

Local Operating Network [LON]Works uses ANSI/EIA 709.1-A-1999 as the Protocol Specification, and in some cases RS-485 as the electrical specification.
LonWorks uses LonTalk Protocol over Twisted pair, Power line (powered or un-powered), Radio frequency, Coaxial cabling, or Fiber optics.
Speeds per interface include:
Transformer Coupled at 78 kbps to 1400 meters
Transformer Coupled at 1.25 Mbps to 130 meters
Free Topology at 78 Kbps to 500 meters
Power Line at 10 kbps to 6000 meters
Radio at 15K, Line of sight [400-470 MHz and 900 MHz].

{Back to Industrial Field Bus Index}


M-Bus Description

M-Bus, Meter Bus, Used for remote reading of heat-meters and various sensors and actuators.

{Field Bus Index}


ModBus Description

Developed by MODICON. ModBus Protocol is a messaging structure, and does not define a physical layer.
Normally RS232, RS422, or RS485 are used as the physical layer. EIA or TIA may be substituted for RS.

External sites: Standards / Info {modbus.org}, Protocol Info {automatas.org}

{Industrial Field Bus Index}


Optomux Description

Optomux I/O units communicate with the host computer over an RS-422/485 serial communications link. Up to 256 individual units can be placed on a single serial data link for a total of 4,096 digital and analog I/O. The cable consists of two differential lines and a ground [5-wire]. Optomux supports 8 baud rates of 300, 600, 1,200, 2,400, 4,800, 9,600, 19.2K, and 38.4K baud. Some boards [Brain Boards] also provide Ethernet ports for use on standard 10/100 Mbps Ethernet networks. Wiring is normally connected via screw terminals, but the host may use a 9-pin D connector [pin #]. Of the five wires: blue is ground [3], TH+ is yellow [8], TH- is black [9], FH+ is red [4], FH- is green [5], all other pins on the connector are unused. two additional differential links go between Optomux units. Refer to Opto22 [a manufacturer of controllers] for additional data.

{Industrial Field Bus Index}


PAMUX Description

The PArallel MUltipleXed [PAMUX] Parallel bus was developed by Opto22.
The PAMUX interface supports up to 32 stations containing up to 512 I/O points.
PAMUX is an I/O board standard, and not just a cabling interface.
Refer to Opto22 for additional information. Refer to this site for a Pin-Out {UAB "BBD SOFT"}

{Industrial Field Bus Index}


P-Net Description

EN 50170 Vol. 1, and IEC 61158 Type 4: P-Net was developed by PROCES-DATA A/S.
P-Net is based EIA485, providing a 1200m cable length, but P-Net only allows one data rate 76,800bps.
Data is sent as an asynchronous transmission, the Bit Encoding used is: Non Return to Zero (NRZ) encoding. The P-Net field bus was developed in 1984.

Tutorials / Data {IPUO - the International P-NET User Organization}

{Industrial Field Bus Index}


ProfiBus Description

Process Field Bus: [~ Pro-Fi-Bus] is based on the EIA-485 bus and EN-50170, using a non-powered 2-wire bus. The connection is half-duplex over a shielded, twisted-pair cable.
Process Field bus will use either a 9 pin D (DIN 19245) or 12mm connector (EC50170). Data rates may be from 9600 to 12M baud, with message lengths of 244 bytes. At 12 Mbps the maximum cable distance is 100 meters.
A maximum distance of 1200 meters may be achieved using a maximum data rate of 94kps. Up to 126 nodes may be connected in up two 5 segments, which are separated by repeaters.
Each segment may contain up to 32 nodes which are laid out in a single node. Each node has one master and slave devices.
I also see it uses IEC/ISA-S50.02-1992 as the standard, as does Foundation Fieldbus. Which provides up to 32 devices on a segment running at 31.25 kps (differential).

PROFIBUS International

{Industrial Field Bus Index}


SafetyBus Description

SafetyBus is based on the CanBus [with added redundancy] as a multi-master system with a linear bus topology and uses an open protocol.
SafetyBus is event driven, with messages being sent only when an event changes.


Smart Distributed System (SDS)

SDS; Smart Distributed System defines the physical layer and application layer (based on CANbus) for an event driven interface.
SDS was introduced in 1995 and is used for intelligent sensors and actuators, operating over a single 4-wire cable [2-Power, 2-Data], interfacing up to 64 nodes with a maximum of 126 addresses.
The communication bus impedance is 120 ohms +/- 10 percent.
The SDS baud rate is 125, 250, 500 and 1000kBaud; Definition of baud.
A data rate of 125kBaud allows for a maximum cable length of 1500 feet. 64 nodes may reside on the bus, while a repeater will permit up to 126 nodes.
SDS uses DSTP (Dual Shielded Twisted Pair) interconnections.

Smart Distributed System only includes the Application, Data Link and Physical layers of the ISO/OSI Reference Model.

Application Layer Protocol Specification (Rev 2.0)
Physical Layer Specification (Rev 2.0), 1999, written by Honeywell.

Simplified Interconnect of a Smart Sensor Devices in a system
Smart Sensor Devices in a Smart Distributed System

{Industrial Field Bus Index}


WorldFIP Description

WorldFIP "Flux Information Processbus" [European Standard EN50170].
The Physical Layer: is compliant to IEC 1158-2 for all speeds [up to 2.5Mbit/sec (typically 1Mbit/sec)] on twisted pair and fiber optic.
The Physical Layer, Data Link Layer, and Application Layer are specified.





Data Highway Description

The Description of the Data Highway Field Bus is now listed on the Data Highway Field Bus page.

{Industrial Field Bus Index}


Larry's Web Page
Home

Electronic Parts and Equipment Distributors Electronic Component Manufacturers OEM Electronic Equipment Manufacturers EDA Software Producers CAD/CAE Software Engineering Standards, EE Publications Interface/Embedded Computer Bus Electronic Engineering Design Data Engineering Reference Information.
DistributorsComponents Equipment Software Standards Buses Design Reference

Modified 6/13/15
© 1998 - 2016 All rights reserved Larry Davis