Page 1
Operating Manual
CX27 Gateway
I2720-2.0 en
Page 2
d
Page 3
1 Safety instructions 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Documentation 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 General information 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 EtherCAT connection 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Setting isochronous data transfer 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Configuration with TwinCAT 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 Configuration with EtherCAT Studio 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 EtherCAT 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Basic principles 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Principle of operation 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Configuration 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 Communication 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Synchronization 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
6 CX27-object specifications 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Detailed object description 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Emergency messages 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 Connections 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 Supply voltage (socket X104) 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 FireWire (sockets X5/X6/X101/X102) 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3 Ethernet (sockets X7/X100) 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4 EtherCAT (sockets X8/X9) 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5 Digital inputs and outputs 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8 Status display 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1 System LED 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Ethernet 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3 EtherCAT 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9 Accessories 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1 System accessories 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.1 BPX001 active backplane 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2 Housing connection elements 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 Voltage supply 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.1 Power pack NTX001 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.2 Supply cable 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3 FireWire 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.1 FireWire cable (module to module; IP20) 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HBMQuantumX
Page 4
4
10 Abbreviations 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11 Support 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HBM QuantumX
Page 5
1 Safety instructions
Appropriate use
The module and the connected transducers may be used for measurement and directly
related control tasks only. Any other use is not appropriate.
To ensure safe operation, the module may only be used as specified in the operating
manual. It is also essential to follow the respective legal and safety regulations for the
application concerned during use. The same applies to the use of accessories.
Each time, before starting up the modules, you must first run a project planning and risk
analysis that takes into account all the safety aspects of automation technology. This
particularly concerns personal and machine protection.
Additional safety precautions must be taken in plants where malfunctions could cause major
damage, loss of data or even personal injury. In the event of a fault, these precautions
establish safe operating conditions.
This can be done, for example, by mechanical interlocking, error signaling, limit value
switches, etc.
5Safety instructions
Safety rules
A module must not be connected directly to a power supply network. The maximum
permissible supply voltage is 10 to 30 V (DC).
The supply connection, as well as the signal and sense leads, must be installed in such a
way that electromagnetic interference does not adversely affect device functionality (HBM
recommendation: ”Greenline shielding design”, downloadable from the Internet at
http://www.hbm.com/Greenline).
Automation equipment and devices must be covered over in such a way that adequate
protection or locking against unintentional actuation is provided (such as access checks,
password protection, etc.).
When devices are working in a network, these networks must be designed in such a way that
malfunctions in individual nodes can be detected and the nodes shut down.
Safety precautions must be taken both in terms of hardware and software, so that a line
break or other interruptions to signal transmission, such as via the bus interfaces, do not
cause undefined states or loss of data in the automation device.
HBMQuantumX
Page 6
6 Safety instructions
Conditions on site
For modules with degree of protection IP20:
− Protect the modules from humidity or effects of the weather such as rain, snow, etc.
− The permissible relative humidity at 31°C is 80% (non-condensing); linear reduction down
to 50%, at 40°C.
− Ensure that the ventilation openings on the sides are not covered.
For all modules:
− Do not expose the instrument to direct sunlight.
− Observe the maximum permissible ambient temperatures given in the specifications.
Maintenance and cleaning
The modules are maintenance-free. Please note the following when cleaning the housing:
− Before cleaning, disconnect the equipment completely.
− Clean the housing with a soft, slightly damp (not wet!) cloth. Never use solvents, since
these could damage the labelling on the front panel and the display.
− When cleaning, ensure that no liquid gets into the module or connections.
General dangers of failing to follow the safety instructions
The module is a state-of-the-art device and as such is failsafe. The module may give rise to
further dangers if it is inappropriately installed and operated by untrained personnel. Any
person instructed to carry out installation, commissioning, maintenance or repair of the
module must have read and understood the Operating Manuals and in particular the
technical safety instructions.
Remaining dangers
The scope of supply and performance of the module covers only a small area of
measurement technology. In addition, equipment planners, installers and operators should
plan, implement and respond to the safety engineering considerations of measurement
technology in such a way as to minimize remaining dangers. Prevailing regulations must be
complied with at all times. There must be reference to the remaining dangers connected with
measurement technology. After making settings and carrying out activities that are
password-protected, you must make sure that any controls that may be connected remain in
a safe condition until the switching performance of the module has been tested.
Working safely
Error messages should only be acknowledged once the cause of the error is removed and
no further danger exists.
HBM QuantumX
Page 7
Conversions and modifications
The module must not be modified from the design or safety engineering point of view except
with our express agreement. Any modification shall exclude all liability on our part for any
resultant damage.
In particular, any repair or soldering work on motherboards (replacement of components) is
prohibited. When exchanging complete modules, use only original parts from HBM.
The module is delivered from the factory with a fixed hardware and software configuration.
Changes can only be made within the possibilities documented in the manuals.
Qualified personnel
Qualified personnel means persons entrusted with the installation, fitting, commissioning and
operation of the product who possess the appropriate qualifications for their function. This
module is only to be installed and used by qualified personnel, strictly in accordance with the
specifications and the safety rules and regulations.
7Safety instructions
This includes people who meet at least one of the three following requirements:
• Knowledge of the safety concepts of automation technology is a requirement and as
project personnel, you must be familiar with these concepts.
• As automation plant operating personnel, you have been instructed how to handle the
machinery and are familiar with the operation of the modules and technologies described
in this documentation.
• As commissioning engineers or service engineers, you have successfully completed the
training to qualify you to repair the automation systems. You are also authorized to
activate, to ground and label circuits and equipment in accordance with safety
engineering standards.
It is also essential to comply with the legal and safety requirements for the application
concerned during use. The same applies to the use of accessories.
NOTE
The safety instructions in this document also apply to the NTX001 power supply and
the BPX001 backplane.
HBMQuantumX
Page 8
8 Safety instructions
In this manual, the following symbols are used to point out residual dangers:
Symbol: DANGER
Meaning: Maximum danger level
Warns of an imminently dangerous situation in which failure to comply with safety
requirements will result in death or serious bodily injury.
Symbol: WARNING
Meaning: Dangerous situation
Warns of a potentially dangerous situation in which failure to comply with safety
requirements can result in death or serious bodily injury.
Symbol: CAUTION
Meaning: Potentially dangerous situation
Warns of a potentially dangerous situation in which failure to comply with safety
requirements could result in damage to property or some form of bodily injury.
Symbol:
Meaning: Electrostatic Sensitive Devices
Devices marked with this symbol can be destroyed by electrostatic discharge. Please
observe the precautions for handling electrostatic-sensitive devices.
Symbol: On the equipment
Meaning: Observe information provided in the operating manual.
HBM QuantumX
Page 9
Symbols pointing out notes on use and waste disposal as well as useful information:
Symbol: NOTE
Points out that important information about the product or its handling is being given.
Symbol:
Meaning: CE mark
The CE mark enables the manufacturer to guarantee that the product complies with the
requirements of the relevant EC directives (the declaration of conformity is available at
http://www.hbm.com/hbmdoc).
9Safety instructions
Symbol:
Meaning: Statutory marking requirements for waste disposal
National and local regulations regarding the protection of the environment and recycling of
raw materials require old equipment to be separated from regular domestic waste for
disposal.
For more detailed information on disposal, please contact the local authorities or the dealer
from whom you purchased the product.
HBMQuantumX
Page 10
10
2 Documentation
Purpose of this operating manual
This operating manual gives you information about the CX27 EtherCAT Gateway to the
measurement modules of the QuantumX DAQ family. It should support you in integrating the
QuantumX family into your real-time automation jobs.
The QuantumX family documentation consists of
• A printed quick start guide for initial start up (printed version)
• This operating manual (PDF format)
• The QuantumX operating manual (PDF format)
• A comprehensive HTML help with index and easy search options, which is available after
the installation of a software package (e.g. QuantumX Assistant, catmanEASY)
We reserve the right to modification and revision of this documentation. Updates will be
published on the relevant product pages of our Internet site, www.hbm.com.
Further Information
EtherCAT is an open standard (IEC/FDIS 61158), so please take the information available on
www.ethercat.org as further reference to this operating manual.
CANopen documentation can be obtained from the user organization, CAN in Automation
(CiA) (www.can-cia.de).
HBM QuantumX
Page 11
3 General information
The CX27 QuantumX module is a so-called gateway. A gateway allows networks based on
totally different protocols to communicate with each other.
The main task of the Ethernet/EtherCAT CX27 Gateway is to receive and forward the data of
the modules connected via FireWire.
Front Back
FireWire
CX27 sync
I
N
Ethernet
11
Digital platform
Ethernet
FireWire
IN
EtherCAT
OUT
FireWire
Fig. 2.1: CX27 Gateway; block diagram
Data are transferred, module timing is synchronized and optimum voltage is supplied via the
FireWire connections. Data transmission is asynchronous (all nodes) or isochronous (to a
specific node, e.g. CX27).
You can interconnect a total of twelve modules in series via FireWire.
The connection to the modules can either be made with appropriate FireWire connection
cables (1-KAB269-x), or via the BPX001 backplane (see Fig. 2.2). The backplane
interconnects up to nine modules, without the need for complicated cabling, and can link
these to additional modules or backplanes via two additional FireWire sockets. The FireWire
interfaces of the individual modules are actively connected to each other.
HBMQuantumX
Page 12
12
CX27
EtherCAT IN/OUT
BPX001
FireWire
CX27
Ethernet
Fig. 2.2: CX27 connection via the BPX001 backplane
The CX27 Gateway has two Ethernet interfaces and one EtherCAT interface (IN/OUT) for a
network connection. The Ethernet interfaces at the front and back of the module are
equivalent, and are implemented as RJ45 sockets.
The Ethernet interface at the front of the module is designed for measurement and servicing
purposes and is used with a backplane mounting.
The Ethernet interface at the back of the module can be used in distributed operation (see
Fig. 2.3).
Measurement tasks: the central interface to all the connected modules and their measured
values.
Service tasks: the central interface to all the connected modules for diagnosis or update.
Note: the factory settings of the modules can be restored with the QuantumX Assistant.
Note
The Ethernet interfaces at front and back of the Gateway must have different IP
addresses! You can configure both interfaces with the QuantumX Assistant. With a
BPX001 backplane mounting, only the Ethernet socket at the front is available.
HBM QuantumX
Page 13
13
MX...
10 V − 30 V DC
MX...
CX27
X102
X101
X102
X101
max. 1.5 A
FireWire connection
1-Kab269-2
2 m connection cable
Ethernet connection
Fig. 2.3: Example: Ethernet connection to a PC/laptop via CX27
X102
X101
Alternative Ethernet connection
at the front
HBMQuantumX
Page 14
14
The RJ45 connecting sockets at the front, X8 and X9, are designed for connection to the
EtherCAT fieldbus with real-time capability (Ethernet for Controller and Automation
Technology).
10 V − 30 V DC
MX...
MX...
CX27
(slave)
FireWire
EtherCAT connection
Master
X9
Further slaves
Fig. 2.4: Example: QuantumX-EtherCAT connection via CX27
HBM QuantumX
Page 15
4 EtherCAT connection
EtherCAT connection basically comprises the following steps:
1. One-off module/channel setup for isochronous data traffic with the QuantumX Assistant
(possibly also channel configuration).
2. Setting and configuring the individual channels via EtherCAT:
• channel configuration (SDO)
• process data assignment (PDO)
The following EtherCAT configuration tools are currently available:
• EtherCAT Studio (König PA)
• TwinCAT (Beckhoff)
The XML file required for configuration can be found on the QuantumX System CD or on the
HBM Internet site. You can also perform the configuration via a network scan or the
information stored in the EEPROM.
15
4.1 Setting isochronous data transfer
You must first configure the relevant module channels for isochronous data transmission with
the QuantumX Assistant (”Signals” tab) and via Ethernet TCP/IP:
1. Connect your modules in the deactivated state to the CX27 Gateway via FireWire cable
1-KAB269 (from connection X102 to X101, etc.), or use the active 1-BPX001 backplane
for connection.
2. Connect your PC to the CX27 Gateway via an Ethernet cable.
3. Switch on the supply voltage.
4. Launch the QuantumX Assistant.
5. In the ”Signals” tab, activate isochronous data transfer for the required channels (see
Fig.2.1).
activate
Fig.2.1: Activating isochronous data transfer
You can now work via the EtherCAT Gateway and configure your modules for EtherCAT
applications.
HBMQuantumX
Page 16
16
4.2 Configuration with TwinCAT
Always use the current software version!
• Start TwinCAT
• Run TwinCAT system manager
• Right-click on I/O Device node and select ”Scan devices”, validate next dialog boxes (the
EtherCAT node is then added to the devices)
• Right-click on the EtherCAT device node and click on ”Append” box
• Highlight and insert ”HBM CX27” slave
(the HBM CX27 node is then added below the EtherCAT device)
• Select CX27 box and click the ”Process Data” tab
• Click ”Load PDO info from device” to refresh the object dictionary
• Highlight the inputs address field under the ”Sync Manager” dialog
• Activate ”PDO Assignment” and mark amount of PDOs (= QuantumX isochronous
signals)
Check amount
of PDOs
• Run EtherCAT Master and check PDO data from CX27 Slave (basic measurement)
Select Inputs
32
Note
You need the relevant Device Description File (HBM_CX27.xml) for the device to
integrate the QuantumX EtherCAT Gateway into the network. If there is a version
conflict, you can find the XML Device Description File on the QuantumX System CD or
on the relevant Download sites at ”www.hbm.com”.
HBM QuantumX
Page 17
4.3 Configuration with EtherCAT Studio
Always use the current software version!
• Start EtherCAT Studio
• Right-click on EtherCAT Master in ”Append” dialog, select ”HBM Communication modules
−> HBM CX27”
• Attach master and accept ”Online Operations” for network scan
• Select CX27 Slave and click ”CoE Online” tab
• Refresh object dictionary and check identifiers (AI_connector_identification)
• Select ”FMMU/SM” tab on CX27 slave
• Under Sync Manager Configuration field, highlight inputs address field
• Activate ”PDO assignment” and mark amount of PDOs (= QuantumX isochronous signals)
17
PDOs
MX840: 8
Inputs
Note
You need the relevant Device Description File (HBM_CX27.xml) for the device to
integrate the QuantumX EtherCAT Gateway into the network. If there is a version
conflict, you can find the XML Device Description File on the QuantumX System CD or
on the relevant Download sites at ”www.hbm.com”.
HBMQuantumX
Page 18
18
5 EtherCAT
5.1 Basic principles
EtherCAT (Ethernet for Control Automation Technology) is an open and standardized
fieldbus system, characterized by a high performance capability and corresponding in
principle to a specifically adapted Ethernet solution (standard: IEC/FDIS 61158):
EtherCAT uses Ethernet Frames as defined in IEEE 802.3 and supports the use of other
Ethernet protocols in the same network.
End users of EtherCAT have banded together in the EtherCAT Technology Group (ETG) to
support and promote EtherCAT technology
(www.ethercat.org).
EtherCAT replaces the classic Ethernet hubs and switches star topology (although this can
still be used) with an easy-to-cable line topology. Branches or stub lines are supported. The
grouping here is usually one master and additional slaves.
Master
IN
Fig.5.5: Example: CX27 Gateway to EtherCAT, modules connected via FireWire
5.2 Principle of operation
In contrast to standard Ethernet, the Ethernet Frames from the slaves are processed in
passing (IN and OUT sockets). The standard Ethernet Frame sent by the master (as per
IEEE 802.3) is not first received, then interpreted and the process data copied at every
interconnection, as is the case with other industrial Ethernet solutions. The EtherCAT slave
devices read the data relevant to them as the telegram passes through the device. Input data
are also inserted into the telegram in passing. So a frame is not fully received before being
processed, the processing starts as early as possible. Sending also occurs with a minimal
time offset of just a few bits. The master relies on a standard Ethernet controller.
CX27
OUT
FireWireEtherCAT
MX840 MX ...
HBM QuantumX
Page 19
5.3 Configuration
Most of the effort required for implementation is usually taken on by the configuration tool.
Clearly defined interfaces have been created to minimize this effort. The configuration tool
learns about the device properties from the XML file (Device Description File = DDF). In turn,
the configuration tool also generates an XML file containing all the relevant information about
the network topology, the process data layout, startup and diagnosis. The actual master
implementation only has to load this file and extract the Ethernet frames required to start and
operate the network.
19
The QuantumX EtherCAT slaves can be configured either via DDF or via a scan and the
EEPROM integrated in the slave. This allows the SM/FMMU information (SYNC
Manager/Fieldbus Memory Management Unit) to be read out.
5.4 Communication
By default, EtherCAT uses CANopen (CoE − CANopen over EtherCAT) as the application
layer.
CANopen (CAN: Controller Area Network) is the open protocol standard for CAN in
automation technology and has been standardized in the ”CAN in Automation” (CiA)
association. The protocol uses CANBus as the transmission medium and specifies the basic
structures for network management, the use of the CAN Identifier (message address), the
behavior on the bus over time, the type of data transmission, and application-specific
profiles. This should ensure that CANopen modules from different manufacturers can be
combined (that the devices speak the same language). CANopen defines the application
layer (OSI Layer 7) as the communication profile specified by the CiA in Standard DS30x as
the same for all applications. It establishes how communication is to take place. As with
some other fieldbuses, a distinction is made between real-time data and parameter data.
HBMQuantumX
Page 20
20
CANopen uses communication objects with different properties:
Service Data Objects (SDO)
In the parameter channel, all the CX27 parameters can be read and modified by the SDO
service. The required parameter is addressed within an SDO telegram by index and
sub-index.
SDOs form the communication channel for transmitting device parameters, such as the ADC
sample rate. As these parameters are transmitted acyclically (for example, once only, when
powering up the network), SDOs have a subordinate priority.
Process Data Objects (PDO)
A PDO telegram is used, for example, to transmit cyclic measurement data in real time,
which in turn is used for controlling, regulating and observing the ongoing process. The
transmission times here are linked to the cycle times/clock rates specified by a master. No
objects are addressed in the telegram, instead the content of previously selected parameters
is directly sent.
All the device parameters are stored in an object dictionary. This object dictionary contains
the description, data type and structure of the parameters, as well as the address (index).
For the QuantumX CX27 Gateway, the standardized DS404 device profile for the
sensor/controller group is enlisted, with meaningful additions, and this is shown in Chapter 6.
Only the indexes required for configuration are described here, starting from 0x6000. For a
description of the other index ranges, please refer to the CiA Standard.
Object dictionary DS404 (Version 1.2.2)
The object dictionary is the compilation of all the variables and parameters (objects) of a
CANopen device. This gives the data the process image and the parameters can be used to
influence the operating behavior of a CANopen device.
An object dictionary is structured in such a way that some parameters are mandatory for all
the devices of this category and others can be freely defined and used. In CANopen, objects
are primarily given a number (the so-called index), which uniquely identifies them and can
also be used to address them. Objects can be implemented as simple data types, such as
bytes, integers, longs or also strings. With more complex structures, such as arrays and
structures, a sub-index is introduced to address the individual elements.
The structure of the object dictionary, the assignment of index numbers, and some
mandatory entries are specified in the device profiles. For the user, the object dictionary is
stored as an EDS file (Electronic Data Sheet). In the EDS file, all the objects are stored with
index, sub-index, name, data type, default value, minima, maxima and access options
(read/write, transmission by SDO only or also by PDO, etc.). This means that the EDS file
describes the full functionality of a a CANopen device.
CANopen standard objects (from address 0x1xxx) can be obtained from the CiA
(www.can-cia.de).
HBM QuantumX
Page 21
5.5 Synchronization
It is important for the timing of all the nodes in the network to be exactly synchronized when
simultaneous actions are required for widely distributed processes. With the distributed
clocks synchronization method (IEEE 1588), the timing of the master clock is transmitted to
the slave clocks via the EtherCAT network and aligned to compensate for the delay offset.
With an EtherCAT grouping, the principal clock is in a slave device, as the master should
deliberately be mapped by standard components. All the nodes can then be synchronized
with an error of less than 1 ms.
The distributed clocks option can be activated/deactivated by a relevant tag in the Device
Description File (DDF). If distributed clocks is activated, the timing master forwards the time
to the QuantumX slave and this distributes the timing to the modules. The default is for
distributed clocks to be activated.
The distributed clocks approach is also useful when you want to perform measurements in
parallel via Ethernet and enlist the same time stamp as a reference.
If the master does not support distributed clocks, the time is set to zero on module startup
and timing commences from this point.
21
The EtherCAT CX27 slave connects the powerful, modular QuantumX data acquisition
system to this fieldbus with up to 199 time-synchronized signals. The maximum sampling
rate at this time is 1200 Hz.
Up to 3 Sync Managers can be assigned.
The CX27 operates with the ”SYNC 0” pulse. The cycle time can be set up to the 125 µs
range. Smaller values cause the loss of real-time data.
HBMQuantumX
Page 22
22
6 CX27 object specifications
Possible SDOs for the Gateway are described in this chapter (name, description, value
range, data type, index/sub-index)
Index
The index gives the position of the object in the object dictionary. The index value
specification is hexadecimal. The values for the DS404 device profile are located from
address 0x6xxx.
Object code
The object code indicates the data structure of the object.
Object code Meaning Coding
VAR A simple value, of the Integer8, Unsigned32 or Visible String8
type, for example.
ARRAY A data field, where every entry is of the same data type. 8
RECORD A data field containing entries that are a combination of simple
data types.
CANopen
7
9
Data type Value range Data length
Boolean 0 = false, 1 = true 1 byte
INT8 −128 to +128 1 byte
INT16 −32768 to +32768 2 bytes
INT32 −2147483648 to +2147483648 4 bytes
UINT8 0 to 255 1 byte
UINT16 0 to 65535 2 bytes
UINT32 0 to 4294967295 4 bytes
Visible String8 ASCII characters 8 bytes
Visible String16 ASCII characters 16 bytes
Access
ro: Read only
rw: Read/write
wo: Write only
PDO mapping
PDO mapping is understood to be the mapping of application objects (real-time data) from
the object dictionary to process data objects. CANopen device profiles provide default
mapping for every device type, which is suitable for most applications.
HBM QuantumX
Page 23
Object index organization
Object index (hex) Object index (dec) Object
0000 0 Not used
0001 − 001F 1 − 31 Static Data Types
0020 − 003F 32 − 63 Complex Data Types
0040 − 005F 64 − 95 Manufacturer Specific Complex Data Types
0060 − 007F 96 − 127 Device Profile Specific Static Data Types
0080 − 009F 128 − 159 Device Profile Specific Complex Data Types
00A0 − 0FFF 160 − 4095 Reserved for further use
1000 − 1FFF 4096 − 8191 Communication Profile Area
2000 − 5FFF 8192 − 24575 Manufacturer Specific Profile Area
6000 − 9FFF 24576 − 40959 Standardized Device Profile Area
A000 − FFFF 40960 − 65535 Reserved for further use
23CANopen
HBMQuantumX
Page 24
24
CANopen
SDO Object overview
Description Object name Index (hex) Page
Sensor
Sensor type AI_Sensor_type 6110 25
Operating mode AI_Operating_mode 6112 27
ADC sample rate AI_ADC_sample_rate 6114 29
Sensor manufacturer Al_Sensor_manufacturer 6115 29
Sensor model Al_Sensor_model 6116 30
Sensor serial number Al_Sensor_serialnumber 6118 30
Sensor location Al_Sensor_location 6119 31
Sensor calibration period Al_Sensor_ calibration_period 611B 31
TEDS
TEDS control Al_TEDS_control 611C 32
Scaling
Input scaling 1 FV AI_Input_scaling_1_FV 6120 36
Input scaling 1 PV AI_Input_scaling_1_PV 6121 36
Input scaling 2 FV AI_Input_scaling_2_FV 6122 37
Input scaling 2 PV AI_Input_scaling_2_PV 6123 37
Input offset AI_Input_offset 6124 41
Autozero AI_Autozero 6125 41
Scaling factor Al_Scaling_factor 6126 38
Scaling offset Al_Scaling_offset 6127 38
Process Value Reading
Input PV AI_Input_PV 6130 39
Physical unit PV AI_Physical_unit_PV 6131 40
Overflow Limits for Process Values
Input Status
Status AI_Status 6150 34
Filter type AI_Filter_type 61A0 33
Filter frequency AI_Filter_frequency 61A2 33
Identification
Connector signal name Al_Signal_name 61B0 35
Connector identification Al_Connector_identification 61B1 35
HBM QuantumX
Page 25
6.1 Detailed object description
Analog input sensor type
Object description Index 6110 (hex) 24848 (dec) Note
Object name AI_sensor_type Specifies the type of sensor which is
Object code Array
Data type UINT16
CiA standard Yes
Category Optional
Value description Sub-index 0 (hex) 1 (hex) 2 (hex) to C7 (hex)
Description Number of entries AI_sensor_type 1 AI_sensor_type 2 AI_sensor_type_199
Entry category Mandatory Mandatory Optional Optional
Access ro rw rw rw
PDO mapping No No No No
Value range 1 − 199 UINT16 UINT16 UINT16
Default value No 0 0 0
connected to the analog input.
25CANopen
Value Description
0 Unknown
1 Thermocouple type J
2 Thermocouple type K
3 Thermocouple type L
4 Thermocouple type N
5 Thermocouple type R
6 Thermocouple type S
7 Thermocouple type T
8 − 29 Reserved (other types of thermocouple)
30 PT100
31 PT200
32 PT500
33 PT1000
34 PT5000
35 IR sensor
36 − 39 Reserved
40 Voltage
41 +/− 10 V
42 0 − 10 V
43 +/− 1 V
44 0 − 1 V
45 +/− 100 mV
46 0 − 100 mV
47 − 49 Reserved
50 Current
HBMQuantumX
Page 26
26
CANopen
Value Description
51 4 − 20mA
52 0 − 20mA
53 − 59 Reserved
60 Frequency
61 − 69 Reserved
70 Strain gage
71 Strain gage full bridge Analog input sensor type
72 Strain gage half bridge
73 Strain gage quarter bridge
74 − 79 Reserved
80 LVDT
81 − 89 Reserved
90 Pressure transducer
91 − 99 Reserved
100 Temperature transducer
101 − 109 Reserved
110 Force transducer
111 − 119 Reserved
120 Potentiometer
121 − 139 Reserved
140 NTC
141 − 9999 Reserved
10000 − 65535 Manufacturer specific use
HBM QuantumX
Page 27
Analog input operating mode
Object description Index 6112 (hex) 24850 (dec) Note
Object name AI_Operating_mode A value other than 0 sets the analog input
Object code Array
Data type UINT8
CiA standard Yes
Category Optional
Value description Sub-index 0 (hex) 1 (hex) 2 (hex) to C7 (hex)
Description Number of entries AI_Operating_
mode 1
Entry category Mandatory Mandatory Optional Optional
Access ro rw rw rw
PDO mapping No No No No
Value range 1 − 199 UINT8 UINT8 UINT8
Default value No 0 0 0
channel to special operating modes.
AI_Operating_
mode 2
AI_Operating_mode
199
27CANopen
Value Description
0 Channel off (not operating)
1 Normal operation
2 − 9 Reserved
10 − 255 Implementation specific
Several signals
QuantumX modules are able to deliver several signals from one connector.
Module MX410:
1. Signal S1 with filter setting 1
2. Signal S2 with filter setting 2
For these signals, all the objects described above are available.
Peak unit MX410: 8 signals
1. Peak 1 with different modes, (positive peak, negative peak, peak-to-peak)
2. Peak 2 with different modes, (positive peak, negative peak, peak-to-peak)
.
.
.
8. Peak 8 with different modes, (positive peak, negative peak, peak-to-peak)
For these signals, all the objects in the analog input function block described above are
read-only.
HBMQuantumX
Page 28
28
CANopen
So it is useful to indicate the mode of the signal in object 6112h as follows:
10: Signal_S1
11: Signal_S2
20: Signal_positive_peak
21: Signal_negative_peak
22: Signal_peak_to_peak
30: Signal_rms
100: Signal_CAN
HBM QuantumX
Page 29
Analog input ADC sample rate
given in multiples of microseconds
Object description Index 6114 (hex) 24852 (dec) Note
Value description
Object name AI_ADC_sample_rate This value uses the reciprocal conversion rate
Object code Array
Data type UINT32
CiA standard Yes
Category Optional
Sub-index
Description Number of
Entry category Mandatory Mandatory Optional Optional
Access ro rw rw rw
PDO mapping No No No No
Value range 1 − 199 UINT32 UINT32 UINT32
Default value No 1 1 1
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
entries
AI_ADC_sample_
rate 1
deployed by the AD converter. The value is
given in multiples of microseconds.
AI_ADC_sample_
rate 2
29CANopen
.
AI_ADC_sample_rate
199
Analog input sensor manufacturer
Object description Index 6115 (hex) 24853 (dec) Note
Object name AI_sensor_manufacturer
Object code Array
Data type Visible string
CiA standard Yes
Category Optional
Value description
Sub-index
Description Number of entries AI_sensor_manufa
Entry category Mandatory Mandatory Optional Optional
Access ro ro ro ro
PDO mapping No No No No
Value range 1 − 199 see object
Default value No 0 0 0
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
cturer 1
description
AI_sensor_manufac
turer 2
see object
description
AI_sensor_tmanufact
urer 199
see object
description
HBMQuantumX
Page 30
30
Analog input sensor model
Object description Index 6116 (hex) 24854 (dec) Note
Object name AI_sensor_model This value provides the model of each
Object code Array
Data type Visible string
CiA standard Yes
Category Optional
Value description
Sub-index
Description Number of entries AI_sensor_model1AI_sensor_model 2 AI_sensor_model
Entry category Mandatory Mandatory Optional Optional
Access ro ro ro ro
PDO mapping No No No No
Value range 1 − 199 see object
Default value No 0 0 0
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
description
connected sensor.
see object
description
CANopen
199
see object
description
Analog input sensor serial number
Object description Index 6118 (hex) 24856 (dec) Note
Value description
Object name AI_serial_number This value provides the serial number of each
Object code Array
Data type Visible string
CiA standard Yes
Category Optional
Sub-index
Description Number of entries AI_sensor_serial_
Entry category Mandatory Mandatory Optional Optional
Access ro ro ro ro
PDO mapping No No No No
Value range 1 − 199 see object
Default value No 0 0 0
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
number 1
description
connected sensor.
AI_sensor_serial_
number 2
see object
description
AI_sensor_serial_
number 199
see object
description
HBM QuantumX
Page 31
Analog input sensor location
value may be added to the calibration date to
libration
d is also defined i
Object description Index 6119 (hex) 24857 (dec) Note
Value description
Object name AI_sensor_location This value provides the ”LocationID” defined
Object code Array
Data type UINT16
CiA standard Yes
Category Optional
Sub-index
Description Number of entries AI_sensor_location1AI_sensor_location2AI_sensor_location
Entry category Mandatory Mandatory Optional Optional
Access ro ro ro ro
PDO mapping No No No No
Value range 1 − 199 see IEEE14514 see IEEE14514 see IEEE14514
Default value No 0 0 0
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
in IEEE14514.
31CANopen
199
Analog input sensor calibration date
Object description Index 611A (hex) 24858 (dec) Note
Value description
Object name AI_sensor_calibration_date This value provides the recommended time
Object code Array
Data type Time of day
CiA standard Yes
Category Optional
Sub-index
Description Number of entries AI_sensor_calibrati
Entry category Mandatory Mandatory Optional Optional
Access ro ro ro ro
PDO mapping No No No No
Value range 1 − 199 see IEEE14514 see IEEE14514 see IEEE14514
Default value No 0 0 0
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
on_period 1
period between transducer calibrations. The
value may be added to the calibration date to
calculate the date for the next calibration. The
ca
/IEEE14514/.
AI_calibration_perio
d 2
perio
n
AI_calibration_period
199
HBMQuantumX
Page 32
32
value may be added to the calibration date
IEEE14514
CANopen
Sensor calibration period
Object description Index 611B (hex) 24859 (dec) This value provides the recommended time
Object name AI sensor calibration period
Object code Array
Data type Time difference
CiA standard Yes
Value description
Sub-index
Description Number of entries AI sensor
Entry category Mandatory Mandatory Optional Optional
Access ro ro ro ro
PDO mapping No No No No
Value range 1 − 199 see CiA301 see CiA301 see CiA301
Default value No No No No
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
calibration period 1
period between transducer calibrations. The
value may be added to the calibration date
to calculate the date for the next calibration.
The calibration period is also defined in
AI sensor
calibration period 2
.
AI sensor calibration
period 199
AI TEDS control
Object description Index 611C (hex) 24860 (dec)
Object name AI_TEDS_control
Object code Array
Data type UINT8
CiA standard To be incorporated
Value description
Sub-index
Description Controls the handling of TEDS and non-TEDS sensors in the DAQ system
Access rw
PDO mapping possible
Values 0 Ignore TEDS Means that the DAQ system will not use the
Default value −
−
data stored in the sensor to adapt the settings.
2 Use TEDS if
available
3 TEDS required Means that the DAQ has to use the TEDS data.
Means that the DAQ system will use the TEDS
data to setup the DAQ. But if there is no TEDS
available in the sensor, the DAQ system will not
go to an error state.
If there is no TEDS data available, the DAQ
system indicates an error.
HBM QuantumX
Page 33
Filter type
characteristic in object 61A0h
Object description Index 61A0 (hex) 24992 (dec)
Object name AI_Filter_type
Object code Array
Data type UINT8
CiA standard Yes
Value description
Sub-index
Description Filter characteristics selection
Access rw
PDO mapping no
Values 0 No filter
Default value −
−
1 Moving average
2 Repeating average
3
4
5 − 99 Reserved
100 − 255 Manufacturer
Low-pass Bessel
characteristic
Low-pass
Butterworth
characteristic
specific
33CANopen
Low-pass Bessel and low-pass Butterworth are
standard filter characteristics in the test and
measurement world.
Filter frequency
Object description Index 61A2 (hex) 24994 (dec) Here the cut-off filter frequency is specified
Object name AI_Filter_frequency
Object code
Data type Float
CiA standard To be incorporated
Value description
Sub-index
Description
Access
PDO mapping
Values
Default value −
−
in Hz, according to the selected filter
characteristic in object 61A0h.
.
HBMQuantumX
Page 34
34
Status
Object description Index 6150 (hex) 24912 (dec)
Object name AI_Status
Object code
Data type
CiA standard To be incorporated
Data content
Bit 0 (LSB) No sensor connected, signal invalid, overload.
1 and 4 Set, if object 611C has value of 3 (TEDS_required) and TEDS is
not present or invalid or object 611C has value of 2 (use TEDS if
available) and TEDS is invalid.
1 Overload positive
2 Overload negative
3 Reserved
4 Set, if object 611C has value of 2 (use TEDS if available) and
TEDS is not present
5 Sensor with TEDS connected
6 Setting changed
7 (MSB) Reserved
CANopen
HBM QuantumX
Page 35
Connector signal name
Object description Index 61B0 (hex) 25008 (dec)
Object name AI_Connector_signalname
Object code
Data type Character string
CiA standard No
Character string String to describe the meaning of the signal
Connector identification
Object description Index 61B1 (hex) 25009 (dec)
Object name AI_Connector_identification
Object code
Data type Character string
CiA standard No
Character string Example: MX840_0009E500080E_12_1_1_1 String to identify the source of the signal.
Modultype_serialnumber_modulID_Connector_Channel_Signal Modul identification can be defined by the
user.
35CANopen
HBMQuantumX
Page 36
36
It is scaled in the physical unit of the field
channel. It is scaled in the physical unit of
Input scaling 1, field value (electrical input, float format, point 1)
Object description Index x120 (hex) 24864 (dec) Note
Object name AI_Input_scaling_1_FV This object defines the field value of the first
Object code Array
Data type Float, INT16, INT24, INT32
CiA standard Yes
Category Optional
Value description
Sub-index
Description Number of entries Input scaling 1 FV1Input scaling 1 FV 2 Input scaling 1 FV
Entry category Mandatory Mandatory Optional Optional
Access ro rw rw rw
PDO mapping No No No No
Value range 1 − 254 Data type specific Data type specific Data type specific
Default value No No No No
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
CANopen
calibration point for the analog input channel.
It is scaled in the physical unit of the field
value.
199
Input scaling 1, process value (physical output, float format, point 1)
Object description Index x121 (hex) 24865 (dec) Note
Value description
Object name AI_Input_scaling_1_PV This object defines the process value of the
Object code Array
Data type Float, INT16, INT24, INT32
CiA standard Yes
Category Optional
Sub-index
Description Number of entries Input scaling 1 PV 1 Input scaling 1 PV 2
Entry category Mandatory Mandatory Optional Optional
Access ro rw rw rw
PDO mapping No No No No
Value range 1 − 254 Data type specific Data type specific Data type specific
Default value No No No No
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
first calibration point for the analog input
channel. It is scaled in the physical unit of
the process value.
Input scaling 1 PV 199
HBM QuantumX
Page 37
Input scaling 2 field value (physical output, float format, point 2)
channel. It is scaled in the physical unit of
channel. It is scaled in the physical unit of
Object description Index x122 (hex) 24866 (dec) Note
Value description
Object name Input_scaling_2_FV This object defines the field value of the
Object code Array
Data type Float, INT16, INT24, INT32
CiA standard Yes
Category Optional
Sub-index
Description Number of entries Input scaling 2
Entry category Mandatory Mandatory Optional Optional
Access ro rw rw rw
PDO mapping No No No No
Value range 1 − 254 Data type specific
Default value No No No No
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
Field value 1
second calibration point for the analog input
channel. It is scaled in the physical unit of
the field value.
Input scaling 2
Field value 2
37CANopen
Input scaling 2
Field value 199
Input scaling 2 process value (electrical input, float format, point 2)
Object description Index x123 (hex) 24867 (dec) Note
Value description
Object name Input_scaling_2_PV This object defines the process value of the
Object code Array
Data type Float, INT16, INT24, INT32
CiA standard Yes
Category Optional
Sub-index
Description Number of entries Input scaling 2
Entry category Mandatory Mandatory Optional Optional
Access ro rw rw rw
PDO mapping No No No No
Value range 1 − 254 Data type specific Data type specific Data type specific
Default value No No No No
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
Process value 1
second calibration point for the analog input
channel. It is scaled in the physical unit of
the process value.
Input scaling 2
Process value 2
Input scaling 2
Process value 199
HBMQuantumX
Page 38
38
to obtain process values
values from the field values:
Process value = (Field value Scaling
Scaling factor
Object description Index 6126 (hex) 24870 (dec) Note
Object name AI_Scaling_Factor This object represents the scaling factor by
Object code Array
Data type Float
CiA standard Yes
Category Optional
Value description
Sub-index
Description Number of entries Scaling factor 1 Scaling factor 2 Scaling factor 199
Entry category Mandatory Mandatory Optional Optional
Access ro rw rw rw
PDO mapping No No No No
Value range 1 − C7 Float Float Float
Default value No 1 1 1
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
CANopen
which the field value needs to be multiplied
to obtain process values.
.
Scaling offset
Object description Index 6127 (hex) 24871 (dec) Note
Value description
Object name AI_Scaling_Offset This object represents the scaling offset
Object code Array
Data type Float
CiA standard Yes
Category Optional
Sub-index
Description Number of entries Scaling offset 1 Scaling offset 2 Scaling offset 199
Entry category Mandatory Mandatory Optional Optional
Access ro rw rw rw
PDO mapping No No No No
Value range 1 − C7 Float Float Float
Default value No 0 0 0
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
which is needed to calculate the process
values from the field values:
Process value = (Field value * Scaling
factor) + Scaling offset
HBM QuantumX
Page 39
Input PV (characteristic curve output unit)
quantity scaled in the physical unit of the
kN,
Object description Index x130 (hex) (dec) Note
Object name AI_Input_PV This object represents the result of the input
Object code Array
Data type Real32, INT16, INT24, INT32
CiA standard Yes
Category Conditional
Value description
Sub-index
Description Number of entries AI_Input_PV 1 AI_Input_PV 2 AI_Input_PV 199
Entry category Mandatory Mandatory Optional Optional
Access ro ro ro ro
PDO mapping No No No No
Value range 1 − C7 Data type specific Data type specific Data type specific
Default value No No No No
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
scaling block and gives the measured
quantity scaled in the physical unit of the
process values (e.g. degrees centigrade, kg,
39CANopen
mm, etc.).
HBMQuantumX
Page 40
40
Physical unit PV (characteristic curve output unit)
Object description Index 6131 (hex) 24881 (dec) Note
Object name Physical_Unit_PV
Object code Array
Data type UINT32
CiA standard 303
Category Conditional
Value description
Sub-index
Description Number of entries Physical unit PV 1 Physical unit PV 2 Physical unit PV 199
Entry category Mandatory Mandatory Optional Optional
Access ro rw rw rw
PDO mapping No No No No
Value range 1 − C7 UINT32 UINT32 UINT32
Default value No No No No
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
CANopen
This object is to assign SI units and prefixes for the process values within the analog input
function block. The structure of the SI unit entry is as follows:
0781516232431
Prefix SI numerator SI denominator Reserved
MSB LSB
The coding of the physical units and prefixes is done according to /5/. Within this profile,
there are some additional physical units specified:
Example:
Code (hex) Physical unit
02 kg
21 N
55 m/s
56 N@m
4E bar
2D °C
05 K
20 Hz
26 V
04 A
2
Unit km/h: prefix 3 for kilos (103)
SI numerator: 1h for m
SI denominator 48h for h
HBM QuantumX
Page 41
Input offset (in the physical output quantity, float format)
scaled in the physical unit of the process
Object description Index 6124 (hex) 24868 (dec) Note
Value description
Object name AI_Input_offset This object defines the additional offset
Object code Array
Data type Float, INT16, INT24, INT32
CiA standard Yes
Category Optional
Sub-index
Description Number of entries Input offset 1 Input offset 2 Input offset 199
Entry category Mandatory Mandatory Optional Optional
Access ro rw rw rw
PDO mapping No No No No
Value range 1 − C7 Data type specific Data type specific Data type specific
Default value No No No No
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
value for the analog input channel. It is
scaled in the physical unit of the process
value.
41CANopen
Autozero
Object description Index 6125 (hex) 24869 (dec) Note
Value description
Object name AI_ A write to this object will zero the input of
Object code
Data type
CiA standard
Category
Sub-index
Description
Entry category
Access
PDO mapping
Value range
Default value
0 (hex) 1 (hex) 2 (hex) to C7 (hex)
the signal.
HBMQuantumX
Page 42
42
Operating mode
Object description Index 6112 (hex) 24850 (dec) Note
Object name AI_Operating_mode
Object code Array
Data type UINT8
CiA standard Yes
Category Optional
Value description
Sub-index
Description Number of entries Operating mode 1
Entry category Mandatory Mandatory
Access ro rw
PDO mapping No No
Value range 1−C7 UINT8
Default value No 0
0 (hex) 1 (hex)
CANopen
Value Meaning
0 Channel off (not operating)
1 Normal operation
2 − 9 Reserved
10 − 255 Implementation specific: 10 Signal_S1
11 Signal_S2
20 Signal_positive_peak
21 Signal_negative_peak
22 Signal_peak_to_peak
30 Signal_rms
100 Signal_CAN
HBM QuantumX
Page 43
General objects
Description Index (hex) Index (dec) Type
Device type 1000 4096 UINT32
Hardware revision 1009 4105 String
Software revision 100A 4106 String
Identity object 1018 4120 Record
Handling of CAN signals on EtherCAT
The MX840 handles full CAN signal conditioning. So the signals are ready-scaled according
to the description in the database.
Further scaling is not possible.
Description of MX840 CAN signals in DS404
43CANopen
The objects
6110h
6114h, 6115h, 6116h, 6118h, 6119h, 611Ah, 611Bh
611Ch
X120h, X121h, X122h, X123h, 6126h, 6127h
X124h
61A0h, 61A2h
are available but will deliver 0, and cannot be changed.
Object 6125h will be ignored.
Objects 61B0h, 61B1h, 6150h and X130h are implemented as in the description above.
HBMQuantumX
Page 44
44
7 Connections
X5 X6 X7 X8 X9
FireWire connections for
additional CX27 modules (without
supply voltage)
Digital inputs and
outputs with LED status
display
X2X2
Ethernet connection
EtherCAT
output
EtherCAT
input
Fig.3.1: CX27 Gateway; front
Supply voltage VG strip cover
X104
Fig.3.2: CX27 Gateway; back
FireWire connections for
MX modules
X100X101X102
Ethernet connection
HBM QuantumX
Page 45
7.1 Supply voltage (socket X104)
There are various ways to supply voltage to the CX27 Gateway module:
• With a power pack via socket X104 at the back
Socket X104
45
1)
Function
Top view
Pin Input / output
1 P Supply voltage 10 to 30 V DC (−)
2 IO I2C bus SDA (data)
3 P Supply voltage 10 to 30 V DC (+)
4 IO I2C bus SCL (clock)
1)
I = input, O = output, P = power or signal reference
• When using the BPX001 backplane, via the VG strip at the back
• Via the FireWire connections at the rear. The FireWire connections at the front do not
carry any supply voltage and thus do not supply the instrument
7.2 FireWire (sockets X5/X6/X101/X102)
Sockets X101 and X102 at the back of the Gateway module are designed for QuantumX
module connection.
Connect the Gateway to the modules as shown in Fig. 2.3 (Gateway socket X102 −−>
module socket X101 −−> module socket X102 ...).
Sockets X5 and X6 at the back of the Gateway are not supported by firmware version
1.0, but can be activated at a later date by a firmware update!
HBMQuantumX
Page 46
46
7.3 Ethernet (sockets X7/X100)
The CX27 Gateway has two equivalent Ethernet interfaces, one at the front (X7) and one at
the back (X100).
Ethernet TCP/IP acts as a central access to all the modules connected to the CX27 Gateway
via FireWire. An LED is integrated into each of the connecting sockets to indicate link status
and transmission activity.
The interfaces can be addressed directly or via DHCP.
7.4 EtherCAT (sockets X8/X9)
Two RJ45 sockets are available at the front for connecting the EtherCAT fieldbus system.
The connection to the master is made via socket X9 (IN), with additional slaves connected
via socket X8 (OUT).
The interfaces support the following Ethernet variants (as per IEEE 802.3) − 100BASE-TX at
100Mbit/s, full-duplex, auto-negotiation and MDI/MDI-X auto-crossover.
HBM QuantumX
Page 47
7.5 Digital inputs and outputs
The CX27 provides two digital inputs (pin 1 or 2) and two digital outputs (pin 3 or 4) on a
screw terminal plug.
The digital IO line can be used in two ways:
A) with external power supply
• in this case connect your power line to pin 2 (24 V)
• voltage level within a range of 5.5 ... 42 V
• maximum load: 100 mA
B) internal power supply
• in this case, please connect pin 8 (UINT) to pin 2 (24 V)
• voltage level is TTL (5.5 V nominal)
• maximum load: 1 mA
47
Input or output status is indicated through a LED below the screw terminal.
Each output is short circuit proof. We recommend to use shielded cable in disruptive
interference. Connector for shield (pin 7) and signal ground (pin 1) are different.
Pin 8: U
Pin 7: Cable shield
Pin 6: 4 − digital OUT 2
Pin 5: 3 − digital OUT 1
Pin 4: 2 − digital IN 2
Pin 3: 1 − digital IN 2
Pin 2: 24 V = external supply voltage
Pin 1: Signal ground
Example with 1 digital input and 1 digital output with internal power supply:
8
7
5
= internal supply voltage
INT
Digital IN:
i.e. trigger
3
Bridge: 24 V to U
INT
Digital OUT: i.e. Status LED
HBMQuantumX
Page 48
48
8 Status display
8.1 System LED
Green Error-free operation
Yellow System not ready, boot procedure running
Flashing yellow Download active, identification detection
Red Error, faulty synchronization
System LED
8.2 Ethernet
Green LED is lit Ethernet link status is ok
Yellow LED flashes Ethernet data transmission ongoing
8.3 EtherCAT
Green LED (Link/Activity LED):
Off EtherCAT has no link
Flashes EtherCAT has a link and data transmission is ongoing
Permanently lit EtherCAT has a link but there is no data transmission
Yellow LED (RUN LED):
Off EtherCAT in INIT state
Flashes slowly EtherCAT in PRE-OPERATIONAL state
Single flash EtherCAT in SAFE-OPERATIONAL state
Permanently lit EtherCAT in OPERATIONAL state
Flashes quickly EtherCAT in BOOTSTRAP state
HBM QuantumX
Page 49
9 Accessories
System accessories
Article Description Order No.
QuantumX backplane (standard) Backplane for max. 9 modules of the QuantumX family;
General information:
− Wall or control cabinet installation (19”);
− Connection of external modules via FireWire possible;
− Power supply: 24 V DC;
− Power consumption: max 5 A (150 W);
Note: Only modules with degree of protection IP20 can be
inserted.
Housing connection element for QuantumX
modules
Mechanical connection elements for QuantumX modules
(IP20 / IP65); Set consisting of 2 housing clips, including
assembly material for fast connection of 2 modules.
Cables
FireWire
IP20
Module to module connection cable 5m FireWire connection cable between QuantumX
Hub to module connection cable 3m FireWire connection cable between hub and
PC to module connection cable 3m FireWire connection cable between PC and
FireWire PC-Card FireWire PC-Card with FireWire B interface for
FireWire Hub FireWire Power Hub for connection of up to 3
modules in IP20 design (length: 5 m); Fitted both
ends with appropriate plugs.
Note: The cable can be used to optionally supply
connected QuantumX modules with voltage (max. 1.5
A, from source to last acceptor).
Order No.: 1-KAB269-5
QuantumX modules in IP20 design (length: 3 m);
Fitted both ends with appropriate plugs.
Note: The cable cannot be used to supply QuantumX
modules with voltage.
Order No.: 1-KAB275-3
QuantumX module (length: 3 m); Fitted both ends
with appropriate plugs.
Note: The cable can be used to optionally supply
connected QuantumX modules via the hub with
voltage (max. 1.5 A, from source to last acceptor).
Order No.: 1-KAB270-3
connection of QuantumX amplifiers to notebook or
PC (via PC CARD adapter)
Order No.: 1-MX-PCCARD
FireWire chains (including supply).
Attention: Hub in IP20 design.
Order No.: 1-MX-FWHUB
1-BPX001
1-CASECLIP
49
Ethernet
Ethernet crossover cable Ethernet patch cable between PC and QuantumX
module in IP65 design (length: 5 m); Fitted both ends
with appropriate plugs.
Order No.: 1-KAB239-2 Order No.: 1-KAB273-5
HBMQuantumX
Page 50
50
9.1 System accessories
9.1.1 BPX001 backplane
9.1.2 Housing connection elements
Covers for housings
with protection class
Housing clip
HBM QuantumX
IP65
Housing clip
Page 51
9.2 Voltage supply
9.2.1 Power pack NTX001
51
Europe mains cable
Mains
UK mains cable
USA mains cable
Australia mains cable
Order No.: 1-NTX001
3 m
NTX001
Modules
HBMQuantumX
Page 52
52
9.2.2 Supply cable
3m 30
Approx. 10−15 mm
Twisted and tinned
Plug ODU Medi-Snap
S11M08-P04MJGO−5280
bk
br
Cable LIYY 2x0.5 mm
+
2
Order No.: 1-KAB271-3 (length 3 m)
9.3 FireWire
9.3.1 FireWire cable (module to module; IP20)
0.2 m
2.0 m
5.0m
Plug ODU
SX1LOC−P08MFG0−0001
Order No.: 1-KAB269-2 (length 2 m)
1-KAB269-0.2 (length 0.2 m)
1-KAB269-5 (length 5 m)
HBM QuantumX
Page 53
10 Abbreviations
Abbreviation Description
CAN Controller Area Network, international, standardized protocol
Cat Category classification of cables also used for Ethernet
CiA CAN in Automation (www.can−cia.org)
CoE CANOpen over EtherCAT, used as a higher-level protocol
DDF Device Description File
EDS Electronic Data Sheet
EtherCAT
FMMU Fieldbus Memory Management Unit
FPGA Field Programmable Gate Array
FV Field Value
MDI Medium Dependent Interface
MDI-X Medium Dependent Interface, crossover cabling
OSI Open System Interconnect
PDO Process Data Objects (real-time module data)
PV Process Value
SDO Service Data Objects (data for module parameterization)
SM Synchronization Manager, controls access to the application
53Abbreviations
(ISO 11898)
communication (the minimum classification for EtherCAT cables
is Category 5).
Ethernet Control Automation Technology
memory
HBMQuantumX
Page 54
54 Accessories
11 Support
Support:
E−mail: support@hbm.com
Internet: www.hbm.com
Headquarters world-wide:
Europe
Hottinger Baldwin Messtechnik GmbH:
Im Tiefen See 45, 64293 Darmstadt, Germany
Tel. +49 6151 8030, Fax +49 6151 8039100
E−mail: info@hbm.com
www.hbm.com
North and South America
HBM, Inc., 19 Bartlett Street, Marlborough, MA 01752, USA
Tel. +1−800−578−4260 / +1−508−624−4500,
Fax +1−508−485−7480
E−mail: info@usa.hbm.com
Asia
Hottinger Baldwin Measurement (Suzhou) Co., Ltd.
106 Heng Shan Road, Suzhou 215009, Jiangsu, VR China
Tel. (+86) 512 68247776, Fax (+86) 512 68259343
E−mail: hbmchina@hbm.com.cn
Up to date addresses of representatives can also be found on the Internet under:
www.hbm.com/vertretungen
HBM QuantumX
Page 55
55Support
HBMQuantumX
Page 56
E Hottinger Baldwin Messtechnik GmbH. All rights reserved.
All details describe our products in general form only.
They are not to be understood as express warranty and do
not constitute liability whatsoever.
Hottinger Baldwin Messtechnik GmbH
Im Tiefen See 45 S 64293 Darmstadt S Germany
Tel. +49 6151 803−0 S Fax: +49 6151 803−9100
Email: info@hbm.com S www.hbm.com
measure and predict with confidence
I2720−2.0 en
Loading...