imc fieldbus conection options
Errors and changes excepted
For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
Table of contents
1. imc fieldbus connection options
................................................................................................................................... 31.1 CAN-Bus
................................................................................................................................... 41.2 LIN-Bus
................................................................................................................................... 51.3 J1587-Bus
................................................................................................................................... 61.4 ARINC-Bus
................................................................................................................................... 71.5 FlexRay-Bus
................................................................................................................................... 81.6 XCPoE Slave
................................................................................................................................... 91.7 XCPoE Master
................................................................................................................................... 101.8 PROFIBUS
................................................................................................................................... 121.9 imc EtherCAT Slave
................................................................................................................................... 131.10 MVB-Bus
................................................................................................................................... 141.11 RoaDyn Interface
2. Fieldbus: Technical Details
................................................................................................................................... 152.1 CAN-Bus Interface
................................................................................................................................... 152.2 J1587-Bus Interface
................................................................................................................................... 152.3 LIN-Bus Interface
................................................................................................................................... 162.4 imc EtherCAT Slave Interface
................................................................................................................................... 162.5 FlexRay-Bus Interface
................................................................................................................................... 162.6 PROFIBUS Interface
................................................................................................................................... 172.7 XCPoE Interface
................................................................................................................................... 172.8 MVB-Bus Interface
................................................................................................................................... 182.9 ARINC-Bus Interface
................................................................................................................................... 182.10 RoaDyn Interface Interface
Index 19
imc fieldbus conection options
Errors and changes excepted 2For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
1. imc fieldbus connection optionsData Sheet Version 3.8
Along with the capture of data with the modular amplifiers, imc measurement devices can also collectdata from digital bus systems. At the moment, the bus systems named in this document are supported.
The data acquired using the bus systems are treated in the same way as other data, and can besynchronously stored and displayed along with these, and jointly subjected along with them tocalculations. Depending on the software- and hardware configurations, targeted output of data onspecific bus systems may also be possible.
Depending on the software and the hardware equipment a purposeful expenditure of data to theadequate bus system is possible.
Device platform, max amount of interface modules in one device:
Physical structure:
All fieldbus interface modules are configuration options ("configurations modules"), devices can onlybe equipped ex-factory with those modules. An exchange or plug-in by the user is not allowed.
Operating conditions:
Depending on the module variety (with/ without extended temperature range), the respective user’sinstructions are described along with the associated housing type.
Power supply:
provided by the measurement system
Data storage:
handled by the measurement system
imc fieldbus conection options
CAN-Bus
Errors and changes excepted 3For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
1.1 CAN-BusCAN-Bus is a fieldbus system with a maximum transfer rate of 1 MBit/s which is widely prevalent andaccepted in the automotive and other manufacturing industries. The imc CAN-Bus Interface offers twoindependent, electrically isolated CAN nodes via which the two CAN-busses can be integrated into an imcmeasurement device both for receiving and sending.
Terminal connection:
2x DSUB-9 (1 isolated node per connector)
Software and the handling:
The module is fully supported by the imc STUDIO and the imc DEVICES operating software for themeasurement system.
Recommended imc software:
imc DEVICES Version 2.7 R3
imc STUDIO Version 3.0 R4
For configuration of the CAN-Bus, a dedicated software assistant is provided.
There are package as additional option available, those package include the following protocols:
ECU-protocols inclusive OBD-2, CCP, KW2000 and XCPoC (XCP over CAN)
Transfer protocol:
CAN High Speed (ISO 11898) 1 Mbaud
CAN Low Speed (ISO11519) 125 Kbaudis software-configurable for each node (is valid for all CAN2 modules,and also for the BUSDAQ/CAN(-ET))
in case of older modules (e.g. CRPL/CAN):CAN Low Speed is not software-configurable, it is available as a defines custom version
Isolation strength:
50 V to system ground (protection ground)
Remarks:
Only with CAN2 fieldbus interface:
Parameterization of imc CANSAS measurement modules directly via the CAN-Bus interface.
Terminator resistor (120 ) can be software-activated for each node.
CAN High Speed and CAN Low Speed is software-configurable for each node
Order code: Article number Remarks
CRFX/CAN2 1190028 for installation in a CRONOSf lex Base UnitCRFX/CAN2-ET 1191019 version in extended temperature rangeCRC/CAN2 1170010 for installation in a CRONOScompact housingCRC/CAN2-ET 1171011 version in extended temperature rangeCRC/CAN2-R 1170133 for installation in a CRONOScompact RACKCRC/CAN2-R-ET 1171092 version in extended temperature rangeCRSL/CAN2 1180009 for installation in a CRONOS-SLCRPL/CAN2 1080147 for installation in a CRONOS-PLCRPL/CAN2-ET 1081104 version in extended temperature rangeSPAR/CAN2 1130095 for installation in a SPARTANSPAR/CAN2-ET 1131038 version in extended temperature rangeBUSDAQ/CAN 1040030 for installation in a BUSDAQBUSDAQ/CAN-ET 1041013 version in extended temperature range
imc fieldbus conection options
LIN-Bus
Errors and changes excepted 4For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
1.2 LIN-BusLIN-Bus is an especially simple and affordable fieldbus standard from the automotive field, which isspecially designed for networking smart sensors and actuators. The gross transfer rates can extend up to20 kBit/s. The imc LIN-Interface offers two independent, electrically isolated nodes which can operate asthe LIN-Master.
Terminal connection:
2x DSUB-9 (1 isolated LIN-node per connector)
Software and the handling:
The module is fully supported by the imc STUDIO and the imc DEVICES operating software for themeasurement system.
Recommended imc software:
imc DEVICES Version 2.7 R3 for all devices with s/n 14xx and 16xx
imc DEVICES Version 2.6 R3 SP14 for all devices with s/n 12xx and 13xx
imc STUDIO Version 3.0 R4
For configuration of the LIN-Bus, a dedicated software assistant is provided.
Transfer protocols:
LIN 2.0 ; LIN 1.3 (both LIN specifications can run on the fieldbus simultaneously)
Isolation strength:
±50 V to system ground (protection ground)
Remarks:
“Master Node” 1 k resistor connectable by software for each node.
Order codes: Article number Remarks
CRFX/LIN 1190029 for installation in a CRONOSf lex Base UnitCRFX/LIN-ET 1191xxx version in extended temperature range
CRC/LIN 1170011 for installation in a CRONOScompactCRC/LIN-ET 1171012 version in extended temperature range
CRC/LIN-R 1170134 for installation in a CRONOScompact RACKCRC/LIN-R-ET 1171093 version in extended temperature range
CRSL/LIN 1180010 for installation in a CRONOS-SL
CRPL/LIN 1080148 for installation in a CRONOS-PLCRPL/LIN-ET 1081105 version in extended temperature range
SPAR/LIN 1130096 for installation in a SPARTANSPAR/LIN-ET 1131039 version in extended temperature range
BUSDAQ/LIN 1040031 for installation in a BUSDAQBUSDAQ/LIN-ET 1041014 version in extended temperature range
imc fieldbus conection options
J1587-Bus
Errors and changes excepted 5For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
1.3 J1587-BusJ1587 is a fieldbus standard particularly widespread in the American truck manufacturing industry as adiagnostics interface. The imc J1587 interface provides an electrically isolated J1587 node.
Terminal connection:
1x DSUB-9
Software and the handling:
The module is fully supported by the imc STUDIO and the imc DEVICES operating software for themeasurement system.
Recommended imc software:
imc DEVICES Version 2.7 R3 SP10
imc STUDIO Version 3.0 R4
For configuration of the J1587-Bus, a dedicated software assistant is provided.
The configuration is realized via an access database and a special additional component (OCX).
Transfer protocols:
J1587
Isolation strength:
±50 V to system ground (protection ground)
Remarks:
Special version with RS485 interface available upon request
Order code: Article number Remarks
CRFX/J1587-2 1190033 for installation in a CRONOSf lex Base UnitCRFX/J1587-2-ET 1191xxx version in extended temperature range
CRC/J1587-2 1170050 for installation in a CRONOScompact housingCRC/J1587-2-ET 1171050 version in extended temperature range
CRC/J1587-2-R 1170xxx for installation in a CRONOScompact RACKCRC/J1587-2-R-ET 1171xxx version in extended temperature range
CRSL/J1587-2 1180104 for installation in a CRONOS-SL
imc fieldbus conection options
ARINC-Bus
Errors and changes excepted 6For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
1.4 ARINC-BusThe ARINC Bus is a fieldbus system specially adapted to aerospace engineering, having transfer rate of upto 100 kBit/s.
Terminal connection:
2x DSUB-15 (imc standard, a custom pin configuration can be realized)8 Rx receive channels, 4 Tx transmit channels
Software and the handling:
The module is fully supported by the imc STUDIO and the imc DEVICES operating software for themeasurement system.
Recommended imc software:
imc DEVICES Version 2.7 R3 SP7 supports the transmitting of messages
imc STUDIO Version 3.0 R4
For configuration of the ARINC-Bus, a dedicated software assistant is provided.
The configuration is realized via an access database and a special additional component (OCX).
Transfer protocols:
ARINC 429
Order codes: Article number Remarks
CRFX/ARINC-8Rx 1190030 for installation in a CRONOSf lex Base UnitCRFX/ARINC-8Rx-ET 1191xxx version in extended temperature range
CRC/ARINC-8Rx 1170012 for installation in a CRONOScompactCRC/ARINC-8RX-ET 1171013 version in extended temperature rangeCRC/ARINC-8Rx-4TX 1170177 version with additionally 4 transmit channelsCRC/ARINC-8Rx-4TX-ET 1170xxx extended temperature range
CRC/ARINC-8RX-R 1170143 for installation in a CRONOScompact RACKCRC/ARINC-8RX-R-ET 1171xxx version in extended temperature rangeCRC/ARINC-8RX-4TX-R 1170178 version with additionally 4 transmit channelsCRC/ARINC-8RX-4TX-R-ET 1171xxx extended temperature range
CRSL/ARINC-8Rx 1180012 for installation in a CRONOS-SL
CRPL/ARINC-8Rx 1080171 for installation in a CRONOS-PLCRPL/ARINC-8Rx-ET 1081117 version in extended temperature range
SPAR/ARINC-8Rx 1130098 for installation in a SPARTANSPAR/ARINC-8Rx-ET 1131041 version in extended temperature range
BUSDAQ/ARINC-8RX 1040xxx for installation in a BUSDAQBUSDAQ/ARINC-8RX-ET 1041015 version in extended temperature range
imc fieldbus conection options
FlexRay-Bus
Errors and changes excepted 7For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
1.5 FlexRay-BusFlexRay is a serial fieldbus system from the automotive industry which serves the purpose of networkingECUs and offers transfer rates of up to 10 MBit/s / channel.
The imc FlexRay Interface enables connection to the associated bus both for receiving (reading) and forsending (writing). The module processes a FlexRay cluster consisting of two FlexRay channels, which canbe operated either in parallel or separately.
Modules of the model "FlexRay2" transfer data at up to 60 kSamples/s per Interface module.
Modules of the model "FlexRay" achieve up to 30 kSamples/s per module and, in conjunction with imcBUSDAQ devices additionally provide a Sleep mode with high-speed starting capability.
Terminal connection:
1x DSUB-9 (channel A & B together)
Software and the handling:
The module is fully supported by the imc STUDIO and the imc DEVICES operating software for themeasurement system.
Recommended imc software:
imc DEVICES Version 2.7 R3 for all devices with s/n 14xx and 16xx
imc DEVICES Version 2.8 for all devices with s/n 13xx
imc STUDIO Version 3.0 R4 for all devices with s/n 14xx and 16xx
imc STUDIO Version 3.1 for all devices with s/n 13xx
For configuration of the FlexRay-Bus, a dedicated software assistant is provided.
Import of Fibex files, with the description of the data transmitted on the bus, is supported. Thesettings can be made via the software assistant
The Interface can transmit Frames. The content of the Frames will be defined via process vector,virtual bits and display variables.
Transfer protocols:
FlexRay protocol specification v3.0
Order code: Article number Remarks
CRFX/FLEXRAY2 1190031 for installation in a CRONOSf lex Base UnitCRFX/FLEXRAY2-ET 1191022 version in extended temperature range
CRC/FLEXRAY2 1170048 for installation in a CRONOScompactCRC/FLEXRAY2-ET 1171048 version in extended temperature range
CRC/FLEXRAY2-R 1170135 for installation in a CRONOScompact RACKCRC/FLEXRAY2-R-ET 1171094 version in extended temperature range
CRSL/FLEXRAY2 1180068 for installation in a CRONOS-SL
SPAR/FLEXRAY2 1130097 for installation in a SPARTANSPAR/FLEXRAY2-ET 1131040 version in extended temperature range
BUSDAQ/FLEXRAY2 1040xxx for installation in a BUSDAQBUSDAQ/FLEXRAY-ET 1041019 version in extended temperature range
imc fieldbus conection options
XCPoE Slave
Errors and changes excepted 8For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
1.6 XCPoE SlaveSlave for Extended Calibration Protocol over Ethernet
Data acquired using the imc measurement device can be provided to other programs via the Ethernet.The ECU protocol XCP is used. Essentially, the imc device acts as an ECU. In consequence, data from theimc measurement device are directly accessible to standard software products from third-partymanufacturers such as Canape from Vector, or INCA from ETAS. Integration of the imc measurementdevice into other environments thus becomes possible as well.
Terminal connection:
1x RJ45 -Ethernet 100 MBit
Software and the handling:
The module is fully supported by the imc STUDIO and the imc DEVICES operating software for themeasurement system.
Recommended imc software:
imc DEVICES Version 2.7 R3 for all devices with s/n 14xx and 16xx
imc DEVICES Version 2.6 R3 SP8 for all devices with s/n 12xx and s/n 13xx
imc STUDIO Version 3.0 R4
For configuration of the XCPoE, a dedicated software assistant is provided.
As signal source the imc device’s process vector is used. This means that the measurementchannels and virtual channels represented by process vector variables are available to externalsubscribers and systems via XCP. The data are available and valid directly after preparation,independently of trigger releases.
The Ethernet enables high-speed data transfer at up to 10 kHz per channel.
Configuration of the XCPoE destination device is accomplished by means of an A2L file createdupon preparation of the measurement.
Data source: The XCPoE Client requests the measured data once the device has been configured.
Transfer protocols:
“XCP -Part 1- Overview”; Ver. 1.0; ASAM e.V.“XCP -Part 2- Protocol Layer Specification” Ver. 1.0; ASAM e.V.“XCP -Part 3- Transport Layer Specification XCP on Ethernet (TCP_IP and UDP_IP)”; Ver. 1.0; ASAM e.V.“XCP -Part 4- Interface Specification”; Ver. 1.0; ASAM e.V.
Isolation strength: 50 V to system ground (protection ground)
Order code: Article number Remarks
CRFX/XCPoE 1190032 for installation in a CRONOSf lex Base UnitCRFX/XCPoE-ET 1191xxx version in extended temperature rangeCRC/XCPoE 1170049 for installation in a CRONOScompactCRC/XCPoE-ET 1171xxx version in extended temperature rangeCRC/XCPoE-R 1170xxx for installation in a CRONOScompact RACKCRC/XCPoE-R-ET 1171xxx version in extended temperature rangeCRSL/XCPoE 1180069 for installation in a CRONOS-SLCRPL/XCPoE 1080200 for installation in a CRONOS-PLCRPL/XCPoE-ET 1081xxx version in extended temperature rangeSPAR/XCPoE 1130xxx for installation in a SPARTANSPAR/XCPoE-ET 1131xxx version in extended temperature rangeBUSDAQ/XCPoE 1040xxx for installation in a BUSDAQBUSDAQ/XCPoE-ET 1041xxx version in extended temperature range
imc fieldbus conection options
XCPoE Master
Errors and changes excepted 9For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
1.7 XCPoE MasterMaster for Extended Calibration Protocol over Ethernet
The imc measurement device can acquire data from a control device by means of the XCP protocol. Thedata are transferred via the Ethernet.
The configuration is performed by means of an A2L-file, which must be available for the control device tobe addressed.
Terminal connections:
1x RJ45 -Ethernet 100 MBit
Software and system handling:
The module is fully supported by the imc STUDIO and the imc DEVICES operating software for themeasurement system.
Recommended imc software:
imc DEVICES Version 2.8 R3 SP9
imc STUDIO Version 4.0 R1
Configuration of the XCPoE destination device is accomplished by means of an A2L file createdupon preparation of the measurement.
Isolation strength: 50 V to system ground (protection ground)
Order code: Article number Remarks
CRFX/XCPoE-MASTER 11900xx for imc CRONOSf lex Base UnitCRFX/XCPoE-MASTER-ET 1191xxx version in extended temperature rangeCRC/XCPoE-MASTER 11700xx for imc CRONOScompactCRC/XCPoE-MASTER-ET 1171xxx version in extended temperature range
imc fieldbus conection options
PROFIBUS
Errors and changes excepted 10For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
1.8 PROFIBUSPROFIBUS-DP has achieved world-wide prevalence as an industrial fieldbus for production- and processautomation. Both sensors and actuators as well as multiple distributed control systems can benetworked at data rates of up to 12 MBit/s.
The imc PROFIBUS Interface allows the steaming communication within a Profibus network to be loggedand interpreted. It provides the ability to extract individual messages from the streaming communicationand to display the data they contain as measurement channels.
To configure the interface, exact knowledge of the Profibus network’s configuration is required. Forinstance, in order to extract a datagram from a message, the following information is needed:
1. the PROFIBUS network's data transfer rate2. the PROFIBUS protocol used3. the bus address of the message's sender4. the bus address of the message's recipient5. Byte/bit offset of the datagram in the message
In general, the information required can be obtained from the configuration of the PROFIBUS Master andthe description of the respective PROFIBUS-Slave (GSD-file).
Note:
Since there is no logic connection to the Profibus network, sending and receiving data as a bus subscriberis not possible. In consequence, the imc PROFIBUS Interface does not constitute either a Profibusmaster-or slave-interface, but is simply an interface via which is able to log the bus communication as anindependent observer (“sniffer”).
Terminal connection: 1x DSUB-9
Software and the handling:
The module is fully supported by the imc STUDIO and the imc DEVICES operating software for themeasurement system.
Recommended imc software:
imc DEVICES Version 2.7 R3 for all devices with s/n 14xx and 16xx
imc DEVICES Version 2.6 R3 SP7 for all devices with s/n 12xx and s/n 13xx
imc STUDIO Version 3.0 R4
For configuration of the PROFIBUS, a dedicated software assistant is provided.
Transfer protocols:
DPV0, DPV1
Isolation strength:
50 V to system ground (protection ground)
Order code: Article number Remarks
CRFX/PROFIBUS 1190xxx for installation in a CRONOSf lex Base UnitCRFX/PROFIBUS-ET 1191xxx version in extended temperature rangeCRC/PROFIBUS 1170146 for installation in a CRONOScompactCRC/PROFIBUS-ET 1171xxx version in extended temperature rangeCRC/PROFIBUS-R 1170147 for installation in a CRONOScompact RACKCRC/PROFIBUS-R-ET 1171xxx version in extended temperature rangeCRSL/PROFIBUS 1180xxx for installation in a CRONOS-SL
CRPL/PROFIBUS 1080xxx for installation in a CRONOS-PL
imc fieldbus conection options
PROFIBUS
Errors and changes excepted 11For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
Order code: Article number Remarks
CRPL/PROFIBUS-ET 1081xxx version in extended temperature range
SPAR/PROFIBUS 1130xxx for installation in a SPARTANSPAR/PROFIBUS-ET 1131xxx version in extended temperature range
BUSDAQ/PROFIBUS 1040xxx for installation in a BUSDAQBUSDAQ/PROFIBUS-ET 1041xxx version in extended temperature range
imc fieldbus conection options
imc EtherCAT Slave
Errors and changes excepted 12For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
1.9 imc EtherCAT SlaveThe fieldbus module EtherCAT Slave Interface (imc ECAT-Slave-IF) provide the integration of imcCRONOSf lex and imc CRONOScompact devices into an automation system with an EtherCAT fieldbus.
The complete imc CRONOS device is integrated via the interface into the in den EtherCAT fieldbus as aSlave module, which is operated by an external EtherCAT Master.
Data from the imc measurement device are thus available throughout an EtherCAT system andintegration of the device into other system environments are possible.
Terminal connection:
2x RJ45 -EtherCAT 100 MBit
Software and the handling:
The module is fully supported by the imc STUDIO and the imc DEVICES operating software for themeasurement system.
Recommended imc software:
imc DEVICES Version 2.7 R3
imc STUDIO Version 3.0 R4
For the configuration, a dedicated software assistant is provided.
As the signal source, the imc device’s process vector is used. This means that the measurementchannels and virtual channels represented by process vector variables are available to externalsubscribers and systems via EtherCAT. The data are available and valid directly after preparation,independently of trigger releases.
Via the interface, it is possible to read and write process vector variables (pv.Variables) of the imcsystem. Reading and writing can occur either cyclically or irregularly.
Cyclical data are transmitted cyclically after the Fieldbus and the imc measurement system start.
Irregular data can be queried sporadically by the EtherCAT Master by means of the protocol CoE(CANopen over EtherCAT), which is supported by the imc system.
Configuration and parameterization of the imc measurement system are easy to perform using thedevice software imc STUDIO, by means of which an "EtherCAT-Slave-Information" document (ESI)can be created or exported in XML-format. This serves the purpose of system configuration for theEtherCAT Master.
Alternatively or additionally, parameterization of the imc systems via the CoE protocol is possible.
Transfer protocol:
EtherCAT Specification – Part 4 - Data Link Layer protocols specification
EtherCAT Specification – Part 6 - Application Layer protocol specification
Order code: Article number Remarks
CRFX/ECAT-Slave 1190040 for installation in a CRONOSf lex Base UnitCRFX/ECAT-Slave-ET 1191038 version in extended temperature range
CRC/ECAT-Slave 1170026 for installation in a CRONOScompactCRC/ECAT-Slave-ET 1171023 version in extended temperature range
CRC/ECAT-Slave-R 1170xxx for installation in a CRONOScompact RACKCRC/ECAT-Slave-R-ET 1171xxx version in extended temperature range
imc fieldbus conection options
MVB-Bus
Errors and changes excepted 13For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
1.10 MVB-BusMVB is the abbreviation of "Multipurpose Vehicle Bus". This is a serial communication bus for railvehicles. It connects control devices with each other as well as with simple sensors and actuators.
The MVB is standardized by the International Electrotechnical Commission (IEC) and the "DeutschesInstitut für Normung (DIN)", as well as other bodies.
The MVB-Bus Interface integrates the associated fieldbus into an imc measurement device in order tomake the measurement channels, status information and control communication already in the vehicleavailable. Upon request, it can be equipped with fiber-optical transmittance instead of wire-basedelectrical coupling, in order to meet electric rail vehicles’ special requirements in terms of immunity toelectromagnetic interference.
Terminal connection:
2x DSUB-9
Software and the handling:
The module is fully supported by the imc STUDIO and the imc DEVICES operating software for themeasurement system.
Recommended imc software:
imc DEVICES Version 2.8
imc STUDIO Version 4.0
For configuration of the MVB-Bus, a dedicated software assistant is provided.
Remarks regarding operational reliability:
The interface is hard-wired for either EMD or ESD+. The user must ensure that the device isconnected to and operated by only one bus which conforms to the selected standard. Correctfunctioning of the MVB bus is not guaranteed in case of incorrect (incompatible) wiring, which maylead to disturbance of the bus communication, malfunctioning of third–party bus subscribers, oreven irreversible damage to the device.
Order code: article number remarks
CRFX/MVB 1190081 for installation in a CRONOSf lex Base UnitCRFX/MVB-ET 1191023 version in extended temperature range
CRC/MVB 1170xxx for installation in a CRONOScompactCRC/MVB-ET 1171xxx version in extended temperature range
CRC/MVB-R 1170xxx for installation in a CRONOScompact RACKCRC/MVB-R-ET 1171xxx version in extended temperature range
imc fieldbus conection options
RoaDyn Interface
Errors and changes excepted 14For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
1.11 RoaDyn InterfaceThe RoaDyn® Interface provides the interface between the wheel force transducer system RoaDyn®System 2000 by Kistler and an imc CRONOS measurement device.
Along with the RoaDyn® system’s (3x force, 3x torque, angle, angular velocity, temperature, supplyvoltage) main channels, all additional service channels (single force components, errors etc.) areavailable.
Terminal connection:
2x BNC (Trigger und SYNC)
1x RJ45
Software and the handling:
The module is fully supported by the imc STUDIO and the imc DEVICES operating software for themeasurement system.
Recommended and tested imc software:
imc STUDIO Version 3.0 R4 and imc STUDIO Version 4.0 R1 and higher
imc DEVICES Version 2.7 R3 and imc DEVICES Version 2.8 R3 and higher
For the RoaDyn® configuration a dedicated software assistant is provided. The handling of thisassistant is described in the software manual.
The imc CRONOS measurement system has to be expanded with imc Online FAMOS Professional.
Order code: Article number Remarks
CRFX/RoaDyn 1190084 for installation in a CRONOSf lex Base UnitCRFX/RoaDyn-ET 1191xxx version in extended temperature range
CRC/RoaDyn 1170150 for installation in a CRONOScompactCRC/RoaDyn-ET 1171xxx version in extended temperature range
CRC/RoaDyn-R 1170151 for installation in a CRONOScompact RACKCRC/RoaDyn-R-ET 1171xxx version in extended temperature range
imc fieldbus conection options
CAN-Bus Interface
Errors and changes excepted 15For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
2. Fieldbus: Technical Details2.1 CAN-Bus Interface
Parameter Value Remarks
Number of CAN-nodes 2
Connector plug 2x DSUB-9 per module for each of CAN_IN / CAN_OUT
Transfer protocol CAN High Speed1 MBaud (ISO 11898)
CAN Low Speed125 KBaud (ISO 11519)
default
switchable per software
Max. cable length at dataTransfer rate 25 m at 1000 kBit/s
90 m at 500 kBit/s
CAN High Speedcable delay 5,7 ns/m
Termination 124 switchable by software for each node
Parameterize ofimc CANSAS modules
yes current modules type "CAN2" and BUSDAQ/CAN(-ET)
Isolation strength ±50 V to system ground (protection ground)
2.2 J1587-Bus Interface
Parameter Value Remarks
Number of J1587 plugs 1
Terminal connection 1x DSUB-9
Transfer protocol J1587
with RS485 interface custom version: special order
Isolation strength ±50 V to system ground (protection ground)
2.3 LIN-Bus Interface
Parameter Value Remarks
Number of LIN-nodes 2
Terminal connection 2x DSUB-9 per module for each of LIN_IN / LIN_OUT
Transfer protocol LIN 2.0, 2.1, LIN 1.3
1-20 kBaud adjustable
both LIN specifications can run on a bussimultaneously
Isolation strength ±50 V to system ground (protection ground)
imc fieldbus conection options
imc EtherCAT Slave Interface
Errors and changes excepted 16For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
2.4 imc EtherCAT Slave Interface
Parameter Value Remarks
Sendable channel types process vector
Receivable channel types process vector
Terminal connection 2x RJ45 EtherCAT in / out
Transfer protocol EtherCAT Specification – Part 4 Data Link Layer protocols specification
EtherCAT Specification – Part 6Application Layer protocol
specification
Along with cyclical data transfer on thebasis of EtherCAT, the interface isparameterized using CANopenâ overEtherCAT (CoE)
Data rate up to 100 kHz per channel
Highest bus data rate 200 µs (5 kHz)
Highest possible cyclicallytransferable channel count
Bus data rate / 4,5 µs - 10 max. 34 channels at 200 µs bus rate
2.5 FlexRay-Bus Interface
Parameter Value Remarks
Number of clusters 1 1x channel A+B
Terminal connection 1x DSUB-9 per module optionally with two connectors
Transfer protocol FlexRay protocol specification v3.0
Baud rate 2.5 / 5.0 or 10.0 MBit
Data rate
max 30 kSample/s
max 60 kSample/s
per module
current modules type FlexRay2
2.6 PROFIBUS Interface
Parameter Value Remarks
Transfer protocol DPV0, DPV1
Terminal connection 1x DSUB-9 per module
Sendable channel types not supported
Baud rate max. 12 MBit per connector
Isolation strength ±50 V to system ground (protection ground)
imc fieldbus conection options
XCPoE Interface
Errors and changes excepted 17For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
2.7 XCPoE Interface
Parameter Value Remarks
Terminal connection 1x RJ45
Data rate max. 10 kHz per channel
Transfer protocol XCP -Part 1- Overview; Ver. 1.0; ASAM e.V.
XCP -Part 2- Protocol Layer Specification Ver. 1.0; ASAM e.V.
XCP -Part 3- Transport Layer Specification XCP on Ethernet(TCP_IP and UDP_IP)”; Ver. 1.0; ASAM e.V.
XCP -Part 4- Interface Specification; Ver. 1.0; ASAM e.V.
An A2L-file isgenerated uponpreparation of themeasurement, withwhich the XCPoEreceiver can beconfigured.
Transmittable channel type process vector
Ethernet 100 Mbit
Isolation strength ±50 V to System ground(protection ground)
2.8 MVB-Bus Interface
Property Characteristics
Node 1
Transmission medium Copper: twisted pair, RS485
Terminal connection 2x DSUB-9
Topography Bus
Standardize IEC 61375-3-1Electronic Railway Equipment - Train Communication Network - Part 3-1:
MVB - Multipurpose Vehicle BusIEC 61375-3-2
Electronic railway equipment - Train communication Network - Part 3-2: MVB -Multipurpose Vehicle Bus Conformance Testing
Physical Layer EMD Electrical Middle distance mediumnon-reactive tapping of data
or as an option (alternatively) an interface supporting:
ESD+ Electrical short distance(a different hardware version1 of the MVB-Bus interface support ESD+,
EMD is not supported with this hardware version any more)
Line length 200 m with up to 32 subscribers
Redundancy Duplication: messages sent on both lines
Gross data rate 1.5 MBit/s
Reaction time typically 4 µs, max. 43 µs
Address room 4095 physical devices, 4095 logical ports, 8-bit station addresses for messages
Frame size 16,32, 64, 128 and 256 Bit
Operation mode Cyclical for process data, sporadic for message data with arbitration
1 An enhanced future version of the module is in preparation, which will not limit the EMD/ESD+ selection to a fixed order option, butwill make the choice flexibly selectable by means of the front panel configuration switch.
imc fieldbus conection options
ARINC-Bus Interface
Errors and changes excepted 18For more information, contact:
Berlin: +49 - 30 - 46 70 90 - 0
2014-03-19
2.9 ARINC-Bus Interface
Parameter Value typ. min. / max. Remarks
Number of Rx-channels 8
Number of Tx-channels 4
Terminal connection 2x DSUB-15
Transfer protocol ARINC 429
Low (12.5 kbit/s)
High (100 kbit/s)
Max. voltage for each Rxconnection
29 V to System ground (protection ground)
Max. voltage for each Txconnection
5 V 4.5 V / 5.5 V to GND"ZERO": min -0.25 V .. max 0.25 V
10 V 9 V / 11 V differential"ZERO": min -0.25 V .. max 0.25 V
2.10 RoaDyn Interface InterfaceThe RoaDyn® Interface provides the interface between the wheel force transducer system RoaDyn® 2000by Kistler and an imc CRONOS measurement device. The compatible Kistler unit version is 4.01a, 4.01band c with DSP-Type_ VC33.
Along with the RoaDyn® system’s (3x force, 3x torque, angle, angular velocity, temperature, supplyvoltage) main channels, all additional service channels (single force components, errors etc.) areavailable.
Parameter Value Remarks
Nodes Interface for a Kistler 2000 systemmax. 4 wheels
Terminal connection 2x BNC
RJ45
Clock and Trigger
for the data exchange
Channels all channels of the
RoaDyn® system available:
10 main channels ( 3x force,3x torque, angle, angular velocity,
temperature, supply voltage
additionally all service andadditional-channels
(single force, error cases etc.)
Transmitting medium Ethernet 100 MBit 10/100 MBit, approvable cable length for100 MBit Ethernet max. 100 maccording IEEE 802.3
Delay of tested Kistler unit - Version: 4.01a- DSP-Type: SBC31
2 ms plus 16 Samlpes complete delay is compensated in thedata processingimc Online FAMOS calculate with correctmeasurement valueimc Curve Window
Sampling rate max. 1 kHzsynchronized to imc system
Errors and changes excepted
Index
- A -ARINC-Bus
Technical details 18
- C -CAN-Bus
Technical details 15
- E -EtherCAT Slave
Technical details 16
- F -FlexRay
Technical details 16
- J -J1587-Bus
Technical details 15
- L -LIN-Bus
Technical details 15
- M -MVB-Bus
Technical details 17
- P -PROFIBUS
Technical details 16
- R -RoaDyn
Technical details 18
- T -Technical details
ARINC-Bus 18CAN-Bus 15EtherCAT Slave 16FlexRay 16J1587-Bus 15LIN-Bus 15MVB-Bus 17PROFIBUS 16RoaDyn 18XCPoE 17
- X -XCPoE
Technical details 17