Bromma Spare Part Kits

Profibus Gateway kit no: 1013417

Parts included:
Kit instructions Profibus gateway
1
50 00083 1013417-1

3 2
T-connector M12
CAN terminating
1023560
resistor plug M12
1019449

4
Power cable
open end
70396
5
CANOPEN cable
open end
1016668

Applicable in:
All Bromma spreaders with SCS2 or SCS3 control system and Profibus communication to crane.

Settings:
See pages 2-3 for SCS2 or page 4 for SCS3. Verify that area sizes are properly set.

Remarks:
Note that the Gateway is delivered with the initial setting: Default Mode
The Gateway communicates both with CAN and B-CAN

Kit no: 50 00083 -1- April. 09 rev.01 Bromma Conquip

 Bromma Spare Part Kits

Area check SCS2

Get log view
Used to retrieve the onboard error and event log.

1.Gets next setof logged messages (max 128 messages each

time its’ pressed)
2.Get all messages in log.
3.If checked, auto mode ison. Auto mode triggers theNext
button [1] at an interval of X seconds defined by [4].
4.Interval for reading via auto mode in seconds.
5.Enable filtering.The filtered table is shown if checked.
Filtering can be used to only view certain partsof the log.
6.Opens the Filtering constraint dialog. Select the type of
filtering here.
7.Clears the log table on the PC. The log in the SCS2
remains unaffected.
8.Saves the entire log table in a comma separated textfile.
Can be opened for instance in Wordpad, Excel etc.
9.Cancels current operation.
10.Load button. Loads and displays a saved logfile.

6
4 1 2 5

1494 Info A1 357 ANYBUS_DATA_INPUT_AREA_SIZE 12 2006‐08‐05 10:36:14

1496 Info A1 358 ANYBUS_DATA_OUTPUT_AREA_SIZE 18 2006‐08‐05 10:36:14
2889 Info A1 357 ANYBUS_DATA_INPUT_AREA_SIZE 12 2006‐08‐05 12:24:45
3 2890 Info A1 358 ANYBUS_DATA_OUTPUT_AREA_SIZE 18 2006‐08‐05 12:24:45
2934 Info A1 357 ANYBUS_DATA_INPUT_AREA_SIZE 12 2006‐08‐05 13:32:41
2935 Info A1 358 ANYBUS_DATA_OUTPUT_AREA_SIZE 18 2006‐08‐05 13:32:41
3078 Info A1 357 ANYBUS_DATA_INPUT_AREA_SIZE 12 2006‐08‐05 13:43:03
3079 Info A1 358 ANYBUS_DATA_OUTPUT_AREA_SIZE 18 2006‐08‐05 13:43:03
4222 Info A1 357 ANYBUS_DATA_INPUT_AREA_SIZE 12 2006‐08‐05 16:07:49
4223 Info A1 358 ANYBUS_DATA_OUTPUT_AREA_SIZE 18 2006‐08‐05 16:07:49
4756 Info A1 357 ANYBUS_DATA_INPUT_AREA_SIZE 12 2006‐08‐05 19:05:01
4757 Info A1 358 ANYBUS_DATA_OUTPUT_AREA_SIZE 18 2006‐08‐05 19:05:01

9
8
7 10

Get log view

Bromma Conquip Kit no: 50 00083 -2- April. 09 rev.01

 Bromma Spare Part Kits

Field bus Connections.

Mapping of I/O
By using the AnyBus the crane can utilise the SCS2 as an
OUT integrated slave on the PLC network or an AnyBus card can be
Byte 0-63 used as a Master bus for an internal I/O bus on the Spreader. The
Project principle behind the AnyBus is that the interface card translates a
specific number of different bus protocols to a standardised format on the
outputs
address and data bus of the node. To change between different
buses one can then simply change the type of interface card. For
details regarding configuration of a specific bus, please view the
user manual for that specific card and the electrical documentation
for your specific project.

IN The size of the data exchange area between the SCS2 and the
Anybus card is configurable up to 64 bytes in and 64 bytes out.
Byte 0-63 The configuration is done via HMS standard files. This interface
Project
specific must be configured in the same way for both the Master and the
inputs SCS2 slave for the bus to work correctly. For each project a
document has to be sent to the customer describing the used parts
of the interface. When referring to in/out we view it from the SCS2
side, hence input for the SCS2 is an output from the master in the
crane. Hence the crane PLC and the AnyBus card must have
corresponding addresses and the number of bytes configured for
input/output data have to be the same on both sides of the
communication link i.e. the crane PLC and the SCS2.
Output Segment
In the output segment it is possible to use a number of bytes for diagnostic information in the form codes. The
code sent will be equivalent with the code displayed in the onboard display, hence there will be three levels of this
code INFO, WARNING, ERROR. Apart from the code and the byte for indicating the type of code a counter
will be incremented each time a code is sent. The counter is a 16bit value and therefore will begin from 0 if the
counter overflows. The value of this counter will be sent each time that a new diagnostic message is transmitted.

Spreader diagnostic area

Byte 0
Byte 1
Byte 2-3 (WORD)
Byte 4-5 (WORD)
Byte 6-7 (WORD)
=> Type of error (info, warning, error)
=> Node ID (the number of th e node from which the message originates)
=> Diagnostic code
=> Sub Code for diagnostics
=> Sequential counter value (message number)

System diagnostic area.

This part is named the assert diagnostics and is basically only used to find discrepancies in the SCS2 system.
The objective of it is mainly for Bromma Group’s R&D to identify unforeseen weaknesses in the system. If the
customer wishes to implement/decode this it can help Bromma Group to improve its’ equipment further,
however the customer might find little or no use in this information on their own behalf. The assert part is
configured in the following way.
Byte 8 => Node ID
Byte 9-10 => Row Number (of source code)
Byte 11-16 => Filename (1:st 6 char.)
Byte 17-18 => sequential counter

Kit no: 50 00083 -3- April. 09 rev.01 Bromma Conquip

 Bromma Spare Part Kits

Area check SCS3

How to check area size on SCS3 PLC

Bromma Conquip Kit no: 50 00083 -4- April. 09 rev.01

 Bromma Spare Part Kits

Overview

Termination Switch
Each bus segment in a PROFIBUS network must be terminated properly to ensure
error-free operation. If the module is used as the first or last node in a network
segment, the termination switch shall to be in ON position. Other-wise the switch has
to be in OFF position.

Note:If an external termination connector is used, the switch must be in OFF position.

Node Address Switches

These rotary switches can be used to set the node address of the
module in the range 1... 99. The switches are read once during start-
up, i.e. if the setting is changed, a reset is required in order for the
change to have effect.

Example:
When the left switch is set to 4 and the right one is set to 2, the final
value will be 42.

Status Indicators

Kit no: 50 00083 -5- April. 09 rev.01 Bromma Conquip

 Bromma Spare Part Kits

Connectors
The module supports three different types of connectors; 9-pin d-sub, screw terminal, and 2mm board-to-
board. The 9-pin D--sub is the standard connector and is recommended for data transfer rates higher than
1500kbit/s. This connector is also recommended by the PROFIBUS DP standard IEC 61158.

*) RTS is used in some equipment to determine the direction of transmission. In normal applications only A-
Line, B-Line and Shield are used.
**) +5V BUS and GND BUS are used for bus termination. Some devices, like optical transceivers (RS485
to fibre optics) might require external power supply from these pins. This device is not allowed to draw more
than 80mA from these power pins.
Bromma Conquip Kit no: 50 00083 -6- April. 09 rev.01
 Bromma Spare Part Kits

Basic Operation
Network- and Software Requirements
As a member of the Anybus concept of interchangeable network products, the Anybus-S PROFIBUS is
compatible with any product that supports the Anybus-S application interface. However, due to the nature of
the PROFIBUS networking system, certain things needs to be taken into account:

• The total (Input + Output) I/O size must exceed zero.

• The Cyclic I/O size for each direction cannot exceed 244 bytes
• Acyclic I/O is not supported
• The max. theoretical total I/O size (Input + Output) is 416 bytes. This value will be less when
using User Parameterization Data and Device Diagnostics (see 2-7 “PROFIBUS Buffer
Sizes”).
• The flexible nature of the Anybus concept allows the application to modify the behaviour on
PROFIBUS in ways which contradict the generic GSD-file or in other ways voids network
cer-tification. Those responsible for the implementation of the final product should ensure that
their level of implementation matches their own requirements and policies regarding network
certifi-cation and interoperability.
• The use of advanced PROFIBUS-specific functionality may require in-depth knowledge in
PROFIBUS networking internals and/or information from the official PROFIBUS specifica-
tions. In such cases, those responsible for the implementation of the product should either ob-
tain the PROFIBUS specification to gain sufficient knowledge or limit their implementation is
such a way that this is not necessary.

For further information about the Anybus-S software interface, consult the general Anybus-S Parallel Design
Guide.
Communication Settings
The Anybus module detects the PROFIBUS baudrate automatically.
Supported baud rates:

• 9.6 kbps • 500 kbps

• 19.2 kbps • 1.5 Mbps
• 45.45 kbps • 3 Mbps
• 93.75 kbps • 6 Mbps
• 187.5 kbps • 12 Mbps

Node Address
The node address can either be set using the on-board switches (range 0... 99) or through the mailbox interface
(range 0... 126). Note that address 126 is reserved for commissioning purposes.
See also...
• 1-2 “Node Address Switches”
• 3-9 “FB_SET_NODE_ADDRESS”
• 3-10 “FB_GET_NODE_ADDRESS”

Kit no: 50 00083 -7- April. 09 rev.01 Bromma Conquip

 Bromma Spare Part Kits

Data Exchange
I/O Data (Cyclic Data Exchange)
I/O Data is exchanged as Cyclical I/O on PROFIBUS. Note that the data sizes specified during initial-isation
must be sufficient to hold the data specified in the network configuration. If this is not the case, the Anybus
module will indicate an error on the Fieldbus Diagnostics LED
See also...
•3-2 “FB_INIT”
•3-8 “FB_SET_CONFIG”

Parameter Data (Acyclic Data Exchange)

Acyclic exchange of data is not supported on the Anybus-S PROFIBUS.

PROFIBUS Implementation
Conformance Notes
Products which claim PROFIBUS compliance must pass conformance tests at a certified test facility. HMS
embedded products for PROFIBUS are successfully tested for pre-compliance and found to com-ply with
PROFIBUS specifications. Test reports etc. are available and registered at the PROFIBUS Or-ganisation
(PNO).
The use of certified PROFIBUS networking technology (e.g. Anybus) does not automatically make the end
product certified. To be able to state PROFIBUS compliance for the end product, the final imple-mentation
will need to pass further certification tests at a certified test facility. Due to the vast custom-isation possibilities
found in the Anybus concept, the use of such technology alone does in itself not constitute a discount of the
certification fee.
Generic implementations1 generally only require basic knowledge in the PROFIBUS networking system and
are certifiable by nature as long as basic usage procedures are followed (exceptions and instructions are stated
where appropriate).
With advanced implementations2, the topic of network certification becomes slightly more complex. A side
effect of the inherent flexibility of the Anybus concept is that the application, in theory, can alter the behaviour
on PROFIBUS in ways which makes it impossible to successfully pass network certifica-tion tests. HMS
cannot possible foresee all possible usage scenarios for this type of implementation, which mean that those
responsible for the implementation of the Anybus module into the final product should take the necessary steps
to ensure that the implementation operates according to PROFIBUS specifications. This process may involve
steps which require in-depth knowledge in PROFIBUS net-working internals and/or information from the
official PROFIBUS specifications. Those responsible for the implementation of the final product should either
obtain the PROFIBUS specification to gain sufficient knowledge or limit their implementation in such a way
that this is not necessary.
Due to the rapid development in the industrial communication industry, and the impact this may have on
network certification procedures, always make sure to use the very latest Anybus revision when cer-tifying the
final product.
In case of uncertainties, contact your nearest HMS support department.

Contact information:http://www.profibus.com/pb/support/
See also...
Electronic Data Sheet (GSD-file)•2-4 “Electronic Data Sheet (GSD-file)”

Bromma Conquip Kit no: 50 00083 -8- April. 09 rev.01

 Bromma Spare Part Kits

Electronic Data Sheet (GSD-file)

On PROFIBUS, the characteristics of a device is stored in an ASCII-format data file with the suffix GSD.
This file is used by the PROFIBUS configuration tool when setting up the network. HMS pro-vides a generic
GSD-file, which corresponds to the default settings in the module.

Network Conformance Notes:

• The Anybus module is certified for network compliance under the condition that the implemen-
tation is compatible with the generic GSD-file supplied by HMS. Any changes which require
de-viations from the generic GSD-file voids network certification, and re-certification of the end
product is necessary.

See also... • 2-3 “Conformance Notes”

Device Identity
By default, the Anybus module identifies itself as a generic HMS product as follows:

Information Default Value

Vendor Name ‘HMS Industrial Networks
’Model Name‘ Anybus-S PROFIBUS (FW x.x)’
Ident Number 1003h

The device identity can be customized to allow the module to appear as a vendor specific
implementa-tion rather than a generic HMS product.

Network Conformance Notes:

• Custom device identity information requires a custom GSD-file, and thus re-
certification of the end product is necessary.
• PROFIBUS Ident Numbers are assigned by the PNO (PROFIBUS User
Organisation).

See also... • 3-2 “FB_INIT”

Configuration Data Handling

General Information
The maximum amount of configuration data that can be handled by the module is determined by the size of
the Configuration Data buffer, which is specified in FB_INIT.

The Anybus module is a modular slave, which means that the input/output block size is flexible and not tied
to a specific block length. The input/output blocks are specified by so-called Identifier bytes, which
defines the Input- and/or Output Data length as well as data consistency. The Identifier bytes are de-fined
in the GSD-file and are automatically extracted by the configuration tool when adding modules to the
configuration.
Network Conformance Notes:
• Custom Configuration Data is not supported by the generic GSD-file supplied by HMS.

See also... •3-2 “FB_INIT”

Kit no: 50 00083 -9- April. 09 rev.01 Bromma Conquip

 Bromma Spare Part Kits

Validation
During network startup, the master sends its Actual Configuration to the Anybus module for validation. By
default, the Anybus module adopts it’s Configuration Data from the master (i.e. a mismatch is not possible,
unless the configuration is bigger than the data sizes specified in ANYBUS_INIT).Validation of the
Configuration Data is optional.

• Configuration Data not validated (Default)No verification is performed. The size must however
not exceed the one defined in FB_INIT.
• Configuration Data validated (Advanced Users Only)The application downloads its expected
Configuration Data to the Anybus module, which in turn compares it to the Actual
Configuration received from the master, and provides a suitable re-sponse.
See also...
• 3-2 “FB_INIT”
• 3-8 “FB_SET_CONFIG”

User Parameterization Data

General Information
The master identifies itself with the slaves by sending Parameterization Data, specifying how the slave shall
operate (i.e. Master address, PNO-ID, Sync/Freeze capabilities etc.).
The Parameterization Data consists of three parts:

As seen in the table above, support for additional (i.e. > 1 byte) User Parameterization Data can option-ally
be implemented by supporting the corresponding mailbox commands in the application. Note how-ever that
this invalidates the generic GSD-file supplied by HMS.
The maximum amount of User Parameterization Data that can be handled by the module is determined by the
size of the User Parameterization Data buffer, which is specified in FB_INIT.
Network Conformance Notes:
• User Parameterization Data is not supported by the generic GSD-file supplied by HMS.
See also...
• 3-2 “FB_INIT”
Validation
The DP Standard Parameters are always evaluated by the Anybus module. Validation of User Parame-
terization Data is optional.•User Parameterization Data not validated (Default)No verification is performed.
The size must however not exceed the one defined in FB_INIT.
• User Parameterization Data validated (Advanced Users Only)The application can download its
expected User Parameterization Data to the Anybus module, which in turn compares it to the
actual User Parameterization Data received from the master, and provides a suitable
response.
See also... • 3-2 “FB_INIT”
• 3-5 “FB_CHECK_USER_PARAMETER_DATA”
• 3-6 “FB_GET_USER_PARAMETER”
Bromma Conquip Kit no: 50 00083 -10- April. 09 rev.01
 Bromma Spare Part Kits

Fieldbus Data Exchange

Basics
The module exchanges data on the fieldbus via two data buffers:

• Input Data BufferData written to this buffer will be sent to

the fieldbus.

• Output Data BufferThis buffer contains data received from

the fieldbus.

Basically, in order to exchange data on the fieldbus, all the appli-

cation has to do is to read/write data from/to these two buffers.
Note: The size and composition of the data buffers is determined during module initialisation. There-
fore, the module will not be able to exchange data on the fieldbus unless it has been properly
initialised first. For more information, see 10-1 “Start Up and Initialisation”.

Dual Port Memory vs. Internal Memory

Each of the two data buffers can have a portion of their data situated
in dual port memory. The remain-der is located in Internal Memory.
The advantage of having data situated in dual port memory is that it
can be accessed much faster than data situated in the In-ternal
Memory. Internal Memory can only be ac-cessed indirectly via
mailbox commands, and is thus better suited for less time critical
data.
It is possible to configure how much data that should be reside in
dual port memory, and how much that should be located in Internal
Memory. The maximum size of each data buffer is 2 kbytes, out of
which up to 5121 bytes can be configured to reside in dual port
memory.

Data types
Most fieldbus systems makes a distinction between fast cyclical data and slower parameter data. This is
reflected in the way data is treated by the Anybus-S module:

• I/O DataThis type of data is usually associated with fast fieldbus data (a.k.a. cyclic
data).
• Parameter DataThis type of data is usually associated with slow fieldbus data (a.k.a. acyclic
data).
How this data is treated for each fieldbus type is described in each separate fieldbus appendix.

1.Future Anybus versions may allow a larger amount of data to reside in dual port memory, see A-1
“Extended Memory Mode (4K DPRAM)”.

Kit no: 50 00083 -11- April. 09 rev.01 Bromma Conquip

 Bromma Spare Part Kits

Memory Map
The dual port memory is subdivided into several smaller areas based on their usage, see memory map below.

Note: Implementing A11 in the application will affect the memory map. See A-1 “Extended Memory
Mode (4K DPRAM)” for further information.

Bromma Conquip Kit no: 50 00083 -12- April. 09 rev.01

 Bromma Spare Part Kits

Control Register Area

This area contains information about the Anybus module; revision, initialisation parameters, fieldbus type and
status etc. This area also contains registers for Watchdog handling and Event Notification han-dling.

Note: Generally, the Control Register Area must be allocated by the application before access. Howev-er,
during module initialisation, it is allowed to read static data such as software revision, fieldbus type, module type
etc. without handshaking.

Kit no: 50 00083 -13- April. 09 rev.01 Bromma Conquip

 Bromma Spare Part Kits

Electrical Specification
Power Supply Requirements
The module features dual power supply pins. These can either be tied together or powered separately,
depending on the power supply in the host application. Either way, both must be powered in order for the
module to operate properly. Generally, it is recommended to tie both power supplies together.

Signal Characteristics

Bromma Conquip Kit no: 50 00083 -14- April. 09 rev.01

 Bromma Spare Part Kits

PE & Shielding Recommendations

In order to achieve proper EMC behaviour, the module must be properly connected to protective earth in
accordance with the fieldbus requirements.
The Anybus-S features three metal plated mounting holes, out of which two are used for extended elec-trical
connection between the application and the module. One of these two holes are used for connec-tion to
protective earth (PE). This hole will from now on be referred to as ‘the PE-hole’
If the housing of the application is of non conductive type, it is recommended to use PE-hole. However, if the
housing of the application is conductive, there are a two options:

• Protective Earth connection via PE-holeIn this case, the fieldbus connector must be completely
isolated from the application housing in order to avoid ground loops etc.

• Protective Earth connection via fieldbus connector / application housingIn this case, the PE-hole
must be isolated from the application in order to avoid ground loops etc.

The application must provide support for these different options in order to ensure compatibility with all fieldbus
systems. This issue becomes a bit more complex when using a fieldbus system that uses more than one fieldbus
connector as these connectors may need to be treated differently. In these cases, it is recommended to isolate
the fieldbus connectors from the application housing and use the PE-hole.
Contact HMS and/or consult each fieldbus specification for further information regarding PE/shielding
requirements.

Environmental Specification
Temperature
Operating
+0 to +70 degrees Celsius
(Test performed according to IEC-68-2-1 and IEC 68-2-2.)
Non Operating
-15 to +85 degrees Celsius
(Test performed according to IEC-68-2-1 and IEC 68-2-2.)

Relative Humidity
The product is designed for a relative humidity of 5 to 95% non-condensing.
Test performed according to IEC 68-2-30.

EMC compliance
The Anybus-S modules are tested according to EMC directive 89/336/EEC.
Emission
According to EN 61000-6-4:2001
Tested per 55011:1998/55022:1994, class A, radiatedImmunity
According to EN 61000-6-2:2001Tested perEN 61000-4-2:1995 (Electrostatic Discharge (ESD))
EN 61000-4-3:1996 (Radiated, radio frequency electromagnetic field)
EN 61000-4-4:1995 (Fast transients/burst)
EN 61000-4-5:1995 (Surge)
EN 61000-4-6:1996 (HF Injection)

Kit no: 50 00083 -15- April. 09 rev.01 Bromma Conquip

 Bromma Spare Part Kits

Conformance with Predefined Standards

Fieldbus
CertificationAll Anybus-S modules are pre-certified and found to comply with each fieldbus standard.
Please note that although the module itself has been pre-certified, the final product may still require re-
certification depending on the fieldbus standard.
This pre-certification is valid under the following conditions:
• Standard fieldbus connectors
• No fieldbus specific initialisation parameters
•Non-modified device description file (i.e. ‘.GSD’ or ‘.EDS’)

If any of these conditions change, the module is not considered to be pre-certified and requires re-cer-tification.
For more information, consult the fieldbus standard and/or contact HMS.

CE-Mark
Generally, most Anybus-S modules are certified according to the European CE standard unless other-wise
stated. It is however important to note that although the Anybus-S itself is certified, the final prod-uct may
still require re-certification depending on the application.

UL/cUL-Certificate
The Anybus-S modules are UL/cUL recognized for the US (NRAQ2) and Canada (NRAQ8) according to
UL508, “Programmable Controller”.

Troubleshooting
The module does not exchange data
• Check the Anybus-S Watchdog LED. If the module does not flash green at 1hz, this means that
the module is not initialised and therefore cannot exchange data.
Initialisation troubles
• Verify that the responses to the initialisation mailbox messages does not contain any error indi-cations.
•The maximum I/O/Parameter data sizes may differ between different fieldbus systems. Verify that
the initialisation parameters suit the currently used Anybus-S version.
•If using the HW_CHK mailbox message - does the module respond? If not, the module has de-
tected a hardware problem. The reason for the problem is indicated on the Anybus-S Watchdog LED.
•If using the ‘Load from FLASH’ mailbox command - ensure that the flash actually contains a valid
mailbox sequence.
The driver example in this document does not work
•In most cases, the example can’t work without modifications as it would require very specific
conditions to be met. Instead, we have chosen to illustrate how the code should work generally rather
than going into details on how to implement the code in a particular application.
•The example is provided for educational purposes and is far from complete. Several essential functions
for initialisation, error handling etc. has intentionally been left out and must be imple-mented by the user.
Common Handshaking Troubles, solutions
•Never write new commands to the Application Indication Register unless the module has re-sponded
to a previous command in the Anybus Indication Register first.
•Write to the Application Indication Register only when required. Unnecessary accesses to this register
will only result in loss of processing power. Use locked requests if an area should be ac-cessed as
soon as possible.
Bromma Conquip Kit no: 50 00083 -16- April. 09 rev.01
 Bromma Spare Part Kits

Reset Related Problems

•If the application utilizes hardware reset, for example via a manual reset button, there is a risk of the
interrupt line being held at a low level from the start. Therefore, certain precautions are need-ed to
ensure proper functionality. See C-1 “Interrupt Line and Hardware Reset”x

Above: The unit’s dimensions and placement of the four mounting holes, IP20 variant.

Electrical interface
The CAN interface ground and the power ground are connected.

Connector Interface Function

X1 5 pin male M12 Power and debug port
X2 5 pin female M12 CanOpen – towards the spreader control system.
No termination in the unit.
X3 8 pin female M12 or Fieldbus – towards the crane control system.
9-pole female D-SUB*
* D-SUB only valid for Profibus DPV1

Pin X1 Signal
1 Power supply 10V to 30V
2 Bootstrap, pull to gnd for bootstrap mode
3 Ground
4 Tx C167 (connect to Rx pin 2 in the PC female D-SUB)
5 Rx C167 (connect to Tx pin 3 in the PC female D-SUB)

Kit no: 50 00083 -17- April. 09 rev.01 Bromma Conquip

 Bromma Spare Part Kits

Pin X2 Signal
1 nc
2 nc
3 Ground
4 CAN high. No termination in the unit.
5 CAN low. No termination in the unit.

Pin X3 M12 Signal

1-8 Depending on type of AnyBus card

Pin X3 D-SUB Signal

1-9 According to manual for mounted AnyBus card

LED indicators
LED color and Status Description
description

On Power ON
Green
Power
Off Power OFF

On Anybus HW initialization error

Red
Anybus error
Off Anybus OK

Blinking Preoperational mode

Green
CANopen status Single flash Stopped mode

On Operational mode

Off Communication OK

Single flash CAN error state

Red
CANopen error
Double flash Other node failed

On Bus off

Green 2 seconds on/off Operational

BCAN status

Red 2 seconds on/off Communication lost/Not initialized

BCAN error

Bromma Conquip Kit no: 50 00083 -18- April. 09 rev.01