The Bus Coupler - Aventics DeviceNet VS LP04 Instrucciones De Servicio

18 AVENTICS | DeviceNet | R402000617–BDL–001–AC

The bus coupler

Fig. 1: Bus coupler elements and switch locations
1 Data plug
2 Rotary switch, tens
3 Power supply plug
beginning. The CAN controller hardware only enables the device with
the lowest identifier to complete its transfer. All other devices switch to
receiving mode during the transfer. Thus the identifier determines the
priority of a message on the bus.
A transmitter sends its message to all CAN nodes, which then decide
themselves if they will process the message. A maximum of 8 data
bytes can be transferred in one telegram due to CAN guidelines. It is
characteristic for CAN that only the layers 1 and 2 of the ISO/OSI model,
and thus the physical transfer (level, telegram structure, timing, error
recognition and synchronization of bus access) are specified by ISO
standards 11519 and 11898. Layer 7, i.e. the significance of the data
byte as user or system data and the allocation of the identifier is
determined by manufacturer-specific profiles (CANopen, Device Net,
SeleCAN, SDS, layer 2...). These different protocols are not compatible
with each other.
4 The bus coupler
The bus coupler can be operated on a programmable logic controller
(PLC) using the DeviceNet fieldbus protocol.
A maximum of 32 valve solenoids (16 valves) can be connected per bus
coupler.
1 2
4 Rotary switch, units
5 DIP-Switch, Default position:
3 4 5
1 = CLOSE
2-6 = OPEN